VIM 6 0 - Instalation Guide
Transcript of VIM 6 0 - Instalation Guide
-
8/15/2019 VIM 6 0 - Instalation Guide
1/147
OpenText Vendor Invoice Management
Installation Guide
This guide describes the installation of all Vendor InvoiceManagement (VIM) 6.0 components: Vendor InvoiceManagement SAP component, optional OpenText ApprovalPortal, and optional Vendor Invoice Management CRM SSFcomponent.
VIM060000-IGD-EN-3
-
8/15/2019 VIM 6 0 - Instalation Guide
2/147
OpenText Vendor Invoice Management
Installation Guide
VIM060000-IGD-EN-3Rev.: 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: [email protected]
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.
https://knowledge.opentext.com/https://knowledge.opentext.com/mailto:[email protected]://ftp.opentext.com/ftp://ftp.opentext.com/http://www.opentext.com/http://www.opentext.com/https://knowledge.opentext.com/mailto:[email protected]://ftp.opentext.com/http://www.opentext.com/
-
8/15/2019 VIM 6 0 - Instalation Guide
3/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management iii
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
-
8/15/2019 VIM 6 0 - Instalation Guide
4/147
Table of Contents
iv OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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 ServiceFramework (SSF) Component Installation 110
14 Preparing Installation ............................................................113
14.1 Password Control................................................................................. 113
-
8/15/2019 VIM 6 0 - Instalation Guide
5/147
Table of Contents
VIM060000-IGD-EN-3 Installation Guide v
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 ApplicationServer................................................................................................... 136
20.4 Activating SAP Systems ...................................................................... 136
GLS Glossary 137
IDX Index 145
-
8/15/2019 VIM 6 0 - Instalation Guide
6/147
-
8/15/2019 VIM 6 0 - Instalation Guide
7/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 7
Chapter 1
Introduction
1.1 About the Product
Vendor Invoice Management (VIM) is a packaged business solution that basicallysolves a business problem – paying correct amount to vendors on-time. VIM is anadd-on to your SAP system, the majority of its functions and processes run insidethe SAP system; it deals only with invoices that will be posted to SAP ERP. Itintegrates with standard SAP functions such as Invoice Verification, FinancialProcessing, etc.
Patches Patches (Hot Fixes), Support Packages and the latest versions of the Release Notesfor VIM are available in the OpenText Knowledge Center:https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605. Thelatest 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 theKnowledge Center, initiate a ticket request in SAP Service Marketplace.
For OpenText customers: Send an email to [email protected].
1.2 About the Document
1.2.1 Target Audience
This document addresses those who participate in the administration andmaintenance 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 forthis component includes:
• Site administrators• Database administrators
• Network administrators
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151494mailto:[email protected]://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151605https://knowledge.opentext.com/knowledge/llisapi.dll/Open/10151494mailto:[email protected]
-
8/15/2019 VIM 6 0 - Instalation Guide
8/147
Chapter 1 Introduction
8 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
1.2.2 Document Overview
This Installation Guide includes the complete installation information for all VendorInvoice 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 interfaceThis 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 commandprompt. It is also used for example data, text to be entered in text boxes, andother literals.
Note: If you copy command line examples from a PDF, be aware that PDFscan contain hidden characters. OpenText recommends copying from theHTML version of the document, if it is available.
KEY NAMESKey names appear in ALL CAPS, for example:Press CTRL+V.
Angled brackets < > are used to denote a variable or placeholder. The userreplaces the brackets and the descriptive content with the appropriate value. Forexample, becomes serv01.
Internal cross-referencesClick the cross-reference to go directly to the reference target in the currentdocument.
External cross-referencesExternal cross-references are usually text references to other documents.However, if a document is available in HTML format, for example, in theKnowledge Center, external references may be active links to a specific section in
the referenced document.
-
8/15/2019 VIM 6 0 - Instalation Guide
9/147
1.3 Contact Information
VIM060000-IGD-EN-3 Installation Guide 9
Warnings, notes, and tips
Caution
Cautions help you avoid irreversible problems. Read this informationcarefully 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 theproduct information provided by OpenText. You can access the following supportsources through OpenText Online:
• Communities
• Knowledge Center
OpenText Online Communities(http://communities.opentext.com/communities/livelink.exe/open/OpenTextOnlineCommunity) 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'scorporate extranet and primary site for technical support. The Knowledge Center isthe 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 SupportContacts at http://support.opentext.com/.
http://online.opentext.com/http://communities.opentext.com/communities/livelink.exe/open/OpenTextOnlineCommunityhttp://communities.opentext.com/communities/livelink.exe/open/OpenTextOnlineCommunityhttp://communities.opentext.com/communities/livelink.exe/open/OpenTextOnlineCommunityhttps://knowledge.opentext.com/https://knowledge.opentext.com/http://support.opentext.com/http://online.opentext.com/http://communities.opentext.com/communities/livelink.exe/open/OpenTextOnlineCommunityhttp://communities.opentext.com/communities/livelink.exe/open/OpenTextOnlineCommunityhttps://knowledge.opentext.com/http://support.opentext.com/
-
8/15/2019 VIM 6 0 - Instalation Guide
10/147
-
8/15/2019 VIM 6 0 - Instalation Guide
11/147
Part 1
Vendor Invoice Management SAP Component
Installation
-
8/15/2019 VIM 6 0 - Instalation Guide
12/147
Part 1 Vendor Invoice Management SAP Component Installation
12 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
This part describes the installation of the SAP component of Vendor InvoiceManagement (VIM).
-
8/15/2019 VIM 6 0 - Instalation Guide
13/147
-
8/15/2019 VIM 6 0 - Instalation Guide
14/147
Chapter 2 Preparing Installation
14 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
2.2 Password Control
The OpenText Vendor Invoice Management package is protected with a specificpassword. During installation, this password is requested by the SAP Add-OnInstallation Tool (SAINT).
The following table shows the passwords for VIM installation, SAP upgrade andVIM 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 asdescribed in this document:
• In-depth knowledge of SAP administration tasks, in particular the SAP Add-OnInstallation Tool (SAINT)
• Basic knowledge of the employed operating system
2.3.2 SAP PrerequisitesCheck 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; thisis 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 ASABAP
• 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 “Thenote 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
-
8/15/2019 VIM 6 0 - Instalation Guide
15/147
2.3 Checking Prerequisites
VIM060000-IGD-EN-3 Installation Guide 15
The following components must be installed for SAP ECC 6.0 up to EHP5:
Component: SAP_APPL Component: SAP_BASISOption
Release Support package Release Support package
1 600 SAPKH60006 700 SAPKB70010
2 602 SAPKH60205 700 SAPKB70010
3 604 SAPKH60402 700 orabove
SAPKB70103
4 605 - 700 orabove
SAPKB70203
SAP ECC 5.0
• Support Package Manager (transaction code SPAM) level 41
• Apply OSS note 938147: OAWD: Object does not exist (OA 233)
• 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 5.0:
Component SAP_ APPLLevel: 500
Component SAP_BASISLevel: 640
• The following support packages must be installed:
SAPKB64022, SAPKH50019
SAP R/3 4.7
• Apply OSS note 938147: OAWD: Object does not exist (OA 233)
• Apply OSS note 1568202: OpenText Vendor Invoice Management Solutions
• Apply OSS note 1390369: ALV graphic: Double number of bars
Support Package Manager (transaction code SPAM) level 41
Component SAP_ APPLLevel: 470
Component SAP_BASISLevel: 620
The following support packages must be installed:
SAPKB62064, SAPKH47030
-
8/15/2019 VIM 6 0 - Instalation Guide
16/147
Chapter 2 Preparing Installation
16 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
SAP R/3 4.6 C
• Support Package Manager (transaction code SPAM) level 47
• Apply OSS note 938147: OAWD: Object does not exist (OA 233)
• Apply OSS note 1568202: OpenText Vendor Invoice Management Solutions
• Apply OSS note 1390369: ALV graphic: Double number of bars
• Apply OSS note 636217: DDIC activation error as table width greater than 1962bytes
The following components and support packages are prerequisites.
The following components must be installed for SAP R/3 4.6 C:
Component SAP_ APPLLevel: 46C
Component SAP_BASISLevel: 46C
The following support packages must be installed:
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.
-
8/15/2019 VIM 6 0 - Instalation Guide
17/147
2.3 Checking Prerequisites
VIM060000-IGD-EN-3 Installation Guide 17
SAP 4.7 or above
In the Maintain Runtime Environment node, the Configure RFC
Destination entry must have the icon.
SAP 4.6C
-
8/15/2019 VIM 6 0 - Instalation Guide
18/147
-
8/15/2019 VIM 6 0 - Instalation Guide
19/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 19
Chapter 3
Installing the OpenText Package
This chapter describes the installation of the Basis package of Vendor InvoiceManagement (VIM) on an SAP application server. Read also “PreparingInstallation” on page 13 with general information on installation in an SAPenvironment.
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 SAPapplication server in the /usr/sap/trans folder (this is the parent folder of theDIR_EPS_ROOT folder).
SAP ver-
sion
File Source path Target path
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/34.6C
OTEXVIM_601_46C.SAR INST_ERP_46C/DATA
/
/usr/sap/trans/
EPS
2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with thefollowing command: SAPCAR -xvf .
The resulting PAT file will be extracted to the EPS/in folder relative to the pathof the SAPCAR file.
3. Carry out the import of the package as described in the respective SAPdocumentation.
3.2 Post Installation Activities
To ensure the integrity of the installed transports, you have to perform and validatethe following procedures:
• “Activating Business Configuration Sets” on page 20
-
8/15/2019 VIM 6 0 - Instalation Guide
20/147
Chapter 3 Installing the OpenText Package
20 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
• “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 VIMupgrade, do not perform the actions described in this section. In case of aVIM upgrade, previous VIM configuration data will be overwritten afteractivating Business Configuration Sets (BC Sets). Any custom changesperformed in a previous version of VIM need to be redone after the BC Setsactivation.
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 thetransactions.
• Depending on the SAP version, the following screens might look differenton 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 decideif it is appropriate to activate this BC Set.
Activate BC set in the Configuration client of the Development system andcreate a transport from BC set activation, move the transport to requiredsystems.
-
8/15/2019 VIM 6 0 - Instalation Guide
21/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 21
Don’t activate BC set in the production system. Create a customization transportin Development System configuration client by activating BC set and move it todesired systems.
To apply recommended user settings:
1. To access the Business Configuration Sets: Activation screen, execute theSCPR20 transaction.
From the Utilities menu, click User Settings.
VIM 6.0 supports the following languages:
• Dutch
• English
• French
• German
• Italian
-
8/15/2019 VIM 6 0 - Instalation Guide
22/147
Chapter 3 Installing the OpenText Package
22 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
• Japanese
• Portuguese
• Spanish
• Russian
• Chinese
To select your applicable languages, select the respective check box in theManual Selection column.
2. Click the Maint. Transaction tab.
Apply the settings, as shown in the screenshot.
3. To copy the settings, click .
You are now ready to activate the BC set.
To activate BC Sets:
1. To access the Business Configuration Sets: Activation screen, execute theSCPR20
transaction.
-
8/15/2019 VIM 6 0 - Instalation Guide
23/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 23
2. Enter the BC set name /OTEXVIM/VIM60_CORE
_CUSTOMIZING and click theActivate button (highlighted in the screenshot.
Note: If you are prompted to create a new transport, follow your standardchange 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 theSAP GUI: Activation ended with warning.
-
8/15/2019 VIM 6 0 - Instalation Guide
24/147
Chapter 3 Installing the OpenText Package
24 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
3.2.2 Configuring Workflow Dialog Tasks
Use the instructions in this section to set the attribute to “General Task” for thefollowing 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 thebutton.
-
8/15/2019 VIM 6 0 - Instalation Guide
25/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 25
3. In the Standard Task: Display screen, select Additional data > Agentassignment > Maintain.
For SAP version 4.7 or above:
For SAP version 4.6C:
-
8/15/2019 VIM 6 0 - Instalation Guide
26/147
Chapter 3 Installing the OpenText Package
26 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
4. In the Standard task: Maintain Agent Assignment screen, select the name ofthe 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
27/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 27
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 SAPversion 4.7 or above) or the Synchronization button (for SAP version 4.6 C, seehighlight).
3.2.4 Configuring Object Services
The VIM dashboard and the OpenText Document Processing document services areaccessible from the SAP Invoice function.
To activate the object services:
1. Execute the SM30 transaction.
-
8/15/2019 VIM 6 0 - Instalation Guide
28/147
-
8/15/2019 VIM 6 0 - Instalation Guide
29/147
-
8/15/2019 VIM 6 0 - Instalation Guide
30/147
Chapter 3 Installing the OpenText Package
30 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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 clickthe Number ranges button.
-
8/15/2019 VIM 6 0 - Instalation Guide
31/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 31
3. Click the button.
-
8/15/2019 VIM 6 0 - Instalation Guide
32/147
Chapter 3 Installing the OpenText Package
32 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
4. Click the button to add a new number range.
5. Enter required value and save it.
-
8/15/2019 VIM 6 0 - Instalation Guide
33/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 33
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.
-
8/15/2019 VIM 6 0 - Instalation Guide
34/147
Chapter 3 Installing the OpenText Package
34 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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 functionmodule, as shown above.
-
8/15/2019 VIM 6 0 - Instalation Guide
35/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 35
6. Click the Activate button in the tool bar to activate the function module, seehighlight in the screenshot above.
-
8/15/2019 VIM 6 0 - Instalation Guide
36/147
-
8/15/2019 VIM 6 0 - Instalation Guide
37/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 37
9. If you receive a message saying Program must be regenerated, as shownabove, 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 businessobject is generated and the function module is active.
-
8/15/2019 VIM 6 0 - Instalation Guide
38/147
Chapter 3 Installing the OpenText Package
38 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
3.2.7 Generating Business Object
In some case, the /OPT/B2081 business object might not be generated in the systemproperly. 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 logisticinvoice 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 theinvoice is blocked.
Note: OpenText advises against parking documents outside of VIM andstrongly recommends parking documents through the DP workflow. If parkingis 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), OpenTextrecommends 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
39/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 39
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 updatethe respective data.
The following event linkages can be turned on or off to enable or disable VIMworkflows:
Table 3-2: Event linkages for VIM workflows
Object type Event
Receiver type
Receiver function module
Check function module
Usage com-
ments
FIPP DELETED
TS00275270
SWW _ WI_CREATE_VIA_EVENT
—
Invoice Ap-proval (IAP)
FIPP POSTED
TS00275270
SWW _ WI_CREATE_VIA_EVENT
—
IAP
BUS2081 DELETED
TS00275270
SWW _ WI_CREATE_VIA_EVENT
—
IAP
BUS2081 POSTED
TS00275270
SWW _ WI_CREATE_VIA_EVENT
—
IAP
BUS2081 POSTED
WS00275264
/OPT/BL_PO_BLK_RECEIVER
—
Invoice Excep-tion (IE)
/OPT/FIPP ZWFI_CREATED
WS00275254
/OPT/BL_NPO_PRK_RECEIVER
/PTGWFI/PIR_F_CHECKFM
IE
/OPT/B2081 ZWFI_PARKED
WS00275260
/OPT/BL_PO_PRK_RECEIVER
/PTGWFI/PRK_M_CHECKFM
IE
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
-
8/15/2019 VIM 6 0 - Instalation Guide
40/147
Chapter 3 Installing the OpenText Package
40 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
Object type Event
Receiver type
Receiver function module
Check function module
Usage com-
ments
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) byclicking 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
41/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 41
4. Save your changes with a transport and move this transport to subsequentsystems.
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 onyour system. Otherwise, you can skip this section.
You maintain the maximum allowed tries and the time limits for extraction andvalidation, using table /OPT/VIM_RETRY. To maintain this table, use transactionSM30.
To set the extraction and validation retry count:
1. Execute the SM30 transaction.
-
8/15/2019 VIM 6 0 - Instalation Guide
42/147
-
8/15/2019 VIM 6 0 - Instalation Guide
43/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 43
Extraction7200
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
TextOpenText VIM
ASelect the check box.
4. Save your settings.
To maintain entries in the P/S modules:
1. Execute the FIBF transaction.
-
8/15/2019 VIM 6 0 - Instalation Guide
44/147
Chapter 3 Installing the OpenText Package
44 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
2. Follow the menu path Settings > P/S Modules > … of a customer.
3. Click the New Entries button.
4. Enter the details as shown in the following screenshot.
5. Save your settings.
To maintain entries in process modules:
1. Execute the FIBF transaction.
2. Follow the menu path Settings > Process Modules > … of a customer.
3. Click the New Entries button.
4. Enter the details as shown in the following screenshot.
-
8/15/2019 VIM 6 0 - Instalation Guide
45/147
-
8/15/2019 VIM 6 0 - Instalation Guide
46/147
Chapter 3 Installing the OpenText Package
46 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
2. Follow the menu path Utilities > Copy from Client.
3. Enter values in the required fields. Text Name and Target Name must be thesame.
Click .
-
8/15/2019 VIM 6 0 - Instalation Guide
47/147
3.2 Post Installation Activities
VIM060000-IGD-EN-3 Installation Guide 47
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.
-
8/15/2019 VIM 6 0 - Instalation Guide
48/147
-
8/15/2019 VIM 6 0 - Instalation Guide
49/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 49
Chapter 4
Verifying Installation
Make sure that the OpenText Vendor Invoice Management add-on is reflected in theinstalled components.
To verify the installation:
1. 1. From the SAP menu, open System > Status.
2. Click the button next to Component version.
-
8/15/2019 VIM 6 0 - Instalation Guide
50/147
Chapter 4 Verifying Installation
50 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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
-
8/15/2019 VIM 6 0 - Instalation Guide
51/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 51
Chapter 5
Upgrading
This chapter describes the upgrade procedure for both SAP upgrade and VIMupgrade.
5.1 Upgrading SAP
This section discusses the process to perform during an SAP upgrade with regardsto 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 automaticallyrecognizes that an SAP add-on is installed and requests the respective upgradepackage. This way the standard SAP upgrade procedure also updates the VIM add-ons to the relevant version.
Passwordcontrol
The OpenText Vendor Invoice Management package is protected with a specificpassword. During upgrade, this password is requested by the SAP Add-OnInstallation Tool (SAINT). For the SAP upgrade password, see “Password Control” on page 14.
Prerequisites
• Support Package Manager (transaction code SPAM) level 35
• Make sure the profile parameter transport/systemtype is set to CUSTOMER, notto SAP. If it is set to SAP, you will get object generation errors.
• Apply OSS note 1082597: Not enough business functions activated in SFW5; thisis used for Switch Frame Work for activating the PO based invoice parkinginfrastructure.
• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s ASABAP
• Apply OSS note 938147: OAWD: Object does not exist (OA 233)
• Apply OSS note 1568202: OpenText Vendor Invoice Management Solutions
• The following component must be installed:
Component SAP_BASISLevel: 700
• The following support package must be installed:
-
8/15/2019 VIM 6 0 - Instalation Guide
52/147
Chapter 5 Upgrading
52 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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 backupor take a snapshot of the SAP system.
To perform the SAP upgrade:
1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAPapplication server in the /usr/sap/trans folder. This is the parent folder of theDIR_EPS_ROOT folder.
Upgrade to ECC
6.0 from SAP
version
File Source path Target path
SAP ECC 5.0SAP R/3 4.7SAP R/3 4.6C
OTEXERP_UPGR_VIM604_700.
SAR
UPGR_ERP/DATA/ /usr/sap/trans/
EPS
Upgrade to ECC5.0 from SAP
version
File Source path Target path
SAP R/3 4.7SAP R/3 4.6C
OTEXERP_UPGR _VIM603_640.
SAR
UPGR_ERP/DATA/ /usr/sap/trans/
EPS
Upgrade to SAP
4.7 from SAP
version
File Source path Target path
SAP R/3 4.6C OTEXERP_UPGR _VIM602_620.
SAR
UPGR_ERP/DATA/ /usr/sap/trans/
EPS
2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with thefollowing command: SAPCAR -xvf .
The resulting PAT file is extracted to the EPS/in folder relative to the path of theSAPCAR file.
-
8/15/2019 VIM 6 0 - Instalation Guide
53/147
-
8/15/2019 VIM 6 0 - Instalation Guide
54/147
Chapter 5 Upgrading
54 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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 baselineconfiguration 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 errorreferencing 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-Insreferenced for the VIM namespace.
-
8/15/2019 VIM 6 0 - Instalation Guide
55/147
5.2 Upgrading VIM
VIM060000-IGD-EN-3 Installation Guide 55
If the two objects are green (see screenshot above), they are active andgenerated. This is okay and can be ignored.
Execute the COM_PRODUCT_UPGRADE report using transaction SE38. This report isoutlined 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 ProjectManager.
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 youhave done to VIM; you will have to migrate the customizing to VIM 6.0.
Passwordcontrol
The OpenText Vendor Invoice Management package is protected with a specificpassword. During VIM upgrade, this password is requested by the SAP Add-OnInstallation 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 invoiceparking infrastructure.
-
8/15/2019 VIM 6 0 - Instalation Guide
56/147
-
8/15/2019 VIM 6 0 - Instalation Guide
57/147
5.2 Upgrading VIM
VIM060000-IGD-EN-3 Installation Guide 57
OTEXVIM
520_620 or OTEXVIM 516_620
R/3 4.6C
Component SAP_BASISLevel: 46C
• The following support package must be installed:
SAPKB46C53
• Support Package Manager (transaction code SPAM) level 47
• The following add-on component must be installed:
OTEXVIM 520_46C or OTEXVIM 516_46C
Check VIM version numberMake sure that you already have VIM 5.1.6 or VIM 5.2 installed. To check theversion of VIM, open System > Status from the SAP menu and check theComponent
Version.
For more details, see “Verifying Installation” on page 49.
-
8/15/2019 VIM 6 0 - Instalation Guide
58/147
Chapter 5 Upgrading
58 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
Adjust SAINT tool settingsIn the settings of the SAINT tool, make sure that ABAP/Screen Generation isset 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; thatmeans, the entire VIM processes must not be performed.
2. Before you begin the update, perform a complete backup or take a snapshot ofthe 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
59/147
5.2 Upgrading VIM
VIM060000-IGD-EN-3 Installation Guide 59
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.
1. Copy the respective SAPCAR file (*.SAR) from the product CD to the target SAPapplication server in the /usr/sap/trans folder. This is the parent folder of theDIR_EPS_ROOT folder.
SAP system File Source path Target path
SAP ECC 6.0 OTEXVIM_UPGR_604_700.SAR
UPGR_VIM/DATA/ /usr/sap/trans/EPS
SAP ECC 5.0 OTEXVIM_UPGR_603_640.SAR
UPGR_VIM/DATA/ /usr/sap/trans/EPS
SAP R/3 4.7 OTEXVIM_UPGR_602_620.SAR
UPGR_VIM/DATA/ /usr/sap/trans/EPS
SAP R/3 4.6C OTEXVIM_UPGR_601_46C.SAR
UPGR_VIM/DATA/ /usr/sap/trans/EPS
2. Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with thefollowing command: SAPCAR -xvf .
The resulting PAT file is extracted to the EPS/in folder relative to the path of theSAPCAR file.
3. Carry out the import of the package as described in the respective SAPdocumentation.
4. Continue the Add On process by selecting Add On OTEXVIM.
Click the Continue button.
-
8/15/2019 VIM 6 0 - Instalation Guide
60/147
-
8/15/2019 VIM 6 0 - Instalation Guide
61/147
5.2 Upgrading VIM
VIM060000-IGD-EN-3 Installation Guide 61
7. Make sure that Start options is set to Start in dialog immediately forPreparation and Continue in Dialog immediately for Import 1, Import 2,and Clean Up.
Click the Continue button.A message is displayed, confirming the successful import.
8. Check in the SAINT tool if the package has been imported successfully with thenew release number. See “Verifying Installation” on page 49 for specific releasenumber.
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 describedin “Post Installation Activities” on page 19, except activating BC set.
Important
Do not activate BC Sets, as described in “Activating BusinessConfiguration Sets” on page 20. If you activate BC Sets, all theconfiguration data is overwritten with OpenText baseline configurationdata 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 ProjectManager.
With this information, we can keep our customer installation database up-to-date, which helps us providing faster technical support for you.
-
8/15/2019 VIM 6 0 - Instalation Guide
62/147
-
8/15/2019 VIM 6 0 - Instalation Guide
63/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 63
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 objectsare protected.
Can I repair the OpenText objects?It is not recommended to repair OpenText objects. [email protected] before making any repairs; OpenText might have alreadyissued a patch for the intended repair and the same functionality can be achievedby using appropriate user exits.
There is an error when starting the workflow.Make sure the standard task is defined as a general task.
-
8/15/2019 VIM 6 0 - Instalation Guide
64/147
-
8/15/2019 VIM 6 0 - Instalation Guide
65/147
Part 2
OpenText Approval Portal Installation
-
8/15/2019 VIM 6 0 - Instalation Guide
66/147
Part 2 OpenText Approval Portal Installation
66 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
This part describes the installation of the OpenText Approval Portal component. TheApproval Portal is designed to work within SAP Web Application Server (WAS) 7.0or SAP NetWeaver Portal (NWP) 7.0. The Approval Portal can be deployed as astandalone application residing on WAS only or as an application inside NWP usingAppIntegrator 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
67/147
-
8/15/2019 VIM 6 0 - Instalation Guide
68/147
Chapter 7 Preparing Installation
68 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
• OpenText recommends having both landscapes on the same operatingsystem.
WAS 7.0
(Win-dows)
Portal
7.0 (Win-dows)
WAS 7.0
(UNIX)
Portal
7.0(UNIX)
WAS CE 7.1SAP NetWeaver CE 7.1
Portal CE 7.1
WAS CE 7.2SAP NetWeaver CE 7.2
Portal CE 7.2
WAS 7.3SAP NetWeaver 7.3
Portal 7.3
SSLOpenText recommends implementing SSL (HTTPS) if security is a concern. BasicAuthentication in SPNego is using Base64 encryption which can be easily decrypted.See http://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspx for furtherinformation.
Sizingrequirements
Standard sizing requirements for SAP WAS or NWP 7.0 apply.
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 theCPIC user.
User type
Communication Data (CPIC)
ProfileCreate a profile with the following authorization objects and add it to the CPICuser:
Object: S_RFC
ActivityExecute (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_TYPEFUGR (Function Group)
http://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspxhttp://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspx
-
8/15/2019 VIM 6 0 - Instalation Guide
69/147
7.2 Installation Components
VIM060000-IGD-EN-3 Installation Guide 69
Object: S_CPIC
ActivityAccept, Initialize (37 and 51)
Name of an ABAP/4 FORM routineCPIC
Symbolic destination*
If you wish to narrow this down, examine table TXCOM and choose entryunder the SDEST field that represents the destination of the system you arecommunicating with.
Program Names with Search Help/ORS/*, /OPT/*, /PTGWFI/*
Object: S_DATASET (Authorization for file access)
ActivityRead, 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 toassign additional roles. See the Archive Server Installation manual.
Example:
OpenText Archive Server provides the following profiles that need to beassigned to the CPIC user to access images:
• S_ AL_ ADMLO (Display ArchiveLink administrator)
• S_ AL_ ADMDE (Delete ArchiveLink administrator)
DefaultsDecimal 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
-
8/15/2019 VIM 6 0 - Instalation Guide
70/147
Chapter 7 Preparing Installation
70 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
7.3 System Architecture
This section explains the overall system architecture of the Approval Portal. There isone 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 integratedauthentication
• as an application inside NWP using AppIntegrator iView
The following diagrams show the architecture for each scenario:
-
8/15/2019 VIM 6 0 - Instalation Guide
71/147
-
8/15/2019 VIM 6 0 - Instalation Guide
72/147
Chapter 7 Preparing Installation
72 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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 OpenTextApproval Portal:
Standalone J2EE application residing on WAS only utilizing integratedauthentication
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 integratedauthentication
SAP GUI Logon ID required. Dual Stack forces to use SAP user managementbased on ABAP Stack.
-
8/15/2019 VIM 6 0 - Instalation Guide
73/147
-
8/15/2019 VIM 6 0 - Instalation Guide
74/147
-
8/15/2019 VIM 6 0 - Instalation Guide
75/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 75
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 withadministrator 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 folderusr/sap//SYS/global/opentext/invoiceCfg. This is thedefault location for putting the application configuration file. If youdeploy to another location, you will have to manually add a startupparameter in the Config Tool to tell the application where to look for theconfiguration files. This will also require restarting the WAS. See step 2on page 76 for details.
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 in the following.
The 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.propertiescontaining 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
-
8/15/2019 VIM 6 0 - Instalation Guide
76/147
Chapter 8 Installing the Approval Portal
76 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
Lang_EN.properties
containing all the text for the English language resource
Lang_ES.properties
containing all the text for the Spanish language resourceLang_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 therelease 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 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 folderusr/sap//SYS/global/opentext/invoiceCfg.
If you deploy to another location thanusr/sap//SYS/global/opentext/invoiceCfg, you must add a startup
-
8/15/2019 VIM 6 0 - Instalation Guide
77/147
8.2 Configuring the Administrator Role
VIM060000-IGD-EN-3 Installation Guide 77
parameter in the Config Tool, manually, to tell the application where to look forthe configuration files.
You find the Config Tool in the following directory:
usr/sap///j2ee/configtool.Notes:
• SID is the system ID of the WAS (example O15).
• INSTANCE_NAME is the WAS instance in the format of JCxx, wherexx 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=.
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 folder contains applicationspecific information.
8.2 Configuring the Administrator Role
Important
This section is only needed if you are installing as a standalone J2EEapplication residing on WAS only utilizing integrated authentication.
-
8/15/2019 VIM 6 0 - Instalation Guide
78/147
Chapter 8 Installing the Approval Portal
78 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
This section describes the installation activities to assign the administrator role tothe user for the Approval Portal application. As the Administrator, you must loginto the Administrator page to perform some application configuration and toperform 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 thedomain user through WAS Visual Administrator.
You must perform this configuration before deploying the .sca or .sda, to ensurethat 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
79/147
VIM060000-IGD-EN-3 Installation Guide 79
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.
-
8/15/2019 VIM 6 0 - Instalation Guide
80/147
Chapter 8 Installing the Approval Portal
80 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
3. In the Choose Users or Groups dialog box, type the domain user to whom youwant 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://:/vimportal/admin.
-
8/15/2019 VIM 6 0 - Instalation Guide
81/147
8.3 Deploying the Software Component Archive
VIM060000-IGD-EN-3 Installation Guide 81
If you see a screen similar to the one above, you have configured theadministrator role successfully.
8.3 Deploying the Software Component Archive
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 DeploymentManager (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 withadministrator rights.
2. Make sure the .sca (Software Component Archive) or .sda (SoftwareDeployment Archive) file is on a medium, for example, a CD drive, or a shareddirectory, accessible from the host server.
3. Connect to the SAP Software Deployment Manager (SDM):
You find SDM in the following directory:usr/sap///SDM/program.
Notes:
• SID is the system ID of the WAS (example O15).
-
8/15/2019 VIM 6 0 - Instalation Guide
82/147
Chapter 8 Installing the Approval Portal
82 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
• INSTANCE_NAME is the WAS instance in the format of JCxx, wherexx is the instance number (example JC00).
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 orIM_ APPROVAL_PORTAL6_0.sda file.
Note: The filename might be different.
-
8/15/2019 VIM 6 0 - Instalation Guide
83/147
8.3 Deploying the Software Component Archive
VIM060000-IGD-EN-3 Installation Guide 83
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 followingprocedure:
To check correct deployment of the Approval Portal:
1. In the SDM, click the SDM Repository tab and expand SAPJ2EEEngine.
-
8/15/2019 VIM 6 0 - Instalation Guide
84/147
Chapter 8 Installing the Approval Portal
84 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
IM_ APPROVAL_PORTAL should be displayed under SAPJ2EEEngine. The versionnumber 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://:/vimportal.
You will see OpenText Approval error messages. This is correct as you have notdone 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
85/147
8.3 Deploying the Software Component Archive
VIM060000-IGD-EN-3 Installation Guide 85
Note: If opentext.com/IM_ APPROVAL_PORTAL is not displayed, usethis Installation Guide to check if anything is wrong or redo theinstallation.
8.3.4 Optional: Starting the Approval Portal J2EE Application
Manually
By deploying through SDM, the Approval Portal J2EE application will startautomatically. If the Approval Portal J2EE application doesn't, you can start itmanually.
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.
-
8/15/2019 VIM 6 0 - Instalation Guide
86/147
-
8/15/2019 VIM 6 0 - Instalation Guide
87/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 87
Chapter 9
Configuring SAP NetWeaver Portal Components
If you are deploying the Approval Portal on WAS and the users are accessing theapplication through SAP NetWeaver Portal, you must configure the SAPNetWeaver 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. Tomake the application available for SAP NetWeaver Portal users, you have toperform 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 ofcreating 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
88/147
Chapter 9 Configuring SAP NetWeaver Portal Components
88 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
3. Right-click on the new folder and select New > iView.
-
8/15/2019 VIM 6 0 - Instalation Guide
89/147
9.1 Creating AppIntegrator IViews for Users
VIM060000-IGD-EN-3 Installation Guide 89
4. In the iView wizard, click Portal Component – create an iView from a portalcomponent ... and click Next.
5. In Step 1: Portal Archive Selection, click com.sap.portal.appintegrator.sap and
click Next.
-
8/15/2019 VIM 6 0 - Instalation Guide
90/147
Chapter 9 Configuring SAP NetWeaver Portal Components
90 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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
-
8/15/2019 VIM 6 0 - Instalation Guide
91/147
9.1 Creating AppIntegrator IViews for Users
VIM060000-IGD-EN-3 Installation Guide 91
• 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
92/147
Chapter 9 Configuring SAP NetWeaver Portal Components
92 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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=
-
8/15/2019 VIM 6 0 - Instalation Guide
93/147
-
8/15/2019 VIM 6 0 - Instalation Guide
94/147
Chapter 9 Configuring SAP NetWeaver Portal Components
94 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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 mustsearch by giving Role ID Prefix and Role Name when assigning the roleto the user.
4. Click Next.
-
8/15/2019 VIM 6 0 - Instalation Guide
95/147
9.2 Creating Roles for Users
VIM060000-IGD-EN-3 Installation Guide 95
5. Click Finish.
6. Click Open the object for editing and click OK.
-
8/15/2019 VIM 6 0 - Instalation Guide
96/147
Chapter 9 Configuring SAP NetWeaver Portal Components
96 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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 > DeltaLink.
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 theroles to the SAP NetWeaver Portal users.
To assign roles to SAP NetWeaver Portal users:
1. In the SAP NetWeaver Portal, click User Administration > IdentityManagement.
-
8/15/2019 VIM 6 0 - Instalation Guide
97/147
9.4 Configuring IViews and Roles for the Administrator
VIM060000-IGD-EN-3 Installation Guide 97
2. In the Search Criteria, enter the users or groups you want to assign to the newrole (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 therole.
The only difference from the user configuration is the URL template:
http://$host$:$port$/vimportal/admin?urlView=Y&PORTALUSER=
-
8/15/2019 VIM 6 0 - Instalation Guide
98/147
Chapter 9 Configuring SAP NetWeaver Portal Components
98 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
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, assignit to the appropriate administrators, as described in “Assigning Roles to SAPNetWeaver Portal Users” on page 96.
When you, as the administrator, navigate to the Approval Admin iView, it will looklike the following screenshot:
You have now finished the installation and configuration of the OpenText ApprovalPortal.
-
8/15/2019 VIM 6 0 - Instalation Guide
99/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 99
Chapter 10
Applying a New Patch
Note: Unlike the VIM SAP component, the Approval Portal is a build and hasno dependencies of previous patches or support packages. You can uninstallthe previous version and directly install the newest version without applyingthe patches in between. However, the patch or build needs to match to the VIMSAP component. For example, Approval Portal SP2 does not work with VIMSAP components SP1 or SP3, it will only work with SP2.
New .sca file or .sda fileFollow the steps to undeploy the .sca or .sda file in “Uninstalling Using
Software Deployment Manager” on page 105, and then follow the steps todeploy the .sca file or .sda file in “Deploying the .sca File or .sda File” onpage 82.
New .properties filesExtract the new .properties files from the media to and perform the Reinitialize Application task. See section 23 "Administeringand Troubleshooting the Approval Portal" in OpenText Vendor Invoice Manage-ment - Administration Guide (VIM-AGD) for more details.
-
8/15/2019 VIM 6 0 - Instalation Guide
100/147
-
8/15/2019 VIM 6 0 - Instalation Guide
101/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 101
Chapter 11
Upgrading the Approval Portal from PreviousVersions
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 isbest 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
102/147
-
8/15/2019 VIM 6 0 - Instalation Guide
103/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 103
Chapter 12
Troubleshooting
For information on troubleshooting the Approval Portal, see section 23.14"Troubleshooting" in OpenText Vendor Invoice Management - Administration Guide(VIM-AGD).
-
8/15/2019 VIM 6 0 - Instalation Guide
104/147
-
8/15/2019 VIM 6 0 - Instalation Guide
105/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 105
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 DeploymentManager
This section describes how to uninstall the .epa and .ear files from the SAPSoftware 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///SDM/program.
Notes:• SID is the system ID of the WAS (example O15).
• INSTANCE_NAME is the WAS instance in the format of JCxx, wherexx is the instance number (example JC00).
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 touse 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.
-
8/15/2019 VIM 6 0 - Instalation Guide
106/147
Chapter 13 Uninstalling the Approval Portal
106 OpenText Vendor Invoice Management VIM060000-IGD-EN-3
6. To finish the undeployment, click Confirm.
opentext.com\IM_ APPROVAL_PORTAL should no longer appear in the VisualAdministrator.
13.2 Removing SAP NetWeaver Portal Components
This section describes how to remove iViews, pages, worksets and roles from theSAP 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 theproperties files. The default folder name isusr/sap//SYS/global/opentext/invoiceCfg, where is the systemID of the Web Application Server (WAS). See “Preparing the Installation” onpage 75 for details on the properties files.
-
8/15/2019 VIM 6 0 - Instalation Guide
107/147
13.4 Optional: Removing the Startup Parameter in the Config Tool
VIM060000-IGD-EN-3 Installation Guide 107
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 theConfig Tool, see step 2 on page 76 in “Preparing the Installation” on page 75.
Removing the startup parameter, using the J2EE Config Tool, finishes theuninstallation process.
To remove the startup parameter:
1. Invoke the J2EE Config Tool:
You find the Config Tool in the following directory:usr/sap///j2ee/configtool.
Notes:
• SID is the system ID of the WAS (example O15).
• INSTANCE_NAME is the WAS instance in the format of JCxx, wherexx is the instance number (example JC00).
The script file is:
• configtool.bat for Windows hosts
• configtool.sh for Unix hosts
2. Remove the startup parameter:
-Dcom.opentext.vim.portal.invoiceCfg=
Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/opentext/invoiceCfg
3. Save your settings.
4. Restart the WAS to remove the startup parameter.
The uninstallation is now completed.
-
8/15/2019 VIM 6 0 - Instalation Guide
108/147
-
8/15/2019 VIM 6 0 - Instalation Guide
109/147
Part 3
-
8/15/2019 VIM 6 0 - Instalation Guide
110/147
Vendor Invoice Management CRM Shared
Service Framework (SSF) Component
Installation
-
8/15/2019 VIM 6 0 - Instalation Guide
111/147
13.4 Optional: Removing the Startup Parameter in the Config Tool
VIM060000-IGD-EN-3 Installation Guide 111
This part describes the installation of the Vendor Invoice Management CRM SharedService Framework (SSF) component:.
-
8/15/2019 VIM 6 0 - Instalation Guide
112/147
-
8/15/2019 VIM 6 0 - Instalation Guide
113/147
VIM060000-IGD-EN-3 OpenText Vendor Invoice Management 113
Chapter 14
Preparing Installa