OpenText Vendor Invoice Management For SAP Solutions 7.5 SP5 - Installation Guide English (VIM070500-05-IGD-En-2)

OpenText™ Vendor Invoice Management
for SAP® Solutions
Installation Guide
This guide describes the installation of all Vendor Invoice

Management (VIM) components: Vendor Invoice Management
SAP ERP component, Business Center components, optional
OpenText Approval Portal, optional Mobile Approval Portal,
optional KPI Dashboard, optional Vendor Invoice Management
ABAP CDS views component, optional Vendor Invoice
Management SAP CRM SAP Shared Service Framework
component, optional Vendor Invoice Management SAP
NetWeaver® Business Warehouse (VIM BW) component,
optional Vendor Invoice Management SAP NetWeaver
Gateway component, optional Vendor Invoice Management
Supplier Self Service component, optional Vendor Invoice
Management ARIBA Integration component, optional Vendor
Invoice Management ABAP OTVIMS4 component, optional
Vendor Invoice Management Integration with ARIBA, PI
Scenario objects, and optional Vendor Invoice Management
ABAP Invoice Analysis app components.
VIM070500-05-IGD-EN-2
OpenText™ Vendor Invoice Management for SAP® Solutions
Installation Guide
VIM070500-05-IGD-EN-2
Rev.: 21. Dec. 2016
This documentation has been created for software version 7.5 SP5.
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 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
Support: https://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2016 Open Text. All Rights Reserved.

Trademarks owned by Open Text.
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
Part 1 About Vendor Invoice Management 9
1 About this document ............................................................... 11

1.1 Target audience .............................................................................. 11
1.2 Document overview ......................................................................... 11
Part 2 Vendor Invoice Management SAP ERP component

installation 13
2 Preparing installation .............................................................. 15

2.1 General .......................................................................................... 15
2.2 Password control ............................................................................ 16
2.3 Checking prerequisites .................................................................... 16
2.4 Notes on transports ......................................................................... 18
3 Installing the OpenText package ........................................... 19

3.1 Installing the package ...................................................................... 19
3.2 Post installation activities ................................................................. 20
3.3 Language packs ............................................................................. 37
4 Verifying installation ............................................................... 39
5 Installing Single Click Entry for SAP GUI .............................. 41
6 Installing a VIM Support Package .......................................... 43

6.1 SAP ERP prerequisites ................................................................... 43
6.2 Handling workflow container inconsistencies ..................................... 44
6.3 SAP installation ............................................................................... 45
6.4 Post installation activities after installing a new SP ............................ 51
7 Upgrading ................................................................................. 53
7.1 Upgrade overview ........................................................................... 53
7.2 Handling workflow container inconsistencies ..................................... 55
7.3 Upgrading SAP ERP ....................................................................... 56
7.4 Upgrading VIM ................................................................................ 60
7.5 SAP S/4HANA conversion ............................................................... 66
7.6 Post installation activities after an upgrade ........................................ 67
8 Troubleshooting ...................................................................... 73
8.1 FAQs ............................................................................................. 73
Part 3 Business Center components installation 75
9 Business Center components and packages ....................... 77
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide iii
VIM070500-05-IGD-EN-2
Table of Contents
10 Summary of installation steps ............................................... 81
Part 4 KPI Dashboard installation 83
11 Installing the KPI Dashboard .................................................. 85
12 Post installation activities ...................................................... 87

12.1 Activating the SAP Web Dynpro service ........................................... 87
12.2 Setting the connection for the SAP Web Dynpro service .................... 92
12.3 Setting up the SAP NetWeaver Portal integration .............................. 93
Part 5 OpenText Approval Portal installation 97
13 Preparing installation .............................................................. 99

13.1 Installation prerequisites .................................................................. 99
13.2 Installation components ................................................................. 102
13.3 System architecture ...................................................................... 102
14 Installing Web Viewer/Brava! View for the Approval

Portal ...................................................................................... 107
15 Installing the Approval Portal ............................................... 109

15.1 JCo3 migration considerations ....................................................... 109
15.2 Preparing the installation ............................................................... 110
15.3 Configuring the administrator role ................................................... 113
15.4 Deploying the Software Component Archive ................................... 118
15.5 Deploying the Software Component Archive with SAP NetWeaver
7.3 ............................................................................................... 125
15.6 Deploying the Software Component Archive using SUM .................. 128
16 Configuring SAP NetWeaver Portal components ............... 133

16.1 Creating AppIntegrator iViews for users .......................................... 133
16.2 Creating AppIntegrator iViews for users with SAP NetWeaver 7.3,
7.4, and 7.5 .................................................................................. 139
16.3 Creating roles for users ................................................................. 149
16.4 Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5 ........ 153
16.5 Assigning roles to SAP NetWeaver Portal users .............................. 156
16.6 Configuring iViews and roles for the administrator ........................... 157
16.7 Administering the OpenText Approval Portal ................................... 158
17 Applying a new patch ............................................................ 159
18 Upgrading the Approval Portal from previous versions .... 161
19 Troubleshooting .................................................................... 163
iv OpenText Vendor Invoice Management for SAP Solutions – Installation Guide

VIM070500-05-IGD-EN-2
Table of Contents
20 Supporting installation of the standalone NWAS Portal

and Mobile Approval Portal on Unix or Linux ..................... 165
21 Uninstalling the Approval Portal .......................................... 167

21.1 Uninstalling using Software Deployment Manager ........................... 167
21.2 Uninstalling with SAP NetWeaver 7.3, 7.4, and 7.5 .......................... 168
21.3 Removing SAP NetWeaver Portal components ............................... 169
21.4 Deleting properties files ................................................................. 170
21.5 Optional: Removing the startup parameter in the Config Tool ........... 170
Part 6 Mobile Approval Portal installation 173
22 Introduction to the Mobile Approval Portal ......................... 175
23 Authentication for the Mobile Approval Portal ................... 179
24 Installing Web Viewer for the Mobile Approval Portal ....... 181
25 Installing the Mobile Approval Portal .................................. 183

25.1 Installing the Mobile Approval Portal on standalone NWAS
7.0/7.3/7.4 .................................................................................... 183
25.2 Installing the Mobile Approval Portal on SAP NetWeaver Portal
7.0/7.3/7.4/7.5 ............................................................................... 183
Part 7 Vendor Invoice Management ABAP CDS views

component installation 185
26 Preparing installation ............................................................ 187

26.1 Password control .......................................................................... 187
26.2 Checking prerequisites .................................................................. 187
27 Installing the OpenText package ......................................... 189
Part 8 Vendor Invoice Management SAP CRM SAP Shared

Service Framework component installation 191

30 Post installation activities .................................................... 199

30.1 Activating business configuration sets in the CRM system ............... 199
30.2 Maintaining a logical system for the CRM system in VIM .................. 203
30.3 Installing Support Packages 1 and 2 ............................................... 203
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide v

VIM070500-05-IGD-EN-2
Table of Contents
31 Verifying installation ............................................................. 205
Part 9 Vendor Invoice Management SAP NetWeaver Business

Warehouse component installation 207

34 Verifying the installation ....................................................... 215
35 Upgrading SAP NetWeaver BW ............................................ 217
Part 10 Vendor Invoice Management component for SAP

NetWeaver Gateway installation 219

Part 11 Vendor Invoice Management Supplier Self Service


40.1 Installation prerequisites ................................................................ 231
40.2 Installation components ................................................................. 232
40.3 System architecture ...................................................................... 232
41 Installation on the SAP HANA Cloud ................................... 233

41.1 Preparing the installation ............................................................... 233
41.2 Deploying the application on the SAP HANA Cloud Server .............. 233
41.3 Installing the SAP HANA Cloud connector ...................................... 235
Part 12 Vendor Invoice Management ARIBA Integration


vi OpenText Vendor Invoice Management for SAP Solutions – Installation Guide

VIM070500-05-IGD-EN-2
Table of Contents

45.1 Activating business configuration sets for the OTVIMARB
component ................................................................................... 245
Part 13 Vendor Invoice Management ABAP OTVIMS4 component

installation 247

Part 14 Vendor Invoice Management integration with Ariba, PI

scenario objects installation 253
48 Importing ABAP workbench objects ................................... 255
Part 15 Vendor Invoice Management ABAP Invoice Analysis app

components installation 257

50 Setup for the Invoice Analysis app ...................................... 261

50.1 System landscape ......................................................................... 262
50.2 Configuring network options ........................................................... 263
50.3 Checking the Fiori landscape ......................................................... 263
51 Installing the OpenText packages ....................................... 265
52 Activating services ................................................................ 267

52.1 Enabling OData service ................................................................. 267
52.2 Activating the service .................................................................... 268
52.3 Activating the service nodes on BSP and UI5 .................................. 269
53 Integrating the Invoice Analysis app into Fiori

Launchpad ............................................................................. 271
GLS Glossary 277
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide vii
VIM070500-05-IGD-EN-2
Part 1
About Vendor Invoice Management
Part 1 About Vendor Invoice Management
Vendor Invoice Management (VIM) is a packaged business solution that basically

solves a business problem – paying correct amount to vendors on-time. VIM is an
add-on to your SAP ERP system, the majority of its functions and processes run
inside the SAP ERP system; it deals only with invoices that will be posted to SAP
ERP. It integrates with standard SAP functions such as Invoice Verification,
Financial Processing, and so on.
Patches Patches (Hot Fixes), Support Packages and the latest versions of the Release Notes
for VIM are available on OpenText My Support: https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/10151605. The latest versions of the documentation are
also available on My Support: https://knowledge.opentext.com/knowledge/
llisapi.dll/Open/10151494.
For SAP Invoice Management by OpenText customers: To obtain access to My

Support, initiate a ticket request in SAP Service Marketplace.
For OpenText customers: Send an email to support@opentext.com.
Important note for SAP Reseller Customers
For information about all OpenText products resold by SAP (including VIM
and ICC), check SAP Marketplace Note 1791874: SAP Products by OpenText
- Software and Support Lifecycle. This note provides detailed information
about software life cycle, access to Support Packages, access to latest
documentation, language packages, and other patches, as well as Support
ticket handling.
10 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide

VIM070500-05-IGD-EN-2
Chapter 1
About this document
1.1 Target audience

This document addresses those who participate in the administration and
maintenance of Vendor Invoice Management (VIM). This includes
• SAP Basis Administrators

• SAP Workflow Administrators
• SAP Configuration and Development Support
VIM features the optional component Web Invoice Approval. The target audience for
this component includes:
• Site administrators
• Database administrators
• Network administrators
1.2 Document overview

This Installation Guide includes the complete installation information for all Vendor
Invoice Management components:
• “About Vendor Invoice Management” on page 9

• “Vendor Invoice Management SAP ERP component installation” on page 13
• “Business Center components installation” on page 75
• “KPI Dashboard installation” on page 83
• “OpenText Approval Portal installation” on page 97
• “Mobile Approval Portal installation” on page 173
• “Vendor Invoice Management ABAP CDS views component installation”
on page 185
• “Vendor Invoice Management SAP CRM SAP Shared Service Framework
component installation” on page 191
• “Vendor Invoice Management SAP NetWeaver Business Warehouse component
installation” on page 207
• “Vendor Invoice Management component for SAP NetWeaver Gateway
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 11

VIM070500-05-IGD-EN-2
Chapter 1 About this document
• “Vendor Invoice Management Supplier Self Service component installation”

on page 229
• “Vendor Invoice Management ARIBA Integration component installation ”
on page 237
• “Vendor Invoice Management ABAP OTVIMS4 component installation”
on page 247
• “Vendor Invoice Management integration with Ariba, PI scenario objects
• “Vendor Invoice Management ABAP Invoice Analysis app components

VIM070500-05-IGD-EN-2
Part 2
Vendor Invoice Management SAP ERP
component installation
Part 2 Vendor Invoice Management SAP ERP
This part describes the installation of the SAP ERP component of Vendor Invoice
Management (VIM).
Note: With VIM 7.5 SP3 and later, VIM supports SAP S/4HANA on Premise, as
well. There is no separate installation guide for the S/4HANA version, but
there are separate Release Notes. In general, what is said in this guide for SAP
ERP, is valid as well for SAP S/4HANA on Premise. If this is not the case, there
is an explicit remark.

VIM070500-05-IGD-EN-2
Chapter 2
Preparing installation
2.1 General
Caution
The following information is very important. Read the table carefully
before the installation.
Disclaimer This guide delivers an overview of the installation procedures.

OpenText disclaims all warranties for an unauthorized use of this
guide. Any unauthorized use is conducted on your own
responsibility excluding any liability of OpenText. If you have
any questions, contact OpenText Global Technical Services.
Supported versions 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 this guide are superseded by the versions
specified in the Release Notes.
OpenText Support If you require additional help with technical problems, contact
Center OpenText Customer Support. You can find the contact
information for your region at http://www.opentext.com/support.
Important
Make sure the SAP workflow system is configured to run workflows. To
check this, run the SWU3 transaction. Make sure most of the relevant items are
configured correctly, indicated by the icon. It is very important that, in the
Maintain Runtime Environment node, Configure RFC destination has the
icon.
Note: Check for and download the available latest support packs and hot fixes
on OpenText My Support: https://knowledge.opentext.com/knowledge/
llisapi.dll/Open/10151605.

VIM070500-05-IGD-EN-2
Chapter 2 Preparing installation
2.2 Password control

The OpenText Vendor Invoice Management package is protected with a specific
password. During installation, this password is requested by the SAP Add-On
Installation Tool (SAINT).
The following table shows the passwords for VIM installation, SAP ERP upgrade
and VIM upgrade.
VIM Package SAP ERP 6.0

VIM installation 3AF9DE6C3A
SAP ERP upgrade 3AF9DE6A2D
VIM upgrade 3AF9DE6C3D
2.3 Checking prerequisites

2.3.1 Required knowledge
The following knowledge is required for 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
2.3.2 SAP ERP prerequisites

Check the following prerequisites prior to installation:
SAP ERP 6.0
• Support Package Manager (transaction code SPAM) level 35

• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s AS
ABAP
• Apply OSS note 1462364: Dependent structure has inconsistent runtime object
after mass activation. This is specific to SAP ERP 6.0 system, up to EHP5.
• Apply OSS note 1390369: ALV graphic: Double number of bars
• For a list of available software components, check OSS note 2068615: SAP Invoice
Management by OpenText 7.5
The following components must be installed for SAP ERP 6.0 up to EHP8:

VIM070500-05-IGD-EN-2
2.3. Checking prerequisites
Option Component: SAP_BASIS

Release Level Support package
1 700 0013 SAPKB70013
2 701 0003 SAPKB70103
3 702 0003 SAPKB70203
4 higher -
Note: For a list of all currently supported combinations of VIM versions and
SAP products, see SAP Note 2339256 (https://launchpad.support.sap.com/#/
notes/2339256).
2.3.3 Workflow customizing

Make sure the SAP workflow system is configured to run workflows.
To check for correct workflow configuration:
• Run the SWU3 transaction.

Make sure that the complete section Maintain Runtime Environment is
configured correctly, indicated by the icon.
2.3.4 Installation tool

OpenText Vendor Invoice Management 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) that can be extracted using the SAPCAR command line tool. The different
SAPCAR files are located in a DATA folder below the respective package folder named
as the package and SAP release.

VIM070500-05-IGD-EN-2
2.4 Notes on transports

This section applies to EHP5 and higher. SAP has implemented additional checks
during the import of transports.
Some steps of the installation and upgrade procedures make use of transports. These
transports have been created in the OpenText development or packaging systems.
These systems do not have the same components and component versions as your
systems. So, when the transport is imported, you must select the Ignore invalid
component version check box.

VIM070500-05-IGD-EN-2
Chapter 3
Installing the OpenText package
This chapter describes the installation of the Basis package of Vendor Invoice
Management (VIM) on an SAP ERP system. Read also “Preparing installation“
on page 15 with general information on installation in an SAP environment.
3.1 Installing the package

The basic components are installed with the Basis package.
To install the Basis package:
1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAP
application server in the \usr\sap\trans folder (this is the parent folder of the
DIR_EPS_ROOT folder).
SAP version File Source path Target path

SAP ERP 6.0 OTEXVIM_INST_750_70 INST_ERP\DATA\ \usr\sap\trans
0.SAR \EPS
2. 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. Add the support packages to the queue now. Adding support packages at this
point saves time and is a safer variant of the installation.
Important
• If your SAP system is ERP 6.0 EHP8 or later, respectively S/4HANA
1511 on premise or later, add at least the VIM 7.5 support packages
SP1, SP2, and SP3 to the installation queue.
• After that, start the import and start the installation with target
support level SP3 or later.
• Do not try to import only the basis package, you will get stuck.
4. Carry out the import of the package(s) as described in the respective SAP
documentation.
5. To finish installation, install the most recent VIM 7.5 Support Package (SP). You
find the SPs on My Support: https://knowledge.opentext.com/knowledge/cs.dll/
Open/10151605. For further information, see the Release Notes of the respective
SP.

VIM070500-05-IGD-EN-2
Chapter 3 Installing the OpenText package
3.2 Post installation activities

To ensure the integrity of the installed transports, you have to perform and validate
the following procedures:
• “Activating Business Configuration Sets” on page 20

• “Configuring workflow dialog tasks” on page 22
• “Refreshing SAP workflow runtime buffer” on page 24
• “Configuring object services” on page 25
• “Maintaining number ranges” on page 27
• “Linking events for VIM workflows” on page 30
• “Maintaining the SAPscript form for approval” on page 32
• “Maintaining standard text” on page 34
• “Setting background user parameters for Non PO invoice posting” on page 36
• “Configuring additional settings” on page 36
• “Installing transport with layout variants” on page 37
3.2.1 Activating Business Configuration Sets

Important
This section is only relevant for VIM installation. For an SAP and VIM
upgrade, do not perform the actions described in this section. In case of a
VIM upgrade, previous VIM configuration data will be overwritten after
activating Business Configuration Sets (BC Sets). Any custom changes
performed in a previous version of VIM need to be redone after the BC Sets
activation.
Notes
• For every client, you must activate new BC Sets after installing VIM 7.5.
• You have to login in English to activate the BC Sets.
• Always use “Expert mode” to activate the BC sets.
• You need the appropriate security authorization to run some of the
transactions.
• Depending on the SAP version, the following screens might look different on
your system.
Activate BC Set /OTEXVIM/VIM75_BASELINE_LEGACY
Activate the BC set in the Configuration client of the Development system and create
a transport from BC set activation, move the transport to required systems.

VIM070500-05-IGD-EN-2
3.2. Post installation activities
Don’t activate the BC set in the production system. Create a customization transport
in Development System configuration client by activating the BC set and move it to
desired systems.
To activate BC Sets:
1. To access the Business Configuration Sets: Activation screen, run the SCPR20
transaction.
2. Enter the BC set name /OTEXVIM/VIM75_BASELINE_LEGACY and click the

Activate button .
Note: If you are prompted to create a new transport, follow your standard
change request process for tracking changes.
3. Apply the recommended settings, as shown in the screenshot.
4. Click the Activate button.

After BC Set activation, a message is displayed in the lower left of the SAP GUI,
for example: Activation ended with warning.

VIM070500-05-IGD-EN-2
Tip: You can ignore any warnings during the activation. If you get an
error during activation of a BC set, then activate it again. In many cases the
error will disappear. You can ignore activation errors like No data found
for writing activation links for object <xxx>.
5. After you have activated the BC set /OTEXVIM/VIM75_BASELINE_LEGACY,

continue and activate BC set /OTEXVIM/VIM75_BASELINE_NEWFOR75.
3.2.2 Configuring workflow dialog tasks

Use the instructions in this section to set the attribute to “General Task” for the
following tasks:
Table 3-1: Workflow dialog tasks
Task Dialog Task ID

1 DP WF 00275278
2 PO Parked 00275262
3 PO Blocked Line level 00275265
4 PO Blocked Header 00275267
5 NPO parked 00275260
6 IAP 00275253
7 Referee workitem 00275283
To configure a General Task:
1. Run the PFTC transaction.
2. In the Task type field, select Standard task, enter the task ID and click the
button.

VIM070500-05-IGD-EN-2
3. In the Standard Task: Display screen, select Additional data > Agent
assignment > Maintain.
4. In the Standard task: Maintain Agent Assignment screen, select the name of
the assignment and then click the Attributes button.

VIM070500-05-IGD-EN-2
5. In the Task popup, select General Task and click the Transfer button.
The standard task is now configured as a General Task.
If you are prompted to create a new transport, continue with the next step.
If you are asked if you want to Transfer missing elements from the object
method?, click No.
6. Follow your standard change request process for tracking changes.
7. Repeat the procedure for all the tasks mentioned in Table 3-1 on page 22.
3.2.3 Refreshing SAP workflow runtime buffer

For proper operation of VIM, you need to refresh the SAP workflow runtime buffer.
To refresh runtime buffer:
1. Run the SWU_OBUF transaction.

VIM070500-05-IGD-EN-2
2. To refresh the runtime buffer, click the Start Synchronization button.
3.2.4 Configuring object services

Note: The new table entries should have been installed by the package. To
check the settings, use Step 1 to Step 4 of the following procedure. You must
link the new services to WF_START (Step 5).
The VIM dashboard and the OpenText Document Processing document services are
accessible from the SAP Invoice function.
To activate the object services:
1. Run the SM30 transaction.
2. Enter SGOSATTR in the Table/View field and click the Maintain button.

VIM070500-05-IGD-EN-2
3. When a popup is displayed, indicating that the table is cross client, click the
button.
4. Check whether the entries for the services WF_ZOPT/VIM and ZOPT_SERVC are
present.
If the entries are not present, add these entries, as shown in the screenshots
below.

VIM070500-05-IGD-EN-2
5. Double-click WF_START. Enter WF_ZOPT/VIM in Next service and save.

If you are prompted to create a new transport, continue with the next step.
6. Follow your standard change request process for tracking changes.
3.2.5 Maintaining number ranges

You have to maintain number ranges for the following objects:
Object Description
/PTGWFI/RI CP Document
/OPT/DOCID Document Processing
/ORS/STACK Invoice Approval
/ORS/USRMP Invoice Approval Usermap
/OPT/REGID Incoming Document Handling (IDH) framework
Important
All the number ranges intervals must be 01.
To maintain the number range:
1. Run the SNRO transaction.

VIM070500-05-IGD-EN-2
2. Enter the object name from the table above, for example /OPT/DOCID and click
the Number ranges button.
3. Click the button.

VIM070500-05-IGD-EN-2
4. Click the button to add a new number range.
5. Enter required value and save it.

VIM070500-05-IGD-EN-2
3.2.6 Linking events for VIM workflows

Note: The entries should have been installed by the activation of the BC sets.
But you have to activate the linkages and switch on the event queue. If an entry
is missing, add the entry.
SAP events are trigger points for VIM workflows. For example, when a logistic
invoice is posted, SAP ERP generates the event POSTED from the business object
BUS2081. The event is linked to trigger the VIM workflow solution for blocked
invoices if the invoice is blocked.
Event linkages are not activated automatically. You must add the event linkages
manually.
Note: OpenText advises against parking documents outside of VIM and

strongly recommends parking documents through the DP workflow. If parking
is done outside the DP workflow, then sometimes, due to system limitations,
parking events are not raised properly. In this case, parked documents do not
show up in the VAN report. To prevent this issue (if it occurs), OpenText
recommends queuing the parking events.
In case of not properly raised parking events, perform the following actions:
1. To queue parking events, run the SWE2 transaction.

Select the check box Enable event queue for the events /OPT/B2081 -
ZWFI_PARKED and /OPT/FIPP - ZWFI_CREATED and save the configuration.
2. To schedule the Event Queue Job, run the SWEQADM transaction. You can
set the frequency according to your requirement how often to update the
respective data.
The following event linkages can be turned on or off to enable or disable VIM
workflows:
Table 3-2: Event linkages for VIM workflows
Object type Event Receiver function module Usage

comments
Receiver type Check function module
FIPP DELETED SWW_WI_CREATE_VIA_EVENT Invoice
Approval (IAP)
TS00275270 —
FIPP POSTED SWW_WI_CREATE_VIA_EVENT IAP
TS00275270 —
BUS2081 DELETED SWW_WI_CREATE_VIA_EVENT IAP
TS00275270 —

VIM070500-05-IGD-EN-2
Object type Event Receiver function module Usage

comments
Receiver type Check function module
BUS2081 POSTED SWW_WI_CREATE_VIA_EVENT IAP
TS00275270 —
BUS2081 POSTED /OPT/BL_PO_BLK_RECEIVER Invoice
Exception (IE)
TS00275264 /OPT/BL_PO_CHECK_ROLL_OUT Posted
Approval
/OPT/FIPP ZWFI_CREATE /OPT/BL_NPO_PRK_RECEIVER IE
D
/PTGWFI/PIR_F_CHECKFM
WS00275254
/OPT/B2081 ZWFI_PARKED /OPT/BL_PO_PRK_RECEIVER IE
WS00275260 /PTGWFI/PRK_M_CHECKFM
FIPP DELETED /OPT/VIM_RPT_RECEIVER_FM VIM Analytics
(VAN)
— —
FIPP POSTED /OPT/VIM_RPT_RECEIVER_FM VAN
— —
BUS2081 DELETED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
BUS2081 POSTED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— — May be used in
special
situation.
Should be
inactive in
standard
configuration.
BUS2081 RELEASED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
BUS2081 CANCELLED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
/ORS/INVAP POSTED /OPT/AAFS_POST_RECEIVER Posted
Approval
— —
Note: There is a dependency between two entries for Object Type BUS2081 and
Event POSTED, the one with Receiver Type TS00275264, and the one with an
empty Receiver Type.

VIM070500-05-IGD-EN-2
In transaction SWETYPV, make sure that only one of these event linkages is
activated.
• If you use your own blocking workflow, activate only the event linkage with
empty Receiver Type. This event linkage ensures that VAN will be correctly
updated.
• If you use the standard blocking workflow template, activate only the event
linkage with Receiver Type TS00275264. This event linkage updates VAN
with the same function module as the other event linkage but it also starts
the blocking workflow.
One of the two event linkages must be activated.
To enable and disable VIM workflows:
1. To open the Event Type Linkages screen, run the SWE2 transaction.
2. Create the event linkage entries shown in “Event linkages for VIM workflows”
on page 30 (if not already existing) by clicking the New Entries button.
To edit an existing event linkage entry, double-click the entry.
3. To enable the workflow, select the Type linkage active check box.
To disable the workflow, clear the check box.
4. Save your changes with a transport and move this transport to subsequent
systems.
Note: Repeat the procedure for all event linkage entries shown in “Event
linkages for VIM workflows” on page 30.
3.2.7 Maintaining the SAPscript form for approval

The SAPscript form is client-dependent. You must copy it from client 000 to all
required clients. Perform the following steps to do a client copy of the standard
SAPscript form SYSTEM to the form /ORS/SAPSCRIPT, which is used in VIM
approval.
To maintain the SAPscript form:
1. Make sure that namespace /ORS/ is modifiable.

Therefore, run the SE03 transaction, and, under Administration, run Set
System Change Option.
The value for namespace /ORS/ must be Modifiable.
2. Run the SE71 transaction.

VIM070500-05-IGD-EN-2
3. On the Utilities menu, click Copy from Client.
4. Enter values in the required fields. In Form Name, enter SYSTEM, and in Target
Form, enter /ORS/SAPSCRIPT.
5. To submit, click .
If you are asked for a package, enter /ORS/000007.

VIM070500-05-IGD-EN-2
3.2.8 Maintaining standard text

The standard text is client dependent and should be copied from client 000 to all
required clients. Perform the following steps to do a client copy of the following
standard text in the required languages.
• /OPT/VIM_RTV_EXAMPLE
• /OPT/VIM_SIGNATURE_RTV
Copying the following texts is only required if the SRM PO functionality is being
implemented in VIM.
• /OPT/VIM_DP_SRM_PRICE_HEADER
• /OPT/VIM_DP_SRM_QTY_FOOTER
• /OPT/VIM_DP_SRM_QTY_HEADER
• /OPT/VIM_DP_SRM_QTY_URL_HEAD
To maintain standard text:
1. Run the SO10 transaction.
2. Navigate to the menu path Utilities > Copy from Client.

VIM070500-05-IGD-EN-2
Note: To copy the text in all languages at once, you can use an asterisk in
the Language field.
3. Enter values in the required fields. Text Name and Target Name must be the
same.
Click .
4. If a dialog box like the following opens, click Yes.
5. Click the Back button on the confirmation page.
6. Repeat the steps for all standard text shown in the list above.

VIM070500-05-IGD-EN-2
3.2.9 Setting background user parameters for Non PO invoice

posting
If Non PO invoices are posted in background with an alternative BDC ID 41, it is
necessary to adjust user parameters for the background posting user, typically WF-
BATCH.
To set background user parameters for Non PO invoice posting:
1. Run the SU01 transaction and open the user WF-BATCH in edit mode.
2. Enter the following parameter:
Parameter ID Parameter value

FO3 2
Note: Use O like Oscar in FO3. Note that there is a blank in front of the
parameter value 2. The 2 is the second character.
3.2.10 Configuring additional settings

This section lists topics that are important for post installation actions and that are
already described in other guides.
• Regarding online posting using the MIRO transaction and Enhancement Points
(for SAP ERP 6.0 version), see section 9.11.3 “Enhancing MIRO for pre-
population of data during online invoice creation” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
• Regarding the configuration of BAdIs for invoice processing, see section 9.8.1
“Activating BAdI for invoice processing” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide (VIM-CGD).

VIM070500-05-IGD-EN-2
3.3. Language packs
Use transaction SE19 to check the runtime behavior of the BAdIs. The following
are the standard values:
BAdI Implementation Runtime behavior

/OPT/VIM_MIGO_ENH /OPT/VIM_CHECK_MIGO Implementation is called
/OPT/VIM_MIRO_ENH /OPT/VIM_CHECK_MIRO Implementation is called
/OPT/ /OPT/ Implementation is not
VIM_ENH_SPOT_MIRO CL_IM_VIM_BADI_MIRO called
3.2.11 Installing transport with layout variants

The layouts provided in the baseline for the IDH Admin Tool and the new VIM
Analytics program are stored in the LTDX table.
Due to limitations of BC set technology, the entries are not correctly entered in the
table when the BC sets are activated. Therefore copy the transport EW3K900402 into
the transport directory and install the transport using STMS. You must install the
transport to every client because the transport contains client specific data.
You find this transport on your installation CD.
Note: This transport with layout variants may come in a new version with a
Support Package (SP). Therefore, check the Release Notes of the latest SP that
you want to install, and use the transport which is contained in the SP instead
of the transport from the installation CD.
OpenText recommends setting the layout /IDH as default layout for the IDH Admin
Tool (transaction /OPT/VIM_7AX8; report /OPT/VIM_ICC_ADMIN_TOOL).
3.3 Language packs

Languages for VIM (except for English) are delivered in a cumulative language
pack, which you can obtain on OpenText My Support: https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605. For the Business
Center integration into VIM, additional language packs are available.
3.3.1 VIM language packs

Cumulative VIM provides a cumulative language pack with every SP. You can obtain the
language pack cumulative language pack on My Support in the folder of the respective SP.
You can import the cumulative language pack after the respective SP is installed. To
import the language pack, use the SMLT transaction. You can import the language
pack multiple times for several languages.
Translation VIM provides a translation guide that describes the various aspects of translating
Guide VIM into new languages. In addition, the translation guide contains a section
explaining what to do if you want to use the available SAP tools “Secondary

VIM070500-05-IGD-EN-2
Language” and “Language Supplementation” instead of translating into a new

language. The translation guide is available on My Support: https://
knowledge.opentext.com/knowledge/llisapi.dll/Properties/46423475
3.3.2 Business Center integration into VIM: language packs

Business Center components can be deployed together with VIM. In this case, you
must install the corresponding language packs of the Business Center components
together with the language pack of VIM. This applies to the following language
packs:
• Language Pack of Business Center Foundation OTBCFND
• Language Pack of Business Center Inbound OTBCINB
• Language Pack of Business Center VIM Base OTBCSL30 (VIM 7.5 SP4: OTBCSL03)
You find the first two language packs in the Business Center folder on My Support:
https://knowledge.opentext.com/knowledge/cs.dll/Open/62972488
The third language pack is available in the VIM folder on My Support:
VIM 7.5 SP4 language pack for OTBCSL03: https://knowledge.opentext.com/

knowledge/cs.dll/Open/62825607
VIM 7.5 SP5 language pack for OTBCSL30: https://knowledge.opentext.com/

knowledge/cs.dll/Open/65221794

VIM070500-05-IGD-EN-2
Chapter 4
Verifying installation
Make sure that the OpenText Vendor Invoice Management add-on is reflected in the
installed components.
To verify the installation:
1. From the SAP menu, open System > Status.
2. Click the button next to Component version.

VIM070500-05-IGD-EN-2
Chapter 4 Verifying installation
In the System: Component information dialog, you should see the OTEXVIM
add-on component installed, with Release number 750.

VIM070500-05-IGD-EN-2
Chapter 5
Installing Single Click Entry for SAP GUI
VIM 7.5 introduces the Single Click Entry feature in the DP Dashboard. The Single
Click Entry feature allows users to easily capture index data by clicking the
appropriate field zone of the invoice that is displayed in the Detail pane of the DP
Dashboard. For more information, see section 4.2 “Using the Single Click Entry
feature” in OpenText Vendor Invoice Management for SAP Solutions - User Guide (VIM-
UGD).
Notes
• Single Click Entry is an optional feature. If it is not installed, the
functionality is just not available in the DP Dashboard.
• Single Click Entry only supports SAP GUI for Windows, no other SAP GUIs.
• To use Single Click Entry, an installation of OpenText Invoice Capture
Center (ICC) is mandatory. Single Click Entry only works if the DP process
has been started using ICC.
You download the software for Single Click Entry from My Support, the folder for
OpenText™ Invoice Capture Center for SAP® Solutions: https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/15664414. Open the folder of
the appropriate version, 7.5 or higher.
The installation of Single Click Entry is described in Invoice Capture Center

Administrator's Guide, chapter “3 Installing Single Click Entry for SAPGUI (ICC)”.
You find the Invoice Capture Center documentation on My Support: https://
knowledge.opentext.com/knowledge/cs.dll/Open/15448194. Open the folder of the
appropriate version, 7.5 or higher.

VIM070500-05-IGD-EN-2
Chapter 6
Installing a VIM Support Package
This chapter describes the installation of a Support Package (SP) for VIM.
6.1 SAP ERP prerequisites

Make sure that you already have installed the latest VIM SP. Any repairs made to
the VIM objects will be overwritten by the new SP.
To check the SAP ERP prerequisites:
2. Click the button next to Component version.

In the System: Component information dialog box, you should see the
OTEXVIM add-on component installed, with Release number xxx_yyy where
xxx is the VIM version (for example 600) and yyy is the SAP basis component
version.

VIM070500-05-IGD-EN-2
Chapter 6 Installing a VIM Support Package
6.2 Handling workflow container inconsistencies

In certain cases, workflow containers of open VIM workflows may get inconsistent
as a result of an SP installation. This can happen when a new field is introduced into
one of VIM data structures and, by some reason, it must be introduced not at the end
of the structure but in the middle. OpenText tries to avoid such changes, but
sometimes they cannot be avoided.
Note: If possible, finish the processing of all currently open DP documents

before the SP installation. Do not create new DP documents during the SP
installation procedure.
Inconsistent data in workflow containers often results in short dumps. They happen
when, after an SP installation, a user tries to open a work item that was created
before the SP installation.
To solve the problem, the workflow containers can be processed by a special

program provided by SAP in OSS note 910573. The program requires that a new
table is created with the same structure as the table changed in the SP installation
process, in the version that existed in the system before the SP installation. You can
normally find the old version using ABAP dictionary version management.
However, to simplify the solution of potential problems, OpenText recommends that
you create that copy before the SP installation is started.
The only VIM database table that is currently known to cause these problems is
table /OPT/VIM_1HEAD. OpenText recommends that you create a copy (for example
with the name ZZZ1HEAD) in transaction SE11. It is important that the table copy will
not reference any include or append structures. You can achieve this by performing
the following steps:
To expand includes:
1. Copy the table /OPT/VIM_1HEAD.
2. Without activating the copy, open it in change mode.
3. Set the pointer on each include line (.INCLUDE) that is still displayed, and, on
the Edit menu, click Include > Copy Components.
Normally, all fields will be expanded at once. After this, you can activate the
table.

VIM070500-05-IGD-EN-2
6.3. SAP installation
6.3 SAP installation

1. Determine which VIM SP file is needed based upon your SAP version. For more
information, see the Release Notes for the SP.
2. Log on to the SAP server and copy the corresponding file to the following
location on the server: \usr\sap\trans\EPS\in.
3. Open the SAP GUI and access client 000 as the DDIC user.
4. Run the /nSPAM transaction.
5. In the Support Package Manager window, click Support Package > Load
Packages > From Application Server.
6. You are asked to confirm if you want to upload the OCS Package for the VIM
SP. Click Yes.
The package is uploaded into the system, and a confirmation screen is

displayed.

VIM070500-05-IGD-EN-2
7. Click the back arrow button to return to the previous screen.
8. To define the SPAM Queue, click the Display/define button.
The Component Selection window opens.

9. Scroll down until you find the OTEXVIM component and click this line.
A dialog box opens, with the OTEXVIM Patch highlighted.
10. Click the checkmark button to confirm the queue selection. The Release may be
different in your SAP implementation.
You now see the package name in the queue. The Status is yellow and reads
Next action: Import queue.
11. In the Extras menu, click Settings.

VIM070500-05-IGD-EN-2
The SPAM: Settings screen opens.
12. Click the Always radio button in the section ABAP/Screen Generation. Then
click the confirmation checkmark.
13. In the Extras menu, click Ignore generation errors.
Note: This step is Support Package specific. Perform it if it is mentioned in

the Release Notes of the Support Package.
The Support Package may contain Data Dictionary changes that require
database table conversions or other additional activities. Without performing

VIM070500-05-IGD-EN-2
these additional activities, the generation will result in errors that must be
ignored first.
14. You are now ready to import. Click the Import Truck button to begin.
The Import Queue confirmation is displayed.
15. At this point, you can choose the Start Options, which control whether each
phase executes in a dialog process or a background process. Make your
selections and start by clicking the confirmation checkmark button.
The import starts running. If you chose to run in dialog, you see the process
steps running at the bottom of the screen. Otherwise you need to monitor the
log.
When the import has completed, you see a message Queue <queue name>
imported successfully (SAP ERP 6.0) in the dialog box.
16. Click the Checkmark button.
17. Now check the import logs for errors, code 8 or above. To display the logs, click
the Import Log button.
18. Verify that you do not have any error codes eight (8) or above. Warning codes
of four (4) are acceptable.
Note: Some objects can display generation errors. For a list of these
objects, see the Release Notes for the SP.
19. When you have finished viewing, click the Back button.
20. To resolve the domain and tables generation errors (see Step 13 on page 47), the
table data must be converted with the SAP Database Utility (transaction SE14).
Open this transaction in a new window and perform the conversion for each of
the tables listed in the Release Notes for the SP.

VIM070500-05-IGD-EN-2
21. Click Edit.
22. Select Background and Save data, and click Activate and adjust database. You
can set the parameters of the proposed background job to immediate execution.

VIM070500-05-IGD-EN-2
As soon as the jobs created this way for all tables are finished, activate the
domain /OPT/VIM_TAXRATE in the SE11 transaction. There should be no errors
in the activation log.
Note: You must perform the database adjustment in each of the systems
where the SP is installed or transported, including the production system.
23. Return back to the SPAM transaction screen.

Now you can confirm the queue to complete the task.
24. To confirm the queue, click the checkmark icon in the application toolbar.
The SPAM status changes to a green light and the queue is cleared. The
following message will appear: You have applied OTEXVIM <patch number>
successfully.

VIM070500-05-IGD-EN-2
6.4. Post installation activities after installing a new SP
6.4 Post installation activities after installing a new

SP
Restart ICC/ After you have installed a new VIM SP and (if applicable) a new Business Center SP,
BCC server you must restart your ICC/BCC server.
The load manager and the hotspots of the ICC/BCC server will continue to use the
old data definitions. This may lead to inconsistencies if you do not restart the server.

VIM070500-05-IGD-EN-2
Chapter 7
Upgrading
This chapter describes the upgrade procedure for both SAP ERP upgrade and VIM
upgrade.
Notes
• Upgrading is not yet supported for SAP S/4HANA on Premise. Therefore,
this chapter is not applicable for SAP S/4HANA on Premise.
• Terminology
Former versions of SAP (4.6C and 4.7) are no SAP ERP versions, but SAP R/3
versions. Therefore, the wording in many locations would have to be “SAP
ERP or R/3” instead of “SAP ERP”. To make reading more convenient in this
chapter, also the R/3 versions (4.6C and 4.7) are called “SAP ERP”.
7.1 Upgrade overview

An upgrade from VIM versions since 5.1.6 to VIM 7.5 is possible directly or in two
steps using a VIM 6.0 version as intermediate version.
The following tables show the details.
Table 7-1: VIM upgrades for SAP version ERP 6.0
VIM source version Recommended Upgrade Guide

start level
VIM 5.1.6 installed, but Installation Guide VIM 7.5, “Upgrading
not productive (or data to VIM” on page 60.
be discarded) You must use the upgrade package, and
you must follow the post installation
activities for installation.
VIM 5.2 VIM 5.2 SP6 Installation Guide VIM 7.5, “Upgrading
VIM” on page 60
VIM” on page 60
VIM” on page 60

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
Table 7-2: Exchange upgrades for other SAP versions
Source version Recommended Upgrade Guide

start level
VIM 6.0 / 4.6C VIM 6.0 SP1 Installation Guide VIM 7.5, “Upgrading
SAP ERP” on page 56
VIM 6.0 / 4.7 VIM 6.0 SP1 Installation Guide VIM 7.5, “Upgrading
VIM 6.0 / ERP 5.0 VIM 6.0 SP1 Installation Guide VIM 7.5, “Upgrading
VIM 5.2 / ERP 5.0 VIM 5.2 SP6 Installation Guide VIM 7.5, “Upgrading
The following 2-step upgrades have a VIM upgrade to VIM 6.0 SP1 as a first step.
Perform this intermediate step completely. Activate all BC sets mentioned in the
Upgrade Guide and execute all the conversion and migration tools according to the
Upgrade Guide.
Table 7-3: VIM upgrades in 2 steps for SAP version ERP 6.0
Source version Intermediate step Upgrade Guide

VIM 5.1.6 productive Upgrade to VIM 6.0 SP1 VIM Upgrade Guide 5.1.6 to 6.0
(https://knowledge.opentext.com/
knowledge/cs.dll/properties/
21388817)
Second step: Installation Guide VIM 7.5,
VIM upgrade from 6.0 SP1 “Upgrading VIM” on page 60
to 7.5
Table 7-4: Exchange upgrades in 2 steps for other SAP versions

VIM 5.1.6 / 4.6C Upgrade to VIM 6.0 SP1 VIM Upgrade Guide 5.1.6 to 6.0
21388817)
VIM 5.1.6 / 4.7 Upgrade to VIM 6.0 SP1 VIM Upgrade Guide 5.1.6 to 6.0
21388817)
VIM 5.1.6 / ERP 5.0 Upgrade to VIM 6.0 SP1 VIM Upgrade Guide 5.1.6 to 6.0
21388817)

VIM070500-05-IGD-EN-2
7.2. Handling workflow container inconsistencies

VIM 5.2 / 4.6C Upgrade to VIM 6.0 SP1 VIM 6.0 SP1 Release Notes (https://
knowledge.opentext.com/
19224213)
VIM 5.2 / 4.7 Upgrade to VIM 6.0 SP1 VIM 6.0 SP1 Release Notes (https://
knowledge.opentext.com/
19224213)
Second step in all cases: Installation Guide VIM 7.5,
Exchange upgrade from “Upgrading SAP ERP”
VIM 6.0 SP1 on page 56
Table 7-5: SAP S/4HANA conversion

VIM 7.0 / VIM 7.5 VIM 7.5 SP5 or later Installation Guide VIM 7.5, “SAP S/
4HANA conversion ” on page 66
7.2 Handling workflow container inconsistencies

In certain cases, workflow containers of open VIM workflows may get inconsistent
as a result of an upgrade. This can happen when a new field is introduced into one
of VIM data structures and, by some reason, it must be introduced not at the end of
the structure but in the middle. OpenText tries to avoid such changes, but
sometimes they cannot be avoided.
Notes
• If possible, finish the processing of all currently open DP documents before
upgrading the production system. Do not create new DP documents during
the upgrade procedure.
• For more information about upgrading, see the VIM 7.5 Upgrade Guide,
available on My Support: https://knowledge.opentext.com/knowledge/
llisapi.dll/Properties/61798981
Inconsistent data in workflow containers often results in short dumps. They happen
when, after an upgrade, a user tries to open a work item that was created before the
upgrade.
To solve the problem, the workflow containers can be processed by a special

program provided by SAP in OSS note 910573. The program requires that a new
table is created with the same structure as the table changed in the upgrade process,
in the version that existed in the system before the upgrade. You can normally find
the old version using ABAP dictionary version management. However, to simplify
the solution of potential problems, OpenText recommends that you create that copy
before the upgrade is started.

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
The only VIM database table that is currently known to cause these problems is
table /OPT/VIM_1HEAD. OpenText recommends that you create a copy (for example
with the name ZZZ1HEAD) in transaction SE11. It is important that the table copy will
not reference any include or append structures. You can achieve this by performing
the following steps:
To expand includes:
1. Copy the table /OPT/VIM_1HEAD.
2. Without activating the copy, open it in change mode.
3. Set the pointer on each include line (.INCLUDE) that is still displayed, and, on
the Edit menu, click Include > Copy Components.
Normally, all fields will be expanded at once. After this, you can activate the
table.
7.3 Upgrading SAP ERP

This section discusses the process to perform during an SAP ERP upgrade with
regards to VIM.
Notes
• This section is about changing the SAP version from 4.6C, 4.7, or ERP 5.0 to
ERP 6.0. It is not about going to a higher EHP level within ERP 6.0.
• Do not use the “Keep files” option when you are upgrading your SAP
version from 4.7 or ERP 5.0 to ERP 6.0. Even if this is technically possible,
you will end up in a constellation where no further VIM upgrade is possible
without an ACP file.
When you have to upgrade your SAP ERP system and you already installed VIM
using packages, you have to use the specific VIM SAP ERP upgrade packages.
When you upgrade an SAP release to a higher release, the system automatically
recognizes that an SAP add-on is installed and requests the respective upgrade
package. This way the standard SAP ERP upgrade procedure also updates the VIM
add-ons to the relevant version.
Password The OpenText Vendor Invoice Management package is protected with a specific
control password. During upgrade, this password is requested by the SAP Add-On
Installation Tool (SAINT). For the SAP ERP upgrade password, see “Password
control” on page 16.
Prerequisites
• Make sure the profile parameter transport/systemtype is set to CUSTOMER, not
to SAP. If it is set to SAP, you will get object generation errors.

VIM070500-05-IGD-EN-2
7.3. Upgrading SAP ERP
• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s AS

ABAP
• The following components must be installed for SAP ERP 6.0 up to EHP8:

1 700 0013 SAPKB70013
2 701 0003 SAPKB70103
3 702 0003 SAPKB70203
4 higher -
• One of the following add-on components must be installed:
• OTEXVIM 520_640
• OTEXVIM 603_640
• OTEXVIM 602_620
• OTEXVIM 601_46C
To prepare the SAP ERP upgrade:
1. Inform all users about the scheduled downtime as early as possible.
2. Before you begin the upgrade, it is recommended to perform a complete backup

or to take a snapshot of the SAP ERP system.
3. Save values from PO number lists and delivery note (DN) number lists in
your /OPT/VIM_1HEAD table.
If you want to keep the values for these fields, where the PO numbers and DN
numbers for a DP document were stored as a comma-separated list, you have to
use a migration program. The migration program is part of VIM 6.0 SP6 and
VIM 5.2 SP11.
If you are on a lower version, you have to install transport D89K904627 (for SAP
4.6C: D81K903267). You find this transport on your installation CD.
Then run report /OPT/VIM_MIGRATE_PO_DN_LISTS to store PO_LIST and
DN_LIST values in the new table /OPT/VIM_1PO_DN.
You get a log with the count of resulting entries in the table /OPT/VIM_1PO_DN.
To perform the SAP ERP upgrade:
application server in the \usr\sap\trans folder. This is the parent folder of the
DIR_EPS_ROOT folder.

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
Upgrade to SAP File Source path Target path

ERP 6.0 from SAP
version
SAP ECC 5.0 OTEXVIM_EXCH UPGR_ERP/DATA/ \usr\sap\trans
SAP R/3 4.7 _750_700.SAR \EPS
SAP R/3 4.6C

The resulting PAT file is extracted to the EPS\in folder relative to the path of the
SAPCAR file.
3. Follow the standard SAP ERP system upgrade instructions.

During the prepare phase of the SAP ERP upgrade, the Upgrade Assistant
shows you the existing VIM component that is installed.
4. Select the OTEXVIM component and other components if required.
Click the OK button to continue.
5. To include the OTEXVIM exchange package, select Upgrade with SAINT package.

VIM070500-05-IGD-EN-2
7.3. Upgrading SAP ERP
Click the OK button to continue.

6. In the following screen, click the OK button to continue.
7. Continue with the SAP ERP upgrade process.
Important
In case of an SAP ERP upgrade, do not activate BC Sets, as described in
“Activating Business Configuration Sets” on page 20. If you activate BC
Sets, all the configuration data is overwritten with OpenText baseline
configuration data and all custom configuration changes are lost.
At the end of the upgrade you may see the following screen.
When checking the LONGPOST.LOG, you may discover the following error
referencing the VIM namespace.
A2PESEEF_BADI 103 BAdI implementation "/OPT/VIM_CHECK_MIRO" must still be migrated
2 EPU139 Postprocessing necessary when upgrade has been completed"SEEF_BADI""103"
A2WESEEF_BADI 051 Migrate implementation "/OPT/VIM_CHECK_MIRO" using transaction SPAU
Execute the upgrade report "COM_PRODUCT_UPGRADE"
In transaction SPAU, you may see the /OPT/VIM_CHECK_MIGO Business Add-Ins

referenced for the VIM namespace.

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
If the two objects are green (see screenshot above), they are active and
generated. This is okay and can be ignored.
Run the COM_PRODUCT_UPGRADE report using transaction SE38. This report is
outlined in the “SAP ERP Central Component 6.0 SR3 ABAP Upgrade Guide”
section for Follow-up Activities, 6.22 Executing Conversion Programs for the
Product Master, p. 154.
If you have errors running this program, refer to SAP notes 970046 and 1055794.
To finish the SAP ERP upgrade:
1. After the upgrade, perform the installation verifying activities, as described in

“Verifying installation“ on page 39.
2. Test the entire VIM process like for a new VIM installation.
7.4 Upgrading VIM

This section discusses the process to perform an upgrade from VIM 5.2, VIM 6.0, or
VIM 7.0 to VIM 7.5.
Password The OpenText Vendor Invoice Management package is protected with a specific
control password. During VIM upgrade, this password is requested by the SAP Add-On
Installation Tool (SAINT). For passwords for a VIM upgrade, see “Password
control” on page 16.
Prerequisites
General prerequisites
• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s
AS ABAP
• Apply OSS note 1462364: Dependent structure has inconsistent runtime
object after mass activation. This is specific to SAP ERP 6.0 system, up to
EHP5.
• For a list of available software components, check OSS note 2068615: SAP
Invoice Management by OpenText 7.5
• The following components must be installed:

VIM070500-05-IGD-EN-2
7.4. Upgrading VIM
SAP ERP 6.0
Component SAP_BASIS
Level: 700
• The following components must be installed for SAP ERP 6.0 up to EHP8:

1 700 0013 SAPKB70013
2 701 0003 SAPKB70103
3 702 0003 SAPKB70203
4 higher -
• The following add-on component must be installed:
OTEXVIM 520_700 or OTEXVIM 604_700 or OTEXVIM 700
VIM version
Upgrade to VIM 7.5 is supported with minimal versions of VIM 5.2 SP6 or VIM
6.0 SP1 or VIM 7.0. If you have a lower support package level within VIM 5.2 or
VIM 6.0, you must upgrade to the required SP level first, and activate the BC
sets delivered with the SPs.
Direct upgrade from VIM 5.1.6 is not supported. You can upgrade from VIM
5.1.6 to VIM 6.0 SP1 and then go on to VIM 7.5.
To check the version of VIM, open System > Status from the SAP menu and
check the Component Version.
For more details, see “Verifying installation“ on page 39. The following
screenshots show system component information with the required minimum
SP levels of OTEXVIM.

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
Adjust SAINT tool settings

In the settings of the SAINT tool, make sure that ABAP/Screen Generation is set
to Always.

VIM070500-05-IGD-EN-2
7.4. Upgrading VIM
To prepare the VIM upgrade:
1. Inform all users about the scheduled VIM downtime as early as possible.
Users must not perform any actions on the Accounts Payable module; that
means, the entire VIM processes must not be performed.
2. Before you begin the update, perform a complete backup or take a snapshot of
the SAP ERP system.
3. Make sure the namespaces /OPT/, /ORS/, and /PTGWFI/ are modifiable:
a. Run the SE06 transaction.

b. Click System change option in the application tool bar.
c. In the Namespace/Name Range list, change the namespaces /OPT/, /ORS/,

and /PTGWFI/ to Modifiable and save.
4. This step is not relevant, if you are upgrading from VIM 7.0 to VIM 7.5.
Save values from PO number lists and delivery note (DN) number lists in
your /OPT/VIM_1HEAD table.
If you want to keep the values for these fields, where the PO numbers and DN
numbers for a DP document were stored as a comma-separated list, you have to
use a migration program. The migration program is part of VIM 6.0 SP6 and
VIM 5.2 SP11.
If you are on a lower version, you have to install transport D89K904627. You
find this transport on your installation CD.
Then run report /OPT/VIM_MIGRATE_PO_DN_LISTS to store PO_LIST and
DN_LIST values in the new table /OPT/VIM_1PO_DN.
You get a log with the count of resulting entries in the table /OPT/VIM_1PO_DN.
To perform the VIM upgrade:
When you have to upgrade VIM and you already installed VIM using packages, you
have to use the specific VIM upgrade packages.
application server in the \usr\sap\trans folder. This is the parent folder of the
DIR_EPS_ROOT folder.

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
SAP ERP system File Source path Target path

SAP ERP 6.0 OTEXVIM_UPGR UPGR_VIM/DATA/ \usr\sap\trans\
_750_700.SAR EPS

SAPCAR file.
3. Carry out the import of the package as described in the respective SAP
documentation.
4. Continue the Add On process by selecting Add On OTEXVIM.
Click the Continue button.
5. When the Add Modification Adjustment Transports to the Queue message is

displayed, click the No button to continue.
6. When you are prompted for the password, enter the password as provided in
“Password control” on page 16.

VIM070500-05-IGD-EN-2
7.4. Upgrading VIM
7. Make sure that Start options is set to Start in dialog immediately for
Preparation and Continue in Dialog immediately for Import 1, Import 2,
and Clean Up.
A message is displayed, confirming the successful import.
8. Check in the SAINT tool if the package has been imported successfully with the
new release number. See “Verifying installation“ on page 39 for specific release
number.
To finish the VIM upgrade:
1. If you need login languages other than English, install the language packs for
the languages you need. For more information, see “Language packs”
on page 37.
2. Install the most recent VIM 7.5 Support Package (SP). You find the SPs on My
Support: https://knowledge.opentext.com/knowledge/cs.dll/Open/10151605. For
further information, see the Release Notes of the respective SP.
3. After the upgrade, perform/verify all the post installation activities as described
in “Post installation activities after an upgrade” on page 67.
Important
Do not activate the BC Sets for first installation, as described in
“Activating Business Configuration Sets” on page 20. If you activate
these BC Sets, all the configuration data is overwritten with OpenText
baseline configuration data and all custom configuration changes are
lost.
4. Test the entire VIM process like for a new VIM installation.

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
7.5 SAP S/4HANA conversion

This section describes the process to perform during an SAP S/4HANA conversion
with regards to VIM.
Prerequisites
• The target version on SAP side is SAP S/4HANA 1610 on premise.

• The VIM version must be VIM 7.5 SP5 or later.
• For systems with VIM 7.5 SP5, see the following procedure.
To update and activate tables in the system:
1. Run the SE11 transaction to check if tables /OPT/X052, /OPT/Y052, /OPT/

Z052 exist in your system.
These tables are not part of VIM 7.5 but might be in the system from an older
VIM version.
2. If the tables exist, open the table definition, and check the data element for
table field CONFIG_LINE.
3. For each of the tables, change the data element for table field CONFIG_LINE
from VERI_LRAW to /OPT/LRAW2048.
4. Activate the tables.
Table 7-6: Available VIM components
Component for SAP ERP 6.0 Component in SAP S/4HANA on premise

OTEXVIM Can be converted
OTVIMCDS Can be converted
OTVIMARB To be replaced by component with the same name but
different version (750_S4), provided specially for SAP S/
4HANA. Component technical name:
SAPK-754COINOTVIMARB
OTVIMWSR Can be converted
OTVIMWUI Can be converted
OTVIMS4 New component for SAP S/4HANA
OTVIMGW Not available for SAP S/4HANA
OTVIMBW Not available for SAP S/4HANA
OTVIMHNA Obsolete, replaced by OTVIMCDS
The components available for SAP S/4HANA are highlighted in the table.

VIM070500-05-IGD-EN-2
7.6. Post installation activities after an upgrade
Performing the SAP S/4HANA conversion - For the actual SAP S/4HANA
conversion, use the guides provided by SAP, for example http://help.sap.com/
saphelp_nw75/helpdata/en/5c/41b3173c9a4aca8c05392635d622f4/content.htm.
Installing additional VIM components - After your SAP system has been converted
to SAP S/4HANA, you can add the additional components OTVIMS4 and OTVIMARB
(version 750_S4).
For more information, see OpenText Vendor Invoice Management 7.5 S4HANA
Release Notes (https://knowledge.opentext.com/knowledge/cs.dll/link/61907298)
7.6 Post installation activities after an upgrade

To ensure the integrity of the installed transports, you must perform and validate
the following procedures:
• “Activating business configuration sets” on page 67
• “Maintaining number ranges after upgrade” on page 68
• “Checking the BTE handler modules configuration” on page 69
• “Checking status and runtime behavior of BAdIs for Invoice Processing”
on page 70
• “Installing transport with layout variants” on page 70
• “Populating invoice transaction field VORGANG for credit memos” on page 71
• “Removing obsolete user process option 2742” on page 71
• “Copying standard texts for Return to Vendor functionality to client”
on page 71
• “Checking settings for the PDF history log” on page 71
• “Checking settings for approval validation” on page 72
7.6.1 Activating business configuration sets

Notes
• To activate the BC sets, sign in in English and use the expert mode.
• You must activate the BC sets in every client separately.
• Check the tables in /OTEXVIM/VIM75_52_LOW60_D and /OTEXVIM/
VIM75_BASELINE_<xxx> (see the following list) using the Compare button
( ) in the SCPR20 transaction, and decide if it is appropriate to activate this
BC Set. Save and export the log file to a local file. To keep the color
information, use export format Rich text format. Differences between
existing tables and BC sets are marked in yellow. After activating the BC set
you might want to set some customizing entries back to the old values.
The business configuration sets (BC Sets) for post installation activities after an
upgrade are the following:

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
/OTEXVIM/VIM75_52_LOW60_D
Activate this BC Set if your source system for the upgrade is VIM 5.2 or VIM 6.0
SP3 or earlier. If you get an activation error, ignore it.
/OTEXVIM/VIM75_BASELINE_52_60_D
Activate this BC Set if your source system for the upgrade is VIM 5.2 or VIM 6.0.
If you get an activation error, ignore it.
Note: This means, if your source version is VIM 5.2 or VIM 6.0 SP1 or VIM
6.0 SP2 , you have to activate both BC Sets: /OTEXVIM/VIM75_52_LOW60_D
and /OTEXVIM/VIM75_BASELINE_52_60_D.
/OTEXVIM/VIM75_BASELINE_NEWFOR75
Activate this BC Set in any case. You should not have activation errors here. If
you have activation errors, repeat the activation. If you still have activation
errors, you have to find out the reason. You can ignore activation errors like No
data found for writing activation links for object <xxx>.
Notes
• To make it easier to compare the values of the Z-constants, the following
additional BC sets are available:
• /OTEXVIM/VIM75_BASELINE_LCONST
• /OTEXVIM/VIM75_BASELINE_DCONST
• /OTEXVIM/VIM75_BASELINE_NCONST
You can use these BC sets to compare the system settings related to constants
in the LEGACY set (which normally should not be applied in case of upgrade),
in the 52_60_D set (for old versions), and in the NEWFOR75 set.
• OpenText recommends that you run each of these BC sets with compare
option, to get an overview of the constant values, that are going to be
changed when the BC sets are activated. The values in green are added
constants, the values in yellow are changes. Note that you do not need to
activate these BC sets.
7.6.2 Maintaining number ranges after upgrade

Follow the procedures given in “Maintaining number ranges” on page 27 to
configure the number range for the new number range object /OPT/REGID.

VIM070500-05-IGD-EN-2
7.6.3 Checking the BTE handler modules configuration

In VIM 7.5, all BTE handler modules are registered as partner modules. In earlier
VIM version, the modules were registered as customer modules.
Check the following settings:
In the BF32 transaction, the 6 VIM events should be configured; see the following
screenshot.
Check with the BF34 transaction, if these events occur in the customer section. If yes,
remove them.
In the BF42 transaction, the VIM process RWBAPI01 should be configured; see the
following screenshot.
Check with the BF44 transaction, if this process occurs in the customer section. If yes,
remove it.

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
7.6.4 Checking status and runtime behavior of BAdIs for

Invoice Processing
Use transaction SE19 to check the runtime behavior of the BAdIs. The following are
the standard values:
BAdI Implementation Runtime behavior

/OPT/VIM_MIGO_ENH /OPT/VIM_CHECK_MIGO Implementation is called
/OPT/VIM_MIRO_ENH /OPT/VIM_CHECK_MIRO Implementation is called
/OPT/ /OPT/CL_IM_VIM_BADI_MIRO Implementation is not
VIM_ENH_SPOT_MIRO called
To prevent the activation of BAdI /OPT/VIM_ENH_SPOT_MIRO, leave the Planned

Status for Business Function /OPT/VIM_SFW_MIRO empty (in the SFW5 transaction).
7.6.5 Installing transport with layout variants

The layouts provided in the baseline for the IDH Admin Tool and the new VIM
Analytics program are stored in the LTDX table.
Due to limitations of BC set technology, the entries are not correctly entered in the
table when the BC sets are activated. Therefore copy the transport EW3K900402 into
the transport directory and install the transport using STMS. You must install the
transport to every client because the transport contains client specific data.
You find this transport on your installation CD.
Note: This transport with layout variants may come in a new version with a
Support Package (SP). Therefore, check the Release Notes of the latest SP that
you want to install, and use the transport which is contained in the SP instead
of the transport from the installation CD.
OpenText recommends setting the layout /IDH as default layout for the IDH Admin
Tool (transaction /OPT/VIM_7AX8; report /OPT/VIM_ICC_ADMIN_TOOL).

VIM070500-05-IGD-EN-2
7.6.6 Populating invoice transaction field VORGANG for

credit memos
In VIM 7.0, a new field VORGANG was introduced in the /OPT/VIM_1HEAD table. The
new field gives room for the classification of invoice / credit memo / subsequent
debit / subsequent credit, which is used in PO invoices.
After an upgrade from a version older than VIM 7.0, the VORGANG field is empty for
all invoices. To make its value consistent with the CREDIT_MEMO field, run the
program /OPT/VIM_UPDATE_VORGANG_FOR_CM.
The program will set the VORGANG field to 2 for every document in the DP workflow
with CREDIT_MEMO flag selected.
7.6.7 Removing obsolete user process option 2742

In VIM 6.0, process option 2742 was used as a user process option, but it is not
needed anymore. In VIM 7.0, process option 2742 was reused and renamed to IDH
Trigger.
This is not designed as a user process option but it still occurs in some process types
and must be removed.
If you are upgrading from a version older than VIM 7.0, run the program /OPT/
VIM_PURGE_PROCESS_OPTIONS.
7.6.8 Copying standard texts for Return to Vendor

functionality to client
For the Return to Vendor functionality, some standard texts have been introduced.
Copy these texts to the clients as described in “Maintaining standard text”
on page 34.
7.6.9 Checking settings for the PDF history log

The PDF history log is a feature that was not contained in older VIM versions. The
PDF history log is written to an archive in the customer's environment. Thus, it must
be configured as described in section 4.2 “PDF history log scenario” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD). To
avoid warning messages in the application log (SLG1), complete the configuration as
described there.

VIM070500-05-IGD-EN-2
Chapter 7 Upgrading
7.6.10 Checking settings for approval validation

VIM 7.5 introduced a new switch to make the approval validation switchable (see
section 13.10.4.1 “Activating and deactivating approval validation” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD)).
In previous versions, the approval validation was always active. This could cause
issues in some business scenarios. The overall goal of the new constant
SKIP_BAPICHECK is to make the process more simple. Approvals do not need to stop
because of errors generated by those deep checks.
Note: Basic checks like whether a cost center exists are still performed.
After applying the BC sets for VIM 7.5, the setting for approval validation is
“switched off”.
If you want to restore the behavior of the old version, set the Z-constant IAP
SKIP_BAPICHECK to an empty value or remove the Z-constant.

VIM070500-05-IGD-EN-2
Chapter 8
Troubleshooting
8.1 FAQs
The following FAQs cover basic troubleshooting information.
Does VIM consist of any standard SAP objects/repairs?

No
Does VIM consist of any Z objects?

No
How do I check whether installation is successful?

Refer to “Verifying installation“ on page 39.
What is the namespace?

SAP assigns name spaces for its partners; by doing so the changes to these objects
are protected.
Can I repair the OpenText objects?

It is not recommended to repair OpenText objects. Contact
support@opentext.com before making any repairs; OpenText might have
already issued a patch for the intended repair and the same functionality can be
achieved by using appropriate user exits.
There is an error when starting the workflow.

Make sure the standard task is defined as a general task.

VIM070500-05-IGD-EN-2
Part 3
Business Center components installation
Part 3 Business Center components installation
This part describes the installation of Business Center components that are needed
for the Business Center Solution Integration for VIM. The solution integration
comprises the following features:
Business Center Inbound Configuration

Business Center Inbound Configuration is used to handle incoming document
processing in VIM. For more information, see section 8 “Incoming document
processing” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
Note: Business Center Inbound Configuration replaces the Incoming

Document Handling (IDH) framework and the ICC Dispatcher framework
with VIM 7.5 SP3 and later. If you implement VIM new with VIM 7.5 SP3
or later, you must use Business Center Inbound Configuration. When
upgrading to VIM 7.5 SP3 or later, you can use Business Center Inbound
Configuration or ICC Dispatcher and IDH. However, keep in mind that
ICC Dispatcher and IDH will be discontinued in the future.
The following apps are based on SAP Fiori®.
VIM Resolve Invoice Exceptions Fiori app

This app allows users to access VIM exceptions (process steps) in web browsers
or mobile devices, for example an iPad or iPhone.
VIM Enter Cost Assignment Fiori app

This app allows users to handle coding processes for Non-PO based invoices,
using web browsers or mobile devices.
VIM Approve Invoices Fiori app

This app allows users with an SAP account to approve their invoices, using web
browsers or mobile devices.
Notes
• The VIM Fiori apps, which all are using the Business Center Fiori Task App,
are optional components. If you are not using them, skip the respective
sections.
• For information about the configuration of the VIM Fiori apps, see section 14
“Apps based on the Fiori Task App” in OpenText Vendor Invoice Management
• You can download the Business Center components from the Business
Center download section on My Support.

VIM070500-05-IGD-EN-2
Chapter 9
Business Center components and packages
This section lists all components that are needed for the integration of VIM and
Business Center, including those that are used to run VIM Fiori apps. For
information regarding the prerequisites for standard Business Center components,
such as SAP Basis versions, see OpenText Business Center for SAP Solutions -
Installation Guide (BOCP-IGD). The VIM integration components need only standard
Business Center components as prerequisites.
If you intend to use Business Center VIM integration components, make sure to
select and install appropriate Business Center components versions (SPs), based on
“VIM and Business Center compatibilities” on page 77:
Table 9-1: VIM and Business Center compatibilities
VIM target SP level Necessary Business Center component version / SP

level
VIM 7.5 SP2 (7.0 SP6) Business Center 10.0
VIM 7.5 SP3 (7.0 SP7) Business Center 10.0 SP1
VIM 7.5 SP4 (7.0 SP8) Business Center 16 and SP1 of OTBCWUI
VIM 7.5 SP5 (7.0 SP9) Business Center 16 SP1
You can download VIM integration components, whose names begin with OTBCSL
(see the following lists), using the links that are provided in the download area of
the corresponding VIM SP on OpenText My Support. For your convenience, links
for the downloads of the corresponding general Business Center components are
provided at the same location.
SAP Integration
Business Center Foundation

OTBCBAS: Business Center Base 16
OTBCINB: Business Center Inbound 16
OTBCFND: Business Center Foundation 16
Solution Accelerator for Business Center - Base component

OTBCSL00: Business Center Solution Base 16
Solution Integration VIM

OTBCSL30: Business Center VIM Base
OTBCSL03: Business Center VIM Foundation. This includes the integration of the
following components:

VIM070500-05-IGD-EN-2
Chapter 9 Business Center components and packages
• Business Center Inbound Configuration

• VIM Resolve Invoice Exceptions Fiori app
• VIM Enter Cost Assignment Fiori app
• VIM Approve Invoices Fiori app
Fiori Integration
Business Center Foundation

OTBCWUI: Business Center Web UI 16
OTBCWSR: Business Center Web Services 16
Solution Integration VIM

OTBCSL33: Business Center VIM Web Services
OTBCUS03: Business Center VIM Web UI
The following packages and included VIM components are available:
Package Component Release

/OTBCBAS/INST_UPG_0700_003 OTBCBAS 0700_003
/OTBCINB/INST_UPG_0700_003 OTBCINB 0700_003
/OTBCFND/INST_UPG_0700_003 OTBCFND 0700_003
/OTBCWSR/INST_UPG_0740_003 OTBCWSR 0740_003
/OTBCWUI/INST_UPG_0740_003 OTBCWUI 0740_003
/OTBCSL00/INST_UPG_0700_003 OTBCSL00 0700_003
/OTBCUS03/INST_UPG_0740_003 OTBCUS03 0740_003
During the installation process, the following major packages are used:
Component Release SAP OCS OCS Password

Release Filename Package
OTBCSL30 0700_003 700 Q5Y00200734 SAPK-003CO 8B87CC35AF
37_0000021.P INOTBCSL30
AT
OTBCSL03 0700_003 700 Q5Y00200734 SAPK-003CO 8B87CC36AC
37_0000036.P INOTBCSL03
AT
OTBCSL33 0700_003 700 QAL0020073 SAPK-003CO 8B87CC35AC
437_0000023. INOTBCSL33
PAT

VIM070500-05-IGD-EN-2
Component Release SAP OCS OCS Password
Release Filename Package
OTBCUS03 0740_003 740 Q5O00200734 SAPK-003CO 8B81D336AC
37_0000038.P INOTBCUS0
AT 3
This component information relates to the initial installation of the components. It is

delivered with VIM 7.0 SP9 / VIM 7.5 SP5. When installing subsequent SPs of VIM,
you need to install the corresponding SPs of the Business Center VIM solution
components. For detailed information on this, see the Release Notes of the respective
VIM SPs.
Depending on your system landscape, different Business Center components will

not be necessarily installed on the same server. The following diagram provides an
overview on where the specific components must be installed.
Note: “Fiori Server” and “Gateway Frontend Server” mean the same server.
For more information, see section 4 “Setup for the Fiori Task App” in OpenText
Business Center for SAP Solutions - Installation Guide (BOCP-IGD).

VIM070500-05-IGD-EN-2
Chapter 10
Summary of installation steps
This section summarizes the required installation steps and their sequence for
installing Business Center for VIM integration.
Notes
• The installation steps for each component, listed in this section, are related to
the initial installation of components delivered with VIM 7.0 SP8 / VIM 7.5
SP4. When installing components for later VIM SPs, all additional SPs of the
respective Business Center and VIM solution components need to be
installed according to “VIM and Business Center compatibilities” on page 77.
• First you must install VIM with the wanted SP level. After that, you can
install the corresponding Business Center VIM integration
To install Business Center for VIM integration:
1. Install Business Center Foundation:
a. Install the Business Center Base (OTBCBAS), Inbound (OTBCINB), and

Foundation (OTBCFND) add-ons using the SAINT transaction.
b. Install the Support Packages 0001 for Business Center Base (OTBCBAS),
Inbound (OTBCINB) and Foundation (OTBCFND) using the SPAM transaction.
c. Activate Business Center BC sets /OTX/PF00_GENERAL_SET_003_01, /OTX/
PF01_INBOUND_003_01, and /OTX/PF02_FOUNDATION_003_01 using the
SCPR20 transaction.
2. Install the VIM integration:
a. Install the Base for Business Center solution accelerators (OTBCSL00) add-on
using the SAINT transaction.
b. Install the Support Package 0001 for Base for Business Center solution
accelerators (OTBCSL00) using the SPAM transaction.
c. Activate the BC set of the Base for Business Center solution accelerators (/
OTX/PS00_BASE_003_01) using the SCPR20 transaction.
d. Install the VIM Base (OTBCSL30) and after that the VIM Foundation
(OTBCSL03) add-ons using the SAINT transaction.
e. Install the Support Packages 0001 for VIM Base (OTBCSL30) and VIM
Foundation (OTBCSL03) using the SPAM transaction.
f. Mandatory. Do not skip this step.
Activate the BC set of the VIM Foundation (/OTX/PS03_VIM_003_01) using
the SCPR20 transaction.

VIM070500-05-IGD-EN-2
Chapter 10 Summary of installation steps
3. Optional installations but required for the Business Center Fiori Task App
Install Web Services.
a. Install the Business Center Web Services (OTBCWSR) and after that the VIM
Web Services (OTBCSL33) add-ons using the SAINT transaction on the
system where you also installed the Business Center Foundation (OTBCFND)
and the VIM Foundation (OTBCSL03).
b. On the same system, install the Support Packages 0001 for Business Center
Web Services (OTBCWSR) and VIM Web Services (OTBCSL33) using the SPAM
transaction.
c. Install the Business Center Web UI (OTBCWUI) add-on using the SAINT
transaction on the system that you want to use for the Web UI.
d. On the same system, install the Support Packages 0001 and 0002 for the
Business Center Web UI (OTBCWUI) using the SPAM transaction.
e. On the same system, install the VIM Web UI (OTBCUS03) add-on using
the SAINT transaction.
f. On the same system, install the Support Package 0001 for VIM Web UI
(OTBCUS03) using the SPAM transaction.
Important
Installing the Business Center Web Services (OTBCWSR) and VIM Web
Services (OTBCSL33) on a different system than the Business Center
Foundation (OTBCFND) and VIM Foundation (OTBCSL03) is not
supported.
4. Optional installations but required for the Business Center Fiori Task App
Activate OData and UI services.
a. The Fiori Task App communicates with the ABAP backend using a
dedicated OData service (PS33_DATA_SRV). To invoke this service using the
HTTP protocol, activate it first on the Gateway Frontend Server. For more
information, see section 6.3.1 “Enabling OData service” in OpenText
b. Activate the UI service /sap/bc/ui5_ui5/otbcwui/PS30_VIM_UI_02 in

the SICF transaction.
c. Activate the Business Center UI:

To activate the service, run the SICF transaction and activate the /sap/bc/
ui5_ui5/otbcwui/pf07_bc_ui_02 service.
Additionally, for the templates, activate the /sap/bc/ui5_ui5/otbcwui/
pf07_bc_ui_02_t service.
For more information, see section 6.3.2 “Activating the service” in OpenText

VIM070500-05-IGD-EN-2
Part 4
KPI Dashboard installation
Part 4 KPI Dashboard installation
This part describes the installation and post installation activities needed for the
“Key Performance Indicator” Dashboard (KPI Dashboard). The KPI Dashboard is a
tool for managers showing VIM related process data at a glance in graphical charts.
For further information, see section 26 “KPI Dashboard” in OpenText Vendor Invoice
Notes
• The KPI Dashboard is not supported in the VIM 7.5 version for SAP S/
4HANA on Premise.
• The KPI Dashboard is an optional component.
• If you are not using the KPI Dashboard, you can skip this part.

VIM070500-05-IGD-EN-2
Chapter 11
Installing the KPI Dashboard
The KPI Dashboard is installed together with the VIM Basis package.

VIM070500-05-IGD-EN-2
Chapter 12
Post installation activities
The following activities are needed to configure the KPI Dashboard on your system.
12.1 Activating the SAP Web Dynpro service

The settings in this section are necessary to activate the SAP Web Dynpro service.
Prerequisites
There are specific OpenText name spaces that have to be modifiable in order to
change the service settings. So first check with transaction SE03
Navigate to Transport Organizer Tool > Administration > Set System Change
Option
Make sure, the Open Text Name space / Prefix /OPT and /ORS are set to Modifiable.
After you have finished the customizing of services, change back the settings.

VIM070500-05-IGD-EN-2
Chapter 12 Post installation activities
To activate the service:
1. To activate the Web Dynpro service on the SAP ERP system, run the SICF
transaction.
2. In Virtual Host, enter default_host and click Execute.
3. In the tree, select sap > bc > webdynpro.

VIM070500-05-IGD-EN-2
12.1. Activating the SAP Web Dynpro service
4. Highlight vim_kpi_MAIN and, on the menu, click Service/Host > Activate.

5. Highlight vim_kpi_MAIN and double-click to change the service settings.
Continue with “To configure time out settings:“ on page 90.

VIM070500-05-IGD-EN-2
To configure time out settings:
1. Configure the Session Timeout to a reasonable time limit, for example 5

minutes..
If a user has an open KPI Dashboard, does nothing for a couple of minutes and
then tries to change a filter or category, a timeout error occurs. As long as the
time without activity is shorter than the session timeout parameter, no error will
occur.
2. Save the changes and leave the service maintenance.
Error Handling
You can customize a few default pages for error handling in the Web Dynpro
service.
Error pages are shown for defined reasons; for example, if the timeout is reached for
the web session. The default setting is to show SAP standard error pages.
You can change these settings for the following use cases:

VIM070500-05-IGD-EN-2
12.1. Activating the SAP Web Dynpro service
• Logon Errors
• Application Errors
• Logoff Page
• Not Accessible

VIM070500-05-IGD-EN-2
12.2 Setting the connection for the SAP Web Dynpro

service
You activate the SSL connection for Web Dynpro by configuring the SAP Web AS, as
described in the SAP help: http://help.sap.com/saphelp_nw70ehp2/helpdata/en/90/
71d273fa724cc9bb644ab00405e6f8/frameset.htm
Do not change the service settings described in “Activating the SAP Web Dynpro
service” on page 87. Make sure that the SSL settings are not activated in the Logon
Data tab.

VIM070500-05-IGD-EN-2
12.3. Setting up the SAP NetWeaver Portal integration
Change the KPI constant DASHBOARD_START_URL to https://xxxxx:8443/xxxx. See

section 26.4.10.5 “KPI Dashboard start URL” in OpenText Vendor Invoice Management
12.3 Setting up the SAP NetWeaver Portal integration

Use Internet Explorer 8 (or higher) for setting up the SAP NetWeaver® Portal
integration for the KPI Dashboard on NetWeaver 7.0 and login to the SAP
NetWeaver Portal as Administrator.
A System Object is needed to integrate the KPI Dashboard in the SAP NetWeaver
Portal. The System Object is a set of connection properties to represent an external or
SAP system (SAP R3, CRM, BW) used to retrieve data into portal iViews. If not
existing, you must create a System Object in the NetWeaver Portal.
Note: If you use an SAP NetWeaver Portal version higher than 7.0, refer
directly to the SAP Portal documentation: http://help.sap.com/saphelp_nw74/
helpdata/de/4b/8d080d231e2b5fe10000000a42189c/frameset.htm. Follow the
description of creating an iView type based on a Web Dynpro ABAP
application.
12.3.1 Prerequisites
This example shows the customizing for the connection to a specific ABAP® system.
To customize the connection to an ABAP system:
1. In the SAP NetWeaver Portal, navigate to System Administration > System

Configuration > System Landscape > Browse > Portal Content > System
landscape.
2. System Alias settings

In the Display drop down list, select System Aliases. The System Alias Editor
is displayed.
Enter the Alias name: Generally it reads <SID>CLNT<CLIENTNO>; for example:
BI7CLNT100.
Click the Add button and save.
3. Connector settings
In the Display drop down list, select Object, and then, in the Property
Category drop down list, select Connector.
Provide minimum connector properties for example. See the following
screenshot for example values.

VIM070500-05-IGD-EN-2
4. ITS settings
ITS settings are maintained for displaying SAP transactions in the portal as an
iView.
In the Display drop down list, select Object, and then, in the Property
Category drop down list, select Internet Transaction Server (ITS).
Provide ITS properties as shown in the following screenshot.

VIM070500-05-IGD-EN-2
12.3. Setting up the SAP NetWeaver Portal integration
The property values to enter can be read from the ABAP system using
transactions SICF and SMICM.
For a detailed description how to set up the System Object in the Portal, see
http://wiki.sdn.sap.com/wiki/display/EP/How+to+Create+System+Object+in+the
+Portal+for+Connecting+to+SAP+backend+System.
12.3.2 Adding the Portal component

To add the Portal component:
1. In the SAP NetWeaver Portal, navigate to Content Administration > Portal

Content > Browse > Portal-Content.
2. Choose a folder or generate a new folder. To select the iView object, right-click
the folder and select new > iView.
3. In the Display drop down list, select Object, and then, in the Property
Category drop down list, select Content - Web Dynpro.
Provide properties as shown in the following screenshot.

VIM070500-05-IGD-EN-2
Check also other properties for design or layout, and customize them if needed.
4. To test the newly generated iView object, click the Preview button. If everything
is customized correctly, a separate window opens and shows the KPI
Dashboard content in the iView.

VIM070500-05-IGD-EN-2
Part 5
OpenText Approval Portal installation
Part 5 OpenText Approval Portal installation
This part describes the installation of the OpenText Approval Portal component. The
Approval Portal is designed to work within SAP NetWeaver Application Server Java
(NWAS) 7.0, 7.3, or 7.4 or SAP NetWeaver Portal (NWP) 7.0, 7.3, 7.4, or 7.5.
The Approval Portal can be deployed as a standalone application residing on NWAS

only or as an application inside NWP using AppIntegrator iView. Install all the
components in a coordinated manner.
Notes
• The Approval Portal is an optional component.
• If you are not using the Approval Portal, you can skip this part.
• Please refer to section 11 “Administering the Approval Portal” in OpenText
Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-
AGD) for administering and troubleshooting the Approval Portal.
• You might want to install multiple instances of the Approval Portal on the
same SAP NetWeaver Portal. In this case, contact OpenText Customer
Support.

VIM070500-05-IGD-EN-2
Chapter 13
13.1 Installation prerequisites

A complete installation and configuration of OpenText Vendor Invoice Management
is needed for installing and testing the Approval Portal. Although it is possible to
install the Approval Portal before the installation and configuration of the SAP ERP
component, you will not be able to verify if the installation of the Approval Portal is
completed and correct.
Server
Web Application Server

SAP NetWeaver Application Server Java (NWAS) 7.0 SP9 or above with
SPNegoLoginModule and NWAS 7.3 SP3 or above and NWAS 7.4 SP3 or above.
For SPNego configuration, see SAP Note 1488409.
SAP NetWeaver Portal

SAP NetWeaver Portal (NWP) 7.0 SP9 or above and NWP 7.3 SP3 or above and
NWP 7.4 SP3 or above and NWP 7.5.
Notes
• The requirement “SPx or above” does also refer to the EhP level.
• For further information, see the SAP Note: 994791-SPNego Wizard.
Supported The following list shows the supported resolution modes that have been tested in
Screen the OpenText R&D lab. The resolution modes have been tested in all supported
Resolution
browsers.
1. 1280 x 800 - Laptop view
2. 1920 x 1080 - Laptop view
3. 1680 x 1050 - Desktop view
4. 1280 x 1024 - Desktop view
Web browsers The following matrix shows the web browsers and versions that are supported by
the new interface of the Approval Portal, which is delivered since VIM 7.0 SP2. The
matrix is based on tests performed at OpenText R&D Lab. It considers accessibility
and usability aspects.

VIM070500-05-IGD-EN-2
Browser and Version

Server IE9 IE10 IE11 Firefox > Chrome > 22 Safari > 5.0
17
NWAS 7.0
NWAS 7.3
NWAS 7.4
NWP 7.0
NWP 7.3
NWP 7.4
Operating The Approval Portal supports Windows, Unix and other operating systems
systems supported by SAP.
There is no restriction which Windows or Unix versions or patch levels are

supported. Approval Portal supports all versions.
Note: The new Approval Portal has not been tested in Unix environment.
Aligned with SAP operating system support, see the SAP Product Availability
Matrix (PAM) for more details.
SSL OpenText recommends implementing SSL (HTTPS) if security is a concern. Basic

Authentication in SPNego is using Base64 encryption which can be easily decrypted.
See http://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspx for further
information.
Sizing require- Standard sizing requirements for NWAS or NWP 7.0 apply.
ments
SAP user A SAP CPIC user in the SAP ERP server
The communication with the SAP ERP system is accomplished by using a CPIC user
ID. However, the Web user is recorded as the agent who approved an invoice, not
the CPIC user.
User type
Communication Data (CPIC)
Profile
Create a profile with the following authorization objects and add it to the CPIC
user:
Object: S_RFC
Activity
Execute (16)
VIM070500-05-IGD-EN-2
13.1. Installation prerequisites
Names of RFC to be protected

/OPT/VIM_FG1A2, /ORS/*, /OPT/*, /ORS/SAPL000007_APPR_SCREEN, /
PTGWFI/*, OPTB, ARFC, ERFC, RFC1, SDIFRUNTIME, SUNI, SYST, SYSU
RFC_TYPE
FUGR (Function Group)
Object: S_CPIC
Activity
Accept, Initialize (37 and 51)
Name of an ABAP/4 FORM routine
CPIC
Symbolic destination
*
If you wish to narrow this down, examine table TXCOM and choose entry
under the SDEST field that represents the destination of the system you are
communicating with.
Program Names with Search Help
/ORS/*, /OPT/*, /PTGWFI/*
Object: S_DATASET (Authorization for file access)
Activity
Read, Write (33 and 34)
Filename
* (physical file name)
Program Names with Search Help

/ORS/*, /OPT/*, /PTGWFI/*
The following 2 authorization objects for the CPIC user are applicable for SAP
ERP 702 SP14 and higher and SAP NetWeaver Portal 702 SP15 and higher:
Object: S_RZL_ADM (Authorization object for R/3 system administration)
Activity
Display (03)
Object: S_WF_SUBST (Workflow: substitute rule)
Activity
Display (03)
Additional SAP Standard Profile needed: S_A.CPIC and S_A.USER
Note: If you are using an Archive Server to pull in images, you may need
to assign additional roles. See the Archive Server Installation manual.
Example: OpenText™ Archive Center provides the following profiles that need to
be assigned to the CPIC user to access images:
• S_AL_ADMLO (Display SAP ArchiveLink® administrator)
VIM070500-05-IGD-EN-2
• S_AL_ADMDE (Delete ArchiveLink administrator)
Defaults
Decimal notation should be 1,234,567.89.
Note: For SAP ERP systems with EHP5 or higher, one additional authorization
is required for the CPIC user.
S_WF_WI
Classification of tasks
*
Activities
12 (Resubmit work item)
Work item type

W – Dialog work item
13.2 Installation components

Both Software Component Archive (.sca) file and Software Deployment Archive
(.sda) file are supplied; you can choose which format is suitable for your situation.
Each file contains the following:
• SAP NetWeaver Application Server Java components
• Java Enterprise archive (.ear file) - for the actual J2EE application
VIM 7.5 SPx installation package
For all Support Packages of VIM 7.5, the respective OpenText Vendor Invoice
Management 7.5 Support Package folder on My Support (accessible via https://
knowledge.opentext.com/knowledge/cs.dll/Open/10151605) provides an
installation package of the VIM 7.5 SPx Approval Portal in the Web and
Mobile Approval Component folder.
13.3 System architecture

This section explains the overall system architecture of the Approval Portal. There is
one main component of the product:
• Java Application (.ear file) which is the Approval Portal application.
The Software Component Archive (.sca) file or Software Deployment Archive

(.sda) file will be deployed using SAP Software Deployment Manager (SDM).
There are 2 ways to configure the Approval Portal application. It can be deployed:
• as a standalone J2EE application residing on NWAS only utilizing integrated
authentication
VIM070500-05-IGD-EN-2
13.3. System architecture
• as an application inside NWP using AppIntegrator iView
The following diagrams show the architecture for each scenario:
Figure 13-1: Approval Portal architecture with NWAS
The SAP help pages linked in the following discuss some of the communication
channels between each component:
• Simple and Protected GSS API Negotiation Mechanism (SPNEGO) (http://
help.sap.com/saphelp_nw70ehp1/helpdata/en/43/
4bd58c6c5e5f34e10000000a1553f6/frameset.htm)
• Network and Transport Layer Security (http://help.sap.com/saphelp_nw70ehp1/
helpdata/en/3a/7cddde33ff05cae10000000a128c20/frameset.htm)
• SAP Java Connector (JCO) (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/
6f/1bd5c6a85b11d6b28500508b5d5211/content.htm)
VIM070500-05-IGD-EN-2
Figure 13-2: Approval Portal architecture with NWP
Note: Approval Portal can be used if the SAP NetWeaver Portal is configured
to use SAML-based authentication. No specific VIM configuration is required
in this case. For more information on SAML, see the SAP documentation
(http://help.sap.com/saphelp_nwce72/helpdata/en/17/
6d45fc91e84ef1bf0152f2b947dc35/content.htm?frameset=/en/17/
6d45fc91e84ef1bf0152f2b947dc35/frameset.htm&current_toc=/en/45/
b6af743753003ae10000000a11466f/plain.htm&node_id=10&
show_children=true#jump10).
VIM070500-05-IGD-EN-2
13.3. System architecture
13.3.1 SAP user requirements

For the SAP user, the following log in properties are required for the OpenText
Approval Portal:
Standalone J2EE application residing on NWAS only utilizing integrated

authentication
No need for SAP GUI Logon ID. Only network ID is required.
Application inside NWP using AppIntegrator iView

No need for SAP GUI Logon ID. Only Portal ID is required.
Dual Stack installation (SAP ABAP and Java Stack) utilizing integrated
authentication
SAP GUI Logon ID required. Dual Stack forces to use SAP user management
based on ABAP Stack.
Standalone J2EE application residing on NWAS with NWP utilizing integrated

authentication by accessing application directly without iView
No need for SAP GUI Logon ID; only network ID is required.
VIM070500-05-IGD-EN-2
Chapter 14
Installing Web Viewer/Brava! View for the Approval
Portal
To display invoice images, you can integrate OpenText™ Imaging Web Viewer
(Web Viewer) into the Approval Portal. The Approval Portal supports Web Viewer,
version 10.2.0.
Note: OpenText recommends that you use the latest patch of the supported
Web Viewer software version.
As an alternative, you can use OpenText™ Brava!™ View for SAP Solutions (Brava!
View).
• To install Web Viewer 10.2.0, download the software from the following location:
http://knowledge.opentext.com/knowledge/cs.dll/Open/19642255.
• For the Web Viewer installation, see the appropriate section in section 3
“Installing Web Viewer” in OpenText Imaging Web Viewer - Installation and
Configuration Guide (CLWEBV-IGD).
• To install Brava! View, download the software from the following location:
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/62290594.
• For the installation of Brava! View, see section 2 “Installing Brava! View for SAP
Solutions” in OpenText Brava! View for SAP Solutions - Installation and
Configuration Guide (BRWEBV-IGD).
• To apply the latest patch for Web Viewer 10.2.0, download the software from the
following location: https://knowledge.opentext.com/knowledge/cs.dll/Open/
22422170
• It is necessary to install Archiving and Document Access for SAP Solutions 10.0
SP2. For more information, see OpenText Archiving and Document Access for SAP
Solutions - Installation and Upgrade Guide (ER-IGD).
• You perform the configuration that is necessary for the Web Viewer integration
in the /IXOS/OA_CUST_A archive tables in SAP ERP. For a description of the
configuration, see section 20.2 “Configuration for Java Viewer/Web Viewer/
Brava! View” in OpenText Archiving and Document Access for SAP Solutions -
Scenario Guide (ER-CCS).
VIM070500-05-IGD-EN-2
Chapter 15
Installing the Approval Portal
15.1 JCo3 migration considerations

As part of VIM 7.5 SP3, Approval Portal extended the support for SAP Java
Connector 3 (JCo3). You can decide if you want to use the JCo2 or the JCo3
installation package, based on the following considerations:
• JCo3 by framework takes care of Connection Management Handling, and all JCo
destinations are created on SAP NetWeaver Administrator Portal.
• JCo3 destination configuration and pool parameters are maintained at SAP
NetWeaver Administrator Portal. For more information, see section 11.1.2 “SAP
Connection for JCo3” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD).
• A minimal JCo3 destination configuration is maintained on the Approval Portal
Admin Console. For more information, see section 11.1.2 “SAP Connection for
JCo3” in OpenText Vendor Invoice Management for SAP Solutions - Administration
Guide (VIM-AGD).
• The JCo3 package is completely aligned with JCo2 package, having all
functionalities, except connector usage.
• The JCo3 package contains an option of switching JCo2 connector
implementation by applying a CI and necessary configuration. For more
information, see section 11.1 “Configuring the Approval Portal” in OpenText
Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-AGD).
• The JCo3 migration is based on SAP Note 549268.
Choose one of the following Approval Portal packages on My Support:

• JCo2 version package: IM_APPROVAL_PORTAL7_5SP<XX>.zip
• JCo3 version package: IM_APPROVAL_PORTAL7_5SP<XX>_JCo3.zip .
where <XX> refers to the Support Package number.
VIM070500-05-IGD-EN-2
Chapter 15 Installing the Approval Portal
15.2 Preparing the installation

To prepare the installation, perform the following steps:
1. Deploy application specific files to server

To gain access to the file system, sign on to the host server as a user with
administrator rights.
Extract the files from opentext.zip from the delivery to a folder on the server.
Important
OpenText recommends you to create and deploy to the folder usr/sap/
<SID>/SYS/global/opentext/invoiceCfg. This is the default location
for putting the application configuration file. If you deploy to another
location, you will have to manually add a startup parameter in the
Config Tool to tell the application where to look for the configuration
files. This will also require restarting the SAP NetWeaver Application
Server Java (NWAS). See Step 2 on page 111 for details.
<SID> is the system ID of the NWAS. Example: T39.
Example: E:\usr\sap\T39\SYS\global\opentext\invoiceCfg
This folder is referenced as <Approval_Portal_installdir> in the following.

The <Approval_Portal_installdir> folder contains the following files:
configuration.xml
containing all the configuration for the application
Note: Each Approval Portal Support Package (SP) delivers an

configuration.xml file. If you overwrite your existing file, your
settings will be gone. If you keep the old file, you may be missing
some new options introduced for the new SP. See the Release Notes of
the respective SP if the file can be left as it is or if it must be merged to
incorporate the new settings.
mobileconfiguration.xml
containing all the configuration for mobile support
RequestMappings.xml
OpenText strictly recommends not to modify this file. The Approval Portal
application internally uses this file.
Lang_Support.properties
containing all the mapping of languages code; see section 11.4.2
“Configuring additional languages” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD) for details.
Lang_DE.properties
containing all the text for the German language resource
VIM070500-05-IGD-EN-2
15.2. Preparing the installation
Lang_EN.properties
containing all the text for the English language resource
Lang_ES.properties
containing all the text for the Spanish language resource
Lang_FR.properties
containing all the text for the French language resource
Lang_IT.properties
containing all the text for the Italian language resource
Lang_JA.properties
containing all the text for the Japanese language resource
Lang_NL.properties
containing all the text for the Dutch language resource
Lang_PT.properties
containing all the text for the Portuguese language resource
Lang_RU.properties
containing all the text for the Russian language resource
Lang_ZH.properties
containing all the text for the Chinese language resource
There might be more .properties files, depending on the package and the
release for additional languages. The language resource files can be changed.
See section 11.4.1 “Changing language resources” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for details.
Important
Make sure the <Approval_Portal_installdir> folder has:
• correct permissions for the J2EE application to write and read

• Full Control permission to the J2EE Engine service user (or to
Everyone)
2. Optional: Invoke the J2EE Config Tool
Important
This step is only needed if you deploy the configuration files to a
location other than the folder usr/sap/<SID>/SYS/global/opentext/
invoiceCfg.
If you deploy to another location than usr/sap/<SID>/SYS/global/opentext/

invoiceCfg, you must add a startup parameter in the Config Tool, manually, to
tell the application where to look for the configuration files.
You find the Config Tool in the following directory: usr/sap/<SID>/
<INSTANCE_NAME>/j2ee/configtool.
VIM070500-05-IGD-EN-2
Notes
• SID is the system ID of the NWAS (example O15).

• INSTANCE_NAME is the NWAS instance in the format of JCxx, where
xx is the instance number (example JC00).
The script file is:
• configtool.bat for Windows hosts
• configtool.sh for Unix hosts
a. Add the startup parameter to the Java parameters on the server: -Dcom.
opentext.vim.portal.invoiceCfg=<Approval_Portal_installdir>.
Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/opentext/
invoiceCfg
b. Save the new parameter.
3. To apply the new startup parameter, restart the NWAS.

Restarting informs the server that the <Approval_Portal_installdir> folder
contains application specific information.
VIM070500-05-IGD-EN-2
15.3. Configuring the administrator role
15.3 Configuring the administrator role

Important
This section is only needed if you are installing as a standalone J2EE
application residing on NWAS only utilizing integrated authentication.
This section describes the installation activities to assign the administrator role to the
user for the Approval Portal application. As the Administrator, you must login to
the Administrator page to perform some application configuration and to perform
other administration tasks. See section 11 “Administering the Approval Portal” in
OpenText Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-
AGD) for additional information.
15.3.1 Configuring the administrator role for access through

NWAS
This section describes how to create a VIM administrator role and assign it to the
domain user through NWAS Visual Administrator. For a description of the
necessary steps with SAP NetWeaver 7.3 and 7.4, see “Configuring the
Administrator Role for Access Through NWAS for SAP NetWeaver 7.3 and 7.4”
on page 116.
You must perform this configuration before deploying the .sca or .sda, to ensure
that the application recognizes the role.
To create the Administrator role:
1. Log in to J2EE Visual Administrator and navigate to Instance > Server >
Services > Security Provider.
2. Click on the Edit button.
VIM070500-05-IGD-EN-2
3. Click the Runtime tab > Policy Configurations tab > Security Roles tab.
4. To enable editing, click the Edit button.
5. Click the Add button.
6. In the Add Security Role dialog box, enter the role name: com.opentext.vim.
portal.administrator.
Note: The role name is case-sensitive.
Click OK.
To assign the role to the domain administrator user:
1. Select the role you have newly created.
2. Click the Add button which is on the right hand side next to Users.
VIM070500-05-IGD-EN-2
3. In the Choose Users or Groups dialog box, type the domain user to whom you
want to assign the administrator role.
4. Click on Search.
5. Select the user.
6. Click OK.
7. To change back to Read-only mode, click the Edit button.
To verify the configuration of the administrator role:
Note: Check this after you have deployed the .SCA or .SDA file, see
“Deploying the Software Component Archive” on page 118.
• Navigate to http://<NWAS>:<NWASPORT>/vimportal/admin.
VIM070500-05-IGD-EN-2
If you see a screen similar to the one above, you have configured the
administrator role successfully.
15.3.2 Configuring the Administrator Role for Access Through

NWAS for SAP NetWeaver 7.3 and 7.4
This configuration is mandatory if you have NetWeaver 7.3 or 7.4 Portal, but you
want to access the Portal application using a normal web browser. If you want to
launch the Portal Application using NetWeaver 7.3 or 7.4 Portal, you can skip this
section.
To configure the administrator role for access through NWAS for SAP
NetWeaver 7.3 and 7.4:
1. Log in to SAP NetWeaver Administrator and navigate to Configuration >

Identity Management
VIM070500-05-IGD-EN-2
2. Change Search Criteria to Role and click Create Role.
3. In Unique Name, enter com.opentext.vim.portal.administrator, and enter

an optional Description.
4. Click the Assigned Users tab and perform a search. Select the user and click
Add.
5. Save your settings.
VIM070500-05-IGD-EN-2
15.4 Deploying the Software Component Archive

Deploying the Software Component Archive comprises the following steps:
• “Connecting to the SAP Software Deployment Manager (SDM) for SAP

NetWeaver 7.0” on page 118
• “Deploying the .sca file or .sda file” on page 119
• “Checking correct deployment” on page 120
• “Optional: Starting the Approval Portal J2EE application manually” on page 122
• “Optional: Clearing the browser cache” on page 122
15.4.1 Connecting to the SAP Software Deployment Manager

(SDM) for SAP NetWeaver 7.0
You deploy the Software Component Archive, using the SAP Software Deployment
Manager (SDM).
Refer to the SAP help on SDM for more details on how to use SDM.
To connect to SDM:
1. To gain access to the file system, sign on to the host server as a user with
administrator rights.
2. Make sure the .sca (Software Component Archive) or .sda (Software

Deployment Archive) file is on a medium, for example, a CD drive, or a shared
directory, accessible from the host server.
3. Connect to the SAP Software Deployment Manager (SDM):

You find SDM in the following directory: usr/sap/<SID>/<INSTANCE_NAME>/
SDM/program.
Notes

The script file is:
• RemoteGui.bat for Windows hosts
• RemoteGui.sh for Unix hosts
VIM070500-05-IGD-EN-2
15.4. Deploying the Software Component Archive
15.4.2 Deploying the .sca file or .sda file

If there is a previous version of the Approval Portal, remove it before you continue.
Refer to “Uninstalling the Approval Portal“ on page 167 for further information.
To deploy the .sca file or .sda file:
1. In SDM, click the Deployment tab.

2. Click the Add SCA/SDA icon ( ) to add the .sca or .sda file to the
deployment list.
Which one to use depends on your requirements. Both of them will work.
3. In the Choose window, navigate to the IM_APPROVAL_PORTAL7_0.sca or
IM_APPROVAL_PORTAL7_0.sda file.
Note: The filename might be different.
4. Click Choose.
5. Click Next to finish step 1 of 4 of deployment.
6. In step 2 of 4 of deployment, click Next to continue.
7. In step 3 of 4 of deployment, click Start Deployment to continue.
8. Wait until deployment is finished.
VIM070500-05-IGD-EN-2
9. In step 4 of 4 of deployment, click Confirm to continue and finish deployment.
15.4.3 Checking correct deployment

To check whether the Approval Portal is deployed correctly, perform the following
procedure:
To check correct deployment of the Approval Portal:
1. In the SDM, click the SDM Repository tab and expand SAPJ2EEEngine.
IM_APPROVAL_PORTAL should be displayed under SAPJ2EEEngine. The version

number might be displayed, as well.
Note: If IM_APPROVAL_PORTAL is not displayed, use this Installation Guide

to check if anything is wrong or redo the installation.
2. To check the J2EE application from NWAS, navigate to http://
<NWAS>:<NWASPORT>/vimportal.
VIM070500-05-IGD-EN-2
You will see OpenText Approval error messages. This is correct as you have not
done any configuration yet.
3. Check the J2EE application:

Open the J2EE Visual Administrator.
a. Click on a server.
b. Expand Services.
c. Expand Deploy.
d. In the Deployed Components pane, expand sevlet_jsp.

opentext.com/IM_APPROVAL_PORTAL should be displayed.
Note: If opentext.com/IM_APPROVAL_PORTAL is not displayed, use

this Installation Guide to check if anything is wrong or redo the
installation.
VIM070500-05-IGD-EN-2
15.4.4 Optional: Starting the Approval Portal J2EE application

manually
By deploying through SDM, the Approval Portal J2EE application will start
automatically. If the Approval Portal J2EE application doesn't, you can start it
manually.
To start the Approval Portal J2EE application manually:
1. Click on a server.
2. Expand Services.
3. Expand Deploy.
See screenshot in Step 3 on page 121.
4. In the Deployed Components pane, expand sevlet_jsp.
5. Click on opentext.com/IM_APPROVAL_PORTAL.
6. Click the Start Application button on the right.
7. Select the server(s) you want to start and click OK.
15.4.5 Optional: Clearing the browser cache

You might face browser cache issues when you have upgraded from one Approval
Portal version to another Approval Portal version. In this case, it is necessary to clear
the browser cache. As the administrator, guide the end users to perform the
following steps to avoid browser cache issues on the particular browsers that are
supported for the Approval Portal.
To clear the cache on Internet Explorer:
1. Open Internet Explorer.
2. On the Tools menu, click Delete browsing history. Alternatively, press CTRL
+SHIFT+DEL.
3. In the Delete Browsing History dialog box, select the check boxes, as shown in
the following screenshot.
Make sure that the Preserve Favorites website data check box is cleared.
VIM070500-05-IGD-EN-2
4. Click the Delete button. Then wait for the browser to clear the cache.
To clear the cache on Firefox:
1. Open Mozilla Firefox.
2. Press CTRL+SHIFT+DEL.
3. In the Clear All History dialog box, select the check boxes, as shown in the
Make sure to select Everything in the Time range to clear list.
VIM070500-05-IGD-EN-2
4. Click the Clear Now button. Then wait for the browser to clear the cache.
To clear the cache on Chrome:
1. Open Chrome.
2. Press CTRL+SHIFT+DEL.
3. In the Clear browsing data dialog box, select the check boxes, as shown in the
Make sure to select the beginning of time in the Obliterate the following
items from list.
VIM070500-05-IGD-EN-2
15.5. Deploying the Software Component Archive with SAP NetWeaver 7.3
4. Click the Clear browsing data button. Then wait for the browser to clear the
cache.
15.5 Deploying the Software Component Archive with

SAP NetWeaver 7.3
To deploy the Software Component Archive with SAP NetWeaver 7.3:
1. Make sure the .sca file is placed in D:\usr\sap\trans\EPS\in.
2. To start the Java Support Package Manager, navigate to usr/sap/<SID>/

<INSTANCE_NAME>/j2ee/jspm
Notes
The script file is:
VIM070500-05-IGD-EN-2
• go.bat for Windows hosts

• go.sh for Unix hosts
3. Enter user name and password.
4. Click New Software Components, and then click Next.

If the component is already deployed, no applicable software component is
found.
If the component is not yet deployed, click Next to deploy the component.
VIM070500-05-IGD-EN-2
15.5. Deploying the Software Component Archive with SAP NetWeaver 7.3
5. Click Start.
VIM070500-05-IGD-EN-2
6. In the Completed screen, click Exit.
15.6 Deploying the Software Component Archive

using SUM
There is an important change with SAP NetWeaver 7.3 SP10 (and higher) and with
SAP NetWeaver 7.4. As the tool to deploy the Software Component Archive, the
Software Update Manager (SUM) replaces the Java Support Package Manager
(JSPM). This section describes the deployment with SUM.
To undeploy an existing Approval Portal component:
1. Navigate to <drive>:\usr\sap\<SAP instance>\J00\j2ee\console and run

guiconsole.bat.
2. Authenticate using Administrator credentials.

3. Enter the following command:
undeploy name=<Folder Name> vendor=<Vendor Name>
VIM070500-05-IGD-EN-2
15.6. Deploying the Software Component Archive using SUM
Example: To undeploy the 7.0 SP4 packaging file, the command is: undeploy
name=IM_APPROVAL_PORTAL7_0SP4 vendor=opentext.com
4. Press ENTER.
To deploy an existing Approval Portal component using SUM:
1. To place the Properties files, download the Approval Portal package and
extract opentext.zip in the following directory: <drive>:\usr\sap\<SAP
instance>\SYS\global.
2. If a SUM installation already exists in the system, you must rename or delete it.
3. Ensure to have a .SAR file at the location, where the SUM installation takes
place.
4. To install SUM, open a command prompt, navigate to the directory where
the .SAR file is located, and run the following command.
Syntax
sapcar -xvf <SUM…… file.SAR> -R <drive>:\usr\sap\<SAP instance>\
Example
sapcar –xvf SUM10SP10_8-20006676.SAR –R D:\usr\sap\MO3\
The SUM installation takes a couple of minutes. It is completed when the

number of extracted files is displayed at the command prompt.
5. Regarding the new SUM, the SAP control service certificate must be established,
otherwise SUM will not work. You can use the following workaround:
a. Navigate to <drive>:\usr\sap\<SAP instance>\SUM\sdt\param and edit

the jump_config file.
b. Change the parameter value /sapstartsrv/httpsconnection from true
to false and save the changes.
6. Navigate to <drive>:\usr\sap\<SAP instance>\SUM\. Run the STARTUP.bat
file using Run as administrator and wait until SL Controller started is
displayed at the command prompt.
7. Navigate to <drive>:\usr\sap\<SAP instance>\SUM\sdt\exe. Run the
DSUGUI.bat file using Run as administrator.
The SUM tool is opened.
SUM restriction
The SUM tool is valid until you completely finish deploying. You can
always stop and restart without any issues. However, if you want to use
the same SUM that you have previously used for deploying, it will not
work.
Click Log on.

8. For Role Administrator, create a Name and Password. Click OK.
VIM070500-05-IGD-EN-2
Click Next.
9. Specify Credentials
Enter User Name and Password.
Note: Make sure that you heed the Additional Information.
Click Next.
10. Select Target

Select the Manually prepared directory check box. Click Browse, navigate to
the OpenText Approval Portal package directory, and click OK.
Cross check the selected path and click Next.
11. Initialization - System Analysis

Click Next.
VIM070500-05-IGD-EN-2
15.6. Deploying the Software Component Archive using SUM
12. Extraction - Initial Software Extraction

Click Next.
13. Configuration - Information Gathering

Enter the AS Java Administrator Password and click Continue.
Note: This is not the same password that was configured for the SUM
authentication.
A step list is executed. Wait until Select Components is displayed. Click

Continue.
Another step list is executed. Wait until Component Status is displayed. Click
Continue.
Another step list is executed. Wait until System Parameters are displayed. Click
Continue.
Another step list is executed. Wait until a success message is displayed. Click
Next.
14. Checks - Requirements Check

A step list is executed. Wait until a success message is displayed. Click Next.
15. Preprocessing - Update Preparation

A step list is executed. Wait until Begin Update is displayed. Click Continue.
Click Next.
Another step list is executed. Wait until a success message is displayed. Click
Next.
16. Execution - Actual Update
A step list is executed. Wait until a success message is displayed. Click Next.
17. Postprocessing - Post-Update Activities

A step list is executed. Wait until Update Complete is displayed. Click
Continue.
Wait until a success message is displayed. Click Next twice.
18. Summary and Evaluation of the Process

Summary and Feedback Form are displayed. Click Next.
You can send an email to SAP. To finish the package installation, click Exit.
A summary page is displayed.
VIM070500-05-IGD-EN-2
Chapter 16
Configuring SAP NetWeaver Portal components
If you are deploying the Approval Portal on SAP NetWeaver Application Server
Java (NWAS) and the users are accessing the application through SAP NetWeaver
Portal, you must configure the SAP NetWeaver Portal components.
For a description of the configuration with SAP NetWeaver 7.3, 7.4, and 7.5, see
“Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and 7.5”
on page 139 and “Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5”
on page 153.
Note: For information on how to change the title of the iView, page, workset,
or role, refer to the SAP NetWeaver Portal Administration Guide from SAP.
As the SAP NetWeaver Portal administrator, you create the Appintegrator iView. To
make the application available for SAP NetWeaver Portal users, you have to
perform the following steps:
• “Creating AppIntegrator iViews for users” on page 133

• “Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and 7.5”
on page 139
• “Creating roles for users” on page 149
• “Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5” on page 153
• “Assigning roles to SAP NetWeaver Portal users” on page 156
• “Configuring iViews and roles for the administrator” on page 157
• “Administering the OpenText Approval Portal” on page 158
16.1 Creating AppIntegrator iViews for users

Consult your corporate policy on the location and the naming conventions of
creating iViews.
To create AppIntegrator iViews for users:
1. Login to SAP NetWeaver Portal as Administrator and expand Portal Content >
Content Provided by Other Vendor.
2. Create a folder under End User Content or under another location, if wanted.
VIM070500-05-IGD-EN-2
Chapter 16 Configuring SAP NetWeaver Portal components
3. Right-click on the new folder and select New > iView.
VIM070500-05-IGD-EN-2
16.1. Creating AppIntegrator iViews for users
4. In the iView wizard, click Portal Component – create an iView from a portal
component ... and click Next.
5. In Step 1: Portal Archive Selection, click com.sap.portal.appintegrator.sap and

click Next.
VIM070500-05-IGD-EN-2
6. In Step 2: Portal Component Selection, click Generic and click Next.
7. In Step 3: General Properties, enter the following parameters:
• iView Name (mandatory)

• iView ID (mandatory)
• iView ID Prefix
VIM070500-05-IGD-EN-2
16.1. Creating AppIntegrator iViews for users
• Description
Select the Master Language (mandatory).

Click Next.
8. In Step 4: Summary, click Finish to finish the initial iView creation.
9. Click Open the object for editing and click OK.
VIM070500-05-IGD-EN-2
10. In Property Editor, scroll to the Entry Point line and click Yes.
Scroll to the HTTP Request Method line and select HTTP:GET.
Click Save.
11. In Property Editor, scroll to the URL Template line.

Enter the following value:
http://$host$:$port$/vimportal/?
urlView=Y&PORTALUSER=<User.UserID>
Change host and port accordingly:
VIM070500-05-IGD-EN-2
16.2. Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and 7.5
$host$
NWAS server name where the Approval Portal J2EE application was
deployed
$port$
Port of that NWAS
Note: Do not change <User.UserID>.
12. Click Save and Close.

The creation of the AppIntegrator iView is now finished.
16.2 Creating AppIntegrator iViews for users with

SAP NetWeaver 7.3, 7.4, and 7.5
Consult your corporate policy on the location and the naming conventions of
creating iViews.
To create AppIntegrator iViews for users with NetWeaver 7.3, 7.4, and 7.5:
1. Login to SAP NetWeaver Portal as Administrator.
2. To create a new folder, navigate to Content Administration > Portal Content

Management > Portal Content > Content Provided by SAP > End User
Content.
VIM070500-05-IGD-EN-2
3. Right-click End User Content, point to New, and then click Folder.
VIM070500-05-IGD-EN-2
4. On the New Folder tab, enter Folder Name and Folder ID Prefix (for example,
com.opentext); then click Finish at the bottom of the page.
5. After creating the Approval Portal folder, navigate to Content Administration

> Portal Content Management > Portal Content > Portal Applications
VIM070500-05-IGD-EN-2
6. In Portal Applications, expand com.sap.portal.appintegrator.sap
VIM070500-05-IGD-EN-2
7. Right-click the Generic template. In the context menu, click Copy.
8. Navigate to Portal Content > Content Provided by SAP > End User Content.
9. In the Approval Portal folder, paste the Generic iView as PCD Object. See the
VIM070500-05-IGD-EN-2
The wizard of the PCD Object opens.
VIM070500-05-IGD-EN-2
10. Change the Object Name to Approval Portal Iview.

Click Next, then click Finish.
An iView is created.
VIM070500-05-IGD-EN-2
11. To configure the newly created iView, right-click ApprovalPortalIview, then

click Open > Properties.
VIM070500-05-IGD-EN-2
12. On the Approval Portal Iview tab, click All.
13. From the Show Category list, select Content - Generic Launcher.
VIM070500-05-IGD-EN-2
14. Configure the following parameters:
HTTP Request Method

HTTP GET
URL Template
http://<host name>:<port number>/vimportal/?
The URL is different for the Admin iView:
http://<host name>:<port number>/vimportal/admin?
Enter the following values:
<host name>
Name of the NWAS where the Approval Portal J2EE application was
deployed.
<port number>
Port of that NWAS.
Note: Do not change <User.UserID>.
15. To create an Admin iView, repeat Step 1 to Step 14. Choose the relevant URL
Template from Step 14.
16. From the Show Category list, select Navigation.

To make the iView visible, select the Entry Point check box.
VIM070500-05-IGD-EN-2
16.3. Creating roles for users
16.3 Creating roles for users

After creating a new AppIntegrator iView, you must create a role and add the
AppIntegrator iView to the role.
To create roles for users:
1. In the SAP NetWeaver Portal, navigate to the folder you created in “Creating
AppIntegrator iViews for users” on page 133.
2. Right-click on the folder, select New > Role.
VIM070500-05-IGD-EN-2
3. In Step 1, enter Role Name, Role ID, Role ID Prefix and Description.
Select the Master Language.
Notes
• See also Step 7 on page 136 in “Creating AppIntegrator iViews for
users” on page 133.
• Role ID Prefix is not mandatory. If you enter this parameter, you must
search by giving Role ID Prefix and Role Name when assigning the role
to the user.
4. Click Next.
VIM070500-05-IGD-EN-2
16.3. Creating roles for users
5. Click Finish.
6. Click Open the object for editing and click OK.
VIM070500-05-IGD-EN-2
7. In Property Editor, scroll to the Entry Point line and click Yes.
Click Save.
8. Select the AppIntegrator iView created in “Creating AppIntegrator iViews for

users” on page 133, right-click the iView and select Add iView to Role > Delta
Link.
Click Save.
The AppIntegrator iView is added to the role.
9. Click Close.
VIM070500-05-IGD-EN-2
16.4. Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5
16.4 Creating roles for users with SAP NetWeaver 7.3,

7.4, and 7.5
After creating a new AppIntegrator iView, you must create a role and add the
AppIntegrator iView to the role.
To create roles for users with SAP NetWeaver 7.3, 7.4, and 7.5:
1. In the SAP NetWeaver Portal, navigate to the Approval Portal folder; see
“Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and
7.5” on page 139.
2. Right-click on the folder, select New > Role > Freestyle Role.
VIM070500-05-IGD-EN-2
3. Enter properties as shown in the screenshot above: Role Name, Role ID, Role
ID Prefix and Description.
Select the Master Language.
Note: Role ID Prefix is not mandatory. If you enter this parameter, you
must search by giving Role ID Prefix and Role Name when assigning the
role to the user.
4. Click Finish.
VIM070500-05-IGD-EN-2
16.4. Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5
5. To edit the properties of the created role, click Properties.
6. Enter the Name (as shown in the screenshot) and select the Entry Point check
mark.
Click Save.
VIM070500-05-IGD-EN-2
7. Select the AppIntegrator iView created in “Creating AppIntegrator iViews for

users with SAP NetWeaver 7.3, 7.4, and 7.5” on page 139, right-click the iView
and select Add iView to Role > Delta Link.
Click Save.
The AppIntegrator iView is added to the role.
8. To create an Admin role, repeat Step 1 to Step 7. Enter the relevant name for the
Admin role.
9. Click Close.
16.5 Assigning roles to SAP NetWeaver Portal users

After creating AppIntegrator iViews and adding them to roles, you must assign the
roles to the SAP NetWeaver Portal users.
To assign roles to SAP NetWeaver Portal users:
1. In the SAP NetWeaver Portal, click User Administration > Identity

Management.
2. In the Search Criteria, enter the users or groups you want to assign to the new
role (created in “Creating roles for users” on page 149).
Click Go.
3. In the Details of User panel, click the Assigned Roles tab.
4. Click Modify.
5. In the Search Criteria field, search for the new role you created and click Go.
6. Select the new role and click Add.

You can see the role in the Assigned Roles tab.
7. Click Save.
The following screenshot shows a role being assigned to a demo coder.
VIM070500-05-IGD-EN-2
16.6. Configuring iViews and roles for the administrator
16.6 Configuring iViews and roles for the

administrator
Configuring iViews and roles for the administrator is almost the same as for users.
See sections for different NetWeaver versions above.
You can use Approval Admin for the iView Name and Approval Admin Role for the
role.
The only difference from the user configuration is the URL template:
http://$host$:$port$/vimportal/admin?
See Step 11 on page 138 for details on the URL template for users.
VIM070500-05-IGD-EN-2
Once you have finished the creation of the Administrator iView and the role, assign
it to the appropriate administrators, as described in “Assigning roles to SAP
NetWeaver Portal users” on page 156.
When you, as the administrator, navigate to the Approval Admin iView, it will look
like the following screenshot:
You have now finished the installation and configuration of the OpenText Approval
Portal.
16.7 Administering the OpenText Approval Portal

For information on the administration of the Approval Portal, see section 11
“Administering the Approval Portal” in OpenText Vendor Invoice Management for SAP
Solutions - Administration Guide (VIM-AGD).
VIM070500-05-IGD-EN-2
Chapter 17
Applying a new patch
Note: Unlike the VIM SAP ERP component, the Approval Portal is a build and
has no dependencies of previous patches or support packages. You can
uninstall the previous version and directly install the newest version without
applying the patches in between. However, the patch or build needs to match
to the VIM SAP ERP component. Approval Portal 7.5 will only work with the
VIM 7.5 SAP ERP component.
New .sca file or .sda file

Follow the steps to undeploy the .sca or .sda file in “Uninstalling using
Software Deployment Manager” on page 167, and then follow the steps to
deploy the .sca file or .sda file in “Deploying the .sca file or .sda file”
on page 119.
New <language>.properties files

Extract the new <language>.properties files from the media to
<Approval_Portal_installdir> and perform the Reinitialize Application task. See
section 11 “Administering the Approval Portal” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for more details.
VIM070500-05-IGD-EN-2
Chapter 18
Upgrading the Approval Portal from previous
versions
The Approval Portal upgrade procedure is simple:

• Undeploy the old and deploy the new .SCA file, and
• Freshly install the OpenText installation directory.
Note: Consider supported landscapes, browsers, and other configuration

before upgrading.
Direct upgrades from previous versions to 7.5 are possible.
Approval Portal 5.2 to 7.5, Approval Portal 6.0 to 7.5, Approval Portal 7.0 (old UI)
to 7.5
Undeploy the old and deploy the new .SCA file, and freshly install the OpenText
installation directory.
Approval Portal 7.0 (new UI) to 7.5

Undeploy the old and deploy the new .SCA file. You can reuse the existing
OpenText installation directory.
Approval Portal 7.5 uses an additional xml file (RequestMappings.xml), which is

not available in Approval Portal 5.2 and 6.0. Therefore, if you want to upgrade from
Approval Portal 5.2 or 6.0, you must update the existing 5.2 or 6.0 installation
directory with the 7.5 installation directory.
Make sure that all files mentioned in opentext.zip are deployed correctly.
For an upgrade from Approval Portal 7.0 (new UI) to 7.5, you can reuse the original
configuration.xml file. However, it is best to make a backup of the
configuration.xml. For all other upgrade paths, OpenText recommends that you
use the new configuration.xml.
If you changed the language properties files from the previous version and would
like to reuse them in VIM 7.5, change the new language properties files manually.
To upgrade, perform the actions described in “Applying a new patch“ on page 159.
VIM070500-05-IGD-EN-2
Chapter 19
Troubleshooting
For information on troubleshooting the Approval Portal, see section 29.12

“Troubleshooting” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD).
VIM070500-05-IGD-EN-2
Chapter 20
Supporting installation of the standalone NWAS
Portal and Mobile Approval Portal on Unix or Linux
This chapter provides instructions how to enable the installation of the standalone
NWAS Portal and Mobile Approval Portal on Unix or Linux operating systems.
The Configuration tab of the Approval Portal Administration console provides a

Domain input field to accept the authentication domain for users. The setting of this
field is applied to all Approval Portal and Mobile Approval Portal users.
To support Unix or Linux operating systems, you must maintain the Domain field
with the same value, as maintained in the Windows Domain column in the COA
table. For details about the COA configuration, see section 5.5.1 “User Details View”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Example: If the Windows Domain column in the COA table is not maintained for users,
leave the Domain field in the Configuration tab of the Approval Portal Administration
console empty as well.
VIM070500-05-IGD-EN-2
Chapter 21
Uninstalling the Approval Portal
To uninstall the Approval Portal, perform the following steps:

• “Uninstalling using Software Deployment Manager” on page 167
• “Uninstalling with SAP NetWeaver 7.3, 7.4, and 7.5” on page 168
• “Removing SAP NetWeaver Portal components” on page 169
• “Deleting properties files” on page 170
• “Optional: Removing the startup parameter in the Config Tool” on page 170
21.1 Uninstalling using Software Deployment

Manager
This section describes how to uninstall the .epa and .ear files from the SAP
Software Deployment Manager (SDM) repository. For a description of uninstalling
with SAP NetWeaver 7.3, 7.4, and 7.5, see “Uninstalling with SAP NetWeaver 7.3,
7.4, and 7.5” on page 168.
To uninstall files from the SDM repository:
1. Connect to the SAP Software Deployment Manager (SDM) in the host server:
You find SDM in the following directory: usr/sap/<SID>/<INSTANCE_NAME>/
SDM/program.
Notes
The script file is:
• RemoteGui.bat for Windows hosts
• RemoteGui.sh for Unix hosts
Refer to the Software Deployment Manager Guide for more details on how to
use SDM.
2. In SDM, click the Undeployment tab.
3. Find and click IM_APPROVAL_PORTAL.
4. Click Select.
VIM070500-05-IGD-EN-2
Chapter 21 Uninstalling the Approval Portal
5. Click Start Undeployment.

In Step 2 of 2, you see the progress.
6. To finish the undeployment, click Confirm.

opentext.com\IM_APPROVAL_PORTAL should no longer appear in the Visual
Administrator.
21.2 Uninstalling with SAP NetWeaver 7.3, 7.4, and 7.5

This section describes how to undeploy the Approval Portal with SAP NetWeaver
7.3, 7.4, and 7.5.
To undeploy the Approval Portal with SAP NetWeaver 7.3, 7.4, and 7.5:
1. Navigate to D:\usr\sap\W73\J00\j2ee\console\ and run guiconsole.bat.
2. Enter user name and password.
3. In the J2EE Engine Console, type list_app to view the list of components that
are deployed.
4. To undeploy, run the following command:

undeploy name=IM_APPROVAL_PORTAL7_0 vendor=opentext.com
After undeployment, a success message is displayed.
VIM070500-05-IGD-EN-2
21.3. Removing SAP NetWeaver Portal components
21.3 Removing SAP NetWeaver Portal components

This section describes how to remove iViews, pages, worksets and roles from the
SAP NetWeaver Portal content.
Note: First, unassign the role if you already have assigned it to a user.
To remove SAP NetWeaver Portal components:
1. Login to the SAP NetWeaver Portal as SAP NetWeaver Portal Administrator.
2. Click Content Administration.
3. Expand Portal Content.
4. Navigate to the folder that was created in “Creating AppIntegrator iViews for
users” on page 133.
VIM070500-05-IGD-EN-2
Chapter 21 Uninstalling the Approval Portal
Right-click the folder and click Delete.

5. In the Delete Confirmation page, click Finish.
The “OpenText Approval Portal” folder is now deleted.
21.4 Deleting properties files

At this stage of the uninstallation process, delete the folder that contains the
properties files. The default folder name is usr/sap/<SID>/SYS/global/opentext/
invoiceCfg, where <SID> is the system ID of the SAP NetWeaver Application
Server Java (NWAS). See “Preparing the installation” on page 110 for details on the
properties files.
21.5 Optional: Removing the startup parameter in the

Config Tool
Note: This section is only relevant if you have added a startup parameter in
the Config Tool, see Step 2 on page 111 in “Preparing the installation”
on page 110.
Removing the startup parameter, using the J2EE Config Tool, finishes the
uninstallation process.
To remove the startup parameter:
1. Invoke the J2EE Config Tool:

You find the Config Tool in the following directory: usr/sap/<SID>/
<INSTANCE_NAME>/j2ee/configtool.
Notes
The script file is:
VIM070500-05-IGD-EN-2
21.5. Optional: Removing the startup parameter in the Config Tool
• configtool.bat for Windows hosts

• configtool.sh for Unix hosts
2. Remove the startup parameter:

-Dcom.opentext.vim.portal.invoiceCfg=<Approval_Portal_installdir>.
Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/opentext/
invoiceCfg
4. Restart the NWAS to remove the startup parameter.
The uninstallation is now completed.
VIM070500-05-IGD-EN-2
Part 6
Mobile Approval Portal installation
Part 6 Mobile Approval Portal installation
This part describes the installation of the Mobile Approval Portal, which is an
enhancement to the Invoice Approval. Users can approve their invoices, using a
mobile device, for example a Blackberry, an iPhone, or an iPad. The Mobile
Approval Portal is based on HTML5.
Note: The Mobile Approval Portal is an optional component. If you are not
using the Mobile Approval Portal, you can skip this part.
For information on the configuration of the Mobile Approval Portal, see section 12
“Configuring the Mobile Approval Portal” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD).
VIM070500-05-IGD-EN-2
Chapter 22
Introduction to the Mobile Approval Portal
A mobile application (Mobile Approval Portal) is available as a new SAP mobile

solution for VIM. Using the Mobile Approval Portal, users can perform their
approval tasks in a simple GUI, directly on their mobile device.
The Mobile Approval Portal component is enhanced with the mobile capabilities
Sencha Touch. This enriches the look and feel on the supported mobile platforms.
For detailed information about Sencha Touch, see http://www.sencha.com/products/
touch/features/.
Operating The Mobile Approval Portal supports Windows, Unix and other operating systems
systems supported by SAP.
There is no restriction which Windows or Unix versions or patch levels are

supported. Mobile Approval Portal supports all versions. Aligned with SAP
operating system support, see the SAP Product Availability Matrix (PAM) for more
details.
The following table shows which mobile operating systems, devices, and browsers
are fully supported.
The Category column signifies Performance, Usability/Accessibility and Document

Viewing aspects, ranked from A to C. A, B, and C are rankings from top to bottom
on the mentioned aspects. These ranks are provided based on testing in OpenText
Mobile lab with real devices and simulators.
Mobile Operating Device Browser Category

System
iOS (5.1.x or higher) iPad Safari (5.1.x or higher) A
iOS (5.1.x or higher) iPhone Safari (5.1.x or higher) A
BlackBerry (BB OS 10) BlackBerry BlackBerry OS 10 C
browser
Android (4.0.x or Any Android device[a] Chrome (23.0 or higher) B
higher) and Supported
browsers
WindowsPhone (8 or Any WindowsPhone Internet Explorer B
higher) device mobile version (10 or
higher)
[a]
In general, you can view the Mobile Approval Portal inside the browser on all kind of Android devices.
Due to the diversity of physical Android devices, OpenText cannot guarantee 100% compatibility on all
functionality that the Mobile Approval Portal offers.
VIM070500-05-IGD-EN-2
Chapter 22 Introduction to the Mobile Approval Portal
Web Viewer Mobile Approval Portal users can display invoices using OpenText Imaging Web
integration Viewer. Web Viewer is a web application for displaying and printing documents in
Web-based scenarios and for appending comments to these documents. The
documents may be stored in OpenText Archive Center or other repositories.
The Web Viewer integration is completed for the invoice document and supports all
documents supported by Web Viewer.
On the Mobile Browser without Web Viewer, it is not possible to render TIFF
documents. JPG, PNG and GIF documents are supported to be shown in browser by
default. To support PDF documents, a specific browser-plugin or a separate viewer
app is needed.
However, Web Viewer is able to display TIFF documents on the Mobile Browser on
Mobile Approval Portal.
Web Viewer is installed on a web server. It generates HTML pages containing the
document to be displayed and sends them to the browser. The Web Viewer can be
used by any leading application server configured appropriately.
Web Viewer supports documents from the following products:

• OpenText™ Archiving and Document Access for SAP Solutions
• OpenText™ DocuLink for SAP Solutions
Limitations
• Web Viewer does not support MS Office documents.
• For attachments, the Web Viewer integration is not implemented. Any attached
document, like PDF, JPEG, GIF or PNG, will be forced to open in a separate
browser window by default.
Notes
• OpenText strongly recommends that you implement Web Viewer to display
images on the Mobile Approval Portal.
• For further information about Web Viewer, see OpenText Imaging Web Viewer
- Installation and Configuration Guide (CLWEBV-IGD).
VIM070500-05-IGD-EN-2
Figure 22-1: HTML5 Mobile Approval Portal Architecture
VIM070500-05-IGD-EN-2
Chapter 23
Authentication for the Mobile Approval Portal
This section describes the communication and authentication needed for the Mobile
Approval Portal.
The Mobile Approval Portal uses domain authentication. It can be accessed using
WiFi or VPN on the same network or on an external network.
To access from external network without WiFi or VPN, keep the Mobile Approval
Portal URL in the DMZ and connect with Virtual Host. This requires IT help to
configure the URL in the DMZ.
Note: For security reasons and also to grant stable access to the Mobile
Approval Portal, OpenText recommends that you use a VPN connection.
The detail authentication mechanism is the same as for the Approval Portal, for
example, which SSO mechanism is used. See “Preparing installation“ on page 99
VIM070500-05-IGD-EN-2
Chapter 24
Installing Web Viewer for the Mobile Approval

Portal
OpenText Imaging Web Viewer can be integrated in the Mobile Approval Portal. To
ensure security for the Web Viewer integration, OpenText recommends that you
verify the “Use Signature” setting in /IXOS/OA_CUST_A with the following
prerequisites:
• Archiving and Document Access for SAP Solutions (OTEXBAS) 10.0 SP2
• OpenText Imaging Web Viewer 10.2.0, latest patch.
• OpenText Archive Services Patch ASR-1021-007 or higher (as included in
Enterprise Library 10.2.1 Patch Collection 1021_2012_04)
Note: See also the Release Notes of Archiving and Document Access for SAP
Solutions 10.0 SP2.
Web Viewer version 10.5.0 will be supported with a later Support Package.
The Mobile Approval Portal supports Windows, Unix and other operating systems
supported by SAP. For the Web Viewer installation, see the appropriate section in
section 3 “Installing Web Viewer” in OpenText Imaging Web Viewer - Installation and
Configuration Guide (CLWEBV-IGD).
To install Web Viewer 10.2.0, download the software from the following location:
http://knowledge.opentext.com/knowledge/cs.dll/Open/19642255.
To apply the latest patch for Web Viewer 10.2.0, download the software from the
following location: https://knowledge.opentext.com/knowledge/cs.dll/Open/
22422170
Notes
• OpenText recommends that you use the latest patch of the supported Web
Viewer software version.
• OpenText also recommends installing Web Viewer on a NetWeaver 7.3, 7.4,
and 7.5 instance where Mobile Approval Portal is not running or on a
supported Tomcat version. This approach improves the performance of
viewing invoice images on Mobile devices.
• OpenText also recommends installing Web Viewer on the same domain as
the Archive Center and SAP NetWeaver Application Server Java.
VIM070500-05-IGD-EN-2
Chapter 25
Installing the Mobile Approval Portal
Installing the Mobile Approval Portal differs depending on the application server
you use:
• Standalone SAP NetWeaver Application Server Java (NWAS)

• SAP NetWeaver Portal
25.1 Installing the Mobile Approval Portal on

standalone NWAS 7.0/7.3/7.4
For a new standalone NWAS 7.0/7.3/7.4 installation, refer to “Preparing installation“
on page 99. If the SAP standalone NWAS 7.0/7.3/7.4 is already in place, skip this
step.
The Mobile Approval Portal software component is packaged along with the
Approval Portal component. The installation of the Mobile Approval Portal is
similar to Approval Portal. Refer to “Installing the Approval Portal“ on page 109.
25.2 Installing the Mobile Approval Portal on SAP

NetWeaver Portal 7.0/7.3/7.4/7.5
For a new SAP NetWeaver Portal 7.0/7.3/7.4/7.5 installation, refer to “Preparing
installation“ on page 99. If the SAP NetWeaver Portal 7.0/7.3/7.4/7.5 is already in
place, skip this step.
The Mobile Approval Portal software component is packaged along with the
Approval Portal component. The installation of the Mobile Approval Portal is
similar to Approval Portal. Refer to “Installing the Approval Portal“ on page 109.
25.2.1 Prerequisites
The following versions are supported:
SAP NetWeaver Portal

7.0 SP8 or higher
All higher support packages and enhancement packages of NetWeaver 7.0, 7.3,
7.4, and 7.5.
Approval Portal
7.5
VIM070500-05-IGD-EN-2
Chapter 25 Installing the Mobile Approval Portal
25.2.2 Scenario 1: Enabling Mobile Approval Portal for existing

customers running on SAP NetWeaver Portal
1. Un-deploy the existing Approval Portal.
2. For SAP NetWeaver Portal 7.0/7.3/7.4/7.5 customers, deploy/configure the

SPNego login module.
Mobile Approval Portal uses SSO with the SPNego Login Module. Therefore, it
is only supported on SAP standalone NWAS 7.0/7.3/7.4. If you are already on
SAP NetWeaver Portal 7.0/7.3/7.4/7.5, and you want to have Mobile Approval
Portal support, install the standalone NWAS (AS JAVA) component also on SAP
NetWeaver Portal 7.0/7.3/7.4/7.5. This means, both AS JAVA and EP Core should
be available on the NetWeaver instance.
Refer to “Installing the Mobile Approval Portal on standalone NWAS
7.0/7.3/7.4 ” on page 183 for specific SAP NetWeaver Portal versions.
3. Deploy the Approval Portal with the officially supported Support Package.
4. Access the Mobile Approval Portal URL in a supported smartphone / tablet.
25.2.3 Scenario 2: Enabling Mobile Approval Portal for new

customers
1. For SAP NetWeaver Portal 7.0/7.3/7.4/7.5 customers, deploy/configure the
SPNego login module.
Refer to “Installing the Mobile Approval Portal on standalone NWAS
7.0/7.3/7.4 ” on page 183 for specific SAP NetWeaver Portal versions.
2. Deploy the Approval Portal with the officially supported Support Package.
3. Access the Mobile Approval Portal URL in a supported smartphone / tablet.
VIM070500-05-IGD-EN-2
Part 7
Vendor Invoice Management ABAP CDS
views component installation
Part 7 Vendor Invoice Management ABAP CDS views
This part describes the installation of the Vendor Invoice Management ABAP CDS
views component. This component is used for the new VIM Analytics (VAN) report
in case of a SAP system with SAP NetWeaver AS ABAP 7.40 SP05 or higher. The
installation of this component is optional.
Important
The VIM SAP HANA component is no longer supported. It is replaced by
the new VIM ABAP CDS views component.
This component includes development objects, including ABAP CDS views, for the
new VAN. The ABAP CDS views are highly optimized for SAP® HANA database
systems but are also supporting all other database systems.
Note: Current results of mass data tests on Oracle® have shown that ABAP
CDS views are not the best choice for the new VAN on an Oracle Database
system.
VIM070500-05-IGD-EN-2
Chapter 26

Installation Tool (SAINT). For the VIM ABAP CDS views installation package, the
password is: 2BE2D4655A

The following prerequisites must be fulfilled for the installation of the VIM ABAP
CDS views package.

described in this document.
26.2.2 ABAP CDS views prerequisites

Check the following prerequisites prior to installation.
• For a list of available software components, check OSS note 2068615.
SAP NetWeaver AS ABAP 7.40 SP05 is the precondition for installing the VIM ABAP
CDS views package. In detail the following components must be installed:
Component SAP_ABA
Level: 740, support package SAPKA74005
Component SAP_BASIS
Level: 740, support package SAPKB74005
Another precondition for installing the VIM ABAP CDS views package is VIM 7.5
SP3.
Component OTEXVIM
Support package SAPK-75003INOTEXVIM
VIM070500-05-IGD-EN-2

VIM 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.
*.SAR) that can be extracted using the SAPCAR command line tool.
VIM070500-05-IGD-EN-2
Chapter 27
This chapter describes the installation of the VIM ABAP CDS views package.
To install the VIM ABAP CDS views package:
1. Copy the OTVIMCDS_INST_750_740.SAR file from My Support to a local folder.
2. Call the SAINT transaction (in client).

You get an initial screen, which shows the installed components.
3. On the menu, click Installation Package > Load packages > From Front
End and load the OTVIMCDS_INST_750_740.SAR file.
4. To add the VIM 7.5 CDS Views component, click Continue.
5. Select the package for the OTVIMCDS component. Carry out the import of the
package as described in the respective SAP documentation.
VIM070500-05-IGD-EN-2
Part 8
Vendor Invoice Management SAP CRM SAP
Shared Service Framework component
installation
Part 8 Vendor Invoice Management SAP CRM SAP
Shared Service Framework component installation
This part describes the installation of the Vendor Invoice Management SAP CRM
SAP Shared Service Framework component.
Note: This component is not supported in the VIM 7.5 version for SAP S/
4HANA on Premise.
VIM070500-05-IGD-EN-2
Chapter 28

Installation Tool (SAINT). For the VIM SAP CRM SAP Shared Service Framework
installation package, the password is 316C596F6A.

The following prerequisites must be fulfilled for the installation of the SAP Shared
Service Framework integration.

Installation Tool (SAINT) and CRM Add-On Installation
28.2.2 SAP CRM EHP1 prerequisites

The following components must be installed for SAP CRM 7.0 EHP1:
Component SAP_ABA
Level: 702
Component BBPCRM
Level: 701
Component SAP_BASIS
Level: 702
The following support packages must be installed:
SAPKA70203 (ABA), SAPKB70203 (BASIS)
VIM070500-05-IGD-EN-2

Component SAP_ABA
Level: 731
Component BBPCRM
Level: 702
Component SAP_BASIS
Level: 731
The following support packages must be installed:
SAPKA73102 (ABA), SAPKB73102 (BASIS), SAPKU70202 (CRM)

Component SAP_ABA
Level: 740
Component BBPCRM
Level: 703
Component SAP_BASIS
Level: 740
The following support packages must be installed: SAPKB74003 (BASIS),

SAPKA74003 (ABA), SAPKU71301 (CRM)
VIM070500-05-IGD-EN-2
28.2. Checking prerequisites
28.2.5 Activating Shared Service Framework

Independently from the EHP version, the following steps to activate the Shared
Service Framework are always required.
To activate Shared Service Framework using Switch Framework:
1. Run the SFW5 transaction.
2. Expand the ENTERPRISE_BUSINESS_FUNCTIONS node, select the Planned

Status check box for business functions CRM_IC_CEBP & CRM_SHSVC and
click the Activate Changes icon.

VIM070500-05-IGD-EN-2
Chapter 29
This chapter describes the installation of the Basis package of Vendor Invoice
Management (VIM) on an SAP CRM application server.
The basic components are installed with the Basis package.
SAP CRM version
• SAP CRM 7.0 EHP1

• SAP CRM 7.0 EHP2: Additional step needed, see Step 3 on page 197
• SAP CRM 7.0 EHP3: Additional step needed, see Step 3 on page 197
File
OTVIMSSF_INST_VIM701_702.SAR
Source path
INST_CRM_700/DATA/
Target path
\usr\sap\trans\EPS

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. Only if you install on SAP CRM 7.0 EHP2 or SAP CRM 7.0 EHP3:
An ACP file is necessary. The ACP file is available in SAP Marketplace as
Attribute Change Package 01 for OTVIMSSF 701_702.
Extract the CSR0120031469_0080724.PAT file from the
CSR0120031469_0080724.zip folder and copy it to the \usr\sap\trans\EPS
\in folder.
4. Carry out the import of the package as described in the respective SAP
documentation.
VIM070500-05-IGD-EN-2
VIM070500-05-IGD-EN-2
Chapter 30
To put the SAP Shared Service Framework integration into operation, you must
perform the following post installation tasks:
• “Activating business configuration sets in the CRM system” on page 199

• “Maintaining a logical system for the CRM system in VIM” on page 203
• “Installing Support Packages 1 and 2” on page 203
30.1 Activating business configuration sets in the

CRM system
Notes
• For every client, you must activate new BC Sets after installing VIM 6.0
CRM.
• You need the appropriate security authorization to run some of the
transactions.
You activate the BC Sets in the following steps:
1. Apply recommended user settings
2. Activate BC Set /OTVIMSSF/VIM60_SSF_CUSTOMIZING
Note: Check the tables in /OTVIMSSF/VIM60_SSF_CUSTOMIZING and decide

if it is appropriate to activate this BC Set.
Activate the BC set in the Configuration client of the development system and
create a transport from BC set activation, move the transport to the required
systems.
Do not activate the BC set in the production system. Create a customization
transport in the development system configuration client by activating the BC
set and move it to the desired systems.
To apply recommended user settings:
transaction.
From the Utilities menu, click User Settings.
VIM070500-05-IGD-EN-2
VIM 7.5 supports the following languages for CRM:
• German (DE)
• English (EN)
• Spanish (ES)
• French (FR)
• Hungarian (HU)
• Italian (IT)
• Japanese (JA)
• Dutch (NL)
• Portuguese (PT)
• Romanian (RO)
• Russian (RU)
• Chinese (ZH)
VIM070500-05-IGD-EN-2
30.1. Activating business configuration sets in the CRM system
To select your applicable languages, select the respective check box in the
Manual Selection column.
2. Click the Maint. Transaction tab.
Apply the settings, as shown in the screenshot.
3. To copy the settings, click .

You are now ready to activate the BC set.
To activate BC Sets:
transaction.
VIM070500-05-IGD-EN-2
2. Enter the BC set name /OTVIMSSF/VIM60_SSF_CUSTOMIZING and click the

Activate button (highlighted in the screenshot.
Note: If you are prompted to create a new transport, follow your standard
change request process for tracking changes.
3. Apply the recommended settings, as shown in the screenshot.
4. Click the Activate button.
Tip: You can skip any warnings during the activation.
After successful BC Set activation, a message is displayed in the lower left of the
SAP GUI: Activation ended with additional information.
VIM070500-05-IGD-EN-2
30.2. Maintaining a logical system for the CRM system in VIM
30.2 Maintaining a logical system for the CRM system

in VIM
To integrate the VIM SAP CRM SAP Shared Service Framework component into the
VIM SAP ERP component, you must maintain a logical system for the CRM system
in the backend ERP system (VIM SAP ERP component system). Support for SAP
CRM SAP Shared Service Framework will only be activated if the logical system of
the CRM is maintained. This setting generates the Service Requests button in the
dashboards and the Create SR check box in the process type definition.
To maintain a logical system for the CRM system in the SAP ERP system:
1. In VIM, run the /N/OPT/SPRO transaction and navigate to the menu path
Vendor Invoice Management > Cross Component Configuration > CRM
Integration > Maintain CRM Logical System.
2. Enter the logical system for the CRM system in the Constant Value field.
30.3 Installing Support Packages 1 and 2

When you have finished the package installation, use the SPAM transaction to install
the Support Packages 1 and 2. See the instructions in Release Notes OpenText
Vendor Invoice Management 6.0 CRM SSF SP1.pdf and Release Notes OpenText
VIM 60 CRM SSF SP2.pdf; available on My Support: https://
knowledge.opentext.com/knowledge/cs.dll/Open/19229480
VIM070500-05-IGD-EN-2
Chapter 31
Verifying installation
Make sure that the OpenText Vendor Invoice Management CRM add-on is reflected
in the installed components.
2. Click next to Component version.
VIM070500-05-IGD-EN-2
Chapter 31 Verifying installation
OTVIMSSF add-on component installed, with Release number 701_702 and
patch level 0002.
VIM070500-05-IGD-EN-2
Part 9
Vendor Invoice Management SAP
NetWeaver Business Warehouse
Part 9 Vendor Invoice Management SAP NetWeaver
Business Warehouse component installation
This part describes the installation of the Vendor Invoice Management SAP
NetWeaver Business Warehouse (VIM BW) component.
4HANA on Premise.
VIM070500-05-IGD-EN-2
Chapter 32

Installation Tool (SAINT). The following table shows the passwords for the VIM 7.0
BW installation package, which is also used for VIM 7.5:
SAP_BASIS Password
700 F17CB370FA
730 F17CB070FA

The following prerequisites must be fulfilled for the installation of the VIM BW
component.

32.2.2 VIM 7.0 BW prerequisites

• See OSS note 2068615: SAP Invoice Management by OpenText 7.5
Important
Running the OTVIMBW component is not supported when you are using an
SAP® HANA database.
• For SAP NetWeaver BW 7.3 only: Implement OSS note 1636155: 730SP6: Error
‘RSTRAN 510’ while activating Transformation (if not yet in the system with
SP6)
• The following components must be installed for SAP NetWeaver BW 7.x:
VIM070500-05-IGD-EN-2
Table 32-1: SAP NetWeaver BW 7.0 / SAP NetWeaver BW 7.3 EHP1 / SAP
NetWeaver BW 7.4
Option Component: SAP_BW Component: SAP_BASIS

Release Support Package Release Support Package
1 700 SAPKW70023 700 SAPKB70013
2 731 SAPKW73103 731 ----
3 740 ---- 740 ----
Table 32-2: SAP NetWeaver BW 7.3
Option Component: SAP_BW Component: SAP_BASIS

Release Support Package Release Support Package
1 730 SAPKW73001 730 SAPKB73001
• The Add-On BI_CONT ‘Business Intelligence Content’ must be installed in a

suitable version, for example:
• BI_CONT 705 for SAP NetWeaver BW 7.0
• BI_CONT 747 for SAP NetWeaver BW 7.3 EHP1

VIM070500-05-IGD-EN-2
Chapter 33
This chapter describes the installation of the Basis package of VIM on an SAP
NetWeaver BW application server.
The basic components of VIM SAP NetWeaver BW are installed with the Basis
package.
SAP NetWeaver BW 7.0 / SAP NetWeaver BW 7.3 EHP1
File
OTVIMBW_INST_VIM700_700.SAR
Source path
INST_BW_700/DATA/
Target path
\usr\sap\trans\EPS
SAP NetWeaver BW 7.3
File
OTVIMBW_INST_VIM700_730.SAR
Source path
INST_BW_730/DATA/
Target path
\usr\sap\trans\EPS

following command:
SAPCAR -xvf <name of SAPCAR file>
SAPCAR file.
3. Call transaction SAINT (in client 000). You get an initial screen, which shows the
installed components.
Click Start to add the VIM 7.0 BW component.
VIM070500-05-IGD-EN-2
4. Click Start to see the screen that presents the packages ready to be installed.
VIM070500-05-IGD-EN-2
5. Choose the package for component OTVIMBW. Carry out the import of the
VIM070500-05-IGD-EN-2
Chapter 34
Verifying the installation
Make sure that the VIM BW add-on is reflected in the installed components.
VIM070500-05-IGD-EN-2
Chapter 34 Verifying the installation
In the System: Component information dialog box, you should see the OTVIMBW
VIM070500-05-IGD-EN-2
Chapter 35
Upgrading SAP NetWeaver BW
The following upgrades are supported by exchange packages:

• Upgrade from SAP NetWeaver BW 7.0 to SAP NetWeaver BW 7.3
Source Path File Name Password

UPGR_BW_730/DATA/ OTVIMBW_EXCH_700_730.SAR F17CB076ED
• Upgrade from SAP NetWeaver BW 7.3 to SAP NetWeaver BW 7.3 EHP 1
Source Path File Name Password

UPGR_BW_731/DATA/ OTVIMBW_EXCH_700_731.SAR F17CB376ED
The following upgrade does not need an exchange package:

• Upgrade from SAP NetWeaver BW 7.0 to SAP NetWeaver BW 7.3 EHP 1
VIM070500-05-IGD-EN-2
Part 10
Vendor Invoice Management component for
SAP NetWeaver Gateway installation
Part 10 Vendor Invoice Management component for
SAP NetWeaver Gateway installation
This part describes the installation of the Vendor Invoice Management SAP
NetWeaver Gateway package (VIM GW). The VIM GW component is needed to run
the Supplier Self Service component.
4HANA on Premise.
Figure 4: Supplier Self Service architecture
VIM070500-05-IGD-EN-2
Chapter 36

Installation Tool (SAINT). The following table shows the passwords for the VIM 7.0
GW installation package, which is also used for VIM 7.5:
SAP_BASIS Password
700 up to 731 F17CB670FA
740 and higher not required
If you are asked for a SAP note number, use 2068615.

The following prerequisites must be fulfilled for the installation of the VIM GW
component.


36.2.2 VIM Gateway prerequisites


• For general information on the installation of the SAP NetWeaver Gateway
components, see http://help.sap.com/saphelp_gateway20sp08/helpdata/en/76/
08828d832e4aa78748e9f82204a864/content.htm.
• The following components must be installed for SAP NetWeaver Gateway:
VIM070500-05-IGD-EN-2
Table 36-1: SAP ERP 6.0 up to EHP7
Option Component: GW_CORE Component: IW_FND Component: IW_BEP

Releas Support Releas Support Releas Support
e Package e Package e Package
1 200 SAPK-20004IN 250 SAPK-25004INI 200 SAPK-20004INI
GWCORE WFND WBEP
• Implement OSS note 1744864: Multiple Origin for Generated BOR/RFC Objects
does not work
Table 36-2: SAP ERP 6.0 EHP7
Option Component: Component: IWFND_GC Component:

SAP_GWFND SAP_BASIS
Releas Support Releas Support Releas Support
e Package e Package e Package
1 740 SAPK-74009IN 100 SAPK-10002INI 740 SAPKB74009
SAPGWFND WFNDGC
Note: The Gateway component is not yet available for EHP8 (SAP_BASIS 750).

(SAINT) for installation. SAINT uses single PAT files (extension *.PAT), which
*.SAR), which can be extracted using the SAPCAR command line tool.
The SAR files can also be used directly in transaction SAINT.
VIM070500-05-IGD-EN-2
Chapter 37
To install the OpenText VIM GW package:
1. Copy the respective SAPCAR file (OTVIMGW_INST_VIM700_700.SAR

or OTVIMGW_INST_VIM750_740.SAR) from My Support to a local folder.
2. Call the SAINT transaction (in client 000).

3. On the menu, click Installation Package > Load packages > From Front End
and load file OTVIMGW_INST_VIM700_700.SAR or OTVIMGW_INST_VIM750_740.
SAR.
4. To add the VIM 7.0 GW component, click Continue.
5. Choose the package for component OTVIMGW. Carry out the import of the
Note: Gateway package OTVIMGW_INST_VIM750_740 does only

support Supplier Self Service cloud deployment with VIM version 7.5 SP2
(7.0 SP6).
All previous Supplier Self Service cloud deployment versions are only
supported with Gateway package OTVIMGW_INST_VIM700_700.
VIM070500-05-IGD-EN-2
Chapter 38
Make sure that the VIM GW add-on is reflected in the installed components.

In the System: Component information dialog box, you should see the OTVIMGW
VIM070500-05-IGD-EN-2
Chapter 39
Make sure that namespace /OPT/ is modifiable.
Therefore, run the SE03 transaction, and, under Administration, run Set System
Change Option.
The value for namespace /OPT/ must be Modifiable.
VIM070500-05-IGD-EN-2
Part 11
Vendor Invoice Management Supplier Self
Service component installation
Part 11 Vendor Invoice Management Supplier Self
Service component installation
This part describes the installation of the Vendor Invoice Management Supplier Self
Service component.
4HANA on Premise.
VIM070500-05-IGD-EN-2
Chapter 40
40.1 Installation prerequisites

A complete installation and configuration of OpenText Vendor Invoice Management
is needed for installing and testing the Supplier Self Service. Although it is possible
to install the Supplier Self Service before the installation and configuration of the
SAP ERP and Gateway component, you will not be able to verify if the installation of
the Supplier Self Service is completed and correct.
The Supplier Self Service lean variant is enabled for multiple deployment options:
• HANA Cloud Deployment (runs on SAP HANA Cloud Platform)
• On-Premise (runs on SAP ABAP NetWeaver)
Operating This section covers support and restrictions of Supplier Self Service in regards to
system and operating systems and web browsers.
browser support
• The Supplier Self Service web application does not support any mobile operating
systems. It does not support any other operating systems than Windows.
Therefore, Mac/iOS, Linux, and Android operating systems are not supported.
• For supported browsers, see OSS note 1716423: SAPUI5 Browser Support for
Mobile and Desktop Applications
• Some additional browser settings are necessary:
Firefox
You must customize the language preferences: Go to Tools > Options, and
click the Content tab. In the Languages area, click Choose.
Add languages from the Select a language to add list. When performing
an HTTP request, Firefox will send all the languages chosen with the Accept-
Language header in the order of preference in which they are arranged in the
list.
Windows Internet Explorer 9
The website might appear blank or might not be displayed correctly. In this
case, set and use the Compatibility View on the menu bar of the browser:
• To use the Compatibility View, open the webpage in Internet Explorer,
and then, on the Tools menu, click Compatibility View. If you do not see
the Tools menu, press ALT.
• To set the Compatibility View, on the Tools menu, click Compatibility
View settings. If you do not see the Tools menu, press ALT. In the
Compatibility View Settings dialog box, enter the address of the
webpage, and then click Add.
VIM070500-05-IGD-EN-2
SAP user The communication with the SAP NetWeaver Gateway system is accomplished by
using a Service user ID. Creation and assignment of the specific profile is described
in section 23.1.3 “Configuring Gateway users” in OpenText Vendor Invoice
40.2 Installation components

For the cloud deployment option, a WAR file (Web application ARchive) is supplied.
It is used to distribute a collection of Java Servlets, JavaScript files, XML files, and
other resources that together constitute the Supplier Self Service web application.
The on-premise application is part of the GW 740 package, and will be automatically
deployed to the ABAP stack.
40.3 System architecture

This section explains the overall system architecture of the Supplier Self Service.
There are a few ways to deploy and run the Supplier Self Service application. The
following diagram shows the architecture for each scenario:
Figure 40-1: Supplier Self Service system architecture
If you plan to use the On-Premise deployment, skip “Installation on the SAP HANA
Cloud“ on page 233.
VIM070500-05-IGD-EN-2
Chapter 41
Installation on the SAP HANA Cloud
The SAP HANA Cloud Platform is an in-memory cloud platform based on open
standards. The platform is Java EE 6 Web Profile certified and provides a secure,
scalable runtime environment with reusable platform services. Therefore, Supplier
Self Service can run on the SAP HANA Cloud Platform just like on any Java-based
application server.
Note: You need an SAP account for accessing the SAP HANA Cloud.
41.1 Preparing the installation

To prepare the installation, you must deploy application specific files to the SAP
HANA Cloud Server. You also need a Cloud connector as a separate server
component that has to be installed on premise.
41.2 Deploying the application on the SAP HANA

Cloud Server
You deploy the application on the Cloud by using the SAP HANA Cloud Cockpit.
You must deploy the vimsupplierselfservice package in the form of a WAR file.
Deploying the Supplier Self Service application publishes it to the SAP HANA
Cloud Platform. For more information, see https://help.hana.ondemand.com/help/
frameset.htm?abded969628240259d486c4b29b3948c.html
To deploy the application:
1. Log on to the cockpit, and click Java Applications in the navigation area.
2. In the Java Applications panel, click Deploy Application.
VIM070500-05-IGD-EN-2
Chapter 41 Installation on the SAP HANA Cloud
3. In the Deploy Application dialog box, select the specific WAR file
vimsupplierselfservice.war to deploy. Initially the Cockpit proposes the
same name as for the WAR file. OpenText recommends that you enter the
application name vim3s but you can choose any other identifier you want.
Note: The application name must start with a letter, can contain lowercase
letters and numbers only, and must not exceed 30 characters. You can also
assign a display name and a description to the Java application.
4. Optional Specify additional parameters to configure the application. If omitted,

default values are assigned. For more information about the deploy parameters,
see the deploy command documentation https://help.hana.ondemand.com/
help/frameset.htm?937db4fa204c456f9b7820f83bc87118.html.
VIM070500-05-IGD-EN-2
41.3. Installing the SAP HANA Cloud connector
5. Click Deploy to deploy the WAR file to the cloud platform. The Deploy
Application dialog box remains on the screen while the deployment is in
progress. When the deployment is finished, a confirmation appears that the
application has been successfully deployed.
Note: At this stage, the application is not yet up and running.
Next steps To make your deployed application available for requests, you must start it inside
the SAP HANA Cloud Cockpit. For more information, see section 23.2 “Customizing
the HANA Cloud Server (option)” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM-CGD).
You can update or redeploy the application with a new WAR file or make changes
to the configuration parameters whenever required. To open the Deploy
Application dialog box in update mode, click Update application.
41.3 Installing the SAP HANA Cloud connector

The SAP HANA Cloud connector serves as the link between on-demand
applications on the SAP HANA Cloud Platform and existing on-premise systems.
Using Cloud connector, you can configure the systems that are exposed to the SAP
HANA Cloud Platform and control the resources available for the cloud applications
in those systems. Thus, you can benefit from your existing assets without exposing
the whole internal landscape.
Important
The SAP HANA Cloud connector must not be used with products other than
SAP HANA Cloud Platform.
The Cloud connector is a separate server component. It must be installed on premise

as described in the following online help: https://help.hana.ondemand.com/help/
frameset.htm?e6c7616abb5710148cfcf3e75d96d596.html
Note: OpenText strongly recommends that you use the latest version of the
SAP HANA Cloud connector software. Due to known security vulnerability
risks, do not use any version of SAP HANA Cloud connector earlier than 2.4.1.
VIM070500-05-IGD-EN-2
Part 12
Vendor Invoice Management ARIBA
Integration component installation
Part 12 Vendor Invoice Management ARIBA
Integration component installation
This part describes the installation and upgrade of the Vendor Invoice Management
ARIBA Integration (OTVIMARB) component. It integrates Ariba® with VIM.
If you do not have installed the OTVIMARB component yet, you must use the
installation package. If you are upgrading from VIM 7.0 and the OTVIMARB
component is installed already, you must use the upgrade package. The OTVIMARB
component is available in two releases. Release OTVIMARB 750 is for SAP ERP,
release OTVIMARB 750_S4 is for SAP S/4HANA on Premise.
VIM070500-05-IGD-EN-2
Chapter 42

The packages for the OTVIMARB component are protected with a specific
password.
OTVIMARB Package Password

Installation (SAP ERP) 2BE2D6734B
Upgrade (SAP ERP) 2BE2D6734C
Installation (SAP S/4HANA on Premise) <none>

The following prerequisites must be fulfilled for the installation of the OTVIMARB
component.

42.2.2 OTVIMARB prerequisites

• Vendor Invoice Management, minimum 7.0 SP3
• The following components must be installed for Ariba Network Integration 1.0
for SAP Business Suite:
VIM070500-05-IGD-EN-2
Table 42-1: Ariba Network Integration 1.0 for SAP Business Suite
Option Component: Component: Component:

ARBFNDI1 ARBERPI1 S4CORE
Release Support Release Support Release Support
Package Package Package
1 100 See the 600 See the
following following
Note. Note.
2 100
Notes
• OpenText recommends that you use the latest SP level of the OTVIMARB
component. The exact supported SP levels of the SAP components
ARBFNDI1 and ARBERPI1 are listed in the Release Notes of the
OTVIMARB support package.
• For a current and complete list of supported support packages of VIM,
VIM Ariba Integration component, and Ariba Network Integration for
SAP Business Suite, see the following Knowledge Base article: https://
knowledge.opentext.com/go/58540435.
• Implement OSS note 1935335: Mapping methods cannot be used from BAdI
implementations
• Implement OSS note 2026351: Extraction report modes inconsistence

(SAINT) for installation. SAINT uses single PAT files (extension *.PAT), which
*.SAR), which can be extracted using the SAPCAR command line tool.
The SAR files can also be used directly in transaction SAINT.
VIM070500-05-IGD-EN-2
Chapter 43
To install the OpenText OTVIMARB package:
1. Copy the respective SAPCAR file (*.SAR) from My Support to a local folder.
File
• OTVIMARB_INST_750_700.SAR (for installation on SAP ERP)
• OTVIMARB_UPGR_750_700.SAR (for upgrade on SAP ERP)
• OTVIMARB_INST_750_S4.SAR (for installation on SAP S/4HANA on Premise)
2. Call the SAINT transaction (in client 000).

3. On the menu, click Installation Package > Load packages > From Front End
and load file OTVIMARB_INST_750_700.SAR, OTVIMARB_UPGR_750_700.SAR, or
OTVIMARB_INST_750_S4.SAR.
4. To add or update the OTVIMARB component, click Continue.
5. Choose the package for component OTVIMARB. Carry out the import of the
VIM070500-05-IGD-EN-2
Chapter 44
Make sure that the OTVIMARB add-on is reflected in the installed components.

OTVIMARB add-on component installed, with Release number 750.
VIM070500-05-IGD-EN-2
Chapter 45
45.1 Activating business configuration sets for the

OTVIMARB component
Note: For every client, you must activate new BC sets after installing the
OTVIMARB component.
To activate the BC sets:
1. Login to your productive clients (in English).
2. Activate the BC Sets /OTVIMARB/700_CUSTOMIZING and /OTVIMARB/

700_SP1_CUSTOMIZING.
Note: Consider the most recent Release Notes for latest information on new BC
sets and additional post installation activities.
VIM070500-05-IGD-EN-2
Part 13
Vendor Invoice Management ABAP
OTVIMS4 component installation
Part 13 Vendor Invoice Management ABAP OTVIMS4
This part describes the installation of the Vendor Invoice Management ABAP
OTVIMS4 component. This component is needed for modifications that are
necessary to use certain VIM functions in a system based on SAP S/4HANA on
Premise. The installation of this component is not possible in an SAP ERP system,
the component is only for an SAP S/4HANA on Premise system.
VIM070500-05-IGD-EN-2
Chapter 46

Installation Tool (SAINT). For the VIM ABAP OTVIMS4 installation package, the
password is not required.

The following prerequisites must be fulfilled for the installation of the VIM ABAP
OTVIMS4 package.


46.2.2 ABAP OTVIMS4 prerequisites

Check the following prerequisites prior to installation.

• For a list of available software components, check OSS note 2068615.
Component S4CORE
Release: 100
Component SAP_ABA
Release: 75A
Component SAP_BASIS
Level: 750
Another precondition for installing the OTVIM4S package is VIM 7.5 SP4.
Component OTEXVIM
VIM070500-05-IGD-EN-2

VIM070500-05-IGD-EN-2
Chapter 47
This chapter describes the installation of the OTVIMS4 package.
To install the OTVIMS4 package:
1. Copy the OTVIMS4_INST_750_S4.SAR file from My Support to a local folder.

End and load the OTVIMS4_INST_750_S4.SAR file.
4. To add the OTVIMS4 component, click Continue.
5. Select the package for the OTVIMS4 component. Carry out the import of the
VIM070500-05-IGD-EN-2
Part 14
Vendor Invoice Management integration
with Ariba, PI scenario objects installation
Part 14 Vendor Invoice Management integration with
Ariba, PI scenario objects installation
This section describes the installation of the additional objects required to integrate
VIM with Ariba Network using the SAP NetWeaver Process Integration adapter
scenario (PI) and Ariba Cloud Integration (CI) components.
VIM070500-05-IGD-EN-2
Chapter 48
Importing ABAP workbench objects
You can select Ariba CI components to be used for your Ariba integration project
with the PI scenario. If you need to send status updates from SAP ERP back into the
Ariba Network, you need to import a set of transports and then adjust the VIM
configuration as described in section 24.2 “Integrating the Ariba SAP NetWeaver
Process Integration adapter” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM-CGD). The adapter version CI-8 and later is
supported.
Because of dependencies on the Ariba CI-8 adapter, OpenText delivers the necessary
ABAP workbench objects as a separate set of transport files. You find the transport
files on My Support.
The delivery of the transport files is provided with VIM 7.5 SP5. This scenario is
supported by VIM 7.0 SP3 and VIM 7.5 SP1 and later VIM versions. You can use the
provided transport files with the mentioned older VIM versions and SPs.
To import the transport files:
1. On My Support, access VIM 7.5 SP5 and Ariba Cloud Integration with PI
(https://knowledge.opentext.com/knowledge/cs.dll/Open/64801445).
2. Download the transport files.
3. Perform the import in the following sequence:
1. EW3K901050
2. EW3K901080
3. EW3K901083
4. After the import, perform additional configuration steps as described in section

24.2 “Integrating the Ariba SAP NetWeaver Process Integration adapter” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD). Additional information is available in an integration white paper,
which describes the different integration options and the necessary
configuration. The white paper is available for integration partners on My
Support: https://knowledge.opentext.com/knowledge/cs.dll/Overview/
38761889.
VIM070500-05-IGD-EN-2
Part 15
Vendor Invoice Management ABAP Invoice
Analysis app components installation
Part 15 Vendor Invoice Management ABAP Invoice
Analysis app components installation
This part describes the installation of the two Vendor Invoice Management ABAP
components that are needed for the VIM Invoice Analysis Fiori app (Invoice
Analysis app). The first component OTVIMWSR must run on the backend system,
where the VIM system is installed. The second component OTVIMWUI must be
installed on the front-end system. The installation of the components is optional, but
they are necessary if you want to use the Invoice Analysis app.
VIM070500-05-IGD-EN-2
Chapter 49

Installation Tool (SAINT). For the Invoice Analysis app installation package, the
passwords are the following:
Component Password
OTVIMWSR 2BE2C0725B
OTVIMWUI 2BE2C07440

The following prerequisites must be fulfilled for the installation of the Invoice
Analysis app package.

49.2.2 Checking Invoice Analysis app prerequisites

SAP prerequi- You can install the Invoice Analysis app on systems with SAP Basis 7.00 Support
sites Package Level 22 or higher.
The Invoice Analysis web application requires SAP Basis 7.40 Support Package
Level 9 or higher. The Invoice Analysis web user interface requires at least UI5
version 1.26.8. You can check the installed version by following the relative URL /
sap/public/bc/ui5_ui5/index.html.
Prior to installation, check the following prerequisites. For more information about
the overall system landscape and the relevant AddOn packages with detailed
prerequisites, see “System landscape” on page 262.
OSS notes Check the following OSS notes to avoid known problems with the SAP Add-On
Installation Tool (SAINT):
VIM070500-05-IGD-EN-2
• SAP 7.00 - OSS note 822380

• SAPCAR tool - OSS note 212876
Invoice Analysis The Invoice Analysis app uses a backend system and a frontend system. Both
app prerequi- systems have different system requirements. The backend system is a VIM system
sites
with the component IW_BEP (backend provider), which is available from SAP BASIS
700 SP 0022.
For the frontend system, you need SAP NetWeaver AS ABAP 7.40 SP09 as
precondition.
Another precondition for installing the Invoice Analysis app package is VIM 7.5 SP4.
Component OTEXVIM

VIM070500-05-IGD-EN-2
Chapter 50
Setup for the Invoice Analysis app
Setting up the Invoice Analysis app comprises the following deployment options:
• System landscape
• Configuring network options
• Checking the Fiori landscape
VIM070500-05-IGD-EN-2
Chapter 50 Setup for the Invoice Analysis app
50.1 System landscape
Figure 50-1: Invoice Analysis app landscape
The Invoice Analysis app includes the VIM Invoice Analysis UI (AddOn OTVIMWUI).
Minimum requirement for this AddOn is the following.
• User Interface Technology 7.40 (AddOn SAP_UI, version 740)
The WebUI retrieves data from the technical service /OPT/VIM_FX_VA2_SRV_SRV_V2.

The activation of this service is described in “Enabling OData service” on page 267.
The /OPT/VIM_FX_VA2_SRV_SRV_V2 service is part of the VIM Invoice Analysis Web

Services (AddOn OTVIMWSR). Prerequisites for this AddOn are the following.
• Backend Event Provider (AddOn IW_BEP) or SAP Gateway Foundation

7.40 (AddOn SAP_GWFND)
• OpenText Vendor Invoice Management (AddOn OTEXVIM)
OpenText recommends that you install the OTVIMWSR AddOn on the same system as
the OTEXVIM AddOn, as shown in Figure 50-1: “Invoice Analysis app landscape”
VIM070500-05-IGD-EN-2
50.2. Configuring network options
on page 262, but any other installation variants are also possible. However, all
systems must be connected using trusted RFCs.
50.2 Configuring network options

You must define which systems must be opened from a network perspective for an
Intranet or Extranet scenario. For more information, see the SAP Help
regarding Deployment Options (http://help.sap.com/fiori_bs2013/helpdata/en/4c/
ca4152fc94b610e10000000a44176d/content.htm) and Multiple Network Zones (http://
help.sap.com/saphelp_nw74/helpdata/en/aa/37ff4fa187622fe10000000a44176d/
content.htm?frameset=/en/1d/300050d5ac612fe10000000a44176d/frameset.htm&
current_toc=/en/f3/780118b9cd48c7a668c60c3f8c4030/plain.htm&node_id=15).
50.3 Checking the Fiori landscape

The Fiori system landscape must meet the requirements of the SAP guidelines. For
more information, see the SAP Help (http://help.sap.com/fiori_bs2013/helpdata/en/
ba/f61f533f86ef28e10000000a4450e5/content.htm?frameset=/en/4c/
ca4152fc94b610e10000000a44176d/frameset.htm&current_toc=/en/40/
1b675374bc6655e10000000a423f68/plain.htm&node_id=3&show_children=false).
VIM070500-05-IGD-EN-2
Chapter 51
Installing the OpenText packages
This chapter describes the installation of the two packages needed for the Invoice
Analysis app.
To install the VIM Web Services Component package on the backend:
1. Copy the OTVIMWSR_INST_750.SAR file from My Support to a local folder.

End and load the OTVIMWSR_INST_750.SAR file.
4. To add the OTVIMWSR 7.5 component, click Continue.
5. Select the package for the OTVIMWSR component. Carry out the import of the
To install the VIM Web UI Component package on the frontend:
1. Copy the OTVIMWUI_INST_750_740.SAR file from My Support to a local folder.

End and load the OTVIMWUI_INST_750_740.SAR file.
4. To add the OTVIMWUI 7.5 component, click Continue.
5. Select the package for the OTVIMWUI component. Carry out the import of the
VIM070500-05-IGD-EN-2
Chapter 52
Activating services
This section comprises the following actions:

• Enabling OData service
• Activating the service
• Activating the service nodes on BSP and UI5
52.1 Enabling OData service

The Invoice Analysis app communicates with the ABAP backend using a dedicated
OData service (/OPT/VIM_FX_VA2_SRV_SRV_V2). To invoke this service using the
HTTP protocol, it first must be enabled. This section describes the necessary steps.
Prerequisite All connection settings must be configured accordingly and the SAP NetWeaver
Gateway must be activated.
Call the /IWFND/MAINT_SERVICE transaction and maintain the backend OData

service for the external service /OTX/PF05_DATA.
Therefore you might need to connect to the backend system where the AddOn
Package OTVIMWSR is installed according to your system landscape setting.
VIM070500-05-IGD-EN-2
Chapter 52 Activating services
After that you must activate the registered service. To activate the service, run
the SICF transaction and activate the /sap/opu/odata/OPT/
VIM_FX_VA2_SRV_SRV_V2 service.
52.2 Activating the service

The technical unit of the Invoice Analysis app in the ABAP Frontend Server is a BSP.
A prerequisite for launching a BSP using the browser is an active service that is
bound to the BSP in the SICF transaction. For UI5 applications, the service is created
by default automatically, nevertheless you must activate it before it can be used.
To activate the service, run the SICF transaction and activate the /sap/bc/ui5_ui5/
opt/ svanreports service.
VIM070500-05-IGD-EN-2
52.3. Activating the service nodes on BSP and UI5
52.3 Activating the service nodes on BSP and UI5

After activating the services, create the service nodes. Perform the following steps to
create service nodes for opt and svanreports. After the service nodes are created,
you can run the URL of the BSP application.
To configure the Invoice Analysis app service on the BSP node:
1. Run the SICF transaction.
2. Navigate to the following path: default_host > sap > bc > bsp.
3. Select the bsp service.
4. Right-click the bsp service and create the new sub-element opt.
5. When opt is created, right-click the opt service and create a new sub-element
svanreports.
6. To activate the newly created services opt and svanreports, right-click them,
and then click Activate Service.
To configure the Invoice Analysis app service on the UI5 node:
1. Run the SICF transaction.
2. Navigate to the following path: default_host > sap > bc > ui5_ui5.
3. Select the ui5_ui5 service.
4. Right-click the ui5_ui5 service and create the new sub-element opt.
5. When opt is created, right-click the opt service and create a new sub-element
svanreports.
VIM070500-05-IGD-EN-2
Chapter 52 Activating services
6. To activate the newly created services opt and svanreports, right-click them,
and then click Activate Service.
VIM070500-05-IGD-EN-2
Chapter 53
Integrating the Invoice Analysis app into Fiori

Launchpad
This section provides a description how to create a solution specific tile for the SAP
Fiori Launchpad. Every tile is referring to the same Invoice Analysis web application
but with different parametrization.
For more details and further information about the Fiori Launchpad, see http://
scn.sap.com/docs/DOC-53178.
Figure 53-1: Overview of involved Fiori Launchpad infrastructure parts
When creating tiles for the Launchpad, there are three different ways how you can
link an application. For a UI5 application that is delivered as component, only the
“Target Mapping SAP UI5 Fiori App” mechanism is recommended.
Direct Link
The tile is directly referring to a relative or absolute URL.
Target Mapping Other SAP Fiori App

The tile is referring to a configured action of a semantic object that is defined as
target mapping through the Launchpad Designer. The target mapping links to a
Launchpad application that has been defined using the LPD_CUST transaction.
Necessary details are the Launchpad role, the Launchpad instance, and the
application alias.
Target Mapping SAP UI5 Fiori App

The tile refers to a configured action of a semantic object that is defined as target
mapping through the Launchpad Designer. In the target mapping, the concrete
UI5 component details are specified.
VIM070500-05-IGD-EN-2
Chapter 53 Integrating the Invoice Analysis app into Fiori Launchpad
Figure 53-2: Fiori Launchpad tile setup
Because the Invoice Analysis app is delivered as a UI5 component, the tile creation
description is referring to “Target Mapping SAP UI5 Fiori App”.
To create a Fiori Launchpad tile:
1. Create a semantic object.

For the Invoice Analysis app tile, create the semantic object SVANREPORTSOBJ.
To do this, run the /n/UI2/SEMOBJ transaction in SAP GUI. The semantic object
is only a logical placeholder. It does not consist of any specific data.
2. Create a tile catalog.

You use a tile catalog to group tiles and their target mappings. A tile catalog is
later included into the menu tree of a role that holds specific permissions. If you
want to include only a subset of a catalog into the menu of a role, create a tile
group.
You create tile catalogs and also groups using the Launchpad Designer, which
you can access through the relative URL /sap/bc/ui5_ui5/sap/
arsrvc_upb_admn/main.html.
VIM070500-05-IGD-EN-2
Note: For the Invoice Analysis app, at least one catalog is necessary. If you
plan to enroll the Fiori Launchpad configuration to another Fiori server,
ensure that a customizing request is specified, using the Settings button.
3. Create an Invoice Analysis target mapping.

In the Launchpad Designer, you must create one target mapping to the Invoice
Analysis app.
a. In the Intent area, choose the Semantic Object you have created in Step 1
on page 272 and specify an Action.
You can freely define the action. You must remember it when creating the
solution tiles. For that string, no value help is provided.
b. In the Target area, click SAP UI5 Fiori App for the Source of Navigation
Target.
c. Enter the parameters exactly as follows.
Title
<A title of your choice>
URL
/sap/bc/ui5_ui5/opt/svanreports
Component
ot.vim.van
4. Create tiles.
After you have defined the target mapping, you can create the wanted solution
tiles. For the Invoice Analysis app, you can create a static tile.
VIM070500-05-IGD-EN-2
General
Title
<A title of your choice>
Subtitle
<A subtitle of your choice>
Navigation
Use semantic object navigation

Select this check box.
Semantic Object
Enter the object that you have created in Step 1 on page 272.
Action
Enter the action that you have defined in Step 3 on page 273.
5. Assign catalog to role.

To provide the Invoice Analysis catalog to your users, you must create one or
more roles. This depends on your business roles. Then, you must add the
created catalog to the role menu tree. Make sure that you properly assign the
role to your user groups. For this, use the SAP GUI transaction PFCG.
6. Personalize the Launchpad.

Users can now access the Launchpad with the relative URL /sap/bc/ui5_ui5/
ui2/ushell/shells/abap/Fiorilaunchpad.html.
On the menu on the right, users must click Personalize Homepage. Then, they
can search for the created Invoice Analysis catalog and add one or more tiles
from it to the Home Page.
VIM070500-05-IGD-EN-2
7. Configure a direct link from the Gateway Server.
a. Sign in to the SAP Gateway Server.

b. Run the SE80 transaction and enter the package name /OPT/
SVAN_ANALYTICS.
c. Navigate to index.html and double-click index.html.
d. Access the Properties tab and copy the URL for direct access on the
browser.
VIM070500-05-IGD-EN-2
VIM070500-05-IGD-EN-2
Glossary
AAK
See SAP Add-On Assembly Kit (AAK).
After Image
Technical option to realize an delta upload from the source systems into the SAP
NetWeaver BW system. A data record loaded as After Image provides the status
of the record after it has been changed, or after data has been added.
Aging Report
Part of the Central Reporting infrastructure. The Aging Report reports about the
aging of documents and work items in the current system.
AP processor
Accounts Payable personnel
Application Component Hierarchy
Hierarchy of folders to structure DataSources in SAP NetWeaver BW.
Approval chart of authority (COA)
The Approval chart of authority (COA) determines first approver and next
approver for an invoice by combinations of Company Code (specific or range),
Expense Type (marketing expense, utility), Cost Objects (G/L account, Cost
Center), and HR objects (Position, Job code).
Approval Portal
VIM web interface for approving invoices.
Archive system
Computer system that enables storage, management and retrieval of archived

data and documents
ArchiveLink document types
Document types that need to be customized for ArchiveLink
ArchiveLink
Service integrated in the SAP NetWeaver Application Server ABAP for linking
archived documents and the application documents entered in the SAP ERP
system
VIM070500-05-IGD-EN-2
Glossary
Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can perform in the SAP ERP system. These authorizations are
stored in Authorization profiles.
Automation Report
Tool that provides data about automated and manual processing steps of VIM
documents
BAdI
See Business Add-Ins (BAdI).
BAPI®
SAP programming interface: Business Application Programming Interface
Baseline
Set of functionality with pre-defined configuration and the starting point to

implement VIM
BasisCube
See InfoCube.
BDC ID
Business Data Communication ID. The BDC ID is used by the system to process
an SAP transaction to create an SAP Document in user context.
Block
Situation where an invoice has a price or quantity variance that prevents invoice
from posting
BTE
See Business Transaction Event (BTE).
Business Add-Ins (BAdI)
Business Add-Ins (BAdI) is an SAP enhancement technique based on ABAP

objects. BAdI can be inserted into the SAP ERP system to accommodate user
requirements too specific to be included in the standard delivery.
Business Center Capture
OpenText Business Center Capture for SAP Solutions. Business Center

component for use in VIM. Automates the capture of paper invoices by using
OCR to extract invoice data.
VIM070500-05-IGD-EN-2
Glossary
Business Center
OpenText Business Center for SAP Solutions. OpenText product that helps
receiving incoming documents, capturing processes, and filing them within a SAP
system. VIM is tightly integrated with Business Center.
Business rules
Rules that describe the operations, definitions and constraints that apply to an
organization
Business Transaction Event (BTE)
Event used for extending a Non PO invoice functionality to call a custom program
Buyer
Person who is in charge of the PO. This role should have authorization to create
and change the purchase order. This role is also responsible for negotiating and
communicating with vendors.
Central Audit Report
Part of the Central Reporting infrastructure. The Central Audit Report is a

slimmed VIM Analytics (VAN). The main difference to VAN is that the Central
Audit Report serves as a single point of access in a multiple backend scenario.
Central Reporting
Reporting infrastructure that provides several reports that enable you to measure
certain properties of VIM documents and their work items, in order to optimize
working with VIM. Central Reporting comprises the following individual reports:
Aging Report, Central Audit Report, Exception Analysis Report, Key Process Analytics
Report, Productivity Report, and Summary Report.
Characteristic
Type of InfoObject in SAP NetWeaver BW that represents descriptions of fields,

such as Vendor ID, Invoice Number, Unit of Measure, and Posting Date.
COA
See Approval chart of authority (COA).
Coding
Coding allocates an invoice to G/L account and cost object if required.
Contract agent
Person who can create and modify SAP contracts.
VIM070500-05-IGD-EN-2
Glossary
Dashboard
User interface that organizes and presents information in a way that is easy to
read. Users can also perform actions from the dashboard.
Data Transfer Process (DTP)
Object in SAP NetWeaver BW to transfer data from source objects to target objects
DataSource
Set of fields in SAP NetWeaver BW that provide the data for a business unit for
data transfer to the SAP NetWeaver BW system; technically, it contains an extract
structure and an extraction function module.
DataStore Object (DSO)
Storage location for consolidated and cleansed data in SAP NetWeaver BW
DocuLink
OpenText™ DocuLink for SAP Solutions enables the archiving, management and
retrieval of SAP CRM or SAP ERP documents from within the SAP infrastructure.
Document Processing (DP)
VIM component that captures invoice metadata including line items for PO and
performs preconfigured business rules
Document type
Type of document such as PO, Non PO, OCR, Non OCR
DP
See Document Processing (DP).
DSO
See DataStore Object (DSO).
DTP
See Data Transfer Process (DTP).
Duplicate analyzer
Person who is responsible to identify duplicate invoices
EDI
See Electronic Data Interchange (EDI).
Electronic Data Interchange (EDI)
Method for transferring data between different application systems in the form of
messages. SAP applications support EDI with messages sent in an SAP
VIM070500-05-IGD-EN-2
Glossary
Intermediate Document (IDoc) format. VIM supports the creation of vendor

invoices through the EDI/IDoc interface.
Event Type Linkage
Error handling method. Event Type Linkage determines what the application
should do in case an error could not be handled.
Exception Analysis Report
Part of the Central Reporting infrastructure. The Exception Analysis Report

reports all work items with exceptions, grouped by exception, company code or
vendor.
Exception
Action that is not part of normal operations or standards
FI
See Financial Accounting (FI).
Financial Accounting (FI)
SAP module for the Finance and Accounting department
IAP
See Invoice Approval (IAP).
ICC
See Invoice Capture Center (ICC).
IDoc
See Intermediate Document (IDoc).
IE
See Invoice Exception (IE).
Indexer
Person responsible for entering index data
Indexing
Process of entering or storing data into the system
InfoArea
Folder in SAP NetWeaver BW to organize InfoCubes, DataStore Objects, InfoObjects,

and InfoObject Catalogs
InfoCube
Self-contained dataset in SAP NetWeaver BW, for example, of a business-oriented

area; an InfoCube is a quantity of relational tables arranged according to the
VIM070500-05-IGD-EN-2
Glossary
enhanced star schema: A large fact table in the middle surrounded by several
dimension tables
InfoObject Catalog
Folder structure in SAP NetWeaver BW to organize InfoObjects
InfoObject
Smallest information unit in SAP NetWeaver BW. Key figures and Characteristics
are collectively called InfoObjects.
InfoPackages
Object in SAP NetWeaver BW that specifies when and how to load data from a
given source system to the SAP NetWeaver BW system
InfoProvider
Object in SAP NetWeaver BW for which queries can be created or executed.

InfoProviders are the objects or views that are relevant for reporting.
Information provider
Receiving role for option Refer for Information
Intermediate Document (IDoc)
Standard SAP message document format for the EDI interface.
Invoice Approval (IAP)
VIM component that enables users to perform coding, approving and rejecting
invoices
Invoice approver
Person who approves invoices
Invoice Capture Center (ICC)
Optional VIM OCR component
Invoice characteristic
A value specific to each invoice (for example country) that allows flexible
processing in VIM. An invoice characteristic is determined during runtime and
depends on the corresponding index data of the document.
Invoice coder
Person who enters the accounting info on invoices to allocate the cost
VIM070500-05-IGD-EN-2
Glossary
Invoice Exception (IE)
VIM component that handles the exceptions that arise after an SAP invoice is
created
Invoice requester
Person who requested goods and services for Non PO invoices
Key Figure
Type of InfoObject in SAP NetWeaver BW that represents numeric values or

quantities, such as Number of Invoices and Gross Invoice Amount.
Key Process Analytics Report
Part of the Central Reporting infrastructure. The Key Process Analytics Report
reports about a variety of key figures regarding the VIM process: It shows the
accumulated amounts of all documents in the DP workflow, in parked state and
in posted state.
KPI Dashboard
Tool for managers showing VIM related process data at a glance in graphical
charts.
LIV
See Logistic invoice (LIV).
Logistic invoice (LIV)
purchase order invoice
Materials Management (MM)
Materials management module of the SAP ERP software package. Materials

management is used for procurement and inventory management.
MM
See Materials Management (MM).
Mobile Approval Portal
VIM component for approving invoices on mobile devices.
MultiProvider
Object in SAP NetWeaver BW that is based on InfoCube(s), DataStore Object(s),

and/or InfoObject(s). A MultiProvider is used as a layer for the creation of end user
queries; the MultiProvider itself does not contain any data; rather, data resides in
the BasisCubes.
VIM070500-05-IGD-EN-2
Glossary
Namespace
Name range reserved by SAP for customer objects and SAP objects to make sure
that objects are not overwritten by SAP objects during the import of corrections or
an upgrade
Non purchase order (Non PO)
Order that is not based on a PO
Non purchase order (Non PO) invoice (PIR)
Invoice based on a Non purchase order (Non PO)
Number range
Array of numbers that can be used for an object in the SAP ERP system
OCR
See Optical character recognition (OCR).
Optical character recognition (OCR)
Mechanical or electronic translation of images of handwritten, typewritten or

printed text (usually captured by a scanner) into machine-editable text
Park
Situation where an invoice is not posted and is waiting for further processing
Parked invoice document
Temporary document that the AP processor can change and post. SAP assigned
document number becomes real number when posted.
Persistent Staging Area (PSA)
Data staging area in SAP NetWeaver BW. It allows to check data in an

intermediate location before the data is sent to its destinations in SAP NetWeaver
BW.
PIR
See Non purchase order (Non PO) invoice (PIR).
PO
See Purchase order (PO).
Posted invoice document
Invoice that has already been posted in SAP ERP. Only free-form text fields can
be changed. Related documents such as POs or good receipts may be created or
changed to effect the invoice. If the document is not needed, it must be cancelled
( PO invoice) or reversed ( non-PO invoice).
VIM070500-05-IGD-EN-2
Glossary
Price variance
Situation where the price on the invoice is different from the price in the purchase
order
Process Chain
Sequence of processes in SAP NetWeaver BW that are scheduled to wait in the

background for an event; used to automate, visualize and monitor the processes.
Process options
Processing options for the user in the dashboard, such as Referral, Authorization,
and Actions
Process type
Process type for a document. The process type determines the initial actor and
various collaboration options available to the various actors during the process
flow.
Productivity Report
Part of the Central Reporting infrastructure. The Productivity Report reports

about the productivity of users/roles and the activities of users/roles.
PSA
See Persistent Staging Area (PSA).
Purchase order (PO) invoice
Invoice based on a Purchase order (PO)
Purchase order (PO)
SAP module. PO indicates a document sent from a buyer to a seller. The purpose
of the document is to order the delivery of goods or services.
Quantity variance
Situation where the quantity on the invoice is different from the quantity in the
purchase order
Receiver
Person who can create and reverse the goods receipt in SAP ERP
Requisitioner
Person who requested goods and services
VIM070500-05-IGD-EN-2
Glossary
Roles
Set of predefined roles for the SAP user
SAP Add-On Assembly Kit (AAK)
Standardized delivery procedure for software
SAP Customer Relationship Management (SAP CRM)
SAP application that provides software for ticket systems, for example in the
Accounts Payable department.
SAP NetWeaver Business Warehouse (SAP NetWeaver BW)
SAP application that allows to integrate, transform, and consolidate relevant

business information from productive SAP applications and external data
sources.
SAP Shared Service Framework
SAP software that contains a rich set of tools to improve and automate Shared
Service Center operations.
SAP Supplier Relationship Management (SAP SRM)
SAP application that automates, simplifies, and accelerates procure-to-pay

processes for goods and services.
Scan operator
Person who scans the invoices into images (may not have a SAP ID)
Service approver
Person who approves a service entry
Service requisitioner
Person who enters a service entry
Summary Report
Part of the Central Reporting infrastructure. The Summary Report provides a

summary of all documents processed through VIM.
Swimlane
Diagram representing a specific VIM process. A swimlane comprises the process

description, roles, user interface and options of the process.
VIM070500-05-IGD-EN-2
Glossary
Tax expert
Person who advises on invoices that need tax audit. Normally tax department
personnel.
Transformation (TRF)
Object in SAP NetWeaver BW to connect source objects to data targets; it allows

to consolidate, cleanse and integrate data
TRF
See Transformation (TRF).
VAN
See VIM Analytics (VAN).
Vendor Invoice Management (VIM)
Packaged business solution that solves a business problem – paying correct

amount to vendors on-time and with the lowest cost. VIM delivers not technology
but best-practice business processes. VIM provides values to customers in process
efficiency, visibility and compliance.
Vendor maintenance
Person who is responsible for creating and maintaining the vendor master
records
VIM Analytics (VAN)
VIM component that gives users a clear data report on their invoices in progress.
VIM Analytics allows to track the documents routed through SAP workflows via
VIM.
VIM Workplace
Tool for VIM super users, which allows users to display lists of their work items
that meet a selection they have entered before. Users also can display work items
of other users and of their team as a whole.
Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP ERP system.
VIM070500-05-IGD-EN-2

OpenText Vendor Invoice Management For SAP Solutions 7.5 SP5 - Installation Guide English (VIM070500-05-IGD-En-2)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Vendor Invoice Management For SAP Solutions 7.5 SP5 - Installation Guide English (VIM070500-05-IGD-En-2)

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

for SAP® Solutions

This guide describes the installation of all Vendor Invoice

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Copyright © 2016 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

1 About this document ............................................................... 11

Part 2 Vendor Invoice Management SAP ERP component

2 Preparing installation .............................................................. 15

3 Installing the OpenText package ........................................... 19

4 Verifying installation ............................................................... 39

5 Installing Single Click Entry for SAP GUI .............................. 41

6 Installing a VIM Support Package .......................................... 43

Part 3 Business Center components installation 75

9 Business Center components and packages ....................... 77

10 Summary of installation steps ............................................... 81

Part 4 KPI Dashboard installation 83

11 Installing the KPI Dashboard .................................................. 85

12 Post installation activities ...................................................... 87

Part 5 OpenText Approval Portal installation 97

13 Preparing installation .............................................................. 99

14 Installing Web Viewer/Brava! View for the Approval

15 Installing the Approval Portal ............................................... 109

16 Configuring SAP NetWeaver Portal components ............... 133

17 Applying a new patch ............................................................ 159

18 Upgrading the Approval Portal from previous versions .... 161

19 Troubleshooting .................................................................... 163

iv OpenText Vendor Invoice Management for SAP Solutions – Installation Guide

20 Supporting installation of the standalone NWAS Portal

21 Uninstalling the Approval Portal .......................................... 167

Part 6 Mobile Approval Portal installation 173

22 Introduction to the Mobile Approval Portal ......................... 175

23 Authentication for the Mobile Approval Portal ................... 179

25 Installing the Mobile Approval Portal .................................. 183

Part 7 Vendor Invoice Management ABAP CDS views

26 Preparing installation ............................................................ 187

27 Installing the OpenText package ......................................... 189

Part 8 Vendor Invoice Management SAP CRM SAP Shared

28 Preparing installation ............................................................ 193

29 Installing the OpenText package ......................................... 197

30 Post installation activities .................................................... 199

OpenText Vendor Invoice Management for SAP Solutions – Installation Guide v

31 Verifying installation ............................................................. 205

Part 9 Vendor Invoice Management SAP NetWeaver Business

32 Preparing installation ............................................................ 209

33 Installing the OpenText package ......................................... 211

34 Verifying the installation ....................................................... 215

35 Upgrading SAP NetWeaver BW ............................................ 217

Part 10 Vendor Invoice Management component for SAP

36 Preparing installation ............................................................ 221

37 Installing the OpenText package ......................................... 223

38 Verifying the installation ....................................................... 225

39 Post installation activities .................................................... 227

Part 11 Vendor Invoice Management Supplier Self Service

40 Preparing installation ............................................................ 231

41 Installation on the SAP HANA Cloud ................................... 233

Part 12 Vendor Invoice Management ARIBA Integration

42 Preparing installation ............................................................ 239

vi OpenText Vendor Invoice Management for SAP Solutions – Installation Guide

43 Installing the OpenText package ......................................... 241

44 Verifying the installation ....................................................... 243

45 Post installation activities .................................................... 245