Professional Documents
Culture Documents
SAP Solutions
Installation Guide
VIM070000-IGD-EN-6
OpenText Vendor Invoice Management for SAP Solutions
Installation Guide
VIM070000-IGD-EN-6
Rev.: 18. July 2014
This documentation has been created for software version 7.0.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text SA
Tel: 35 2 264566 1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: http://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2014 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not
exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names
mentioned herein are property of Open Text SA or other respective owners.
Disclaimer
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
Part 1 About Vendor Invoice Management 7
6 Upgrading ................................................................................. 49
6.1 Upgrade Overview .......................................................................... 49
6.2 Handling Workflow Container Inconsistencies ................................... 51
6.3 Upgrading SAP ERP ....................................................................... 52
6.4 Upgrading VIM ................................................................................ 56
6.5 Post Installation Activities After an Upgrade ...................................... 62
7 Troubleshooting ...................................................................... 67
7.1 FAQs ............................................................................................. 67
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide iii
VIM070000-IGD-EN-6
Table of Contents
20 Installing Web Viewer for the Mobile Approval Portal ....... 157
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 information about all OpenText products resold by SAP (including VIM
and ICC), check SAP Marketplace Note 1791874: SAP Products by OpenText
- Software and Support Lifecycle. This note provides detailed information
about software life cycle, access to Support Packages, access to latest
documentation, language packages, and other patches, as well as Support
ticket handling.
VIM features the optional component Web Invoice Approval. The target audience for
this component includes:
• Site administrators
• Database administrators
• Network administrators
This part describes the installation of the SAP ERP component of Vendor Invoice
Management (VIM).
2.1 General
Caution
The following information is very important. Read the table carefully
before the installation.
Important
Make sure the SAP workflow system is configured to run workflows. To
check this, run the SWU3 transaction. Make sure most of the relevant items are
configured correctly, indicated by the icon. It is very important that, in the
Maintain Runtime Environment node, Configure RFC destination has the
icon.
Note: Check for and download the available latest support packs and hot fixes
at the OpenText Knowledge Center: https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/10151605.
The following table shows the passwords for VIM installation, SAP ERP upgrade
and VIM upgrade.
The following components must be installed for SAP ECC 6.0 up to EHP7:
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.
Some steps of the installation and upgrade procedures make use of transports. These
transports have been created in the OpenText development or packaging systems.
These systems do not have the same components and component versions as your
systems. So, when the transport is imported, you must select the Ignore invalid
component version check box.
This chapter describes the installation of the Basis package of Vendor Invoice
Management (VIM) on an SAP ERP system. Read also “Preparing Installation“
on page 13 with general information on installation in an SAP environment.
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).
3. Carry out the import of the package as described in the respective SAP
documentation.
4. To finish installation, install the most recent VIM 7.0 Support Package (SP). You
find the SPs in the Knowledge Center: https://knowledge.opentext.com/
knowledge/cs.dll/Open/10151605. For further information, see the Release Notes
of the respective SP.
Notes
• For every client, you must activate new BC Sets after installing VIM 7.0.
• You need the appropriate security authorization to run some of the
transactions.
• Depending on the SAP version, the following screens might look different on
your system.
1. To access the Business Configuration Sets: Activation screen, run the SCPR20
transaction.
From the Utilities menu, click User Settings.
• Chinese
• Dutch
• English
• French
• German
• Hungarian
• Italian
• Japanese
• Portuguese
• Romanian
• Russian
• Spanish
• Czech
• Polish
• Turkish
To select your applicable languages, select the respective check box in the
Manual Selection column.
To activate BC Sets:
1. To access the Business Configuration Sets: Activation screen, run the SCPR20
transaction.
Note: If you are prompted to create a new transport, follow your standard
change request process for tracking changes.
Tip: You can ignore any warnings during the activation. If you get an
error during activation of a BC set, then activate it again. In many cases the
error will disappear. You can ignore activation errors like No data found
for writing activation links for object <xxx>.
2. In the Task type field, select Standard task, enter the task ID and click the
button.
3. In the Standard Task: Display screen, select Additional data > Agent
assignment > Maintain.
4. In the Standard task: Maintain Agent Assignment screen, select the name of
the assignment and then click the Attributes button.
5. In the Task popup, select General Task and click the Transfer button.
The standard task is now configured as a General Task.
If you are prompted to create a new transport, continue with the next step.
If you are asked if you want to Transfer missing elements from the object
method?, click No.
7. Repeat the procedure for all the tasks mentioned in Table 3-1 on page 22.
The VIM dashboard and the OpenText Document Processing document services are
accessible from the SAP Invoice function.
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.
Object Description
/PTGWFI/RI CP Document
/OPT/DOCID Document Processing
/ORS/STACK Invoice Approval
/ORS/USRMP Invoice Approval Usermap
/OPT/REGID Incoming Document Handling (IDH) framework
Important
All the number ranges intervals must be 01.
2. Enter the object name from the table above, for example /OPT/DOCID and click
the Number ranges button.
SAP events are trigger points for VIM workflows. For example, when a logistic
invoice is posted, SAP ERP generates the event POSTED from the business object
BUS2081. The event is linked to trigger the VIM workflow solution for blocked
invoices if the invoice is blocked.
With VIM 6.0 and higher, event linkages are no longer created automatically. You
must add the event linkages manually.
In case of not properly raised parking events, perform the following actions:
2. To schedule the Event Queue Job, run the SWEQADM transaction. You can
set the frequency according to your requirement how often to update the
respective data.
The following event linkages can be turned on or off to enable or disable VIM
workflows:
TS00275270 —
BUS2081 DELETED SWW_WI_CREATE_VIA_EVENT IAP
TS00275270 —
TS00275270 —
BUS2081 POSTED /OPT/BL_PO_BLK_RECEIVER Invoice
Exception (IE)
WS00275264 /OPT/BL_PO_CHECK_ROLL_OUT
BUS2081 POSTED /OPT/BL_PO_BLK_RECEIVER IE
TS00275264 /OPT/BL_PO_CHECK_ROLL_OUT
/OPT/FIPP ZWFI_CREATE /OPT/BL_NPO_PRK_RECEIVER IE
D
/PTGWFI/PIR_F_CHECKFM
WS00275254
/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
— — May be used in
special
situation.
Should be
inactive in
standard
configuration.
BUS2081 RELEASED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
BUS2081 CANCELLED /OPT/VIM_RPT_PO_INV_RECEIVER VAN
— —
/ORS/INVAP POSTED /OPT/AAFS_POST_RECEIVER Posted
Approval
— —
Note: There is a dependency between two entries for Object Type BUS2081 and
Event POSTED, the one with Receiver Type WS00275264, and the one with an
empty Receiver Type.
In transaction SWETYPV, make sure that only one of these event linkages is
activated.
• If you use your own blocking workflow, activate only the event linkage with
empty Receiver Type. This event linkage ensures that VAN will be correctly
updated.
• If you use the standard blocking workflow template, activate only the event
linkage with Receiver Type WS00275264. This event linkage updates VAN
with the same function module as the other event linkage but it also starts
the blocking workflow.
1. To open the Event Type Linkages screen, run the SWE2 transaction.
2. Create the event linkage entries shown in “Event linkages for VIM workflows”
on page 30 (if not already existing) by clicking the New Entries button.
To edit an existing event linkage entry, double-click the entry.
3. To enable the workflow, select the Type linkage active check box.
To disable the workflow, clear the check box.
4. Save your changes with a transport and move this transport to subsequent
systems.
Note: Repeat the procedure for all event linkage entries shown in “Event
linkages for VIM workflows” on page 30.
4. Enter values in the required fields. In Form Name, enter SYSTEM, and in Target
Form, enter /ORS/SAPSCRIPT.
5. To submit, click .
If you are asked for a package, enter /ORS/000007.
The standard text is client dependent and should be copied from client 000 to all
required clients. Perform the following steps to do a client copy of the following
standard text in the required languages:
• /OPT/VIM_DP_SRM_PRICE_HEADER
• /OPT/VIM_DP_SRM_QTY_FOOTER
• /OPT/VIM_DP_SRM_QTY_HEADER
• /OPT/VIM_DP_SRM_QTY_URL_HEAD
Note: To copy the text in all languages at once, you can use an asterisk in
the Language field.
3. Enter values in the required fields. Text Name and Target Name must be the
same.
Click .
4. If a dialog box like the following opens, click Yes.
6. Repeat the steps for all standard text shown in the list above.
1. Run the SU01 transaction and open the user WF-BATCH in edit mode.
Note: Use O like Oscar in FO3. Note that there is a blank in front of the
parameter value 2. The 2 is the second character.
OpenText recommends setting the layout /IDH as default layout for the IDH Admin
Tool (transaction /OPT/VIM_7AX8; report /OPT/VIM_ICC_ADMIN_TOOL).
Cumulative Beginning with VIM 7.0 SP2, VIM provides a cumulative language pack with every
language pack SP. You need this language pack, if you did not install the initial language pack of
the VIM version along with the installation package. You can obtain the cumulative
language pack in the Knowledge Center in the folder of the respective SP.
You can import the cumulative language pack after the respective SP is installed.
The initial language pack of the VIM version is not required. To import the language
pack, use the SMLT transaction. You can import the language pack multiple times for
several languages.
Translation VIM provides a translation guide that describes the various aspects of translating
Guide VIM into new languages. In addition, the translation guide contains a section
explaining what to do if you want to use the available SAP tools “Secondary
Language” and “Language Supplementation” instead of translating into a new
language. The translation guide is available in the Knowledge Center: https://
knowledge.opentext.com/knowledge/llisapi.dll/Properties/46423475
Make sure that the OpenText Vendor Invoice Management add-on is reflected in the
installed components.
In the System: Component information dialog, you should see the OTEXVIM
add-on component installed, with Release number 700.
This chapter describes the installation of a Support Package (SP) for VIM.
Inconsistent data in workflow containers often results in short dumps. They happen
when, after an SP installation, a user tries to open a work item that was created
before the SP installation.
The only VIM database table that is currently known to cause these problems is
table /OPT/VIM_1HEAD. OpenText recommends that you create a copy (for example
with the name ZZZ1HEAD) in transaction SE11. It is important that the table copy will
not reference any include or append structures. You can achieve this by performing
the following steps:
To expand includes:
3. Set the pointer on each include line (.INCLUDE) that is still displayed, and, on
the Edit menu, click Include > Copy Components.
Normally, all fields will be expanded at once. After this, you can activate the
table.
6. You are asked to confirm if you want to upload the OCS Package for the VIM
SP. Click Yes.
10. Click the checkmark button to confirm the queue selection. The Release may be
different in your SAP implementation.
You now see the package name in the queue. The Status is yellow and reads
Next action: Import queue.
12. Click the Always radio button in the section ABAP/Screen Generation. Then
click the confirmation checkmark.
13. In the Extras menu, click Ignore generation errors.
The Support Package may contain Data Dictionary changes that require
database table conversions or other additional activities. Without performing
these additional activities, the generation will result in errors that must be
ignored first.
14. You are now ready to import. Click the Import Truck button to begin.
15. At this point, you can choose the Start Options, which control whether each
phase executes in a dialog process or a background process. Make your
selections and start by clicking the confirmation checkmark button.
The import starts running. If you chose to run in dialog, you see the process
steps running at the bottom of the screen. Otherwise you need to monitor the
log.
When the import has completed, you see a message Queue <queue name>
imported successfully (ECC 6.0) in the dialog box.
17. Now check the import logs for errors, code 8 or above. To display the logs, click
the Import Log button.
18. Verify that you do not have any error codes eight (8) or above. Warning codes
of four (4) are acceptable.
Note: Some objects can display generation errors. For a list of these
objects, see the Release Notes for the SP.
19. When you have finished viewing, click the Back button.
20. To resolve the domain and tables generation errors (see Step 13 on page 45), the
table data must be converted with the SAP Database Utility (transaction SE14).
Open this transaction in a new window and perform the conversion for each of
the tables listed in the Release Notes for the SP.
22. Select Background and Save data, and click Activate and adjust database. You
can set the parameters of the proposed background job to immediate execution.
As soon as the jobs created this way for all tables are finished, activate the
domain /OPT/VIM_TAXRATE in the SE11 transaction. There should be no errors
in the activation log.
Note: You must perform the database adjustment in each of the systems
where the SP is installed or transported, including the production system.
24. To confirm the queue, click the checkmark icon in the application toolbar.
The SPAM status changes to a green light and the queue is cleared. The
following message will appear: You have applied OTEXVIM <patch number>
successfully.
This chapter describes the upgrade procedure for both SAP ERP upgrade and VIM
upgrade.
Terminology
Former versions of SAP (4.6C and 4.7) are no SAP ERP versions, but SAP R/3
versions. Therefore, the wording in many locations would have to be “SAP
ERP or R/3” instead of “SAP ERP”. To make reading more convenient in this
chapter, also the R/3 versions (4.6C and 4.7) are called “SAP ERP”.
The following 2-step upgrades have a VIM upgrade to VIM 6.0 SP1 as a first step.
Perform this intermediate step completely. Activate all BC sets mentioned in the
Upgrade Guide and execute all the conversion and migration tools according to the
Upgrade Guide.
Table 6-3: VIM upgrades in 2 steps for SAP version ERP 6.0
Notes
• If possible, finish the processing of all currently open DP documents before
upgrading the production system. Do not create new DP documents during
the upgrade procedure.
• For more information about upgrading, see the document “FAQ on Upgrade
to 7.0”, available in the Knowledge Center: https://knowledge.opentext.com/
knowledge/cs.dll/Properties/38482369
Inconsistent data in workflow containers often results in short dumps. They happen
when, after an upgrade, a user tries to open a work item that was created before the
upgrade.
The only VIM database table that is currently known to cause these problems is
table /OPT/VIM_1HEAD. OpenText recommends that you create a copy (for example
with the name ZZZ1HEAD) in transaction SE11. It is important that the table copy will
not reference any include or append structures. You can achieve this by performing
the following steps:
To expand includes:
3. Set the pointer on each include line (.INCLUDE) that is still displayed, and, on
the Edit menu, click Include > Copy Components.
Normally, all fields will be expanded at once. After this, you can activate the
table.
When you have to upgrade your SAP ERP system and you already installed VIM
using packages, you have to use the specific VIM SAP ERP upgrade packages.
When you upgrade an SAP release to a higher release, the system automatically
recognizes that an SAP add-on is installed and requests the respective upgrade
package. This way the standard SAP ERP upgrade procedure also updates the VIM
add-ons to the relevant version.
Password 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 ERP 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, 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
• For a list of available software components, check OSS note 1791715: SAP Invoice
Management by OpenText 7.0
• The following components must be installed for SAP ECC 6.0 up to EHP7:
• OTEXVIM 601_46C
3. Save values from PO number lists and delivery note (DN) number lists in
your /OPT/VIM_1HEAD table.
If you want to keep the values for these fields, where the PO numbers and DN
numbers for a DP document were stored as a comma-separated list, you have to
use a migration program. The migration program is part of VIM 6.0 SP6 and
VIM 5.2 SP11.
If you are on a lower version, you have to install transport D89K904627 (for SAP
4.6C: D81K903267). You find this transport on your installation CD.
Then run report /OPT/VIM_MIGRATE_PO_DN_LISTS to store PO_LIST and
DN_LIST values in the new table /OPT/VIM_1PO_DN.
You get a log with the count of resulting entries in the table /OPT/VIM_1PO_DN.
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.
5. To include the OTEXVIM exchange package, select Upgrade with SAINT package.
Click the OK button to continue.
Important
In case of an SAP ERP upgrade, do not activate BC Sets, as described in
“Activating Business Configuration Sets” on page 18. If you activate BC
Sets, all the configuration data is overwritten with OpenText baseline
configuration data and all custom configuration changes are lost.
At the end of the upgrade you may see the following screen.
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"
If the two objects are green (see screenshot above), they are active and
generated. This is okay and can be ignored.
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.
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.
• Apply OSS note 822380: Problems w/ add-on inst/upgrade to SAP NW 7.0s
AS ABAP
• Apply OSS note 1462364: Dependent structure has inconsistent runtime
object after mass activation. This is specific to SAP ECC 6.0 system, up to
EHP5.
• For a list of available software components, check OSS note 1791715: SAP
Invoice Management by OpenText 7.0
• The following components must be installed:
ECC 6.0
Component SAP_BASIS
Level: 700
• The following components must be installed for SAP ECC 6.0 up to EHP7:
VIM version
Upgrade to VIM 7.0 is supported with minimal versions of VIM 5.2 SP6 or VIM
6.0 SP1. If you have a lower support package level within VIM 5.2 or VIM 6.0,
you must upgrade to the required SP level first, and activate the BC sets
delivered with the SPs.
Direct upgrade from VIM 5.1.6 is not supported. You can upgrade from VIM
5.1.6 to VIM 6.0 SP1 and then go on to VIM 7.0.
To check the version of VIM, open System > Status from the SAP menu and
check the Component Version.
For more details, see “Verifying Installation“ on page 39. The following
screenshots show system component information with the required minimum
SP levels of OTEXVIM.
1. Inform all users about the scheduled VIM downtime as early as possible.
Users must not perform any actions on the Accounts Payable module; that
means, the entire VIM processes must not be performed.
2. Before you begin the update, perform a complete backup or take a snapshot of
the SAP ERP system.
3. Make sure the namespaces /OPT/, /ORS/, and /PTGWFI/ are modifiable:
4. Save values from PO number lists and delivery note (DN) number lists in
your /OPT/VIM_1HEAD table.
If you want to keep the values for these fields, where the PO numbers and DN
numbers for a DP document were stored as a comma-separated list, you have to
use a migration program. The migration program is part of VIM 6.0 SP6 and
VIM 5.2 SP11.
If you are on a lower version, you have to install transport D89K904627. You
find this transport on your installation CD.
Then run report /OPT/VIM_MIGRATE_PO_DN_LISTS to store PO_LIST and
DN_LIST values in the new table /OPT/VIM_1PO_DN.
You get a log with the count of resulting entries in the table /OPT/VIM_1PO_DN.
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 SAP
application server in the \usr\sap\trans folder. This is the parent folder of the
DIR_EPS_ROOT folder.
3. Carry out the import of the package as described in the respective SAP
documentation.
6. When you are prompted for the password, enter the password as provided in
“Password Control” on page 14.
Click the Continue button.
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.
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 the
new release number. See “Verifying Installation“ on page 39 for specific release
number.
1. If you need login languages other than English and German, install the
language packs for the languages you need. For more information, see
“Language Packs” on page 38.
2. Install the most recent VIM 7.0 Support Package (SP). You find the SPs in the
Knowledge Center: https://knowledge.opentext.com/knowledge/cs.dll/Open/
10151605. For further information, see the Release Notes of the respective SP.
3. After the upgrade, perform/verify all the post installation activities as described
in “Post Installation Activities After an Upgrade” on page 62.
Important
Do not activate the BC Sets for first installation, as described in
“Activating Business Configuration Sets” on page 18. If you activate
these BC Sets, all the configuration data is overwritten with OpenText
baseline configuration data and all custom configuration changes are
lost.
4. Test the entire VIM process like for a new VIM installation.
5. When you have successfully completed all tests, inform the OpenText Project
Manager.
With this information, we can keep our customer installation database up-to-
date, which helps us providing faster technical support for you.
The business configuration sets (BC Sets) for post installation activities after an
upgrade are the following:
/OTEXVIM/VIM70_BASELINE_52_60_D
Activate this BC Set if your source system for the upgrade is VIM 5.2. If you get
an activation error, ignore it.
/OTEXVIM/VIM70_BASELINE_LOWSP_D
Activate this BC Set if your source system for the upgrade is lower than VIM 5.2
SP8 or VIM 6.0 SP3 respectively. If you get an activation error, ignore it.
/OTEXVIM/VIM70_BASELINE_NEWFOR70
Activate this BC Set in any case. You should not have activation errors here. If
you have activation errors, repeat the activation. If you still have activation
errors, you have to find out the reason. You can ignore activation errors like No
data found for writing activation links for object <xxx>.
In the BF32 transaction, the 6 VIM events should be configured; see the following
screenshot.
Check with the BF34 transaction, if these events occur in the customer section. If yes,
remove them.
In the BF42 transaction, the VIM process RWBAPI01 should be configured; see the
following screenshot.
Check with the BF44 transaction, if this process occurs in the customer section. If yes,
remove it.
OpenText recommends setting the layout /IDH as default layout for the IDH Admin
Tool (transaction /OPT/VIM_7AX8; report /OPT/VIM_ICC_ADMIN_TOOL).
After an upgrade, the VORGANG field is empty for all invoices. To make its value
consistent with the CREDIT_MEMO field, run the program /
OPT/VIM_UPDATE_VORGANG_FOR_CM.
The program will set the VORGANG field to 2 for every document in the DP workflow
with CREDIT_MEMO flag selected.
This is not designed as a user process option but it still occurs in some process types
and must be removed.
7.1 FAQs
The following FAQs cover basic troubleshooting information.
This part describes the installation and post installation activities needed for the
“Key Performance Indicator” Dashboard KPI Dashboard. The KPI Dashboard is a
tool for managers showing VIM related process data at a glance in graphical charts.
For further information, see section 25 “KPI Dashboard” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
Notes
• The KPI Dashboard is an optional component.
• If you are not using the KPI Dashboard, you can skip this part.
The KPI Dashboard is installed together with the VIM Basis package.
The following activities are needed to configure the KPI Dashboard on your system.
Prerequisites
There are specific OpenText name spaces that have to be modifiable in order to
change the service settings. So first check with transaction SE03
Navigate to Transport Organizer Tool > Administration > Set System Change
Option
Make sure, the Open Text Name space / Prefix /OPT and /ORS are set to Modifiable.
After you have finished the customizing of services, change back the settings.
1. To activate the Web Dynpro service on the SAP ERP system, run the SICF
transaction.
Error Handling
You can customize a few default pages for error handling in the Web Dynpro
service.
Error pages are shown for defined reasons; for example, if the timeout is reached for
the web session. The default setting is to show SAP standard error pages.
You can change these settings for the following use cases:
• Logon Errors
• Application Errors
• Logoff Page
• Not Accessible
Do not change the service settings described in “Activating the SAP Web Dynpro
Service” on page 73. Make sure that the SSL settings are not activated in the Logon
Data tab.
A System Object is needed to integrate the KPI Dashboard in the SAP NetWeaver
Portal. The System Object is a set of connection properties to represent an external or
SAP system (SAP R3, CRM, BW) used to retrieve data into portal iViews. If not
existing, you must create a System Object in the NetWeaver Portal.
9.3.1 Prerequisites
This example shows the customizing for the connection to a specific ABAP® system.
3. Connector settings
In the Display drop down list, select Object, and then, in the Property
Category drop down list, select Connector.
Provide minimum connector properties for example. See the following
screenshot for example values.
4. ITS settings
ITS settings are maintained for displaying SAP transactions in the portal as an
iView.
In the Display drop down list, select Object, and then, in the Property
Category drop down list, select Internet Transaction Server (ITS).
Provide ITS properties as shown in the following screenshot.
The property values to enter can be read from the ABAP system using
transactions SICF and SMICM.
For a detailed description how to set up the System Object in the Portal, see
http://wiki.sdn.sap.com/wiki/display/EP/How+to+Create+System+Object+in+the
+Portal+for+Connecting+to+SAP+backend+System.
2. Choose a folder or generate a new folder. To select the iView object, right-click
the folder and select new > iView.
3. In the Display drop down list, select Object, and then, in the Property
Category drop down list, select Content - Web Dynpro.
Provide properties as shown in the following screenshot.
Check also other properties for design or layout, and customize them if needed.
4. To test the newly generated iView object, click the Preview button. If everything
is customized correctly, a separate window opens and shows the KPI
Dashboard content in the iView.
This part describes the installation of the OpenText Approval Portal component. The
Approval Portal is designed to work within SAP NetWeaver Application Server Java
(NWAS) 7.0 or 7.3 or SAP NetWeaver Portal (NWP) 7.0 or 7.3.
With VIM 7.0 SP4 and higher, NWAS 7.4 and NWP 7.4 are also supported.
Notes
• The Approval Portal is an optional component.
• If you are not using the Approval Portal, you can skip this part.
• Please refer to section 12 “Administering the Approval Portal” in OpenText
Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-
AGD) for administering and troubleshooting the Approval Portal.
• You might want to install multiple instances of the Approval Portal on the
same SAP NetWeaver Portal. In this case, contact OpenText Customer
Support.
Server
Notes
• The requirement “SPx or above” does also refer to the EhP level.
• For further information, see the SAP Note: 994791-SPNego Wizard.
Recommended The following list shows the supported resolution modes that have been tested in
Screen the OpenText R&D lab. The resolution modes have been tested in all supported
Resolution
browsers.
Web browsers The following matrix shows the web browsers and versions that are supported by
the new interface of the Approval Portal, which is delivered since VIM 7.0 SP2. The
matrix is based on tests performed at OpenText R&D Lab. It considers accessibility
and usability aspects.
Note: The old interface of the Approval Portal supports only Internet Explorer
7.0, 8.0, and 9.0.
With VIM 7.0 SP4 and above, the old interface of the Approval Portal also
supports Internet Explorer 10.0 and 11.0.
NWAS 7.3
NWAS 7.4
(with VIM 7.0
SP4)
NWP 7.0
NWP 7.3
Operating The Approval Portal supports Windows, Unix and other operating systems
systems supported by SAP.
Note: The new Approval Portal has not been tested in Unix environment.
Aligned with SAP operating system support, see the SAP Product Availability
Matrix (PAM) for more details.
Sizing require- Standard sizing requirements for NWAS or NWP 7.0 apply.
ments
SAP user A SAP CPIC user in the SAP ERP server
The communication with the SAP ERP system is accomplished by using a CPIC user
ID. However, the Web user is recorded as the agent who approved an invoice, not
the CPIC user.
User type
Communication Data (CPIC)
Profile
Create a profile with the following authorization objects and add it to the CPIC
user:
Object: S_RFC
Activity
Execute (16)
Names of RFC to be protected
/OPT/VIM_FG1A2, /ORS/*, /OPT/*, /ORS/SAPL000007_APPR_SCREEN, /
PTGWFI/*, OPTB, ARFC, ERFC, RFC1, SDIFRUNTIME, SUNI, SYST, SYSU
RFC_TYPE
FUGR (Function Group)
Object: S_CPIC
Activity
Accept, Initialize (37 and 51)
Name of an ABAP/4 FORM routine
CPIC
Symbolic destination
*
If you wish to narrow this down, examine table TXCOM and choose entry
under the SDEST field that represents the destination of the system you are
communicating with.
Program Names with Search Help
/ORS/*, /OPT/*, /PTGWFI/*
Object: S_DATASET (Authorization for file access)
Activity
Read, Write (33 and 34)
Filename
* (physical file name)
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:
Defaults
Decimal notation should be 1,234,567.89.
Note: For SAP ERP systems with EHP5 or higher, one additional authorization
is required for the CPIC user.
S_WF_WI
Classification of tasks
*
Activities
12 (Resubmit work item)
VIM 7.0 SPx installation packages for old and new interface
For all Support Packages of VIM 7.0 (SP2 and higher), the respective OpenText
Vendor Invoice Management 7.0 Support Package folder in the Knowledge
Center (accessible via https://knowledge.opentext.com/knowledge/cs.dll/Open/
32893475) provides two installation packages of the VIM 7.0 SPx Approval
Portal in the Web and Mobile Approval Component folder: one for the new
user interface (which is introduced with VIM 7.0 SP2), and one for the old user
interface.
There are 2 ways to configure the Approval Portal application. It can be deployed:
• as a standalone J2EE application residing on NWAS only utilizing integrated
authentication
• as an application inside NWP using AppIntegrator iView
The 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_nw70ehp1/helpdata/en/43/
4bd58c6c5e5f34e10000000a1553f6/frameset.htm)
• Network and Transport Layer Security (http://help.sap.com/saphelp_nw70ehp1/
helpdata/en/3a/7cddde33ff05cae10000000a128c20/frameset.htm)
• SAP Java Connector (JCO) (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/
6f/1bd5c6a85b11d6b28500508b5d5211/content.htm)
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.
Important
OpenText recommends you to create and deploy to the folder usr/sap/
<SID>/SYS/global/opentext/invoiceCfg. This is the default location
for putting the application configuration file. If you deploy to another
location, you will have to manually add a startup parameter in the
Config Tool to tell the application where to look for the configuration
files. This will also require restarting the SAP NetWeaver Application
Server Java (NWAS). See Step 2 on page 94 for details.
<SID> is the system ID of the NWAS. Example: T39.
Example: E:\usr\sap\T39\SYS\global\opentext\invoiceCfg
configuration.xml
containing all the configuration for the application
mobileconfiguration.xml
containing all the configuration for mobile support
RequestMappings.xml
OpenText strictly recommends not to modify this file. The Approval Portal
application internally uses this file.
Lang_Support.properties
containing all the mapping of languages code; see section 12.3.2
“Configuring Additional Languages” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for details.
Lang_DE.properties
containing all the text for the German language resource
Lang_EN.properties
containing all the text for the English language resource
Lang_ES.properties
containing all the text for the Spanish language resource
Lang_FR.properties
containing all the text for the French language resource
Lang_IT.properties
containing all the text for the Italian language resource
Lang_JA.properties
containing all the text for the Japanese language resource
Lang_NL.properties
containing all the text for the Dutch language resource
Lang_PT.properties
containing all the text for the Portuguese language resource
Lang_RU.properties
containing all the text for the Russian language resource
Lang_ZH.properties
containing all the text for the Chinese language resource
There might be more .properties files, depending on the package and the
release for additional languages. The language resource files can be changed.
See section 12.3.1 “Changing Language Resources” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD) for details.
Important
Make sure the <Approval_Portal_installdir> folder has:
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.
Notes
• SID is the system ID of the NWAS (example O15).
• INSTANCE_NAME is the NWAS instance in the format of JCxx, where
xx is the instance number (example JC00).
Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/
opentext/invoiceCfg
b. Save the new parameter.
This section describes the installation activities to assign the administrator role to the
user for the Approval Portal application. As the Administrator, you must login to
the Administrator page to perform some application configuration and to perform
other administration tasks. See section 12 “Administering the Approval Portal” in
OpenText Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-
AGD) for additional information.
You must perform this configuration before deploying the .sca or .sda, to ensure
that the application recognizes the role.
1. Log in to J2EE Visual Administrator and navigate to Instance > Server >
Services > Security Provider.
3. Click the Runtime tab > Policy Configurations tab > Security Roles tab.
6. In the Add Security Role dialog box, enter the role name:
com.opentext.vim.portal.administrator.
Click OK.
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.
6. Click OK.
Note: Check this after you have deployed the .SCA or .SDA file, see
“Deploying the Software Component Archive” on page 101.
• Navigate to http://<NWAS>:<NWASPORT>/vimportal/admin.
If you see a screen similar to the one above, you have configured the
administrator role successfully.
To configure the administrator role for access through NWAS for SAP
NetWeaver 7.3 and 7.4:
4. Click the Assigned Users tab and perform a search. Select the user and click
Add.
100 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
11.3. Deploying the Software Component Archive
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.
Notes
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 101
VIM070000-IGD-EN-6
Chapter 11 Installing the Approval Portal
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.
102 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
11.3. Deploying the Software Component Archive
1. In the SDM, click the SDM Repository tab and expand SAPJ2EEEngine.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 103
VIM070000-IGD-EN-6
Chapter 11 Installing the Approval Portal
You will see OpenText Approval error messages. This is correct as you have not
done any configuration yet.
a. Click on a server.
b. Expand Services.
c. Expand Deploy.
104 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
11.4. Deploying the Software Component Archive with SAP NetWeaver 7.3 and 7.4
1. Click on a server.
2. Expand Services.
3. Expand Deploy.
See screenshot in Step 3 on page 104.
5. Click on opentext.com/IM_APPROVAL_PORTAL.
Notes
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 105
VIM070000-IGD-EN-6
Chapter 11 Installing the Approval Portal
106 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
11.4. Deploying the Software Component Archive with SAP NetWeaver 7.3 and 7.4
5. Click Start.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 107
VIM070000-IGD-EN-6
Chapter 11 Installing the Approval Portal
108 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 12
If you are deploying the Approval Portal on SAP NetWeaver Application Server
Java (NWAS) and the users are accessing the application through SAP NetWeaver
Portal, you must configure the SAP NetWeaver Portal components.
For a description of the configuration with SAP NetWeaver 7.3 and 7.4, see
“Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4”
on page 115 and “Creating Roles for Users with SAP NetWeaver 7.3 and 7.4”
on page 129.
Note: For information on how to change the title of the iView, page, workset,
or role, refer to the SAP NetWeaver Portal Administration Guide from SAP.
As the SAP NetWeaver Portal administrator, you create the Appintegrator iView. To
make the application available for SAP NetWeaver Portal users, you have to
perform the following steps:
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.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 109
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
110 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.1. Creating AppIntegrator IViews for Users
4. In the iView wizard, click Portal Component – create an iView from a portal
component ... and click Next.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 111
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
112 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.1. Creating AppIntegrator IViews for Users
• Description
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 113
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
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.
114 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.2. Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4
$host$
NWAS server name where the Approval Portal J2EE application was
deployed
$port$
Port of that NWAS
To create AppIntegrator iViews for users with NetWeaver 7.3 and 7.4:
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 115
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
3. Right-click End User Content, point to New, and then click Folder.
116 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.2. Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4
4. On the New Folder tab, enter Folder Name and Folder ID Prefix (for example,
com.opentext); then click Finish at the bottom of the page.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 117
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
118 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.2. Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4
8. Navigate to Portal Content > Content Provided by SAP > End User Content.
9. In the Approval Portal folder, paste the Generic iView as PCD Object. See the
following screenshot.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 119
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
120 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.2. Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 121
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
122 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.2. Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4
13. From the Show Category list, select Content - Generic Launcher.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 123
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
URL Template
http://<host name>:<port number>/vimportal/?
urlView=Y&PORTALUSER=<User.UserID>
The URL is different for the Admin iView:
http://<host name>:<port number>/vimportal/admin?
urlView=Y&PORTALUSER=<User.UserID>
Enter the following values:
<host name>
Name of the NWAS where the Approval Portal J2EE application was
deployed.
<port number>
Port of that NWAS.
124 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.3. Creating Roles for Users
1. In the SAP NetWeaver Portal, navigate to the folder you created in “Creating
AppIntegrator IViews for Users” on page 109.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 125
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
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 112 in “Creating AppIntegrator IViews for
Users” on page 109.
• Role ID Prefix is not mandatory. If you enter this parameter, you must
search by giving Role ID Prefix and Role Name when assigning the role
to the user.
4. Click Next.
126 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.3. Creating Roles for Users
5. Click Finish.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 127
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
7. In Property Editor, scroll to the Entry Point line and click Yes.
Click Save.
9. Click Close.
128 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.4. Creating Roles for Users with SAP NetWeaver 7.3 and 7.4
To create roles for users with SAP NetWeaver 7.3 and 7.4:
1. In the SAP NetWeaver Portal, navigate to the Approval Portal folder; see
“Creating AppIntegrator IViews for Users with SAP NetWeaver 7.3 and 7.4”
on page 115.
2. Right-click on the folder, select New > Role > Freestyle Role.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 129
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
3. Enter properties as shown in the screenshot above: Role Name, Role ID, Role
ID Prefix and Description.
Select the Master Language.
Note: Role ID Prefix is not mandatory. If you enter this parameter, you
must search by giving Role ID Prefix and Role Name when assigning the
role to the user.
4. Click Finish.
130 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.4. Creating Roles for Users with SAP NetWeaver 7.3 and 7.4
6. Enter the Name (as shown in the screenshot) and select the Entry Point check
mark.
Click Save.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 131
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
8. Click Close.
2. In the Search Criteria, enter the users or groups you want to assign to the new
role (created in “Creating Roles for Users” on page 125).
Click Go.
4. Click Modify.
5. In the Search Criteria field, search for the new role you created and click Go.
7. Click Save.
The following screenshot shows a role being assigned to a demo coder.
132 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
12.6. Configuring IViews and Roles for the Administrator
You can use Approval Admin for the iView Name and Approval Admin Role for the
role.
The only difference from the user configuration is the URL template:
http://$host$:$port$/vimportal/admin?
urlView=Y&PORTALUSER=<User.UserID>
See Step 11 on page 114 for details on the URL template for users.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 133
VIM070000-IGD-EN-6
Chapter 12 Configuring SAP NetWeaver Portal Components
Once you have finished the creation of the Administrator iView and the role, assign
it to the appropriate administrators, as described in “Assigning Roles to SAP
NetWeaver Portal Users” on page 132.
When you, as the administrator, navigate to the Approval Admin iView, it will look
like the following screenshot:
You have now finished the installation and configuration of the OpenText Approval
Portal.
134 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 13
Applying a New Patch
Note: Unlike the VIM SAP ERP component, the Approval Portal is a build and
has no dependencies of previous patches or support packages. You can
uninstall the previous version and directly install the newest version without
applying the patches in between. However, the patch or build needs to match
to the VIM SAP ERP component. Approval Portal 7.0 will only work with the
VIM 7.0 SAP ERP component.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 135
VIM070000-IGD-EN-6
Chapter 14
Upgrading the Approval Portal from Previous
Versions
You can upgrade the Approval Portal from version 5.2 to 7.0 and from version 6.0 to
7.0.
Make sure that all files mentioned in opentext.zip are deployed correctly.
You can reuse the original configuration.xml file as there are no changes; but it is
best to make a backup of the configuration.xml.
If you changed the language properties files from the previous version and would
like to reuse them in VIM 7.0, change the new language properties files manually.
To upgrade, perform the actions described in “Applying a New Patch“ on page 135.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 137
VIM070000-IGD-EN-6
Chapter 15
Troubleshooting
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 139
VIM070000-IGD-EN-6
Chapter 16
Supporting Installation of the Standalone NWAS
Portal and Mobile Approval Portal on Unix or Linux
This chapter provides instructions how to enable the installation of the standalone
NWAS Portal and Mobile Approval Portal on Unix or Linux operating systems.
To support Unix or Linux operating systems, you must maintain the Domain field
with the same value, as maintained in the Windows Domain column in the COA
table. For details about the COA configuration, see section 5.5.1 “User Details View”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Example: If the Windows Domain column in the COA table is not maintained for users,
leave the Domain field in the Configuration tab of the Approval Portal Administration
console empty as well.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 141
VIM070000-IGD-EN-6
Chapter 17
Uninstalling the Approval Portal
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
• SID is the system ID of the NWAS (example O15).
• INSTANCE_NAME is the NWAS instance in the format of JCxx, where
xx is the instance number (example JC00).
Refer to the Software Deployment Manager Guide for more details on how to
use SDM.
4. Click Select.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 143
VIM070000-IGD-EN-6
Chapter 17 Uninstalling the Approval Portal
To undeploy the Approval Portal with SAP NetWeaver 7.3 and 7.4:
3. In the J2EE Engine Console, type list_app to view the list of components that
are deployed.
144 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
17.3. Removing SAP NetWeaver Portal Components
Note: First, unassign the role if you already have assigned it to a user.
4. Navigate to the folder that was created in “Creating AppIntegrator IViews for
Users” on page 109.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 145
VIM070000-IGD-EN-6
Chapter 17 Uninstalling the Approval Portal
Removing the startup parameter, using the J2EE Config Tool, finishes the
uninstallation process.
Notes
• SID is the system ID of the NWAS (example O15).
• INSTANCE_NAME is the NWAS instance in the format of JCxx, where
xx is the instance number (example JC00).
146 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
17.5. Optional: Removing the Startup Parameter in the Config Tool
Example: -Dcom.opentext.vim.portal.invoiceCfg=c:/
opentext/invoiceCfg
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 147
VIM070000-IGD-EN-6
Part 5
Mobile Approval Portal Installation
Part 5 Mobile Approval Portal Installation
This part describes the installation of the Mobile Approval Portal, which is an
enhancement to the Invoice Approval. Users can approve their invoices, using a
mobile device, for example a Blackberry, an iPhone, or an iPad. The Mobile
Approval Portal is based on HTML5.
Note: The Mobile Approval Portal is an optional component. If you are not
using the Mobile Approval Portal, you can skip this part.
For information on the configuration of the Mobile Approval Portal, see section 13
“Configuring the Mobile Approval Portal” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD).
150 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 18
The Mobile Approval Portal component in VIM 7.0 is enhanced with the mobile
capabilities Sencha Touch. This enriches the look and feel on the supported mobile
platforms. For detailed information about Sencha Touch, see http://
www.sencha.com/products/touch/features/.
Operating The Mobile Approval Portal supports Windows, Unix and other operating systems
systems supported by SAP.
The following table shows which mobile operating systems, devices, and browsers
are fully supported:
VIM 7.0 adds the new column Category which signifies Performance, Usability/
Accessibility and Document Viewing aspects, ranked from A to C. A, B, and C are
rankings from top to bottom on the mentioned aspects. These ranks are provided
based on testing in OpenText Mobile lab with real devices and simulators.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 151
VIM070000-IGD-EN-6
Chapter 18 Introduction to the Mobile Approval Portal
Web Viewer Mobile Approval Portal users can display invoices using OpenText Imaging Web
integration Viewer. Web Viewer is a web application for displaying and printing documents in
Web-based scenarios and for appending comments to these documents. The
documents may be stored in OpenText Archive Server or other repositories.
The Web Viewer integration is completed for the invoice document and supports all
documents supported by Web Viewer.
On the Mobile Browser without Web Viewer, it is not possible to render TIFF
documents. JPG, PNG and GIF documents are supported to be shown in browser by
default. To support PDF documents, a specific browser-plugin or a separate viewer
app is needed.
However, Web Viewer is able to display TIFF documents on the Mobile Browser on
Mobile Approval Portal.
Web Viewer is installed on a web server. It generates HTML pages containing the
document to be displayed and sends them to the browser. The Web Viewer can be
used by any leading application server configured appropriately.
Limitations
• Web Viewer does not support MS Office documents.
• For attachments, the Web Viewer integration is not implemented. Any attached
document, like PDF, JPEG, GIF or PNG, will be forced to open in a separate
browser window by default.
Notes
• OpenText strongly recommends that you implement Web Viewer to display
images on the Mobile Approval Portal.
• For further information about Web Viewer, see OpenText Imaging Web Viewer
- Installation and Configuration Guide (CLWEBV-IGD).
152 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Figure 18-1: HTML5 Mobile Approval Portal Architecture
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 153
VIM070000-IGD-EN-6
Chapter 19
Authentication for the Mobile Approval Portal
This section describes the communication and authentication needed for the Mobile
Approval Portal.
The Mobile Approval Portal uses domain authentication. It can be accessed using
WiFi or VPN on the same network or on an external network.
To access from external network without WiFi or VPN, keep the Mobile Approval
Portal URL in the DMZ and connect with Virtual Host. This requires IT help to
configure the URL in the DMZ.
Note: For security reasons and also to grant stable access to the Mobile
Approval Portal, OpenText recommends that you use a VPN connection.
The detail authentication mechanism is the same as for the Approval Portal, for
example, which SSO mechanism is used. See “Preparing Installation“ on page 85
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 155
VIM070000-IGD-EN-6
Chapter 20
OpenText Imaging Web Viewer can be integrated in the Mobile Approval Portal. To
ensure security for the Web Viewer integration, OpenText recommends that you
verify the “Use Signature” setting in /IXOS/OA_CUST_A with the following
prerequisites:
Note: See also the Release Notes of OpenText Archiving and Document Access
for SAP Solutions 10.0 SP2.
Web Viewer version 10.5.0 will be supported with a later Support Package.
The Mobile Approval Portal supports Windows, Unix and other operating systems
supported by SAP. For the Web Viewer installation, see the appropriate section in
section 3 “Installing Web Viewer” in OpenText Imaging Web Viewer - Installation and
Configuration Guide (CLWEBV-IGD).
To install Web Viewer 10.2.0, download the software from the following location:
http://knowledge.opentext.com/knowledge/cs.dll/Open/19642255.
To apply patch 004 (or higher) for Web Viewer 10.2.0, download the software from
the following location: https://knowledge.opentext.com/knowledge/cs.dll/Open/
22422170
Notes
• OpenText recommends that you use the latest patch of the supported Web
Viewer software version.
• OpenText also recommends installing Web Viewer on a NetWeaver 7.3 or 7.4
instance where Mobile Approval Portal is not running or on a supported
Tomcat version. This approach improves the performance of viewing invoice
images on Mobile devices.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 157
VIM070000-IGD-EN-6
Chapter 20 Installing Web Viewer for the Mobile Approval Portal
158 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 21
Installing the Mobile Approval Portal differs depending on the application server
you use:
The Mobile Approval Portal software component is packaged along with the
Approval Portal component. The installation of the Mobile Approval Portal is
similar to Approval Portal. Refer to “Installing the Approval Portal“ on page 93.
The Mobile Approval Portal software component is packaged along with the
Approval Portal component. The installation of the Mobile Approval Portal is
similar to Approval Portal. Refer to “Installing the Approval Portal“ on page 93.
21.2.1 Prerequisites
The following versions are supported:
Approval Portal
7.0
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 159
VIM070000-IGD-EN-6
Chapter 21 Installing the Mobile Approval Portal
3. Deploy the Approval Portal with the officially supported Support Package.
2. Deploy the Approval Portal with the officially supported Support Package.
160 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Part 6
Vendor Invoice Management SAP CRM SAP
Shared Service Framework Component
Installation
Part 6 Vendor Invoice Management SAP CRM SAP
Shared Service Framework Component Installation
This part describes the installation of the Vendor Invoice Management SAP CRM
SAP Shared Service Framework component.
162 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 22
Preparing 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
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 163
VIM070000-IGD-EN-6
Chapter 22 Preparing Installation
The following components must be installed for SAP CRM 7.0 EHP2:
Component SAP_ABA
Level: 731
Component BBPCRM
Level: 702
Component SAP_BASIS
Level: 731
The following components must be installed for SAP CRM 7.0 EHP3:
Component SAP_ABA
Level: 740
Component BBPCRM
Level: 703
Component SAP_BASIS
Level: 740
164 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
22.2. Checking Prerequisites
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.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 165
VIM070000-IGD-EN-6
Chapter 23
This chapter describes the installation of the Basis package of Vendor Invoice
Management (VIM) on an SAP CRM application server.
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).
File
OTVIMSSF_INST_VIM701_702.SAR
Source path
INST_CRM_700/DATA/
Target path
\usr\sap\trans\EPS
3. Only if you install on SAP CRM 7.0 EHP2 or SAP CRM 7.0 EHP3:
An ACP file is necessary. The ACP file is available in SAP Marketplace as
Attribute Change Package 01 for OTVIMSSF 701_702.
Extract the CSR0120031469_0080724.PAT file from the
CSR0120031469_0080724.zip folder and copy it to the \usr\sap\trans\EPS
\in folder.
4. Carry out the import of the package as described in the respective SAP
documentation.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 167
VIM070000-IGD-EN-6
Chapter 23 Installing the OpenText Package
168 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 24
To put the SAP Shared Service Framework integration into operation, you must
perform the following post installation tasks:
• For every client, you must activate new BC Sets after installing VIM 6.0
CRM.
• You need the appropriate security authorization to run some of the
transactions.
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.
1. To access the Business Configuration Sets: Activation screen, run the SCPR20
transaction.
From the Utilities menu, click User Settings.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 169
VIM070000-IGD-EN-6
Chapter 24 Post Installation Activities
• Chinese
• Dutch
• English
• French
• German
• Hungarian
• Italian
• Japanese
• Portuguese
• Romanian
• Russian
• Spanish
170 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
24.1. Activating Business Configuration Sets in the CRM System
• Czech
• Polish
• Turkish
To select your applicable languages, select the respective check box in the
Manual Selection column.
To activate BC Sets:
1. To access the Business Configuration Sets: Activation screen, run the SCPR20
transaction.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 171
VIM070000-IGD-EN-6
Chapter 24 Post Installation Activities
Note: If you are prompted to create a new transport, follow your standard
change request process for tracking changes.
After successful BC Set activation, a message is displayed in the lower left of the
SAP GUI: Activation ended with additional information.
172 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
24.2. Maintaining a Logical System for the CRM System in VIM
To maintain a logical system for the CRM system in the SAP ERP system:
1. In VIM, run the /N/OPT/SPRO transaction and navigate to the menu path
Vendor Invoice Management > Cross Component Configuration > CRM
Integration > Maintain CRM Logical System.
2. Enter the logical system for the CRM system in the Constant Value field.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 173
VIM070000-IGD-EN-6
Chapter 25
Verifying Installation
Make sure that the OpenText Vendor Invoice Management CRM add-on is reflected
in the installed components.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 175
VIM070000-IGD-EN-6
Chapter 25 Verifying Installation
In the System: Component information dialog box, you should see the
OTVIMSSF add-on component installed, with Release number 701_702 and
patch level 0002.
176 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Part 7
Vendor Invoice Management SAP
NetWeaver Business Warehouse
Component Installation
Part 7 Vendor Invoice Management SAP NetWeaver
Business Warehouse Component Installation
This part describes the installation of the Vendor Invoice Management SAP
NetWeaver Business Warehouse (VIM BW) component.
178 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 26
Preparing Installation
SAP_BASIS Password
700 F17CB370FA
730 F17CB070FA
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 179
VIM070000-IGD-EN-6
Chapter 26 Preparing Installation
Table 26-1: SAP NetWeaver BW 7.0 / SAP NetWeaver BW 7.3 EHP1 / SAP
NetWeaver BW 7.4
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.
180 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 27
This chapter describes the installation of the Basis package of VIM on an SAP
NetWeaver BW application server.
The basic components of VIM SAP NetWeaver BW are installed with the Basis
package.
1. 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).
File
OTVIMBW_INST_VIM700_700.SAR
Source path
INST_BW_700/DATA/
Target path
\usr\sap\trans\EPS
File
OTVIMBW_INST_VIM700_730.SAR
Source path
INST_BW_730/DATA/
Target path
\usr\sap\trans\EPS
3. Call transaction SAINT (in client 000). You get an initial screen, which shows the
installed components.
Click Start to add the VIM 7.0 BW component.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 181
VIM070000-IGD-EN-6
Chapter 27 Installing the OpenText Package
4. Click Start to see the screen that presents the packages ready to be installed.
182 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
5. Choose the package for component OTVIMBW. Carry out the import of the
package as described in the respective SAP documentation.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 183
VIM070000-IGD-EN-6
Chapter 28
Verifying the Installation
Make sure that the VIM BW add-on is reflected in the installed components.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 185
VIM070000-IGD-EN-6
Chapter 28 Verifying the Installation
In the System: Component information dialog box, you should see the OTVIMBW
add-on component installed, with Release number 700.
186 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 29
Upgrading SAP NetWeaver BW
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 187
VIM070000-IGD-EN-6
Part 8
Vendor Invoice Management SAP
NetWeaver Gateway Component
Installation
Part 8 Vendor Invoice Management SAP NetWeaver
Gateway Component Installation
This part describes the installation of the Vendor Invoice Management SAP
NetWeaver Gateway (VIM GW) component. The VIM GW component is needed to
run the Supplier Self Service component, which is introduced with VIM 7.0 SP3.
190 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 30
Preparing Installation
SAP_BASIS Password
700 and compatible F17CB670FA
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 191
VIM070000-IGD-EN-6
Chapter 30 Preparing Installation
• Implement OSS note 1744864: Multiple Origin for Generated BOR/RFC Objects
does not work
Note: The VIM GW component is not yet released for SAP_BASIS 740 (EHP7).
On the product CD, the single PAT files are archived in SAPCAR files (extension
*.SAR), which can be extracted using the SAPCAR command line tool.
192 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 31
Installing the OpenText Package
3. On the menu, click Installation Package > Load packages > From Front End
and load file OTVIMGW_INST_VIM700_700.SAR.
5. Choose the package for component OTVIMGW. Carry out the import of the
package as described in the respective SAP documentation.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 193
VIM070000-IGD-EN-6
Chapter 32
Verifying the Installation
Make sure that the VIM GW add-on is reflected in the installed components.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 195
VIM070000-IGD-EN-6
Part 9
Vendor Invoice Management Supplier Self
Service Component Installation
Part 9 Vendor Invoice Management Supplier Self
Service Component Installation
This part describes the installation of the Vendor Invoice Management Supplier Self
Service component. The Supplier Self Service component is introduced with VIM 7.0
SP3.
198 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 33
Preparing Installation
Server SAP HANA Cloud Platform or any other Java-based application server (SP3
restriction)
Operating This section covers support and restrictions of Supplier Self Service in regards to
system and operating systems and web browsers.
browser support
• The Supplier Self Service web application does not support any mobile operating
systems. It does not support any other operating systems than Windows.
Therefore, Mac/iOS, Linux, and Android operating systems are not supported.
• For supported browsers, see https://sapui5.hana.ondemand.com/sdk/docs/guide/
BrowserSupport.html. See also OSS note 1716423: SAPUI5 Browser Support for
Mobile and Desktop Applications
• Some additional browser settings are necessary:
Firefox
You must customize the language preferences: Go to Tools > Options, and
click the Content tab. In the Languages area, click Choose.
Add languages from the Select a language to add list. When performing
an HTTP request, Firefox will send all the languages chosen with the Accept-
Language header in the order of preference in which they are arranged in the
list.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 199
VIM070000-IGD-EN-6
Chapter 33 Preparing Installation
SAP user The communication with the SAP NetWeaver Gateway system is accomplished by
using a Service user ID. Creation and assignment of the specific profile is described
in section 22.1.3 “Configuring Gateway Users” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
Note: With VIM 7.0 SP3, only Option 1 is supported. It is described in the
following.
200 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 34
Installation on the SAP HANA Cloud
The SAP HANA Cloud Platform is an in-memory cloud platform based on open
standards. The platform is Java EE 6 Web Profile certified and provides a secure,
scalable runtime environment with reusable platform services. Therefore, Supplier
Self Service can run on the SAP HANA Cloud Platform just like on any Java-based
application server.
Note: You need an SAP account for accessing the HANA Cloud.
Prerequisites
• You have downloaded and configured the SAP HANA Cloud Platform console
client. For more information, see https://help.hana.ondemand.com/help/
frameset.htm?7613dee4711e1014839a8273b0e91070.html.
• Depending on your account type, deploy the application on the respective
landscape. For more information, see https://help.hana.ondemand.com/help/
frameset.htm?350356d1dc314d3199dca15bd2ab9b0e.html.
1. In the opened command line console, run the neo deploy command with the
appropriate parameters. You can define the parameters of commands directly in
the command line, as in Example 34-1, “Deployment on the SAP HANA Cloud
Server” on page 202.
2. Enter your password if requested.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 201
VIM070000-IGD-EN-6
Chapter 34 Installation on the SAP HANA Cloud
3. Press ENTER.
The deployment of your application starts.
neo deploy -- host <SAP HANA Cloud host> -- account <your account> --
application vim3s -- source vimsupplierselfservice.war -- user <email or
user name>
Notes
• OpenText recommends entering the application name vim3s but you can
choose any other identifier you want.
• If the source file vimsupplierselfservice.war is located somewhere on
your system but not on the deployment folder you have to add the path
information to the filename.
• If you face any problems with the runtime environment, you can set the
custom parameter runtime-version manually, as described in https://
help.hana.ondemand.com/help/frameset.htm?
13afe5ca6e38485d8e6523f610c0ed29.html.
Next steps To make your deployed application available for requests, you must start it by
running the neo start command or manage inside the SAP HANA Cloud cockpit.
For more information, see section 22.2 “Customizing the HANA Cloud Server
(Option)” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
If you need more information about the SAP HANA Cloud Platform console client,
see the online documentation: https://help.hana.ondemand.com/help/frameset.htm?
46acebcd81384c9881f8ae7c5f3e3cac.html
Note: The SAP HANA Cloud connector must not be used with products other
than SAP HANA Cloud Platform.
202 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
34.3. Installing the SAP HANA Cloud Connector
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 203
VIM070000-IGD-EN-6
Part 10
Vendor Invoice Management Input Channel
for Ariba Network Integration for SAP
Business Suite Installation
Part 10 Vendor Invoice Management Input Channel for
Ariba Network Integration for SAP Business Suite
Installation
This part describes the installation of the Vendor Invoice Management input channel
for Ariba Network Integration for SAP Business Suite (VIM ARB).
206 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 35
Preparing Installation
SAP_BASIS Password
700 and compatible F17CB07598
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 207
VIM070000-IGD-EN-6
Chapter 35 Preparing Installation
• Implement OSS note 1935335: Mapping methods cannot be used from BAdI
implementations
On the product CD, the single PAT files are archived in SAPCAR files (extension
*.SAR), which can be extracted using the SAPCAR command line tool.
208 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Chapter 36
Installing the OpenText Package
3. On the menu, click Installation Package > Load packages > From Front End
and load file OTVIMARB_INST_VIM700_700.SAR.
5. Choose the package for component OTVIMARB. Carry out the import of the
package as described in the respective SAP documentation.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 209
VIM070000-IGD-EN-6
Chapter 37
Post Installation Activities
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 211
VIM070000-IGD-EN-6
Chapter 38
Verifying the Installation
Make sure that the VIM ARB add-on is reflected in the installed components.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 213
VIM070000-IGD-EN-6
Glossary
AAK
See SAP Add-On Assembly Kit (AAK).
After Image
Technical option to realize an delta upload from the source systems into the SAP
NetWeaver BW system. A data record loaded as After Image provides the status
of the record after it has been changed, or after data has been added.
Aging Report
Part of the Central Reporting infrastructure. The Aging Report reports about the
aging of documents and work items in the current system.
AP processor
The Approval chart of authority (COA) determines first approver and next
approver for an invoice by combinations of Company Code (specific or range),
Expense Type (marketing expense, utility), Cost Objects (G/L account, Cost
Center), and HR objects (Position, Job code).
Approval Portal
Archive system
ArchiveLink
Service integrated in the SAP NetWeaver Application Server ABAP for linking
archived documents and the application documents entered in the SAP ERP
system
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 215
VIM070000-IGD-EN-6
Glossary
Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can perform in the SAP ERP system. These authorizations are
stored in Authorization profiles.
Automation Report
Tool that provides data about automated and manual processing steps of VIM
documents
BAdI
See Business Add-Ins (BAdI).
BAPI®
Baseline
BasisCube
See InfoCube.
BDC ID
Business Data Communication ID. The BDC ID is used by the system to process
an SAP transaction to create an SAP Document in user context.
Block
Situation where an invoice has a price or quantity variance that prevents invoice
from posting
BTE
See Business Transaction Event (BTE).
Business rules
Rules that describe the operations, definitions and constraints that apply to an
organization
Event used for extending a Non PO invoice functionality to call a custom program
216 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Glossary
Buyer
Person who is in charge of the PO. This role should have authorization to create
and change the purchase order. This role is also responsible for negotiating and
communicating with vendors.
Central Reporting
Reporting infrastructure that provides several reports that enable you to measure
certain properties of VIM documents and their work items, in order to optimize
working with VIM. Central Reporting comprises the following individual reports:
Aging Report, Central Audit Report, Exception Analysis Report, Key Process Analytics
Report, Productivity Report, and Summary Report.
Characteristic
COA
See Approval chart of authority (COA).
Coding
Contract agent
Dashboard
User interface that organizes and presents information in a way that is easy to
read. Users can also perform actions from the dashboard.
Object in SAP NetWeaver BW to transfer data from source objects to target objects
DataSource
Set of fields in SAP NetWeaver BW that provide the data for a business unit for
data transfer to the SAP NetWeaver BW system; technically, it contains an extract
structure and an extraction function module.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 217
VIM070000-IGD-EN-6
Glossary
DocuLink
VIM component that captures invoice metadata including line items for PO and
performs preconfigured business rules
Document type
DP
See Document Processing (DP).
DSO
See DataStore Object (DSO).
DTP
See Data Transfer Process (DTP).
Duplicate analyzer
EDI
See Electronic Data Interchange (EDI).
Method for transferring data between different application systems in the form of
messages. SAP applications support EDI with messages sent in an SAP
Intermediate Document (IDoc) format. VIM supports the creation of vendor
invoices through the EDI/IDoc interface.
Error handling method. Event Type Linkage determines what the application
should do in case an error could not be handled.
218 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Glossary
Exception
FI
See Financial Accounting (FI).
IAP
See Invoice Approval (IAP).
ICC
See Invoice Capture Center (ICC).
IDoc
See Intermediate Document (IDoc).
IE
See Invoice Exception (IE).
Indexer
Indexing
InfoArea
InfoCube
InfoObject Catalog
InfoObject
Smallest information unit in SAP NetWeaver BW. Key figures and Characteristics
are collectively called InfoObjects.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 219
VIM070000-IGD-EN-6
Glossary
InfoPackages
Object in SAP NetWeaver BW that specifies when and how to load data from a
given source system to the SAP NetWeaver BW system
InfoProvider
Information provider
VIM component that gathers and displays all VIM exceptions in one place. Users
can start the respective dashboard by processing a work item directly from the
Integrated Invoice Cockpit.
VIM component that enables users to perform coding, approving and rejecting
invoices
Invoice approver
Invoice characteristic
A value specific to each invoice (for example country) that allows flexible
processing in VIM. An invoice characteristic is determined during runtime and
depends on the corresponding index data of the document.
Invoice coder
Person who enters the accounting info on invoices to allocate the cost
VIM component that handles the exceptions that arise after an SAP invoice is
created
220 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Glossary
Invoice requester
Key Figure
Part of the Central Reporting infrastructure. The Key Process Analytics Report
reports about a variety of key figures regarding the VIM process: It shows the
accumulated amounts of all documents in the DP workflow, in parked state and
in posted state.
KPI Dashboard
Tool for managers showing VIM related process data at a glance in graphical
charts.
LIV
See Logistic invoice (LIV).
MM
See Materials Management (MM).
MultiProvider
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
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 221
VIM070000-IGD-EN-6
Glossary
Number range
Array of numbers that can be used for an object in the SAP ERP system
OCR
See Optical character recognition (OCR).
Park
Situation where an invoice is not posted and is waiting for further processing
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).
Invoice that has already been posted in SAP ERP. Only free-form text fields can
be changed. Related documents such as POs or good receipts may be created or
changed to effect the invoice. If the document is not needed, it must be cancelled
( PO invoice) or reversed ( non-PO invoice).
Price variance
Situation where the price on the invoice is different from the price in the purchase
order
222 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Glossary
Process Chain
Process options
Processing options for the user in the dashboard, such as Referral, Authorization,
and Actions
Process type
Process type for a document. The process type determines the initial actor and
various collaboration options available to the various actors during the process
flow.
Productivity Report
PSA
See Persistent Staging Area (PSA).
SAP module. PO indicates a document sent from a buyer to a seller. The purpose
of the document is to order the delivery of goods or services.
Quantity variance
Situation where the quantity on the invoice is different from the quantity in the
purchase order
Receiver
Person who can create and reverse the goods receipt in SAP ERP
Requisitioner
Roles
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 223
VIM070000-IGD-EN-6
Glossary
SAP application that provides software for ticket systems, for example in the
Accounts Payable department.
SAP software that contains a rich set of tools to improve and automate Shared
Service Center operations.
Scan operator
Person who scans the invoices into images (may not have a SAP ID)
Service approver
Service requisitioner
Summary Report
Swimlane
Tax expert
Person who advises on invoices that need tax audit. Normally tax department
personnel.
Transformation (TRF)
224 OpenText Vendor Invoice Management for SAP Solutions – Installation Guide
VIM070000-IGD-EN-6
Glossary
TRF
See Transformation (TRF).
VAN
See VIM Analytics (VAN).
Vendor maintenance
Person who is responsible for creating and maintaining the vendor master
records
VIM component that gives users a clear data report on their invoices in progress.
VIM Analytics allows to track the documents routed through SAP workflows via
VIM.
VIM Workplace
Tool for VIM super users, which allows users to display lists of their work items
that meet a selection they have entered before. Users also can display work items
of other users and of their team as a whole.
Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP ERP system.
OpenText Vendor Invoice Management for SAP Solutions – Installation Guide 225
VIM070000-IGD-EN-6