VIM For SAP Solutions 20.4 Installation Guide English VIM200400 IGD en 09 PDF

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

Vendor Invoice Management.
The components of Vendor Invoice Management include

Foundation, Invoice Solution, and Solutions Beyond Invoice.
VIM200400-IGD-EN-09
OpenText™ Vendor Invoice Management for SAP® Solutions
Installation Guide
VIM200400-IGD-EN-09
Rev.: 2021-Mar-24
This documentation has been created for OpenText™ Vendor Invoice Management for SAP® Solutions 20.4.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2021 Open Text. All Rights Reserved.

Trademarks owned by Open Text.
One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
1 About Vendor Invoice Management for SAP Solutions ....... 11
1.1 Architectural Overview ..................................................................... 13
1.2 About this document ........................................................................ 14
1.2.1 Target audience .............................................................................. 14
1.2.2 Further information sources ............................................................. 14
1.2.3 Document overview ......................................................................... 15
2 Introduction .............................................................................. 17
Part 1 Prerequisites for installation 19
3 General ..................................................................................... 21
4 SAP prerequisites .................................................................... 23
5 OpenText prerequisites .......................................................... 25
6 Installation tool ........................................................................ 27
7 Patches ..................................................................................... 29
8 Notes on transports ................................................................ 31
9 Required knowledge ............................................................... 33
Part 2 Foundation 35
10 Installing ................................................................................... 37
10.1 Installing packages .......................................................................... 37
10.1.1 Mandatory SAP installation packages ............................................... 38
10.1.2 Optional SAP installation packages .................................................. 38
10.1.3 Optional S/4HANA installation packages .......................................... 39
10.1.4 Installation steps ............................................................................. 39
10.2 Post installation activities ................................................................. 40
10.2.1 Configuring number ranges .............................................................. 40
10.2.2 Configuring general tasks ................................................................ 41
10.2.3 Maintaining event type linkages ....................................................... 43
10.3 Installing language packages ........................................................... 44
11 Fiori Deployment ..................................................................... 47

11.1 Deployment options on premise ....................................................... 47
11.1.1 System landscape ........................................................................... 48
11.1.2 Configuring network options ............................................................. 49
11.1.3 Checking the Fiori landscape ........................................................... 49
VIM200400-IGD-EN-09 Installation Guide iii

Table of Contents
11.2 Deployment options on SAP Cloud Platform ..................................... 49

11.2.1 System landscape ........................................................................... 50
11.2.2 Installing the VIM UI on SAP Cloud Platform Neo account ................. 51
11.3 Setting up a multiple backend system ............................................... 56
11.4 Setup Fiori ...................................................................................... 56
11.4.1 Activating services .......................................................................... 56
11.4.1.1 Enabling OData service ................................................................... 56
11.4.1.1.1 Multiple Origin Composition ............................................................. 58
11.4.1.2 Activating the service ...................................................................... 59
11.4.2 Installing Fiori perspectives .............................................................. 59
11.4.3 Setup Fiori launchpad content .......................................................... 59
11.4.3.1 On premise ..................................................................................... 59
11.4.3.1.1 Transports ...................................................................................... 60
11.4.3.1.2 SAP system alias ............................................................................ 60
11.4.3.2 SAP Cloud Platform ........................................................................ 61
12 Upgrading ................................................................................. 63
Part 3 Invoice Solution 65
13 VIM classic mode installation ................................................. 67

13.1 Preparing installation ....................................................................... 67
13.1.1 Checking prerequisites .................................................................... 67
13.1.1.1 SAP S/4HANA prerequisites ............................................................ 67
13.1.2 Selecting required components and downloading the packages ......... 68
13.2 Installing packages .......................................................................... 72
13.2.1 Installing the package ...................................................................... 72
13.2.2 Post installation activities ................................................................. 73
13.2.2.1 Importing transport with Fiori layouts ................................................ 74
13.2.2.2 Installing transport with layout variants ............................................. 75
13.2.2.3 Activating Business Configuration Sets ............................................. 75
13.2.2.4 Configuring workflow dialog tasks .................................................... 77
13.2.2.5 Refreshing SAP workflow runtime buffer ........................................... 79
13.2.2.6 Configuring object services .............................................................. 80
13.2.2.7 Maintaining number ranges .............................................................. 81
13.2.2.8 Linking events for VIM workflows ..................................................... 84
13.2.2.9 Maintaining the SAPscript form for approval ...................................... 86
13.2.2.10 Maintaining standard text ................................................................. 88
13.2.2.11 Setting background user parameters for Non PO invoice posting ....... 89
13.2.2.12 Configuring additional settings ......................................................... 90
13.2.2.13 Maintaining Business Transaction Events ......................................... 91
13.2.2.14 Configuring the system landscape .................................................... 91
13.2.2.15 Fiori: Activating services .................................................................. 92
iv OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

Table of Contents
13.2.2.16 Fiori: Setting up Launchpad content on-premise ................................ 92

13.2.2.17 Fiori: Setting up Launchpad content on cloud .................................... 93
13.2.2.18 Fiori: Deploying Fiori apps on cloud .................................................. 94
13.2.2.19 Adjusting BAdI for extended VAT date support .................................. 94
13.2.2.20 Performing the mandatory configuration ........................................... 94
13.2.3 Language packs ............................................................................. 94
13.2.3.1 VIM language packs ........................................................................ 95
13.3 Installing Single Click Entry for SAP GUI .......................................... 95
13.4 Installing a VIM Support Package ..................................................... 97
13.4.1 Post installation activities after installing a new Support Package ....... 97
13.4.1.1 Importing transport with Fiori layouts ................................................ 97
13.4.1.2 Activating business configuration sets .............................................. 97
13.4.1.3 Restart ICC/BCC server .................................................................. 98
13.5 Upgrading ....................................................................................... 98
13.5.1 Changes in VIM Invoice Solution component structure ...................... 98
13.5.2 Upgrading VIM 7.5/7.6 to VIM 20.4 ................................................. 101
13.5.2.1 Upgrading to VIM 20.4 during an SAP S/4HANA conversion ............ 102
13.5.2.1.1 Preparing the conversion ............................................................... 102
13.5.2.1.2 Performing the conversion ............................................................. 103
13.5.2.2 Upgrading VIM 7.5 to VIM 20.4 without conversion .......................... 104
13.5.2.2.1 Preparing the upgrade ................................................................... 104
13.5.2.2.2 Installing the package .................................................................... 105
13.5.2.3 Post installation activities after an upgrade ...................................... 105
13.5.2.3.1 Importing transport with Fiori layouts .............................................. 105
13.5.2.3.2 Activating business configuration sets ............................................ 105
13.5.2.3.3 Checking status and runtime behavior of BAdIs for Invoice
Processing ................................................................................... 106
13.5.2.3.4 Reviewing BAdI for extended VAT date support .............................. 106
13.5.2.3.5 Checking Inbound component ........................................................ 107
13.5.2.3.6 Checking the logic module configuration ......................................... 107
13.5.2.3.7 Reviewing posting logic in current document types .......................... 108
13.5.2.3.8 Reviewing parked processing ........................................................ 108
13.5.2.3.9 Updating Fiori launchpad tiles ........................................................ 108
13.5.3 Upgrading VIM 16.3 to VIM 20.4 .................................................... 108
13.5.3.1 Preparing the upgrade ................................................................... 109
13.5.3.2 Upgrading ..................................................................................... 109
13.5.3.3 Post installation activities after an upgrade ...................................... 109
13.5.3.3.1 Importing transport with Fiori layouts .............................................. 110
13.5.3.3.2 Activating business configuration sets ............................................ 110
13.5.3.3.3 Checking status and runtime behavior of BAdIs for invoice
processing .................................................................................... 111
13.5.3.3.4 Updating Fiori launchpad tiles ........................................................ 111
VIM200400-IGD-EN-09 Installation Guide v

Table of Contents
13.5.3.3.5 Adjusting BAdI for extended VAT date support ................................ 111
13.5.4 ACP files ...................................................................................... 111
13.6 Troubleshooting ............................................................................ 112
13.6.1 Table length restrictions for /OPT/VIM_1HEAD ............................... 112
13.6.2 Handling workflow container inconsistencies ................................... 112
13.6.3 Missing translations in line items of indexing screen ........................ 113
13.6.4 Issue with loading Fiori apps .......................................................... 114
14 Simple Mode VIM installation ............................................... 115

14.1 Overview ...................................................................................... 115
14.2 Simple Mode installation ................................................................ 116
14.2.1 Prerequisites ................................................................................ 116
14.2.2 Installing the Simple Mode components .......................................... 117
14.2.3 Post installation activities ............................................................... 119
14.2.3.1 Maintaining standard text ............................................................... 119
14.2.4 Update ......................................................................................... 121
14.2.5 Troubleshooting ............................................................................ 121
14.2.5.1 Possible problem during upgrade ................................................... 122
15 KPI Dashboard installation ................................................... 123

15.1 Installing the KPI Dashboard .......................................................... 123
15.2 Post installation activities ............................................................... 123
15.2.1 Activating the SAP Web Dynpro service ......................................... 123
15.2.2 Setting the connection for the SAP Web Dynpro service .................. 129
15.2.3 Setting up the SAP NetWeaver Portal integration ............................ 130
15.2.3.1 Prerequisites ................................................................................ 130
15.2.3.2 Adding the Portal component ......................................................... 132
16 OpenText Approval Portal installation ................................ 135

16.1 Preparing installation ..................................................................... 135
16.1.1 Installation prerequisites ................................................................ 135
16.1.2 Installation components ................................................................. 139
16.1.3 System architecture ...................................................................... 139
16.1.3.1 SAP user requirements ................................................................. 141
16.2 Installing Web Viewer/Brava! View for the Approval Portal ............... 142
16.3 Installing the Approval Portal .......................................................... 143
16.3.1 JCo3 migration considerations ....................................................... 143
16.3.2 Preparing the installation ............................................................... 144
16.3.3 Configuring the administrator role ................................................... 147
16.3.3.1 Configuring the administrator role for access through NWAS ........... 147
16.3.3.2 Configuring the Administrator Role for Access Through NWAS for
SAP NetWeaver 7.3 and 7.4 .......................................................... 150
16.3.4 Deploying the Software Component Archive ................................... 152
vi OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

Table of Contents
16.3.4.1 Optional: Starting the Approval Portal J2EE application manually ..... 152
16.3.4.2 Optional: Clearing the browser cache ............................................. 152
16.3.5 Deploying the Software Component Archive with SAP NetWeaver
7.3 ............................................................................................... 155
16.3.6 Deploying the Software Component Archive using SUM .................. 158
16.4 Configuring SAP NetWeaver Portal components ............................. 161
16.4.1 Creating AppIntegrator iViews for users .......................................... 162
16.4.2 Creating AppIntegrator iViews for users with SAP NetWeaver 7.3,
7.4, and 7.5 .................................................................................. 168
16.4.3 Creating roles for users ................................................................. 178
16.4.4 Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5 ........ 182
16.4.5 Assigning roles to SAP NetWeaver Portal users .............................. 185
16.4.6 Configuring iViews and roles for the administrator ........................... 186
16.4.7 Administering the OpenText Approval Portal ................................... 187
16.5 Applying a new patch .................................................................... 187
16.6 Upgrading the Approval Portal from previous versions ..................... 188
16.7 Troubleshooting ............................................................................ 189
16.8 Supporting installation of the standalone NWAS Portal and Mobile
Approval Portal on Unix or Linux .................................................... 189
16.9 Uninstalling the Approval Portal ..................................................... 189
16.9.1 Uninstalling using Software Deployment Manager ........................... 190
16.9.2 Uninstalling with SAP NetWeaver 7.3, 7.4, and 7.5 .......................... 191
16.9.3 Removing SAP NetWeaver Portal components ............................... 192
16.9.4 Deleting properties files ................................................................. 193
16.9.5 Optional: Removing the startup parameter in the Config Tool ........... 193
17 Mobile Approval Portal installation ..................................... 195

17.1 Introduction to the Mobile Approval Portal ....................................... 195
17.2 Authentication for the Mobile Approval Portal .................................. 199
17.3 Installing Web Viewer for the Mobile Approval Portal ....................... 199
17.4 Installing the Mobile Approval Portal ............................................... 200
17.4.1 Installing the Mobile Approval Portal on standalone NWAS 7.3/7.4 ... 200
17.4.2 Installing the Mobile Approval Portal on SAP NetWeaver Portal
7.3/7.4/7.5 .................................................................................... 201
17.4.2.1 Prerequisites ................................................................................ 201
17.4.2.2 Scenario 1: Enabling Mobile Approval Portal for existing customers
running on SAP NetWeaver Portal ................................................. 201
17.4.2.3 Scenario 2: Enabling Mobile Approval Portal for new customers ....... 202
18 Vendor Invoice Management SAP NetWeaver Business

Warehouse component installation ..................................... 203
18.1.1 Checking prerequisites .................................................................. 203
18.1.1.1 VIM BW add-on prerequisites ........................................................ 203
VIM200400-IGD-EN-09 Installation Guide vii

Table of Contents
18.2 Installing or upgrading the OpenText package ................................ 204

18.3 Verifying the installation ................................................................. 204
18.4 Uninstalling the VIM BW add-on package ....................................... 204
18.4.1 Prerequisites ................................................................................ 204
18.4.2 Steps before uninstalling ............................................................... 205
18.4.3 Uninstalling the VIM BW package .................................................. 205
19 Vendor Invoice Management BW/4HANA add-on

component installation ......................................................... 207
19.1 About the VIM BW/4HANA add-on ................................................. 207
19.2 Packaging and delivery information ................................................ 208
19.3 Supported environments and compatibility ...................................... 209
19.3.1 Supported systems ....................................................................... 209
19.3.2 OpenText product compatibility ...................................................... 209
19.3.3 Language support ......................................................................... 209
19.4 Installing the VIM BW/4HANA add-on component ........................... 209
19.4.1 Password control .......................................................................... 210
19.4.2 Checking VIM BW/4HANA prerequisites ......................................... 210
19.4.3 Installing the OpenText package .................................................... 210
19.4.3.1 OLTP (source system) ................................................................... 210
19.4.3.2 OLAP (BW/4HANA) system ........................................................... 211
19.5 Upgrade notes .............................................................................. 212
20 Vendor Invoice Management component for SAP

NetWeaver Gateway installation .......................................... 213
20.1.2.1 Required knowledge ...................................................................... 214
20.1.2.2 VIM Gateway prerequisites ............................................................ 214
20.1.2.3 Installation tool .............................................................................. 215
20.2 Installing the OpenText package .................................................... 215
21 Vendor Invoice Management Supplier Self Service - Lean

Variant component installation ............................................ 217
21.1.1 Installation prerequisites ................................................................ 217
21.1.2 Installation components ................................................................. 218
21.1.3 System architecture ...................................................................... 218
21.2 Installation on the SAP HANA Cloud .............................................. 219
21.2.1 Preparing the installation ............................................................... 219
viii OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

Table of Contents
21.2.2 Deploying the application on the SAP HANA Cloud Server .............. 219
21.2.3 Installing the SAP HANA Cloud connector ...................................... 221
22 Vendor Invoice Management electronic invoices

22.1 General package for electronic invoices .......................................... 223
22.2 Inbound component: Integration with SAP Document Compliance .... 224
22.2.1 Prerequisites ................................................................................ 224
22.2.2 Installation .................................................................................... 225
23 Vendor Invoice Management ARIBA integration

23.1 Post installation activities for Business Suite add-on ........................ 227
23.1.1 Activating business configuration set .............................................. 227
23.1.2 Activating BAdI implementations .................................................... 228
23.2 Importing ABAP workbench objects, PI scenario ............................. 229
24 Vendor Invoice Management integration with Ariba, CIG

scenario objects installation ................................................ 231
24.1.2.1 OTVIMARC prerequisites .............................................................. 231
24.1.2.2 Installation tool .............................................................................. 232
24.2 Installing the OpenText package .................................................... 232
24.4.1 Activating business configuration set for the OTVIMARC component 233
Part 4 Solutions Beyond Invoice 235
25 Installing ................................................................................. 237

25.1 Installing packages ........................................................................ 237
25.1.1 SAP installation packages ............................................................. 238
25.1.2 Optional S/4 HANA installation packages ........................................ 238
25.1.3 Installation steps ........................................................................... 239
25.2 Installing language packages ......................................................... 240
26 Upgrading ............................................................................... 241
27 Uninstalling ............................................................................ 243

27.1 Foundation and Beyond Invoice solutions ....................................... 243
27.2 Prerequisites ................................................................................ 244
27.3 Invoice Solution ............................................................................ 244
27.3.1 Steps before deinstallation ............................................................. 244
VIM200400-IGD-EN-09 Installation Guide ix

Table of Contents
27.3.1.1 Deleting local workflow types ......................................................... 245

27.3.1.2 Deleting table entries in /OTX/PF62_T_PLDA ................................. 245
27.3.1.3 Deleting table entries in /OTX/PF62_T_AIC .................................... 245
27.3.1.4 Deleting layouts for VIM Analytics .................................................. 246
27.3.1.5 (VIM) Deleting GOS entries ........................................................... 246
27.3.1.6 (VIM) Maintaining Business Transaction Events .............................. 247
27.3.1.7 (VIM) Removing authorization group /OPT ...................................... 247
27.3.1.8 (VIM) Removing event type linkages (SWETYPV) ........................... 247
27.3.1.9 (VIM) Cleaning up the MIRO enhancement ..................................... 249
27.3.1.10 (VIM) Cleaning up Ariba PI Scenario transports .............................. 249
27.3.1.11 Deleting all external usages ........................................................... 249
27.3.1.12 Undoing all modifications ............................................................... 249
27.3.2 Steps after deinstallation ............................................................... 249
27.3.2.1 (VIM) Reviewing BAPI for extended VAT date support ..................... 250
27.3.3 Troubleshooting ............................................................................ 250
27.3.3.1 Error in phase CHECK_LOCKED_OBJ ........................................... 250
27.3.3.2 Error in phase COLLECT_OBJLIST ............................................... 251
27.3.3.3 Error in phase DDIC_IMPORT ....................................................... 252
27.3.3.4 Error in phase CHECK_USAGE ..................................................... 253
27.3.3.5 Error in phase CHECK_MOD ......................................................... 253
27.4 Optional activities .......................................................................... 254
GLS Glossary 255
x OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

Chapter 1
About Vendor Invoice Management for SAP

Solutions
OpenText Vendor Invoice Management for SAP Solutions (VIM) is an ABAP add-on
solution to SAP ECC and SAP S/4HANA.
VIM automates the processing of incoming documents into SAP.
Document-centric business processes like the processing of incoming invoices from

vendors or incoming sales orders from customers are typical use cases for VIM.
After capture, data is enriched and validated against predefined business rules.
If no business rules fail, the document is posted in SAP without human intervention.
Although a straight through, no-touch process is the ultimate objective, VIM also
supports the fast and efficient handling and resolution of exceptions.
Exceptions are routed via workflow to the relevant user or user group based on the
role assigned to the exception.
For managers VIM offers a comprehensive suite of operational and analytical

reports. In addition, VIM offers the tools to identify common exceptions that should
be addressed to achieve even higher levels of automation.
VIM includes the following solutions:
• Invoice Solution
• Procure to Pay Solutions
– Order Confirmation
– Delivery Note
– Quotation
• Order to Cash Solutions
– Sales Order
– Remittance Advice
Each solution consists of a best practice implementation for a specific document

scenario. It includes preconfigured mapping rules, enrichment rules, business rules,
user roles and user actions. Learning-based enrichments features embedded easy to
configure machine learning that automates input based on previous user input.
VIM200400-IGD-EN-09 Installation Guide 11

Chapter 1 About Vendor Invoice Management for SAP Solutions
Since VIM resides inside SAP, enrichments and business rules have direct access to
SAP master and transactional data, which avoids complex interfaces and the
replication and duplication of data.
Each solution offers a Workplace used by end-users and managers to manage and
monitor outstanding and completed work items. Each solution includes a
preconfigured set of analytical measures tailored for the specific document scenario.
Solutions can be enhanced to support company-specific business requirements.
VIM Solutions use features offered by its powerful feature rich Foundation.
The VIM Foundation consists of the following components:
• Inbound
• Process
• Workplace
• Analytics
VIM also supports custom solutions where a preconfigured solution is not available
for a specific, less common business process.
VIM offers a simple and intuitive user interface for end-users, managers and
administrators.
Users can choose between the classic SAP GUI or the modern SAP Fiori interface.
SAP Fiori offers a responsive web-based user interface that supports desktop and
mobile devices.
VIM supports various input channels including scan, fax¸ e-mail and web services.
It also supports various input formats, including paper, PDF, TIFF, IDoc and XML.
VIM requires an ArchiveLink-compliant SAP-certified content repository for the

storage of incoming documents. OpenText recommends OpenText Archiving and
12 OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

1.1. Architectural Overview
Document Access for SAP Solutions or OpenText Core Archive for SAP Solutions for
the storage of documents.
VIM integrates seamlessly via its Inbound component with OpenText Intelligent
Capture for SAP Solutions and OpenText Core Capture for SAP Solutions, which
uses advanced machine learning algorithms to extract metadata from imaged-based
documents like PDF and TIFF.
VIM also offers integration with OpenText Extended ECM for SAP Solutions and
OpenText Document Presentment for SAP Solutions.
1.1 Architectural Overview

The following figure gives an overview of the basis architecture. It shows how the
core components of VIM are integrated into SAP and which additional OpenText
components like Document Pipeline, Document Storage, Information Extraction
Service and WebViewer are completing the solution.
Beside the components of this graphic, VIM offers additional components such as
SAP NetWeaver Business Warehouse or BW/4Hana for specific solutions which are
not shown in this basis architectural overview.
Figure 1-1: Technical system landscape

Chapter 1 About Vendor Invoice Management for SAP Solutions
1.2 About this document

1.2.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.2 Further information sources

Product docu- The following documentation is available for VIM on OpenText My Support (https://
mentation knowledge.opentext.com/knowledge/cs.dll/Open/10151494):
• OpenText Vendor Invoice Management for SAP Solutions - User Guide for Invoice
Solution (VIM-UGD)
• OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIM-CGD)
• OpenText Vendor Invoice Management for SAP Solutions - Administration Guide
(VIM-AGD)
• OpenText Vendor Invoice Management for SAP Solutions - Reference Guide for Invoice
Solution (VIM-RGD)
• OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide for Invoice
Solution (VIM-CCS)
• OpenText Vendor Invoice Management for SAP Solutions - Security Guide (VIM-GSM)
Foundation (BOCP-CGD)
Solutions Beyond Invoice (BOCP-CCS)
• OpenText Vendor Invoice Management for SAP Solutions - User Guide for Solutions
Beyond Invoice (BOCP-UGD)
Release Notes Release Notes describe:
• The software supported by the product

1.2. About this document
• Requirements
• Restrictions
• Important dependencies
• New features
• Known issues
• Fixed issues
• Documentation extensions
The Release Notes are updated continuously . The latest version of the VIM Release
Notes is available on OpenText My Support (https://knowledge.opentext.com/
knowledge/cs.dll/Open/10151494).
1.2.3 Document overview

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

• “Foundation” on page 35
• “Invoice Solution” on page 65
• “Solutions Beyond Invoice” on page 235

Chapter 2
Introduction
Vendor Invoice Management for SAP Solutions consists of different solutions for
your business processes. You do not only have management solutions for invoices,
but also for sales orders, remittance advices, delivery notes, quotations or order
confirmations.
Depending on the solution and on the features that you want to use, you have to
download different components and install them on your system.
This guide bundles the information about installation steps and available setup files
into three areas:
1. Foundation
2. Invoice Solution
3. Solutions Beyond Invoice
Depending on the solution that you plan to install and on the features that you want
to use, different areas of the guide are providing the information that you are
searching for.
Foundation
The Foundation bundles information that is valid for all your installations, no matter
which solution you are planning to install.
The mandatory installations that are listed here, must be installed. You cannot set up
a running system if these installations are not completed.
The installations that are marked as optional in this area depend on your
environment or the features that you want to use:
• If you want to set up an integration with Extended ECM, you must complete the
Extended ECM installation.
• If you want to use embedded Analytics you must install the package.
Invoice Solution
Invoice Solution bundles a number of packages and components that are all relevant
if you want to use the invoice solution.
You must only read this section if you plan to use the invoice solution.
Just as the foundation, invoice describes mandatory installation packages that are
relevant for further additional components.

Chapter 2 Introduction
Solutions Beyond Invoice

Solutions Beyond Invoice provide two packages that bundle different solutions:
1. Order to Cash consist of the solution for sales orders and remittance advices.
2. Procure to Pay consist of the solution for delivery notes, quotation and order
confirmation.
You must only read this section if you plan to use one of the listed solutions.

Part 1
Prerequisites for installation
Chapter 3
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 Professional Services.
Supported versions Only the products and versions specified in the Release Notes are
supported. Other versions have not been tested and are therefore
not officially supported for this version. The Release Notes
contain the definitive list of supported versions. Any other
versions mentioned in this guide are superseded by the versions
specified in the Release Notes.
OpenText Support If you require additional help with technical problems, contact
Center OpenText Customer Support. You can find the contact
information for your region at http://www.opentext.com/support.
Caution
If you are performing an upgrade and you have several VIM components
in your system (this may include former Business Center components), all
components must be upgraded at the same time to prevent errors because
of dependencies.
If you are performing an upgrade using SAP Maintenance Planner, it will

take care of identifying the components that must be upgraded together. If
you are upgrading using tools like SAINT, make sure to identify all
components that are part of the upgrade and add all of them into the queue
together.
The component structure has been partially reorganized in VIM 7.6 / 20.4.
To aid you in identifying the components, information is provided on the
structure changes in “Upgrading“ on page 63 for VIM Foundation and
Solutions Beyond Invoice and in “Changes in VIM Invoice Solution
component structure” on page 98 for Invoice Solution.
Important
Make sure the SAP workflow system is configured to run workflows. To check
this, run the SWU3 transaction. Make sure most of the relevant items are
configured correctly, indicated by the icon. It is very important that, in the

Chapter 3 General
Maintain Runtime Environment node, Configure RFC destination has the

icon.
Note: Check for and download the available latest support packs and hot fixes
on OpenText My Support.

Chapter 4
SAP prerequisites
Check the latest version of the Release Notes for any version support and
prerequisites.
Prior to installation, check the following prerequisites. For more information about
the overall system landscape, see “System landscape” on page 48.
SAP support Check the latest version of the Release Notes on OpenText My Support for required
packages support packages for the employed SAP system.
SAP Notes Check the following SAP Notes to avoid known problems with the SAP Add-On
Installation Tool (SAINT):
• SAP Note 822380 - Problems with add-on installation/upgrade in SAP NW 7.0x

AS ABAP
• SAP Note 212876 - The new archiving tool SAPCAR
• SAP Note 3011244 - BC Set Activation results in Activation Links error SCPR116
(and/or) GETWA_NOT_ASSIGNED dump
Recommended to implement on SAP Basis 7.55
• SAP_BW below 7.51 SP9 (used for Fiori Monitoring and Analytics reports. For
more information, see Section 11 “Fiori Monitoring and Analytics reports” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Foundation (BOCP-CGD)):
– SAP Note 2767228 : ODATA: Date variable value help throws an error
– SAP Note 2415249 : Using SAP Analytics Cloud as Client for SAP BW queries
on BW 7.50

Chapter 5
OpenText prerequisites
Prior to installation, check the following prerequisites.
Document Archived documents are displayed with the viewing application installed on your
viewer desktop. On your mobile device, they are displayed according to Mime type and
ArchiveLink settings. Alternatively, they are displayed and rendered into PDF with
the OpenText Imaging Web Viewer (Web Viewer) or OpenText Brava! View for SAP
Solutions (Brava! View) if it is installed and configured.
To support the document view in plug-ins for Mime types where no HTML-based
plug-in is installed, Web Viewer 10.0.0 or Brava! View 16.0 is required as a
minimum. OpenText strongly recommends using Web Viewer with the latest patch.
You can download the corresponding software from My Support.
Table 5-1: Display of archived documents
Desktop iPad/iPhone
Web Viewer / Web Viewer / No Web Viewer / Brava! View
Brava! View on Brava! View off support[a]
Display variant Inplace Inplace New tab
PDF Web Viewer / Acrobat plug-in Built in
Brava! View
XLS Web Viewer / Not supported Built in
Brava! View
PPT Web Viewer / Not supported Built in
Brava! View
DOC Web Viewer / Not supported Built in
Brava! View
Others Web Viewer / Not supported Not supported
Brava! View
[a]Web Viewer or Brava! View may be used in custom solutions to convert the ArchiveLink document in
a PDF for displaying it on an iOS device.
Integration You can integrate the VIM Foundation into other OpenText solutions, like the Fiori
Business Object Browsing for Document Access and Extended ECM for SAP
Solutions solution accelerator. If you do so, make sure to check dependencies and
compatibility.
Recent For more information, download the most recent product documentation, release
information notes and patches description released on My Support.

Chapter 6
Installation tool
Vendor Invoice Management for SAP® Solutions uses the SAP Add-On Installation
Tool (SAINT) for installation.
On the ISO image or ZIP archive of the product, the single PAT files are archived in
SAPCAR files (extension *.SAR). You can extract SAPCAR files with the SAPCAR
command line tool.
SAINT uses single PAT files (extension *.PAT) which integrate several transport files;
these collections are also called packages.
Note: The handling of the installation procedure within SAINT differs

depending on the SAP system that is used. For more details, see the respective
SAP documentation.
The OpenText Vendor Invoice Management packages are protected with specific
passwords. During installation, passwords are requested by SAINT. You find the
passwords in this guide, in the chapters on the respective components.

Chapter 7
Patches
Patches Patches (Hot Fixes), Support Packages and the latest versions of the Release Notes
for VIM are available on OpenText My Support.
For SAP Invoice Management by OpenText customers: To obtain access to My

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

Chapter 8
Notes on 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.

Chapter 9
Required knowledge
The following knowledge is required for the person dealing with the installation as
described in this document:
• In-depth knowledge of SAP administration tasks, in particular the SAP Add-On

Installation Tool (SAINT)
• Basic knowledge of the employed operating system

Part 2
Foundation
Chapter 10
Installing
This section describes the installation of the VIM packages on an SAP application
server. For general information about installing in an SAP environment, see also
“Prerequisites for installation” on page 19.
10.1 Installing packages

The VIM components are provided as add-on packages. Collect the installation files
for the components listed in the corresponding sections. For details about basic
components or additional S/4HANA components, refer to corresponding sections.
Notes
• Customers who purchase VIM from SAP receive the packages from SAP
Marketplace.
• Customers who purchase VIM directly from OpenText download the
packages, including installation packages, from OpenText My Support.
To install the packages:
1. Sign in with Client 000 in English.
2. Load the installation packages and support packages from the front end by
selecting the respective SAPCAR file (*.SAR) from the local file system. The
SAPCAR file is decompressed automatically.
3. Carry out the import of the packages and support packages as described in the
SAP documentation.
4. After the import has finished, continue with the activation of the BC sets. For
more information, see:
• Section 2 “Basic configuration” in OpenText Vendor Invoice Management for

SAP Solutions - Configuration Guide for Foundation (BOCP-CGD)
SAP Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP-CCS)
You can bypass messages you might get during installation. These warn you
about not digitally signed packages/software.

Chapter 10 Installing
10.1.1 Mandatory SAP installation packages

The following packages and included Foundation components are available:
Component SAR file Version Password

OTBCBAS OTBCBAS_0700_006.S 0700_006 8B96C455BF
AR
OTBCSL00 OTBCSL00_0700_006.S 0700_006 8B87C936AF
AR
The VIM components are used as follows:
OTBCBAS
OpenText Process Base.
Mandatory for the whole VIM installation
OTBCSL00
OpenText VIM Solution Base. Mandatory except in case where the product is
installed not on SAP ECC and SAP S/4HANA but another type of SAP
Netweaver system
10.1.2 Optional SAP installation packages

The following packages and included Foundation components are available:

OTBCWUI OTBCWUI_0740_006 0700_006 8B83D04FBF
.SAR
OTBCRM OTBCRM_0700_006. 0700_006 8B86C826BF
SAR
OTBCWUI
OpenText Process Fiori Base.
Needs to be installed if VIM Fiori apps are used
OTBCRM
OpenText Extended ECM integration.
Needs to be installed if the integration between VIM and Extended ECM is used
(OpenText Extended ECM for SAP Solutions is installed – for details check the
Release Notes for Foundation of Vendor Invoice Management for SAP
Solutions)

10.1. Installing packages
10.1.3 Optional S/4HANA installation packages

The following optional S/4HANA packages and included Foundation components
are available

OTBCS4 OTBCS4_1610_106.S 1610_106 8A87B126BF
AR
For details about the components, see Section 3.1 “Analytics and SAP S/4HANA
Backend System” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Solutions Beyond Invoice (BOCP-CCS).
OTBCS4
OpenText VIM S/4 Base.
Needs to be installed if the basic embedded analytics capabilities is used.
10.1.4 Installation steps

This section summarizes the required installation steps and their sequence for
installing VIM.
To install the Foundation:
1. Install the OpenText Process Base (OTBCBAS) add-on using the SAINT
transaction.
Notes
• After the installation, some mandatory configuration is required to

enable the business scenarios. For more information, see Part I
“Foundation” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD) .
2. Install the OpenText VIM Solution Base (OTBCSL00) add-on using

the SAINT transaction.
3. Optional If you want to use the Fiori Task App, install the OpenText Fiori Process
Base Web UI (OTBCWUI) add-on using the SAINT transaction on the system that
you want to use for the Web UI.
4. Optional Install OpenText VIM Extended ECM Integration:
• Install the OpenText VIM Extended ECM Integration (OTBCRM) on the same
system as the OpenText Process Base (OTBCBAS) add-on using the SAINT
transaction.
5. Optional Installation for S/4HANA systems:

Install the OpenText VIM S/4 Base (OTBCS4) using SAINT transaction.
6. Install the language packages
10.2 Post installation activities

After installation, perform the mandatory customizing. You find the description in
both the Configuration and the Solution guide:
• Section 2 “Basic configuration” in OpenText Vendor Invoice Management for SAP

Solutions - Configuration Guide for Foundation (BOCP-CGD)
• Section 2 “Basic configuration” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP-CCS)
10.2.1 Configuring number ranges

The Foundation component of Vendor Invoice Management for SAP Solutions
requires the configuration of different number range objects. This is needed to
register incoming documents in the incoming document ledger (in Inbound
Configuration). It is also needed to register all business related information for the
processing (in Process Foundation / Process Configuration) in the solution specific
process ledger. The following number ranges must be configured in the SNUM
transaction:
/OTX/PF01
Document registration
/OTX/PF02L
Default number range for process ledger entries. You can also replace this by a
solution specific number range object; see the end of this section.
For both objects, create a number range interval 01 with the following attributes:
Instead of using the default number range object for every solution or for your
custom business solution, you can also configure a solution number range object and
interval.

10.2. Post installation activities
The delivered solutions refer to the unique number range object /OTX/PF02. All
documents in the process use the same number range.
To configure a custom number range object for each solution, you can copy the
standard number range object. You need to assign it to the related data model of the
Process Foundation. For details, see Section 6.2.3 “Maintaining level key fields” in
Foundation (BOCP-CGD).
10.2.2 Configuring general tasks

The Process Foundation is running on SAP Business Workflow. Some delivered
tasks and workflow templates must be configured correctly as general tasks. The
following tasks and workflow templates are relevant:
• Workflow Template 00297300

• Workflow Template 00297330
• Standard Task 00297316
• Standard Task 00297303
To configure general tasks:
1. In the PFTC transaction, enter the corresponding objects.
2. Display the standard task or workflow template.
3. Maintain agent assignment.

4. Display attributes of the agent assignment.
5. Set general task and activate your changes.

10.2.3 Maintaining event type linkages

The Process Foundation allows you to control running workflow instances from
external applications using some special event type linkages, which must be
maintained in the SWETYPV transaction.
The Process Foundation allows to control running workflow instances from external
applications by using some special event type linkages, which you must maintain in
the SWETYPV transaction. This refers to the following events and settings:
Table 10-1: Controlling running workflow instances from external applications
Field Setting
Event • FINISH_PROCESS
• INIT_PROCESS
• RUN_ASSIGNMENT
• RUN_CATEGORIES
Object Category BOR Object Type

Object Type /OTX/PF04E
Receiver Type /OTX/PF04

Field Setting
Linkage Setting (Event Receiver) Receiver Call
Function Module
Receiver Function Module
/OTX/PF02_EVENT_RECEIVER
Event delivery
Using tRFC (Default)
Linkage Activated
Activate checkbox.
Behavior Upon Error Feedback
3 Do not change linkage
Receiver Status
0 No errors.
10.3 Installing language packages

Vendor Invoice Management is localized into multiple languages. Refer to the
release notes for the supported languages.
Languages are delivered in two parts:
1. ABAP translation
2. Fiori translation
For the OTBCWUI add on installation package, the Fiori translation is delivered in
OTBCWUI_0740_006_I18N.zip. Import the transport into the system where
component OTBCWUI is installed (frontend system).
The ABAP translation is delivered in language packages. You find the language
packages on My Support in the folder of the respective support package.
You must import language packages for the relevant add-ons. For Vendor Invoice
Management Foundation and Solutions Beyond Invoice, language packs are
available for OTBCBAS, OTBCSLOC and OTBCSLPP which include all supported
languages.
To install the language packages:
1. Sign into the English working Client.
2. Call the SMLT transaction
3. Select the language, and the click the Import package button.
4. In the popup screen click From Front End button.
5. Select the .SAR file that was delivered for the language and the solution.

10.3. Installing language packages
Tip: This step is skipped, if the .SAR file is already decompressed in the
server directory.
6. Carry out the import of the language package as described in the SAP
documentation.
When the import is finished, all translations for the selected languages are
imported into Client 000.
7. Select the language, and then click Menu Language > Special Actions > Client
Maintenace.
8. Run Client Maintenance.

All texts of the selected language are copied from the customizing tables of
Client 000 into the current client in insert mode.
Note: If the old translation displays after you imported the translation, try
to refresh the translation of the language at runtime.
Run the RSLANG20 program for the selected language, and then run the
following transactions:
• /$CUA
• /$DYN

Chapter 11
Fiori Deployment
The settings described in this section are only relevant if you want to use the Fiori
Task App.
11.1 Deployment options on premise

Chapter 11 Fiori Deployment
11.1.1 System landscape
Figure 11-1: Web Services landscape
* OTBCSL33 add-on, which is listed in the graphic is not relevant for the invoice
component of 20.4.
The Fiori Task App of Vendor Invoice Management for SAP Solutions comes with
the OpenText Process Fiori Base (OTBCWUI add-on). This add-on requires the SAP
component SAP_UI. For detailed system requirements, check the Release Notes.
The WebUI retrieves data from the technical service /OTX/PF05_DATA comes with
the OpenText Process Fiori Base (OTBCWUI add-on ). The activation of this service is
described in “Enabling OData service” on page 56.
The /OTX/PF05_DATA service is part of the OpenText Process Base (OTBCBAS add-on).
This add-on requires the SAP component IW_BEP or SAP_GWFND. For detailed system
requirements, check the Release Notes.
OpenText recommends the installation of a Web Dispatcher to prevent direct access

from the client browser to the archive system.
Note: The protocol for Launchpad access (typically HTTPS) must be the same
for archive access.
The following illustrates a sample configuration for the Web Dispatcher:

wdisp/system_0 = SID=T7H, NR=01, MSHOST=<replace-with-frontend-server-host>,
MSPORT=8101, SSL_ENCRYPT=1, SRCSRV=*:*, SRCURL=/sap/opu/odata;/sap/bc
wdisp/system_1 = SID=ARC, EXTSRV=http://<replace-with-archive-host>:8080, SRCSRV=*:*,
SRCURL=/archive

11.2. Deployment options on SAP Cloud Platform
11.1.2 Configuring network options

You must define which systems must be opened from a network perspective for an
Intranet or Extranet scenario. For more information, see the SAP Help regarding
“Deployment Options” and “Multiple Network Zones”.
11.1.3 Checking the Fiori landscape

The Fiori system landscape must meet the requirements of the SAP guidelines. For
more information, see the SAP Help.
11.2 Deployment options on SAP Cloud Platform

11.2.1 System landscape
Figure 11-2: SAP Cloud Platform landscape
The Fiori Task App of VIM comes with the VIM WebUI (IZIP file PF07_BC_NEO_
UI_<version>.zip).
This application has the following destinations:
• The PF05_DATA destination must point to the /OTX/PF05_DATA OData Service,

which is part of the OTBCBAS add-on. This add-on requires the IW_BEP or SAP_
GWFND SAP component. The activation of this service in the SAP backend is
described in “Enabling OData service” on page 56.
• The ARCHIVE destination points to the Archive Server system for documents
retrieval.
For a detailed description of installing the ZIP file in your SAP Cloud Platform
account, as well as the necessary steps for configuring the destinations with your
SAP Cloud Connector, see “Installing the VIM UI on SAP Cloud Platform Neo
account” on page 51. For product limitations connected with the SAP Cloud
Platform Deployment Option, see the dedicated Release Notes.

11.2.2 Installing the VIM UI on SAP Cloud Platform Neo

account
Currently OpenText does not offer the VIM UI application on SAP Cloud Platform
for subscription. This means that you must import the VIM UI application in one of
your sub-accounts.
OpenText recommends the following installation procedure, to ensure that you can
run multiple VIM UI applications in parallel against different backends. The general
idea is to use one sub-account as provider (where the application becomes installed)
and one or more other sub-accounts (under your global account) that subscribe the
VIM UI application from the provider account (called consumer in this procedure).
With that mechanism, the application is only patched at one place and becomes
distributed from there.
The description assumes that you run the SAP_GWFND (SAP Gateway Hub)
component on your backend. If you are using a dedicated frontend server, the
procedure is the same, but the system that becomes connected with the Cloud
Connector is the frontend server.
Note: The OData Provisioning Capability of SAP Cloud Platform is not

considered within the described installation approach. It is not guaranteed that
the VIM OData Service is working properly, because there are various
limitations and the option has not yet been verified.
To install the VIM UI on SAP Cloud Platform:
1. Configure principal propagation: setup trust between the backend and SAP
Cloud Connector; map platform users to SAP system users. For more
information, see the SAP Help: SAP Cloud Platform Connectivity: “Configuring
Principal Propagation”.
2. Cloud Connector: create virtual mapping to internal system:
a. Open the Cloud Connector Administration. On the menu on the left,

expand your SAP Cloud Platform Account node.
b. On the menu, click Cloud To On-Premise.
c. On the Access control tab, add a mapping for your SAP ERP backend
system and a mapping for the Archive Server system. You must use the
name and the port that you choose for the virtual host later when you
maintain the destination on the SAP Cloud Platform. For principal
propagation, it is necessary to choose protocol HTTPS and Principal Type X.
509 Certificate.

d. Expose the following URL paths:
System Path Access Policy

SAP ERP backend /sap/opu Path and all sub-paths
Archive Server system /archive Path and all sub-paths
3. SAP Cloud Platform: import the application in the provider account:
a. On the SAP Cloud Platform Cockpit, expand the Applications node, and
then click HTML5 Applications. Using Import from File, import the
OTBCWUI_NEO_0740_006.zip file.

b. Choose an application name, for example otbcwuipf07bc.

c. Take the 20.4product version.
This version string is only used for storage in the Cloud GIT repository and
has no direct relation to the application version.
After the import, you see the application in the list.
d. To navigate to the application, click it.
e. On the menu on the left, click Versioning.
f. Click the magic wand of the version you want to activate.
Note: In the provider account, it is not necessary to maintain any

destination. The version can be activated although there are
destination errors.
4. SAP Cloud Platform: configure destinations in the consumer accounts:
a. Launch the SAP Cloud Platform Cockpit in your browser.

b. Navigate to the subaccount where you want to consume the Fiori Task
App.
c. On the menu on the left, open the Connectivity node and then click
Destinations.
d. Using the Virtual Host, connect the exposed systems from the Cloud
Connector with a destination on the Cloud Platform. The application
requires a destination for the SAP ERP system where the PF05 OData
Service is running, and a destination for the Archive Server system.

Table 11-1: SAP ERP backend parameters
Name BC_PF05_DATA
Type HTTP
Description
Location ID
URL http://<virtual_host_name>:<port>/sap/opu/
odata/OTX/PF05_DATA;mo;v=3;
Proxy Type OnPremise
Authentication PrincipalPropagation
Table 11-2: Archive Server system parameters
Name BC_ARCHIVE
Type HTTP
Description
Location ID
URL http://<virtual_host_name>:<port>
Proxy Type OnPremise
Authentication NoAuthentication
5. SAP Cloud Platform: subscribe the VIM UI application in the consumer

accounts:
a. On the menu on the left, open the node Applications.

b. Click Subscriptions.

c. To subscribe to any VIM UI application of your provider subaccount, click

New Subscription.
d. As Subscription Name, enter otbcwuipf07bc.
Important
Take exactly this name, as the content for the Fiori Launchpad Site
refers to this name.
e. In the list of Subscribed HTML5 Applications, click the Application link
to maintain the required destinations.

11.3 Setting up a multiple backend system

Vendor Invoice Management for SAP Solutions makes use of the Multi Origin
Composition concept on OData service level to support multiple backend systems.
This concept enables you to instruct the Fiori Task App to fetch the data from a
dedicated backend system. You provide the configured backend system alias in the
front-end server as a URL parameter: &system=<SYSTEM_ALIAS>. This allows you
to connect different backends with one front-end server.
The same system alias has to be configured for the /OTX/PF05_DATA OData service .
It is not possible to run the app without system alias configuration.
11.4 Setup Fiori

11.4.1 Activating services
The settings described in this section are only relevant if you want to use the Fiori
Task App. This section describes how you register and activate the OData service for
the backend communication and also how you activate the UI5 application on the
Fiori Server. For more information, see “System landscape” on page 48.
11.4.1.1 Enabling OData service

The Fiori Task App communicates with the ABAP backend using a dedicated OData
service (/OTX/PF05_DATA). To invoke this service using the HTTP protocol, it first
must be enabled. This section describes the necessary steps.
Prerequisite All connection settings must be configured accordingly and the SAP NetWeaver
Gateway must be activated.

11.4. Setup Fiori
Call the /IWFND/MAINT_SERVICE transaction and maintain the backend OData

service for the external service /OTX/PF05_DATA, version 3.
Maintain the system for the service (default OTBCWUI_BACKEND).
Therefore you might need to connect to the backend system where the OTBCBAS add-
on package is installed according to your system landscape setting
The following screenshot shows an example of /OTX/PF05_DATA, version 2.

After that you must activate the registered service. To activate the service, run the
SICF transaction and activate the /sap/opu/odata/OTX/PF05_DATA service.
11.4.1.1.1 Multiple Origin Composition
The OData service classes (OTBCWSR add-on) can be installed on several backend
systems. In this case, you can configure the service at the gateway system in a way
that data from multiple of the backend systems is requested.
You can perform this using Multiple Origin Composition (MOC). For detailed
information, see the SAP Help.
To configure the OData service accordingly, run the /IWFND/MAINT_

SERVICE transaction and add the system aliases of the systems that should be used.
With regards to MOC, the Fiori Task App provides the additional parameter system
to define which system should be used. If the parameter is not set, the system alias
LOCAL is used.

11.4. Setup Fiori
Important
If several systems are connected, you must set the OData service to error
tolerant, using the following path: SPRO > SAP NetWeaverGateway > OData
Channel > Composition > Flag OData Services to be error tolerant in case of
MDC. If not all users exist in all connected systems, consider using the SAP
“User Role” concept to control the backend system that the users connect to.
11.4.1.2 Activating the service

The technical unit of the Fiori Task App in the ABAP Frontend Server is a BSP. A
prerequisite for launching a BSP using the browser is an active service that is bound
to the BSP in the SICF transaction. For UI5 applications, the service is created by
default automatically, nevertheless you must activate it before it can be used.
To activate the service, run the SICF transaction and activate the /sap/bc/ui5_ui5/
otbcwui/pf07_bc_ui_03 service.
11.4.2 Installing Fiori perspectives

OpenText provides transports to deliver the Fiori perspectives for all Fiori apps used
in VIM. Import these transports into the backend systems where the solutions are
installed.
Access transports on My Support.
Customizing transports contain the Fiori perspectives for the VIM Foundation and
SAP Solutions Beyond Invoice components.
• Solution for incoming delivery notes

• Solution for incoming order confirmation
• Solution for incoming sales order
• Solution for incoming remittance advice
• Solution for incoming quotation
11.4.3 Setup Fiori launchpad content

11.4.3.1 On premise
OpenText provides transports to deliver the Launchpad content for all Fiori apps
used in VIM solutions. For more information, see OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Solutions Beyond Invoice
(BOCP-CCS) and the related solution guides. You can either use the transports and
the predefined tile catalogs or you can integrate the Fiori Task App into the Fiori
Launchpad in your configuration. For more information, see Section 10.1.1
“Integrating Fiori Task App into Fiori Launchpad” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Foundation (BOCP-CGD).

11.4.3.1.1 Transports
You can access the transports on My Support: Import these transports into the
frontend systems where the OTBCWUI add-on is installed
Workbench Transport: VIM Launchpad content

A new entry for semantic object VIM otbcwuipf07bc is delivered. Check the /
n/UI2/SEMOBJ transaction that there does not exist an entry with this key for a
different object.
Customizing Transport: VIM Launchpad content
The following Fiori tile catalogs are delivered. You can assign them to the
related role used in the corresponding business scenario.
Administration
/OTBCWUI/PF07_BC_ADMIN
Perspective Manager
Foundation
/OTBCWUI/PF07_BC_FOUNDATION
Stores and archives documents and triggers VIM Inbound
Solutions
/OTBCWUI/PF07_BC_SOL_DELIVERY_NOTE
Solution for incoming delivery notes
/OTBCWUI/PF07_BC_SOL_ORDER_CONF
Solution for incoming order confirmation
/OTBCWUI/PF07_BC_SOL_SALES_ORDER
Solution for incoming sales order
/OTBCWUI/PF07_BC_SOL_REMITTANCE_ADV
Solution for incoming remittance advice
/OTBCWUI/PF07_BC_SOL_QUOTATION
Solution for incoming quotations
11.4.3.1.2 SAP system alias
With the delivered launchpad content, also a system alias for the multi origin access
is predefined in the service URL. See <Node parameter> in Section 10.1.1 “Integrating
Fiori Task App into Fiori Launchpad” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide for Foundation (BOCP-CGD). You must use the
system alias OTBCWUI_BACKEND and configure it for the delivered launchpad content
according to your system landscape in the SAP IMG Manage SAP System Aliases.
Tip: If you want to use a differnet system alias then the delivered OTBCWUI_
BACKEND you have to change each semantic navigation configuration besides

11.4. Setup Fiori
the launchpad content . For more information, see OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Foundation (BOCP-CGD).
11.4.3.2 SAP Cloud Platform

OpenText provides transports to deliver site content for all Fiori apps used in VIM
solutions.
You access the transports on My Support.
We have 3 different transports, containing the following content:
• Foundation:
– Foundation component of Vendor Invoice Management for SAP Solutions

• Administration:
– Foundation component of Vendor Invoice Management for SAP Solutions

• Solutions:
– Solution for incoming delivery notes

– Solution for incoming order confirmation
– Solution for incoming sales order
– Solution for incoming remittance advice
– Solution for incoming quotations
For more details, see OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Foundation (BOCP-CGD).

Chapter 12
Upgrading
Integration You can integrate the VIM Foundation into other OpenText solutions, like the Fiori
Business Object Browsing for Document Access and Extended ECM for SAP
Solutions solution accelerator. If you do so, make sure to check dependencies and
compatibility.
Upgrading VIM for SAP Foundation

For the Business Center components, no specific upgrade packages are delivered.
For an upgrade from version 16.3.x, install the standard installation packages for the
VIM for SAP Foundation.
Important
Several components of the Foundation are now included in
OTBCBAS (OpenText Process Base). If the OTBCINB, OTBCWSR or OTBCFND
components are installed on your system, no action is required. These
components are now included in the OpenText Process Base package.
Table 12-1: Changes in VIM Foundation component structure
BC 16.3.x Description VIM 7.6 / 20.4 Description

OTBCBAS Business Center Base OTBCBAS OpenText Process Base
OTBCFND Business Center
Foundation
OTBCINB Business Center Inbound
OTBCWSR Business Center Web
Services
OTBCWUI Business Center Web UI OTBCWUI OpenText Process Fiori
Base
OTBCSL00 Base for Business Center OTBCSL00 OpenText VIM Solution
solutions Base
OTBCRM Extended ECM for SAP OTBCRM OpenText VIM xECM
Solutions Integration Integration
OTBCS4 Business Center S/ OTBCS4 OpenText VIM S/4 Base
4HANA Foundation
For upgrading the Solutions Beyond Invoice components, see “Upgrading“

on page 241.

Chapter 12 Upgrading
Mandatory activities
After upgrading, you must process the following activities manually:
Note: When upgrading to Vendor Invoice Management 20.4, observe the

mandatory activities in this section but also the mandatory activities in the
Release Notes.

Part 3
Invoice Solution
Chapter 13
VIM classic mode installation
This part describes the installation of the SAP components of Vendor Invoice
Management (VIM) - Invoice Solution.
Note: Compared to VIM 7.5 and VIM 7.6, some software components have
been restructured in VIM 16.3 and VIM 20.4. If you are performing a new
installation and you know VIM components from a prior installation, make
sure to review “Changes in VIM Invoice Solution component structure”
on page 98.
13.1 Preparing installation

13.1.1 Checking prerequisites
13.1.1.1 SAP S/4HANA prerequisites
Check the following prerequisites prior to installation:
SAP S/4HANA
• SAP S/4HANA 1610 (S4CORE 101) all FPS or

• SAP S/4HANA 1709 (S4CORE 102) all FPS or
• SAP S/4HANA 1809 (S4CORE 103) all FPS
• Support Package Manager (transaction code SPAM) level 66 or later. OpenText
recommends upgrading to the latest version of SPAM before installation.
Note: For a list of all currently supported combinations of VIM versions and
SAP products, see SAP Note 2339256 (https://launchpad.support.sap.com/#/
notes/2339256).
Fiori frontend version – If you want to use the VIM Fiori apps, check the supported
SAP UI versions in the release notes for VIM Foundation.

Chapter 13 VIM classic mode installation
13.1.2 Selecting required components and downloading the

packages
This section explains which components are required for different Invoice Solution
scenarios. VIM Foundation components (OTBCBAS, OTBCSL00) are mandatory to be
installed before or together with Invoice Solution components. The optional Fiori UI
component OTBCWUI is mandatory to be installed if you use Fiori apps with Invoice
Solution. For details on the installation of the prerequisites, see “Foundation”
on page 35.
Core Invoice Solution scenarios, including inbound and Fiori apps, are delivered
with the component OTEXVIM. The component OTBCSL30 provides objects shared by
Classic Mode and Simple Mode of Invoice Solution.
The main invoice scenarios can be complemented by additional optional scenarios

like Ariba integration and others.
The components that are required for each scenario are marked in “Invoice Solution
components depending on scenario” on page 68. The different components do not
necessarily have to be installed on the same server. For more information, see
“Architectural Overview” on page 13.
Table 13-1: Invoice Solution components depending on scenario
Additional,
Core, Inbound
Component Description depends on
and Fiori
scenario
OTEXVIM Invoice Classic x x
OTBCSL30 Invoice Base x x
Ariba Integration using Cloud
OTVIMARC x
Integration Gateway
OTVIMBW BW Invoice Component x
OTVIMBW4 BW/4 Invoice Component x
OTVIMGW Invoice 3s Gateway x
OTBCSL38 Invoice eDocument Connector x
To select components and download packages:
1. Collect the installation files for the components listed in “VIM components -
installation files” on page 69.
Notes
• Customers who purchase VIM through SAP receive the packages from
SAP Marketplace.

13.1. Preparing installation

Table 13-2: VIM components - installation files
Component Description File Version Password

VIM S/4 Invoice OTBCSL30_816
OTBCSL30 81610_106 8A87C935AF
Base 10_106.SAR
VIM S/4 Invoice OTEXVIM_816
OTEXVIM 81610_106 9182CC4BB8
Classic 10_106.SAR
VIM Invoice
OTVIMARC_80
OTVIMARC Ariba CIG 80700_006 8199C454C8
700_006.SAR
Integration
VIM Invoice
OTBCSL38_807
OTVIMSL38 eDocument 80700_006 8B87C935A7
00_006.SAR
Connector
OTVIMBW4_I 100_004
VIM BW/4
OTVIMBW4 NST_100_004.S 8099C151BF
Invoice
AR
VIM BW OTVIMBW_807
OTVIMBW 80700_006 8199C751AB
Invoice 00_006.SAR
VIM S/4 Invoice OTVIMGW_816
OTVIMGW 81610_106 8099C251AB
3s Gateway 10_106.SAR
The following optional components are described in the Foundation or

Solutions Beyond Invoice parts. For their usage, see the following list:

OTBCSLOC, OTBCSLPP
For more information, see “SAP installation packages” on page 238.
Packages for SAP S/4HANA

OTBCS4, OTBCS4OC, OTBCS4PP
For more information, see “Optional S/4HANA installation packages”
on page 39 and “Optional S/4 HANA installation packages” on page 238.
Extended ECM for SAP Solutions integration

OTBCRM
For more information, see “Optional SAP installation packages” on page 38.
Note: The Business Center-based packages existing prior to VIM 20.4 have
been reorganized:
• OTBCFND, OTBCINB and OTBCWSR are included into OTBCBAS.

• OTBCUS03 is included into OTBCWUI.

This reorganization is reflected in respective installation package

attributes. The components that have been moved to other components
will be “removed” from your system when the successor components are
installed, with all objects being kept.
2. Collect the latest post installation transports, available in the installation

package/media under the path Software\Invoice Solution\Postinstall.
All transports are mandatory for their respective scenarios.
Binary name Transport Description Install on Deployment

name scenario
additional_ Q02K900040 ALV grid Back end On-premise
transport_ layouts for
withlayout. Analytics and
zip screen plug-ins
Used for: core
invoice
scenarios
Invoice D9XK900275 Fiori Front end On-premise
Solutions- Launchpad
Launchpad content
Content.zip transports for
on-premise
Used for: Fiori
invoice apps
on-premise
scenario
neo_Invoice Fiori Cloud SCP
Solutions- Launchpad
Launchpad content
Content.zip transports for
SAP Cloud
Platform (SCP)
Used for: Fiori
invoice apps
cloud scenario
neo_Invoice VIM Supplier Cloud SCP
Solutions_ Self Service
otusrregui. registration UI,
zip for SCP
Used for:
Invoice
Supplier Self
Service app
cloud scenario

Binary name Transport Description Install on Deployment

name scenario
Transport_ D02K900158 Transport for Back end On-premise
to_convert_ OTVIMBW4, to
OTVIMBW_DS_ convert existing
to_ data sources
OTVIMBW4. from
zip OTVIMBW
Used for:
Business
Warehouse
scenario
Invoice D64K902536 Fiori Back end On-premise
Solutions_ perspectives
fiori_ layouts
perspective Used for: Fiori
s_layouts. invoice apps
zip on-premise
scenario
Invoice D64K902651 Fiori Back end On-premise
Solutions_ customizing
fiori_ transports for
customizing on-premise
_entries. Used for: Fiori
zip invoice apps
on-premise
scenario
3. If upgrading from VIM 16.3 SP3, SP4, or SP5, you may want to use delta BC sets
instead of full BC sets. You can download delta BC sets from OpenText My
Support under Resources > Patches > Vendor Invoice Management >
OpenText Vendor Invoice Management 20.4 > Invoice Solutions > Additional
Components. Download the file that corresponds to your source VIM version.
For more information, see “Activating business configuration sets”
on page 110.
4. Collect the latest language packs for these components on My Support.

OpenText recommends that you install the most recent VIM 20.4 Support
Package (SP). You find the SPs on My Support. For further information, see the
Release Notes of the respective SP.


This chapter describes the installation of VIM Invoice Solution on an SAP S/4HANA
system. For general information on installation in an SAP environment, see also
“Preparing installation” on page 67.
13.2.1 Installing the package

When you have identified the packages required for your scenarios, perform the
installation.
To install packages:
1. Locate the component SAR files on the installation media in the folder Software
\Invoice Solution\ABAP Addons. In the SAINT transaction, load the .SAR files
from the front end. Alternatively, extract the .PAT files from the .SAR files and
put the .PAT files into the application server transport directory \usr\sap\
trans\EPS\in.
2. Add the support packages to the queue, using the same procedure. Adding
support packages at this point saves time and is a safer variant of the
installation.
3. Carry out the import of the packages as described in the respective SAP
documentation.
4. Additional steps that are required when using Fiori apps

Install and configure the Web Services component OTBCWUI, as described in
“Installation steps” on page 39.
When deploying the Fiori UI on SAP Cloud Platform (SCP), set up Invoice
Solution specifics:
• The Subscription Name must match pf07bcvimneoui03 because the

Launchpad Content is referring to it.
• You need to maintain an additional destination: PS33_DATA_SRV - VIM OData
Service. See the following screenshots:

5. Continue with the post installation steps. For more information, see “Post
installation activities” on page 73.
13.2.2 Post installation activities

To complete the installation, you have to perform and validate the following
procedures:
• “Importing transport with Fiori layouts” on page 74

• “Installing transport with layout variants” on page 75
• “Activating Business Configuration Sets” on page 75
• “Configuring workflow dialog tasks” on page 77
• “Refreshing SAP workflow runtime buffer” on page 79
• “Configuring object services” on page 80
• “Maintaining number ranges” on page 81
• “Linking events for VIM workflows” on page 84
• “Maintaining the SAPscript form for approval” on page 86
• “Maintaining standard text” on page 88
• “Setting background user parameters for Non PO invoice posting” on page 89
• “Configuring additional settings” on page 90
• “Maintaining Business Transaction Events” on page 91
• “Configuring the system landscape” on page 91
• “Fiori: Activating services” on page 92
• “Fiori: Setting up Launchpad content on-premise” on page 92
• “Fiori: Setting up Launchpad content on cloud” on page 93
• “Fiori: Deploying Fiori apps on cloud” on page 94
• “Adjusting BAdI for extended VAT date support” on page 94
• “Performing the mandatory configuration” on page 94

13.2.2.1 Importing transport with Fiori layouts

After installation, you must import the following transport to the systems where you
have installed the VIM add-on. It is necessary for the Fiori apps to work.
You find post installation transports on the installation media / package under the
path Software\Invoice Solution\Postinstall.
• invoice solutions_fiori_perspectives_layouts.zip: Post install - VIM

Fiori Perspectives
Transport name: D64K902536
Parameters for When setting up tiles for VIM, you need to know specific parameters for each Fiori
manual configu- Task App. They are listed in the following table.
ration
nodeId wobjType workplaceId

Approve PS03_VIM_APR_INV PS03_PRC_VIM_APR WP_INBOX
Invoices
Approve PS03_VIM_BULKAPR_IN PS03_VIM_BULKAPR WP_INBOX
Invoices (bulk V
mode)
Enter Cost PS32_VIM_SCO_INV PS32_PRC_VIM_SCO WP_INBOX
Assignment
Simple
Enter Cost PS37_VIM_ECO_INV PS37_PRC_VIM_ECO WP_INBOX
Assignment
Advanced
Resolve Invoice PS31_VIM_RG01 PS31_VIM_WEB WP_INBOX
Exceptions
Confirm PS35_VIM_MPOEX_INV PS35_VIM_MPOEX WP_INBOX
Quantity and
Price
My Approved PS03_VIM_APR_PROC_ PS03_MY_APP PS03_VIM_PR
Invoices ME OC_ME
Supplier PS34_VIM_S3_INV_M PS34_PRC_VIM_S3M SUP_INBOX
Invoices
Supplier PS34_VIM_S3_INV PS34_PRC_VIM_S3 ACC_INBOX
Accountant
Vendor Invoices PS311_PRC_VIM_VANRE PS311_VIM_VANREP WP_INBOX
Report P

13.2.2.2 Installing transport with layout variants

The layouts provided in the baseline for the VIM Analytics program are stored in the
LTDX table.
Due to limitations of BC set technology, the entries are not correctly entered in the
table when the BC sets are activated. Therefore copy the transport Q02K900040 into
the transport directory and install the transport using STMS. You must install the
transport to every client because the transport contains client specific data.
You find the transport in the file additional_transport_withlayout.zip on the

installation media under the path Software\Invoice Solution\Postinstall.
13.2.2.3 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.

• You have to login in English to activate the BC Sets.
• Always use “Expert mode” to activate the BC sets.
• You need the appropriate security authorization to run some of the
transactions.
• The BC sets for the Foundation component are cumulative. Therefore, with
new installations, always use only the most recent BC set. The VIM Invoice
Solution BC set /OTEXVIM/VIM20_4_BASELINE contains all necessary
baseline configuration and is updated in each Support Package. Therefore, it
is sufficient to activate this BC set for a new installation. For Support
Package installation, refer to “Activating business configuration sets”
on page 97.
• Depending on the SAP version, the following screens might look different on
your system.
• OpenText recommends that you activate only one BC set in one call of the
SCPR20 transaction. Close the SCPR20 transaction after each activation and
call the transaction again. Some activation errors depend on this: they do not
occur if the activation is performed in a separate SCPR20 transaction.
To activate BC sets for Invoice Solution:
1. Activate Foundation (Process Base and Solution Base) BC sets. For more
information, see:


2. Activate BC set /OTEXVIM/VIM20_4_BASELINE.

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.
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 required systems.
a. To access the Business Configuration Sets: Activation screen, run the

SCPR20 transaction.
b. Enter the BC set name /OTEXVIM/VIM20_4_BASELINE and click Activate .
Note: If you are prompted to create a new transport, follow your

standard change request process for tracking changes.
c. Apply the recommended settings, as shown in the screenshot.

d. Click Activate.
After BC Set activation, a message is displayed in the lower left of the SAP
GUI, for example: Activation ended with warning.
Tips
• 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>.
• If you get the following error, ignore it and continue: Fill table
key for table /OTX/PF62_T_AIH only up to position 099
only.
13.2.2.4 Configuring workflow dialog tasks

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

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

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.

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

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

2. To refresh the runtime buffer, click the Start Synchronization button.
13.2.2.6 Configuring object services

The OpenText Document Processing document service is accessible from the GOS
menu for SAP invoices (transactions MIR4 / FB60).
To activate the object services:
1. Run the SM30 transaction.
2. Enter SGOSATTR in the Table/View field and click the Maintain button.
3. When a dialog box is displayed, indicating that the table is cross client, click the
button.
4. Add the entries for the service WF_ZOPT/VIM, as shown in the following
screenshot.

5. Double-click WF_START. Enter WF_ZOPT/VIM in Next service and save.

If you are prompted to create a new transport, continue with the next step.
6. Follow your standard change request process for tracking changes.
13.2.2.7 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
Important
All the number ranges intervals must be 01.
To maintain the number range:
1. Run the SNRO transaction.

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

4. Click the button to add a new number range.
5. Enter required value and save it.

13.2.2.8 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 S/4HANA generates the event POSTED from the business
object BUS2081. The event is linked to trigger the VIM workflow solution for blocked
invoices if the invoice is blocked.
Event linkages are not activated automatically. You must add the event linkages
manually.
Note: OpenText advises against parking documents outside of VIM and

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

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

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

Object type Event Receiver function module Usage

comments
Receiver type Check function module
BUS2081 POSTED SWW_WI_CREATE_VIA_EVENT IAP
TS00275270 —
BUS2081 POSTED /OPT/BL_PO_BLK_RECEIVER Invoice
Exception (IE)
TS00275264 /OPT/BL_PO_CHECK_ROLL_OUT Posted
Approval
/OPT/FIPP ZWFI_ /OPT/BL_NPO_PRK_RECEIVER IE
CREATED
/PTGWFI/PIR_F_CHECKFM
WS00275254
/OPT/B2081 ZWFI_PARKED /OPT/CL_C_BAPI_MM_PARK_HANDLER Parked
processing
VIM_PARKED_ —
DP
FIPP DELETED /OPT/VIM_RPT_RECEIVER_FM VIM Analytics
(VAN)
— —
FIPP POSTED /OPT/VIM_RPT_RECEIVER_FM VAN
— —
BUS2081 DELETED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
BUS2081 POSTED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— — May be used in
special
situation.
Should be
inactive in
standard
configuration.
BUS2081 RELEASED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
BUS2081 CANCELLED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
/ORS/INVAP POSTED /OPT/AAFS_POST_RECEIVER Posted
Approval
— —

Note: There is a dependency between two entries for Object Type BUS2081 and
Event POSTED, the one with Receiver Type TS00275264, and the one with an
empty Receiver Type.
In transaction SWETYPV, make sure that only one of these event linkages is
activated.
• If you use your own blocking workflow, activate only the event linkage with
empty Receiver Type. This event linkage ensures that VAN will be correctly
updated.
• If you use the standard blocking workflow template, activate only the event
linkage with Receiver Type TS00275264. This event linkage updates VAN
with the same function module as the other event linkage but it also starts
the blocking workflow.
One of the two event linkages must be activated.
To enable and disable VIM workflows:
1. To open the Event Type Linkages screen, run the SWE2 transaction.
2. Create the event linkage entries shown in “Event linkages for VIM workflows”
on page 84 (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 84.
13.2.2.9 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.
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.

13.2.2.10 Maintaining standard text

The standard text is client dependent and should be copied from client 000 to all
required clients. Perform the following steps to do a client copy of the following
standard text in the required languages.
• /OPT/VIM_RTV_EXAMPLE
• /OPT/VIM_SIGNATURE_RTV
To maintain standard text:
1. Run the SO10 transaction.
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.
Click .
4. If a dialog box like the following opens, click Yes.
5. Click the Back button on the confirmation page.
6. Repeat the steps for all standard text shown in the list above.
13.2.2.11 Setting background user parameters for Non PO invoice posting

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

Parameter ID Parameter value

FO3 2
Note: Use O like Oscar in FO3. Note that there is a blank in front of the
parameter value 2. The 2 is the second character.
13.2.2.12 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,
see Section 8.11.3 “Enhancing MIRO for pre-population of data during online
invoice creation” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIM-CGD).
• Regarding the configuration of BAdIs for invoice processing, see Section 8.9.1
“Activating BAdI for invoice processing” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide for Invoice Solution (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 Implementation is called
/OPT/ /OPT/ Implementation is not
VIM_ENH_SPOT_MIRO CL_IM_VIM_BADI_MIRO called

13.2.2.13 Maintaining Business Transaction Events

Business Transaction Events (BTEs) are delivered with VIM. For more information
on how BTEs work, refer to the SAP documentation on BTEs.
To maintain BTEs:
1. Run the BF42 transaction.
2. On the Process BTE: Partner Enhancements screen, add the following entries
for process 00005010:
Process
00005010
Function Module
/OPT/BTE_IF_00005010
Partner
/OPT/
Product
/OPT/VIM
3. Add the following entries for process RWBAPI01:
Process
RWBAPI01
Function Module
/OPT/BTE_RWBAPI01_BAPIEXTN
Partner
/OPT/
Product
/OPT/VIM
13.2.2.14 Configuring the system landscape

Run the /OPT/VIM_SLD transaction to configure the system landscape. For more
information, see Section 29.1 “Configuring the System Landscape Directory (SLD)”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIM-CGD).

13.2.2.15 Fiori: Activating services

The following steps are required for the Fiori Task App.
To activate OData and UI services:
1. The Fiori Task App communicates with the ABAP backend using a dedicated
OData service (/OTX/PS33_DATA_SRV). To invoke this service using the HTTP
protocol, activate it first on the Gateway Frontend Server. For VIM 16.3, you
need to set up the version 0003 of OData service in the /IWFND/MAINT_SERVICE
transaction. The activation has to be performed like the activation of /OTX/
PF05_DATA. For general information, see “Enabling OData service” on page 56.
2. Activate the UI service /sap/bc/ui5_ui5/otbcwui/PS30_VIM_UI_03 in

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

To activate the service, run the SICF transaction and activate the /sap/bc/ui5_
ui5/otbcwui/pf07_bc_ui_03 service.
Additionally, for the templates, activate the /sap/bc/ui5_ui5/otbcwui/pf07_
bc_ui_02_t service.
For more information, see “Activating the service” on page 59.
13.2.2.16 Fiori: Setting up Launchpad content on-premise

For the Business Center Fiori Task App, set up the Fiori Launchpad tiles.
The general setup is described in Section 10.1.1 “Integrating Fiori Task App into
Fiori Launchpad” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Foundation (BOCP-CGD). Import the mentioned transport or
configure the tiles.
The tiles are also delivered in the installation package / media under path Software
\Invoice Solution\Postinstall: invoice solutions-launchpad content.zip.
The following Fiori tile catalogs are delivered. You can assign them to the related
role used in the corresponding business scenario.
/OTBCWUI/PS30_VIM
Vendor Invoice Management
/OTBCWUI/PS08_IM_SIMPLE
Vendor Invoice Management (Simple Mode)
/OTBCWUI/PS34_VIM
Vendor Invoice Management - Supplier Self Service
/OTBCWUI/PS34_VIM_ACC
Vendor Invoice Management - Supplier Accountant Perspective

Parameters for When setting up tiles for VIM, you need to know specific parameters for each Fiori
manual configu- Task App. They are listed in the following table.
ration

Approve PS03_VIM_APR_INV PS03_PRC_VIM_APR WP_INBOX
Invoices
Approve PS03_VIM_BULKAPR_IN PS03_VIM_BULKAPR WP_INBOX
Invoices (bulk V
mode)
Enter Cost PS32_VIM_SCO_INV PS32_PRC_VIM_SCO WP_INBOX
Assignment
Simple
Enter Cost PS37_VIM_ECO_INV PS37_PRC_VIM_ECO WP_INBOX
Assignment
Advanced
Resolve Invoice PS31_VIM_RG01 PS31_VIM_WEB WP_INBOX
Exceptions
Confirm PS35_VIM_MPOEX_INV PS35_VIM_MPOEX WP_INBOX
Quantity and
Price
My Approved PS03_VIM_APR_PROC_ PS03_MY_APP PS03_VIM_PR
Invoices ME OC_ME
Supplier PS34_VIM_S3_INV_M PS34_PRC_VIM_S3M SUP_INBOX
Invoices
Supplier PS34_VIM_S3_INV PS34_PRC_VIM_S3 ACC_INBOX
Accountant
Vendor Invoices PS311_PRC_VIM_VANRE PS311_VIM_VANREP WP_INBOX
Report P
13.2.2.17 Fiori: Setting up Launchpad content on cloud

The tiles are also delivered in the following ZIP file: neo-Invoice Solutions-
Launchpad Content.zip, in the installation package / media under path Software\
Invoice Solution\Postinstall.

13.2.2.18 Fiori: Deploying Fiori apps on cloud

The VIM Fiori apps with the Business Center Web UI: ZIP file OTBCWUI_NEO_0740_
006.zip, available in the installation package/media under the path Software\
Foundation\Fiori SAP Cloud Platform
The VIM Supplier Self Service Registration UI for SCP is delivered in ZIP file neo-
invoice solutions_otusrregui.zip, available in the installation package/media
under path Software\Invoice Solution\Postinstall.
For more details, see “Installing the VIM UI on SAP Cloud Platform Neo account”
on page 51.
13.2.2.19 Adjusting BAdI for extended VAT date support

When installing VIM Invoice Solution on SAP S/4HANA 2020 and later releases, an
important manual correction instruction must be implemented to adjust the
implementation of the VAT date BAdI.
Download the correction instruction from OpenText My Support under Resources >
Patches > Vendor Invoice Management > OpenText Vendor Invoice Management
20.4 > Invoice Solutions > Additional Components, and perform the steps
described in the document.
13.2.2.20 Performing the mandatory configuration

Perform the mandatory customizing as described in Part I “Mandatory
configuration” in OpenText Vendor Invoice Management for SAP Solutions -
Note: Leaving the rollout criteria empty will trigger VIM workflows for all
company codes, plants, or document types. Therefore OpenText recommends
that you restrict the rollout criteria accordingly. For more information, see
Section 4 “Defining rollout criteria for parking and blocking processes” in
Invoice Solution (VIM-CGD).
13.2.3 Language packs

Languages for VIM (except for English) are delivered in language packs, which you
can obtain on My Support, in the folder of the respective support package. For
language packs of the Foundation component and the Solutions Beyond Invoice
component, see “Installing language packages” on page 44.

13.3. Installing Single Click Entry for SAP GUI
13.2.3.1 VIM language packs

You can import the language packs after the respective Support Package is installed.
However, you can also install language packs from later Support Packages on earlier
Support Package levels.
To import the language pack, use the SMLT transaction.
VIM translation VIM provides a comprehensive translation description in Section 14 “Translating

description VIM” in OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide for
Invoice Solution (VIM-CCS). It covers the various aspects of translating VIM into new
languages. In addition, the translation chapter 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.
13.3 Installing Single Click Entry for SAP GUI

Install Single Click Entry for SAP GUI on all computers on which also SAP GUI is
installed, and where users are using the Single Click Entry functionality in VIM
Indexing Screen.
If Single Click Entry for SAP GUI is installed on a Vendor Invoice Management
system, it permits to capture data for fields on the index screen using the mouse. For
more information, see Section 4.2 “Using the Single Click Entry feature” in OpenText
Vendor Invoice Management for SAP Solutions - User Guide for Invoice Solution (VIM-
UGD), and “Installing Single Click Entry for SAP GUI” on page 95.
To install Single Click Entry for SAP GUI:
1. Install Microsoft Redistributables. For more information which Microsoft

Redistributables must be installed, see the Release Notes in My Support (https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/58900990).
2. In the SceSapGui folder of the installation media, start SCE for SAP Solutions.
msi.
3. In the Welcome dialog box, click Next.

4. In the License Agreement dialog box, accept the license agreement, and then
click Next.
5. In the Select Installation Folder dialog box, check the path to the installation
folder.
If you want to install Single Click Entry for SAP GUI at a different location, click
Change, and then choose the desired path in the appearing folder dialog box.
6. By default, the software is installed for every user. To install it only for the
current user, click Just me, and then click Next.
7. To start the installation, click Next.
8. Click Close.

After Single Click Entry for SAP GUI has been installed, configure SAP GUI.
To configure SAP GUI and VIM for Single Click Entry for SAP GUI:
1. Start SAP GUI, and then click Options in the system menu.
2. If the Enable Scripting check box at the user settings is cleared, select it.
3. Clear the two additional check boxes controlling notifications because otherwise
you get two notifications for each document that is opened on the index screen.
4. Click Apply.
5. In transaction RZ11 in the section sapgui/user_scripting, set Current value to

True.
6. In the section sapgui/user_scripting_disable_recording, set Current value to

False.
7. Use transaction N/OPT/SPRO to set the variable XML_AR_DELETE_EARLY. For

SceSapGui, do not set this variable to the value X. For more information, see
Section 7.1 “Defining frequently used default values” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIM-
CGD).
8. Configure clean-up of XML files for documents that have left the VIM
Foundation Inbound component. For more information, see Section 7.2.3 “Batch
Program /OPT/VIM_ICC_DL_CLEANUP” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD).
If you want to restrict scripting to specific users, additional configuration is needed.
To restrict scripting to specific users:
• In transaction RZ11, in the section sapgui/user_scripting_per_user, set Current

value to True.
After login, SAP GUI scripting remains available for those users that have the
authorization for the Execute(16) action of the authorization object S_SCR in
class BC_A.
On the login screen, SAP GUI scripting is then available for every user.

13.4. Installing a VIM Support Package
13.4 Installing a VIM Support Package

This chapter describes the installation of a Support Package (SP) for VIM.
For troubleshooting information about handling workflow container inconsistencies,

see “Handling workflow container inconsistencies” on page 112.
Identify and download the Support Packages needed for each component used for
your Invoice Solution scenarios. While SPs for the main Invoice Solution component
OTEXVIM are provided regularly, other components are not necessarily updated
every time.
Support packages are available on My Support for all customers.
After you have identified and downloaded the support package files, perform the SP
installation in the SPAM transaction.
Note: If VIM 7.5/7.6/16.3 is installed on your system, refer to “Upgrading”

on page 98.
13.4.1 Post installation activities after installing a new Support

Package
13.4.1.1 Importing transport with Fiori layouts
After installing a new Support Package, you must import a new transport with Fiori
layouts to the systems where you have installed the VIM Support Package. The
transport is necessary for the Fiori apps to work.
You find post installation transports on OpenText MySupport, in the folder of the
respective support package. You only need the transport provided with the highest
support package that you are installing.
13.4.1.2 Activating business configuration sets

After installing a new Support Package, you must activate business configuration
sets (BC sets).
Notes
• To activate the BC sets, sign in in English and use the expert mode.
• You must activate the BC sets in every client separately.

13.4.1.3 Restart ICC/BCC server

After you have installed a new VIM Support Package and (if applicable) a new
Business Center Support Package, you must restart your ICC/BCC server.
The load manager and the hotspots of the ICC/BCC server will continue to use the
old data definitions. This may lead to inconsistencies if you do not restart the server.
13.5 Upgrading
For the Invoice Solution component, no specific upgrade packages are delivered.
For an upgrade from an earlier version, install the standard installation packages for
the components used in your business scenarios. Identify these packages with the
information provided in “Selecting required components and downloading the
packages” on page 68 and “Changes in VIM Invoice Solution component structure”
on page 98.
This chapter describes the following upgrade scenarios:
• Upgrading from VIM 7.5 or VIM 7.6 to VIM 20.4 on SAP S/4HANA. For more
information, see “Upgrading VIM 7.5/7.6 to VIM 20.4” on page 101.
• Upgrading from VIM 16.3 to VIM 20.4. For more information, see “Upgrading
VIM 16.3 to VIM 20.4” on page 108.
For information about upgrading from any VIM version on SAP ERP to VIM 7.5 or
VIM 7.6, see Section 13.6.5 “Upgrading VIM” in OpenText Vendor Invoice Management
for SAP Solutions - Installation Guide (VIME070600-IGD) (Installation Guide VIM 7.6).
For troubleshooting information about handling workflow container inconsistencies,

see “Handling workflow container inconsistencies” on page 112.
13.5.1 Changes in VIM Invoice Solution component structure

To reduce the number of components to be installed, some VIM components have
been restructured compared to VIM 7.5 / 7.6. VIM components OTVIMWUI and
OTVIMWSR (Fiori based Analytics report) are not supported anymore. If they are
installed on your system, remove them before upgrading.
Compared to VIM 16.3, only VIM Foundation components and components of

Solutions Beyond Invoice (Sales Orders and others) have been restructured, but not
Invoice Solution components. For more information on component structure of
Foundation and Solutions Beyond Invoice in “Upgrading“ on page 63.
The structure changes are different when upgrading from VIM 7.5 or from 7.6.
“Changes in VIM Invoice Solution component structure from VIM 7.5 to VIM 20.4”
on page 99 explains the changes in components structure, comparing VIM 7.5 up
to SP8, VIM 7.5 from SP9 to SP11, being upgraded to VIM 20.4.

13.5. Upgrading
on page 99 lists software components with technical release numbers applicable to
the respective VIM support package. If you are upgrading from VIM 7.5 SP8 and
older, follow each line for a component starting from the far left to find the changes
related to the component. When upgrading from VIM 7.5 SP9 to SP11, follow the
respective lines starting in the middle.
Table 13-5: Changes in VIM Invoice Solution component structure from VIM 7.5
to VIM 20.4
From To From To
7.5 up to 7.5 SP9- Comments 7.5 SP9- 20.4 Comments
SP8 SP11 SP11
OTBCUS03 OTBCUS03 OTBCUS03 - Included into
0740_004 0740_004 0740_004 OTBCWUI (VIM
Foundation)
OTBCSL33 OTBCSL33 OTBCSL33 OTEXVIM VIM Invoice,
0700_004 0700_005 0700_005 81610_106 Fiori apps
objects included
into OTEXVIM
OTBCSL03 OTBCSL33 VIM Invoice OTBCSL03 OTEXVIM VIM Invoice,
0700_004 0700_005 Fiori objects 0700_005 81610_106 Inbound objects
moved from included into
SL03 to SL33 OTEXVIM
OTBCSL03 VIM Invoice
0700_005 Inbound objects
remain in SL03
OTBCSL30 OTBCSL30 OTBCSL30 OTBCSL30
0700_004 0700_005 0700_005 81610_106
OTVIMWUI OTVIMWUI OTVIMWUI - Not supported
anymore, must
be uninstalled
before upgrade
(see the Note at
the end of this
table)
OTVIMWS OTVIMWS OTVIMWS - Not supported
R R R anymore, must
be uninstalled
before upgrade
(see the Note at
the end of this
table)
OTVIMARB OTVIMARB OTVIMARB OTEXVIM Included into
750 750 750 81610_106 OTEXVIM

From To From To
7.5 up to 7.5 SP9- Comments 7.5 SP9- 20.4 Comments
SP8 SP11 SP11
OTVIMARC New. Replaces
80700_006 the transport
package
provided earlier
OTVIMGW OTVIMGW OTVIMGW OTVIMGW
700 / 740 700 / 740 700 / 740 81610_106
OTVIMCDS OTVIMCDS OTVIMCDS OTEXVIM Included into
750 750 750 81610_106 OTEXVIM
OTVIMBW OTVIMBW OTVIMBW OTVIMBW
700 / 700 / 700 / 80700_006
700_730 700_730 700_730
OTBCSL38 New with SP9 OTBCSL38 OTBCSL38
0700_005 0700_005 80700_006
Note: To be able to uninstall the components OTVIMWUI and OTVIMWSR, you

first need to import ACP files that allow uninstallation. You can download
these files using the following link:
https://mimage.opentext.com/support/ecm/secure/patches/vim/oneoff/
vimi-23593/ACP_OTVIMWUI_OTVIMWSR.zip
Import the respective ACP files using the transaction SAINT on the systems
where the components are installed.
on page 100 explains the changes in components structure of VIM 7.6 being
upgraded to VIM 20.4.
Table 13-6: Changes in VIM Invoice Solution component structure from VIM 7.6
to VIM 20.4
From To
7.6 20.4 Comments
OTBCSL30 OTBCSL30 Compared to 7.6, contains only DDIC objects on
80700_006 81610_106 20.4
OTEXVIM All invoice inbound objects included into
81610_106 OTEXVIM
OTEXVIM OTEXVIM
80700_006 81610_106
OTBCSL33 OTEXVIM All Fiori apps objects included into OTEXVIM
80700_006 81610_106

13.5. Upgrading
From To
7.6 20.4 Comments
OTVIMCDS OTEXVIM Included into OTEXVIM
80700_006 81610_106
OTVIMARB OTEXVIM Included into OTEXVIM
80700_006 81610_106
OTVIMARC OTVIMARC Same component used, no need to upgrade
80700_006 80700_006
OTVIMGW OTVIMGW
80700_006 81610_106
OTVIMBW OTVIMBW Same component used, no need to upgrade
80700_006 80700_006
OTBCSL38 OTBCSL38 Same component used, no need to upgrade
80700_006 80700_006
13.5.2 Upgrading VIM 7.5/7.6 to VIM 20.4

In most cases, an upgrade of VIM 7.5/7.6 to VIM 20.4 is done during a conversion to
a new SAP S/4HANA version. For a description of this case, see “Upgrading to VIM
20.4 during an SAP S/4HANA conversion” on page 102.
For a description of an upgrade from VIM 7.5 to VIM 20.4 without an SAP S/
4HANA conversion, see “Upgrading VIM 7.5 to VIM 20.4 without conversion”
on page 104.
Important
For upgrades from VIM 7.5, an ACP file to modify the installation package
attributes is required if you were using any of the following additional
components:
• OTBCSL03
• OTBCSL33
• OTVIMARB
• OTVIMS4
• OTVIMCDS
You can download the ACP file from OpenText My Support: Patches > Vendor
Invoice Management > Vendor Invoice Management for SAP Solutions 20.4
> Invoice Solutions > ACP Files > OTEXVIM81610_106_UPG_75.SAR
If you purchased VIM through SAP and you are performing the upgrade with
SAP Maintenance Planner, the package attributes will be adjusted
automatically.

13.5.2.1 Upgrading to VIM 20.4 during an SAP S/4HANA conversion

This section describes the process to perform during an SAP S/4HANA conversion
with regards to VIM.
SAP S/4HANA In your environment, you might have VIM 7.5/7.6 installed in the system and plan to
conversion and run a conversion from SAP ERP to SAP S/4HANA. During the conversion, VIM
VIM licenses
needs to be upgraded to 20.4.
The following scenarios can apply:
You have purchased the VIM license from SAP

You need to make sure that you have a license for “SAP Invoice Management
for SAP S/4HANA by OpenText”. If you only have a license for “SAP Invoice
Management by OpenText”, you need to speak to your SAP sales representative
to convert the licenses.
The SAP Maintenance Planner should recognize the VIM add-ons and
download the VIM 20.4 add-on automatically.
You have purchased VIM licenses from OpenText directly
OpenText does not distinguish from a commercial perspective between VIM for
SAP ERP and VIM for SAP S/4HANA. No commercial conversion of the license
is required.
The SAP Maintenance Planner will not be able to automatically perform the VIM
upgrade because you do not have a VIM license from SAP. Consult the SAP
Note 2523380 - “Improvements to Rectify Erroneous Systems in Maintenance
Planner”.
OpenText also recommends that you check the latest version of the SAP Note
2721274 - “SAP S/4HANA conversion/upgrade planning for reseller Add-ons”.
Note: If there are issues with the SAP Maintenance Planner, open a ticket at
SAP for the component BC-UPG-MP. Clearly explain in the ticket if the
software was bought from SAP and Maintenance Planner does not proceed as
expected or if the software was bought from OpenText and help is needed how
to do the conversion for a partner add-on not licensed by SAP.
13.5.2.1.1 Preparing the conversion
Checking obsolete components

Review the VIM 20.4 Release Notes for obsoleted components and features. During
the conversion, objects removed from the VIM 20.4 package in comparison to VIM
7.5 may be deleted (by installation tools). Make sure that you only use supported
components and features.
OTVIMGW If you have installed the OpenText Gateway component for Supplier Self Service,
OTVIMGW, on your VIM 7.5 system, you must uninstall the Gateway component
before you begin the conversion. There is no upgrade path maintained for it in the
SAP Maintenance Planner, and the versions provided with VIM 7.5 are not

13.5. Upgrading
compatible with SAP S/4HANA. When the conversion is finished, install the
component OTVIMGW that is provided with the VIM 20.4 installation package.
Performing technical preparation
To update and activate tables in the system:
1. Run the SE11 transaction to check if tables /OPT/X052, /OPT/Y052, /OPT/Z052

exist in your system.
These tables are not part of VIM 7.5 but might be in the system from an older
VIM version.
2. If the tables exist, open the table definition, and check the data element for table
field CONFIG_LINE.
3. For each of the tables, change the data element for table field CONFIG_LINE from
VERI_LRAW to /OPT/LRAW2048.
4. Activate the tables.
13.5.2.1.2 Performing the conversion
You can perform the conversion to the following SAP S/4HANA versions:
Conversion to SAP S/4HANA 1610, 1709, 1809, 1909, or 2020
• Business Center needs to be installed at least on version 16.3. The Business

Center version needs to match the VIM Support Package version. For more
information, see the Release Notes.
• During the conversion, for VIM add-ons, the target version 20.4 or its later
Support Package needs to be selected in the SAP Maintenance Planner. The
process differs whether the VIM licenses were bought via SAP or OpenText.
For more information, see “Upgrading to VIM 20.4 during an SAP S/4HANA
conversion” on page 102.
Notes
– During conversion, in the SUM phase RUN_RSUPG_TADIR_

COMPONENT_CHECK, you might face messages like the following:
“719” “objects found without delivery transport” “for Software
Component” “OTEXVIM”
You can ignore these messages.
– See the Release Notes of VIM for compatibility of Business Center
components.
• For issues with the Maintenance Planner or SUM, open an incident at SAP
for component BC-UPG-MP.

• After the conversion, continue with the post installation steps after upgrade.
For more information, see “Post installation activities after an upgrade”
on page 105.
Performing the SAP S/4HANA conversion – For the actual SAP S/4HANA
conversion, use the guides provided by SAP.
13.5.2.2 Upgrading VIM 7.5 to VIM 20.4 without conversion

This section describes an upgrade of VIM 7.5 to VIM 20.4 that is done without an
SAP S/4HANA conversion. This may apply to customers who installed VIM 7.5 on
SAP S/4HANA 1610.
Prerequisites
• Component S4CORE is installed with release 101 or later.

• Support Package Manager (transaction code SPAM) minimum level 66
Note: OpenText advises against activating the complete BC set during the
upgrade without checking, because it might overwrite any changed standard
configuration. Instead you can detect missing entries manually, using the
compare functionality in the SCPR20 transaction.
13.5.2.2.1 Preparing the upgrade
To prepare the upgrade:
1. Check the installed component versions.
a. On the System menu, click Status, then click Components.

b. Check the versions of installed components.
2. Select required components and download the packages.

Collect all missing installation and Support Packages files as shown in
“Selecting required components and downloading the packages” on page 68.
Notes
• Several components of VIM 7.5 are now included in the OTEXVIM main
package: OTBCSL03, OTBCSL33, OTVIMARB, OTVIMCDS, OTVIMS4. If these
components are installed on your system, no action is required because
these are included into the main package.
• OTBCUS03 of VIM 7.5 is now included in the OTBCWUI OpenText Process
Fiori Base package. If OTBCUS03 component is installed on your system,
no action is required because it is included in the OpenText Process Fiori
Base package
• If the demo package OTVIMWSR is installed on your system, it needs to be
uninstalled. This demo component is not supported anymore.

13.5. Upgrading
13.5.2.2.2 Installing the package
For the installation steps that you need to perform, see “Installing the package”
on page 72.
If you perform the upgrade during an SAP S/4HANA conversion, also see
“Upgrading to VIM 20.4 during an SAP S/4HANA conversion” on page 102
13.5.2.3 Post installation activities after an upgrade

To complete the upgrade, you must perform and validate the following procedures:

• “Activating business configuration sets” on page 105
• “Checking status and runtime behavior of BAdIs for Invoice Processing”
on page 106
• “Reviewing BAdI for extended VAT date support” on page 106
• “Checking Inbound component” on page 107
• “Checking the logic module configuration” on page 107
• “Reviewing posting logic in current document types” on page 108
• “Reviewing parked processing” on page 108
• “Updating Fiori launchpad tiles” on page 108
13.5.2.3.1 Importing transport with Fiori layouts
After upgrading, you must import the following transport to the systems where you
have performed the upgrade. It is necessary for the Fiori apps to work.
You find post installation transports on the installation media / package under the
path Software\Invoice Solution\Postinstall.

Fiori Perspectives
13.5.2.3.2 Activating business configuration sets
Notes

The business configuration sets (BC sets) for post installation activities after an
upgrade are the following. All post installations sets of 7.5 Support Packages must
be executed and all BC sets must be activated.
Upgrading from OpenText recommends that you upgrade to VIM 7.5 SP6 before the upgrade.
VIM 7.5 < SP5
If this is not possible, it is possible to perform an upgrade to VIM 20.4. However it is
necessary to review the release notes for all VIM 7.5 support packages before SP6
that are not yet installed on your system and follow the post installation steps.
When finished, activate the BC set /OTEXVIM/VIM20_4_BASELINE.
13.5.2.3.3 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:

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

Status for Business Function /OPT/VIM_SFW_MIRO empty (in the SFW5 transaction).
13.5.2.3.4 Reviewing BAdI for extended VAT date support
The installation of VIM delivers a BAdI implementation for SAP BAdI VATDATE_
VALUES.
Note: The BAdI definition allows only one implementation to be active.

Importing this transport replaces the active standard implementation linked to
SAP class CL_BADI_EXM_VATDATE_VALUES_SAP. The OpenText implementation,
which becomes active, calls the standard class if a document is not being
posted from VIM. If you are using a custom implementation, OpenText
recommends that you activate it again and merge the logic of the OpenText
implementation into it.
When the target SAP release is SAP S/4HANA 2020 and later releases, an important
manual correction instruction must be implemented to adjust the implementation of
VAT date BAdI.

13.5. Upgrading
13.5.2.3.5 Checking Inbound component
The Inbound component is mandatory for VIM 16.3 and later versions. Do not use
the Incoming Document Handling (IDH) framework and the ICC Dispatcher
framework any longer.
Make sure that the Z constant 005 / BC_INBOUND is set to X. To do this, run the SM30
transaction for view /OPT/VIM_ZCONST.
For information about configuring inbound processes, see Section 6 “Incoming

document processing” in OpenText Vendor Invoice Management for SAP Solutions -
13.5.2.3.6 Checking the logic module configuration
VIM 7.5 introduced logic module processing. For more information, see Section 8.4
“Processing logic modules” in OpenText Vendor Invoice Management for SAP Solutions
- Configuration Guide for Invoice Solution (VIM-CGD).
As an upgrade customer on VIM 7.5, you might still be running VIM in a 7.0 mode
without logic modules. From VIM 16.3, this is no longer supported.
Check if the Z constant VIM_VERSION_SWITCH is set to 700. To do this, run the SM30
transaction for view /OPT/VIM_ZCONST. If the setting is 700, delete the Z constant.
VIM 16.3 has introduced new logic modules. Check the currently used document
types for correct logic module configuration. Add missing logic modules to your
configuration if necessary. As a reference, you can use the default document types
delivered in the main BC Set /OTEXVIM/VIM20_4_BASELINE.
In VIM 16.3, logic for enhancing initial data was moved to logic modules. Therefore
you have to include the following modules to your existing logic module
configuration:
PO Document Types
• Process line items from OCR

For more information, see Section 30.10 “Process Line Items from OCR” in
OpenText Vendor Invoice Management for SAP Solutions - Reference Guide for Invoice
Solution (VIM-RGD).
NPO Document Types
• Process Line Items from OCR.

For more information, see Section 31.4 “Process Line Items from OCR” in
OpenText Vendor Invoice Management for SAP Solutions - Reference Guide for Invoice
Solution (VIM-RGD).
• Enrich NPO Line Items

For more information, see Section 31.5 “Enrich NPO Line Items” in OpenText
Vendor Invoice Management for SAP Solutions - Reference Guide for Invoice Solution
(VIM-RGD).
13.5.2.3.7 Reviewing posting logic in current document types
VIM 16.3 has introduced a new posting logic for NPO and PO invoices using
logistics invoice verification.
OpenText recommends that you evaluate the new posting logic and switch
processing of invoices to the new logic.
For more information, see Section 32 “Posting invoices” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIM-CGD).
13.5.2.3.8 Reviewing parked processing
VIM 16.3 has replaced parked processing for NPO and PO invoices by processing
parked documents in DP. For more information, see Section 8.3 “Configuring parked
processing” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIM-CGD).
Old parked processes are no longer supported. Continuing their usage must be
evaluated and tested customer-specifically.
13.5.2.3.9 Updating Fiori launchpad tiles
If you use VIM Fiori apps, you must adjust the launchpad tile configuration. For the
current parameters, see “Fiori: Setting up Launchpad content on-premise”
on page 92.
13.5.3 Upgrading VIM 16.3 to VIM 20.4

You can upgrade from VIM 16.3 to VIM 20.4 independently of an SAP S/4HANA
upgrade, unless you are upgrading SAP S/4HANA to the release 2020. As it is only
VIM 20.4 that will support SAP S/4HANA 2020, you must upgrade VIM and SAP S/
4HANA at the same time.
Prerequisites
• Component S4CORE is installed with release 101 or later.

• Support Package Manager (SPAM transaction) minimum level 66
The following applies if you have purchased VIM licenses from OpenText directly:
It can happen that the SAP Maintenance Planner will not be able to automatically
perform the VIM upgrade because you do not have a VIM license from SAP. For
more information, see the SAP Note 2523380 - “Improvements to Rectify Erroneous
Systems in Maintenance Planner”.
OpenText also recommends that you check the latest version of the SAP Note
2721274 - “SAP S/4HANA conversion/upgrade planning for reseller Add-ons”.

13.5. Upgrading
Note: If there are issues with the SAP Maintenance Planner, open a ticket at
SAP for the component BC-UPG-MP. Clearly explain one of the following in the
ticket:
• The software was bought from SAP and Maintenance Planner does not
proceed as expected.
• The software was bought from OpenText and help is needed how to do the
conversion for a partner add-on not licensed by SAP.
13.5.3.1 Preparing the upgrade
To prepare the upgrade:
1. Check the installed component versions.
a. On the System menu, click Status, and then click Components.
b. Check the versions of installed components.
2. Select required components and download the packages. Collect all missing
installation and Support Packages files as shown in “Selecting required
components and downloading the packages” on page 68.
13.5.3.2 Upgrading
If you are upgrading VIM without an SAP S/4HANA upgrade, install VIM packages
following standard procedures. For the installation steps that you need to perform,
see “Installing the package” on page 72.
If you are upgrading VIM at the same time as upgrading SAP S/4HANA, select the
new VIM version and SP level (if SPs are available) in the component selection step
of the upgrade tool of your choice, typically SAP Maintenance Planner. Follow the
standard procedures as recommended by SAP.
13.5.3.3 Post installation activities after an upgrade

To complete the upgrade, you must perform and validate the following procedures:
• “Activating business configuration sets” on page 110
• “Checking status and runtime behavior of BAdIs for invoice processing”

on page 111
• “Updating Fiori launchpad tiles” on page 111
• “Adjusting BAdI for extended VAT date support” on page 111

13.5.3.3.1 Importing transport with Fiori layouts
After upgrading, you must import the following transport to the systems where you
have performed the upgrade. It is necessary for the Fiori apps to work.
You find post installation transports on the installation media/package under the
path Software\Invoice Solution\Postinstall:

Fiori Perspectives
13.5.3.3.2 Activating business configuration sets
Notes
Several BC sets are provided for upgrades. A full BC set containing complete
configuration is included into the main VIM installation package. Three delta BC
sets are provided for download in OpenText My Support under Resources > Patches
> Vendor Invoice Management > OpenText Vendor Invoice Management 20.4 >
Invoice Solutions > Additional Components:
/OTEXVIM/VIM1633_204_UPGRADE
Delta BC set for upgrades from VIM 16.3 SP3 to 20.4. Transport Q02K900159
/OTEXVIM/VIM20_4_BASELINE
Complete BC set. Use this BC set for all other upgrade scenarios.

13.5. Upgrading
13.5.3.3.3 Checking status and runtime behavior of BAdIs for invoice processing
Use the SE19 transaction to check the runtime behavior of the BAdIs. The following
table shows the standard values:

/OPT/ /OPT/
Implementation is not called
VIM_ENH_SPOT_MIRO CL_IM_VIM_BADI_MIRO
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).
13.5.3.3.4 Updating Fiori launchpad tiles
If you use VIM Fiori apps, you must adjust the launchpad tile configuration. For the
current parameters, see “Fiori: Setting up Launchpad content on-premise”
on page 92.
13.5.3.3.5 Adjusting BAdI for extended VAT date support
When the target SAP release is SAP S/4HANA 2020 and later releases, an important
manual correction instruction must be implemented to adjust the implementation of
VAT date BAdI.
13.5.4 ACP files

When performing upgrades of the SAP system or VIM components, conflicts
between the package attributes might arise. Such conflicts could not be foreseen at
the time when the packages were created. To resolve such conflicts, Attribute
Change Package (ACP) files are used. OpenText provides ACP files for different
product versions, either along with the product installation, or as a separate
download.
Table 13-7: ACP files for VIM 16.3
Component PAT file Comments

This ACP file allows an upgrade
to VIM 16.3/20.4 from VIM 7.5
OTEXVIM Q0200207762770000062.PAT
SP<XX>. It adds the attribute of
VIM 7.5 (OTEXVIM) “D”.

13.6 Troubleshooting
13.6.1 Table length restrictions for /OPT/VIM_1HEAD
This section applies if some custom fields have been added into VIM table /OPT/
VIM_1HEAD.
Historically, SAP systems were able to use different database back ends, each with
different capabilities. To support all of them, SAP imposes restrictions on table row
size. The most common limit for current releases is 4030 or 4096 characters. The
table /OPT/VIM_1HEAD as delivered by OpenText does not surpass the limit, but the
limit can be surpassed when custom fields are added through an append structure.
In this case, during the activation phase of VIM upgrade or support package
installation, you might get the following error in the activation log:
Table /OPT/VIM_1HEAD is too long (>4096)
All modern databases are able to handle longer rows, and it is possible to set a
different length limit according to your needs. If your upgrade is affected by the
restriction, see SAP Note 2458652 that explains the problem and describes the
procedure to solve it.
13.6.2 Handling workflow container inconsistencies

In certain cases, workflow containers of open VIM workflows may get inconsistent
as a result of an upgrade or a Support Package 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.
Notes
• If possible, finish the processing of all currently open DP documents before

upgrading the production system. Do not create new DP documents during
the upgrade procedure.
• For more information about upgrading, see the VIM 7.5 Upgrade Guide,
available on My Support: https://knowledge.opentext.com/knowledge/
llisapi.dll/Properties/61798981
Inconsistent data in workflow containers often results in short dumps. They happen
when, after an upgrade, a user tries to open a work item that was created before the
upgrade.
To solve the problem, the workflow containers can be processed by a special

program provided by SAP in SAP 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.

13.6. Troubleshooting
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.
13.6.3 Missing translations in line items of indexing screen

The field labels of the index screen are fully customizable. Line item labels are based
on the data element that is mapped to the field. To make use of this new feature, you
need to load the data element descriptions as the baseline configuration. You
perform this using the /OPT/VIM_MIGRATE_LABELS program in the SE38 transaction.
During installation of language packs, all labels should be available. If line item
labels are missing for a language, you can run this program.
• You can process the program for all available languages or for a set of languages.
• You can choose which languages you want to load in the selection screen.
• Running the program updates line item labels only, not header labels.
• After running the program, you must add the table entries in /OPT/IDX_ITM_T
into a customizing request manually to transport them to the rest of the systems
in the landscape.
Note: You can also add entries using an /OPT/SPRO node or the /OPT/VIM_
ITM_SCR_DES transaction. For more information, see Section 8.1.7
“Customizing field labels in the index screen” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIM-
CGD). In this case, the entries are automatically stored in a customizing
request.

13.6.4 Issue with loading Fiori apps

If the Fiori apps are not working, check the following:
• Check, if the PLDA post install transport is imported to the current client.
• Check if BC set /OTEXVIM/VIM20_4_BASELINE has been activated correctly,
including all Sub-BC-sets.

Chapter 14
Simple Mode VIM installation
This part describes the installation of Simple Mode VIM. For Simple Mode, all
Business Center components are mandatory. For more information, see “Installing
the package” on page 72.
14.1 Overview
Simple Mode provides additional apps, which are based on SAP Fiori:
VIM Vendor Invoices Workspace Fiori app

This app allows the expert accountant to access all invoices within the different
process steps (Validate / Process / Enter Cost Assignment / Approve) according
to role assignment. It provides a workplace-like view on the outstanding and
finished processes in a web browser. The following apps can all be accessed
from the Vendor Invoices Workspace app:
VIM Validate Invoices Fiori app
This app allows the validator to validate the invoice and to enter missing
information using a web browser.
VIM Process Invoices Fiori app
This app allows the accountant to resolve invoice exceptions, to bypass
rules, and to access the invoice in the SAP Fiori app Manage Supplier Invoices.
For more information, see https://fioriappslibrary.hana.ondemand.com/sap/
fix/externalViewer/#/detail/Apps('F0859')/S9OP.
VIM Enter Cost Assignment Simple Fiori app
This app allows users to code their invoices using a web browser or tablet
device.
VIM Approve Invoices Fiori app
This app allows users to approve their invoices using a web browser.
Notes
• Simple Mode processing happens only in Fiori, not in SAP GUI.

• The Fiori apps of Simple Mode are completely based on Business Center
components and configuration. No additional configuration in VIM is
required.

Chapter 14 Simple Mode VIM installation
14.2 Simple Mode installation

installing Simple Mode.
14.2.1 Prerequisites
Backend system
• Minimum SAP S/4HANA 1610 with the following components:
Component Minimum Minimum SP

Release Level
S4CORE 101 0002
SAP_BASIS 751 0002
• Support package manager (SPAM) version 75

• Check if the following SAP Notes are applicable. Install them if applicable:
– 0002452394 - Facade for supplier invoicing draft: No information about

postings to G/L accounts
– 0002492429 - Withholding tax: Error when posting an invoice with
invoice reduction
– 0002604781 - Create Supplier Invoice: BAdI
SUPPLIER_INVOICE_VALIDATION not called
– 0002531710 - Create Supplier Invoice: Draft ID transferred to BAdI
INVOICE_UPDATE.
– 0002503246 - SAP Fiori app 'Create Supplier Invoice': Technical correction
for RBKP-ROOT_KEY
– 0002658164 - Supplier factsheet - overflow in annual spend
– 0002511288 - Logistics invoice verification APIs: Check for duplicate
invoices
– 0002515311 - Customizable messages for SAP Note 0002511288
– 0002658658 - Supplier Invoice Draft Facade: Duplicate invoice check
– 0002475974 - Namespace not converted in odata metadata service
– 0002377545 - Supplier Invoice draft facade: Message 076
(APPL_MM_IV_MODEL) not displayed correctly
– For installation on SAP S/4HANA 1809: 0002719086 - Supplier Invoice
Draft Facade: Dump when posting an invoice

14.2. Simple Mode installation
Table 14-1: Installed VIM components
Component Release SP level

OTBCBAS 0700_006 0000
OTBCSL00 0700_006 0000
OTBCSL30 81610_106 0000
Notes
• For more information, see “VIM classic mode installation“ on page 67

and “Installing the package” on page 72.
• You can install the Classic VIM component OTEXVIM in parallel.
Frontend system
• Minimal UI5 version: For the supported UI5 version, see the Business Center
Release Notes.
• Installed and configured SAP Fiori app Manage Supplier Invoices. For more
information, see the Fiori Apps Library.
• Installed and configured SAP Fiori fact sheet Supplier. For more information,
see the Fiori Apps Library: https://fioriappslibrary.hana.ondemand.com/sap/
fix/externalViewer/#/detail/Apps('F0354')/S11OP
• Installed and configured SAP Fiori app Purchase Order (Version 2). For more
information, see the Fiori Apps Library: https://
fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/
Apps('F0348A')/S13OP
Table 14-2: Installed OpenText Process Fiori Base component
Component Release SP level

OTBCWUI 0740_006 0000
14.2.2 Installing the Simple Mode components

The following add-ons need to be available on the same backend system as the
Simple Mode add-on on the latest Support Package level: OTBCBAS, OTBCSL00,
OTBCSL30.
The following add-on needs to be available on the frontend system: OTBCWUI.
For more information, see “Selecting required components and downloading the
packages” on page 68.
To install the Simple Mode components:
1. Download the following installation file:

Component Release Filename OCS Package Password

OTBCSL08 81610_106 OTBCSL08_INST SAPK-106COIN 8A87C936A7
_UPG_81610_106 OTBCSL08
.SAR
2. Collect the latest post installation transports, available in the installation

package/media under the path Software\Invoice Solution\Postinstall.
Binary name Transport Description Install on Deploymen

t scenario
OTBCSL08_ Q12K900028 Simple Mode VIM Back end On-premise
PostInstallati - Fiori perspectives
on_FIORI_ layouts
Perspectives_
20_4.zip
OTBCSL08_ DA5K900072 Simple Mode VIM Back end On-premise
PostInstallati - Launchpad
on_FIORI_ content for on-
Launchpad_ premise
Content_20_4.
zip
OTBCSL08_ Simple Mode VIM Back end On-premise
WebIDE_ - WebIDE
Templates_20_ Templates
4.zip
3. Collect the languages for OTBCSL08. They are delivered together with all other
languages for Invoice Solution. For more information, see “Language packs”
on page 94.
4. Install VIM – Simple Mode:
a. Install the add-on OTBCSL08 and all support packages using the SAINT
transaction.
If the Business Center components described in “Prerequisites” on page 116
are not installed on the system, install all add-ons with all Support
Packages at once.
b. Follow the instructions in “Installing“ on page 37 regarding post
installation activities like BC sets activation, service activation, and so on.
c. Activate the BC set /OTX/PS08_INVOICE_106 using the SCPR20 transaction.
This BC set is cumulative, it is not necessary to activate BC sets from lower
support packages.
d. Import the post installation transports to all clients where the apps are
intended to run. See Step 2 on page 118.
e. Install the language pack for component OTBCSL08.
f. Perform the customizing as described in Part V “Simple Mode VIM” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
for Invoice Solution (VIM-CGD).

g. Also perform the customizing as described in Part I “General features and

configuration” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Solutions Beyond Invoice (BOCP-CCS).
5. Set up the Fiori Launchpad tiles for the Simple Mode based Fiori apps.
The general setup is described in Section 10.1.1 “Integrating Fiori Task App into
Fiori Launchpad” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Foundation (BOCP-CGD).
When setting up tiles for VIM, you need to know specific parameters for each
Fiori app. The parameters are listed in the following table:

Vendor PS08_PRC_INV PS08_INV_WP
Invoices
Workplace[a]
Validate PS08_INV_VAL_A PS08_VAL_INV_HD WP_INBOX
Invoices DV
Process PS08_INV_PRC PS08_PRC_INV WP_INBOX
Invoices
Approve PS08_INV_APPR PS08_APPR_INV WP_INBOX
Invoices
Enter Cost PS08_INV_CODE PS08_CODING_INV PS08_INV_COD_WP
Assignment
[a]
The Vendor Invoices Workplace tile is also delivered with transports; see Step 2 on page 118.
You can access them on My Support. For details, see “On premise” on page 59.
14.2.3 Post installation activities

14.2.3.1 Maintaining standard text
The standard text is client dependent. Copy it 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.
The following texts are delivered as a template for the Vendor Reject Functionality
(only English). For more information, see Section 20.4 “Maintaining email
templates” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIM-CGD) and Section 20.6 “Maintaining the email
signature” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIM-CGD). If you want to use custom specific texts, you
may skip copying the following texts.
• /OTX/PS08_RTV_TEMPLATE
• /OTX/PS08_RTV_SIGNATURE

To maintain standard text:
1. Run the SO10 transaction.
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.

Click .
4. If a dialog box like the following opens, click Yes.
5. Click the Back button on the confirmation page.
6. Repeat the steps for all standard text shown in the list above.
14.2.4 Update
For updating Simple Mode from any 16.3 version to 20.4, follow the steps in
“Installing the Simple Mode components” on page 117.
The BC Set of 20.4 delivers new process profile settings, which overwrite the existing
profile. Before activating the new BC Set, save any custom specific customizing
especially in the Process Profile Customizing (roles or country specific
characteristics, and so on). For more information, see Section 7 “Process
Configuration” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Foundation (BOCP-CGD)
If you are upgrading during a system conversion of your SAP S/4HANA version, a
warning during phase RUN_RSUPG_TADIR_COMPONENT_CHECK for component
OTBCSL08 might occur. Several obsolete objects (especially in package /OTX/PS80)
were deleted in version 20.4. Therefore, you can ignore this message for component
OTBCSL08.
14.2.5 Troubleshooting
This section collects possible problems with the installation of Simple Mode. It also
provides information how to solve these problems.

14.2.5.1 Possible problem during upgrade

Problem When upgrading to Simple Mode, the following error may occur in the browser
console when opening the Fiori apps: Failed to append view 'ot.approve.
requests03.view.item.Document' since the parent control with id
'splitter' does not exist in template 'undefined'.
To solve the problem:
1. Use the Business Center app Perspective Manager to delete all perspectives of
type ITEM starting with PS08 for the current client.
2. Re-import the post installation transport for Perspective Layouts in the
current client.

Chapter 15
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 27 “KPI Dashboard” in OpenText Vendor Invoice
Notes
• The KPI Dashboard is not supported in the VIM 7.5 version for SAP S/
4HANA on Premise.
• The KPI Dashboard is an optional component.
• If you are not using the KPI Dashboard, you can skip this part.
15.1 Installing the KPI Dashboard

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

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

Chapter 15 KPI Dashboard installation
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.
To activate the service:
1. To activate the Web Dynpro service on the SAP S/4HANA system, run the SICF
transaction.

2. In Virtual Host, enter default_host and click Execute.
3. In the tree, select sap > bc > webdynpro.

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

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:

• Logon Errors
• Application Errors
• Logoff Page
• Not Accessible

15.2.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.
Do not change the service settings described in “Activating the SAP Web Dynpro
service” on page 123. Make sure that the SSL settings are not activated in the Logon
Data tab.
Change the KPI constant DASHBOARD_START_URL to https://xxxxx:8443/xxxx. See

Section 27.4.10.5 “KPI Dashboard start URL” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide for Invoice Solution (VIM-CGD).

15.2.3 Setting up the SAP NetWeaver Portal integration

Use Internet Explorer 8 (or higher) for setting up the SAP NetWeaver® Portal
integration for the KPI Dashboard on NetWeaver 7.0 and login to the SAP
NetWeaver Portal as Administrator.
A System Object is needed to integrate the KPI Dashboard in the SAP NetWeaver
Portal. The System Object is a set of connection properties to represent an external or
SAP system (SAP R3, CRM, BW) used to retrieve data into portal iViews. If not
existing, you must create a System Object in the NetWeaver Portal.
Note: If you use an SAP NetWeaver Portal version higher than 7.0, refer
directly to the SAP Portal documentation. Follow the description of creating an
iView type based on a Web Dynpro ABAP application.
15.2.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.

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

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.
15.2.3.2 Adding the Portal component
To add the Portal component:
1. In the SAP NetWeaver Portal, navigate to Content Administration > Portal

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

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

Chapter 16
OpenText Approval Portal installation
This chapter describes the installation of the OpenText Approval Portal component.
The Approval Portal is designed to work within SAP NetWeaver Application Server
Java (NWAS) 7.3 or 7.4 or SAP NetWeaver Portal (NWP) 7.3, 7.4, or 7.5.
The Approval Portal can be deployed as a standalone application residing on NWAS

only or as an application inside NWP using AppIntegrator iView. Install all the
components in a coordinated manner.
Notes
• The Approval Portal is an optional component.
• If you are not using the Approval Portal, you can skip this part.
• Please refer to Section 7.8 “Administering the Approval Portal” in OpenText

Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-
AGD) for administering and troubleshooting the Approval Portal.
• You might want to install multiple instances of the Approval Portal on the
same SAP NetWeaver Portal. In this case, contact OpenText Customer
Support.

16.1.1 Installation prerequisites
A complete installation and configuration of OpenText Vendor Invoice Management
is needed for installing and testing the Approval Portal. Although it is possible to
install the Approval Portal before the installation and configuration of the SAP S/
4HANA 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.3 SP3 or above and NWAS
7.4 SP3 or above. For SPNego configuration, see SAP Note 1488409.
SAP NetWeaver Portal

SAP NetWeaver Portal (NWP) 7.3 SP3 or above and NWP 7.4 SP3 or above and
NWP 7.5.

Chapter 16 OpenText Approval Portal installation
Notes
• Approval Portal 20.4 JCO3 Java 1.8 and Approval Portal 20.4 Java 1.8
packages are supported only in NWAS 7.5 and NWP 7.5.
• The requirement “SPx or above” does also refer to the EhP level.
• For further information, see the SAP Note: 994791-SPNego Wizard.
Supported The following list shows the supported resolution modes that have been tested in
Screen the OpenText R&D lab. The resolution modes have been tested in all supported
Resolution
browsers.
1. 1280 x 800 - Laptop view

2. 1920 x 1080 - Laptop view
3. 1680 x 1050 - Desktop view
4. 1280 x 1024 - Desktop view
Web browsers The following matrix shows the web browsers and versions that are supported by
the new interface of the Approval Portal, which is delivered since VIM 7.0 SP2. The
matrix is based on tests performed at OpenText R&D Lab. It considers accessibility
and usability aspects.
Browser and Version

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

supported. Approval Portal supports all versions.
Note: The new Approval Portal has not been tested in Unix environment.
Aligned with SAP operating system support, see the SAP Product Availability
Matrix (PAM) for more details.

SSL OpenText recommends implementing SSL (HTTPS) if security is a concern. Basic

Authentication in SPNego is using Base64 encryption which can be easily decrypted.
Sizing require- Standard sizing requirements for NWAS or NWP 7.3 apply.
ments
SAP user An SAP CPIC user in the SAP S/4HANA server
The communication with the SAP S/4HANA system is accomplished by using a

CPIC user ID. However, the Web user is recorded as the agent who approved an
invoice, not the CPIC user.
User type
Communication Data (CPIC)
Profile
Create a profile with the following authorization objects and add it to the CPIC
user:
Object: S_RFC
Activity
Execute (16)
Names of RFC to be protected
/OPT/VIM_FG1A2, /ORS/*, /OPT/*, /ORS/SAPL000007_APPR_SCREEN, /
PTGWFI/*, OPTB, ARFC, ERFC, RFC1, SDIFRUNTIME, SUNI, SYST, SYSU
RFC_TYPE
FUGR (Function Group)
Object: S_CPIC
Activity
Accept, Initialize (37 and 51)
Name of an ABAP/4 FORM routine
CPIC
Symbolic destination
*
If you wish to narrow this down, examine table TXCOM and choose entry
under the SDEST field that represents the destination of the system you are
communicating with.
Program Names with Search Help
/ORS/*, /OPT/*, /PTGWFI/*
Object: S_DATASET (Authorization for file access)
Activity
Read, Write (33 and 34)
Filename
* (physical file name)

Program Names with Search Help

/ORS/*, /OPT/*, /PTGWFI/*
The following 2 authorization objects for the CPIC user are applicable for SAP
ERP 702 SP14 and higher and SAP NetWeaver Portal 702 SP15 and higher:
Object: S_RZL_ADM (Authorization object for R/3 system administration)
Activity
Display (03)
Object: S_WF_SUBST (Workflow: substitute rule)
Activity
Display (03)
Additional SAP Standard Profile needed: S_A.CPIC and S_A.USER
Note: If you are using an Archive Server to pull in images, you may need
to assign additional roles. See the Archive Server Installation manual.
Example: OpenText™ Archive Center provides the following profiles that need to
be assigned to the CPIC user to access images:
• S_AL_ADMLO (Display SAP ArchiveLink® administrator)

• 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

16.1.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 20.4 SPx installation package
For all Support Packages of VIM 20.4, the respective OpenText Vendor Invoice
Management 20.4 Support Package folder on My Support provides an
installation package of the VIM 20.4 SPx Approval Portal in the Web and
Mobile Approval Component folder.
16.1.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:

Figure 16-1: Approval Portal architecture with NWAS
The SAP help pages linked in the following discuss some of the communication
channels between each component:
• Simple and Protected GSS API Negotiation Mechanism (SPNEGO) (https://

help.sap.com/doc/saphelp_nw73ehp1/latest/en-US/b3/
728d0e84f34b70891819cb77b61e2f/frameset.htm)
• Network and Transport Layer Security (https://help.sap.com/viewer/
bd0c15451669484cbc84a54440340179/latest/en-US/
4b6858bc8ec53260e10000000a42189b.html)
• SAP Java Connector (JCO) (https://help.sap.com/viewer/
db5b67e2690e4c0f8254813e9b1e05fb/latest/en-US/
4870792c872c1b5ae10000000a42189c.html)

Figure 16-2: Approval Portal architecture with NWP
Note: Approval Portal can be used if the SAP NetWeaver Portal is configured
to use SAML-based authentication. No specific VIM configuration is required
in this case. For more information on SAML, see the SAP documentation.
16.1.3.1 SAP user requirements

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

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

No need for SAP GUI Logon ID. Only Portal ID is required.

Dual Stack installation (SAP ABAP and Java Stack) utilizing integrated
authentication
SAP GUI Logon ID required. Dual Stack forces to use SAP user management
based on ABAP Stack.
Standalone J2EE application residing on NWAS with NWP utilizing integrated
authentication by accessing application directly without iView
No need for SAP GUI Logon ID; only network ID is required.
16.2 Installing Web Viewer/Brava! View for the

Approval Portal
To display invoice images, you can integrate OpenText™ Imaging Web Viewer
(Web Viewer) into the Approval Portal. The Approval Portal supports Web Viewer,
version 10.5, 16, and 20.3.
Important
If you have not installed Web Viewer or Brava! View, OpenText recommends,
as a general advice, that you create PDF files from scanning and use the PDF
viewer that is installed on your computer for displaying invoice images.
Note: When using Web Viewer, OpenText recommends that you use the latest
patch of the supported Web Viewer software version.
As an alternative, you can use OpenText™ Brava!™ View for SAP Solutions (Brava!
View).
• To install Web Viewer 10.5, 16, or 20.3, download the software from OpenText
My Support.
• For the Web Viewer installation, see the appropriate section in Section 3
“Installing Web Viewer” in OpenText Imaging Web Viewer - Installation and
Configuration Guide (CLWEBV-IGD).
• To install Brava! View 16.2 or 20.3, download the software from OpenText My
Support.
• For the installation of Brava! View, see Section 2 “Installing Brava! View for SAP
Solutions” in OpenText Brava! View for SAP Solutions - Installation and
Configuration Guide (BRWEBV-IGD).
• To apply the latest patch for Web Viewer, download the software from OpenText
My Support.
• It is necessary to install Archiving and Document Access for SAP Solutions 10.5.
For more information, see OpenText Archiving and Document Access for SAP
Solutions - Installation and Upgrade Guide (ER-IGD).
• You perform the configuration that is necessary for the Web Viewer integration
in the /IXOS/OA_CUST_A archive tables in SAP ERP. For a description of the
configuration, see Section 17.2 “Configuration for Web Viewer” in OpenText
Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS).

16.3. Installing the Approval Portal
Note: Web Viewer 16 and Brava! View 16.2 versions are not supported on the
Mobile Approval Portal. For more details on Web Viewer and Brava! View
support, see the Web Viewer Support and Brava! View Support sections in the
Release Notes.
16.3 Installing the Approval Portal

16.3.1 JCo3 migration considerations
VIM 20.4 Approval Portal supports the SAP Java Connector 3 (JCo3) and 3.1.
• JCo3 by framework takes care of Connection Management Handling, and all JCo
destinations are created on SAP NetWeaver Administrator Portal.
• JCo3 destination configuration and pool parameters are maintained at SAP

NetWeaver Administrator Portal. For more information, see Section 7.8.1.2 “SAP
Connection for JCo3” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD).
• A minimal JCo3 destination configuration is maintained on the Approval Portal

Admin Console. For more information, see Section 7.8.1.2 “SAP Connection for
JCo3” in OpenText Vendor Invoice Management for SAP Solutions - Administration
Guide (VIM-AGD).
• The JCo3 package is completely aligned with JCo2 package, having all
functionalities, except connector usage.
• The JCo3 migration is based on SAP Note 549268.
Choose one of the following Approval Portal packages on My Support:
• JCo3.1 version package with Java 1.8: IM_APPROVAL_PORTAL20_4_JCo3_JAVA1_

8.zip
• JCo3 version package with Java 1.6: IM_APPROVAL_PORTAL20_4_JCo3.zip
Table 16-1: JCo3 compatibility matrix for versions 7.6 and 20.4 of the Approval
Portal
Approval Portal version 7.6 / 20.4

JCo3 + Java 1.6
JCo3 + Java 1.8
JCo3.1 + Java 1.6

JCo3.1 + Java 1.8

16.3.2 Preparing the installation

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

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

The <Approval_Portal_installdir> folder contains the following files:
configuration.xml
containing all the configuration for the application
Note: Each Approval Portal Support Package (SP) delivers an
configuration.xml file. If you overwrite your existing file, your
settings will be gone. If you keep the old file, you may be missing
some new options introduced for the new SP. See the Release Notes of
the respective SP if the file can be left as it is or if it must be merged to
incorporate the new settings.
mobileconfiguration.xml
containing all the configuration for mobile support
RequestMappings.xml
OpenText strictly recommends not to modify this file. The Approval Portal
application internally uses this file.
Lang_Support.properties
containing all the mapping of languages code; see Section 7.8.4.2
“Configuring additional languages” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD) for details.
Lang_DE.properties
containing all the text for the German language resource
Lang_EN.properties
containing all the text for the English language resource

Lang_ES.properties
containing all the text for the Spanish language resource
Lang_FR.properties
containing all the text for the French language resource
Lang_IT.properties
containing all the text for the Italian language resource
Lang_JA.properties
containing all the text for the Japanese language resource
Lang_NL.properties
containing all the text for the Dutch language resource
Lang_PT.properties
containing all the text for the Portuguese language resource
Lang_RU.properties
containing all the text for the Russian language resource
Lang_ZH.properties
containing all the text for the Chinese language resource
There might be more .properties files, depending on the package and the
release for additional languages. The language resource files can be changed.
See Section 7.8.4.1 “Changing language resources” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for details.
Important
Make sure the <Approval_Portal_installdir> folder has:
• correct permissions for the J2EE application to write and read

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

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

• INSTANCE_NAME is the NWAS instance in the format of JCxx, where

xx is the instance number (example JC00).
The script file is:
• configtool.bat for Windows hosts

• configtool.sh for Unix hosts
a. Add the startup parameter to the Java parameters on the server: -Dcom.
opentext.vim.portal.invoiceCfg=<Approval_Portal_installdir>.
Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/opentext/
invoiceCfg
b. Save the new parameter.
3. To apply the new startup parameter, restart the NWAS.
Restarting informs the server that the <Approval_Portal_installdir> folder
contains application specific information.

16.3.3 Configuring the administrator role

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

This section describes how to create a VIM administrator role and assign it to the
domain user through NWAS Visual Administrator. For a description of the
necessary steps with SAP NetWeaver 7.3 and 7.4, see “Configuring the
Administrator Role for Access Through NWAS for SAP NetWeaver 7.3 and 7.4”
on page 150.
You must perform this configuration before deploying the .sca or .sda, to ensure
that the application recognizes the role.
To create the Administrator role:
1. Log in to J2EE Visual Administrator and navigate to Instance > Server >
Services > Security Provider.
2. Click on the Edit button.

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.

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 152.
• Navigate to http://<NWAS>:<NWASPORT>/vimportal/admin.

If you see a screen similar to the one above, you have configured the
administrator role successfully.
16.3.3.2 Configuring the Administrator Role for Access Through NWAS

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

Identity Management

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.

16.3.4 Deploying the Software Component Archive

Deploying the Software Component Archive comprises the following steps:
• “Optional: Starting the Approval Portal J2EE application manually” on page 152
• “Optional: Clearing the browser cache” on page 152
16.3.4.1 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.
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.
16.3.4.2 Optional: Clearing the browser cache

You might face browser cache issues when you have upgraded from one Approval
Portal version to another Approval Portal version. In this case, it is necessary to clear
the browser cache. As the administrator, guide the end users to perform the
following steps to avoid browser cache issues on the particular browsers that are
supported for the Approval Portal.
To clear the cache on Internet Explorer:
1. Open Internet Explorer.
2. On the Tools menu, click Delete browsing history. Alternatively, press CTRL
+SHIFT+DEL.
3. In the Delete Browsing History dialog box, select the check boxes, as shown in
the following screenshot.
Make sure that the Preserve Favorites website data check box is cleared.

4. Click the Delete button. Then wait for the browser to clear the cache.
To clear the cache on Firefox:
1. Open Mozilla Firefox.
2. Press CTRL+SHIFT+DEL.
3. In the Clear All History dialog box, select the check boxes, as shown in the
following screenshot.
Make sure to select Everything in the Time range to clear list.

4. Click the Clear Now button. Then wait for the browser to clear the cache.
To clear the cache on Chrome:
1. Open Chrome.
2. Press CTRL+SHIFT+DEL.
3. In the Clear browsing data dialog box, select the check boxes, as shown in the
Make sure to select the beginning of time in the Obliterate the following
items from list.

4. Click the Clear browsing data button. Then wait for the browser to clear the
cache.
16.3.5 Deploying the Software Component Archive with SAP

NetWeaver 7.3
To deploy the Software Component Archive with SAP NetWeaver 7.3:
1. Make sure the .sca file is placed in D:\usr\sap\trans\EPS\in.

2. To start the Java Support Package Manager, navigate to usr/sap/<SID>/
<INSTANCE_NAME>/j2ee/jspm
Notes

The script file is:
• go.bat for Windows hosts

• go.sh for Unix hosts

3. Enter user name and password.
4. Click New Software Components, and then click Next.

If the component is already deployed, no applicable software component is
found.
If the component is not yet deployed, click Next to deploy the component.

5. Click Start.

6. In the Completed screen, click Exit.
16.3.6 Deploying the Software Component Archive using SUM

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

guiconsole.bat.
2. Authenticate using Administrator credentials.
3. Enter the following command:

undeploy name=<Folder Name> vendor=<Vendor Name>

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

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

the jump_config file.
b. Change the parameter value /sapstartsrv/httpsconnection from true
to false and save the changes.
6. Navigate to <drive>:\usr\sap\<SAP instance>\SUM\. Run the STARTUP.bat
file using Run as administrator and wait until SL Controller started is
displayed at the command prompt.
7. To open the SUM tool, access the following URL: http://<NW Host>:1128/
lmsl/sumjava/<Instance ID>/index.html.
Example: http://localhost:1128/lmsl/sumjava/d9e/index.html
A new SUM UI is started.
Notes
• The process stops several times. Restart it repeatedly.

• SUM restriction
The SUM tool is valid until you completely finish deploying. You can
always stop and restart without any issues. However, if you want to use

the same SUM that you have previously used for deploying, it will not
work.
Click Log on.

8. For Role Administrator, create a Name and Password. Click OK.
Click Next.
9. Specify Credentials
Enter User Name and Password.
Note: Make sure that you heed the Additional Information.
Click Next.
10. Select Target
Select the Manually prepared directory check box. Click Browse, navigate to
the OpenText Approval Portal package directory, and click OK.
Cross check the selected path and click Next.
11. Initialization - System Analysis
Click Next.
12. Extraction - Initial Software Extraction
Click Next.
13. Configuration - Information Gathering
Enter the AS Java Administrator Password and click Continue.
Note: This is not the same password that was configured for the SUM
authentication.
A step list is executed. Wait until Select Components is displayed. Click

Continue.

16.4. Configuring SAP NetWeaver Portal components
Another step list is executed. Wait until Component Status is displayed. Click
Continue.
Another step list is executed. Wait until System Parameters are displayed. Click
Continue.
Another step list is executed. Wait until a success message is displayed. Click
Next.
14. Checks - Requirements Check
A step list is executed. Wait until a success message is displayed. Click Next.
15. Preprocessing - Update Preparation
A step list is executed. Wait until Begin Update is displayed. Click Continue.
Click Next.
Another step list is executed. Wait until a success message is displayed. Click
Next.
16. Execution - Actual Update
A step list is executed. Wait until a success message is displayed. Click Next.
17. Postprocessing - Post-Update Activities
A step list is executed. Wait until Update Complete is displayed. Click
Continue.
Wait until a success message is displayed. Click Next twice.
18. Summary and Evaluation of the Process
Summary and Feedback Form are displayed. Click Next.
You can send an email to SAP. To finish the package installation, click Exit.
A summary page is displayed.
16.4 Configuring SAP NetWeaver Portal components

If you are deploying the Approval Portal on SAP NetWeaver Application Server
Java (NWAS) and the users are accessing the application through SAP NetWeaver
Portal, you must configure the SAP NetWeaver Portal components.
For a description of the configuration with SAP NetWeaver 7.3, 7.4, and 7.5, see
“Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and 7.5”
on page 168 and “Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5”
on page 182.
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 162

• “Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and 7.5”
on page 168
• “Creating roles for users” on page 178
• “Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5” on page 182
• “Assigning roles to SAP NetWeaver Portal users” on page 185
• “Configuring iViews and roles for the administrator” on page 186
• “Administering the OpenText Approval Portal” on page 187
16.4.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.
3. Right-click on the new folder and select New > iView.

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.

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

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

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:

$host$
NWAS server name where the Approval Portal J2EE application was
deployed
$port$
Port of that NWAS
Note: Do not change <User.UserID>.
12. Click Save and Close.

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

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

Management > Portal Content > Content Provided by SAP > End User
Content.

3. Right-click End User Content, point to New, and then click Folder.

4. On the New Folder tab, enter Folder Name and Folder ID Prefix (for example,
com.opentext); then click Finish at the bottom of the page.
5. After creating the Approval Portal folder, navigate to Content Administration

> Portal Content Management > Portal Content > Portal Applications

6. In Portal Applications, expand com.sap.portal.appintegrator.sap

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

The wizard of the PCD Object opens.

10. Change the Object Name to Approval Portal Iview.

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

11. To configure the newly created iView, right-click ApprovalPortalIview, then

click Open > Properties.

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

14. Configure the following parameters:
HTTP Request Method

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

To make the iView visible, select the Entry Point check box.

16.4.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 162.
2. Right-click on the folder, select New > Role.

3. In Step 1, enter Role Name, Role ID, Role ID Prefix and Description.
Select the Master Language.
Notes
• See also Step 7 on page 165 in “Creating AppIntegrator iViews for

users” on page 162.
• Role ID Prefix is not mandatory. If you enter this parameter, you must
search by giving Role ID Prefix and Role Name when assigning the role
to the user.
4. Click Next.

5. Click Finish.
6. Click Open the object for editing and click OK.

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 162, right-click the iView and select Add iView to Role > Delta
Link.
Click Save.
The AppIntegrator iView is added to the role.
9. Click Close.

16.4.4 Creating roles for users with SAP NetWeaver 7.3, 7.4,
and 7.5
After creating a new AppIntegrator iView, you must create a role and add the
AppIntegrator iView to the role.
To create roles for users with SAP NetWeaver 7.3, 7.4, and 7.5:
1. In the SAP NetWeaver Portal, navigate to the Approval Portal folder; see
“Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and
7.5” on page 168.
2. Right-click on the folder, select New > Role > Freestyle Role.

3. Enter properties as shown in the screenshot above: Role Name, Role ID, Role
ID Prefix and Description.
Select the Master Language.
Note: Role ID Prefix is not mandatory. If you enter this parameter, you
must search by giving Role ID Prefix and Role Name when assigning the
role to the user.
4. Click Finish.

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.

7. Select the AppIntegrator iView created in “Creating AppIntegrator iViews for

users with SAP NetWeaver 7.3, 7.4, and 7.5” on page 168, right-click the iView
and select Add iView to Role > Delta Link.
Click Save.
The AppIntegrator iView is added to the role.
8. To create an Admin role, repeat Step 1 to Step 7. Enter the relevant name for the
Admin role.
9. Click Close.
16.4.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 178).
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.

16.4.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?urlView=Y&PORTALUSER=<User.
UserID>
See Step 11 on page 167 for details on the URL template for users.
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 185.

16.5. Applying a new patch
When you, as the administrator, navigate to the Approval Admin iView, it will look
like the following screenshot:
You have now finished the installation and configuration of the OpenText Approval
Portal.
16.4.7 Administering the OpenText Approval Portal

For information on the administration of the Approval Portal, see Section 7.8
“Administering the Approval Portal” in OpenText Vendor Invoice Management for SAP
Solutions - Administration Guide (VIM-AGD).
16.5 Applying a new patch

Note: Unlike the VIM SAP S/4HANA 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 S/4HANA component. Approval Portal 7.5 will only
work with the VIM 7.5 SAP ERP component.
New .sca file or .sda file

Follow the steps to undeploy the .sca or .sda file in “Uninstalling using
Software Deployment Manager” on page 190, and then deploy the .sca file
or .sda file.

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 7.8 “Administering the Approval Portal” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for more details.
16.6 Upgrading the Approval Portal from previous

versions
The Approval Portal upgrade procedure is simple:
• Undeploy the old and deploy the new .SCA file, and
• Freshly install the OpenText installation directory.
Note: Consider supported landscapes, browsers, and other configuration

before upgrading.
Direct upgrades from previous versions to 7.5 are possible.
Approval Portal 7.0 (new UI) to 7.6

Undeploy the old and deploy the new .SCA file. You can reuse the existing
OpenText installation directory.
Approval Portal 7.5 to 7.6
Undeploy the old and deploy the new .SCA file. You can reuse the existing
OpenText installation directory.
Make sure that all files mentioned in opentext.zip are deployed correctly.
For an upgrade from Approval Portal 7.0 (new UI) to 7.6, you can reuse the original
configuration.xml file. However, it is best to make a backup of the
configuration.xml. For all other upgrade paths, OpenText recommends that you
use the new configuration.xml.
If you changed the language properties files from the previous version and would
like to reuse them in VIM 7.5, change the new language properties files manually.
To upgrade, perform the actions described in “Applying a new patch” on page 187.

16.7. Troubleshooting
16.7 Troubleshooting
For information on troubleshooting the Approval Portal, see Section 9.11.12
“Troubleshooting” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD).
16.8 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 3.1.4.1 “User Details
View” in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
for Invoice Solution (VIM-CGD).
Example: If the Windows Domain column in the COA table is not maintained for users,
leave the Domain field in the Configuration tab of the Approval Portal Administration
console empty as well.
16.9 Uninstalling the Approval Portal

To uninstall the Approval Portal, perform the following steps:
• “Uninstalling using Software Deployment Manager” on page 190

• “Uninstalling with SAP NetWeaver 7.3, 7.4, and 7.5” on page 191
• “Removing SAP NetWeaver Portal components” on page 192
• “Deleting properties files” on page 193
• “Optional: Removing the startup parameter in the Config Tool” on page 193

16.9.1 Uninstalling using Software Deployment Manager

This section describes how to uninstall the .epa and .ear files from the SAP
Software Deployment Manager (SDM) repository. For a description of uninstalling
with SAP NetWeaver 7.3, 7.4, and 7.5, see “Uninstalling with SAP NetWeaver 7.3,
7.4, and 7.5” on page 191.
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.
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.

16.9. Uninstalling the Approval Portal
16.9.2 Uninstalling with SAP NetWeaver 7.3, 7.4, and 7.5

This section describes how to undeploy the Approval Portal with SAP NetWeaver
7.3, 7.4, and 7.5.
To undeploy the Approval Portal with SAP NetWeaver 7.3, 7.4, and 7.5:
1. Navigate to D:\usr\sap\W73\J00\j2ee\console\ and run guiconsole.bat.
2. Enter user name and password.

3. In the J2EE Engine Console, type list_app to view the list of components that
are deployed.
4. To undeploy, run the following command:

undeploy name=IM_APPROVAL_PORTAL7_0 vendor=opentext.com
After undeployment, a success message is displayed.

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

16.9. 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.
16.9.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 144 for details on the
properties files.
16.9.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 145 in “Preparing the installation”
on page 144.
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:

• configtool.bat for Windows hosts

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

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

Chapter 17
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 7.9
“Configuring the Mobile Approval Portal” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD).
17.1 Introduction to the Mobile Approval Portal

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

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

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

System
iOS (5.1.x or later) iPad Safari (5.1.x or later) A

Chapter 17 Mobile Approval Portal installation
Mobile Operating Device Browser Category

System
iOS (5.1.x or later) iPhone Safari (5.1.x or later) A
Android (6.0.x or later) Any Android device[a] Chrome (23.0 or later) B
and Supported
browsers
[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.
Web Viewer Mobile Approval Portal users can display invoices using OpenText Imaging Web
integration Viewer.
Important
Web Viewer is a web application for displaying and printing documents in Web-
based scenarios and for appending comments to these documents. The documents
may be stored in OpenText Archive Center or other repositories.
The Web Viewer integration is completed for the invoice document and supports all
documents supported by Web Viewer.
On the Mobile Browser without Web Viewer, it is not possible to render TIFF
documents. JPG, PNG and GIF documents are supported to be shown in browser by
default. To support PDF documents, a specific browser-plugin or a separate viewer
app is needed.
However, Web Viewer is able to display TIFF documents on the Mobile Browser on
Mobile Approval Portal.
Web Viewer is installed on a web server. It generates HTML pages containing the
document to be displayed and sends them to the browser. The Web Viewer can be
used by any leading application server configured appropriately.
Web Viewer supports documents from the following products:
• OpenText™ Archiving and Document Access for SAP Solutions

• OpenText™ DocuLink for SAP Solutions
Limitations
• Web Viewer does not support MS Office documents.

• For attachments, the Web Viewer integration is not implemented. Any attached
document, like PDF, JPEG, GIF or PNG, will be forced to open in a separate
browser window by default.

17.1. Introduction to the Mobile Approval Portal
Notes
• OpenText 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).

Figure 17-1: HTML5 Mobile Approval Portal Architecture

17.2. Authentication for the Mobile Approval Portal
17.2 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 135
17.3 Installing Web Viewer for the Mobile Approval

Portal
OpenText Imaging Web Viewer can be integrated in the Mobile Approval Portal.
Important
To ensure security for the Web Viewer integration, OpenText recommends that you
verify the “Use Signature” setting in /IXOS/OA_CUST_A with the following
prerequisites:
• Archiving and Document Access for SAP Solutions (OTEXBAS) 10.5

• OpenText Imaging Web Viewer 10.5, 16, or 20.3, latest patch.
• OpenText Archive Services Patch ASR-1021-007 or later (as included in
Enterprise Library 10.2.1 Patch Collection 1021_2012_04)
Notes
• OpenText recommends that you use the latest patch available for these
versions.
• See also the Release Notes of Archiving and Document Access for SAP
Solutions 10.5.
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.5, 16, or 20.3, download the software from OpenText My
Support.
To apply the latest patch for Web Viewer 10.5, 16, or 20.3, download the software
from OpenText My Support.
Notes
• OpenText recommends that you use the latest patch of the supported Web
Viewer software version.
• OpenText also recommends installing Web Viewer on a NetWeaver 7.3, 7.4,
and 7.5 instance where Mobile Approval Portal is not running or on a
supported Tomcat version. This approach improves the performance of
viewing invoice images on Mobile devices.
• OpenText also recommends installing Web Viewer on the same domain as
the Archive Center and SAP NetWeaver Application Server Java.
• Web Viewer 16 and Brava! View 16.2 versions are not supported on the
Mobile Approval Portal. For more details on Web Viewer and Brava! View
support, see the Web Viewer Support and Brava! View Support sections in
the Release Notes.
17.4 Installing the Mobile Approval Portal

Installing the Mobile Approval Portal differs depending on the application server
you use:
• Standalone SAP NetWeaver Application Server Java (NWAS)

• SAP NetWeaver Portal
17.4.1 Installing the Mobile Approval Portal on standalone

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

17.4. Installing the Mobile Approval Portal
17.4.2 Installing the Mobile Approval Portal on SAP NetWeaver

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

7.3 SP8 or higher
All higher support packages and enhancement packages of NetWeaver 7.3, 7.4,
and 7.5.
Approval Portal
7.5
17.4.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.3/7.4/7.5 customers, deploy/configure the SPNego

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

17.4.2.3 Scenario 2: Enabling Mobile Approval Portal for new customers

1. For SAP NetWeaver Portal 7.3/7.4/7.5 customers, deploy/configure the SPNego
login module.
Refer to “Installing the Mobile Approval Portal on standalone NWAS 7.3/7.4”
on page 200 for specific SAP NetWeaver Portal versions.
2. Deploy the Approval Portal with the officially supported Support Package.
3. Access the Mobile Approval Portal URL in a supported smartphone / tablet.

Chapter 18
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.
The same procedure must be followed when upgrading the component OTVIMBW
from the following earlier versions:
• OTVIMBW 700
• OTVIMBW 700_730

The following prerequisites must be fulfilled for the installation of the VIM BW
component.
18.1.1.1 VIM BW add-on prerequisites

• The following components must be installed for SAP NetWeaver BW 7.5 or SAP
NetWeaver BW 7.5 on HANA (lowest release/SP listed):
Table 18-1: SAP NetWeaver BW 7.5 or SAP NetWeaver BW 7.5 on HANA
Option Component: SAP_BW Component: SAP_BASIS

Release Support Package Release Support Package
1 750 SAPK-75004INSAPBW 750 SAPK-75005INSAPBAS
IS
• The Add-On BI_CONT ‘Business Intelligence Content’ must be installed in a

suitable version, for example:
BI_CONT 757 for SAP NetWeaver BW 7.5 or SAP NetWeaver BW 7.5 on HANA.
For installations on or conversions to SAP S/4HANA, an ACP file to modify the

installation package attributes is required. You can download the ACP file from
OpenText My Support: Patches > Vendor Invoice Management > Vendor Invoice
Management for SAP Solutions 20.4 > Invoice Solutions > ACP Files >
otvimbw80700_006_acp_s4.sar

Chapter 18 Vendor Invoice Management SAP NetWeaver Business Warehouse component installation
18.2 Installing or upgrading the OpenText package

This chapter describes the installation or upgrade of the package OTVIMBW on an SAP
NetWeaver BW application server.
To install or upgrade the OTVIMBW package:
1. Locate the OTVIMBW component SAR file on the installation media in the folder
Software\Invoice Solution\ABAP Addons. In the SAINT transaction, load
the .SAR file from the front end. Alternatively, extract the .PAT file from
the .SAR file and put the .PAT file into the application server transport directory
\usr\sap\trans\EPS\in.
2. Add the support packages (if available) to the queue, using the same procedure.
Adding support packages at this point saves time and is a safer variant of the
installation.
3. Carry out the import of the package as described in the respective SAP
documentation.
18.3 Verifying the installation

Make sure that the VIM BW add-on is reflected in the installed components.
To verify the installation:
1. From the SAP menu, open System > Status.
2. In the System: Component information dialog box, you should see the OTVIMBW
add-on component installed, with Release number 80700_006.
18.4 Uninstalling the VIM BW add-on package

The following components must be installed on the system with the following
minimal versions:
• AOFTOOLS 500_740 SP2

• SAINT/SPAM 7.5/070
• OpenText component OTVIMBW 80700_006. If you have earlier version of OTVIMBW
installed, see older version of the Installation Guide for information on
uninstalling.

18.4. Uninstalling the VIM BW add-on package
18.4.2 Steps before uninstalling

1. Delete all entries with eventid = '/OPT/%' from table btcued.
2. Delete all entries with eventid = '/OPT/%' from table btcuev.
18.4.3 Uninstalling the VIM BW package

To uninstall the add-ons, you can use the SAINT transaction.

Chapter 19
Vendor Invoice Management BW/4HANA add-on
component installation
This part describes the installation of the Vendor Invoice Management BW/4HANA
add-on (VIM BW/4HANA) component.
19.1 About the VIM BW/4HANA add-on

SAP BW/4HANA is an evolution of BW that is completely optimized and tailored to
SAP HANA. The SAP BW/4HANA code can only run on SAP HANA as it is
interwoven with SAP HANA engines and libraries. SAP BW4/HANA is a new SAP
BW product, it is not a successor of any old SAP BW version including SAP BW on
HANA Database, for example SAP BW 7.x on HANA.
Figure 19-1: History of SAP HANA with BW
The VIM BW/4HANA add-on delivers the same content as the content delivered by
VIM BW 7.0. While VIM BW 7.0 can be installed on BW 7.5 systems (also on HANA
database), VIM BW/4HANA 100 can be installed on a SAP BW/4HANA system. The
version number 100 implicates that the add-on is created for a BW/4HANA system
installed with component DW4CORE version 100.
The VIM BW/4HANA component is a new add-on for the new SAP product BW/
4HANA. It is not the successor of any VIM BW add-on, therefore the upgrade from
any earlier VIM BW add-on to BW/4HANA is impossible.
All custom views and queries created for the VIM BW add-on must be recreated
again using the new Composite Providers delivered in the VIM BW/4HANA add-

Chapter 19 Vendor Invoice Management BW/4HANA add-on component installation
on. Tools for creating BW frontend reports must be SAP tools compatible with the
SAP BW/4HANA platform.
The OLTP (source) system for VIM BW/4HANA must be an SAP S/4HANA system
installed with VIM 16.3 or later.
To check or edit objects delivered in VIM BW/4HANA, you need BW Modeling

Tools, for example in Eclipse or SAP HANA Studio.
The following list shows the main differences between the two VIM add-ons:
• The VIM BW/4HANA add-on is content delivered for the new SAP BW/4HANA
product, not for other SAP BW versions.
• The VIM BW/4HANA content is communicated with the OLTP system using
ODP Framework. ODP-enabled DataSources (ODP – SAP Extractors) are used
instead of BW Extractors.
• PSA (Persistent Source Area) is not supported any more. Data load from source
system will be written directly in advanced DSO.
• Obsolete objects in VIM BW 7.0 are replaced by VIM BW/4HANA objects:
– DSO replaced by advanced DSO
– InfoCubes replaced by advanced DSO
– Composite Providers are delivered instead of old Multi Providers.
– All transformations are either converted or created for the new objects
– All DTP (Data Transfer Processes) are created for new objects.
• Like in VIM BW 7.0, the VIM BW/4HANA 100 content provides the same set of
Query Variables, which can be used in queries to offer the user a selection
regarding the variables.
• Process Chains are created for new VIM BW/4HANA objects. Their names in the
BW/4HANA version begin with /OPT/VIM_B4H. Their purpose is the same as
the two meta process chains delivered in VIM BW 7.0.
19.2 Packaging and delivery information

The software and documentation for the VIM BW/4HANA add-on includes the
following:
• SAR file OTVIMBW4_INST_100_004.SAR
• TR D02K900158 - Convert VIM DataSource to ODP-enabled
• Documentation: this part of OpenText Vendor Invoice Management for SAP Solutions
- Installation Guide (VIM-IGD).

19.3. Supported environments and compatibility
19.3 Supported environments and compatibility

This section provides details about supported platforms, systems, and versions.
19.3.1 Supported systems

The system must be installed with SAP BW/4HANA 1.0 or later:
Table 19-1: SAP BW/4HANA components
Option Component: DW4CORE Component: SAP_BASIS

Releas Support Package Releas Support Package
e e
1 100 SAPK-10001INDW4CORE 750 SAPK-75005INSAPBASIS
19.3.2 OpenText product compatibility

This section provides details about which versions of other OpenText products are
compatible with this release of the VIM BW/4HANA add-on.
Note: For the latest compatibility information for OpenText products, refer to
the Compatibility Matrix on My Support: https://knowledge.opentext.com/go/
matrix.
Product name Version Notes

Vendor Invoice Management 16.3 HANA database
19.3.3 Language support

The VIM BW/4HANA add-on is currently available in English.
19.4 Installing the VIM BW/4HANA add-on component

This section describes the installation of the VIM BW/4HANA add-on component.
For detailed information how to install a package, refer to the SAP documentation.

19.4.1 Password control

The VIM BW/4HANA add-on is protected with a specific password. During
installation, this password is requested by the SAP Add-On Installation Tool
(SAINT).
SAP_BASIS DW4CORE Password

750 100 8099C151BF
19.4.2 Checking VIM BW/4HANA prerequisites

• The following components must be installed for SAP NetWeaver BW/4HANA:
Table 19-2: SAP BW/4HANA components
Option Component: DW4CORE Component: SAP_BASIS

Releas Support Package Releas Support Package
e e
1 100 SAPK-10001INDW4CORE 750 SAPK-75005INSAPBASIS
• BW/4HANA BI content add-on BW4CONT 100 must be installed.
19.4.3 Installing the OpenText package

19.4.3.1 OLTP (source system)
Import the following transport on the source system using transaction code STMS:
D02K900158 – Convert VIM Datasource to ODP-enabled
You find the transport in the file Transport_to_convert_OTVIMBW_DS_to_

OTVIMBW4.zip, in the installation package/media under the path Software\Invoice
Solution\Postinstall.
Note: This transport will be included into the VIM package as soon as the
uninstallation of objects is supported by SAP tools.

19.4. Installing the VIM BW/4HANA add-on component
19.4.3.2 OLAP (BW/4HANA) system

Refer to “Vendor Invoice Management SAP NetWeaver Business Warehouse
component installation“ on page 203. There is no significant difference between
installing VIM BW 7.0 and VIM BW/4HANA 100.
To install the OLAP system:
1. Download the SAPCAR file OTVIMBW4_INST_100_004.SAR from the folder BW/

4HANA Add-On Component OTVIMBW4 on My Support.
2. Call transaction SAINT (in client 000). On the initial screen, which shows the
installed components, load the package OTVIMBW4_INST_100_004.SAR from
Front End using the menu Installation Package > Load packages > SAR
archives from Front End.
3. Click Start to install the OpenText OTVIMBW4 component.
4. After installing, verify that the system is successfully installed: On the menu,
click System > Status. Click the Component icon for the Product Version, all
components are displayed:
Note: Uninstalling the VIM BW/4HANA component is supported starting with

SAP Support Package Manager - Version 7.50/0073. OpenText recommends
that you upgrade AOFTOOLS to the newest version, from AOFTOOLS 500_740: SP
0004 and later.

19.5 Upgrade notes

The VIM BW/4HANA component is a new add-on for the new SAP product SAP
BW/4HANA. It is not the successor of any VIM BW add-on, therefore the upgrade
from any earlier VIM BW add-on to VIM BW/4HANA add-on is impossible.

Chapter 20
Vendor Invoice Management component for SAP
NetWeaver Gateway installation
This part describes the installation of the Vendor Invoice Management SAP
NetWeaver Gateway package (VIM GW). The VIM GW component is needed to run
the Supplier Self Service component.
Note: This component is not supported in the VIM 7.5 version for SAP S/
4HANA on Premise.
Figure 20-1: Supplier Self Service architecture

Chapter 20 Vendor Invoice Management component for SAP NetWeaver Gateway installation

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).
SAP_BASIS Password
751 and later 8099C251AB

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

The following knowledge is required for the person dealing with the installation as
described in this document:
• In-depth knowledge of SAP administration tasks, in particular the SAP Add-On

Installation Tool (SAINT)
• Basic knowledge of the employed operating system
20.1.2.2 VIM Gateway prerequisites

• For general information on the installation of the SAP NetWeaver Gateway

components, see the SAP Help.
• The following components must be installed for SAP NetWeaver Gateway:
• Implement SAP note 1744864: Multiple Origin for Generated BOR/RFC Objects
does not work
Table 20-1: SAP components (OTVIMGW)
Option Component: SAP_GWFND

Release Support Package
1 751 -

20.2. Installing the OpenText package
20.1.2.3 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), which can be extracted using the SAPCAR command line tool.
The SAR files can also be used directly in transaction SAINT.
20.2 Installing the OpenText package

To install the OpenText VIM GW package:
1. Copy the respective SAPCAR file (OTVIMGW_81610_106.SAR) from My Support 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_81610_106.SAR.
4. To add the VIM GW component, click Continue.
5. Choose the package for component OTVIMGW. Carry out the import of the
package as described in the respective SAP documentation.

Make sure that the VIM GW add-on is reflected in the installed components.
1. From the SAP menu, open System > Status.
2. Click next to Component version.

In the System: Component information dialog box, you should see the OTVIMGW
add-on component installed, with Release number 81610_106.

Chapter 20 Vendor Invoice Management component for SAP NetWeaver Gateway installation

Make sure that namespace /OPT/ is modifiable.
Therefore, run the SE03 transaction, and, under Administration, run Set System
Change Option.
The value for namespace /OPT/ must be Modifiable.

Chapter 21
Vendor Invoice Management Supplier Self Service -
Lean Variant component installation
This part describes the installation of the Vendor Invoice Management Supplier Self
Service - Lean Variant component.

21.1.1 Installation prerequisites
A complete installation and configuration of OpenText Vendor Invoice Management
is needed for installing and testing the Supplier Self Service. Although it is possible
to install the Supplier Self Service before the installation and configuration of the
SAP S/4HANA and Gateway component, you will not be able to verify if the
installation of the Supplier Self Service is completed and correct.
The Supplier Self Service lean variant is enabled for multiple deployment options:
• HANA Cloud Deployment (runs on SAP HANA Cloud Platform)

• On-Premise (runs on SAP ABAP NetWeaver)
Operating This section covers support and restrictions of Supplier Self Service in regards to
system and operating systems and web browsers.
browser support
• The Supplier Self Service web application does not support any mobile operating
systems. It does not support any other operating systems than Windows.
Therefore, Mac/iOS, Linux, and Android operating systems are not supported.
• For supported browsers, see SAP note 1716423: SAPUI5 Browser Support for
Mobile and Desktop Applications
• Some additional browser settings are necessary:
Firefox
You must customize the language preferences: Go to Tools > Options, and
click the Content tab. In the Languages area, click Choose.
Add languages from the Select a language to add list. When performing
an HTTP request, Firefox will send all the languages chosen with the Accept-
Language header in the order of preference in which they are arranged in the
list.
Windows Internet Explorer 9
The website might appear blank or might not be displayed correctly. In this
case, set and use the Compatibility View on the menu bar of the browser:

Chapter 21 Vendor Invoice Management Supplier Self Service - Lean Variant component installation
– 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.
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 21.1.3 “Configuring Gateway users” in OpenText Vendor Invoice
21.1.2 Installation components

For the cloud deployment option, a WAR file (Web application ARchive) is supplied.
It is used to distribute a collection of Java Servlets, JavaScript files, XML files, and
other resources that together constitute the Supplier Self Service web application.
The on-premise application is part of the GW 740 package, and will be automatically
deployed to the ABAP stack.
21.1.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 21-1: Supplier Self Service system architecture

21.2. Installation on the SAP HANA Cloud
If you plan to use the On-Premise deployment, skip “Installation on the SAP HANA
Cloud” on page 219.
21.2 Installation on the SAP HANA Cloud

The SAP HANA Cloud Platform is an in-memory cloud platform based on open
standards. The platform is Java EE 6 Web Profile certified and provides a secure,
scalable runtime environment with reusable platform services. Therefore, Supplier
Self Service can run on the SAP HANA Cloud Platform just like on any Java-based
application server.
Note: You need an SAP account for accessing the SAP HANA Cloud.
21.2.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.
21.2.2 Deploying the application on the SAP HANA Cloud

Server
You deploy the application on the Cloud by using the SAP HANA Cloud Cockpit.
You must deploy the vimsupplierselfservice package in the form of a WAR file.
Deploying the Supplier Self Service application publishes it to the SAP HANA
Cloud Platform. For more information, see https://help.hana.ondemand.com/help/
frameset.htm?abded969628240259d486c4b29b3948c.html
To deploy the application:
1. Log on to the cockpit, and click Java Applications in the navigation area.
2. In the Java Applications panel, click Deploy Application.

Chapter 21 Vendor Invoice Management Supplier Self Service - Lean Variant component installation
3. In the Deploy Application dialog box, select the specific WAR file
vimsupplierselfservice.war to deploy. Initially the Cockpit proposes the
same name as for the WAR file. OpenText recommends that you enter the
application name vim3s but you can choose any other identifier you want.
Note: The application name must start with a letter, can contain lowercase
letters and numbers only, and must not exceed 30 characters. You can also
assign a display name and a description to the Java application.
4. Optional Specify additional parameters to configure the application. If omitted,

default values are assigned. For more information about the deploy parameters,
see the deploy command documentation https://help.hana.ondemand.com/
help/frameset.htm?937db4fa204c456f9b7820f83bc87118.html.

21.2. Installation on the SAP HANA Cloud
5. Click Deploy to deploy the WAR file to the cloud platform. The Deploy
Application dialog box remains on the screen while the deployment is in
progress. When the deployment is finished, a confirmation appears that the
application has been successfully deployed.
Note: At this stage, the application is not yet up and running.
Next steps To make your deployed application available for requests, you must start it inside
the SAP HANA Cloud Cockpit. For more information, see Section 21.2
“Customizing the HANA Cloud Server (option)” in OpenText Vendor Invoice
You can update or redeploy the application with a new WAR file or make changes
to the configuration parameters whenever required. To open the Deploy
Application dialog box in update mode, click Update application.
21.2.3 Installing the SAP HANA Cloud connector

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

as described in the following online help: https://help.hana.ondemand.com/help/
frameset.htm?e6c7616abb5710148cfcf3e75d96d596.html
Note: OpenText strongly recommends that you use the latest version of the
SAP HANA Cloud connector software. Due to known security vulnerability
risks, do not use any version of SAP HANA Cloud connector earlier than 2.4.1.

Chapter 22
Vendor Invoice Management electronic invoices
This part describes the installation of the Vendor Invoice Management electronic
invoices component.
Currently, this covers Italian FatturaPA, German XRechnung, and generic electronic
invoice (UBL). For general information about e-invoicing, see Section 10 “Processing
electronic invoices” in OpenText Vendor Invoice Management for SAP Solutions -
Scenario Guide for Invoice Solution (VIM-CCS).
22.1 General package for electronic invoices

Support for processing electronic invoices is delivered with VIM support packages
as listed per country in the following table. Check the corresponding Release Notes
for additional requirements.
Country Latest VIM SP Transport delivery

Italy, FatturaPA VIM 7.5 SP9 / VIM 16.3 SP3 yes
Germany, XRechnung (UBL) VIM 7.5 SP9 / VIM 16.3 SP3 yes
Generic (UBL) VIM 7.5 SP10 / VIM 16.3 SP4 yes
UN-CEFACT Version 1 VIM 7.5 SP11 / VIM 16.3.5 yes
UN-CEFACT Version 2
(including XRechnung in VIM 7.5 SP11 / VIM 16.3.5 yes
CEFACT format)
Transport based deliveries are provided on OpenText My Support. The important

difference is that apart from product status tracking, support packages provide
configuration as BC sets, allowing selective activation. Configuration transports can
be installed only completely.
OpenText recommends that you implement the e-invoicing support by upgrading to

VIM 7.5 SP9, VIM 16.3.3, VIM 7.6 or VIM 20.4 and optionally installing the SAP
Document Compliance integration component (OTBCSL38) as described in
“Installation” on page 225.
The minimum supported VIM release and support package levels for the transport
deliveries are VIM 7.5 SP7 with Business Center 16.3 Update 1, and VIM 16.3 with
Business Center 16.3.
For more information about the transport deliveries, see VIM 7.5 SP11 or VIM 16.3.5
Installation Guides that are provided on OpenText My Support.

Chapter 22 Vendor Invoice Management electronic invoices component installation
22.2 Inbound component: Integration with SAP

Document Compliance
SAP Document Compliance is a component offered by SAP to help companies
integrating their SAP ERP and SAP S/4HANA systems with electronic invoice
delivery networks and platforms. OpenText supports the integration of SAP
Document Compliance and VIM on the inbound side, automating the tasks of
invoice entry. The data of the electronic invoices is mapped to corresponding VIM
fields and the DP process is started for further steps like verification, approvals, and
invoice posting.
The objects for integration with SAP Document Compliance are delivered as a new
component OTBCSL38. Before the installation, make sure that you installed and
configured the prerequisites.
The component OTBCSL38 requires the Inbound component, which is provided as

the component OTBCSL30 with VIM 7.6 and included directly into VIM 20.4. In both
cases, you need to install the Process Base and Solution Base components (OTBCBAS
and OTBCSL00). For more information, see “Installation” on page 225 and the
Release Notes.
The following table lists the SAP notes to be implemented for specific scenarios. It
assumes that you have already installed and configured SAP Document
Compliance / eDocument Framework.
Note: You find the most current list of the SAP notes in SAP documentation
and support documents.
Note Scenario
2777052 - eDocument: Prerequisites for SAP Note 2765690 General
2765690 - eDocument Framework (21) General
2771424 - eDocument Italy: Enhancements for Incoming
Italy
Invoices
2690949 - eDocument Germany - EU eInvoicing: Overview Note Germany
2690993 - eDocument Germany - EU eInvoicing: Prerequisite for
Germany
SAP Note 2613785
2613785 - eDocument Germany - EU eInvoicing Germany
2690958 - eDocument Germany - EU eInvoicing: Configuration
Germany
and Customizing
2805582 - eDocument Germany - EU eInvoicing: Corrections Germany
2618098 - eDocument EU: Prerequisite for SAP Note 2523477 General/PEPPOL
2523477 - eDocument EU: eInvoice General/PEPPOL

22.2. Inbound component: Integration with SAP Document Compliance
Note Scenario
2432169 - eDocument EU: ABAP Proxy Objects General/PEPPOL
2433472 - eDocument EU: Prerequisite for SAP Note 2390901 General/PEPPOL
2390901 - eDocument EU: AIF Implementation General/PEPPOL
2440686 - eDocument EU: AIF Customizing General/PEPPOL
2442063 - eDocument EU: AIF Setup General/PEPPOL
2778717 - eDocument EU: AIF Interface Connector
General/PEPPOL
Implementation
2783795 - eDocument EU PEPPOL: Installation Overview General/PEPPOL
2813297 - eDocument EU: Prerequisites for SAP Note 2805188 General/PEPPOL
2805188 - eDocument EU: eInvoice Corrections General/PEPPOL
2423423 - eDocument Netherlands - EU eInvoicing: Prereq. for
Netherlands
SAP Note 2438748
2438748 - eDocument Netherlands - EU eInvoicing Netherlands
2420449 - eDocument Netherlands - EU eInvoicing:
Netherlands
Configuration and Customizing
2819556 - eDocument Netherlands: Enablement for Push
Netherlands
Scenario
2805560 - eDocument Netherlands - EU eInvoicing: Corrections Netherlands
For electronic invoices delivered over PEPPOL (Germany, Netherlands, Belgium),

also implement the notes marked as “General/PEPPOL”.
22.2.2 Installation
If you have purchased VIM through SAP, you can download the installation
package from SAP Marketplace. In case you purchased VIM directly from OpenText,
install the component OTBCSL38 using the SAINT transaction or with other tools like
SAP Maintenance Planner.
SAR file name: OTBCSL38_80700_006.SAR
Password: 8B87C935A7
Activate the BC set /OTBCSL38/EDOCU_INTEGRATION_SAP.

Chapter 23
Vendor Invoice Management ARIBA integration

VIM can be integrated with Ariba® Network. For detailed information about the
integration, see Section 23 “Integration with the Ariba Network” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution (VIM-
CGD). When you have decided which integration scenario you want to use, you can
perform the appropriate installation and configuration steps as described in the
following sections.
For the web-services-based integration (formerly known as Business Suite Add-On

integration), no additional components need to be installed in VIM 16.3 and later, as
the integration components are being delivered with the core VIM package. You
only need to run the post-installation steps described in “Post installation activities
for Business Suite add-on” on page 227. This consists of activating the BC sets and
activating the BAdI implementations.
Note: Ariba Business Network Integration adapter is supported by SAP until

December 31, 2021. OpenText can support this integration option until the
mentioned date only. OpenText recommends that you plan the transition to
Ariba Cloud Integration Gateway in the near future.
If you decide to use PI-based integration, or for Ariba CIG integration, you must
import additional transports. For more information, see the sections later in this
guide.
23.1 Post installation activities for Business Suite

add-on
23.1.1 Activating business configuration set
Note: For every client, you must activate a new BC set.
To activate the BC sets:
1. Login to your productive clients (in English).
2. Activate the BC Set /OTEXVIM/VIM20_4_BASELINE_ARIBA.
Note: Consider the most recent Release Notes for latest information on new BC
sets and additional post installation activities.

Chapter 23 Vendor Invoice Management ARIBA integration component installation
23.1.2 Activating BAdI implementations

The Ariba integration is delivered inactive in the standard VIM installation. To be
able to integrate VIM with the Ariba Network, you need to activate two BAdI
implementations in the SAP customizing (SPRO transaction).
To activate BAdI implementations for the Ariba integration:
1. Run the SPRO transaction and navigate to the following node: Integration with
Other SAP Components > Business Network Integration > Integration with
the Ariba Network > Application-Specific Settings > Business Add-Ins
(BAdIs) > BAdI: Outbound Mapping
2. In the Outbound Mapping, select the Active check box (very first column) for
the implementation /OPT/EH_E_ARB_BADI_OUTB_MAPS4.
In case of an SAP S/4HANA conversion from SAP ERP, if you already had the
Ariba integration component OTVIMARB installed, you might have the older
implementation /OPT/EH_E_ARB_BADI_OUTB_MAP active in the Outbound
Mapping. To set it to inactive, clear the check box.
3. Switch to BAdI: Inbound Mapping.
4. To activate the inbound BAdI implementation /OPT/EH_E_ARB_BADI_INB_MAP,

select the Active check box (very first column).

23.2. Importing ABAP workbench objects, PI scenario
23.2 Importing ABAP workbench objects, PI scenario

This section deals with the Vendor Invoice Management integration with Ariba, PI
scenario objects. This section describes the installation of the additional objects
required to integrate VIM with Ariba Network using the SAP NetWeaver Process
Integration adapter scenario (PI) and Ariba Cloud Integration (CI) components.
Note: Ariba Cloud Integration adapter is supported by SAP until December

31, 2021. OpenText can support this integration option until the mentioned
date and only on releases supported by SAP. OpenText recommends that you
plan the transition to Ariba Cloud Integration Gateway in the near future.
You can select Ariba CI components to be used for your Ariba integration project
with the PI scenario. If you need to send status updates from SAP S/4HANA back
into the Ariba Network, you need to import a set of transports and then adjust the
VIM configuration as described in Section 23.2 “Integrating the Ariba SAP
NetWeaver Process Integration adapter” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide for Invoice Solution (VIM-CGD). The adapter
version CI-8 and later is supported.
Because of dependencies on the Ariba CI-8 adapter, OpenText delivers the necessary
ABAP workbench objects as a separate set of transport files. You find the transport
files on My Support.
The delivery of the transport files is provided with VIM 7.5 SP5. This scenario is
supported by VIM 7.0 SP3 and VIM 7.5 SP1 and later VIM versions, including 16.3
and 20.4. You can use the provided transport files with the mentioned older VIM
versions and SPs.
To import the transport files:
1. On My Support, access VIM 7.5 SP5 and Ariba Cloud Integration with PI.
2. Download the transport files.
3. Perform the import in the following sequence:
1. EW3K901050
2. EW3K901080
3. EW3K901083
4. After the import, perform additional configuration steps as described in Section

23.2 “Integrating the Ariba SAP NetWeaver Process Integration adapter” in
Invoice Solution (VIM-CGD). Additional information is available in an
integration white paper, which describes the different integration options and
the necessary configuration. The white paper is available for integration
partners on My Support: https://knowledge.opentext.com/knowledge/cs.dll/
Overview/38761889.

Chapter 24
Vendor Invoice Management integration with Ariba,
CIG scenario objects installation
This part describes the installation of the additional objects required to integrate
VIM with Ariba Network using the Ariba Cloud Integration Gateway (CIG).
SAP Ariba Cloud Integration Gateway (CIG) is the recommended integration option
to integrate VIM with Ariba Network.
The minimum VIM release and SP levels are VIM 7.5 SP5 with Business Center 16.0
update 1, and VIM 16.3 with Business Center 16.3. On VIM 7.6 and 20.4, the initial
package and all later SPs are supported.

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

Installation (SAP ERP) 8199C454C8

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

• See OSS note 2068615: SAP Invoice Management by OpenText 7.5.

• Vendor Invoice Management, minimum 7.5 on SAP ERP, minimum 16.3 on SAP
S/4HANA.
• The following components must be installed for Cloud Integration Gateway:
Table 24-1: Ariba Cloud Integration Gateway
Component: Component:
Option VIM release
ARBCI1 ARBCI2
1 SAP ERP 6.0 7.5, 7.6 100 100
2 SAP S/4HANA 16.3, 20.4 10S 10S

Chapter 24 Vendor Invoice Management integration with Ariba, CIG scenario objects installation
24.1.2.2 Installation tool

VIM uses the SAP Add-On Installation Tool (SAINT) for installation. SAINT uses
single PAT files (extension *.PAT), which integrate several transport files. These
collections are also called packages.
On the product CD, the single PAT files are archived in SAPCAR files (extension
*.SAR), which can be extracted using the SAPCAR command line tool.
You can also use the SAR files directly in the SAINT transaction.
24.2 Installing the OpenText package

To install the OTVIMARC package:
1. Copy the respective SAPCAR file (*.SAR) from My Support to a local folder.
File – OTVIMARC_80700_006.SAR (for VIM 16.3/20.4 installation on SAP S/
4HANA)
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 then load file OTVIMARC_80700_006.SAR.
4. To add or update the OTVIMARC component, click Continue.
5. Choose the package for component OTVIMARC. Carry out the import of the
package as described in the respective SAP documentation.

Make sure that the OTVIMARC add-on is reflected in the installed components.
1. On the SAP menu, click System > Status.
2. Click next to Component version.

In the System: Component information dialog box, you should see the
OTVIMARC add-on component installed, with Release number 80700_006.


24.4.1 Activating business configuration set for the
OTVIMARC component
Note: For every client, you must activate new BC sets after installing the
OTVIMARC component.
The customizing transport creates or updates an entry in the Business Center

Inbound Registration IDoc node, with the following parameters:
• Partner number = <space>

• Partner type = LS
• Partner role = LS
• Message type = INVOIC
• Test = X
Note: Before performing the import, verify whether you already have such an
entry. Save the values of non-key fields to restore them after import. The
corresponding IDoc mapping entries are created for development object
ARBCIG_INVOIC.
To activate the BC sets:
1. Login to your productive clients (in English).
2. Activate the BC set /OTVIMARC/VIM204_CUSTOMIZING.
Note: Consider the most recent Release Notes for latest information on
new BC sets and additional post installation activities.

Part 4
Part 4 Solutions Beyond Invoice
Before you start installing, the Foundation must be installed. For more information,
see “Foundation” on page 35.

Chapter 25
Installing
This section describes the installation of the Solutions Beyond Invoice packages on
an SAP application server. For general information about installing in an SAP
environment, see also “Prerequisites for installation” on page 19.

The Solutions Beyond Invoice components are provided as add-on packages. For
details about basic components or additional S/4HANA components, refer to
corresponding sections.
Collect the installation files for the components listed in the corresponding sections.
Notes
• Customers who purchase VIM from SAP receive the packages from SAP
Marketplace.

To install the packages:
1. Sign in with Client 000 in English.
2. Load the installation packages and support packages from the front end by
selecting the respective SAPCAR file (*.SAR) from the local file system. The
SAPCAR file is decompressed automatically.
3. Carry out the import of the packages and support packages as described in the
SAP documentation.
4. After the import has finished, continue with the activation of the BC sets. For
more information, see:


You can bypass messages you might get during installation. These warn you
about not digitally signed packages/software.

25.1.1 SAP installation packages

The following packages and included Solutions Beyond Invoice components are
available:
Component SAR file Release Password

OTBCSLOC OTBCSLOC_0700_006.SAR 0700_006 8B87C949DC
OTBCSLPP OTBCSLPP_0700_006.SAR 0700_006 8B87C956CF
OTBCSLOC
OpenText VIM Order to Cash.
Mandatory if you want to use the preconfigured Remittance Advice, or Sales
Order processing solutions of Order to Cash .
OTBCSLPP
OpenText VIM Procure to Pay.
Mandatory if you want to the preconfigured Delivery Note, Order
Confirmation, or Quotation processing solutions of Procure to Pay.
25.1.2 Optional S/4 HANA installation packages

The following optional S/4HANA packages and included Solutions Beyond Invoice
components are available:

OTBCS4OC OTBCS4OC_1610_106.SAR 1610_106 8A87B149DC
OTBCS4PP OTBCS4PP_1610_106.SAR 1610_106 8A87B156CF
For details about OTBCS4OC components, see:
• Sales Order: Section 8 “Sales Order Analytics” in OpenText Vendor Invoice

(BOCP-CCS)
• Remittance Advice: Section 28 “Analytics” in OpenText Vendor Invoice
(BOCP-CCS)
For details about OTBCS4PP components, see:
• Quotation: Section 13 “Analytics” in OpenText Vendor Invoice Management for SAP

Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP-CCS)
• Delivery Notes: Section 18 “Analytics” in OpenText Vendor Invoice Management for

• Order Confirmation: Section 23 “Analytics” in OpenText Vendor Invoice

(BOCP-CCS)
The Solutions Beyond Invoice components for S/4HANA are used as follows:
OTBCS4OC
OpenTextVIM S/4 Order to Cash.
Needs to be installed if you want to use the embedded analytics capabilities for
Remittance Advice or Sales Order.
OTBCS4PP
OpenText VIM S/4 Procure to Pay.
Needs to be installed if you want to use the embedded analytics capabilities for
Delivery Note, Order Confirmation, or Quotation.
25.1.3 Installation steps

installing Solutions Beyond Invoice.
Notes
• For the Dashboard for Purchase Order / Purchase Requisition Monitoring, no

separate installation is necessary. For technical reasons, this is already
included in OTBCSL00.
To install the Solutions Beyond Invoice:
1. Install the solution package that you want to use:
Notes
• You find the solutions installation files on My Support.
2. Install Order to Cash to use one of the following solutions:
• Sales Order
• Remittance Advice
• Install the OpenText VIM Order Cash (OTBCSLOC) add-on using the SAINT
transaction.
3. Install Procure to Pay to use one of the following solutions:
• Delivery Notes
• Order Confirmation
• Quotations

• Install the VIM for SAP Procure to Pay Solutions (OTBCSLPP) add-on using
the SAINT transaction.
4. Optional Installation for S/4HANA systems: :
• Install OpenText VIM S/4 Procure to Pay (OTBCS4PP) using SAINT

transaction.
• Install OpenText VIM S/4 Order to Cash (OTBCS4OC) using SAINT
transaction.
5. Install the language packages.
25.2 Installing language packages

The installation is described in the Foundation chapter. For more information, see
“Installing language packages” on page 44.

Chapter 26
Upgrading
To upgrade the Solutions Beyond Invoice component, you must also upgrade the
Foundation component. This also applies the other way round for a Foundation
upgrade. For more information, see “Upgrading“ on page 63.
Note: Several solutions that were formerly separate, are now included in one
of the listed packages. If you installed one of the solutions, that are listed here,
you must also install the related solution within one step with
the OTBCBAS and the OTBCSL00 add-on.
• OTBCSLPP add-on if you have installed one of the following solutions:

OTBCSL01, OTBCSL09, OTBCSL10.
• OTBCSLOC add-on if you installed one of the following solutions: OTBCSL02,
OTBCSL07.
Table 26-1: Changes in VIM Solutions Beyond Invoice component structure
BC 16.3.x Description VIM 7.6 / 20.4 Description

OTBCSL02 Solution for Incoming OTBCSLOC OpenText VIM Order to
Sales Orders Cash
OTBCSL07 Solution for Incoming
Remittance Advices
OTBCSL09 Solution for Incoming OTBCSLPP OpenText VIM Procure to
Order Confirmations Pay
Delivery Notes
Quotations
OTBCS4SL Business Center S/ OTBCS4OC OpenText VIM S/4 Order
4HANA Solutions to Cash
OTBCS4PP OpenText VIM S/4
Procure to Pay
OTBCSL05 Solution for Incoming HR not included in VIM 7.6 /
documents 20.4
Caution
The Solution for Incoming HR Documents (component OTBCSL05) is not
included in Vendor Invoice Management 7.6 or 20.4. Before upgrading to
Vendor Invoice Management 7.6 or 20.4, check if the component OTBCSL05
is installed. If this is the case, uninstall it before the upgrade. By doing this,

Chapter 26 Upgrading
all objects including data of the Solution for Incoming HR Documents are
deleted. No other solutions are affected. If OTBCSL05 is not installed, no
action is required.
To be able to uninstall OTBCSL05, delete the entries with the following

layout ID from the /OTX/PF62_T_PLDA table:
• E914DBE8165BA2F196340050560113B8
• E9157F793F770DF196340050560113B8
• E73EB8F34F90A6F19EC50050560113B8
• E73EB975BADD30F19EC50050560113B8
• E7768D17052979F19EC50050560113B8
• E792185A3EFCABF19EC50050560113B8
• E7921869F37C3DF19EC50050560113B8

Chapter 27
Uninstalling
VIM add-ons, see list in “Installing“ on page 37, can be deleted. It is definitely the
decision of the customer to delete an add-on and thereby lose data in the VIM tables.
Important
• Before deleting VIM add-ons, always open a ticket at OpenText Customer

Support.
• The customer is responsible to evaluate if data needs to be saved. The
customer is also responsible for actually saving the data that is legally
relevant and should not be deleted.
• All entries in the /OTX/PF62_T_PLDA and /OTX/PF62_T_AIC table must be
deleted before you start the deinstallation.
27.1 Foundation and Beyond Invoice solutions

Important
All entries in the /OTX/PF62_T_PLDA and /OTX/PF62_T_AIC table must be
deleted before you start the deinstallation.
The VIM add-ons must be deinstalled in the following sequence due to package
dependencies in the import conditions. Add-ons to be deinstalled must exist in the
system.
1. OTBCSLPP.
2. OTBCSLOC
3. OTBCSL00
4. OTBCRM
5. OTBCWUI
6. OTBCS4PP
7. OTBCS4OC
8. OTBCS4
9. OTBCBAS

Chapter 27 Uninstalling
27.2 Prerequisites
Mandatory SAP Notes
2507738
Change to object directory entry of DDLS-dependent VIEWs and STOBs
Note: OpenText recommends a backup or snapshot of the system before

starting the deinstallation.
27.3 Invoice Solution

Invoice Solution add-ons, for example OTEXVIM, can be deleted. It is definitely the
decision of the customer to delete an add-on and thereby lose data in the VIM tables.
Important
• The customer is responsible to evaluate if data needs to be saved. The

customer is also responsible for actually saving the data that is legally
relevant and should not be deleted.
• Removing Invoice Solution add-ons does not delete data in SAP tables.
Example: If workflows were started in the system, the entries in the SAP workflow
tables remain.
The following instructions does not cover the removal of this data.
• OpenText recommends that you select all VIM related components in one
deinstallation run. The following steps are based on a complete
deinstallation, including all Business Center components.
Note: Sections that are marked with (VIM) at the beginning of the heading are
only relevant for VIM, other sections also for Business Center.
To uninstall the add-ons, you can use the SAINT transaction.
27.3.1 Steps before deinstallation

The following steps are mandatory before deinstallation. If you do not follow these
instructions, it will lead to errors during the deinstallation or inconsistent table
entries after deinstallation.

27.3. Invoice Solution
27.3.1.1 Deleting local workflow types

The following steps are only necessary when removing the main add-on OTEXVIM
and all Business Center components.
During workflow runtime, temporary objects are created by the workflow runtime
environment. You have to delete these objects manually using the SWF_CNT_STR_
EDIT transaction. Delete local types for structures (if present) with the field Package
pointing to the following packages:
• /OTX/PF02
• /ORS/000007
• /OPT/VIM
27.3.1.2 Deleting table entries in /OTX/PF62_T_PLDA

Delete table entries in table /OTX/PF62_T_PLDA (Fiori perspectives). The

deinstallation program cannot remove these entries automatically. Delete these
entries in all clients.
27.3.1.3 Deleting table entries in /OTX/PF62_T_AIC

Delete table entries in table /OTX/PF62_T_AIC (Fiori Advanced Line Items). The
deinstallation program cannot remove these entries automatically. Delete these
entries in all clients.

27.3.1.4 Deleting layouts for VIM Analytics

The following steps are only necessary when removing the main add-on OTEXVIM.
Layouts have been imported by a separate transport. You have to delete them
manually before deinstallation.
• Run the /OPT/VIM_VA2 transaction, Manage Layouts: Delete layouts /OPT/VA2_

H01 and /OPT/VA2_H02.
• Run the /OPT/VIM_VA2 transaction, and click the Processes tab: Manage Layouts:
Delete layouts /OPT/VA2_P01.
• Run the /OPT/VIM_VA2 transaction , and click the Line items tab: Manage
Layouts: Delete layouts /OPT/VA2_I01 and /OPT/VA2_I02.
27.3.1.5 (VIM) Deleting GOS entries

You need to clear table entries for the VIM GOS menu if they are available.
To delete GOS menu entries:
1. Run the SM30 transaction to maintain the SGOSATTR table and delete the
following entries if they are present:
WF_ZOPT/VIM
OpenText DP Document > Document Dashboard
ZOPT_SERVC
OpenText Dashboard > OpenText Dashboard
2. Remove Next service in WF_START if present.
Note: In custom installations, the Next service entry might be customized

at another service. Verify that the entries WF_ZOPT/VIM and ZOPT_SERVC
are not referenced any more.

27.3.1.6 (VIM) Maintaining Business Transaction Events

You have to remove the Business Transaction Event (BTE) customizing manually
before deinstallation.
To remove the BTE customizing:
1. Run the BF12 transaction and remove entry /OPT/.
2. Run the BF22 transaction and remove entry /OPT/VIM > /OPT/ OpenText Vendor
Invoice Management.
3. Run the BF23 transaction and remove entry /OPT/VIM > /OPT/.
4. Run the BF24 transaction and remove entry /OPT/VIM > OpenText VIM.
5. Run the BF32 transaction and remove all entries with handler names beginning
with /OPT.
6. Run the BF42 transaction and remove all entries with handler names beginning
with /OPT.
27.3.1.7 (VIM) Removing authorization group /OPT

To remove the authorization group /OPT:
1. Run the SE54 transaction.
2. Choose Authorization Groups.
3. Remove the entry /OPT > VIM Tables
27.3.1.8 (VIM) Removing event type linkages (SWETYPV)

To remove event type linkages:
• Run the SWETYPV transaction and remove the following linkages (if present):
Note: “Event type linkages to be removed” on page 248 lists event

linkages that are typically maintained. Depending on your
implementation, not all listed entries may exist. In addition, verify if there
are any extra entries with VIM receiver types (beginning with TS00275 or
WS00275) or VIM function modules (beginning with /OPT).

Table 27-1: Event type linkages to be removed
Receiver Type/Receiver Function

Object Type Event
Module (FM)
VIM_PARKED_DP / /OPT/
/OPT/B2081 ZWFI_PARKED
BL_PO_PRK_RECEIVER
WS00275260 / /OPT/
/OPT/B2081 ZWFI_PARKED
BL_PO_PRK_RECEIVER
WS00275254 / /OPT/
/OPT/FIPP ZWFI_CREATED
BL_NPO_PRK_RECEIVER
/ORS/INVAP POSTED /OPT/AAFS_POST_RECEIVER
/OPT/
BUS2081 CANCELLED
VIM_RPT_PO_INV_RECEIVER
/OPT/
BUS2081 DELETED
VIM_RPT_PO_INV_RECEIVER
TS00275270 /
BUS2081 DELETED
SWW_WI_CREATE_VIA_EVENT
/OPT/VIM_RPT_PO_INV_-
BUS2081 POSTED
RECEIVER
TS00275264 / /OPT/
BUS2081 POSTED
BL_PO_BLK_RECEIVER
TS00275270 /
BUS2081 POSTED
WS00275264 / /OPT/
BUS2081 POSTED
BL_PO_BLK_RECEIVER
/OPT/VIM_RPT_PO_INV_-
BUS2081 RELEASED
RECEIVER
TS00275270 /
FIPP CHANGED
FIPP DELETED /OPT/VIM_RPT_RECEIVER_FM
TS00275270 /
FIPP DELETED
FIPP POSTED /OPT/VIM_RPT_RECEIVER_FM
TS00275270 / /OPT/
FIPP POSTED
VIM_RPT_RECEIVER_FM

27.3.1.9 (VIM) Cleaning up the MIRO enhancement

You might have created implicit enhancements in the SAP includes LMR1MF3U and
LMR1MF3S. For more information, see Section 8.11.3 “Enhancing MIRO for pre-
population of data during online invoice creation” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIM-CGD). In
this case, you must delete those implicit enhancements prior to removing OpenText
add-ons.
27.3.1.10 (VIM) Cleaning up Ariba PI Scenario transports

You might have used the Ariba Network integration with PI and imported the
required transports. For more information, see “Importing ABAP workbench
objects, PI scenario” on page 229. In this case, you must delete the corresponding
objects manually. Perform this first in a development system. Then import the
resulting transport into each system prior to removing OpenText add-ons. This
applies to the following objects:
• Class /OPT/CL_E_SUPPLIER_NETW_ARB_PI
• Class /OPT/CL_IM_VIM_ARB_PI_OUTB
• BAdI Implementation /OPT/VIM_ARB_PI_OUTB
• Package /OPT/VIM_ARB_PI
27.3.1.11 Deleting all external usages

All custom coding referring to objects in the OpenText package has to be removed
before deinstallation.
27.3.1.12 Undoing all modifications

All modifications to OpenText Standard coding have to be undone. You can use the
SAP modification browser (SE95) to find all modifications.
27.3.2 Steps after deinstallation

27.3.2.1 (VIM) Reviewing BAPI for extended VAT date support

After deinstallation, check if the BADI VATDATE_VALUES is calling the SAP default
installation or if a custom implementation is called correctly.
Run the SE18 transaction, enhancement spot: VATDATE_RULES
Before:
After (example):
Note: Custom implementations need to be considered.
27.3.3 Troubleshooting
27.3.3.1 Error in phase CHECK_LOCKED_OBJ
Symptom After post-installation step “Maintaining the SAPscript form for approval”
on page 86 is done, the following error occurs:

Solution Release the mentioned transport and click Repeat to repeat the deinstallation step.
27.3.3.2 Error in phase COLLECT_OBJLIST

Symptom Entries of table /OTX/PF62_T_PLDA cannot be deleted.
Solution Delete the entries mentioned in “Deleting table entries in /OTX/PF62_T_PLDA”

on page 245.

27.3.3.3 Error in phase DDIC_IMPORT
Generated STOB objects (CDS views)

Symptom During activation of the CDS views, the installation program has generated STOB
objects with the source system equal to the current system.
Solution If the mandatory SAP Note 2507738 has not been installed before deinstallation, you
need to manually set the entries to source system “SAP”. You can use the following
coding in a custom created report:
UPDATE tadir SET srcsystem = 'SAP' WHERE object = 'STOB'
AND srcsystem = sy-sysid AND obj_name LIKE '/OPT/%'.

27.3.3.4 Error in phase CHECK_USAGE

Symptom The deinstallation routine stops at phase CHECK_USAGE.
Custom objects
Solution Not all custom objects referencing to objects in the OTEXVIM component have been
removed. Delete all mentioned objects.
Temporary workflow objects

Solution If tables in namespace /SAPWF/ in package $SWF_RUN_CNT are mentioned in this
step, see “Deleting local workflow types” on page 245.
Note: Do not delete these objects manually from package $SWF_RUN_CNT.
27.3.3.5 Error in phase CHECK_MOD
Modifications
Symptom The deinstallation stops at phase CHECK_MOD, if modifications are still present.

Solution Undo all listed modifications.
27.4 Optional activities

Remove event type linkages
Call SWETYPV transaction and delete all entries for /OTX/PF04E object type .
Remove archive link presettings

Call OAWS transaction and delete the /OTX presetting including all dependent
entries.
Remove workflow document types

Call transaction SOA0 and delete all document types starting with the prefix /
OTBC/.
Remove links for content repositories

Call transaction OAC3 and delete all entries for the /OTX/PF01R and /OTX/PF02
business objects.
If available, also delete the following entries:
BUS2017 /OTBC/1DN1
BUS2017 /OTBC/1DN2
BUS2032 /OTBC/2SO1
BUS2032 /OTBC/2SO2
BUS2012 /OTBC/9OC1
BUS2012 /OTBC/9OC2
Remove global document types

Call OAC2 transaction and delete all document types starting with the prefix /
OTBC/.
Remove authorization group for tables

Call SE54 transaction and delete the /OTX authorization group.
Remove Application Log Object configuration

Call SLG0 transaction and delete the configuration for /OTX/PF00 object
including all dependent sub objects.
Remove local workflow container structures

Delete local workflow container structures in SWF_CNT_STR_EDIT transaction
corresponding to the /OTX/PF02 package if still available after the deinstallation
(check OSS note 2254228 for further information).
Remove services
Delete all services within SICF: OData and UI Services which have been
activated according to Installation Guide

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.
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.
Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can perform in the SAP system. These authorizations are stored in
Authorization profiles.

Glossary
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 system to accommodate user
requirements too specific to be included in the standard delivery.
Business Center Capture (BCC)

OpenText Business Center Capture for SAP Solutions. Business Center
component for use in VIM. Automates the capture of paper invoices by using
OCR to extract invoice data.
Business Center Foundation

Central Business Center unit that serves to import, capture, dispatch, process, and
consume business objects. It comprises Inbound Configuration, Process Foundation,
Process Configuration, Business Center Workplace, and Fiori Task App.

Glossary
Business Center Workplace

Central tool to process work objects of the Business Center solutions. It provides
an inbox with personal and shared work item lists to the user. It also provides
access to different business objects and status information for all objects in
process. The user can switch between work centers and navigate in a process-
dependent tree.
Business Center
The name Business Center groups features of the VIM product that help receiving
incoming documents, capturing processes, and filing them within a SAP system.
These feature are an addition to the Vendor Invoice Management features that
form the VIMproduct.
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
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.
Dashboard
User interface that organizes and presents information in a way that is easy to
read. Users can also perform actions from the dashboard.

Glossary
Data Transfer Process (DTP)

Object in SAP NetWeaver BW to transfer data from source objects to target objects
Data View (View)

Dynamic part of a perspective. A set of views is shown in the template at specific
locations at runtime. For each perspective, you can define which view appears at
which location in its template. You can insert each view only once in each
perspective.
DataSource
Set of fields in SAP NetWeaver BW that provide the data for a business unit for
data transfer to the SAP NetWeaver BW system; technically, it contains an extract
structure and an extraction function module.
DataStore Object (DSO)

Storage location for consolidated and cleansed data in SAP NetWeaver BW
DocuLink
OpenText™ DocuLink for SAP Solutions enables the archiving, management and
retrieval of SAP CRM or SAP S/4HANA 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)
EDI
See: Electronic Data Interchange (EDI)

Glossary
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.
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
Fiori Task App

Light-weight web application following the design principles of SAP Fiori. It
provides an inbox showing the items that have been assigned to the logged-in
user. The user then is able to complete items by performing dedicated actions,
entering comments, and editing the data.
IAP
See: Invoice Approval (IAP)
IDoc
See: Intermediate Document (IDoc)
IE
See: Invoice Exception (IE)

Glossary
Inbound Configuration
Connection to various inbound channels, for example scanned paper documents,
fax, email, or IDoc, and the corresponding configuration. Business Center
Inbound Configuration is also used in VIM.
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.
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.
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 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.

Glossary
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
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 S/4HANA 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

Glossary
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
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 S/4HANA 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.
Perspective
Web Services element that defines which item related data is displayed in the
Fiori Task App and where. A perspective defines the content and visual
appearance of items for a specific area of the screen in the Fiori Task App. The
Fiori Task App displays only one perspective at the same time.
PIR
See: Non purchase order (Non PO) invoice (PIR)

Glossary
PO
See: Purchase order (PO)
Posted invoice document

Invoice that has already been posted in SAP S/4HANA. 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
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 Configuration
Easy and technically simplified configuration of complex business scenario
aspects. Process Configuration covers profile configuration, profile assignment,
and authorizations.
Process Foundation
Flexible framework to configure and run processes. It utilizes generic workflow
definitions, which are processed by the SAP Business Workflow engine.
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)

Glossary
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
Roles
Set of predefined roles for the SAP user
SAP Add-On Assembly Kit (AAK)

Standardized delivery procedure for software
SAP Customer Relationship Management (SAP CRM)

SAP application that provides software for ticket systems, for example in the
Accounts Payable department.
SAP NetWeaver Business Warehouse (SAP NetWeaver BW)

SAP application that allows to integrate, transform, and consolidate relevant
business information from productive SAP applications and external data
sources.
SAP 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)
Summary Report
Part of the Central Reporting infrastructure. The Summary Report provides a
summary of all documents processed through VIM.
Transformation (TRF)
Object in SAP NetWeaver BW to connect source objects to data targets; it allows
to consolidate, cleanse and integrate data
TRF
See: Transformation (TRF)
VAN
See: VIM Analytics (VAN)

Glossary
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.
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.
Web Services
Underlying technical concept of the Fiori Task App interface. You configure the
complete content of the Fiori Task App either by customizing or by implementing
an interface for the Web Services.
Work object type

Processing object in the Business Center Workplace. It can represent a process
object, a SAP business object, or information from any SAP tables.
Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP S/4HANA system.

VIM For SAP Solutions 20.4 Installation Guide English VIM200400 IGD en 09 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VIM For SAP Solutions 20.4 Installation Guide English VIM200400 IGD en 09 PDF

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

for SAP® Solutions

This guide describes the installation of all components of

The components of Vendor Invoice Management include

Open Text Corporation

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

Copyright © 2021 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

Part 1 Prerequisites for installation 19

4 SAP prerequisites .................................................................... 23

5 OpenText prerequisites .......................................................... 25

6 Installation tool ........................................................................ 27

8 Notes on transports ................................................................ 31

9 Required knowledge ............................................................... 33

11 Fiori Deployment ..................................................................... 47

VIM200400-IGD-EN-09 Installation Guide iii

11.2 Deployment options on SAP Cloud Platform ..................................... 49

Part 3 Invoice Solution 65

13 VIM classic mode installation ................................................. 67

iv OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

13.2.2.16 Fiori: Setting up Launchpad content on-premise ................................ 92

VIM200400-IGD-EN-09 Installation Guide v

14 Simple Mode VIM installation ............................................... 115

15 KPI Dashboard installation ................................................... 123

16 OpenText Approval Portal installation ................................ 135

vi OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

17 Mobile Approval Portal installation ..................................... 195

18 Vendor Invoice Management SAP NetWeaver Business

VIM200400-IGD-EN-09 Installation Guide vii

18.2 Installing or upgrading the OpenText package ................................ 204

19 Vendor Invoice Management BW/4HANA add-on

20 Vendor Invoice Management component for SAP

21 Vendor Invoice Management Supplier Self Service - Lean

viii OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

22 Vendor Invoice Management electronic invoices

23 Vendor Invoice Management ARIBA integration

24 Vendor Invoice Management integration with Ariba, CIG

Part 4 Solutions Beyond Invoice 235

25 Installing ................................................................................. 237

26 Upgrading ............................................................................... 241

27 Uninstalling ............................................................................ 243

VIM200400-IGD-EN-09 Installation Guide ix

27.3.1.1 Deleting local workflow types ......................................................... 245

GLS Glossary 255

x OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

About Vendor Invoice Management for SAP

VIM automates the processing of incoming documents into SAP.

Document-centric business processes like the processing of incoming invoices from

For managers VIM offers a comprehensive suite of operational and analytical

VIM includes the following solutions:

• Procure to Pay Solutions

• Order to Cash Solutions

Each solution consists of a best practice implementation for a specific document

VIM200400-IGD-EN-09 Installation Guide 11

The VIM Foundation consists of the following components:

VIM requires an ArchiveLink-compliant SAP-certified content repository for the

12 OpenText™ Vendor Invoice Management for SAP® Solutions VIM200400-IGD-EN-09

1.1 Architectural Overview

Figure 1-1: Technical system landscape

VIM200400-IGD-EN-09 Installation Guide 13

1.2 About this document

• SAP Basis Administrators

1.2.2 Further information sources