Opentext™ Vendor Invoice Management For Sap Solutions: Installation Guide

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

Management (VIM) components.
These are Vendor Invoice Management SAP component - classic

and simple mode, Business Center components, optional KPI
Dashboard, optional OpenText Approval Portal, optional
Mobile Approval Portal, optional Vendor Invoice Management
SAP NetWeaver® Business Warehouse (VIM BW) component,
optional Vendor Invoice Management BW/4HANA add-on
component, optional Vendor Invoice Management SAP
NetWeaver Gateway component, optional Vendor Invoice
Management Supplier Self Service - Lean Variant component,
optional Vendor Invoice Management electronic invoices
component, optional Vendor Invoice Management ARIBA
Integration component, and Vendor Invoice Management
integration with Ariba, CIG scenario objects.
VIM160305-IGD-EN-03
OpenText™ Vendor Invoice Management for SAP® Solutions
Installation Guide
VIM160305-IGD-EN-03
Rev.: 2020-Aug-04
This documentation has been created for software version 16.3.5.
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 © 2020 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
Part 1 About Vendor Invoice Management 9
1 About this document ............................................................... 17

1.1 Target audience .............................................................................. 17
1.2 Further information sources ............................................................. 17
1.3 Document overview ......................................................................... 18
Part 2 VIM classic mode installation 19
2 Preparing installation .............................................................. 21

2.1 General .......................................................................................... 21
2.2 Password control ............................................................................ 22
2.3 Checking prerequisites .................................................................... 22
2.4 Notes on transports ......................................................................... 23
3 Installing VIM ........................................................................... 25

3.1 System landscape and installation overview ..................................... 25
3.2 Selecting required components and downloading the packages ......... 26
3.3 Installing the package ...................................................................... 30
3.4 Post installation activities ................................................................. 34
3.5 Language packs ............................................................................. 56
4 Installing Single Click Entry for SAP GUI .............................. 59
5 Installing a VIM Support Package .......................................... 61

5.1 SAP prerequisites ........................................................................... 61
5.2 Collecting Support Packages ........................................................... 62
5.3 SAP installation ............................................................................... 64
5.4 Post installation activities after installing a new Support Package ....... 71
6 Upgrading ................................................................................. 73
6.1 Upgrading VIM 7.5 to VIM 16.3 ........................................................ 73
6.2 ACP files ........................................................................................ 82
7 Troubleshooting ...................................................................... 83
7.1 FAQs ............................................................................................. 83
7.2 Handling workflow container inconsistencies ..................................... 83
7.3 Missing translations in line items of indexing screen .......................... 84
7.4 Issue with loading Fiori apps ............................................................ 85
Part 3 Simple Mode VIM installation 87
8 Overview ................................................................................... 89
VIM160305-IGD-EN-03 Installation Guide iii

Table of Contents
9 Simple Mode installation ........................................................ 91

9.1 Prerequisites .................................................................................. 91
9.2 Installing the Simple Mode components ............................................ 93
9.3 Post installation activities ................................................................. 95
9.4 Troubleshooting .............................................................................. 97
Part 4 KPI Dashboard installation 99
10 Installing the KPI Dashboard ................................................ 101
11 Post installation activities .................................................... 103

11.1 Activating the SAP Web Dynpro service ......................................... 103
11.2 Setting the connection for the SAP Web Dynpro service .................. 108
11.3 Setting up the SAP NetWeaver Portal integration ............................ 109
Part 5 OpenText Approval Portal installation 113
12 Preparing installation ............................................................ 115

12.1 Installation prerequisites ................................................................ 115
12.2 Installation components ................................................................. 118
12.3 System architecture ...................................................................... 119
13 Installing Web Viewer/Brava! View for the Approval

Portal ...................................................................................... 123
14 Installing the Approval Portal ............................................... 125

14.1 JCo3 migration considerations ....................................................... 125
14.2 Preparing the installation ............................................................... 125
14.3 Configuring the administrator role ................................................... 128
14.4 Deploying the Software Component Archive ................................... 134
14.5 Deploying the Software Component Archive with SAP NetWeaver
7.3 ............................................................................................... 141
14.6 Deploying the Software Component Archive using SUM .................. 144
15 Configuring SAP NetWeaver Portal components ............... 149

15.1 Creating AppIntegrator iViews for users .......................................... 149
15.2 Creating AppIntegrator iViews for users with SAP NetWeaver 7.3,
7.4, and 7.5 .................................................................................. 155
15.3 Creating roles for users ................................................................. 165
15.4 Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5 ........ 169
15.5 Assigning roles to SAP NetWeaver Portal users .............................. 172
15.6 Configuring iViews and roles for the administrator ........................... 173
15.7 Administering the OpenText Approval Portal ................................... 174
16 Applying a new patch ............................................................ 175
iv OpenText™ Vendor Invoice Management for SAP® Solutions VIM160305-IGD-EN-03

Table of Contents
17 Upgrading the Approval Portal from previous versions .... 177
18 Troubleshooting .................................................................... 179
19 Supporting installation of the standalone NWAS Portal

and Mobile Approval Portal on Unix or Linux ..................... 181
20 Uninstalling the Approval Portal .......................................... 183

20.1 Uninstalling using Software Deployment Manager ........................... 183
20.2 Uninstalling with SAP NetWeaver 7.3, 7.4, and 7.5 .......................... 184
20.3 Removing SAP NetWeaver Portal components ............................... 185
20.4 Deleting properties files ................................................................. 186
20.5 Optional: Removing the startup parameter in the Config Tool ........... 186
Part 6 Mobile Approval Portal installation 189
21 Introduction to the Mobile Approval Portal ......................... 191
22 Authentication for the Mobile Approval Portal ................... 195
23 Installing Web Viewer for the Mobile Approval Portal ....... 197
24 Installing the Mobile Approval Portal .................................. 199

24.1 Installing the Mobile Approval Portal on standalone NWAS
7.0/7.3/7.4 .................................................................................... 199
24.2 Installing the Mobile Approval Portal on SAP NetWeaver Portal
7.0/7.3/7.4/7.5 ............................................................................... 199
Part 7 Vendor Invoice Management SAP NetWeaver Business

Warehouse component installation 201

25.1 Password control .......................................................................... 203
25.2 Checking prerequisites .................................................................. 203
26 Installing the OpenText package ......................................... 205
27 Verifying the installation ....................................................... 209
28 Installing VIM BW Add-on support package ....................... 211
29 Uninstalling the VIM BW add-on package ........................... 213

29.1 Prerequisites ................................................................................ 213
29.2 Steps before uninstalling ............................................................... 213
29.3 Uninstalling the VIM BW package .................................................. 213
VIM160305-IGD-EN-03 Installation Guide v

Table of Contents
Part 8 Vendor Invoice Management BW/4HANA add-on

component installation 215
30 About the VIM BW/4HANA add-on ....................................... 217
31 Packaging and delivery information .................................... 219
32 Supported environments and compatibility ....................... 221

32.1 Supported systems ....................................................................... 221
32.2 OpenText product compatibility ...................................................... 221
32.3 Language support ......................................................................... 221
33 Installing the VIM BW/4HANA add-on component ............. 223

33.2 Checking VIM BW/4HANA prerequisites ......................................... 223
33.3 Installing the OpenText package .................................................... 224
34 Upgrade notes ....................................................................... 227
Part 9 Vendor Invoice Management component for SAP

NetWeaver Gateway installation 229

35.2 Checking prerequisites .................................................................. 231
36 Installing the OpenText package ......................................... 233
37 Verifying the installation ....................................................... 235
Part 10 Vendor Invoice Management Supplier Self Service - Lean

Variant component installation 239

39.1 Installation prerequisites ................................................................ 241
39.2 Installation components ................................................................. 242
39.3 System architecture ...................................................................... 242
40 Installation on the SAP HANA Cloud ................................... 243

40.1 Preparing the installation ............................................................... 243
40.2 Deploying the application on the SAP HANA Cloud Server .............. 243
40.3 Installing the SAP HANA Cloud connector ...................................... 245
vi OpenText™ Vendor Invoice Management for SAP® Solutions VIM160305-IGD-EN-03

Table of Contents
Part 11 Vendor Invoice Management electronic invoices

41 General package for electronic invoices ............................. 249
42 Business Center Inbound: integration with SAP

Document Compliance .......................................................... 251
42.1 Prerequisites ................................................................................ 251
42.2 Installation .................................................................................... 252
Part 12 Vendor Invoice Management ARIBA Integration


43.1 Activating business configuration set .............................................. 257
43.2 Activating BAdI implementations .................................................... 257
44 Importing ABAP workbench objects ................................... 259
Part 13 Vendor Invoice Management integration with Ariba, CIG

scenario objects installation 261
45 Importing ABAP workbench objects and customizing ...... 263
Part 14 Removing OpenText add-ons 265
46 Prerequisites .......................................................................... 267
47 Steps before deinstallation ................................................... 269

47.1 Deleting local workflow types ......................................................... 269
47.2 Deleting table entries in /OTX/PF62_T_PLDA ................................. 269
47.3 Deleting table entries in /OTX/PF62_T_AIC .................................... 270
47.4 Deleting layouts for VIM Analytics .................................................. 270
47.5 (VIM) Deleting GOS entries ........................................................... 270
47.6 (VIM) Maintaining Business Transaction Events .............................. 271
47.7 (VIM) Removing authorization group /OPT ...................................... 272
47.8 (VIM) Removing event type linkages (SWETYPV) ........................... 272
47.9 (VIM) Cleaning up the MIRO enhancement ..................................... 273
47.10 (VIM) Cleaning up Ariba PI Scenario transports .............................. 273
47.11 Deleting all external usages ........................................................... 273
47.12 Undoing all modifications ............................................................... 273
48 Steps after deinstallation ...................................................... 275

48.1 (VIM) Reviewing BAPI for extended VAT date support ..................... 275
49 Troubleshooting .................................................................... 277
VIM160305-IGD-EN-03 Installation Guide vii

Table of Contents
49.1 Error in phase CHECK_LOCKED_OBJ ........................................... 277

49.2 Error in phase COLLECT_OBJLIST ............................................... 277
49.3 Error in phase DDIC_IMPORT ....................................................... 278
49.4 Error in phase CHECK_USAGE ..................................................... 279
49.5 Error in phase CHECK_MOD ......................................................... 279
GLS Glossary 281
viii OpenText™ Vendor Invoice Management for SAP® Solutions VIM160305-IGD-EN-03

Part 1
About Vendor Invoice Management
Part 1 About Vendor Invoice Management
OpenText™ Vendor Invoice Management for SAP® Solutions 16.3 is an add-on

solution to SAP S/4HANA® on Premise to provide automation of invoice processing,
routing of invoice exceptions, managing of processing rules, and monitoring of
process flows.
By implementing Vendor Invoice Management (VIM), companies achieve the

following:
• Acceleration of AP operations across the enterprise

• Optimal integration of an invoice automation solution into SAP S/4HANA on
Premise
• Higher productivity in Accounts Payable and increased flexibility in cash
management by reducing time until invoices are free for payment
• Improved supplier relations through fast and accurate invoice processing
• Accurate, on-time financial reporting with integrated access to AP information
• Regulatory compliance through a well-managed process using preconfigured
rules, roles and actions considering country specific regulations
Vendor Invoice Management (classic mode) provides the following:
• Seamless integration with SAP® Finance and Logistic functions

• Secure storage and archiving of invoice documents and additional
documentation including processing and approval protocol through SAP
ArchiveLink®
• SAP add-on built on SAP Enterprise technology like ABAP®, SAP Business
Workflow®, SAP Fiori®, SAP NetWeaver®
• Multi-channel input for digital and non-digital invoice formats like scanned
paper invoices, PDF invoices attached to emails, EDI invoices, network invoices,
and so on. This includes integration of the SAP® Ariba® network based on SAP’s
built-in interface with Ariba.
• OCR add-on (OpenText™ Invoice Capture Center for SAP® Solutions; short:
ICC) for intelligent and automated capture of invoice data from scanned and
PDF invoices.
Note: From a technical point of view, OpenText™ Invoice Capture Center

for SAP® Solutions (ICC) corresponds to “OpenText™ Business Center
Capture for SAP® Solutions with invoice solution” (BCC with invoice
solution).
• Framework for data enrichment and data checks to achieve automation of
specific classes of invoices based on the input from OCR or electronic channels.
This approach leads to high-quality automated invoice postings.
• A large library of business rules and data mappings and data enrichment
modules considering different country based aspects
10 OpenText™ Vendor Invoice Management for SAP® Solutions VIM160305-IGD-EN-03

• A pre-configured best-practice baseline configuration delivered as SAP
customizing set
• Tools and workflow processes to optimize processing of invoices that cannot be
fully automated by their nature or invoices triggering exceptions during the
automated processing.
• Best practice approach to automated compliance validation based on vendor
white, grey, and black lists
• Best practice logic to allocate different tasks to the right team and users, for
example:
– Review of basic invoice issues by Accounts Payable or Shared Services team

– Allocation of exceptions to specialized experts, for example a tax expert
reviewing complex tax constellation
– Sending tasks and notifications to teams outside Accounts Payable like
Purchasing team, Goods-in department and roles like receiver, requester and
approvers
• Different coding scenarios: Auto-coding in background, coding in AP, coding by
business users
• Comprehensive approval workflow supporting approval of invoice data in VIM
tables, parked invoices, and posted and blocked invoices
• Unblocking workflows for invoices blocked for payment based on SAP logistic
invoice verification blocking reasons (price, quantity)
• Various UI options (SAP GUI, Web, Fiori) for optimizing user experience for all
roles, users, and devices involved in invoice handling and approval
• A suite of reports to monitor the invoice process, create liability figures for
invoices not yet posted, do evaluations to calculate KPI figures, and further
optimize the invoice process
• Extraction and pre-configured content for SAP Business Warehouse®
• Comprehensive customizing options to adjust and amend the pre-delivered
baseline to specific process flows plus extension points through BAdIs and other
ABAP interfaces to extend the solution to meet customer-specific requirements
VIM160305-IGD-EN-03 Installation Guide 11

Figure 1: VIM 16.3 - Classic Mode
Vendor Invoice Management does not replace SAP invoice transactions and SAP
core logic of logistic invoice verification – Many categories of invoices can be
automated or treated by manual intervention through VIM screens. For other
invoice categories, navigation from VIM into the SAP invoice transaction (typically
MIRO) is required to fully post the invoice. Not all MIRO fields are provided in the
VIM baseline configuration.
VIM builds on top of the SAP core invoice verification. Tolerances are defined in
core SAP customizing. This logic will apply blocking reasons to line items when
invoices are posted. Most prominent blocking reasons are price and quantity. VIM
catches the events created by blocked invoices in core SAP and triggers workflows
for block resolution.
Vendor Invoice Management shares some components with OpenText™ Business

Center for SAP® Solutions. This allows to easily extend the methodology of capturing
and onboarding business documents to SAP S/4HANA beyond invoices.
Vendor Invoice Management provides additional value when used in combination

with other OpenText SAP-centric solutions like OpenText™ Archiving and Document
Access for SAP Solutions and OpenText™ Extended ECM for SAP® Solutions.
“Classic Mode” versus “Simple Mode” – Starting with version 16.3 and only
available for SAP S/4HANA 1610 and later, Vendor Invoice Management provides
two implementation options.
Classic Mode and Simple Mode are generally independent of each other.
Classic Mode Classic Mode is to a large extent compatible with previous VIM versions 7.0 and 7.5.
It offers proven architecture and a framework and many options to configure and

extend the pre-delivered invoice management logic. For details see the description
above. For VIM 16.3, the classic approach was updated and extended to meet SAP S/
4HANA requirements and optimizations and follow SAP strategy to post all
invoices through one invoice transaction: Baseline uses transaction MIRO for all
invoice types including Non-PO invoices.
Classic mode is the choice for organizations upgrading from SAP ECC and older
VIM versions who want to gradually adopt to new SAP S/4HANA concepts and
maintain their approach to invoice processing.
Classic mode provides powerful SAP GUI/Webgui based tools like VIM Workplace
and the VIM Analytics report, a web portal for invoice coding and approval, which
can be integrated with SAP NetWeaver® Portal and SAP Fiori apps for different
tasks like simple coding, approval, and confirming price and quantity on PO related
invoices.
Simple Mode Simple Mode provides a new invoice process designed embracing SAP S/4HANA
concepts like simplification, principle-of-one, digitalization, cloud-first, and new
user experience from the start. The SAP S/4HANA environment is the basis for a
next-generation invoice automation solution that focuses on streamlined and
simplified invoice processing.
While the Classic Mode provides different options, the Simple Mode philosophy is
about a uniform best practice approach based on different invoice scenarios:
• Invoices that can be processed through automation by their nature and structure
• Invoices that can be processed through automation with limited manual
intervention
• Invoices that need manual processing and may use specific features of SAP’s
Fiori app Manage Supplier Invoices
Vendor Invoice Management (Simple Mode) provides the following:
• Invoice automation build around SAP’s Fiori App Manage Supplier Invoices
• End-to-end Fiori user experience
• Capture of scanned paper invoices and PDF invoices through OCR cloud service
with automated optimization through constant feedback, other invoices are
received from networks like Ariba or classic IDocs or other channels.
• Cloud OCR as default option - on premise OCR will also be supported.
• Advanced machine learning features to optimize data capture (feedback from
SAP process and SAP posting to the data extraction service)
• Leverage SAP invoice drafts as container to store preliminary invoice data
(instead of separate business object and header and line items tables of classic
mode)
• Background logic for initial classification of incoming invoice data to control
process and flow (happens in background) - separate into invoices going through
automation and invoices that need manual intervention

• Pre-configured background flow of data enrichments, mappings, and business

rules including auto-post
• Manual postings by picking up the invoice draft created by VIM in background
inside the SAP Fiori App Manage Supplier Invoices
• A Fiori based validation screen for entering core invoice fields.
• Exception handling: AP and other roles get work item tasks to handle invoices
that run into exceptions or need approval.
• Central responsibility lies with the AP team and they will receive most
exceptions for review and resolution which can include collaboration with other
roles.
• Minimum set of mandatory configuration based on pre-delivered best practices
settings
• Limited classical customizing (done on DEV box and transported into QA and
PROD system)
• New “smart” and self-adapting features like intelligent coding defaults, dynamic
auto-classification of vendors into black, grey and white list, and others.
• Extension points through configuration of underlying Business Center process
framework to extend the solution to meet customer specific requirements
Limitations Vendor Invoice Management 16.3 provides a basic version of the new Simple Mode
covering invoices and credit memos. A number of features are not yet released and
there are further limitations. Future versions will provide new features to fully
support the scope of the Simple Mode as explained above.
Figure 2: VIM 16.3 - Simple Mode

Patches Patches (Hot Fixes), Support Packages and the latest versions of the Release Notes
for VIM are available on OpenText My Support: https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/10151605. The latest versions of the documentation are
also available on My Support: https://knowledge.opentext.com/knowledge/
llisapi.dll/Open/10151494.
For SAP Invoice Management by OpenText customers: To obtain access to My

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

Chapter 1
About this document
1.1 Target audience

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

• SAP Workflow Administrators
• SAP Configuration and Development Support
VIM features the optional component Web Invoice Approval. The target audience for
this component includes:
• Site administrators
• Database administrators
• Network administrators
1.2 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 (VIM-UGD)
• OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD)
• OpenText Vendor Invoice Management for SAP Solutions - Administration Guide
(VIM-AGD)
• OpenText Vendor Invoice Management for SAP Solutions - Reference Guide (VIM-
RGD)
• OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide (VIM-CCS)
• OpenText Vendor Invoice Management for SAP Solutions - Security Guide (VIM-GSM)
Release Notes The Release Notes describe the following aspects in detail:
• The software supported by the product

• Requirements
• Restrictions
• Important dependencies

Chapter 1 About this document
• New features
• Known issues
• Fixed issues
• Documentation extensions
The Release Notes are continually updated. The latest version of the VIM Release
Notes is available on OpenText My Support (https://support.opentext.com).
1.3 Document overview

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

• “VIM classic mode installation” on page 19
• “Simple Mode VIM installation” on page 87
• “KPI Dashboard installation” on page 99
• “OpenText Approval Portal installation” on page 113
• “Mobile Approval Portal installation” on page 189
• “Vendor Invoice Management SAP NetWeaver Business Warehouse component
installation” on page 201
• “Vendor Invoice Management BW/4HANA add-on component installation”
on page 215
• “Vendor Invoice Management component for SAP NetWeaver Gateway
• “Vendor Invoice Management Supplier Self Service - Lean Variant component
• “Vendor Invoice Management electronic invoices component installation”
on page 247
• “Vendor Invoice Management ARIBA Integration component installation”
on page 255
• “Vendor Invoice Management integration with Ariba, CIG scenario objects
• “Removing OpenText add-ons” on page 265

Part 2
VIM classic mode installation
Part 2 VIM classic mode installation
This part describes the installation of the SAP components of Vendor Invoice
Management (VIM).

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

OpenText disclaims all warranties for an unauthorized use of this
guide. Any unauthorized use is conducted on your own
responsibility excluding any liability of OpenText. If you have
any questions, contact OpenText 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.
Important
Make sure the SAP workflow system is configured to run workflows. To check
this, run the SWU3 transaction. Make sure most of the relevant items are
configured correctly, indicated by the icon. It is very important that, in the
Maintain Runtime Environment node, Configure RFC destination has the
icon.
Note: Check for and download the available latest support packs and hot fixes
on OpenText My Support: https://knowledge.opentext.com/knowledge/
llisapi.dll/Open/10151605.

Chapter 2 Preparing installation
2.2 Password control

The OpenText Vendor Invoice Management package is protected with a specific
password. During installation, this password is requested by the SAP Add-On
Installation Tool (SAINT). The passwords are available in “Selecting required
components and downloading the packages” on page 26.
2.3 Checking prerequisites

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

Installation Tool (SAINT)
• Basic knowledge of the employed operating system
2.3.2 SAP 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
• SAP S/4HANA 1909 (S4CORE 104) all FPS
• Support Package Manager (transaction code SPAM) level 66 or later. OpenText
recommends upgrading to the latest version of SPAM before installation.
• For a list of available software components, check SAP note 2524249: SAP Invoice
Management by OpenText 16.3.
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, the following SAP
UI versions are supported:
SAP UI5 Version SAP_UI version* Front-end Server*

1.52 7.52 SAP Fiori FES 4.0 (SAP Note 2484979)
1.60 (1811b) 7.53 SAP Fiori FES 5.0 (SAP Note 2618605)
1.71 (1910) 7.54 SAP Fiori FES 6.0 (SAP Note 2775163)

2.4. Notes on transports
2.3.3 Workflow customizing

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

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

OpenText Vendor Invoice Management uses the SAP Add-On Installation Tool
(SAINT) for installation. SAINT uses SAR files (extension *.SAR); these collections
are also called packages.
2.4 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 3
Installing VIM
This chapter describes the installation of the Basis package of Vendor Invoice
Management (VIM) on an SAP S/4HANA system. Read also “Preparing installation“
on page 21 with general information on installation in an SAP environment.
Important
• You are entitled to use OpenText Business Center for SAP Solutions add-
ons to implement additional aspects of your Accounts Payable process,
processing of Order Confirmation and Delivery Notes (limited use). This
limited use is covered by the VIM license. For details about the limited use,
including a definition, see the Release Notes.
• You also find the Business Center documentation on My Support: https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/58878669.
3.1 System landscape and installation overview

Depending on your system landscape, different Business Center components will
not be necessarily installed on the same server. Figure 3-1: “System landscape
example” on page 26 provides an overview on where the specific components
must be installed.
Note: “Fiori Server” and “Gateway Frontend Server” mean the same server.
For more information, see Section 4 “Setup for the Fiori Task App” in OpenText
Business Center for SAP Solutions - Installation Guide (BOCP-IGD).

Chapter 3 Installing VIM
Fiori Server SAP_UI SAP S/4HANA
Mobile Device VIM UI AddOn VIM AddOn

(Classic mode)
Secondary Agent OTBCUS03 OTBCSL30

OTEXVIM
Mobile Web
Browser VIM AddOn
(Simple mode)
UI AddOn
OTBCSL30
R R OTBCSL08
OTBCWUI
Trusted
HTTPS
RFC
BC AddOn
Desktop, Laptop
OTBCBAS
OTBCINB
OTBCFND
Secondary Agent OTBCSL00
OTBCSL01 – n
OTBCRM
Web Browser
Service AddOn
OTBCWSR
Figure 3-1: System landscape example
3.2 Selecting required components and downloading

the packages
To select components and download packages:
1. Collect the installation files for the components listed in “VIM components -
installation files” on page 26.
Notes
• Customers who purchase VIM through SAP receive the packages from
SAP Marketplace.
• Customers who purchase VIM directly from OpenText download the
packages, including installation packages, from OpenText My Support.
Table 3-1: VIM components - installation files
Minimal
Component File Password Remark
version
OTBCBAS_INST_U
OTBCBAS 0700_004 8B96C655BF
PG_0700_004.SAR

3.2. Selecting required components and downloading the packages
Minimal
Component File Password Remark
version
OTBCFND_INST_U
OTBCFND 0700_004 8B92C942BF
PG_0700_004.SAR
OTBCINB_INST_U
OTBCINB 0700_004 8B9DC944BF
PG_0700_004.SAR
OTBCSL00_INST_U
OTBCSL00 0700_004 8B87CB36AF
PG_0700_004.SAR
OTBCWSR_INST_U
OTBCWSR 0740_004 8B83D454BF
PG_0740_004.SAR
OTBCWUI_INST_U On frontend
OTBCWUI 0740_004 8B83D24FBF
PG_0740_004.SAR system
OTBCSL30_INST_U
OTBCSL30 1610_104 8A87CB35AF
PG_1610_104.SAR
OTEXVIM_INST_U
OTEXVIM 81610_104 9182CE4BB8
PG_1610_104.SAR
OTBCUS03_INST_U On frontend
OTBCUS03 0740_004 8B81D436AC
PG_0740_004.SAR system
OTBCSL38_0700_00
OTBCSL38 0700_005 8C87CF35A7
5.SAR
Note: For the ACP file of the OTBCSL38 component, see the following
direct link to the PATCHES area: https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/64946881.
The following optional Business Center components, which are also available to
VIM customers, are described in the first table in Section 6 “Installing” in
OpenText Business Center for SAP Solutions - Installation Guide (BOCP-IGD).
For their usage, see Section 6.1.1 “Basic SAP installation packages” in OpenText
Business Center for SAP Solutions - Installation Guide (BOCP-IGD) and Section
6.1.2 “Optional S/4HANA installation packages” in OpenText Business Center for
SAP Solutions - Installation Guide (BOCP-IGD).
Business Center solutions

OTBCSL01, OTBCSL02, OTBCSL05, OTBCSL07, OTBCSL09, OTBCSL10
Packages for SAP S/4HANA
OTBCS4, OTBCS4SL
Extended ECM for SAP Solutions integration for Business Center
OTBCRM
2. Collect all support packages for these components.

Support packages are available on My Support for all customers. See https://
knowledge.opentext.com/knowledge/cs.dll/Open/10151605.

Table 3-2: VIM support packages - installation files
Support
Component File Remark
Package
OTBCBAS 0001 OTBCBAS_SP01_0700_004.SAR
0002 OTBCBAS_SP02_0700_004.SAR
OTBCFND 0001 OTBCFND_SP01_0700_004.SAR
0002 OTBCFND_SP02_0700_004.SAR
OTBCINB 0001 OTBCINB_SP01_0700_004.SAR
0002 OTBCINB_SP02_0700_004.SAR
OTBCSL00 0001 OTBCSL00_SP01_0700_004.SAR
0002 OTBCSL00_SP02_0700_004.SAR
0003 OTBCSL00_SP03_0700_004.SAR
0004 OTBCSL00_SP04_0700_004.SAR
0005 OTBCSL00_SP05_0700_004.SAR
OTBCWSR 0001 OTBCWSR_SP01_0740_004.SAR
0002 OTBCWSR_SP02_0740_004.SAR
On frontend
OTBCWUI 0001 OTBCWUI_SP01_0740_004.SAR
system
On frontend
0002 OTBCWUI_SP02_0740_004.SAR
system
On frontend
system
On frontend
system

3.2. Selecting required components and downloading the packages
Support
Package
On frontend
system
0002 OTBCSL30_SP02_1610_104.SAR
0003 OTBCSL30_SP03_1610_104.SAR
0004 OTBCSL30_SP04_1610_104.SAR
0005 OTBCSL30_SP05_1610_104.SAR
OTEXVIM 0001 OTEXVIM_SP01_1610_104.SAR
0002 OTEXVIM_SP02_1610_104.SAR
On frontend
OTBCUS03 0001 OTBCUS03_SP01_0740_004.SAR
system
On frontend
0002 OTBCUS03_SP02_0740_004.SAR
system
On frontend
0003 OTBCUS03_SP03_0740_004.SAR
system
On frontend
0004 OTBCUS03_SP04_0740_004.SAR
system
OTBCSL38 0001 OTBCSL38_0700_01.SAR
3. Collect the latest post installation transports on My Support. See https://

Binary name Description Install on Variant

fiori_perspectives_ This binary contains the Back end On-premise
layouts.zip perspectives layouts of the
VIM Fiori apps. These
layouts are rendered
during loading of the Fiori
apps.
vendorinvoicemanagem This binary contains pre- Front end On-premise
ent- configured tiles and target
launchpadcontent.zip mapping for the VIM Fiori
apps. It is applicable for on-
premise deployment.

Binary name Description Install on Variant

neo_ This binary contains the Cloud SCP
VendorInvoiceManagem preconfigured Fiori
ent- Launchpad portal site for
LaunchpadContent.zip the VIM Fiori apps. It is
applicable for cloud
deployment.
vim_neo_ui_03.zip This binary contains the Cloud SCP
VIM Fiori apps UI. It is
deployment.
otusrregui_neo.zip This binary contains the Cloud SCP
VIM Supplier Self Service
registration UI. It is
deployment.
fiori_post_ This binary contains Back end On-premise
installation_ additional transports for
advancecoding.zip customizations of the VIM
Enter Cost Assignment
Advanced Fiori app.
fiori_post_ This binary contains Back end On-premise
installation_ additional transports for
customization.zip customizations of the VIM
Enter Cost Assignment
Advanced Fiori app.
4. Collect the latest language packs for these components on My Support. See
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/71426734.
3.3 Installing the package

To install packages:
1. Run the SAINT transaction.
2. On the menu, click Load Packages to upload the SAR files. Use From Front End
if the installation package is available on your local client. If it is already copied
to the application server, use From application server.
3. Select the components for installation. For more information, see “Selecting
required components and downloading the packages” on page 26.
4. In the support package selection, choose the latest support package for each
component.
5. Double check if all needed components are selected for the installation queue
with the latest support package versions.

3.3. Installing the package
6. Click Continue and follow the installation procedure.
7. Verify the installation.

Make sure that the OpenText Vendor Invoice Management add-on is reflected
in the installed components.
a. From the SAP menu, open System > Status.

b. Click the button next to Component version.

In the System: Component information dialog, you should see the

OpenText add-on components installed.
8. Additional steps that are required when using a separate frontend server
Install Web Services.
a. Install the Business Center Web UI (OTBCWUI) add-on using the SAINT
transaction on the system that you want to use for the Web UI.
b. On the same system, install available Support Packages for the Business
Center Web UI (OTBCWUI) using the SPAM transaction.
c. On the same system, install the VIM Web UI (OTBCUS03) add-on using
the SAINT transaction.
d. On the same system, install available Support Packages for VIM Web UI
(OTBCUS03) using the SPAM transaction.
Important
Installing the Business Center Web Services (OTBCWSR) on a different
system than the Business Center Foundation (OTBCFND) is not
supported.
Alternatively, you can choose the SAP Cloud Platform (SCP) deployment
option. For details, see Section 4.2 “Deployment options on SAP Cloud
Platform” in OpenText Business Center for SAP Solutions - Installation Guide
(BOCP-IGD).

3.3. Installing the package
ZIP File Version in Applicatio UI5 UI5 PF05_DA OTBCWS

Name Manifest n Name Compone Version TA R Version
nt Version
vim_neo_ 16.3 SP5 pf07bcvim ot.approve 1.71 003 0740_004
ui_03 neoui03 .requests0 SP5
3
The installation steps for VIM are the same as for Business Center (see Section
6.2 “Installing the Business Center UI on SAP Cloud Platform Neo account” in
OpenText Business Center for SAP Solutions - Installation Guide (BOCP-IGD))
except the following:
• The file to import in the provider subaccount is PF07_BC_VIM_NEO_UI_03.

zip.
• 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:
9. Continue with the post installation steps. For more information, see “Post
installation activities” on page 34.

3.4 Post installation activities

To ensure the integrity of the installed transports, you have to perform and validate
the following procedures:
• “Importing transport with Fiori layouts” on page 34

• “Installing transport with layout variants” on page 35
• “Activating Business Configuration Sets” on page 36
• “Configuring workflow dialog tasks” on page 38
• “Refreshing SAP workflow runtime buffer” on page 40
• “Configuring object services” on page 41
• “Maintaining number ranges” on page 42
• “Linking events for VIM workflows” on page 45
• “Maintaining the SAPscript form for approval” on page 47
• “Maintaining standard text” on page 49
• “Setting background user parameters for Non PO invoice posting” on page 51
• “Configuring additional settings” on page 52
• “Maintaining Business Transaction Events” on page 53
• “Configuring the system landscape” on page 53
• “Fiori: Activating services” on page 54
• “Fiori: Setting up Launchpad content on-premise” on page 54
• “Fiori: Setting up Launchpad content on cloud” on page 55
• “Fiori: Deploying Fiori apps on cloud” on page 56
• “Performing the mandatory configuration” on page 56
3.4.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 My Support. See https://

• Fiori_Perspectives_layouts.zip: Post install - VIM Fiori Perspectives
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

3.4. Post installation activities
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
3.4.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 latest version of this transport on My Support.

3.4.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 Business Center are cumulative. Therefore, with new
installations, always use only the most recent BC set. The VIM BC set /
OTEXVIM/VIM16_3_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 71.
• 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 Business Center BC sets:
1. Activate Business Center BC sets using the SCPR20 transaction according to

OpenText Business Center for SAP Solutions - Installation Guide (BOCP-IGD).
a. /OTX/PF00_GENERAL_SET_004_04 for the basic settings

b. /OTX/PF01_INBOUND_004_04 for the inbound settings
c. /OTX/PF02_FOUNDATION_004_04 for the foundation configuration
d. Optional /OTX/PS00_BASE_004_04 for the basic settings of Business Center
solutions
e. Optional /OTBCSL38/EDOCU_INTEGRATION_SAP for the integration of VIM
with SAP eDocument
2. Activate BC set /OTEXVIM/VIM16_3_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.
To activate BC Sets:
1. To access the Business Configuration Sets: Activation screen, run the SCPR20
transaction.
2. Enter the BC set name /OTEXVIM/VIM16_3_BASELINE and click Activate .
Note: If you are prompted to create a new transport, follow your standard
change request process for tracking changes.
3. Apply the recommended settings, as shown in the screenshot.
4. Click Activate.
After BC Set activation, a message is displayed in the lower left of the SAP GUI,
for example: Activation ended with warning.
Tip: You can ignore any warnings during the activation. If you get an
error during activation of a BC set, then activate it again. In many cases the

error will disappear. You can ignore activation errors like No data found
for writing activation links for object <xxx>.
3.4.4 Configuring workflow dialog tasks

Use the instructions in this section to set the attribute to “General Task” for the
following tasks:
Table 3-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 3-3 on page 38.
3.4.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.
3.4.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.
3.4.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.

3.4.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 3-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 45 (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 45.
3.4.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.

3.4.10 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 21.4 “Maintaining email
templates” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD) and Section 21.6 “Maintaining the email signature” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD). If you
want to use custom specific texts, you may skip copying the following texts.
• /OPT/VIM_RTV_TEMPLATE
• /OPT/VIM_SIGNATURE_RTV
Copying the following texts is only required if the SRM PO functionality is being
implemented in VIM.
• /OPT/VIM_DP_SRM_PRICE_HEADER
• /OPT/VIM_DP_SRM_QTY_FOOTER
• /OPT/VIM_DP_SRM_QTY_HEADER
• /OPT/VIM_DP_SRM_QTY_URL_HEAD
To maintain standard text:
1. Run the SO10 transaction.

2. Navigate to the menu path Utilities > Copy from Client.
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.
3.4.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.
To set background user parameters for Non PO invoice posting:
1. Run the SU01 transaction and open the user WF-BATCH in edit mode.
2. Enter the following parameter:
Parameter ID Parameter value

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

3.4.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
(for SAP ERP 6.0 version), see Section 11.11.3 “Enhancing MIRO for pre-
population of data during online invoice creation” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
• Regarding the configuration of BAdIs for invoice processing, see Section 11.9.1
“Activating BAdI for invoice processing” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide (VIM-CGD).
Use transaction SE19 to check the runtime behavior of the BAdIs. The following
are the standard values:
BAdI Implementation Runtime behavior

/OPT/VIM_MIGO_ENH /OPT/VIM_CHECK_MIGO Implementation is called
/OPT/VIM_MIRO_ENH /OPT/VIM_CHECK_MIRO Implementation is called
/OPT/ /OPT/ Implementation is not
VIM_ENH_SPOT_MIRO CL_IM_VIM_BADI_MIRO called

3.4.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
3.4.14 Configuring the system landscape

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

3.4.15 Fiori: Activating services

The following steps are required for the Business Center 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 in Business Center. For general information, see Section 6.4.1
“Enabling OData service” in OpenText Business Center for SAP Solutions -
Installation Guide (BOCP-IGD).
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 Section 6.4.2 “Activating the service” in OpenText
Business Center for SAP Solutions - Installation Guide (BOCP-IGD).
3.4.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 9.1.1 “Integrating Fiori Task App into Fiori
Launchpad” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP-CGD). Import the mentioned transport or configure the tiles.
The tiles are also delivered with transports: VendorInvoiceManagement-

LaunchpadContent.zip. You can access them on My Support: https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/71941132
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
3.4.17 Fiori: Setting up Launchpad content on cloud

The tiles are also delivered in the following ZIP file: neo_
VendorInvoiceManagement-LaunchpadContent.zip, available on My Support:
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/77755532

3.4.18 Fiori: Deploying Fiori apps on cloud

The VIM Fiori apps with the Business Center Web UI: ZIP file vim_neo_ui_03.zip,
available on My Support: https://knowledge.opentext.com/knowledge/llisapi.dll/
Open/77755532.
The VIM Supplier Self Service Registration UI for SCP is delivered in ZIP file
otusrregui_neo.zip, available on My Support: https://knowledge.opentext.com/
For more details, see Section 6.2 “Installing the Business Center UI on SAP Cloud
Platform Neo account” in OpenText Business Center for SAP Solutions - Installation
Guide (BOCP-IGD).
3.4.19 Performing the mandatory configuration

Perform the mandatory customizing as described in Part III “Mandatory
configuration” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
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 7 “Defining rollout criteria for parking and blocking processes” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
3.5 Language packs

Languages for VIM (except for English) are delivered in language packs, which you
can obtain on OpenText My Support: https://knowledge.opentext.com/knowledge/
llisapi.dll/Open/71426625. For the Business Center integration into VIM, additional
language packs are available.
3.5.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 (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.

3.5. Language packs
3.5.2 Business Center integration into VIM: language packs

Business Center components can be deployed together with VIM. In this case, you
must install the corresponding language pack of the Business Center components
together with the language pack of VIM. This applies to the following language
pack:
• Language Pack of Business Center Foundation OTBCFND

This language pack includes the Language Pack of Business Center Inbound
OTBCINB.
Note: Language packs are delivered for some, not for all Business Center
packages. The remaining packages are not translation-relevant.
You find the language packs in the Business Center folder on My Support:
https://knowledge.opentext.com/knowledge/cs.dll/Open/60760095

Chapter 4
Installing Single Click Entry for SAP GUI
VIM provides the Single Click Entry feature in the DP Dashboard. The Single Click
Entry feature allows users to easily capture index data by clicking the appropriate
field zone of the invoice that is displayed in the Detail pane of the DP Dashboard.
For more information, see Section 4.2 “Using the Single Click Entry feature” in
OpenText Vendor Invoice Management for SAP Solutions - User Guide (VIM-UGD).
Notes
• Single Click Entry is an optional feature. If it is not installed, the

functionality is just not available in the DP Dashboard.
• Single Click Entry only supports SAP GUI for Windows, no other SAP GUIs.
• To use Single Click Entry, invoice data must be provided by Invoice Capture
Center (ICC) or Information Extraction Service (IES). Single Click Entry only
works if the DP process has been started by those two OCR solutions from
OpenText.
• “Information Extraction Service” (“IES”) is used in this documentation as a

common technical term for both of the following OpenText products:
– OpenText™ Intelligent Capture for SAP® Solutions, formerly known as

OpenText™ Information Extraction Service for SAP® Solutions (IES on
premise)
– OpenText™ Core Capture for SAP® Solutions
You download the software for Single Click Entry from My Support: https://
knowledge.opentext.com/knowledge/cs.dll/Open/77746988
Alternatively, you can download the software for Single Click Entry from My
Support, from the folder for OpenText™ Invoice Capture Center for SAP® Solutions:
Note: For Single Click Entry to work correctly with IES, the Single Click Entry
control needs to be updated to the latest version, patch 26 minimum.
The installation of Single Click Entry is described in Section 2.3.6 “Installing Single
Click Entry for SAP GUI” in OpenText Business Center Capture for SAP Solutions -
Administration Guide (CPBC-AGD). You find the Invoice Capture Center
documentation on My Support: https://knowledge.opentext.com/knowledge/cs.dll/
Open/15448194. Open the folder of the appropriate version.

Chapter 5
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 83.
5.1 SAP prerequisites

Make sure that you already have installed the latest VIM SP. Any repairs made to
the VIM objects will be overwritten by the new SP.
To check the SAP prerequisites:
1. From the SAP menu, open System > Status.
2. Click the Details button next to Product Version.

In the System: Component information dialog box, you should see the VIM
add-on components installed.
3. Check the versions of installed components. Refer to “VIM support packages -

installation files” on page 28.

Chapter 5 Installing a VIM Support Package
4. Select required components and download the packages.

Collect all missing Support Package files as shown in “Selecting required
components and downloading the packages” on page 26.
Note: If VIM 7.5 is installed on your system, refer to “Upgrading“

on page 73.
5.2 Collecting Support Packages

Collect the Support Package installation files for the components listed in “VIM
components - installation files” on page 26. Select the files whose SP level is higher
than the one installed in your system.
Support packages are available on My Support for all customers. For more
information, see https://knowledge.opentext.com/knowledge/cs.dll/Open/10151605.
Table 5-1: VIM support packages - installation files
Support
Package
OTBCBAS 0001 OTBCBAS_SP01_0700_004.SAR
OTBCFND 0001 OTBCFND_SP01_0700_004.SAR
OTBCINB 0001 OTBCINB_SP01_0700_004.SAR

5.2. Collecting Support Packages
Support
Package
0002 OTBCSL00_SP02_0700_004.SAR
0003 OTBCSL00_SP03_0700_004.SAR
0004 OTBCSL00_SP04_0700_004.SAR
0005 OTBCSL00_SP05_0700_004.SAR
OTBCWSR 0001 OTBCWSR_SP01_0740_004.SAR
On frontend
OTBCWUI 0001 OTBCWUI_SP01_0740_004.SAR
system
On frontend
system
On frontend
system
On frontend
system
On frontend
system
0002 OTBCSL30_SP02_1610_104.SAR
0003 OTBCSL30_SP03_1610_104.SAR
0004 OTBCSL30_SP04_1610_104.SAR
0005 OTBCSL30_SP05_1610_104.SAR
OTEXVIM 0001 OTEXVIM_SP01_1610_104.SAR

Support
Package
On frontend
OTBCUS03 0001 OTBCUS03_SP01_0740_004.SAR
system
On frontend
0002 OTBCUS03_SP02_0740_004.SAR
system
On frontend
0003 OTBCUS03_SP03_0740_004.SAR
system
On frontend
0004 OTBCUS03_SP04_0740_004.SAR
system
OTBCSL38 0001 OTBCSL38_0700_01.SAR
Note: If other Business Center solutions are installed on the system, you must
update them to the matching Support Package as well. For details, refer to the
Business Center documentation.
5.3 SAP installation

1. Determine which VIM Support Package file is needed based upon your SAP
version. For more information, see the Release Notes for the Support Package.
2. Open the SAP GUI and access client 000 as the DDIC user.
3. Run the /nSPAM transaction.
4. In the Support Package Manager window, click Support Package > Load
Packages > From Frontend.
5. Upload all collected SAR files.
6. To define the SPAM Queue, click the Display/define button.

5.3. SAP installation
7. Click All Components.

Select Support Packages for all installed VIM/OTBC components.
8. Calculate the queue.

9. Check if all VIM components show the correct target level.
10. Confirm the queue.
11. In the Extras menu, click Settings.
The SPAM: Settings screen opens.

12. Click the Always radio button in the section ABAP/Screen Generation. Then
click the confirmation checkmark.
13. In the Extras menu, click Ignore generation errors.
Note: This step is Support Package specific. Perform it if it is mentioned in

the Release Notes of the Support Package.
The Support Package may contain Data Dictionary changes that require
database table conversions or other additional activities. Without performing
these additional activities, the generation will result in errors that must be
ignored first.
14. You are now ready to import. Click the Import Truck button to begin.
The Import Queue confirmation is displayed.

15. At this point, you can choose the Start Options, which control whether each
phase executes in a dialog process or a background process. Make your
selections and start by clicking the confirmation checkmark button.

The import starts running. If you chose to run in dialog, you see the process
steps running at the bottom of the screen. Otherwise you need to monitor the
log.
When the import has completed, you see a message Queue <queue name>
imported successfully in the dialog box.
16. Click the Checkmark button.
17. Now check the import logs for errors, code 8 or above. To display the logs, click
the Import Log button.
18. Verify that you do not have any error codes eight (8) or above. Warning codes
of four (4) are acceptable.
Note: Some objects can display generation errors. For a list of these
objects, see the Release Notes for the Support Package.
19. When you have finished viewing, click the Back button.
20. To resolve the domain and tables generation errors (see Step 13 on page 67), the
table data must be converted with the SAP Database Utility (transaction SE14).
Open this transaction in a new window and perform the conversion for each of
the tables listed in the Release Notes for the Support Package.

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

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

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

5.4. Post installation activities after installing a new Support Package
5.4 Post installation activities after installing a new

Support Package
5.4.1 Importing transport with Fiori layouts
After installing a new Support Package, you must import the following transport to
the systems where you have installed the VIM Support Package. It is necessary for
the Fiori apps to work.

5.4.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.
The BC sets for post installation activities after installing a Support Package are the
following:
Upgrade from BC sets to activate

VIM 16.3 /OTEXVIM/VIM16_3_UPGRADE_SP1
/OTEXVIM/VIM16_3_UPGRADE_SP2
VIM 16.3.1 /OTEXVIM/VIM16_3_UPGRADE_SP2

Upgrade from BC sets to activate

/OTEXVIM/VIM16_3_DOCTYPES
Optional. Activate this BC set if you want to install the latest VIM standard
baseline document type definitions. Existing custom document types are not
changed.
This BC set is updated with each Support Package to reflect the latest baseline
document type configuration.
5.4.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.

Chapter 6
Upgrading
This chapter describes the following upgrade scenario:
• Upgrading from VIM 7.5 SP7 (or later) to VIM 16.3 on SAP S/4HANA. For more
information, see “Upgrading VIM 7.5 to VIM 16.3” on page 73.
For information about upgrading from any VIM version on SAP ERP to VIM 7.5 SP7
or later, see Section 7.4 “Upgrading VIM” in OpenText Vendor Invoice Management for
SAP Solutions - Installation Guide (VIME070509-IGD).
For troubleshooting information about handling workflow container inconsistencies,

see “Handling workflow container inconsistencies” on page 83.
6.1 Upgrading VIM 7.5 to VIM 16.3

In most cases, an upgrade of VIM 7.5 to VIM 16.3 will be done during a conversion
to a new SAP S/4HANA version. For a description of this case, see “Upgrading to
VIM 16.3 during an SAP S/4HANA conversion” on page 73.
For a description of an upgrade from VIM 7.5 to VIM 16.3 without an SAP S/
4HANA conversion, see “Upgrading to VIM 16.3 without conversion” on page 76.
6.1.1 Upgrading to VIM 16.3 during an SAP S/4HANA

conversion
This section describes the process to perform during an SAP S/4HANA conversion
with regards to VIM.
Important
If you convert to SAP S/4HANA 1809 or later releases from earlier SAP S/
4HANA releases, OpenText recommends the following upgrade strategy:
• If you have installed SAP ECC or SAP S/4HANA 1610 or earlier (including
Suite on HANA, Simple Finance) with VIM 7.5, upgrade VIM to 7.5 SP8.
• If you have installed SAP S/4HANA 1610 or later with VIM 16.3, upgrade
VIM to 16.3.2 or later.
• Perform the SAP upgrade in a second step. This will help to avoid
unnecessary conversions of VIM database tables that would be done
because of amount field length extension. For more information, see SAP
note 2628654.

Chapter 6 Upgrading
SAP S/4HANA In your environment, you might have VIM 7.5 installed in the system and plan to
conversion and run a conversion from SAP ERP to SAP S/4HANA or to a later SAP S/4HANA
VIM licenses
version. During the conversion, VIM needs to be upgraded to 16.3.
• SAP offers an upgrade path from VIM 7.5 SP7 or later to VIM 16.3.2 in the
Maintenance Planner. Before the conversion, update at least to VIM 7.5 SP7 with
Business Center 16.3. During the conversion, upgrade to VIM 16.3.2 with
Business Center 16.3.2.
Note: The upgrade to VIM 16.3.2 with Business Center 16.3.2 is especially
required when doing a conversion to SAP S/4HANA 1809 or later releases.
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 16.3 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. Apply 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.

6.1. Upgrading VIM 7.5 to VIM 16.3
6.1.1.1 Preparing the conversion
Checking obsolete components

Review the VIM 16.3 Release Notes for obsoleted components and features. During
the conversion, objects removed from the VIM 16.3 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
compatible with SAP S/4HANA. When the conversion is finished, install the
component OTVIMGW that is provided with the VIM 16.3 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.
6.1.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, or 1909
• On SAP ERP 6.0 or SAP S/4HANA 1511, the VIM component OTEXVIM needs
to be updated to VIM 7.5 SP7 or later with Business Center 16.3 before the
conversion. For more information, see Section 7.4 “Upgrading VIM” in
OpenText Vendor Invoice Management for SAP Solutions - Installation Guide
(VIME070509-IGD).
• On SAP S/4HANA 1610 or later, the VIM components need to be updated to
VIM 16.3.2 or later before the conversion.
• 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.

Chapter 6 Upgrading
• During the conversion, for VIM and Business Center add-ons, the target
version 16.3.2 or later 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 16.3 during an SAP
S/4HANA conversion” on page 73.
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 78.
Performing the SAP S/4HANA conversion – For the actual SAP S/4HANA
conversion, use the guides provided by SAP, for example https://help.sap.com/
viewer/7bfe8cdcfbb040dcb6702dada8c3e2f0/latest/en-US/
5c41b3173c9a4aca8c05392635d622f4.html.
6.1.2 Upgrading to VIM 16.3 without conversion

This section describes an upgrade of VIM 7.5 to VIM 16.3 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
• OpenText recommends that you update to VIM 7.5 SP7 and finish post
installation steps for VIM 7.5 and all support packages before upgrading to VIM
16.3. An upgrade BC set (/OTEXVIM/VIM16_3_UPGRADE) from VIM 7.5 to VIM
16.3 (any SP) is delivered to minimize the impact on customizing during
upgrade.
Note: Technically it is possible to upgrade from lower support package

levels to VIM 16.3 directly. However be aware that you must review the
post installation steps of skipped VIM 7.5 SPs and execute them if
necessary. The BC sets delivered in these 7.5 SPs are not in included in the
VIM 16.3 package.

The corresponding configuration is only delivered with the installation BC

set /OTEXVIM/VIM16_3_BASELINE, which normally should not be used for
upgrades. However you can use this BC set as a reference when upgrading
from lower SP levels than 7.5 SP6.
OpenText advises against activating the BC set during the upgrade because
it will overwrite any changed standard configuration. Instead you can
detect missing entries manually, using the compare functionality in the
SCPR20 transaction.
6.1.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. Refer to “VIM support
packages - installation files” on page 28.
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 26.
Notes
• Several components of VIM 7.5 may be installed on your system that are
now included in the OTEXVIM main package: OTBCSL03, OTBCSL33,
OTVIMARB, OTVIMCDS, OTVIMS4. For these components, no action is
required because these are updated with the main package.
• If the demo package OTVIMWSR is installed on your system, download
the ACP file for VIM 16.3 and upload it using SAINT before the upgrade.
You find the file on My Support: https://knowledge.opentext.com/
6.1.2.2 Installing the package

For the installation steps that you need to perform, see “Installing the package”
on page 30.
If you perform the upgrade during an SAP S/4HANA conversion, also see
“Upgrading to VIM 16.3 during an SAP S/4HANA conversion” on page 73

Chapter 6 Upgrading
6.1.3 Post installation activities after an upgrade

To ensure the integrity of the installed transports, you must perform and validate
the following procedures:
• “Importing transport with Fiori layouts” on page 78

• “Activating business configuration sets” on page 78
• “Checking status and runtime behavior of BAdIs for Invoice Processing”
on page 80
• “Reviewing BAPI for extended VAT date support” on page 80
• “Checking Business Center Inbound Configuration” on page 81
• “Checking the logic module configuration” on page 81
• “Reviewing posting logic in current document types” on page 82
• “Reviewing parked processing” on page 82
• “Updating Fiori launchpad tiles” on page 82
6.1.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.

6.1.3.2 Activating business configuration sets

Notes
• To activate the BC sets, sign in in English and use the expert mode.
• You must activate the BC sets in every client separately.
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 16.3. 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.

Afterwards, continue with the instructions for VIM 7.5 SP6.
Upgrading from Activate the following BC sets:

VIM 7.5 SP6
/OTEXVIM/VIM16_3_UPGRADE_75SP6
Activate this BC set. It contains new table entries for the upgrade to VIM 16.3.
You can use the comparison function of the SCPR20 transaction to evaluate the
changes.
Activate this BC set. It contains new table entries for VIM 16.3.1. You can use the
comparison function of the SCPR20 transaction to evaluate the changes.
Upgrading from Activate the following BC sets:

VIM 7.5 SP7
and later, up to
VIM 7.5 SP10 /OTEXVIM/VIM16_3_UPGRADE
Activate this BC set. It contains new table entries for VIM 16.3. You can use the
/OTEXVIM/VIM16_3_UPGRADE_SP1_COR

Chapter 6 Upgrading
Upgrading from Activate the following BC set:

VIM 7.5 SP11
/OTEXVIM/VIM16_3_UPGRADE
Activate this BC set. It contains new table entries for VIM 16.3. You can use the
For all Optionally activate the following BC set:

upgrades
/OTEXVIM/VIM16_3_DOCTYPES
Optional. Activate this BC set if you want to install the latest VIM standard
baseline document type definitions. Existing document types are not changed.
This BC set is updated with each support package to reflect the latest baseline
document type configuration.
6.1.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:
BAdI Implementation Runtime behavior

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

Status for Business Function /OPT/VIM_SFW_MIRO empty (in the SFW5 transaction).
6.1.3.4 Reviewing BAPI 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.

6.1.3.5 Checking Business Center Inbound Configuration

Business Center Inbound is mandatory for VIM 16.3. 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 9 “Incoming

document processing” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
6.1.3.6 Checking the logic module configuration

VIM 7.5 introduced logic module processing. For more information, see Section 11.4
“Processing logic modules” in OpenText Vendor Invoice Management for SAP Solutions
- Configuration Guide (VIM-CGD).
As an upgrade customer on VIM 7.5, you may still be running VIM in a 7.0 mode
without logic modules. For 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 introduces 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 BC Set /OTEXVIM/VIM16_3_DOCTYPES.
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 (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 (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 (VIM-RGD).

Chapter 6 Upgrading
6.1.3.7 Reviewing posting logic in current document types

VIM 16.3 introduces 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 33 “Posting invoices” in OpenText Vendor Invoice
6.1.3.8 Reviewing parked processing

VIM 16.3 replaces parked processing for NPO and PO invoices by processing parked
documents in DP. For more information, see Section 11.3 “Configuring parked
processing” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
Old parked processes are no longer supported. Continuing their usage must be
evaluated and tested customer-specifically.
6.1.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 54.
6.2 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 6-1: ACP files for VIM 16.3
Component PAT file Comments

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

Chapter 7
Troubleshooting
7.1 FAQs
The following FAQs cover basic troubleshooting information.
Does VIM consist of any standard SAP objects/repairs?

No
Does VIM consist of any Z objects?

No
How do I check whether installation is successful?

Refer to Step 7 on page 31.
What is the namespace?

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

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

Make sure the standard task is defined as a general task.
7.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

Chapter 7 Troubleshooting
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.
The only VIM database table that is currently known to cause these problems is
table /OPT/VIM_1HEAD. OpenText recommends that you create a copy (for example
with the name ZZZ1HEAD) in transaction SE11. It is important that the table copy will
not reference any include or append structures. You can achieve this by performing
the following steps:
To expand includes:
1. Copy the table /OPT/VIM_1HEAD.

2. Without activating the copy, open it in change mode.
3. Set the pointer on each include line (.INCLUDE) that is still displayed, and, on
the Edit menu, click Include > Copy Components.
Normally, all fields will be expanded at once. After this, you can activate the
table.
7.3 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 11.1.7

7.4. Issue with loading Fiori apps
“Customizing field labels in the index screen” in OpenText Vendor Invoice

Management for SAP Solutions - Configuration Guide (VIM-CGD). In this case,
the entries are automatically stored in a customizing request.
7.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/VIM16_3_BASELINE has been activated correctly,
including all Sub-BC-sets.
• If there are still issues, reactivate BC set /OTEXVIM/VIM16_3_BASELINE_B5 (for
VIM Fiori apps) and BC set /OTEXVIM/VIM16_3_BASELINE_B6 (for Supplier Self
Service Fiori app).

Part 3
Simple Mode VIM installation
Part 3 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 30.

Chapter 8
Overview
Simple Mode provides additional apps, which are based on SAP Fiori:
VIM My Invoices 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 My Invoices 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 or a
mobile device.
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 9
Simple Mode installation
This section summarizes the required installation steps and their sequence for
installing Simple Mode.
9.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 70

• 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

Chapter 9 Simple Mode installation
Table 9-1: Installed Business Center and VIM components
Component Release SP level

OTBCBAS 0700_004 0004
OTBCFND 0700_004 0004
OTBCINB 0700_004 0004
OTBCSL00 0700_004 0004
OTBCWSR 0740_004 0004
OTBCSL30 1610_104 0004
Notes
• For more information, see “VIM classic mode installation” on page 19

and “Installing the package” on page 30.
• 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 9-2: Installed Business Center component
Component Release SP level

OTBCWUI 0740_004 0004

9.2. Installing the Simple Mode components
9.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, OTBCINB,
OTBCFND, OTBCWSR, 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 26.
To install the Simple Mode components:
1. Download the following installation files:
Component Release Filename OCS Package Password

OTBCSL08 1610_104 OTBCSL08_INST SAPK-104COIN 8A87CB36A7
_UPG_1610_104. OTBCSL08
SAR
2. Download the following support packages:
Component Support File

Package
3. Collect the latest post installation transports on My Support. See https://

Transport File
OTBCSL08_PostInstallation_ Postinstall - VIM Fiori
FIORI_Perspectives.zip perspectives
OTBCSL08_PostInstallation_ Postinstall - FIORI Launchpad
FIORI_Launchpad_Content.zip content
4. Collect the latest language packages for these components on My Support. See
5. Install VIM 16.3 – 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 91
are not installed on the system, install all add-ons with all Support
Packages at once.

b. Follow the instructions in Section 6 “Installing” in OpenText Business Center

for SAP Solutions - Installation Guide (BOCP-IGD) regarding post installation
activities like BC sets activation, service activation, and so on.
c. Activate the BC set /OTX/PS08_INVOICE_004_04 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 3 on page 93.
e. Install the language pack for component OTBCSL08.
f. Perform the customizing as described in Part II “Simple Mode VIM” in

(VIM-CGD).
g. Also perform the customizing as described in Part II “General features and

configuration” in OpenText Business Center for SAP Solutions - Scenario Guide
(BOCP-CCS).
6. Set up the Fiori Launchpad tiles for the Simple Mode based Fiori apps.
The general setup is described in Section 9.1.1 “Integrating Fiori Task App into
Fiori Launchpad” in OpenText Business Center for SAP Solutions - Configuration
Guide (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 3 on page 93. You
can access them on My Support. For details, see Section 6.6 “Fiori launchpad content (On premise)”
in OpenText Business Center for SAP Solutions - Installation Guide (BOCP-IGD).

9.3 Post installation activities

9.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 21.4 “Maintaining email
templates” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD) and Section 21.6 “Maintaining the email signature” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (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.

9.4. Troubleshooting
9.4 Troubleshooting
This section collects possible problems with the installation of Simple Mode. It also
provides information how to solve these problems.
9.4.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.

Part 4
KPI Dashboard installation
Part 4 KPI Dashboard installation
This part describes the installation and post installation activities needed for the
“Key Performance Indicator” Dashboard (KPI Dashboard). The KPI Dashboard is a
tool for managers showing VIM related process data at a glance in graphical charts.
For further information, see Section 28 “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.

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

Chapter 11
Post installation activities
The following activities are needed to configure the KPI Dashboard on your system.
11.1 Activating the SAP Web Dynpro service

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

Chapter 11 Post installation activities
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.

11.1. Activating the SAP Web Dynpro service
4. Highlight vim_kpi_MAIN and, on the menu, click Service/Host > Activate.

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

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:

11.1. Activating the SAP Web Dynpro service
• Logon Errors
• Application Errors
• Logoff Page
• Not Accessible

11.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: https://help.sap.com/viewer/
e73bba71770e4c0ca5fb2a3c17e8e229/latest/en-US/
4923501ebf5a1902e10000000a42189c.html
Do not change the service settings described in “Activating the SAP Web Dynpro
service” on page 103. Make sure that the SSL settings are not activated in the Logon
Data tab.

11.3. Setting up the SAP NetWeaver Portal integration
Change the KPI constant DASHBOARD_START_URL to https://xxxxx:8443/xxxx. See

Section 28.4.10.5 “KPI Dashboard start URL” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide (VIM-CGD).
11.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: https://help.sap.com/viewer/
f2f3f4b4543a4803b9023e8c31f1e72a/latest/en-US/
4b8d0808231e2b5fe10000000a42189c.html. Follow the description of creating an
iView type based on a Web Dynpro ABAP application.
11.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.

11.3. Setting up the SAP NetWeaver Portal integration
The property values to enter can be read from the ABAP system using
transactions SICF and SMICM.
For a detailed description how to set up the System Object in the Portal, see
http://wiki.sdn.sap.com/wiki/display/EP/How+to+Create+System+Object+in+the
+Portal+for+Connecting+to+SAP+backend+System.
11.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.

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

only or as an application inside NWP using AppIntegrator iView. Install all the
components in a coordinated manner.
Notes
• The Approval Portal is an optional component.

• If you are not using the Approval Portal, you can skip this part.
• Please refer to Section 12 “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.

Chapter 12
12.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.0 SP9 or above with
SPNegoLoginModule and NWAS 7.3 SP3 or above and NWAS 7.4 SP3 or above.
For SPNego configuration, see SAP Note 1488409.
SAP NetWeaver Portal

SAP NetWeaver Portal (NWP) 7.0 SP9 or above and NWP 7.3 SP3 or above and
NWP 7.4 SP3 or above and NWP 7.5.
Notes
• Approval Portal 7.5 SP6 JCO3 Java 1.8 and Approval Portal 7.5 SP6 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.0
NWAS 7.3
NWAS 7.4
NWAS 7.5
NWP 7.0
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.0 apply.
ments
SAP user A 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:

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

/ORS/*, /OPT/*, /PTGWFI/*
The following 2 authorization objects for the CPIC user are applicable for SAP
ERP 702 SP14 and higher and SAP NetWeaver Portal 702 SP15 and higher:
Object: S_RZL_ADM (Authorization object for R/3 system administration)
Activity
Display (03)
Object: S_WF_SUBST (Workflow: substitute rule)
Activity
Display (03)
Additional SAP Standard Profile needed: S_A.CPIC and S_A.USER

Note: If you are using an Archive Server to pull in images, you may need
to assign additional roles. See the Archive Server Installation manual.
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
12.2 Installation components

Both Software Component Archive (.sca) file and Software Deployment Archive
(.sda) file are supplied; you can choose which format is suitable for your situation.
Each file contains the following:
• SAP NetWeaver Application Server Java components

• Java Enterprise archive (.ear file) - for the actual J2EE application
VIM 7.5 SPx installation package
For all Support Packages of VIM 7.5, the respective OpenText Vendor Invoice
Management 7.5 Support Package folder on My Support (accessible via https://
knowledge.opentext.com/knowledge/cs.dll/Open/10151605) provides an
installation package of the VIM 7.5 SPx Approval Portal in the Web and
Mobile Approval Component folder.

12.3. System architecture
12.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 12-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)

12.3. System architecture
Figure 12-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
(https://help.sap.com/saphelp_nwce72/helpdata/en/17/
6d45fc91e84ef1bf0152f2b947dc35/frameset.htm).

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

Chapter 13
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 and 16.
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 or 16, download the software from the following
location: https://knowledge.opentext.com/knowledge/cs.dll/Open/13057772.
• 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, download the software from the following location:
• 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 the
following location: https://knowledge.opentext.com/knowledge/cs.dll/Open/
15739805
• 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).
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

Chapter 13 Installing Web Viewer/Brava! View for the Approval Portal
support, see the Web Viewer Support and Brava! View Support sections in the
Release Notes.

Chapter 14
Installing the Approval Portal
14.1 JCo3 migration considerations

VIM 16.3 Approval Portal supports the SAP Java Connector 3 (JCo3).
• 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 12.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 12.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 version package with Java 1.8: IM_APPROVAL_PORTAL16_3SP<XX>_JCo3_

JAVA1_8.zip
• JCo3 version package with Java 1.6: IM_APPROVAL_PORTAL16_3SP<XX>_JCo3.zip
where <XX> refers to the Support Package number.
14.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.

Chapter 14 Installing the Approval Portal
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 127 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 12.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

14.2. Preparing the installation
Lang_JA.properties
containing all the text for the Japanese language resource
Lang_NL.properties
containing all the text for the Dutch language resource
Lang_PT.properties
containing all the text for the Portuguese language resource
Lang_RU.properties
containing all the text for the Russian language resource
Lang_ZH.properties
containing all the text for the Chinese language resource
There might be more .properties files, depending on the package and the
release for additional languages. The language resource files can be changed.
See Section 12.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.
14.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 12 “Administering the Approval Portal” in
OpenText Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-
AGD) for additional information.

14.3. Configuring the administrator role
14.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 132.
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 134.
• Navigate to http://<NWAS>:<NWASPORT>/vimportal/admin.

If you see a screen similar to the one above, you have configured the
administrator role successfully.
14.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.

14.4 Deploying the Software Component Archive

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

NetWeaver 7.0” on page 134
• “Deploying the .sca file or .sda file” on page 135
• “Checking correct deployment” on page 136
• “Optional: Starting the Approval Portal J2EE application manually” on page 138
• “Optional: Clearing the browser cache” on page 138
14.4.1 Connecting to the SAP Software Deployment Manager

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

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

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

The script file is:
• RemoteGui.bat for Windows hosts
• RemoteGui.sh for Unix hosts

14.4. Deploying the Software Component Archive
14.4.2 Deploying the .sca file or .sda file

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

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

9. In step 4 of 4 of deployment, click Confirm to continue and finish deployment.
14.4.3 Checking correct deployment

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

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

to check if anything is wrong or redo the installation.
2. To check the J2EE application from NWAS, navigate to http://
<NWAS>:<NWASPORT>/vimportal.

You will see OpenText Approval error messages. This is correct as you have not
done any configuration yet.
3. Check the J2EE application:

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

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

this Installation Guide to check if anything is wrong or redo the
installation.

14.4.4 Optional: Starting the Approval Portal J2EE application

manually
By deploying through SDM, the Approval Portal J2EE application will start
automatically. If the Approval Portal J2EE application doesn't, you can start it
manually.
To start the Approval Portal J2EE application manually:
1. Click on a server.
2. Expand Services.
3. Expand Deploy.
See screenshot in Step 3 on page 137.
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.
14.4.5 Optional: Clearing the browser cache

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

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.

14.5. Deploying the Software Component Archive with SAP NetWeaver 7.3
4. Click the Clear browsing data button. Then wait for the browser to clear the
cache.
14.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.

14.5. Deploying the Software Component Archive with SAP NetWeaver 7.3
5. Click Start.

6. In the Completed screen, click Exit.
14.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>

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

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

the jump_config file.
b. Change the parameter value /sapstartsrv/httpsconnection from true
to false and save the changes.
6. Navigate to <drive>:\usr\sap\<SAP instance>\SUM\. Run the STARTUP.bat
file using Run as administrator and wait until SL Controller started is
displayed at the command prompt.
7. 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.

14.6. Deploying the Software Component Archive using SUM
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.

Chapter 15
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 155 and “Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5”
on page 169.
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 149
• “Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and 7.5”
on page 155
• “Creating roles for users” on page 165
• “Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5” on page 169
• “Assigning roles to SAP NetWeaver Portal users” on page 172
• “Configuring iViews and roles for the administrator” on page 173
• “Administering the OpenText Approval Portal” on page 174
15.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.

Chapter 15 Configuring SAP NetWeaver Portal components
3. Right-click on the new folder and select New > iView.

15.1. Creating AppIntegrator iViews for users
4. In the iView wizard, click Portal Component – create an iView from a portal
component ... and click Next.
5. In Step 1: Portal Archive Selection, click com.sap.portal.appintegrator.sap and

click Next.

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

15.1. Creating AppIntegrator iViews for users
• Description
Select the Master Language (mandatory).

Click Next.
8. In Step 4: Summary, click Finish to finish the initial iView creation.
9. Click Open the object for editing and click OK.

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:

15.2. Creating AppIntegrator iViews for users with SAP NetWeaver 7.3, 7.4, and 7.5
$host$
NWAS server name where the Approval Portal J2EE application was
deployed
$port$
Port of that NWAS
Note: Do not change <User.UserID>.
12. Click Save and Close.

The creation of the AppIntegrator iView is now finished.
15.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.

15.3. Creating roles for users
15.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 149.
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 152 in “Creating AppIntegrator iViews for

users” on page 149.
• 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.

15.3. Creating roles for users
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 149, 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.

15.4. Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5
15.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 155.
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.

15.4. Creating roles for users with SAP NetWeaver 7.3, 7.4, and 7.5
5. To edit the properties of the created role, click Properties.
6. Enter the Name (as shown in the screenshot) and select the Entry Point check
mark.
Click Save.

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

users with SAP NetWeaver 7.3, 7.4, and 7.5” on page 155, 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.
15.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 165).
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.

15.6. Configuring iViews and roles for the administrator
15.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 154 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 172.
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.
15.7 Administering the OpenText Approval Portal

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

Chapter 16
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 183, and then follow the steps to
deploy the .sca file or .sda file in “Deploying the .sca file or .sda file”
on page 135.
New <language>.properties files
Extract the new <language>.properties files from the media to
<Approval_Portal_installdir> and perform the Reinitialize Application task. See
Section 12 “Administering the Approval Portal” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for more details.

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

before upgrading.
Direct upgrades from previous versions to 7.5 are possible.
Approval Portal 5.2 to 7.5, Approval Portal 6.0 to 7.5, Approval Portal 7.0 (old UI)
to 7.5
Undeploy the old and deploy the new .SCA file, and freshly install the OpenText
installation directory.
Approval Portal 7.0 (new UI) to 7.5
Undeploy the old and deploy the new .SCA file. You can reuse the existing
OpenText installation directory.
Approval Portal 7.5 uses an additional xml file (RequestMappings.xml), which is

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

Chapter 18
Troubleshooting
For information on troubleshooting the Approval Portal, see Section 32.12

“Troubleshooting” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD).

Chapter 19
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 6.5.1 “User Details View”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Example: If the Windows Domain column in the COA table is not maintained for users,
leave the Domain field in the Configuration tab of the Approval Portal Administration
console empty as well.

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

• “Uninstalling with SAP NetWeaver 7.3, 7.4, and 7.5” on page 184
• “Removing SAP NetWeaver Portal components” on page 185
• “Deleting properties files” on page 186
• “Optional: Removing the startup parameter in the Config Tool” on page 186
20.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 184.
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.

Chapter 20 Uninstalling the Approval Portal
5. Click Start Undeployment.

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

opentext.com\IM_APPROVAL_PORTAL should no longer appear in the Visual
Administrator.
20.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.

20.3. Removing SAP NetWeaver Portal components
20.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 149.

Chapter 20 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.
20.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 125 for details on the
properties files.
20.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 127 in “Preparing the installation”
on page 125.
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:

20.5. Optional: Removing the startup parameter in the Config Tool
• configtool.bat for Windows hosts

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

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

Part 6
Mobile Approval Portal installation
Part 6 Mobile Approval Portal installation
This part describes the installation of the Mobile Approval Portal, which is an
enhancement to the Invoice Approval. Users can approve their invoices, using a
mobile device, for example a Blackberry, an iPhone, or an iPad. The Mobile
Approval Portal is based on HTML5.
Note: The Mobile Approval Portal is an optional component. If you are not
using the Mobile Approval Portal, you can skip this part.
For information on the configuration of the Mobile Approval Portal, see Section 13
“Configuring the Mobile Approval Portal” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD).

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

Chapter 21 Introduction to the Mobile Approval Portal
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.
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 21-1: HTML5 Mobile Approval Portal Architecture

Chapter 22
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 115

Chapter 23
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 or 16, 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 or 16, download the software from the following
location: https://knowledge.opentext.com/knowledge/cs.dll/Open/13057772.
To apply the latest patch for Web Viewer 10.5 or 16, download the software from the
following location: https://knowledge.opentext.com/knowledge/cs.dll/Open/
15739805
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

Chapter 23 Installing Web Viewer for the Mobile Approval Portal
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.

Chapter 24
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
24.1 Installing the Mobile Approval Portal on

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

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

7.0 SP8 or higher
All higher support packages and enhancement packages of NetWeaver 7.0, 7.3,
7.4, and 7.5.
Approval Portal
7.5

Chapter 24 Installing the Mobile Approval Portal
24.2.2 Scenario 1: Enabling Mobile Approval Portal for existing

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

SPNego login module.
Mobile Approval Portal uses SSO with the SPNego Login Module. Therefore, it
is only supported on SAP standalone NWAS 7.0/7.3/7.4. If you are already on
SAP NetWeaver Portal 7.0/7.3/7.4/7.5, and you want to have Mobile Approval
Portal support, install the standalone NWAS (AS JAVA) component also on SAP
NetWeaver Portal 7.0/7.3/7.4/7.5. This means, both AS JAVA and EP Core should
be available on the NetWeaver instance.
Refer to “Installing the Mobile Approval Portal on standalone NWAS
7.0/7.3/7.4” on page 199 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.
24.2.3 Scenario 2: Enabling Mobile Approval Portal for new

customers
1. For SAP NetWeaver Portal 7.0/7.3/7.4/7.5 customers, deploy/configure the
SPNego login module.
Refer to “Installing the Mobile Approval Portal on standalone NWAS
7.0/7.3/7.4” on page 199 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.

Part 7
Vendor Invoice Management SAP
NetWeaver Business Warehouse
component installation
Part 7 Vendor Invoice Management SAP NetWeaver Business Warehouse component installation
This part describes the installation of the Vendor Invoice Management SAP
NetWeaver Business Warehouse (VIM BW) component.

Chapter 25

Installation Tool (SAINT). The following table shows the passwords for the VIM BW
Add-on installation package, which is also used for VIM 16.3:
VIM BW Add-On SAP_BASIS Password

OTVIMBW 7.0 750 F17CB370FA

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


25.2.2 VIM BW add-on prerequisites

• Support Package Manager (transaction code SPAM) Version 7.50/0063

• See SAP note 2524249: SAP Invoice Management by OpenText 16.3
• The following components must be installed for SAP NetWeaver BW 7.5 on
HANA:
Table 25-1: 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 on HANA

(SAINT) for installation. SAINT uses single PAT files (extension *.PAT) which
integrate several transport files; these collections are also called packages.
On the product CD, the single PAT files are archived in SAPCAR files (extension
*.SAR) that can be extracted using the SAPCAR command line tool.

Chapter 26
Installing the OpenText package
This chapter describes the installation of the Basis package of VIM on an SAP
NetWeaver BW application server.
The basic components of VIM SAP NetWeaver BW are installed with the Basis
package.
To install the Basis package:
1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAP
application server in the \usr\sap\trans folder (this is the parent folder of the
DIR_EPS_ROOT folder).
SAP NetWeaver BW 7.5 on HANA
File
OTVIMBW_INST_VIM700_700.SAR
Source path
INST_BW_700/DATA/
Target path
\usr\sap\trans\EPS
2. Extract the SAPCAR file to the \usr\sap\trans\EPS\in folder with the

following command:
SAPCAR -xvf <name of SAPCAR file>
The resulting PAT file is extracted to the EPS\in folder relative to the path of the
SAPCAR file.
3. Call transaction SAINT (in client 000). You get an initial screen, which shows the
installed components.
Click Start to add the VIM 7.0 BW component.

Chapter 26 Installing the OpenText package
4. Click Start to see the screen that presents the packages ready to be installed.

5. Choose the package for component OTVIMBW. Carry out the import of the
package as described in the respective SAP documentation.

Chapter 27
Verifying the installation
Make sure that the VIM BW add-on is reflected in the installed components.
To verify the installation:
2. Click next to Component version.

Chapter 27 Verifying the installation
In the System: Component information dialog box, you should see the OTVIMBW
add-on component installed, with Release number 700.

Chapter 28
Installing VIM BW Add-on support package
There are two support packages delivered together with VIM BW Add-On 7.0:
• otvimbw_sp1.sar
• otvimbw_sp2.sar
Both support packages can be imported right after installing the main package of
VIM BW Add-On 7.0:
To import support packages:
1. Log in in client 0000 of the BW system as the DDIC user.
2. Run the /nSPAM transaction to import the support packages.

Chapter 29
Uninstalling the VIM BW add-on package
29.1 Prerequisites
The following components must be installed on the system with the following
minimal versions:
• AOFTOOLS 500_740 SP2

• SAINT/SPAM 7.5/070
29.2 Steps before uninstalling

1. Delete all entries in namespace /OPT/ in table BTCUEV.
2. Delete all entries in namespace /OPT/ in table BTCUED.
3. Run the SEPS transaction.
4. On the Electronic Parcel Service screen, on the menu, click Goto > Inbox.
5. On the Electronic Parcel Service: Inbox screen, check if there is any ACP file for
OTVIMBW===700.
6. If there is any such ACP file, select it, and then click the Delete button.
29.3 Uninstalling the VIM BW package

1. Download OTVIMBW700_ACP.SAR from My Support to your local computer.
2. In Client 000, run the SAINT transaction.

3. Go to Installation Package > Load Packages > From Front End, and then load
the SAR file OTVIMBW700_ACP.SAR.
4. On the Uninstallable components tab, select the OTVIMBW component, and then
click Start.

Part 8
Vendor Invoice Management BW/4HANA
add-on component installation
Part 8 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.

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

Chapter 30 About the VIM BW/4HANA add-on
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.

Chapter 31
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).

Chapter 32
Supported environments and compatibility
This section provides details about supported platforms, systems, and versions.
32.1 Supported systems

The system must be installed with SAP BW/4HANA 1.0 or later:
Table 32-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
32.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
32.3 Language support

The VIM BW/4HANA add-on is currently available in English.

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

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
33.2 Checking VIM BW/4HANA prerequisites

• Support Package Manager (transaction code SPAM) version 7.50/0066

• See SAP note 2524249: SAP Invoice Management by OpenText 16.3
• The following components must be installed for SAP NetWeaver BW/4HANA:
Table 33-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
• BW/4HANA BI content add-on BW4CONT 100 must be installed.

Chapter 33 Installing the VIM BW/4HANA add-on component
33.3 Installing the OpenText package

33.3.1 OLTP (source system)
Import the following TR on the source system using transaction code STMS:
D02K900158 – Convert VIM Datasource to ODP-enabled
Note: This TR will be included into the VIM package as soon as the
uninstallation of objects is supported by SAP tools.
33.3.2 OLAP (BW/4HANA) system

Refer to “Vendor Invoice Management SAP NetWeaver Business Warehouse
component installation” on page 201. 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: https://
knowledge.opentext.com/knowledge/llisapi.dll/properties/71426734
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:

33.3. Installing the OpenText package
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.

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

Part 9
Vendor Invoice Management component for
SAP NetWeaver Gateway installation
Part 9 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 8: Supplier Self Service architecture

Chapter 35

Installation Tool (SAINT).
SAP_BASIS Password
751 and later 8099C051AB

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


35.2.2 VIM Gateway prerequisites

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

components, see https://help.sap.com/doc/saphelp_grcac101/latest/en-US/76/
08828d832e4aa78748e9f82204a864/frameset.htm.
• 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 35-1: SAP components (OTVIMGW)
Option Component: SAP_GWFND

Release Support Package
1 751 -

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

Chapter 36
Installing the OpenText package
To install the OpenText VIM GW package:
1. Copy the respective SAPCAR file (OTVIMGW_INST_UPG_1610_104.SAR) from My

Support to a local folder.
The file is available here on My Support: https://knowledge.opentext.com/
2. Call the SAINT transaction (in client 000).

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

Chapter 37
Verifying the installation
Make sure that the VIM GW add-on is reflected in the installed components.
To verify the installation:
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_104.

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

Part 10
Vendor Invoice Management Supplier Self
Service - Lean Variant component
installation
Part 10 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.
Note: This component is not supported in the VIM 7.5 version for SAP S/
4HANA on Premise.

Chapter 39
39.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:
– 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 22.1.3 “Configuring Gateway users” in OpenText Vendor Invoice
39.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.
39.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 39-1: Supplier Self Service system architecture
If you plan to use the On-Premise deployment, skip “Installation on the SAP HANA
Cloud“ on page 243.

Chapter 40
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.
40.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.
40.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 40 Installation on the SAP HANA Cloud
3. In the Deploy Application dialog box, select the specific WAR file
vimsupplierselfservice.war to deploy. Initially the Cockpit proposes the
same name as for the WAR file. OpenText recommends that you enter the
application name vim3s but you can choose any other identifier you want.
Note: The application name must start with a letter, can contain lowercase
letters and numbers only, and must not exceed 30 characters. You can also
assign a display name and a description to the Java application.
4. Optional Specify additional parameters to configure the application. If omitted,

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

40.3. Installing the SAP HANA Cloud connector
5. Click Deploy to deploy the WAR file to the cloud platform. The Deploy
Application dialog box remains on the screen while the deployment is in
progress. When the deployment is finished, a confirmation appears that the
application has been successfully deployed.
Note: At this stage, the application is not yet up and running.
Next steps To make your deployed application available for requests, you must start it inside
the SAP HANA Cloud Cockpit. For more information, see Section 22.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.
40.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.

Part 11
Vendor Invoice Management electronic
invoices component installation
Part 11 Vendor Invoice Management electronic invoices component installation
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 (VIM-CCS).

Chapter 41
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 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 or VIM 16.3.3 and optionally installing the SAP Document Compliance
integration component (OTBCSL38) as described in “Installation” on page 252.
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.
Note: After the import of the transports, you must perform manual
modification steps on VIM 7.5 SP7, VIM 16.3 and VIM 16.3.1, as described at
the end of this section.
The transport delivery files are located in the following folder on OpenText My
Support:
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=76775470
The same location can be reached by navigating to Resources > Patches > Vendor
Invoice Management > Vendor Invoice Management - E-invoicing.
The downloads are organized according to the scenario (Business Center Inbound):
VIM 16.3 with Business Center Inbound

File name: vim-16.3-e-invoicing-bc.zip

Chapter 41 General package for electronic invoices
Transports:
• D02K902488 – Workbench objects

• D02K902493 – Customizing objects
VIM 16.3 with Business Center Inbound for generic UBL

File name: vim-16.3-e-invoicing-bc-patch01.zip
Transports:
• D02K903002 - Workbench objects

• D02K903436 - Customizing objects
VIM 16.3 with Business Center Inbound for UN-CEFACT

File name: vim-16.3-e-invoicing-bc-patch02.zip
Transports:
• D02K904109 - Workbench objects

• D02K904108 - Customizing objects
VIM 7.5 SP7, VIM 16.3 and VIM 16.3 SP1: manual modifications after the import
Several function modules in the delivery contain calls to security check modules
that are delivered with later VIM support packages than previously mentioned.
To ensure package integrity, the unified deliveries are produced for all
supported support packages. This requires some simple manual modifications
for older support package levels:
Perform the following modification in the function modules listed in the
following (transaction SE37):
• /OPT/VIM_DATE_CONVERSION
• /OPT/VIM_GET_EDOC_DATA
• /OPT/VIM_EXIT_MAP_ENH_FATRURA
• /OPT/VIM_EXIT_MAP_ENH_RECHNUNG
• /OPT/VIM_EXIT_MAP_ENH_UBL
Delete or comment out the following three lines at the beginning of the function
module:
IF /opt/vim_auth_check=>check_rfc( ) <> 0.
EXIT.
ENDIF.

Chapter 42
Business Center Inbound: 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.
42.1 Prerequisites
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 Business Center Inbound, which is provided as

the component OTBCSL03 with VIM 7.5 and included directly into VIM 16.3. In both
cases, you need to install Business Center core components. For more information,
see VIM and Business Center 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

Chapter 42 Business Center Inbound: integration with SAP Document Compliance
Note Scenario
2805582 - eDocument Germany - EU eInvoicing: Corrections Germany
2618098 - eDocument EU: Prerequisite for SAP Note 2523477 General/PEPPOL
2523477 - eDocument EU: eInvoice General/PEPPOL
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”.
42.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.
PAT file name: Q020020776277_0000140.PAT
Password: 8C87CF35A7
Activate the BC set /OTBCSL38/EDOCU_INTEGRATION_SAP.
To enable ACCEPT/REJECT feedback messages, some changes are required in VIM

core modules. The changes are included in VIM 7.5 SP10 and later and VIM 16.3.4
and later. If you run an older support package, the changes are delivered as manual
correction instructions:

42.2. Installation
https://mimage.opentext.com/support/ecm/secure/patches/vim/oneoff/VIMI-22539/
vim_7.5_sp10_vimi-22539_ci-25.pdf
A mandatory update for customers not using VIM 7.5 SP10 and VIM 16.3.4, for the
component OTBCSL38 is available for download as patch01. The patch is located in
the following folder on OpenText My Support: https://knowledge.opentext.com/
knowledge/llisapi.dll?func=ll&objId=76775470. You can reach the same location by
navigating to Resources > Patches > Vendor Invoice Management > Vendor
Invoice Management - E-invoicing.
File name: OTBCSL38-patch01.zip

Transports:
D02K902488 - Workbench objects
D02K902493 - Customizing objects

Part 12
Vendor Invoice Management ARIBA
Integration component installation
Part 12 Vendor Invoice Management ARIBA Integration component installation
VIM can be integrated with Ariba® Network. For detailed information about the
integration, see Section 24 “Integration with the Ariba Network” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (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 recommended 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“ on page 257. This consists of activating the BC sets and
activating the BAdI implementations.
If you decide to use PI-based integration, you must import additional transports. For
more information, see “Importing ABAP workbench objects“ on page 259.

Chapter 43
43.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/VIM16_3_BASELINE_ARIBA.
Note: Consider the most recent Release Notes for latest information on new BC
sets and additional post installation activities.
43.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).

Chapter 44
Importing ABAP workbench objects
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.
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 24.2 “Integrating the Ariba SAP
NetWeaver Process Integration adapter” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide (VIM-CGD). The adapter version CI-8 and later is
supported.
Because of dependencies on the Ariba CI-8 adapter, OpenText delivers the necessary
ABAP workbench objects as a separate set of transport files. You find the transport
files on My Support.
The delivery of the transport files is provided with VIM 7.5 SP5. This scenario is
supported by VIM 7.0 SP3 and VIM 7.5 SP1 and later VIM versions. You can use the
provided transport files with the mentioned older VIM versions and SPs.
To import the transport files:
1. On My Support, access VIM 7.5 SP5 and Ariba Cloud Integration with PI
(https://knowledge.opentext.com/knowledge/cs.dll/Open/64801445).
2. Download the transport files.
3. Perform the import in the following sequence:
1. EW3K901050
2. EW3K901080
3. EW3K901083
4. After the import, perform additional configuration steps as described in Section

24.2 “Integrating the Ariba SAP NetWeaver Process Integration adapter” in
(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.

Part 13
Vendor Invoice Management integration
with Ariba, CIG scenario objects
installation
Part 13 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).

Chapter 45
Importing ABAP workbench objects and
customizing
VIM supports Ariba Network integration already for some time. The integration
options available and supported by VIM until now were the following:
• SAP Business Suite Adapter for Ariba

• Ariba Cloud Integration (CI) adapter or its predecessor, Ariba Network Adapter,
with NetWeaver PI
Ariba Cloud Integration Gateway (CIG) is a new integration option supported by

VIM now.
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.
Because of dependencies on the SAP ARBCI1 and ARBCI2 components, OpenText

delivers the necessary objects as a separate set of transport files. You find the
transport files on My Support.
To import the transport files:
1. On My Support, access Vendor Invoice Management - Ariba Network CIG

Integration: https://knowledge.opentext.com/knowledge/llisapi.dll/open/
75256022
2. Download the transport files provided through the link VIM Ariba CIG
Transport Files (file VIM-Ariba-CIG-v2.1.zip)
3. Perform the import.
Importing notes
1. If you have installed transports provided before March 2020, and want to
install the latest version of the solution, import only the workbench
transport. You do not need to reimport the customizing transport unless
you must reset the configuration.
2. When importing the customizing transport on systems with Business Center
16.3.1 or earlier, two import errors are displayed because of truncated
values of key fields for freight and handling costs mapping. As explained
earlier in this section, this mapping is not supported on older VIM /
Business Center support packages. Ignore these errors.
3. The customizing transport creates or updates an entry in the Business
Center Inbound Registration Idoc node with the following parameters:
• Partner number = <space>

Chapter 45 Importing ABAP workbench objects and customizing
• Partner type = LS
• Partner role = LS
• Message type = INVOIC
• Test = X
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.
Transport list
TWRK900759
Workbench objects for outbound invoice status update
TWRK900607
Customizing, CIG IDOC mapping for incoming invoice request. Read the
following Note before importing.
Note: If you have downloaded the transport provided in an earlier
downloads set, do not import TWRK900776 despite its higher transport
number.
4. After the import, perform additional configuration steps as described in Section

24.3 “Integrating Ariba Network using Cloud Integration Gateway” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).

Part 14
Removing OpenText add-ons
Part 14 Removing OpenText add-ons
OpenText 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 OpenText 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.

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

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

Chapter 47 Steps before deinstallation
47.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.
47.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.
47.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.

47.6. (VIM) Maintaining Business Transaction Events
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.
47.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 the following entries:
• 00001020 > /OPT/ > /OPT/VIM > 0

• 00001030 > /OPT/ > /OPT/VIM > 0
• 00001050 > /OPT/ > /OPT/VIM > 0
• 00001140 > /OPT/ > /OPT/VIM > 0
• 00002213 > /OPT/ > /OPT/VIM > 0
• 00002218 > /OPT/ > /OPT/VIM > 0
6. Run the BF42 transaction and remove the following entries:
• Process 00005010, /OPT/BTE_IF_00005010

Chapter 47 Steps before deinstallation
• Process RWBAPI01, /OPT/BTE_RWBAPI01_BAPIEXTN
47.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
47.8 (VIM) Removing event type linkages (SWETYPV)

To remove event type linkages:
• Run the SWETYPV transaction and remove the following linkages (if present):
Table 47-1: Event type linkages to be removed
Object Type Event Receiver Type/

Receiver Function Module (FM)
/OPT/B2081 ZWFI_PARKED VIM_PARKED_DP
/OPT/FIPP ZWFI_CREATED WS00275254
/ORS/INVAP POSTED
BUS2081 CANCELLED
BUS2081 DELETED
BUS2081 DELETED TS00275270
BUS2081 POSTED FM /OPT/VIM_RPT_PO_INV_RECEIVER
BUS2081 POSTED TS00275264
BUS2081 RELEASED FM /OPT/VIM_RPT_PO_INV_RECEIVER
FIPP DELETED
FIPP DELETED TS00275270
FIPP POSTED
FIPP POSTED TS00275270

47.9. (VIM) Cleaning up the MIRO enhancement
47.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 11.11.3 “Enhancing MIRO for pre-
population of data during online invoice creation” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD). In this case, you
must delete those implicit enhancements prior to removing OpenText add-ons.
47.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“ on page 259. 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
47.11 Deleting all external usages

All custom coding referring to objects in the OpenText package has to be removed
before deinstallation.
47.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.

Chapter 48
Steps after deinstallation
48.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.

Chapter 49
Troubleshooting
49.1 Error in phase CHECK_LOCKED_OBJ

Symptom After post-installation step “Maintaining the SAPscript form for approval”
on page 47 is done, the following error occurs:
Solution Release the mentioned transport and click Repeat to repeat the deinstallation step.
49.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 269.
49.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/%'.

49.4. Error in phase CHECK_USAGE
49.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 269.
Note: Do not delete these objects manually from package $SWF_RUN_CNT.
49.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.

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 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.
Automation Report
Tool that provides data about automated and manual processing steps of VIM
documents

Glossary
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
OpenText Business Center for SAP Solutions. OpenText product that helps
receiving incoming documents, capturing processes, and filing them within a SAP
system. VIM is tightly integrated with Business Center.
Business rules
Rules that describe the operations, definitions and constraints that apply to an
organization

Glossary
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.
Data Transfer Process (DTP)

Object in SAP NetWeaver BW to transfer data from source objects to target objects
DataSource
Set of fields in SAP NetWeaver BW that provide the data for a business unit for
data transfer to the SAP NetWeaver BW system; technically, it contains an extract
structure and an extraction function module.
DataStore Object (DSO)

Storage location for consolidated and cleansed data in SAP NetWeaver BW
DocuLink
OpenText™ DocuLink for SAP Solutions enables the archiving, management and
retrieval of SAP CRM or SAP S/4HANA documents from within the SAP
infrastructure.

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

Glossary
Financial Accounting (FI)

SAP module for the Finance and Accounting department
IAP
See: Invoice Approval (IAP)
IDoc
See: Intermediate Document (IDoc)
IE
See: Invoice Exception (IE)
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.

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

Glossary
MM
See: Materials Management (MM)
Mobile Approval Portal

VIM component for approving invoices on mobile devices.
MultiProvider
Object in SAP NetWeaver BW that is based on InfoCube(s), DataStore Object(s),
and/or InfoObject(s). A MultiProvider is used as a layer for the creation of end user
queries; the MultiProvider itself does not contain any data; rather, data resides in
the BasisCubes.
Namespace
Name range reserved by SAP for customer objects and SAP objects to make sure
that objects are not overwritten by SAP objects during the import of corrections or
an upgrade
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.

Glossary
PIR
See: Non purchase order (Non PO) invoice (PIR)
PO
See: Purchase order (PO)
Posted invoice document

Invoice that has already been posted in SAP 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 options
Processing options for the user in the dashboard, such as Referral, Authorization,
and Actions
Process type
Process type for a document. The process type determines the initial actor and
various collaboration options available to the various actors during the process
flow.
Productivity Report
Part of the Central Reporting infrastructure. The Productivity Report reports
about the productivity of users/roles and the activities of users/roles.
PSA
See: Persistent Staging Area (PSA)
Purchase order (PO) invoice

Invoice based on a Purchase order (PO)
Purchase order (PO)

SAP module. PO indicates a document sent from a buyer to a seller. The purpose
of the document is to order the delivery of goods or services.

Glossary
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 Shared Service Framework

SAP software that contains a rich set of tools to improve and automate Shared
Service Center operations.
SAP Supplier Relationship Management (SAP SRM)

SAP application that automates, simplifies, and accelerates procure-to-pay
processes for goods and services.
Scan operator
Person who scans the invoices into images (may not have a SAP ID)
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.
Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP S/4HANA system.

Opentext™ Vendor Invoice Management For Sap Solutions: Installation Guide

Uploaded by

Copyright:

Available Formats

You might also like

Opentext™ Vendor Invoice Management For Sap Solutions: Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Opentext™ Vendor Invoice Management For Sap Solutions: Installation Guide

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

for SAP® Solutions

This guide describes the installation of all Vendor Invoice

These are Vendor Invoice Management SAP component - classic

Open Text Corporation

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

Copyright © 2020 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

1 About this document ............................................................... 17

Part 2 VIM classic mode installation 19

2 Preparing installation .............................................................. 21

3 Installing VIM ........................................................................... 25

4 Installing Single Click Entry for SAP GUI .............................. 59

5 Installing a VIM Support Package .......................................... 61

Part 3 Simple Mode VIM installation 87

VIM160305-IGD-EN-03 Installation Guide iii

9 Simple Mode installation ........................................................ 91

Part 4 KPI Dashboard installation 99

10 Installing the KPI Dashboard ................................................ 101

11 Post installation activities .................................................... 103

Part 5 OpenText Approval Portal installation 113

12 Preparing installation ............................................................ 115

13 Installing Web Viewer/Brava! View for the Approval

14 Installing the Approval Portal ............................................... 125

15 Configuring SAP NetWeaver Portal components ............... 149

16 Applying a new patch ............................................................ 175

iv OpenText™ Vendor Invoice Management for SAP® Solutions VIM160305-IGD-EN-03

17 Upgrading the Approval Portal from previous versions .... 177

18 Troubleshooting .................................................................... 179

19 Supporting installation of the standalone NWAS Portal

20 Uninstalling the Approval Portal .......................................... 183

Part 6 Mobile Approval Portal installation 189

21 Introduction to the Mobile Approval Portal ......................... 191

22 Authentication for the Mobile Approval Portal ................... 195

24 Installing the Mobile Approval Portal .................................. 199

Part 7 Vendor Invoice Management SAP NetWeaver Business

25 Preparing installation ............................................................ 203

26 Installing the OpenText package ......................................... 205

27 Verifying the installation ....................................................... 209

28 Installing VIM BW Add-on support package ....................... 211

29 Uninstalling the VIM BW add-on package ........................... 213

VIM160305-IGD-EN-03 Installation Guide v

Part 8 Vendor Invoice Management BW/4HANA add-on

30 About the VIM BW/4HANA add-on ....................................... 217

31 Packaging and delivery information .................................... 219

32 Supported environments and compatibility ....................... 221

33 Installing the VIM BW/4HANA add-on component ............. 223

34 Upgrade notes ....................................................................... 227

Part 9 Vendor Invoice Management component for SAP

35 Preparing installation ............................................................ 231

36 Installing the OpenText package ......................................... 233

37 Verifying the installation ....................................................... 235

38 Post installation activities .................................................... 237

Part 10 Vendor Invoice Management Supplier Self Service - Lean

39 Preparing installation ............................................................ 241

40 Installation on the SAP HANA Cloud ................................... 243

vi OpenText™ Vendor Invoice Management for SAP® Solutions VIM160305-IGD-EN-03

Part 11 Vendor Invoice Management electronic invoices