OpenText Vendor Invoice Management For SAP Solutions 7.0 - Installation PDF

OpenText Vendor Invoice Management for
SAP Solutions
Installation Guide
This guide describes the installation of all Vendor Invoice
Management (VIM) 7.0 components: Vendor Invoice
Management SAP ERP component, optional OpenText
Approval Portal, optional Mobile Approval Portal, optional KPI
Dashboard, 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, and optional
Vendor Invoice Management input channel for Ariba Network
Integration for SAP Business Suite.
VIM070000-IGD-EN-6
OpenText Vendor Invoice Management for SAP Solutions

Installation Guide
VIM070000-IGD-EN-6
Rev.: 18. July 2014
This documentation has been created for software version 7.0.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text SA
40 Avenue Monterey , Luxembourg, Luxembourg L-2163
Tel: 35 2 264566 1
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: http://support.opentext.com
For more information, visit https://www.opentext.com
Copyright 2014 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not
exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names
mentioned herein are property of Open Text SA or other respective owners.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
Part 1
About Vendor Invoice Management
About This Document ............................................................... 9
1.1
1.2
Target Audience ............................................................................... 9

Document Overview .......................................................................... 9
Part 2
Vendor Invoice Management SAP ERP Component

Installation
Preparing Installation .............................................................. 13
2.1
2.2
2.3
2.4
General ..........................................................................................
Password Control ............................................................................
Checking Prerequisites ....................................................................
Notes on Transports ........................................................................
Installing the OpenText Package ........................................... 17
3.1
3.2
3.3
Installing the Package ..................................................................... 17

Post Installation Activities ................................................................ 17
Language Packs ............................................................................. 38
Verifying Installation ............................................................... 39
Installing a VIM Support Package .......................................... 41
5.1
5.2
5.3
SAP ERP Prerequisites ................................................................... 41

Handling Workflow Container Inconsistencies ................................... 42
SAP Installation .............................................................................. 43
11
13
14
14
16
Upgrading ................................................................................. 49
6.1
6.2
6.3
6.4
6.5
Upgrade Overview ..........................................................................

Handling Workflow Container Inconsistencies ...................................
Upgrading SAP ERP .......................................................................
Upgrading VIM ................................................................................
Post Installation Activities After an Upgrade ......................................
49
51
52
56
62
Troubleshooting ...................................................................... 67
7.1
FAQs ............................................................................................. 67
Part 3
KPI Dashboard Installation
Installing the KPI Dashboard .................................................. 71
Post Installation Activities ...................................................... 73
9.1
9.2
Activating the SAP Web Dynpro Service ........................................... 73

Setting the Connection for the SAP Web Dynpro Service ................... 78
OpenText Vendor Invoice Management for SAP Solutions Installation Guide

VIM070000-IGD-EN-6
69
iii
Table of Contents
iv
9.3
Setting Up the SAP NetWeaver Portal Integration ............................. 79
Part 4
OpenText Approval Portal Installation
83
10
Preparing Installation .............................................................. 85
10.1
10.2
10.3
Installation Prerequisites .................................................................. 85

Installation Components .................................................................. 88
System Architecture ........................................................................ 89
11
Installing the Approval Portal ................................................. 93
11.1
11.2
11.3
11.4
Preparing the Installation ................................................................. 93

Configuring the Administrator Role ................................................... 96
Deploying the Software Component Archive ................................... 101
Deploying the Software Component Archive with SAP NetWeaver
7.3 and 7.4 ................................................................................... 105
12
Configuring SAP NetWeaver Portal Components .............. 109
12.1
12.2
12.3
12.4
12.5
12.6
12.7
Creating AppIntegrator IViews for Users .........................................

Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3
and 7.4 .........................................................................................
Creating Roles for Users ...............................................................
Creating Roles for Users with SAP NetWeaver 7.3 and 7.4 ..............
Assigning Roles to SAP NetWeaver Portal Users ............................
Configuring IViews and Roles for the Administrator .........................
Administering the OpenText Approval Portal ...................................
13
Applying a New Patch ........................................................... 135
14
Upgrading the Approval Portal from Previous Versions ... 137
15
Troubleshooting .................................................................... 139
16
Supporting Installation of the Standalone NWAS Portal

and Mobile Approval Portal on Unix or Linux ..................... 141
17
Uninstalling the Approval Portal .......................................... 143
17.1
17.2
17.3
17.4
17.5
Uninstalling Using Software Deployment Manager ..........................

Uninstalling with SAP NetWeaver 7.3 and 7.4 .................................
Removing SAP NetWeaver Portal Components ..............................
Deleting Properties Files ................................................................
Optional: Removing the Startup Parameter in the Config Tool ..........
143
144
145
146
146
Part 5
Mobile Approval Portal Installation
149
18
Introduction to the Mobile Approval Portal ......................... 151
19
Authentication for the Mobile Approval Portal ................... 155
109
115
125
129
132
133
134

VIM070000-IGD-EN-6
Table of Contents
20
Installing Web Viewer for the Mobile Approval Portal ....... 157
21
Installing the Mobile Approval Portal .................................. 159
21.1
Installing the Mobile Approval Portal on Standalone NWAS

7.0/7.3/7.4 .................................................................................... 159
Installing the Mobile Approval Portal on SAP NetWeaver Portal
7.0/7.3/7.4 .................................................................................... 159
21.2
Part 6
Vendor Invoice Management SAP CRM SAP Shared

Service Framework Component Installation
161
22
Preparing Installation ............................................................ 163
22.1
22.2
Password Control .......................................................................... 163

Checking Prerequisites .................................................................. 163
23
Installing the OpenText Package ......................................... 167
24
Post Installation Activities .................................................... 169
24.1
24.2
24.3
Activating Business Configuration Sets in the CRM System ............. 169

Maintaining a Logical System for the CRM System in VIM ............... 173
Installing Support Packages 1 and 2 ............................................... 173
25
Verifying Installation ............................................................. 175
Part 7
Vendor Invoice Management SAP NetWeaver Business

Warehouse Component Installation
177
26
26.1
26.2

27
28
Verifying the Installation ....................................................... 185
29
Upgrading SAP NetWeaver BW ............................................ 187
Part 8
Vendor Invoice Management SAP NetWeaver Gateway

Component Installation
189
30
30.1
30.2

31
32

VIM070000-IGD-EN-6
Table of Contents
vi
Part 9
Vendor Invoice Management Supplier Self Service

33
33.1
33.2
33.3
Installation Prerequisites ................................................................ 199

Installation Components ................................................................ 200
System Architecture ...................................................................... 200
34
Installation on the SAP HANA Cloud ................................... 201
34.1
34.2
34.3
Preparing the Installation ............................................................... 201

Deploying the Application on the SAP HANA Cloud Server .............. 201
Installing the SAP HANA Cloud Connector ...................................... 202
Part 10
Vendor Invoice Management Input Channel for Ariba

Network Integration for SAP Business Suite Installation
197
205
35
35.1
35.2

36
37
Post Installation Activities .................................................... 211
37.1
Activating Business Configuration Sets for the OTVIMARB

Component ................................................................................... 211
38
GLS
Glossary
215

VIM070000-IGD-EN-6
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 in the OpenText Knowledge Center: https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605. The latest versions
of the documentation are also available in the Knowledge Center: https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/10151494.
For SAP Invoice Management by OpenText customers: To obtain access to the
Knowledge Center, 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.

VIM070000-IGD-EN-6
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 7
Vendor Invoice Management SAP ERP Component Installation on page 11
KPI Dashboard Installation on page 69
OpenText Approval Portal Installation on page 83
Mobile Approval Portal Installation on page 149
Vendor Invoice Management SAP CRM SAP Shared Service Framework

Component Installation on page 161
Vendor Invoice Management SAP NetWeaver Business Warehouse Component

Installation on page 177
Vendor Invoice Management SAP NetWeaver Gateway Component

Installation on page 189
Vendor Invoice Management Supplier Self Service Component Installation

on page 197
Vendor Invoice Management Input Channel for Ariba Network Integration for
SAP Business Suite Installation on page 205

VIM070000-IGD-EN-6
Part 2
Vendor Invoice Management SAP ERP
Part 2 Vendor Invoice Management SAP ERP

This part describes the installation of the SAP ERP component of Vendor Invoice
Management (VIM).
12

VIM070000-IGD-EN-6
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 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
Center
If you require additional help with technical problems, contact

OpenText Customer Support. You can find the contact
information for your region at http://www.opentext.com/services/
support.html.
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
icon. It is very important that, in the
configured correctly, indicated by the
Maintain Runtime Environment node, Configure RFC destination has the
icon.
Note: Check for and download the available latest support packs and hot fixes
at the OpenText Knowledge Center: https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/10151605.

VIM070000-IGD-EN-6
13
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 ECC 6.0
VIM installation
E067B86AE9
SAP ERP upgrade
E067B86CFE
VIM upgrade
E067B86AEE
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:
2.3.2
In-depth knowledge of SAP administration tasks, in particular the SAP Add-On

Installation Tool (SAINT)
Basic knowledge of the employed operating system
SAP ERP Prerequisites

Check the following prerequisites prior to installation:
SAP ECC 6.0
Support Package Manager (transaction code SPAM) level 35
Apply OSS note 1082597: Not enough business functions activated in SFW5; this is
used for Switch Frame Work for activating the PO based invoice parking
infrastructure.
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 ECC 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 1791715: SAP Invoice
Management by OpenText 7.0
The following components must be installed for SAP ECC 6.0 up to EHP7:
14

VIM070000-IGD-EN-6
2.3. Checking Prerequisites
Option
2.3.3
Component: SAP_BASIS
Release
Level
Support package
700
0013
SAPKB70013
701
0003
SAPKB70103
702
0003
SAPKB70203
higher
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.

VIM070000-IGD-EN-6
15
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.
16

VIM070000-IGD-EN-6
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 13 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.
2.
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 ECC 6.0
OTEXVIM_INST_700_70
0.SAR
INST_ERP\DATA\
\usr\sap\trans
\EPS
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.
Carry out the import of the package as described in the respective SAP
documentation.
4.
To finish installation, install the most recent VIM 7.0 Support Package (SP). You
find the SPs in the Knowledge Center: https://knowledge.opentext.com/
knowledge/cs.dll/Open/10151605. For further information, see the Release Notes
of the respective SP.
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 18
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

VIM070000-IGD-EN-6
17
Chapter 3 Installing the OpenText Package
3.2.1
Linking Events for VIM Workflows on page 30
Maintaining the SAPscript Form for Approval on page 33
Maintaining Standard Text on page 34
Setting Background User Parameters for Non PO Invoice Posting on page 36
Configuring Additional Settings on page 37
Installing Transports with Layout Variants for Integrated Invoice Cockpit and
IDH Admin Tool on page 38
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.0.
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.
You activate the BC Sets in the following steps:

1. Apply recommended user settings
2. Activate BC Set /OTEXVIM/VIM70_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.
Dont 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 apply recommended user settings:
1.
To access the Business Configuration Sets: Activation screen, run the SCPR20
transaction.
From the Utilities menu, click User Settings.
18

VIM070000-IGD-EN-6
3.2. Post Installation Activities
VIM 7.0 supports the following languages:
Chinese
Dutch
English
French
German
Hungarian
Italian
Japanese
Portuguese
Romanian
Russian
Spanish

VIM070000-IGD-EN-6
19
New languages for VIM 7.0 are the following:
Czech
Polish
Turkish
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:
1.
20
transaction.

VIM070000-IGD-EN-6
2.
Enter the BC set name /OTEXVIM/VIM70_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.
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/VIM70_BASELINE_LEGACY,

continue and activate BC set /OTEXVIM/VIM70_BASELINE_NEWFOR70.

VIM070000-IGD-EN-6
21
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
DP WF
00275278
PO Parked
00275262
PO Blocked Line level
00275265
PO Blocked Header
00275267
NPO parked
00275260
IAP
00275253
Referee workitem
00275283
To configure a General Task:
22
1.
Run the PFTC transaction.
2.
In the Task type field, select Standard task, enter the task ID and click the
button.

VIM070000-IGD-EN-6
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.

VIM070000-IGD-EN-6
23
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.
3.2.3
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.
Refreshing SAP Workflow Runtime Buffer

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

VIM070000-IGD-EN-6
2.
3.2.4
To refresh the runtime buffer, click the Start Synchronization button.
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.

VIM070000-IGD-EN-6
25
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.
26

VIM070000-IGD-EN-6
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.
3.2.5
Follow your standard change request process for tracking changes.
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.

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

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

VIM070000-IGD-EN-6
29
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.
With VIM 6.0 and higher, event linkages are no longer created 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
FIPP
FIPP
BUS2081
30
Event
Receiver function module
Receiver type
Check function module
DELETED
SWW_WI_CREATE_VIA_EVENT
TS00275270
POSTED
TS00275270
DELETED
TS00275270
Usage
comments
Invoice
Approval (IAP)
IAP
IAP

VIM070000-IGD-EN-6
Object type
BUS2081
BUS2081
BUS2081
/OPT/FIPP
Event
Receiver function module
Receiver type
Check function module
POSTED
TS00275270
POSTED
/OPT/BL_PO_BLK_RECEIVER
WS00275264
/OPT/BL_PO_CHECK_ROLL_OUT
POSTED
/OPT/BL_PO_BLK_RECEIVER
TS00275264
/OPT/BL_PO_CHECK_ROLL_OUT
ZWFI_CREATE
D
/OPT/BL_NPO_PRK_RECEIVER
WS00275254
/OPT/B2081 ZWFI_PARKED
FIPP
FIPP
BUS2081
BUS2081
BUS2081
BUS2081
Usage
comments
IAP
Invoice
Exception (IE)
IE
IE
/PTGWFI/PIR_F_CHECKFM
/OPT/BL_PO_PRK_RECEIVER
IE
WS00275260
/PTGWFI/PRK_M_CHECKFM
DELETED
/OPT/VIM_RPT_RECEIVER_FM
POSTED
/OPT/VIM_RPT_RECEIVER_FM
DELETED
/OPT/VIM_RPT_PO_INV_RECEIVER
POSTED
VAN
May be used in
special
situation.
Should be
inactive in
standard
configuration.
RELEASED
VAN
CANCELLED
/ORS/INVAP POSTED
/OPT/AAFS_POST_RECEIVER

VIM070000-IGD-EN-6
VIM Analytics
(VAN)
VAN
VAN
VAN
Posted
Approval
31
Note: There is a dependency between two entries for Object Type BUS2081 and
Event POSTED, the one with Receiver Type WS00275264, and the one with an
empty Receiver Type.
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 WS00275264. 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.
32

VIM070000-IGD-EN-6
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.
3.
On the Utilities menu, click Copy from Client.

VIM070000-IGD-EN-6
33
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.
3.2.8
Maintaining Standard Text

This activity is only required if the SRM PO functionality is being implemented in
VIM.
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_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.
34
Run the SO10 transaction.

VIM070000-IGD-EN-6
2.
Navigate to the menu path Utilities > Copy from Client.
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.

VIM070000-IGD-EN-6
35
Click
3.2.9
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.
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 WFBATCH.
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
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.
36

VIM070000-IGD-EN-6
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 ECC 6.0 version), see section 9.9.4 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.5.1
Activating BAdI for Invoice Processing in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide (VIM-CGD).
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
/OPT/
VIM_ENH_SPOT_MIRO
/OPT/
CL_IM_VIM_BADI_MIRO
Implementation is not
called

VIM070000-IGD-EN-6
37
3.2.11
Installing Transports with Layout Variants for Integrated

Invoice Cockpit and IDH Admin Tool
The layouts provided in the baseline for the Integrated Invoice Cockpit and the IDH
Admin Tool are stored in the table LTDX. 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 transports D89K901617 and QW3K900246 into the transport
directory and install the transports using STMS.
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 7.0 (other than English and German) are delivered in language
packs, which you can obtain on the OpenText Knowledge Center: https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605.
Cumulative
language pack
Beginning with VIM 7.0 SP2, VIM provides a cumulative language pack with every
SP. You need this language pack, if you did not install the initial language pack of
the VIM version along with the installation package. You can obtain the cumulative
language pack in the Knowledge Center in the folder of the respective SP.
You can import the cumulative language pack after the respective SP is installed.
The initial language pack of the VIM version is not required. To import the language
pack, use the SMLT transaction. You can import the language pack multiple times for
several languages.
Translation
Guide
38
VIM provides a translation guide that describes the various aspects of translating
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
Language and Language Supplementation instead of translating into a new
language. The translation guide is available in the Knowledge Center: https://
knowledge.opentext.com/knowledge/llisapi.dll/Properties/46423475

VIM070000-IGD-EN-6
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.

VIM070000-IGD-EN-6
39
Chapter 4 Verifying Installation
In the System: Component information dialog, you should see the OTEXVIM
add-on component installed, with Release number 700.
40

VIM070000-IGD-EN-6
Chapter 5
Installing a VIM Support Package

This chapter describes the installation of a Support Package (SP) for VIM.
5.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:
1.
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.

VIM070000-IGD-EN-6
41
Chapter 5 Installing a VIM Support Package
5.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.
42

VIM070000-IGD-EN-6
5.3. SAP Installation
5.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.

VIM070000-IGD-EN-6
43
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.
44

VIM070000-IGD-EN-6
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

VIM070000-IGD-EN-6
45
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 (ECC 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 45), 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.
46

VIM070000-IGD-EN-6
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.

VIM070000-IGD-EN-6
47
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.
48

VIM070000-IGD-EN-6
Chapter 6
Upgrading
This chapter describes the upgrade procedure for both SAP ERP upgrade and VIM
upgrade.
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.
6.1 Upgrade Overview

An upgrade from VIM versions since 5.1.6 to VIM 7.0 is possible directly or in two
steps using a VIM 6.0 version as intermediate version.
The following tables show the details.
Table 6-1: VIM upgrades for SAP version ERP 6.0
VIM source version
Recommended
start level
VIM 5.1.6 installed, but

not productive (or data to
be discarded)
Upgrade Guide
Installation Guide VIM 7.0, Upgrading
VIM on page 56.
You must use the upgrade package, and
you must follow the post installation
activities for installation.
VIM 5.2
VIM 5.2 SP6

VIM on page 56
VIM 6.0
VIM 6.0 SP1

VIM on page 56
Table 6-2: Exchange upgrades for other SAP versions

Source version
Recommended
start level
Upgrade Guide
VIM 6.0 / 4.6C
VIM 6.0 SP1

SAP ERP on page 52
VIM 6.0 / 4.7
VIM 6.0 SP1

SAP ERP on page 52
VIM 6.0 / ERP 5.0
VIM 6.0 SP1

SAP ERP on page 52

VIM070000-IGD-EN-6
49
Chapter 6 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 6-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:
VIM upgrade from 6.0 SP1
to 7.0
Installation Guide VIM 7.0,

Upgrading VIM on page 56
Table 6-4: Exchange upgrades in 2 steps for other SAP versions

Source version
Intermediate step
Upgrade Guide
VIM 5.1.6 / 4.6C

21388817)
VIM 5.1.6 / 4.7

21388817)
VIM 5.1.6 / ERP 5.0

21388817)
VIM 5.2 / 4.6C
VIM 6.0 SP1 Release Notes (https://

knowledge.opentext.com/
19224213)
VIM 5.2 / 4.7

19224213)
VIM 5.2 / ERP 5.0

19224213)
Second step in all cases:

Exchange upgrade from
VIM 6.0 SP1
50
Installation Guide VIM 7.0,

Upgrading SAP ERP
on page 52

VIM070000-IGD-EN-6
6.2. Handling Workflow Container Inconsistencies
6.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 document FAQ on Upgrade
to 7.0, available in the Knowledge Center: https://knowledge.opentext.com/
knowledge/cs.dll/Properties/38482369
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.
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.

VIM070000-IGD-EN-6
51
Chapter 6 Upgrading
6.3 Upgrading SAP ERP

This section discusses the process to perform during an SAP ERP upgrade with
regards to VIM.
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
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 14.
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.
Apply OSS note 1082597: Not enough business functions activated in SFW5; this is
used for Switch Frame Work for activating the PO based invoice parking
infrastructure.
Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s AS

ABAP
Option
52
Release
Level
Support package
700
0013
SAPKB70013
701
0003
SAPKB70103
702
0003
SAPKB70203
higher
One of the following add-on components must be installed:
OTEXVIM 604_700
OTEXVIM 603_640
OTEXVIM 602_620

VIM070000-IGD-EN-6
6.3. Upgrading SAP ERP
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:

1.
2.
application server in the \usr\sap\trans folder. This is the parent folder of the
DIR_EPS_ROOT folder.
Upgrade to ECC
6.0 from SAP
version
File
Source path
SAP ECC 5.0

SAP R/3 4.7
SAP R/3 4.6C
OTEXVIM_EXCH UPGR_ERP/DATA/
_700_700.SAR
Target path
\usr\sap\trans
\EPS

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.

VIM070000-IGD-EN-6
53
Chapter 6 Upgrading
5.
To include the OTEXVIM exchange package, select Upgrade with SAINT package.
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 18. 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.
54

VIM070000-IGD-EN-6
6.3. Upgrading SAP ERP
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.
If the two objects are green (see screenshot above), they are active and
generated. This is okay and can be ignored.

VIM070000-IGD-EN-6
55
Chapter 6 Upgrading
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.
3.
When you have successfully completed all tests, inform the OpenText Project
Manager.
With this information, we can keep our customer installation database up-todate, which helps us providing faster technical support for you.
6.4 Upgrading VIM

This section discusses the process to perform an upgrade from VIM 5.2 to VIM 7.0
and from VIM 6.0 to VIM 7.0.
Password
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 14.
Prerequisites
General prerequisites
Apply OSS note 1082597: Not enough business functions activated in SFW5;
this is used for Switch Frame Work for activating the PO based invoice
parking infrastructure.
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 ECC 6.0 system, up to
EHP5.
For a list of available software components, check OSS note 1791715: SAP
Invoice Management by OpenText 7.0
The following components must be installed:
ECC 6.0
Component SAP_BASIS
Level: 700
56

VIM070000-IGD-EN-6
6.4. Upgrading VIM
Option
Release
Level
Support package
700
0013
SAPKB70013
701
0003
SAPKB70103
702
0003
SAPKB70203
higher
The following add-on component must be installed:

OTEXVIM 520_700 or OTEXVIM 604_700
VIM version
Upgrade to VIM 7.0 is supported with minimal versions of VIM 5.2 SP6 or VIM
6.0 SP1. 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.0.
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.

VIM070000-IGD-EN-6
57
Chapter 6 Upgrading
Adjust SAINT tool settings

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

VIM070000-IGD-EN-6
6.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:
4.
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.
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.
1.
application server in the \usr\sap\trans folder. This is the parent folder of the
DIR_EPS_ROOT folder.

VIM070000-IGD-EN-6
59
Chapter 6 Upgrading
2.
SAP ERP system
File
Source path
SAP ECC 6.0
OTEXVIM_UPGR UPGR_VIM/DATA/
_700_700.SAR
Target path
\usr\sap\trans
\EPS

SAPCAR file.
3.
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 14.
60

VIM070000-IGD-EN-6
6.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 and German, install the
language packs for the languages you need. For more information, see
Language Packs on page 38.

VIM070000-IGD-EN-6
61
Chapter 6 Upgrading
2.
Install the most recent VIM 7.0 Support Package (SP). You find the SPs in the
Knowledge Center: 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 62.
Important
Do not activate the BC Sets for first installation, as described in
Activating Business Configuration Sets on page 18. 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.
5.
When you have successfully completed all tests, inform the OpenText Project
Manager.
With this information, we can keep our customer installation database up-todate, which helps us providing faster technical support for you.
6.5 Post Installation Activities After an Upgrade

To ensure the integrity of the installed transports, you must perform and validate
the following procedures:
62
Activating Business Configuration Sets on page 63
Maintaining Number Ranges After Upgrade on page 63
Checking the BTE Handler Modules Configuration on page 63
Checking Status and Runtime Behavior of BAdIs for Invoice Processing

on page 64
Installing Transport with Layout Variant for IDH Admin Tool on page 64
Populating Invoice Transaction Field VORGANG for Credit Memos

on page 65
Removing Obsolete User Process Option 2742 on page 65

VIM070000-IGD-EN-6
6.5. Post Installation Activities After an Upgrade
6.5.1
Activating Business Configuration Sets

Note: Check the tables in /OTEXVIM/VIM70_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:
/OTEXVIM/VIM70_BASELINE_52_60_D
Activate this BC Set if your source system for the upgrade is VIM 5.2. If you get
an activation error, ignore it.
/OTEXVIM/VIM70_BASELINE_LOWSP_D
Activate this BC Set if your source system for the upgrade is lower than VIM 5.2
SP8 or VIM 6.0 SP3 respectively. If you get an activation error, ignore it.
/OTEXVIM/VIM70_BASELINE_NEWFOR70
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>.
6.5.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.
6.5.3
Checking the BTE Handler Modules Configuration

In VIM 7.0, 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.

VIM070000-IGD-EN-6
63
Chapter 6 Upgrading
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.
6.5.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
/OPT/VIM_MIRO_ENH
/OPT/VIM_CHECK_MIRO
/OPT/
VIM_ENH_SPOT_MIRO
/OPT/CL_IM_VIM_BADI_MIRO
Implementation is not
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).
6.5.5
Installing Transport with Layout Variant for IDH Admin

Tool
The layout provided in the baseline for the IDH Admin Tool is stored in table LTDX.
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 QW3K900246 into
the transport directory and install the transport using STMS.
OpenText recommends setting the layout /IDH as default layout for the IDH Admin
Tool (transaction /OPT/VIM_7AX8; report /OPT/VIM_ICC_ADMIN_TOOL).
64

VIM070000-IGD-EN-6
6.5. Post Installation Activities After an Upgrade
6.5.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, 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.
6.5.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.
To do this, run the program /OPT/VIM_PURGE_PROCESS_OPTIONS.

VIM070000-IGD-EN-6
65
Chapter 7
Troubleshooting
7.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.

VIM070000-IGD-EN-6
67
Part 3
KPI Dashboard Installation
Part 3 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 25 KPI Dashboard in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
Notes
70
The KPI Dashboard is an optional component.
If you are not using the KPI Dashboard, you can skip this part.

VIM070000-IGD-EN-6
Chapter 8
Installing the KPI Dashboard

The KPI Dashboard is installed together with the VIM Basis package.

VIM070000-IGD-EN-6
71
Chapter 9
Post Installation Activities

The following activities are needed to configure the KPI Dashboard on your system.
9.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.

VIM070000-IGD-EN-6
73
Chapter 9 Post Installation Activities
To activate the service:
74
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.

VIM070000-IGD-EN-6
9.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 76.

VIM070000-IGD-EN-6
75
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:
76

VIM070000-IGD-EN-6
9.1. Activating the SAP Web Dynpro Service
Logon Errors
Application Errors
Logoff Page
Not Accessible

VIM070000-IGD-EN-6
77
9.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_nw04s/helpdata/en/65/
6a563cef658a06e10000000a11405a/frameset.htm
Do not change the service settings described in Activating the SAP Web Dynpro
Service on page 73. Make sure that the SSL settings are not activated in the Logon
Data tab.
78

VIM070000-IGD-EN-6
9.3. Setting Up the SAP NetWeaver Portal Integration
Change the KPI constant DASHBOARD_START_URL to https://xxxxx:8443/xxxx. See

section 25.4.10.5 KPI Dashboard Start URL in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide (VIM-CGD).
9.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.
9.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.

VIM070000-IGD-EN-6
79
4.
ITS settings
ITS settings are maintained for displaying SAP transactions in the portal as an
iView.
Category drop down list, select Internet Transaction Server (ITS).
Provide ITS properties as shown in the following screenshot.
80

VIM070000-IGD-EN-6
9.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.
9.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.
Category drop down list, select Content - Web Dynpro.
Provide properties as shown in the following screenshot.

VIM070000-IGD-EN-6
81
Check also other properties for design or layout, and customize them if needed.
4.
82
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.

VIM070000-IGD-EN-6
Part 4
OpenText Approval Portal Installation
Part 4 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 or 7.3 or SAP NetWeaver Portal (NWP) 7.0 or 7.3.
With VIM 7.0 SP4 and higher, NWAS 7.4 and NWP 7.4 are also supported.
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
84
The Approval Portal is an optional component.
If you are not using the Approval Portal, you can skip this part.
Please refer to section 12 Administering the Approval Portal in OpenText

Vendor Invoice Management for SAP Solutions - Administration Guide (VIMAGD) 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.

VIM070000-IGD-EN-6
Chapter 10
10.1 Installation Prerequisites
A complete installation and configuration of OpenText Vendor Invoice Management
for SAP Solutions 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. For SPNego configuration,
see SAP Note 1488409.
With VIM 7.0 SP4 and higher, NWAS 7.4 SP3 or above is also supported.
SAP NetWeaver Portal
SAP NetWeaver Portal (NWP) 7.0 SP9 or above and NWP 7.3 SP3 or above.
With VIM 7.0 SP4 and higher, NWP 7.4 SP3 or above is also supported.
Notes
Recommended
Screen
Resolution
The requirement SPx or above does also refer to the EhP level.
For further information, see the SAP Note: 994791-SPNego Wizard.
The following list shows the supported resolution modes that have been tested in
the OpenText R&D lab. The resolution modes have been tested in all supported
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.
Note: The old interface of the Approval Portal supports only Internet Explorer
7.0, 8.0, and 9.0.

VIM070000-IGD-EN-6
85
With VIM 7.0 SP4 and above, the old interface of the Approval Portal also
supports Internet Explorer 10.0 and 11.0.
Server
Browser and Version

IE9
IE10
Firefox > 17
Chrome > 22
Safari > 5.0
NWAS 7.0
NWAS 7.3
NWAS 7.4
(with VIM 7.0
SP4)
NWP 7.0
NWP 7.3
NWP 7.4 (with
VIM 7.0 SP4)
Operating
systems
The Approval Portal supports Windows, Unix and other operating 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
Sizing requirements
SAP user
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.
Standard sizing requirements for NWAS or NWP 7.0 apply.
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:
86

VIM070000-IGD-EN-6
10.1. Installation Prerequisites
Object: S_RFC
Activity
Execute (16)
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.

VIM070000-IGD-EN-6
87
Example: OpenText Archive Server provides the following profiles that need to be
assigned to the CPIC user to access images:
S_AL_ADMLO (Display SAP ArchiveLink administrator)
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
10.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.0 SPx installation packages for old and new interface
For all Support Packages of VIM 7.0 (SP2 and higher), the respective OpenText
Vendor Invoice Management 7.0 Support Package folder in the Knowledge
Center (accessible via https://knowledge.opentext.com/knowledge/cs.dll/Open/
32893475) provides two installation packages of the VIM 7.0 SPx Approval
Portal in the Web and Mobile Approval Component folder: one for the new
user interface (which is introduced with VIM 7.0 SP2), and one for the old user
interface.
88

VIM070000-IGD-EN-6
10.3. System Architecture
10.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
as an application inside NWP using AppIntegrator iView
The following diagrams show the architecture for each scenario:

VIM070000-IGD-EN-6
89
Figure 10-1: Approval Portal architecture with NWAS

The SAP help pages linked in the following discuss some of the communication
channels between each component:
90
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)

VIM070000-IGD-EN-6
10.3. System Architecture
Figure 10-2: Approval Portal architecture with NWP
10.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.

VIM070000-IGD-EN-6
91
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.
92

VIM070000-IGD-EN-6
Chapter 11
Installing the Approval Portal

11.1 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 94 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
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 12.3.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
Lang_EN.properties
containing all the text for the English language resource

VIM070000-IGD-EN-6
93
Chapter 11 Installing the Approval Portal
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 12.3.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:
2.
correct permissions for the J2EE application to write and read
Full Control permission to the J2EE Engine service user (or to

Everyone)
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.
94

VIM070000-IGD-EN-6
11.1. Preparing the Installation
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_installd
ir>.
Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/
opentext/invoiceCfg
b.
3.
Save the new parameter.
To apply the new startup parameter, restart the NWAS.

Restarting informs the server that the <Approval_Portal_installdir> folder
contains application specific information.

VIM070000-IGD-EN-6
95
11.2 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 12 Administering the Approval Portal in
OpenText Vendor Invoice Management for SAP Solutions - Administration Guide (VIMAGD) for additional information.
11.2.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 99.
You must perform this configuration before deploying the .sca or .sda, to ensure
that the application recognizes the role.
To create the Administrator role:
96
1.
Log in to J2EE Visual Administrator and navigate to Instance > Server >
Services > Security Provider.
2.
Click on the Edit button.

VIM070000-IGD-EN-6
11.2. Configuring the Administrator Role
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.

VIM070000-IGD-EN-6
97
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 101.
98
Navigate to http://<NWAS>:<NWASPORT>/vimportal/admin.

VIM070000-IGD-EN-6
11.2. Configuring the Administrator Role
If you see a screen similar to the one above, you have configured the
administrator role successfully.
11.2.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

VIM070000-IGD-EN-6
99
100
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.

VIM070000-IGD-EN-6
11.3. Deploying the Software Component Archive
11.3 Deploying the Software Component Archive

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

NetWeaver 7.0 on page 101
Deploying the .sca File or .sda File on page 102
Checking Correct Deployment on page 103
Optional: Starting the Approval Portal J2EE Application Manually

on page 105
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

VIM070000-IGD-EN-6
101
11.3.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 143 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 (

deployment list.
) to add the .sca or .sda file to the
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.
102
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.

VIM070000-IGD-EN-6
11.3. Deploying the Software Component Archive
9.
11.3.3
In step 4 of 4 of deployment, click Confirm to continue and finish deployment.
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.

VIM070000-IGD-EN-6
103
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.
b.
c.
Click on a server.
Expand Services.
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.
104

VIM070000-IGD-EN-6
11.4. Deploying the Software Component Archive with SAP NetWeaver 7.3 and 7.4
11.3.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 104.
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.
11.4 Deploying the Software Component Archive with

SAP NetWeaver 7.3 and 7.4
To deploy the Software Component Archive with SAP NetWeaver 7.3 and 7.4:
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:
3.
go.bat for Windows hosts
go.sh for Unix hosts
Enter user name and password.

VIM070000-IGD-EN-6
105
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.
106

VIM070000-IGD-EN-6
11.4. Deploying the Software Component Archive with SAP NetWeaver 7.3 and 7.4
5.
Click Start.

VIM070000-IGD-EN-6
107
6.
108
In the Completed screen, click Exit.

VIM070000-IGD-EN-6
Chapter 12
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 and 7.4, see
Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4
on page 115 and Creating Roles for Users with SAP NetWeaver 7.3 and 7.4
on page 129.
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 109
on page 115
Creating Roles for Users on page 125
Creating Roles for Users with SAP NetWeaver 7.3 and 7.4 on page 129
Assigning Roles to SAP NetWeaver Portal Users on page 132
Configuring IViews and Roles for the Administrator on page 133
Administering the OpenText Approval Portal on page 134
12.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.

VIM070000-IGD-EN-6
109
Chapter 12 Configuring SAP NetWeaver Portal Components
3.
110
Right-click on the new folder and select New > iView.

VIM070000-IGD-EN-6
12.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.

VIM070000-IGD-EN-6
111
112
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

VIM070000-IGD-EN-6
12.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.

VIM070000-IGD-EN-6
113
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:
114

VIM070000-IGD-EN-6
12.2. Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4
$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.
12.2 Creating AppIntegrator IViews for Users with

SAP NetWeaver 7.3 and 7.4
Consult your corporate policy on the location and the naming conventions of
creating iViews.
To create AppIntegrator iViews for users with NetWeaver 7.3 and 7.4:
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.

VIM070000-IGD-EN-6
115
3.
116
Right-click End User Content, point to New, and then click Folder.

VIM070000-IGD-EN-6
4.
5.
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.
After creating the Approval Portal folder, navigate to Content Administration

> Portal Content Management > Portal Content > Portal Applications

VIM070000-IGD-EN-6
117
6.
118
In Portal Applications, expand com.sap.portal.appintegrator.sap

VIM070000-IGD-EN-6
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
following screenshot.

VIM070000-IGD-EN-6
119
The wizard of the PCD Object opens.
120

VIM070000-IGD-EN-6
10. Change the Object Name to Approval Portal Iview.

Click Next, then click Finish.
An iView is created.

VIM070000-IGD-EN-6
121
11. To configure the newly created iView, right-click ApprovalPortalIview, then

click Open > Properties.
122

VIM070000-IGD-EN-6
12. On the Approval Portal Iview tab, click All.
13. From the Show Category list, select Content - Generic Launcher.

VIM070000-IGD-EN-6
123
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. From the Show Category list, select Navigation.
To make the iView visible, select the Entry Point check box.
124

VIM070000-IGD-EN-6
12.3. Creating Roles for Users
12.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 109.
2.
Right-click on the folder, select New > Role.

VIM070000-IGD-EN-6
125
3.
In Step 1, enter Role Name, Role ID, Role ID Prefix and Description.
Select the Master Language.
Notes
4.
126
See also Step 7 on page 112 in Creating AppIntegrator IViews for

Users on page 109.
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.
Click Next.

VIM070000-IGD-EN-6
12.3. Creating Roles for Users
5.
Click Finish.
6.
Click Open the object for editing and click OK.

VIM070000-IGD-EN-6
127
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 109, right-click the iView and select Add iView to Role > Delta
Link.
Click Save.
The AppIntegrator iView is added to the role.
9.
128
Click Close.

VIM070000-IGD-EN-6
12.4. Creating Roles for Users with SAP NetWeaver 7.3 and 7.4
12.4 Creating Roles for Users with SAP NetWeaver 7.3

and 7.4
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 and 7.4:
1.
In the SAP NetWeaver Portal, navigate to the Approval Portal folder; see
on page 115.
2.
Right-click on the folder, select New > Role > Freestyle Role.

VIM070000-IGD-EN-6
129
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.
130
Click Finish.

VIM070000-IGD-EN-6
12.4. Creating Roles for Users with SAP NetWeaver 7.3 and 7.4
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.

VIM070000-IGD-EN-6
131
7.
Select the AppIntegrator iView created in Creating AppIntegrator IViews for

Users with SAP NetWeaver 7.3 and 7.4 on page 115, right-click the iView and
select Add iView to Role > Delta Link.
Click Save.
The AppIntegrator iView is added to the role.
8.
Click Close.
12.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 125).
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.
132

VIM070000-IGD-EN-6
12.6. Configuring IViews and Roles for the Administrator
12.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 114 for details on the URL template for users.

VIM070000-IGD-EN-6
133
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 132.
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.
12.7 Administering the OpenText Approval Portal

For information on the administration of the Approval Portal, see section 12
Administering the Approval Portal in OpenText Vendor Invoice Management for SAP
Solutions - Administration Guide (VIM-AGD).
134

VIM070000-IGD-EN-6
Chapter 13
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.0 will only work with the
VIM 7.0 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 143, and then follow the steps to
deploy the .sca file or .sda file in Deploying the .sca File or .sda File
on page 102.
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 12 Administering the Approval Portal in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for more details.

VIM070000-IGD-EN-6
135
Chapter 14
Upgrading the Approval Portal from Previous

Versions
You can upgrade the Approval Portal from version 5.2 to 7.0 and from version 6.0 to
7.0.
Approval Portal 7.0 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.0 installation directory.
Make sure that all files mentioned in opentext.zip are deployed correctly.
You can reuse the original configuration.xml file as there are no changes; but it is
best to make a backup of the configuration.xml.
If you changed the language properties files from the previous version and would
like to reuse them in VIM 7.0, change the new language properties files manually.
To upgrade, perform the actions described in Applying a New Patch on page 135.

VIM070000-IGD-EN-6
137
Chapter 15
Troubleshooting
For information on troubleshooting the Approval Portal, see section 29.11
Troubleshooting in OpenText Vendor Invoice Management for SAP Solutions Administration Guide (VIM-AGD).

VIM070000-IGD-EN-6
139
Chapter 16
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 (VIMCGD).
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.

VIM070000-IGD-EN-6
141
Chapter 17
Uninstalling the Approval Portal

To uninstall the Approval Portal, perform the following steps:
Uninstalling Using Software Deployment Manager on page 143
Uninstalling with SAP NetWeaver 7.3 and 7.4 on page 144
Removing SAP NetWeaver Portal Components on page 145
Deleting Properties Files on page 146
Optional: Removing the Startup Parameter in the Config Tool on page 146
17.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 and 7.4, see Uninstalling with SAP NetWeaver 7.3 and
7.4 on page 144.
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.

VIM070000-IGD-EN-6
143
Chapter 17 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.
17.2 Uninstalling with SAP NetWeaver 7.3 and 7.4

This section describes how to undeploy the Approval Portal with SAP NetWeaver
7.3 and 7.4.
To undeploy the Approval Portal with SAP NetWeaver 7.3 and 7.4:
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.
144

VIM070000-IGD-EN-6
17.3. Removing SAP NetWeaver Portal Components
17.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 109.

VIM070000-IGD-EN-6
145
Chapter 17 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.
17.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 93 for details on the properties files.
17.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 94 in Preparing the Installation
on page 93.
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:
146

VIM070000-IGD-EN-6
17.5. Optional: Removing the Startup Parameter in the Config Tool
2.
configtool.bat for Windows hosts
configtool.sh for Unix hosts
Remove the startup parameter:

-Dcom.opentext.vim.portal.invoiceCfg=<Approval_Portal_installdir>.
Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/
opentext/invoiceCfg
3.
Save your settings.
4.
Restart the NWAS to remove the startup parameter.
The uninstallation is now completed.

VIM070000-IGD-EN-6
147
Part 5
Mobile Approval Portal Installation
Part 5 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 13
Configuring the Mobile Approval Portal in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD).
150

VIM070000-IGD-EN-6
Chapter 18
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 in VIM 7.0 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
systems
The Mobile Approval Portal supports Windows, Unix and other operating 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:
VIM 7.0 adds the new column Category which 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
System
Device
Browser
Category
iOS (5.1.x or higher)
iPad
Safari (5.1.x or higher)
iOS (5.1.x or higher)
iPhone
Safari (5.1.x or higher)
BlackBerry (BB OS 10)
BlackBerry
BlackBerry OS 10
browser
Android (4.0.x or
higher)
Any Android device[a]
Chrome (23.0 or higher) B

and Supported
browsers
WindowsPhone (8 or
higher)
Any WindowsPhone
device
Internet Explorer
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.

VIM070000-IGD-EN-6
151
Chapter 18 Introduction to the Mobile Approval Portal
Web Viewer
integration
Mobile Approval Portal users can display invoices using OpenText Imaging Web
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 Server 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
152
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).

VIM070000-IGD-EN-6
Figure 18-1: HTML5 Mobile Approval Portal Architecture

VIM070000-IGD-EN-6
153
Chapter 19
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 85

VIM070000-IGD-EN-6
155
Chapter 20
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:
OTEXBAS 10.0 SP2
OpenText Imaging Web Viewer 10.2.0 Patch-004 (Patch = WEV-1020-004) or

higher.
Note: OpenText Imaging Web Viewer 10.2.0 SP1 = Patch-005,
WEV-1020-005
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 OpenText 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 patch 004 (or higher) 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 or 7.4

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.

VIM070000-IGD-EN-6
157
Chapter 20 Installing Web Viewer for the Mobile Approval Portal
158
OpenText also recommends installing Web Viewer on the same domain as

the Archive Server and SAP NetWeaver Application Server Java.

VIM070000-IGD-EN-6
Chapter 21
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)
21.1 Installing the Mobile Approval Portal on

Standalone NWAS 7.0/7.3/7.4
For a new standalone NWAS 7.0/7.3 (or 7.4, with VIM 7.0 SP4 and higher)
installation, refer to Preparing Installation on page 85. If the SAP standalone
NWAS 7.0/7.3 (or 7.4, with VIM 7.0 SP4 and higher) 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 93.
21.2 Installing the Mobile Approval Portal on SAP

NetWeaver Portal 7.0/7.3/7.4
For a new SAP NetWeaver Portal 7.0/7.3 (or 7.4, with VIM 7.0 SP4 and higher)
installation, refer to Preparing Installation on page 85. If the SAP NetWeaver
Portal 7.0/7.3 (or 7.4, with VIM 7.0 SP4 and higher) 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 93.
21.2.1
Prerequisites
The following versions are supported:
7.0 SP8 or higher
All higher support packages and enhancement packages of NetWeaver 7.0, 7.3,
and 7.4
Approval Portal
7.0

VIM070000-IGD-EN-6
159
Chapter 21 Installing the Mobile Approval Portal
21.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 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, 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. 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 159 for specific SAP NetWeaver Portal versions.
21.2.3
3.
Deploy the Approval Portal with the officially supported Support Package.
4.
Access the Mobile Approval Portal URL in a supported smartphone / tablet.
Scenario 2: Enabling Mobile Approval Portal for New

Customers
1.
For SAP NetWeaver Portal 7.0/7.3/7.4 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 159 for specific SAP NetWeaver Portal versions.
160
2.
Deploy the Approval Portal with the officially supported Support Package.
3.
Access the Mobile Approval Portal URL in a supported smartphone / tablet.

VIM070000-IGD-EN-6
Part 6
Vendor Invoice Management SAP CRM SAP
Shared Service Framework Component
Installation
Part 6 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.
162

VIM070000-IGD-EN-6
Chapter 22
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.
22.2.1
Required Knowledge
22.2.2

Installation Tool (SAINT) and CRM Add-On Installation
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)

VIM070000-IGD-EN-6
163
22.2.3

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)
22.2.4

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)
164

VIM070000-IGD-EN-6
22.2. Checking Prerequisites
22.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:
22.2.6
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.
Installation Tool
*.SAR) that can be extracted using the SAPCAR command line tool.

VIM070000-IGD-EN-6
165
Chapter 23

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.
1.
SAP CRM version
File
SAP CRM 7.0 EHP1
SAP CRM 7.0 EHP2: Additional step needed, see Step 3 on page 167
SAP CRM 7.0 EHP3: Additional step needed, see Step 3 on page 167
OTVIMSSF_INST_VIM701_702.SAR
Source path
INST_CRM_700/DATA/
Target path
\usr\sap\trans\EPS
2.

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

VIM070000-IGD-EN-6
167
168

VIM070000-IGD-EN-6
Chapter 24

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 169
Maintaining a Logical System for the CRM System in VIM on page 173
Installing Support Packages 1 and 2 on page 173
24.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:
1.
transaction.

VIM070000-IGD-EN-6
169
VIM 7.0 supports the following languages:
170
Chinese
Dutch
English
French
German
Hungarian
Italian
Japanese
Portuguese
Romanian
Russian
Spanish

VIM070000-IGD-EN-6
24.1. Activating Business Configuration Sets in the CRM System
New languages for VIM 7.0 are the following:
Czech
Polish
Turkish
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:
1.
transaction.

VIM070000-IGD-EN-6
171
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.
172

VIM070000-IGD-EN-6
24.2. Maintaining a Logical System for the CRM System in VIM
24.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.
3.
Save your settings.
24.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 in the Knowledge Center: https://
knowledge.opentext.com/knowledge/cs.dll/Open/19229480

VIM070000-IGD-EN-6
173
Chapter 25
Verifying Installation
Make sure that the OpenText Vendor Invoice Management CRM add-on is reflected
in the installed components.
1.
2.
Click
next to Component version.

VIM070000-IGD-EN-6
175
Chapter 25 Verifying Installation
OTVIMSSF add-on component installed, with Release number 701_702 and

patch level 0002.
176

VIM070000-IGD-EN-6
Part 7
Vendor Invoice Management SAP
NetWeaver Business Warehouse
Part 7 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.
178

VIM070000-IGD-EN-6
Chapter 26
Installation Tool (SAINT). The following table shows the passwords for the VIM 7.0
BW installation package:
SAP_BASIS
Password
700
F17CB370FA
730
F17CB070FA

The following prerequisites must be fulfilled for the installation of the VIM BW
component.
26.2.1
Required Knowledge
26.2.2

VIM 7.0 BW Prerequisites

See OSS note 1791715: SAP Invoice Management by OpenText 7.0
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:

VIM070000-IGD-EN-6
179
Table 26-1: SAP NetWeaver BW 7.0 / SAP NetWeaver BW 7.3 EHP1 / SAP
NetWeaver BW 7.4
Option
Component: SAP_BW
Release
Support Package
Release
Support Package
700
SAPKW70023
700
SAPKB70013
731
SAPKW73103
731
----
740
----
740
----
Table 26-2: SAP NetWeaver BW 7.3

Option
26.2.3
Component: SAP_BW
Release
Support Package
Release
Support Package
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
Installation Tool
*.SAR) that can be extracted using the SAPCAR command line tool.
180

VIM070000-IGD-EN-6
Chapter 27

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.
1.
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
2.

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.

VIM070000-IGD-EN-6
181
4.
182
Click Start to see the screen that presents the packages ready to be installed.

VIM070000-IGD-EN-6
5.
Choose the package for component OTVIMBW. Carry out the import of the
package as described in the respective SAP documentation.

VIM070000-IGD-EN-6
183
Chapter 28
Verifying the Installation

Make sure that the VIM BW add-on is reflected in the installed components.
1.
2.
Click

VIM070000-IGD-EN-6
185
Chapter 28 Verifying the Installation
In the System: Component information dialog box, you should see the OTVIMBW
186

VIM070000-IGD-EN-6
Chapter 29
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

VIM070000-IGD-EN-6
187
Part 8
Vendor Invoice Management SAP
NetWeaver Gateway Component
Installation
Part 8 Vendor Invoice Management SAP NetWeaver

Gateway Component Installation
This part describes the installation of the Vendor Invoice Management SAP
NetWeaver Gateway (VIM GW) component. The VIM GW component is needed to
run the Supplier Self Service component, which is introduced with VIM 7.0 SP3.
Figure 4: Supplier Self Service architecture
190

VIM070000-IGD-EN-6
Chapter 30
GW installation package:
SAP_BASIS
Password
700 and compatible
F17CB670FA
If you are asked for a SAP note number, use 1791715.

The following prerequisites must be fulfilled for the installation of the VIM GW
component.
30.2.1
Required Knowledge
30.2.2

VIM 7.0 GW Prerequisites

For general information on the installation of the SAP NetWeaver Gateway

components, see http://help.sap.com/saphelp_gateway20sp06/helpdata/en/c3/
424a2657aa4cf58df949578a56ba80/content.htm.
The following components must be installed for SAP NetWeaver Gateway:

VIM070000-IGD-EN-6
191
Table 30-1: SAP ERP 6.0 up to EHP7

Option Component:
GW_CORE
Component: IW_FND
Component: IW_BEP
Releas Support
e
Package
Releas Support
e
Package
Releas Support Package

e
200
250
SAPK-20004IN
GWCORE
SAPK-25004INI 200
WFND
SAPK-20004INIWB
EP
Implement OSS note 1744864: Multiple Origin for Generated BOR/RFC Objects
does not work
Table 30-2: SAP ERP 6.0 EHP7

Option
Component: SAP_GWFND
Release
Support Package
Release
Support Package
740
SAPK-74004INSAPGWF
ND
740
SAPKB74002
Note: The VIM GW component is not yet released for SAP_BASIS 740 (EHP7).
30.2.3
Installation Tool
(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.
192

VIM070000-IGD-EN-6
Chapter 31

To install the OpenText VIM GW package:
1.
Copy the respective SAPCAR file (OTVIMGW_INST_VIM700_700.SAR) from the

Knowledge Center to a local folder.
2.
Call the SAINT transaction (in client 000).

You get an initial screen, which shows the installed components.
3.
On the menu, click Installation Package > Load packages > From Front End
and load file OTVIMGW_INST_VIM700_700.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

VIM070000-IGD-EN-6
193
Chapter 32

Make sure that the VIM GW add-on is reflected in the installed components.
1.
2.
Click
In the System: Component information dialog box, you should see the OTVIMGW

VIM070000-IGD-EN-6
195
Part 9
Vendor Invoice Management Supplier Self
Service Component Installation
Part 9 Vendor Invoice Management Supplier Self

Service Component Installation
This part describes the installation of the Vendor Invoice Management Supplier Self
Service component. The Supplier Self Service component is introduced with VIM 7.0
SP3.
198

VIM070000-IGD-EN-6
Chapter 33
33.1 Installation Prerequisites
A complete installation and configuration of OpenText Vendor Invoice Management
for SAP Solutions 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.
Server
Operating
system and
browser support
SAP HANA Cloud Platform or any other Java-based application server (SP3
restriction)
This section covers support and restrictions of Supplier Self Service in regards to
operating systems and web browsers.
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 https://sapui5.hana.ondemand.com/sdk/docs/guide/

BrowserSupport.html. See also 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 AcceptLanguage 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.

VIM070000-IGD-EN-6
199
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 22.1.3 Configuring Gateway Users in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
33.2 Installation Components

A WAR (Web application ARchive) file 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.
33.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 33-1: Supplier Self Service system architecture

Note: With VIM 7.0 SP3, only Option 1 is supported. It is described in the
following.
200

VIM070000-IGD-EN-6
Chapter 34
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 HANA Cloud.
34.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.
34.2 Deploying the Application on the SAP HANA

Cloud Server
You deploy the application on the Cloud by using the SAP HANA Cloud Platform
console client. 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. During deployment, you can define various specifics of the
deployed application using the deploy command optional parameters. For more
information, see https://help.hana.ondemand.com/help/frameset.htm?
937db4fa204c456f9b7820f83bc87118.html.
Prerequisites
You have downloaded and configured the SAP HANA Cloud Platform console
client. For more information, see https://help.hana.ondemand.com/help/
frameset.htm?7613dee4711e1014839a8273b0e91070.html.
Depending on your account type, deploy the application on the respective

landscape. For more information, see https://help.hana.ondemand.com/help/
frameset.htm?350356d1dc314d3199dca15bd2ab9b0e.html.
To deploy the application:

1.
In the opened command line console, run the neo deploy command with the
appropriate parameters. You can define the parameters of commands directly in
the command line, as in Example 34-1, Deployment on the SAP HANA Cloud
Server on page 202.
2.
Enter your password if requested.

VIM070000-IGD-EN-6
201
Chapter 34 Installation on the SAP HANA Cloud
3.
Press ENTER.
The deployment of your application starts.
4.
If deployment fails, check if you have defined the parameters correctly.

Example 34-1: Deployment on the SAP HANA Cloud Server
neo deploy -- host <SAP HANA Cloud host> -- account <your account> -application vim3s -- source vimsupplierselfservice.war -- user <email or
user name>
Notes
Next steps
OpenText recommends entering the application name vim3s but you can
choose any other identifier you want.
If the source file vimsupplierselfservice.war is located somewhere on

your system but not on the deployment folder you have to add the path
information to the filename.
If you face any problems with the runtime environment, you can set the
custom parameter runtime-version manually, as described in https://
help.hana.ondemand.com/help/frameset.htm?
13afe5ca6e38485d8e6523f610c0ed29.html.
To make your deployed application available for requests, you must start it by
running the neo start command or manage inside the SAP HANA Cloud cockpit.
For more information, see section 22.2 Customizing the HANA Cloud Server
(Option) in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
If you need more information about the SAP HANA Cloud Platform console client,
see the online documentation: https://help.hana.ondemand.com/help/frameset.htm?
46acebcd81384c9881f8ae7c5f3e3cac.html
34.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.
Note: The SAP HANA Cloud connector must not be used with products other
than SAP HANA Cloud Platform.
202

VIM070000-IGD-EN-6
34.3. Installing the SAP HANA Cloud Connector
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

VIM070000-IGD-EN-6
203
Part 10
Vendor Invoice Management Input Channel
for Ariba Network Integration for SAP
Business Suite Installation
Part 10 Vendor Invoice Management Input Channel for

Ariba Network Integration for SAP Business Suite
Installation
This part describes the installation of the Vendor Invoice Management input channel
for Ariba Network Integration for SAP Business Suite (VIM ARB).
206

VIM070000-IGD-EN-6
Chapter 35
ARB installation package:
SAP_BASIS
Password
700 and compatible
F17CB07598

The following prerequisites must be fulfilled for the installation of the VIM ARB
component.
35.2.1
Required Knowledge
35.2.2

VIM 7.0 ARB Prerequisites

VIM 7.0 SP3 must be installed.
The following components must be installed for Ariba Network Integration 1.0
for SAP Business Suite:
Table 35-1: Ariba Network Integration 1.0 for SAP Business Suite
Option
Component: ARBFNDI1
Component: ARBERPI1
Release
Release
Support Package
100

VIM070000-IGD-EN-6
Support Package
600
207
35.2.3
Implement OSS note 1935335: Mapping methods cannot be used from BAdI
implementations
Installation Tool
(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.
208

VIM070000-IGD-EN-6
Chapter 36

To install the OpenText VIM ARB package:
1.
Copy the respective SAPCAR file (OTVIMARB_INST_VIM700_700.SAR) from the

Knowledge Center to a local folder.
2.
Call the SAINT transaction (in client 000).

You get an initial screen, which shows the installed components.
3.
On the menu, click Installation Package > Load packages > From Front End
and load file OTVIMARB_INST_VIM700_700.SAR.
4.
To add the VIM 7.0 ARB component, click Continue.
5.
Choose the package for component OTVIMARB. Carry out the import of the

VIM070000-IGD-EN-6
209
Chapter 37

37.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.
Apply recommended user settings:

a.
b.
c.
2.
To access the Business Configuration Sets: Activation screen, run the

SCPR20 transaction.
Activate BC set /OTVIMARB/700_CUSTOMIZING.

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.

VIM070000-IGD-EN-6
211
Chapter 38

Make sure that the VIM ARB add-on is reflected in the installed components.
1.
2.
Click
OTVIMARB add-on component installed, with Release number 700.

VIM070000-IGD-EN-6
213
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

VIM070000-IGD-EN-6
215
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 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
216

VIM070000-IGD-EN-6
Glossary
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.
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.

VIM070000-IGD-EN-6
217
Glossary
DataStore Object (DSO)

Storage location for consolidated and cleansed data in SAP NetWeaver BW
DocuLink
OpenText DocuLink 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
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.
218

VIM070000-IGD-EN-6
Glossary
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
ICC
See Invoice Approval (IAP).

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

VIM070000-IGD-EN-6
219
Glossary
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
Integrated Invoice Cockpit
VIM component that gathers and displays all VIM exceptions in one place. Users
can start the respective dashboard by processing a work item directly from the
Integrated Invoice Cockpit.
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
Invoice Exception (IE)
VIM component that handles the exceptions that arise after an SAP invoice is
created
220

VIM070000-IGD-EN-6
Glossary
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.
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

VIM070000-IGD-EN-6
221
Glossary
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
PO
See Non purchase order (Non PO) invoice (PIR).

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).
Price variance
Situation where the price on the invoice is different from the price in the purchase
order
222

VIM070000-IGD-EN-6
Glossary
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
Roles
Set of predefined roles for the SAP user
SAP Add-On Assembly Kit (AAK)
Standardized delivery procedure for software

VIM070000-IGD-EN-6
223
Glossary
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.
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
224

VIM070000-IGD-EN-6
Glossary
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.

VIM070000-IGD-EN-6
225

OpenText Vendor Invoice Management For SAP Solutions 7.0 - Installation PDF

Uploaded by

Document Information

Original Description:

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.0 - Installation PDF

Uploaded by

Copyright:

Available Formats

OpenText Vendor Invoice Management for

OpenText Vendor Invoice Management for SAP Solutions

About Vendor Invoice Management

About This Document ............................................................... 9

Target Audience ............................................................................... 9

Vendor Invoice Management SAP ERP Component

Preparing Installation .............................................................. 13

Installing the OpenText Package ........................................... 17

Installing the Package ..................................................................... 17

Verifying Installation ............................................................... 39

Installing a VIM Support Package .......................................... 41

SAP ERP Prerequisites ................................................................... 41

Upgrade Overview ..........................................................................

KPI Dashboard Installation

Installing the KPI Dashboard .................................................. 71

Post Installation Activities ...................................................... 73

Activating the SAP Web Dynpro Service ........................................... 73

OpenText Vendor Invoice Management for SAP Solutions Installation Guide

Setting Up the SAP NetWeaver Portal Integration ............................. 79

OpenText Approval Portal Installation

Preparing Installation .............................................................. 85

Installation Prerequisites .................................................................. 85

Installing the Approval Portal ................................................. 93

Preparing the Installation ................................................................. 93

Configuring SAP NetWeaver Portal Components .............. 109

Creating AppIntegrator IViews for Users .........................................

Applying a New Patch ........................................................... 135

Upgrading the Approval Portal from Previous Versions ... 137

Troubleshooting .................................................................... 139

Supporting Installation of the Standalone NWAS Portal

Uninstalling the Approval Portal .......................................... 143

Uninstalling Using Software Deployment Manager ..........................

Mobile Approval Portal Installation

Introduction to the Mobile Approval Portal ......................... 151

Authentication for the Mobile Approval Portal ................... 155

OpenText Vendor Invoice Management for SAP Solutions Installation Guide

Installing the Mobile Approval Portal .................................. 159

Installing the Mobile Approval Portal on Standalone NWAS

Vendor Invoice Management SAP CRM SAP Shared

Preparing Installation ............................................................ 163

Password Control .......................................................................... 163

Installing the OpenText Package ......................................... 167

Post Installation Activities .................................................... 169

Activating Business Configuration Sets in the CRM System ............. 169

Verifying Installation ............................................................. 175

Vendor Invoice Management SAP NetWeaver Business

Preparing Installation ............................................................ 179

Password Control .......................................................................... 179

Installing the OpenText Package ......................................... 181

Verifying the Installation ....................................................... 185

Upgrading SAP NetWeaver BW ............................................ 187

Vendor Invoice Management SAP NetWeaver Gateway

Preparing Installation ............................................................ 191

Password Control .......................................................................... 191

Installing the OpenText Package ......................................... 193

Verifying the Installation ....................................................... 195

OpenText Vendor Invoice Management for SAP Solutions Installation Guide

Vendor Invoice Management Supplier Self Service

Preparing Installation ............................................................ 199

Installation Prerequisites ................................................................ 199

Installation on the SAP HANA Cloud ................................... 201

Preparing the Installation ............................................................... 201