VIM 6 0 Instalation Guide PDF

OpenText Vendor Invoice Management
Installation Guide
This guide describes the installation of all Vendor Invoice

Management (VIM) 6.0 components: Vendor Invoice
Management SAP component, optional OpenText Approval
Portal, and optional Vendor Invoice Management CRM SSF
component.
VIM060000-IGD-EN-3
OpenText Vendor Invoice Management
Installation Guide
VIM060000-IGD-EN-3
Rev.: 18. July 2011
This documentation has been created for software version 6.0.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Email: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com
Copyright © by Open Text Corporation, Open Text Inc.

Open Text Corporation is the owner of the trademarks Open Text, OpenText, The Content Experts, OpenText ECM Suite,
OpenText eDOCS, eDOCS, OpenText FirstClass, FirstClass, OpenText Exceed, OpenText HostExplorer, OpenText Exceed
OnDemand, OpenText Exceed 3D, OpenText Exceed Freedom, OpenText Exceed PowerSuite, OpenText Exceed XDK,
OpenText NFS Solo, OpenText NFS Client, OpenText NFS Server, OpenText NFS Gateway, OpenText Everywhere, OpenText
Real Time, OpenText Eloquent Media Server, OpenText Integrated Document Management, OpenText IDM, OpenText
DocuLink, Livelink, Livelink ECM, Artesia, RedDot, RightFax, RKYV, DOMEA, Alchemy, Vignette, Vizible, Nstein,
LegalKEY, Picdar, Hummingbird, IXOS, Alis Gist-in-Time, Eurocortex, Gauss, Captaris, Spicer, Genio, Vista Plus, Burntsand,
New Generation Consulting, Momentum Systems, DOKuStar, and RecoStar among others. This list is not exhaustive.
All other products or company names are used for identification purposes only, and are trademarks of their respective own-
ers. All rights reserved.
Table of Contents
1 Introduction ............................................................................... 7
1.1 About the Product .................................................................................... 7
1.2 About the Document ................................................................................ 7
1.2.1 Target Audience....................................................................................... 7
1.2.2 Document Overview................................................................................. 8
1.2.3 Conventions ............................................................................................. 8
1.3 Contact Information.................................................................................. 9
Part 1 Vendor Invoice Management SAP Component Installation 11
2 Preparing Installation.............................................................. 13
2.1 General .................................................................................................. 13
2.2 Password Control................................................................................... 14
2.3 Checking Prerequisites .......................................................................... 14
2.3.1 Required Knowledge.............................................................................. 14
2.3.2 SAP Prerequisites .................................................................................. 14
2.3.3 Workflow Customizing............................................................................ 16
2.3.4 Installation Tool ...................................................................................... 18
3 Installing the OpenText Package............................................ 19

3.1 Installing the Package ............................................................................ 19
3.2 Post Installation Activities ...................................................................... 19
3.2.1 Activating Business Configuration Sets ................................................. 20
3.2.2 Configuring Workflow Dialog Tasks ....................................................... 24
3.2.3 Refreshing SAP Workflow Runtime Buffer ............................................ 26
3.2.4 Configuring Object Services .................................................................. 27
3.2.5 Maintaining Number Ranges ................................................................. 30
3.2.6 Generating and Activating SAP Parking APIs ....................................... 33
3.2.7 Generating Business Object .................................................................. 38
3.2.8 Linking Events for VIM Workflows ......................................................... 38
3.2.9 Setting the Extraction and Validation Retry Count................................. 41
3.2.10 Maintaining Business Transaction Events (BTEs)................................. 43
3.2.11 Maintaining Standard Text ..................................................................... 45
4 Verifying Installation ............................................................... 49

5 Upgrading ................................................................................ 51
5.1 Upgrading SAP ...................................................................................... 51
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management iii

Table of Contents
5.2 Upgrading VIM ....................................................................................... 55
6 Troubleshooting ......................................................................63
6.1 FAQs ...................................................................................................... 63
Part 2 OpenText Approval Portal Installation 65
7 Preparing Installation ..............................................................67

7.1 Installation Prerequisites ........................................................................ 67
7.2 Installation Components ........................................................................ 69
7.3 System Architecture ............................................................................... 70
7.3.1 SAP User Requirements........................................................................ 72
8 Installing the Approval Portal .................................................75

8.1 Preparing the Installation ....................................................................... 75
8.2 Configuring the Administrator Role ........................................................ 77
8.2.1 Configuring the Administrator Role for Access Through WAS .............. 78
8.3 Deploying the Software Component Archive ......................................... 81
8.3.1 Connecting to the SAP Software Deployment Manager (SDM) ............ 81
8.3.2 Deploying the .sca File or .sda File........................................................ 82
8.3.3 Checking Correct Deployment ............................................................... 83
8.3.4 Optional: Starting the Approval Portal J2EE Application Manually........ 85
9 Configuring SAP NetWeaver Portal Components .................87

9.1 Creating AppIntegrator IViews for Users ............................................... 87
9.2 Creating Roles for Users........................................................................ 93
9.3 Assigning Roles to SAP NetWeaver Portal Users ................................. 96
9.4 Configuring IViews and Roles for the Administrator .............................. 97
10 Applying a New Patch .............................................................99

11 Upgrading the Approval Portal from Previous Versions.....101
12 Troubleshooting ....................................................................103
13 Uninstalling the Approval Portal...........................................105
13.1 Uninstalling Using Software Deployment Manager ............................. 105
13.2 Removing SAP NetWeaver Portal Components.................................. 106
13.3 Deleting Properties Files ...................................................................... 106
13.4 Optional: Removing the Startup Parameter in the Config Tool ........... 107
Part 3 Vendor Invoice Management CRM Shared Service

Framework (SSF) Component Installation 110
14 Preparing Installation ............................................................113

14.1 Password Control................................................................................. 113
iv OpenText Vendor Invoice Management VIM060000-IGD-EN-3

Table of Contents
14.2 Checking Prerequisites ........................................................................ 113

14.2.1 Required Knowledge............................................................................ 113
14.2.2 SAP CRM EHP1 Prerequisites ............................................................ 113
14.2.3 Installation Tool .................................................................................... 114
15 Installing the OpenText Package.......................................... 115

16 Post Installation Activities .................................................... 117
16.1 Activating Business Configuration Sets in the CRM System ............... 117
16.2 Maintaining a Logical System for the CRM System in VIM ................. 120
17 Verifying Installation ............................................................. 123
Part 4 Mobile App Installation 125
18 Authentication for Mobile Approval ..................................... 127

19 Installing the Mobile App ...................................................... 131
20 Post Installation Activities .................................................... 133
20.1 Activating the Web Service .................................................................. 133
20.2 Configuring Profile Parameters............................................................ 134
20.3 Optional: Setting Up SSL Communication for the Web Application
Server................................................................................................... 136
20.4 Activating SAP Systems ...................................................................... 136
GLS Glossary 137
IDX Index 145
VIM060000-IGD-EN-3 Installation Guide v

Chapter 1
Introduction
1.1 About the Product

Vendor Invoice Management (VIM) is a packaged business solution that basically
solves a business problem – paying correct amount to vendors on-time. VIM is an
add-on to your SAP system, the majority of its functions and processes run inside
the SAP system; it deals only with invoices that will be posted to SAP ERP. It
integrates with standard SAP functions such as Invoice Verification, Financial
Processing, etc.
Patches Patches (Hot Fixes), Support Packages and the latest versions of the Release Notes
for VIM are available in the OpenText Knowledge Center:
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605. The
latest versions of the documentation are also available in the Knowledge Center:
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151494.
For SAP Invoice Management by OpenText customers: To obtain access to the
Knowledge Center, initiate a ticket request in SAP Service Marketplace.
For OpenText customers: Send an email to support@opentext.com.
1.2 About the Document

1.2.1 Target Audience
This document addresses those who participate in the administration and
maintenance of Vendor Invoice Management (VIM). This includes
• SAP Basis Administrators
• SAP Workflow Administrators
• SAP Configuration and Development Support
VIM features the optional component Web Invoice Approval. The target audience for
this component includes:
• Site administrators
• Database administrators
• Network administrators
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 7

Chapter 1 Introduction
1.2.2 Document Overview

This Installation Guide includes the complete installation information for all Vendor
Invoice Management components:
• “Vendor Invoice Management SAP Component Installation” on page 11
• “OpenText Approval Portal Installation” on page 65
• “Vendor Invoice Management CRM Shared Service Framework (SSF)
Component Installation” on page 110
• “Mobile App Installation” on page 125
1.2.3 Conventions
User interface
This format is used for elements in the graphical user interface (GUI), such as
buttons, names of icons, menu items, and fields.
Filenames, commands, and sample data
This format is used for file names, paths, URLs, and commands at the command
prompt. It is also used for example data, text to be entered in text boxes, and
other literals.
Note: If you copy command line examples from a PDF, be aware that PDFs
can contain hidden characters. OpenText recommends copying from the
HTML version of the document, if it is available.
KEY NAMES
Key names appear in ALL CAPS, for example:
Press CTRL+V.
<Variable name>
Angled brackets < > are used to denote a variable or placeholder. The user
replaces the brackets and the descriptive content with the appropriate value. For
example, <server_name> becomes serv01.
Internal cross-references
Click the cross-reference to go directly to the reference target in the current
document.
External cross-references
External cross-references are usually text references to other documents.
However, if a document is available in HTML format, for example, in the
Knowledge Center, external references may be active links to a specific section in
the referenced document.
8 OpenText Vendor Invoice Management VIM060000-IGD-EN-3

1.3 Contact Information
Warnings, notes, and tips
Caution
Cautions help you avoid irreversible problems. Read this information
carefully and follow all instructions.
Important
Important notes help you avoid major problems.
Note: Notes provide additional information about a task.

Tip: Tips offer you quicker or easier ways of performing a task.
1.3 Contact Information

OpenText Online (http://online.opentext.com/) is a single point of access for the
product information provided by OpenText. You can access the following support
sources through OpenText Online:
• Communities
• Knowledge Center
OpenText Online Communities
(http://communities.opentext.com/communities/livelink.exe/open/OpenTextOnli
neCommunity) provide the following resources:
• Usage tips, help files, and best practices for customers and partners.
• Information on product releases.
• User groups and forums where you can ask questions of OpenText experts.
The OpenText Knowledge Center (https://knowledge.opentext.com) is OpenText's
corporate extranet and primary site for technical support. The Knowledge Center is
the official source for the following:
• Product downloads, patches, and documentation including Release Notes.
• Discussion forums, Online Communities, and the Knowledge Base.
• OpenText Developer Network (OTDN), which includes developer
documentation and programming samples for OpenText products.
If you need additional assistance, you can find OpenText Corporate Support
Contacts at http://support.opentext.com/.
VIM060000-IGD-EN-3 Installation Guide 9

Part 1
Vendor Invoice Management SAP Component
Installation
Part 1 Vendor Invoice Management SAP Component Installation
This part describes the installation of the SAP component 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 re-
sponsibility excluding any liability of OpenText. If you have any
questions, contact OpenText Global Services.
Supported versions Only the products and versions specified in the Release Notes
are supported. Other versions have not been tested and are
therefore not officially supported for this version. The Release
Notes contain the definitive list of supported versions. Any other
versions mentioned in this guide are superseded by the versions
specified in the Release Notes.
OpenText Support If you require additional help with technical problems, contact
Center OpenText Customer Support. You can find the contact informa-
tion for your region at
http://www.opentext.com/services/support.html.
Important
Make sure the SAP workflow system is configured to run workflows. To
check this, execute 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
at the OpenText Knowledge Center:
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 following table shows the passwords for VIM installation, SAP upgrade and
VIM upgrade.
VIM Package SAP ECC 6.0 SAP ECC 5.0 SAP 4.7 SAP 4.6C
VIM installation 217746711F 217741711F 217740711F 217743711F
SAP upgrade 2177467708 2177417708 2177407708 -

VIM upgrade 2177467118 2177417118 2177407118 2177437118
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 Prerequisites

Check the following prerequisites prior to installation:
SAP ECC 6.0

• Support Package Manager (transaction code SPAM) level 35
• Apply OSS note 1082597: Not enough business functions activated in SFW5; this
is used for Switch Frame Work for activating the PO based invoice parking
infrastructure.
• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s AS
ABAP
• Apply OSS note 938147: OAWD: Object does not exist (OA 233)
You have to apply this note manually even if the system shows a message “The
note cannot be implemented” in transaction SNOTE.
• Apply OSS note 1568202: OpenText Vendor Invoice Management Solutions
• Apply OSS note 1390369: ALV graphic: Double number of bars

The following components must be installed for SAP ECC 6.0 up to EHP5:
Option Component: SAP_APPL Component: SAP_BASIS

Release Support package Release Support package
1 600 SAPKH60006 700 SAPKB70010
2 602 SAPKH60205 700 SAPKB70010
3 604 SAPKH60402 700 or SAPKB70103
above
4 605 - 700 or SAPKB70203
above
SAP ECC 5.0

• The following components must be installed for SAP ECC 5.0:
Component SAP_APPL
Level: 500
Component SAP_BASIS
Level: 640
• The following support packages must be installed:
SAPKB64022, SAPKH50019
SAP R/3 4.7

Support Package Manager (transaction code SPAM) level 41
Component SAP_APPL
Level: 470
Component SAP_BASIS
Level: 620
The following support packages must be installed:
SAPKB62064, SAPKH47030

SAP R/3 4.6 C

• Apply OSS note 636217: DDIC activation error as table width greater than 1962
bytes
The following components and support packages are prerequisites.
The following components must be installed for SAP R/3 4.6 C:
Component SAP_APPL
Level: 46C
Component SAP_BASIS
Level: 46C
SAPKB46C53, SAPKH46C53
2.3.3 Workflow Customizing

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

• Execute the SWU3 transaction.
Make sure most of the relevant items are configured correctly, indicated by the
icon.

SAP 4.7 or above
In the Maintain Runtime Environment node, the Configure RFC

Destination entry must have the icon.
SAP 4.6C

The Workflow RFC destination configured completely entry must have

the icon.
2.3.4 Installation Tool

OpenText Vendor Invoice Management uses the SAP Add-On Installation Tool
(SAINT) for installation. SAINT uses single PAT files (extension *.PAT) which
integrate several transport files; these collections are also called packages.
On the product CD, the single PAT files are archived in SAPCAR files (extension
*.SAR) that can be extracted using the SAPCAR command line tool. The different
SAPCAR files are located in a DATA folder below the respective package folder named
as the package and SAP release.
Note: The handling of the installation procedure within SAINT differs depend-
ing on the SAP system.

Chapter 3
Installing the OpenText Package
This chapter describes the installation of the Basis package of Vendor Invoice
Management (VIM) on an SAP application server. Read also “Preparing
Installation” on page 13 with general information on installation in an SAP
environment.
3.1 Installing the Package

The basic components are installed with the Basis package.
To install the Basis package:

1. 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 ver- File Source path Target path
sion
SAP ECC 6.0 OTEXVIM_604_700.SAR INST_ERP_700/DATA /usr/sap/trans/
/ EPS
SAP ECC 5.0 OTEXVIM_603_640.SAR INST_ERP_640/DATA /usr/sap/trans/

/ EPS
SAP R/3 4.7 OTEXVIM_602_620.SAR INST_ERP_620/DATA /usr/sap/trans/

/ EPS
SAP R/3 OTEXVIM_601_46C.SAR INST_ERP_46C/DATA /usr/sap/trans/

4.6C / EPS
2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

following command: SAPCAR -xvf <name of SAPCAR file>.
The resulting PAT file will be extracted to the EPS/in folder relative to the path
of the SAPCAR file.
3. Carry out the import of the package as described in the respective SAP
documentation.
3.2 Post Installation Activities

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

Chapter 3 Installing the OpenText Package
• “Configuring Workflow Dialog Tasks” on page 24

• “Refreshing SAP Workflow Runtime Buffer” on page 26
• “Configuring Object Services” on page 27
• “Maintaining Number Ranges” on page 30
• “Generating and Activating SAP Parking APIs” on page 33
• “Generating Business Object” on page 38
• “Linking Events for VIM Workflows” on page 38
• “Setting the Extraction and Validation Retry Count” on page 41
• “Maintaining Business Transaction Events (BTEs)” on page 43
• “Maintaining Standard Text” on page 45
3.2.1 Activating Business Configuration Sets
Important
This section is only relevant for VIM installation. For an SAP and VIM
upgrade, do not perform the actions described in this section. In case of a
VIM upgrade, previous VIM configuration data will be overwritten after
activating Business Configuration Sets (BC Sets). Any custom changes
performed in a previous version of VIM need to be redone after the BC Sets
activation.
Notes:
• For every client, you must activate new BC Sets after installing VIM 6.0.
• You need the appropriate security authorization to execute some of the
transactions.
• Depending on the SAP version, the following screens might look different
on your system.
You activate the BC Sets in the following steps:
1. Apply recommended user settings
2. Activate BC Set /OTEXVIM/VIM60_CORE_CUSTOMIZING
Note: Check the tables in /OTEXVIM/VIM60_CORE_CUSTOMIZING and decide
if it is appropriate to activate this BC Set.
Activate BC set in the Configuration client of the Development system and
create a transport from BC set activation, move the transport to required
systems.

Don’t activate BC set in the production system. Create a customization transport

in Development System configuration client by activating BC set and move it to
desired systems.
To apply recommended user settings:

1. To access the Business Configuration Sets: Activation screen, execute the
SCPR20 transaction.
From the Utilities menu, click User Settings.
VIM 6.0 supports the following languages:

• Dutch
• English
• French
• German
• Italian

• Japanese
• Portuguese
• Spanish
• Russian
• Chinese
To select your applicable languages, select the respective check box in the
Manual Selection column.
2. Click the Maint. Transaction tab.
Apply the settings, as shown in the screenshot.

3. To copy the settings, click .
You are now ready to activate the BC set.
To activate BC Sets:
SCPR20 transaction.

2. Enter the BC set name /OTEXVIM/VIM60_CORE_CUSTOMIZING and click the

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

4. Click the Activate button.
Tip: You can skip any warnings during the activation.
After successful BC Set activation, a message is displayed in the lower left of the
SAP GUI: Activation ended with warning.

3.2.2 Configuring Workflow Dialog Tasks

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

1 DP WF 00275278
2 PO Parked 00275262
3 PO Blocked Line level 00275265
4 PO Blocked Header 00275267
5 NPO parked 00275260
6 IAP 00275253
7 Referee workitem 00275283
To configure a General Task:

1. Execute 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.
For SAP version 4.7 or above:
For SAP version 4.6C:

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.
6. Follow your standard change request process for tracking changes.
7. Repeat the procedure for all the tasks mentioned in Table 3-1 on page 24.
3.2.3 Refreshing SAP Workflow Runtime Buffer

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

1. Execute the SWU_OBUF transaction.

For SAP version 4.7 or above:
For SAP version 4.6 C:
2. To refresh the runtime buffer, click the Start Synchronization button (for SAP
version 4.7 or above) or the Synchronization button (for SAP version 4.6 C, see
highlight).
3.2.4 Configuring Object Services

The VIM dashboard and the OpenText Document Processing document services are
accessible from the SAP Invoice function.
To activate the object services:

1. Execute the SM30 transaction.

2. Enter SGOSATTR in the Table/View field and click the Maintain button.
3. When a popup is displayed, indicating that the table is cross client, click the
button.
4. Check whether the entries for the services WF_ZOPT/VIM and ZOPT_SERVC are
present.
If the entries are not present, add these entries, as shown in the screenshots
below.

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

If you are prompted to create a new transport, continue with the next step.

6. Follow your standard change request process for tracking changes.
3.2.5 Maintaining Number Ranges

You have to maintain number ranges for the following objects:
Object Description
/PTGWFI/RI CP Document
/OPT/DOCID Document Processing
/ORS/STACK Invoice Approval
/ORS/USRMP Invoice Approval Usermap (optional)
Important
All the number ranges intervals must be 01.
To maintain the number range:

1. Execute 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.2.6 Generating and Activating SAP Parking APIs

In some case, the standard SAP function module PRELIMINARY_POSTING_POST_ALL
might not be activated in the system. This section describes how you activate it if
needed.
To generate the /OPT/FIPP business object and activate SAP parking APIs:
1. Execute the SWO1 transaction and enter the object /OPT/FIPP.
2. Click the Generate button in the tool bar, see highlight in the screenshot above.
The business object is generated.
3. Click the Display button.

4. Navigate to and click Parked InvoiceExtn.PostParkedInvoice.

Continue and click the Program button, as highlighted in the above screen.
5. Navigate to and double click the PRELIMINARY_POSTING_POST_ALL function

module, as shown above.

6. Click the Activate button in the tool bar to activate the function module, see
highlight in the screenshot above.

7. Click the Single Test button in the tool bar, see highlight in the screenshot
above.
8. Click the Execute button in the tool bar, see highlight in the screenshot above.

9. If you receive a message saying Program must be regenerated, as shown

above, test again by repeating this step until you get the following screen.
Once you see the message above, you have verified that the /OPT/FIPP business
object is generated and the function module is active.

3.2.7 Generating Business Object

In some case, the /OPT/B2081 business object might not be generated in the system
properly. This section describes how to generate it if needed.
To generate the /OPT/B2081 business object:

1. Execute the SWO1 transaction and enter the object /OPT/B2081.
2. Click the generate button in the tool bar, see highlight in the screenshot above.
The business object is generated.
3.2.8 Linking Events for VIM Workflows

SAP events are trigger point for VIM workflows. For example, when a logistic
invoice is posted, SAP 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.
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, execute 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, execute the SWEQADM transaction. You
can set the frequency according to your requirement how often to update
the respective data.
The following event linkages can be turned on or off to enable or disable VIM
workflows:
Table 3-2: Event linkages for VIM workflows
Object type Event Receiver function module Usage com-

ments
Receiver type Check function module
FIPP DELETED SWW_WI_CREATE_VIA_EVENT Invoice Ap-
proval (IAP)
TS00275270 —
FIPP POSTED SWW_WI_CREATE_VIA_EVENT IAP
TS00275270 —
BUS2081 DELETED SWW_WI_CREATE_VIA_EVENT IAP
TS00275270 —
BUS2081 POSTED SWW_WI_CREATE_VIA_EVENT IAP
TS00275270 —
BUS2081 POSTED /OPT/BL_PO_BLK_RECEIVER Invoice Excep-
tion (IE)
WS00275264 —
/OPT/FIPP ZWFI_CREATED /OPT/BL_NPO_PRK_RECEIVER IE
WS00275254 /PTGWFI/PIR_F_CHECKFM
/OPT/B2081 ZWFI_PARKED /OPT/BL_PO_PRK_RECEIVER IE
WS00275260 /PTGWFI/PRK_M_CHECKFM
FIPP DELETED /OPT/VIM_RPT_RECEIVER_FM VIM Analytics

(VAN)
— —
FIPP POSTED /OPT/VIM_RPT_RECEIVER_FM VAN
— —
BUS2081 DELETED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
BUS2081 POSTED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —

Object type Event Receiver function module Usage com-

ments
Receiver type Check function module
BUS2081 RELEASED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
BUS2081 CANCELLED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
To enable and disable VIM workflows:

1. To open the Event Type Linkages screen, execute the SWE2 transaction.
2. Create the event linkage entries shown in Table 3-2 (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 Table 3-2.
3.2.9 Setting the Extraction and Validation Retry Count

This setting is only necessary if Invoice Capture Center (ICC) is implemented on
your system. Otherwise, you can skip this section.
You maintain the maximum allowed tries and the time limits for extraction and
validation, using table /OPT/VIM_RETRY. To maintain this table, use transaction
SM30.
To set the extraction and validation retry count:

1. Execute the SM30 transaction.

2. Enter /OPT/VIM_RETRY in the Table/view field and click the Maintain button.
3. Maintain Number of Retry and Time limit (in seconds).
Call Point
EX
represents extraction.
VA
represents validation.
OpenText recommends the following settings for Time limit (in seconds)

Extraction
7200
Validation
3600
3.2.10 Maintaining Business Transaction Events (BTEs)

To maintain product code /opt/vim:
1. Execute the FIBF transaction.
2. Follow the menu path Settings > Products > … of a customer.

3. Click the New Entries button.
Enter the following details:

Product
/OPT/VIM
Text
OpenText VIM
A
Select the check box.
4. Save your settings.
To maintain entries in the P/S modules:


2. Follow the menu path Settings > P/S Modules > … of a customer.
4. Enter the details as shown in the following screenshot.
To maintain entries in process modules:

2. Follow the menu path Settings > Process Modules > … of a customer.
4. Enter the details as shown in the following screenshot.

3.2.11 Maintaining Standard Text

This activity is only required if the SRM PO functionality is being implemented in
VIM.
The standard text is client dependent and should be copied from client 000 to all
required clients. Execute the following steps to do a client copy of the following
standard text in the required languages:
• /OPT/VIM_DP_SRM_PRICE_HEADER
• /OPT/VIM_DP_SRM_QTY_FOOTER
• /OPT/VIM_DP_SRM_QTY_HEADER
• /OPT/VIM_DP_SRM_QTY_URL_HEAD
To maintain standard text:

1. Execute the SO10 transaction.

2. Follow the menu path Utilities > Copy from Client.
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.

Chapter 4
Verifying Installation
Make sure that the OpenText Vendor Invoice Management add-on is reflected in the
installed components.
To verify the installation:

1. 1. From the SAP menu, open System > Status.
2. Click the button next to Component version.

Chapter 4 Verifying Installation
In the System: Component information dialog, you should see the OTEXVIM
add-on component installed, with Release number as shown in the following
table.
SAP Version Release

ECC 6.0 604_700
ECC 5.0 603_640
SAP 4.7 602_620
SAP 4.6 C 601_46C

Chapter 5
Upgrading
This chapter describes the upgrade procedure for both SAP upgrade and VIM
upgrade.
5.1 Upgrading SAP

This section discusses the process to perform during an SAP upgrade with regards
to VIM.
When you have to upgrade your SAP system and you already installed VIM using
packages, you have to use the specific VIM SAP upgrade packages.
When you upgrade an SAP release to a higher release, the system automatically
recognizes that an SAP add-on is installed and requests the respective upgrade
package. This way the standard SAP upgrade procedure also updates the VIM add-
ons to the relevant version.
Password The OpenText Vendor Invoice Management package is protected with a specific
control password. During upgrade, this password is requested by the SAP Add-On
Installation Tool (SAINT). For the SAP upgrade password, see “Password Control”
on page 14.
Prerequisites
• Make sure the profile parameter transport/systemtype is set to CUSTOMER, not
to SAP. If it is set to SAP, you will get object generation errors.
• Apply OSS note 1082597: Not enough business functions activated in SFW5; this
is used for Switch Frame Work for activating the PO based invoice parking
infrastructure.
• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s AS
ABAP
• The following component must be installed:
Component SAP_BASIS
Level: 700
• The following support package must be installed:

Chapter 5 Upgrading
SAPKB70010
• One of the following add-on components must be installed:

• OTEXVIM 604_700
• OTEXVIM 603_640
• OTEXVIM 602_620
• OTEXVIM 601_46C
To prepare the SAP upgrade:

1. Inform all users about the scheduled downtime as early as possible.
2. Before you begin the upgrade, it is recommended to perform a complete backup
or take a snapshot of the SAP system.
To perform the SAP upgrade:

application server in the /usr/sap/trans folder. This is the parent folder of the
DIR_EPS_ROOT folder.
Upgrade to ECC File Source path Target path
6.0 from SAP
version
SAP ECC 5.0 OTEXERP_UPGR UPGR_ERP/DATA/ /usr/sap/trans/
SAP R/3 4.7 _VIM604_700. EPS
SAP R/3 4.6C SAR
Upgrade to ECC File Source path Target path

5.0 from SAP
version
SAP R/3 4.7 OTEXERP_UPGR UPGR_ERP/DATA/ /usr/sap/trans/
SAP R/3 4.6C _VIM603_640. EPS
SAR
Upgrade to SAP File Source path Target path

4.7 from SAP
version
SAP R/3 4.6C OTEXERP_UPGR UPGR_ERP/DATA/ /usr/sap/trans/
_VIM602_620. EPS
SAR

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

5.1 Upgrading SAP
3. Follow the standard SAP system upgrade instructions.

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

Chapter 5 Upgrading
Important
In case of an SAP upgrade, do not activate BC Sets, as described in
“Activating Business Configuration Sets” on page 20. If you activate BC
Sets, all the configuration data is overwritten with OpenText baseline
configuration data and all custom configuration changes are lost.
At the end of the upgrade you may see the following screen.
When checking the LONGPOST.LOG, you may discover the following error
referencing the VIM namespace.
A2PESEEF_BADI 103 BAdI implementation "/OPT/VIM_CHECK_MIRO" must

still be migrated
2 EPU139 Postprocessing necessary when upgrade has been
completed"SEEF_BADI""103"
A2WESEEF_BADI 051 Migrate implementation "/OPT/VIM_CHECK_MIRO"
using transaction SPAU
Execute the upgrade report "COM_PRODUCT_UPGRADE"
In transaction SPAU, you may see the /OPT/VIM_CHECK_MIGO Business Add-Ins

referenced for the VIM namespace.

5.2 Upgrading VIM
If the two objects are green (see screenshot above), they are active and
generated. This is okay and can be ignored.
Execute the COM_PRODUCT_UPGRADE report using transaction SE38. This report is
outlined in the “SAP ERP Central Component 6.0 SR3 ABAP Upgrade Guide”
section for Follow-up Activities, 6.22 Executing Conversion Programs for the
Product Master, p. 154.
If you have errors running this program, refer to SAP notes 970046 and 1055794.
To finish the SAP upgrade:

1. After the upgrade, perform the installation verifying activities, as described in
“Verifying Installation” on page 49.
2. Test the entire VIM process like for a new VIM installation.
3. When you have successfully completed all tests, inform the OpenText Project
Manager.
With this information, we can keep our customer installation database up-to-
date, which helps us providing faster technical support for you.
5.2 Upgrading VIM

This section discusses the process to perform an upgrade from VIM 5.1.6 to VIM 6.0,
and from VIM 5.2 to VIM 6.0. The upgrade will not include any customizing you
have done to VIM; you will have to migrate the customizing to VIM 6.0.
Password The OpenText Vendor Invoice Management package is protected with a specific
control password. During VIM upgrade, this password is requested by the SAP Add-On
Installation Tool (SAINT). For passwords for a VIM upgrade, see “Password
Control” on page 14.
Prerequisites
General prerequisites
• Apply OSS note 1082597: Not enough business functions activated in SFW5;
this is used for Switch Frame Work for activating the PO based invoice
parking infrastructure.

Chapter 5 Upgrading
• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s

AS ABAP
• Apply OSS note 1462364: Dependent structure has inconsistent runtime
object after mass activation. This is specific to SAP ECC 6.0 system, up to
EHP5.
• Apply OSS note 636217: DDIC activation error as table width greater than
1962 bytes. This is specific to SAP 4.6 C system.
• The following components must be installed:
ECC 6.0
Component SAP_BASIS
Level: 700
SAPKB70010

• The following add-on component must be installed:
OTEXVIM 520_700 or OTEXVIM 516_700
ECC 5.0
Component SAP_BASIS
Level: 640
SAPKB64022

R/3 4.7
Component SAP_BASIS
Level: 620
SAPKB62064


5.2 Upgrading VIM
R/3 4.6C
Component SAP_BASIS
Level: 46C
SAPKB46C53

OTEXVIM 520_46C or OTEXVIM 516_46C
Check VIM version number

Make sure that you already have VIM 5.1.6 or VIM 5.2 installed. To check the
version of VIM, open System > Status from the SAP menu and check the
Component Version.
For more details, see “Verifying Installation” on page 49.

Chapter 5 Upgrading
Adjust SAINT tool settings

In the settings of the SAINT tool, make sure that ABAP/Screen Generation is
set to Always.
To prepare the VIM upgrade:

1. Inform all users about the scheduled VIM downtime as early as possible.
Users must not perform any actions on the Accounts Payable module; that
means, the entire VIM processes must not be performed.
2. Before you begin the update, perform a complete backup or take a snapshot of
the SAP system.
3. Make sure the namespaces /OPT/, /ORS/, and /PTGWFI/ are modifiable:
a. Execute the SE06 transaction.
b. Click System change option in the application tool bar.

5.2 Upgrading VIM
c. In the Namespace/Name Range list, change the namespaces /OPT/, /ORS/,

and /PTGWFI/ to Modifiable and save.
To perform the VIM upgrade:

When you have to upgrade VIM and you already installed VIM using packages, you
have to use the specific VIM upgrade packages.
application server in the /usr/sap/trans folder. This is the parent folder of the
DIR_EPS_ROOT folder.
SAP system File Source path Target path
SAP ECC 6.0 OTEXVIM_UPGR UPGR_VIM/DATA/ /usr/sap/trans/EPS
_604_700.SAR
SAP ECC 5.0 OTEXVIM_UPGR UPGR_VIM/DATA/ /usr/sap/trans/EPS

_603_640.SAR
SAP R/3 4.7 OTEXVIM_UPGR UPGR_VIM/DATA/ /usr/sap/trans/EPS

_602_620.SAR
SAP R/3 4.6C OTEXVIM_UPGR UPGR_VIM/DATA/ /usr/sap/trans/EPS

_601_46C.SAR

The resulting PAT file is extracted to the EPS/in folder relative to the path of the
SAPCAR file.
documentation.
4. Continue the Add On process by selecting Add On OTEXVIM.
Click the Continue button.

Chapter 5 Upgrading
5. When the Add Modification Adjustment Transports to the Queue message is

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

5.2 Upgrading VIM
7. Make sure that Start options is set to Start in dialog immediately for
Preparation and Continue in Dialog immediately for Import 1, Import 2,
and Clean Up.
A message is displayed, confirming the successful import.
8. Check in the SAINT tool if the package has been imported successfully with the
new release number. See “Verifying Installation” on page 49 for specific release
number.
To finish the VIM upgrade:

1. Install VIM 6.0 Support Pack 1.
2. After the upgrade, perform/verify all the post installation activities as described
in “Post Installation Activities” on page 19, except activating BC set.
Important
Do not activate BC Sets, as described in “Activating Business
Configuration Sets” on page 20. If you activate BC Sets, all the
configuration data is overwritten with OpenText baseline configuration
data and all custom configuration changes are lost.
3. Test the entire VIM process like for a new VIM installation.
4. When you have successfully completed all tests, inform the OpenText Project
Manager.
With this information, we can keep our customer installation database up-to-
date, which helps us providing faster technical support for you.

Chapter 6
Troubleshooting
6.1 FAQs
The following FAQs cover basic troubleshooting information.
Does VIM consist of any standard SAP objects/repairs?
No
Does VIM consist of any Z objects?
No
How do I check whether installation is successful?
Refer to “Verifying Installation” on page 49.
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.

Part 2
OpenText Approval Portal Installation
Part 2 OpenText Approval Portal Installation
This part describes the installation of the OpenText Approval Portal component. The
Approval Portal is designed to work within SAP Web Application Server (WAS) 7.0
or SAP NetWeaver Portal (NWP) 7.0. The Approval Portal can be deployed as a
standalone application residing on WAS 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 OpenText Vendor Invoice Management - Administration Guide
(VIM-AGD) for troubleshooting and administrating the Approval Portal.

Chapter 7
7.1 Installation Prerequisites

A complete installation and configuration of the Invoice Approval SAP component
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
component, you will not be able to verify if the installation of the Approval Portal is
completed and correct.
Web browser The following web browsers are supported: Internet Explorer 6.0, 7.0, and 8.0.
Server SAP Web Application Server (WAS) 7.0 SP9 or above with SPNegoLoginModule or
SAP NetWeaver Portal (NWP) 7.0 SP9 or above. The requirement “SP9 or above”
does also refer to the EhP level.
Note: For further information, see the SAP Note: 994791-SPNego Wizard.
Operating The following table shows the supported combinations of operating systems and
systems SAP NetWeaver versions:
Approval Por- Approval Por-

tal 6.0 (Win- tal 6.0 (UNIX)
dows)
SAP NetWeaver 7.0 WAS 7.0
Portal 7.0
SAP NetWeaver CE 7.1 WAS CE 7.1
Portal CE 7.1
Portal CE 7.2
Portal 7.3
The following table shows the supported combinations of operating systems and
SAP NetWeaver 7.0 higher versions.
Notes:
• You can achieve support of the Approval Portal for SAP NetWeaver higher
versions with two landscapes: SAP NetWeaver 7.0 and SAP NetWeaver 7.0
higher version.

• OpenText recommends having both landscapes on the same operating

system.
WAS 7.0 Portal WAS 7.0 Portal

(Win- 7.0 (Win- (UNIX) 7.0
dows) dows) (UNIX)
Portal CE 7.1
Portal CE 7.2
Portal 7.3
SSL OpenText recommends implementing SSL (HTTPS) if security is a concern. Basic

Authentication in SPNego is using Base64 encryption which can be easily decrypted.
See http://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspx for further
information.
Sizing Standard sizing requirements for SAP WAS or NWP 7.0 apply.
requirements
SAP user A SAP CPIC user in the SAP R/3 server

The communication with the SAP system is accomplished by using a CPIC user ID.
However, the Web user is recorded as the agent who approved an invoice, not the
CPIC user.
User type
Communication Data (CPIC)
Profile
Create a profile with the following authorization objects and add it to the CPIC
user:
Object: S_RFC
Activity
Execute (16)
Names of RFC to be protected
/OPT/VIM_FG1A2, /ORS/*, /OPT/*, /ORS/SAPL000007_APPR_SCREEN,
/PTGWFI/*, ARCHIV_GET_CONNECTIONS, ARFC, ERFC, RFC1, SDIFRUNTIME,
SUNI, SYST, SYSU
RFC_TYPE
FUGR (Function Group)

7.2 Installation Components
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/*
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 Server provides the following profiles that need to be
assigned to the CPIC user to access images:
• S_AL_ADMLO (Display ArchiveLink administrator)
• S_AL_ADMDE (Delete ArchiveLink administrator)
Defaults
Decimal notation should be 1,234,567.89.
7.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 Web Application Server Components
• Java Enterprise archive (.ear file) - for the actual J2EE application

7.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 WAS only utilizing integrated
authentication
• as an application inside NWP using AppIntegrator iView
The following diagrams show the architecture for each scenario:

Figure 7-1: Approval Portal architecture with WAS
The SAP help pages linked in the following discuss some of the communication
channels between each component:
• Simple and Protected GSS API Negotiation Mechanism (SPNEGO)
(http://help.sap.com/saphelp_nw2004s/helpdata/en/43/4bd58c6c5e5f34e1000
0000a1553f6/frameset.htm)
• Network and Transport Layer Security
(http://help.sap.com/saphelp_nw70ehp1/helpdata/en/3a/7cddde33ff05cae100
00000a128c20/frameset.htm)
• SAP Java Connector (JCO)
(http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5c6a85b11d6b285005
08b5d5211/content.htm)

Figure 7-2: Approval Portal architecture with NWP
7.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 WAS 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 WAS with NWP utilizing integrated

authentication by accessing application directly without iView
No need for SAP GUI Logon ID; only network ID is required.

Chapter 8
Installing the Approval Portal
8.1 Preparing the Installation

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

To gain access to the file system, sign on to the host server as a user with
administrator rights.
Extract the files from opentext.zip from the delivery to a folder on the server.
Important
OpenText recommends you to create and deploy to the folder
usr/sap/<SID>/SYS/global/opentext/invoiceCfg. This is the
default location for putting the application configuration file. If you
deploy to another location, you will have to manually add a startup
parameter in the Config Tool to tell the application where to look for the
configuration files. This will also require restarting the WAS. See step 2
on page 76 for details.
<SID> is the system ID of the Web Application Server (WAS). Example:
T39.
Example: E:\usr\sap\T39\SYS\global\opentext\invoiceCfg
This folder is referenced as <InstallDir> in the following.
The <InstallDir> folder contains the following files:
configuration.xml
containing all the configuration for the application
mobileconfiguration.xml
containing all the configuration for mobile support
Lang_Support.properties
containing all the mapping of languages code; see section 23.3.2
"Configuring Additional Languages" in OpenText Vendor Invoice Management
- Administration Guide (VIM-AGD) for details.
Lang_DE.properties
containing all the text for the German language resource

Chapter 8 Installing the Approval Portal
Lang_EN.properties
containing all the text for the English language resource
Lang_ES.properties
containing all the text for the Spanish language resource
Lang_FR.properties
containing all the text for the French language resource
Lang_IT.properties
containing all the text for the Italian language resource
Lang_JA.properties
containing all the text for the Japanese language resource
Lang_NL.properties
containing all the text for the Dutch language resource
Lang_PT.properties
containing all the text for the Portuguese language resource
Lang_RU.properties
containing all the text for the Russian language resource
Lang_ZH.properties
containing all the text for the Chinese language resource
There might be more .properties files, depending on the package and the
release for additional languages. The language resource files can be changed.
See section 23.3.1 "Changing Language Resources" in OpenText Vendor Invoice
Management - Administration Guide (VIM-AGD) for details.
Important
Make sure the <InstallDir> folder has:
• correct permissions for the J2EE application to write and read
• Full Control permission to the J2EE Engine service user (or to Every-
one)
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

8.2 Configuring the Administrator Role
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 WAS (example O15).
• INSTANCE_NAME is the WAS 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=<InstallDir>.
Example: -
Dcom.opentext.vim.portal.invoiceCfg=c:/opentext/invoiceCfg
b. Save the new parameter.

3. To apply the new startup parameter, restart the WAS.
Restarting informs the server that the <InstallDir> folder contains application
specific information.
8.2 Configuring the Administrator Role
Important
This section is only needed if you are installing as a standalone J2EE
application residing on WAS 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 23 "Administering and
Troubleshooting the Approval Portal" in OpenText Vendor Invoice Management -
Administration Guide (VIM-AGD) for additional information.
8.2.1 Configuring the Administrator Role for Access Through

WAS
This section describes how to create a VIM administrator role and assign it to the
domain user through WAS Visual Administrator.
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 81.
• Navigate to http://<WAS>:<WASPORT>/vimportal/admin.

8.3 Deploying the Software Component Archive
If you see a screen similar to the one above, you have configured the
administrator role successfully.

Deploying the Software Component Archive comprises the following steps:
• “Connecting to the SAP Software Deployment Manager (SDM)” on page 81
• “Deploying the .sca File or .sda File” on page 82
• “Checking Correct Deployment” on page 83
• “Optional: Starting the Approval Portal J2EE Application Manually” on page 85
8.3.1 Connecting to the SAP Software Deployment Manager

(SDM)
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
8.3.2 Deploying the .sca File or .sda File

If there is a previous version of the Approval Portal, remove it before you continue.
Refer to “Uninstalling the Approval Portal” on page 105 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_PORTAL6_0.sca or
IM_APPROVAL_PORTAL6_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.
8.3.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 WAS, navigate to
http://<WAS>:<WASPORT>/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.
8.3.4 Optional: Starting the Approval Portal J2EE Application

Manually
By deploying through SDM, the Approval Portal J2EE application will start
automatically. If the Approval Portal J2EE application doesn't, you can start it
manually.
To start the Approval Portal J2EE application manually:

1. Click on a server.
2. Expand Services.
3. Expand Deploy.
See screenshot in step 3 on page 84.
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.

Chapter 9
Configuring SAP NetWeaver Portal Components
If you are deploying the Approval Portal on WAS and the users are accessing the
application through SAP NetWeaver Portal, you must configure the SAP
NetWeaver Portal components.
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 87
• “Creating Roles for Users” on page 93
• “Assigning Roles to SAP NetWeaver Portal Users” on page 96
• “Configuring IViews and Roles for the Administrator” on page 97
9.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 9 Configuring SAP NetWeaver Portal Components
3. Right-click on the new folder and select New > iView.

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

click Next.

6. In Step 2: Portal Component Selection, click Generic and click Next.
7. In Step 3: General Properties, enter the following parameters:

• iView Name (mandatory)
• iView ID (mandatory)
• iView ID Prefix

• Description
Select the Master Language (mandatory).
Click Next.
8. In Step 4: Summary, click Finish to finish the initial iView creation.
9. Click Open the object for editing and click OK.

10. In Property Editor, scroll to the Entry Point line and click Yes.
Scroll to the HTTP Request Method line and select HTTP:GET.
Click Save.
11. In Property Editor, scroll to the URL Template line.

Enter the following value:
http://$host$:$port$/vimportal/?urlView=Y&PORTALUSER=<User.UserID
>

9.2 Creating Roles for Users
Change host and port accordingly:

$host$
WAS server name where the Approval Portal J2EE application was deployed
$port$
Port of that WAS
Note: Do not change <User.UserID>.
12. Click Save and Close.
The creation of the AppIntegrator iView is now finished.

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 87.
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 90 in “Creating AppIntegrator IViews for Users”
on page 87.
• Role ID Prefix is not mandatory. If you enter this parameter, you must
search by giving Role ID Prefix and Role Name when assigning the role
to the user.
4. Click Next.

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

7. In Property Editor, scroll to the Entry Point line and click Yes.
Click Save.
8. Select the AppIntegrator iView created in “Creating AppIntegrator IViews for

Users” on page 87, 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.
9.3 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.

9.4 Configuring IViews and Roles for the Administrator
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 93).
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.
9.4 Configuring IViews and Roles for the

Administrator
Configuring iViews and roles for the administrator is almost the same as for users.
See sections 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.UserI
D>

See step 11 on page 92 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 96.
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.

Chapter 10
Applying a New Patch
Note: Unlike the VIM SAP 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 component. For example, Approval Portal SP2 does not work with VIM
SAP components SP1 or SP3, it will only work with SP2.
New .sca file or .sda file
Follow the steps to undeploy the .sca or .sda file in “Uninstalling Using
Software Deployment Manager” on page 105, and then follow the steps to
deploy the .sca file or .sda file in “Deploying the .sca File or .sda File” on
page 82.
New <language>.properties files
Extract the new <language>.properties files from the media to <InstallDir>
and perform the Reinitialize Application task. See section 23 "Administering
and Troubleshooting the Approval Portal" in OpenText Vendor Invoice Manage-
ment - Administration Guide (VIM-AGD) for more details.

Chapter 11
Upgrading the Approval Portal from Previous
Versions
You can upgrade the Approval Portal from version 5.2 to 6.0, only.
Make sure that all files mentioned in opentext.zip are deployed correctly.
You can reuse the original configuration.xml file as there are no changes; but it is
best to make a backup of the configuration.xml.
If you changed the language properties files from the previous version and would
like to reuse them in VIM 6.0, change the new language properties files manually.
To upgrade, perform the actions described in “Applying a New Patch” on page 99.

Chapter 12
Troubleshooting
For information on troubleshooting the Approval Portal, see section 23.14
"Troubleshooting" in OpenText Vendor Invoice Management - Administration Guide
(VIM-AGD).

Chapter 13
Uninstalling the Approval Portal
To uninstall the Approval Portal, perform the following steps:
• “Uninstalling Using Software Deployment Manager” on page 105
• “Removing SAP NetWeaver Portal Components” on page 106
• “Deleting Properties Files” on page 106
• “Optional: Removing the Startup Parameter in the Config Tool” on page 107
13.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.
To uninstall files from the SDM repository:

1. Connect to the SAP Software Deployment Manager (SDM) in the host server:
You find SDM in the following directory:
usr/sap/<SID>/<INSTANCE_NAME>/SDM/program.
Notes:
The script file is:

• RemoteGui.bat for Windows hosts
• RemoteGui.sh for Unix hosts
Refer to the Software Deployment Manager Guide for more details on how to
use SDM.
2. In SDM, click the Undeployment tab.
3. Find and click IM_APPROVAL_PORTAL.
4. Click Select.
5. Click Start Undeployment.
In Step 2 of 2, you see the progress.

Chapter 13 Uninstalling the Approval Portal
6. To finish the undeployment, click Confirm.

opentext.com\IM_APPROVAL_PORTAL should no longer appear in the Visual
Administrator.
13.2 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 87.
Right-click the folder and click Delete.

5. In the Delete Confirmation page, click Finish.
The “OpenText Approval Portal” folder is now deleted.
13.3 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 Web Application Server (WAS). See “Preparing the Installation” on
page 75 for details on the properties files.

13.4 Optional: Removing the Startup Parameter in the Config Tool
13.4 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 76 in “Preparing the Installation” on page 75.
Removing the startup parameter, using the J2EE Config Tool, finishes the
uninstallation process.
To remove the startup parameter:

1. Invoke the J2EE Config Tool:
You find the Config Tool in the following directory:
usr/sap/<SID>/<INSTANCE_NAME>/j2ee/configtool.
Notes:
The script file is:

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

-Dcom.opentext.vim.portal.invoiceCfg=<InstallDir>
Example: -
Dcom.opentext.vim.portal.invoiceCfg=c:/opentext/invoiceCfg

4. Restart the WAS to remove the startup parameter.
The uninstallation is now completed.

Part 3
Vendor Invoice Management CRM Shared
Service Framework (SSF) Component
Installation
13.4 Optional: Removing the Startup Parameter in the Config Tool
This part describes the installation of the Vendor Invoice Management CRM Shared
Service Framework (SSF) component:.

Chapter 14
14.1 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). For the VIM CRM SSF installation package, the password
is 316C596F6A.

The following prerequisites must be fulfilled for the installation of the SSF
integration.
14.2.1 Required Knowledge

The following knowledge is required for the person dealing with the installation as
described in this document:
• In-depth knowledge of SAP administration tasks, in particular the SAP Add-On
Installation Tool (SAINT) and CRM Add-On Installation
• Basic knowledge of the employed operating system
14.2.2 SAP CRM EHP1 Prerequisites

Check the following prerequisites prior to installation:
The following components must be installed for SAP CRM 7.0 EHP1:
Component SAP_ABA
Level: 702
Component BBPCRM
Level: 701
Component SAP_BASIS
Level: 702
SAPKA70203, SAPKB70203

To activate Shared Service Framework using Switch Framework:

1. Execute the SFW5 transaction.
2. Expand the ENTERPRISE_BUSINESS_FUNCTIONS node, select the Planned
Status check box for business functions CRM_IC_CEBP & CRM_SHSVC and
click the Activate Changes icon.
14.2.3 Installation Tool

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

Chapter 15
Installing the OpenText Package
This chapter describes the installation of the Basis package of Vendor Invoice
Management (VIM) on an SAP CRM application server.
The basic components are installed with the Basis package.
To install the Basis package:

application server in the /usr/sap/trans folder (this is the parent folder of the
DIR_EPS_ROOT folder).
SAP CRM version

SAP CRM 7.0 EHP1
File
OTVIMSSF_INST_VIM701_702.SAR
Source path
INST_CRM_700/DATA/
Target path
/usr/sap/trans/EPS

following command:
SAPCAR -xvf <name of SAPCAR file>
The resulting PAT file will be extracted to the EPS/in folder relative to the path
of the SAPCAR file.
documentation.


Chapter 16
Post Installation Activities
To put the SSF integration into operation, you must perform the following post
installation tasks:
• “Activating Business Configuration Sets in the CRM System” on page 117
• “Maintaining a Logical System for the CRM System in VIM” on page 120
16.1 Activating Business Configuration Sets in the

CRM System
Notes:
• For every client, you must activate new BC Sets after installing VIM 6.0
CRM.
• You need the appropriate security authorization to execute some of the
transactions.
You activate the BC Sets in the following steps:
1. Apply recommended user settings
2. Activate BC Set /OTVIMSSF/VIM60_SSF_CUSTOMIZING
Note: Check the tables in /OTVIMSSF/VIM60_SSF_CUSTOMIZING and
decide if it is appropriate to activate this BC Set.
Activate the BC set in the Configuration client of the development system and
create a transport from BC set activation, move the transport to the required
systems.
Do not activate the BC set in the production system. Create a customization
transport in the development system configuration client by activating the BC
set and move it to the desired systems.
To apply recommended user settings:

SCPR20 transaction.
From the Utilities menu, click User Settings.

Chapter 16 Post Installation Activities
VIM 6.0 supports the following languages:

• Dutch
• English
• French
• German
• Italian
• Japanese
• Portuguese
• Spanish
• Russian
• Chinese
To select your applicable languages, select the respective check box in the
Manual Selection column.

16.1 Activating Business Configuration Sets in the CRM System
2. Click the Maint. Transaction tab.
Apply the settings, as shown in the screenshot.

3. To copy the settings, click .
You are now ready to activate the BC set.
To activate BC Sets:
SCPR20 transaction.

2. Enter the BC set name /OTVIMSSF/VIM60_SSF_CUSTOMIZING and click the

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

4. Click the Activate button.
Tip: You can skip any warnings during the activation.
After successful BC Set activation, a message is displayed in the lower left of the
SAP GUI: Activation ended with additional information.
16.2 Maintaining a Logical System for the CRM

System in VIM
To integrate the VIM CRM SSF component into VIM SAP component, you must
maintain a logical system for the CRM system in the backend ERP system (VIM SAP
component system). Support for CRM SSF will only be activated if the logical
system of the CRM is maintained. This setting generates the Service Requests
button in the dashboards and the Create SR check box in the process type
definition.
To maintain a logical system for the CRM system in the SAP ERP system:
1. In VIM, execute the /N/OPT/SPRO transaction and follow the menu path
LiveLink VIM - Configuration > CRM Integration > Maintain CRM Logical
System.

16.2 Maintaining a Logical System for the CRM System in VIM
2. Enter the logical system for the CRM system in the Constant Value field.

Chapter 17
Verifying Installation
Make sure that the OpenText Vendor Invoice Management CRM add-on is reflected
in the installed components.
To verify the installation:

1. From the SAP menu, open System > Status.
2. Click next to Component version.

Chapter 17 Verifying Installation
In the System: Component information dialog box, you should see the
OTVIMSSF add-on component installed, with Release number 701_702.

Part 4
Mobile App Installation
Part 4 Mobile App Installation
This part describes the installation of the mobile App, which is introduced with VIM
6.0 as an enhancement to the Invoice Approval. Users can approve their invoices,
using a mobile device, for example a Blackberry. Mobile support bases on the
OpenText Everywhere (OTE) infrastructure. For further information on OTE, see
OpenText Everywhere - Installation and Administration Guide (MOD-IGD).
A mobile application (mobile App) is available as a new SAP mobile solution for
VIM. Using the mobile App, users can perform their approval tasks in a simple GUI,
directly on their mobile device.

Chapter 18
Authentication for Mobile Approval
This section describes the communication and authentication needed for the mobile
App.
SAP versions The mobile App requires SAP version R/3 4.7 or higher. The prerequisites described
in “SAP Prerequisites” on page 14 apply for the mobile App.
Figure 18-1: Mobile App: communication and authentication

Chapter 18 Authentication for Mobile Approval
The communication of the mobile App with the SAP system is accomplished by
using a CPIC user ID. The OpenText Everywhere (OTE) middleware server is
connected to one SAP backend system.
The CPIC user logon parameters, with which the server will connect to the SAP
system during the web service calls, must be maintained during installation of the
OTE middleware server components.
Therefore the CPIC user must be created in the SAP system with the corresponding
authorities:
User type
Communication Data (CPIC)
Profile
Create a profile with the following authorization objects and add it to the CPIC
user:
Object: S_ICF
ICF_FIELD
SERVICE - Internet Communication Framework Service
ICF_VALUE
/ORS/OTE
Object: S_WFAR_OBJ
Activity
Display (03)
Content repository identification
Enter corresponding repositories.
Document type
Enter corresponding document types.
Object type
Enter corresponding object types.

Defaults
Decimal notation should be 1,234,567.89.
However, the web service user is recorded as the agent who approved an invoice,
not the CPIC user. The web service user authenticates against the active directory or
the content server when he logs on to the App on his mobile device.
OpenText recommends using the https protocol for communication between OTE
environment (middleware server) and SAP system. See “Optional: Setting Up SSL
Communication for the Web Application Server” on page 136.

Chapter 19
Installing the Mobile App
The mobile App bases on OpenText Everywhere (OTE). For a description of the
installation, see OpenText Everywhere - Installation and Administration Guide (MOD-
IGD), which is available in the OpenText Knowledge Center:
https://knowledge.opentext.com/knowledge/llisapi.dll/open/17392805. Open the
folder for Everywhere 1.5.0.

Chapter 20
Post Installation Activities
The following activities are only applicable, if Approval on a mobile device shall be
configured on your system.
20.1 Activating the Web Service

You must make sure that the web service 000007_8_ws is activated in the service
hierarchy.
To activate the web service:

1. Execute the SICF transaction.
2. In the Maintain Services screen, in the Service Path field, enter
/sap/bc/bsp/ors/000007_8_ws/ and execute.
3. If the service is inactive, activate it. Therefore, right-click the service.

4. In the context menu, click Activate Service.
20.2 Configuring Profile Parameters

For the communication between OTE middleware server and SAP backend, you
must make sure that the following profile parameters exist in your system.
• login/create_sso2_ticket
• login/accept_sso2_ticket
To configure profile parameters:

1. If the mentioned profile parameters do not exist, use the RZ10 transaction to
create them.

20.2 Configuring Profile Parameters
2. In the Edit Profiles screen, select the correct instance profile, click Extended
maintenance and change the data of the existing profile.
3. Maintain these profile parameters on the SAP backend. Set the following values:
4. If the SSO2 parameters do not exists, create them in the system.

The following screenshot shows the maintenance in the RZ10 transaction for one
parameter as an example.

5. Restart the system.

For more details according to the SSO2 configuration, see the SAP help:
http://help.sap.com/saphelp_nw04/helpdata/en/5c/b7d53ae8ab9248e100000
00a114084/frameset.htm
20.3 Optional: Setting Up SSL Communication for the

Web Application Server
For security reasons, OpenText recommends setting up SSL communication
between the OTE server component and the SAP server. Therefore, see SAP help
http://help.sap.com/saphelp_nw04/helpdata/en/65/6a563cef658a06e10000000a11
405a/frameset.htm and OSS note 510007 “Setting Up SSL On the Web Application
Server”.
SAP provides a guide for the necessary steps to be executed:
http://help.sap.com/saphelp_nw04/helpdata/en/89/c980808f9ae34aac8eb36e4727
c46b/frameset.htm
20.4 Activating SAP Systems

Data is retrieved from the corresponding SAP system(s) connected to the OTE
middleware server. Therefore, the logical system(s) must be maintained in the SAP
system, where the OTE middleware server connects. For details, see section 10.1
"Activating Logical Systems" in OpenText Vendor Invoice Management - Configuration
Guide (VIM-CGD).

Glossary
AAK
See: SAP Add-On Assembly Kit (AAK)
AP processor
Accounts Payable personnel
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).
Archive system
Computer system that enables storage, management and retrieval of archived
data and documents
ArchiveLink
Service integrated in the SAP Web Application Server for linking archived
documents and the application documents entered in the SAP system
ArchiveLink document types

Document types that need to be customized for ArchiveLink
Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can execute in the SAP system. These authorizations are stored in
Authorization profiles.
BAdI
See: Business Add-Ins (BAdI)
Baseline
Set of functionality with pre-defined configuration and the starting point to
implement VIM

Glossary
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 a new 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 rules
Rules that describe the operations, definitions and constraints that apply to an
organization
Business Transaction Event (BTE)

Event used for extending a Non PO invoice functionality to call a custom program
Buyer
Person who is in charge of the PO. This role should have authorization to create
and change the purchase order. This role is also responsible for negotiating and
communicating with vendors.
COA
See: Approval chart of authority (COA)
Coding
Coding allocates an invoice to G/L account and cost object if required.
Contract agent
Person who can create and modify SAP contracts.
Dashboard
User interface that organizes and presents information in a way that is easy to
read. Users can also perform actions from the dashboard.
DocuLink
OpenText DocuLink enables the archiving, management and retrieval of CRM or
ERP 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)
Duplicate analyzer
Person who is responsible to identify duplicate invoices
Event Type Linkage

Error handling method. Event Type Linkage determines what the application
should do in case an error could not be handled.
Exception
Action that is not part of normal operations or standards
FI
See: Financial Accounting (FI)
Financial Accounting (FI)

SAP module for the Finance and Accounting department
IAP
See: Invoice Approval (IAP)
ICC
See: Invoice Capture Center (ICC)
IE
See: Invoice Exception (IE)
Indexer
Person responsible for entering index data
Indexing
Process of entering or storing data into the system
Information provider
Receiving role for option Refer for Information

Glossary
Invoice Approval (IAP)

VIM component that enables users to perform coding, approving and rejecting
invoices
Invoice approver
Person who approves invoices
Invoice Capture Center (ICC)

Optional VIM OCR component
Invoice 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 a SAP invoice is
created
Invoice requester
Person who requested goods and services for Non PO invoices
LIV
See: Logistic invoice (LIV)
Logistic invoice (LIV)

purchase order invoice
Materials Management (MM)

SAP MM is the materials management module of the SAP ERP software
package. Materials management is used for procurement and inventory
management.
MM
See: Materials Management (MM)
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

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

Glossary
Purchase order (PO)

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

Invoice based on a Purchase order (PO)
Quantity variance
Situation where the quantity on the invoice is different from the quantity in the
purchase order
Receiver
Person who can create and reverse the goods receipt in SAP
Requisitioner
Person who requested goods and services
Roles
Set of predefined roles for the SAP user
SAP Add-On Assembly Kit (AAK)

Standardized delivery procedure for software
Scan operator
Person who scans the invoices into images (may not have a SAP ID)
Service approver
Person who approves a service entry
Service requisitioner
Person who enters a service entry
Swimlane
Diagram representing a specific VIM process. A swimlane comprises the process
description, roles, user interface and options of the process.
Tax expert
Person who advises on invoices that need tax audit. Normally tax department
personnel.
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.
Vendor maintenance
Person who is responsible for creating and maintaining the vendor master
records
VIM Analytics (VAN)

VIM component that gives users a clear data report on their invoices in progress.
VIM Analytics allows to track the documents routed through SAP workflows via
VIM.
Workflow
SAP business workflows can be used to define business processes that are not
yet mapped in the R/3 system.

Index
Configuring
workflow dialog tasks 24
Connect to SDM
.ear file OpenText Approval Portal 81
OpenText Approval Portal 69 conventions 8
.sca file CP Document number range 30
OpenText Approval Portal 69
.sda file
D
Deploy .sca file
A Deploy .sda file
Activate business configuration sets OpenText Approval Portal 82
SSF integration 117 Deploy Software Component Archive
Activating OpenText Approval Portal 81
SAP parking APIs 33
AppIntegrator iViews creation for users
E
SAP NetWeaver Portal components
Event linkage for VIM workflows 38
configuration 87
Extraction and validation retry count 41
Apply new patch
Approval Portal J2EE application F
start manually 85 FAQs
Architecture basic installation 63
Authentication G
mobile App 127 Generating
business object /OPT/B2081 38
B
BTE maintenance 43 I
Business Configuration Sets Installation
activate 20 installation tool 18
Business object /OPT/B2081 mobile App 131
generate 38 OpenText Approval Portal 75
package 19
C password control 14
Check correct deployment prerequisites 14
OpenText Approval Portal 83 required knowledge 14
Configure administrator role SAP prerequisites 14
OpenText Approval Portal 77 verification 49
Configure administrator role for access workflow customizing 16
through WAS Installation components
OpenText Approval Portal 78 OpenText Approval Portal 69

Index
Installation prerequisites installation 75

OpenText Approval Portal 67 installation components 69
Installation tool installation prerequisites 67
SSF integration 114 prepare installation 67, 75
Installing package 19 SAP user requirements 72
iViews and roles for administrator troubleshoot 103
SAP NetWeaver Portal components uninstall 105
configuration 97 upgrade 101
OpenText Online 9
L OpenText package installation
Logical system SSF integration 115
SSF integration 120
P
M Password
Maintain SSF integration 113
number ranges 30 Post installation activities 19
Mobile App mobile App 133
authentication 127 SSF integration 117
installation 131 Prepare installation
post installation activities 133 OpenText Approval Portal 75
profile parameters 134 SSF integration 113
SAP systems activation 136 Prerequisites
SSL communication for Web Application SSF integration 113
Server 136 Profile parameters
web service activation 133 mobile App 134
N R
Number range Refreshing runtime buffer 26
CP Document 30 Required knowledge
SSF integration 113
O Roles assignment to SAP NetWeaver
Object services 27 Portal users
OpenText Approval Portal SAP NetWeaver Portal components
.ear file 69 configuration 96
.sca file 69 Roles creation for users
.sda file 69 SAP NetWeaver Portal components
apply new patch 99 configuration 93
architecture 70 Runtime buffer 26
check correct deployment 83
configure administrator role 77 S
configure administrator role for access SAP CRM EHP1 prerequisites
through WAS 78 SSF integration 113
configure SAP NetWeaver Portal SAP NetWeaver Portal components
components 87 configuration
connect to SDM 81 assigning roles to SAP NetWeaver Portal
deploy .sca file 82 users 96
deploy .sda file 82 create AppIntegrator iViews for users 87
deploy Software Component Archive 81 create roles for users 93

Index
iViews and roles for administrator 97 VIM upgrade

OpenText Approval Portal 87 password control 55
SAP parking APIs VIM workflows
activate 33 event linkage 38
SAP systems activation
mobile App 136 W
SAP upgrade Web service activation
password control 51 mobile App 133
SAP user requirements Workflow customizing 16
OpenText Approval Portal 72 Workflow dialog tasks
Set extraction and validation retry count configure 24
41
SSF integration
activate business configuration sets 117
installation tool 114
logical system 120
OpenText package installation 115
password 113
post installation activities 117
prepare installation 113
prerequisites 113
required knowledge 113
SAP CRM EHP1 prerequisites 113
verify installation 123
SSL communication for Web Application
Server
mobile App 136
standard text maintenance 45
T
Troubleshoot
Troubleshooting
basic installation 63
typography 8
U
Uninstall
Upgrade
SAP 51
VIM 55
V
Verify installation
SSF integration 123
Verifying installation 49

VIM 6 0 Instalation Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VIM 6 0 Instalation Guide PDF

Uploaded by

Copyright:

Available Formats

OpenText Vendor Invoice Management

This guide describes the installation of all Vendor Invoice

Copyright © by Open Text Corporation, Open Text Inc.

Part 1 Vendor Invoice Management SAP Component Installation 11

3 Installing the OpenText Package............................................ 19

4 Verifying Installation ............................................................... 49

VIM060000-IGD-EN-3 OpenText Vendor Invoice Management iii

5.2 Upgrading VIM ....................................................................................... 55

Part 2 OpenText Approval Portal Installation 65

7 Preparing Installation ..............................................................67

8 Installing the Approval Portal .................................................75

9 Configuring SAP NetWeaver Portal Components .................87

10 Applying a New Patch .............................................................99

Part 3 Vendor Invoice Management CRM Shared Service

14 Preparing Installation ............................................................113

iv OpenText Vendor Invoice Management VIM060000-IGD-EN-3

14.2 Checking Prerequisites ........................................................................ 113

15 Installing the OpenText Package.......................................... 115

17 Verifying Installation ............................................................. 123

Part 4 Mobile App Installation 125

18 Authentication for Mobile Approval ..................................... 127

GLS Glossary 137

IDX Index 145

VIM060000-IGD-EN-3 Installation Guide v

1.1 About the Product

1.2 About the Document

VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 7

1.2.2 Document Overview

8 OpenText Vendor Invoice Management VIM060000-IGD-EN-3

Warnings, notes, and tips

Note: Notes provide additional information about a task.

1.3 Contact Information

VIM060000-IGD-EN-3 Installation Guide 9

12 OpenText Vendor Invoice Management VIM060000-IGD-EN-3

Disclaimer This guide delivers an overview of the installation procedures.

VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 13

2.2 Password Control

SAP upgrade 2177467708 2177417708 2177407708 -

2.3 Checking Prerequisites

2.3.2 SAP Prerequisites

SAP ECC 6.0

14 OpenText Vendor Invoice Management VIM060000-IGD-EN-3

Option Component: SAP_APPL Component: SAP_BASIS

SAP ECC 5.0

SAP R/3 4.7

VIM060000-IGD-EN-3 Installation Guide 15

SAP R/3 4.6 C

2.3.3 Workflow Customizing

To check for correct workflow configuration:

16 OpenText Vendor Invoice Management VIM060000-IGD-EN-3

SAP 4.7 or above

In the Maintain Runtime Environment node, the Configure RFC

VIM060000-IGD-EN-3 Installation Guide 17

The Workflow RFC destination configured completely entry must have

2.3.4 Installation Tool

18 OpenText Vendor Invoice Management VIM060000-IGD-EN-3

3.1 Installing the Package

To install the Basis package:

SAP ECC 5.0 OTEXVIM_603_640.SAR INST_ERP_640/DATA /usr/sap/trans/

SAP R/3 4.7 OTEXVIM_602_620.SAR INST_ERP_620/DATA /usr/sap/trans/

SAP R/3 OTEXVIM_601_46C.SAR INST_ERP_46C/DATA /usr/sap/trans/

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

3.2 Post Installation Activities