OpenText Vendor Invoice Management 75 SP9 Release Notes

OpenText™ Vendor Invoice Management
for SAP® Solutions
Release Notes
Version 7.5 SP9
Product Released: 2019-04-30
Release Notes Revised: 2019-05-16

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.5 SP9 Release Notes
3
Contents
1 Introduction .................................................................................................................................... 5
1.1 Release Notes revision history .................................................................................................. 5
2 About OpenText™ Vendor Invoice Management for SAP® Solutions ..................................... 5

2.1 General Data Protection Regulation (GDPR) ............................................................................ 6
3 Installation ...................................................................................................................................... 7
3.1 SAP Prerequisites...................................................................................................................... 7
3.2 Prerequisites on Archive Server (VIMI-4180) ............................................................................ 7
4 New Features .................................................................................................................................. 8

4.1 Change log entries for COA deleted users are maintained when upload function in full
mode is executed (VIMI-19181) ................................................................................................ 8
4.2 PDF log is updated for goods receipt posted outside VIM (VIMI-19766) .................................. 8
4.3 Document rejected from BC workplace is also set to obsolete in VIM (VIMI-20724)................ 8
4.4 Vendor specific tolerance are also factored for balance calculation error and tolerance
checks for a PO invoice. (VIMI-20731) ...................................................................................... 8
4.5 Warning popup for non-zero balance invoice in Web Approval Portal (VIMI-21270) ................ 9
4.6 Populating relevant tax codes based on reporting country (VIMI-21627) ................................. 9
4.7 Display of multiple POs in VIM Analytics (VIMI-21764) ............................................................. 9
4.8 The business rule ‘Invalid Vendor VAT number’ validates Tax Number 5 (VIMI-22002) ........... 9
4.9 Improvements in handling different currencies in Mobile Approval Portal (VIMI-22128) .......... 9
4.10 Date Selections for Data Archiving report (VIMI-22283) ........................................................ 10
4.11 Enter Cost Assignment Advanced Fiori app (VIMI-22342) ...................................................... 10
4.12 Debit / Credit indicator in line item of a DP document is preset based on VIM
Transaction / event type (VIMI-22618) .................................................................................... 10
4.13 Accessibility of commonly used VIM screens for JAWS user (VIMI-
22273,22356,22393,22681) .................................................................................................... 10
4.14 Processing of Leasing invoice from VIM (VIMI-22546) ........................................................... 10
4.15 PO proposal support extended for freight invoices through Bill of Lading (VIMI-16647) ........ 10
4.16 E-Invoice processing for Italy and Germany (VIMI-21314) ..................................................... 11
4.17 De-installation option for OTEXVIM 7.5 (VIMI-22263) ............................................................ 11
5 Packaging and Documentation .................................................................................................. 12

5.1 Packaging and Delivery Information ........................................................................................ 12
2
5.1.1 ABAP Package ........................................................................................................... 12
5.1.2 Language Package ..................................................................................................... 12
5.1.3 Non-ABAP Packages ................................................................................................. 13
5.1.4 Business Center – VIM upgrade from lower support package level .......................... 13
5.1.5 Business Center for SAP Solutions – Limited Use ..................................................... 14
5.1.6 Business Center - downloading components required for different scenarios ........... 14
5.1.7 Business Center – compatibility and support package information ........................... 17
5.1.8 Business Center - installation ..................................................................................... 18
5.1.9 Business Center - ACP files ....................................................................................... 19
5.1.10 Business Center - system landscape example .......................................................... 20
5.1.11 Additional Packages for Fiori Apps ............................................................................. 21
5.2 Documentation ........................................................................................................................ 21
6 Supported Environments and Compatibility ............................................................................. 22

6.1 Compatibility Matrix ................................................................................................................. 22
6.2 Language Support ................................................................................................................... 22
6.3 Approval Portal Downward Compatibility Matrix ..................................................................... 23
6.4 Supported Web Browsers ........................................................................................................ 24
6.5 Supported Operating Systems for Mobile Devices.................................................................. 25
6.6 Web Viewer support ................................................................................................................ 25
6.7 Brava View support.................................................................................................................. 26
6.8 VIM Fiori Apps: Variants .......................................................................................................... 26
6.9 VIM Fiori Apps: SAP UI5 Version Compatibility ....................................................................... 27
7 Fixed issues .................................................................................................................................. 28

7.1 Document Processing (DP) ..................................................................................................... 28
7.2 Document Processing (DP) – Logic Modules .......................................................................... 35
7.3 Invoice Approvals .................................................................................................................... 35
7.4 Web Approval Portal ................................................................................................................ 36
7.5 Fiori Approve Invoices app ...................................................................................................... 37
7.6 Fiori Enter Cost Assignment app ............................................................................................. 37
7.7 Fiori Confirm Quantity and Price app ...................................................................................... 37
7.8 Fiori Exceptions app ................................................................................................................ 38
7.9 Input Channels ........................................................................................................................ 38
7.9.1 Incoming Document Handler (IDH) ............................................................................ 38
7.9.2 IDF Framework (BC Inbound) .................................................................................... 38
7.10 Invoice Exception .................................................................................................................... 38
7.11 VIM Notifications ...................................................................................................................... 39
3
7.12 VIM Analytics (new VAN) Report and VAN Liability Report ..................................................... 39
7.13 Central Reporting and Other Reports ...................................................................................... 39
7.14 VIM Workplace ........................................................................................................................ 39
7.15 Customizing ............................................................................................................................. 40
7.16 Others ...................................................................................................................................... 40
8 Post Installation Activities .......................................................................................................... 41

8.1 Activate BC Set /OTEXVIM/VIM75_SP9_CUSTOMIZING...................................................... 41
8.2 Activate BC Set /OTX/VIM75_SP9_B1_EXT .......................................................................... 41
8.3 Activate BC Set /OTX/VIM75_SP9_INBOUND ....................................................................... 41
8.4 Import transports with perspective layouts for Fiori Apps ........................................................ 41
8.5 Support for leasing invoice: Integration between VIM X SAP leasing solution (VIMI-
22546)...................................................................................................................................... 42
8.5.1 New Role and Template for leasing invoice ............................................................... 42
8.5.2 New process types for leasing invoice ....................................................................... 43
8.5.3 New BDC Procedures for leasing invoice .................................................................. 45
8.5.4 New process options for leasing invoice .................................................................... 48
8.5.5 Defining user process options .................................................................................... 51
8.5.6 New document type for Leasing Invoice .................................................................... 53
8.5.7 Document Type determination for Leasing Invoice .................................................... 58
8.5.8 Inbound field mapping for Leasing Invoice ................................................................. 58
8.5.9 Logic Module processing for Leasing Invoice ............................................................ 59
8.5.10 VIM Analytics (New) configuration for Leasing Invoice .............................................. 60
8.6 Support Bill of Lading functionality (VIMI-16647) .................................................................... 60
8.6.1 Activating Bill of lading configuration to document types ........................................... 60
9 Optional Post Installation Activities ........................................................................................... 66

9.1 Change log entries for COA deleted users are maintained when upload function in full
mode is executed (VIMI-19181) .............................................................................................. 66
9.2 Pop up in Web Approval Portal when balance is not equal to zero (VIMI-21270) .................. 66
10 Known issues ............................................................................................................................... 67

10.1 VIMI-16647 .............................................................................................................................. 67
10.2 VIMI-20385 .............................................................................................................................. 67
10.3 VIMI-23411 .............................................................................................................................. 67
10.4 VIMI-23376 .............................................................................................................................. 67
11 Contact information ..................................................................................................................... 68
4
1 Introduction
These Release Notes provide an overview of OpenText™ Vendor Invoice Management for SAP®
Solutions Version 7.5 SP9, including new features, delivery information, and supported platforms.
OpenText recommends that you read these Release Notes in conjunction with the documentation
included with the software package. If any conflicts exist, the Release Notes supersede the other
documentation.
We also recommend that you check OpenText My Support (https://support.opentext.com) for any
patches or documentation updates that may have been posted after the initial release of this product.
1.1 Release Notes revision history
Revision date Sections revised Description of revisions
2019-04-30 First release. All new content.
Updated terms of the limited use of Business

2019-05-16 Packaging and Delivery
Center
2 About OpenText™ Vendor Invoice Management for

SAP® Solutions
This section provides an overview of OpenText™ Vendor Invoice Management for SAP® Solutions
Version 7.5 SP9.
Welcome to OpenText Vendor Invoice Management (VIM). VIM is an add-on that works with existing
SAP ERP systems to streamline accounts payable operations.
Support Package 9 (SP9) contains quality improvements as well as enhancements for OpenText
Vendor Invoice Management 7.5. Therefore, the installation of SP9 requires the prior installation of
VIM 7.5 SP8. Ensure that you install new Support Package stacks regularly to prevent problems that
have already been corrected, from recurring in the VIM solution.
Caution
Read these Release Notes completely BEFORE applying VIM 7.5 SP9 and follow the
instructions given.
Support Package 9 applies to the following versions of VIM 7.5:
• OpenText Vendor Invoice Management 7.5 for SAP ERP 6.0 (including SAP Suite on HANA, S/4
HANA Finance and SAP Simple Finance)
5
• OpenText Vendor Invoice Management 7.5 Edition for S/4 HANA on Premise: Please see
limitations listed in release notes “OpenText Vendor Invoice Management 7.5 S4HANA Release
Notes” (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/61907298)
2.1 General Data Protection Regulation (GDPR)

The General Data Protection Regulation (GDPR) is a new European Union (EU) law that gives
residents greater protection and control of their personal data. It will regulate the data that companies
in and outside the EU can collect, store, and transfer – as well as how they use it. All companies that
process EU resident data must be ready to comply when the GDPR enforcement starts on May 25,
2018.
SAP S/4HANA provides a superior level of user security and data protection features. VIM as add-on
package profits from the high standard of S/4HANA compared to outside-in solutions with their own
database, duplication of data and lower level security concepts.
Software solutions like VIM cannot be or not to be GDPR compliant. Every customer using SAP
S/4HANA and VIM is responsible to provide GDPR compliance in their organization.
Several VIM features and additional details listed in product documentation can help clients to
achieve GDPR compliance.
6
3 Installation
This chapter gives some hints for the installation of Support Package 9 for Vendor Invoice
Management (VIM) 7.5. For the detailed installation description read the VIM 7.5 Installation Guide.
3.1 SAP Prerequisites

Make sure that you already have VIM 7.5 SP8 installed.
Caution
Any repairs made to the VIM objects will be overwritten by SP9.
3.2 Prerequisites on Archive Server (VIMI-4180)

VIM 7.5 is able to work with any archive that is compatible with SAP ArchiveLink. If you are using
OCR option or the Approval Portal, you must have a content repository that supports the SAP Content
Server HTTP 4.5 Interface.
7
4 New Features
4.1 Change log entries for COA deleted users are maintained
when upload function in full mode is executed (VIMI-19181)
It is now possible to log the changes of COA deleted user along with new or modified user records.
This is applicable only where uploading of COA User map entries are done in full mode.
New Z-constant ‘IAP / COA_UPLOAD_FMODE_LOG’ to be set in SM30 to enable the functionality.
4.2 PDF log is updated for goods receipt posted outside VIM (VIMI-
19766)
The details of how the payment block was resolved and by whom are now shown in the history and
PDF log of the DP document when quantity block of an invoice is released.
4.3 Document rejected from BC workplace is also set to obsolete

in VIM (VIMI-20724)
When an inbound document is rejected from BC workplace the DP document status is also set to
obsolete.
4.4 Vendor specific tolerance are also factored for balance

calculation error and tolerance checks for a PO invoice. (VIMI-
20731)
The tolerance group maintained in SAP vendor master is also considered for triggering exception
‘Tolerance exceeded’ and balance error calculation for a PO invoice.
8
4.5 Warning popup for non-zero balance invoice in Web Approval
Portal (VIMI-21270)
In Web Approval Portal while approving an invoice with non-zero balance a warning popup has been
introduced for user to decide whether to correct the balance or proceed to the next approver.
If the Z-constant ‘IAP / BALANCE_MESSAGE_TYPE’ if set to ‘W’, the approver can correct the
balance or proceed to the next approver. In case the Z-constant is set to ‘E’ then the approver must
correct the balance before proceeding with approval process.
4.6 Populating relevant tax codes based on reporting country

(VIMI-21627)
By default, tax code drop-down list in indexing/approval screen populate relevant tax codes of
invoiced country. However, other tax codes can be populated by providing reporting country key by
using the ‘Change Rep. Country’ push button in VIM similarly to SAP screens.
The reporting country push button is enabled only when “Plant abroad” is activated in SAP
customizing.
4.7 Display of multiple POs in VIM Analytics (VIMI-21764)

When more than one purchase order is used in the invoice, VIM Analytics will be displaying an
asterisk in place of the PO number. Clicking on the field will bring up a list with all PO numbers used.
It is also possible to navigate to individual POs by clicking on their numbers in the list.
4.8 The business rule ‘Invalid Vendor VAT number’ validates Tax
Number 5 (VIMI-22002)
The business rule ‘Invalid Vendor VAT number’ is extended to validate the Tax Number 5 (STCD5)
entered in the indexing screen.
4.9 Improvements in handling different currencies in Mobile

Approval Portal (VIMI-22128)
In Mobile Approval Portal the amount field will be updated as per configured decimal notations of
invoice currency.
9
4.10 Date Selections for Data Archiving report (VIMI-22283)
The selection criteria in Archiving Report has been extended to 'Document Date', ‘Posting Date’ and
'Document Change Date' to archive the DP documents based on the values entered in the respective
fields.
4.11 Enter Cost Assignment Advanced Fiori app (VIMI-22342)

A new Fiori App, “Enter Cost Assignment Advanced” is now provided to support coding on line item
level. The app simplifies entering the cost assignment for Non-PO invoices. This app is designed to
support all coders dealing with simple and complex invoices like in Web Approval Portal. The app
provides an alternative way of coding for Web Approval Portal in Fiori with some feature limitations.
See VIM Configuration Guide for more details.
4.12 Debit / Credit indicator in line item of a DP document is preset

based on VIM Transaction / event type (VIMI-22618)
Based on Transaction / event type in Basic Data tab of indexing screen, the debit / credit indicator for
the line items of an invoice are automatically preset.
4.13 Accessibility of commonly used VIM screens for JAWS user

(VIMI-22273,22356,22393,22681)
Tool-tips and shortcuts are added to commonly used screens such as VIM Analytics, VIM Workplace,
Indexing screen, Approval screen for better accessibility.
4.14 Processing of Leasing invoice from VIM (VIMI-22546)

The SAP solution for lease contract management is part of SAP Flexible Real Estate module (SAP
RE-FX) which is integrated with SAP FI, CO and AA. As part of the integration between VIM and SAP
leasing solution the following functionalities have been implemented.
• Automatic determination of Leasing Invoice – with New classifier

• Leasing Invoice fields in Indexing screen & VIM analytics
• Identifying the correct Leasing Contract – Valid and active contracts
• Enabling the Leasing Invoice for online posting
For more information on leasing invoice processing, see the latest version of VIM Scenario Guide.
4.15 PO proposal support extended for freight invoices through Bill

of Lading (VIMI-16647)
Bill of lading is a unique number that is entered on a GR and can then be referenced in an invoice for
delivery costs. The field “Bill of lading” is available at the header level when a goods receipt is posted
in transaction MIGO. The following functionalities have been implemented in VIM for this release.
• Support of multiple bill of lading numbers for multiple freight condition vendors & multiple
PO’s.
• Bill of lading invoice fields in Indexing screen & VIM Analytics.
10
• Identify correct vendor & PO based on bill of lading number. Popup screen to select one
freight vendor among list of vendors.
• Enabled bill of lading invoice for online posting.
For more information on processing of Pos using bill of lading, see the latest version of VIM User
Guide.
4.16 E-Invoice processing for Italy and Germany (VIMI-21314)

VIM is introducing new modules to support the processing of electronic, XML-based, invoices.
The new features include processing modules and configuration based on Business Center Inbound
that allows starting VIM process with Early Archiving (OAWD file upload) or E-Mail. Existing VIM 7.5
customers who upgraded from VIM 7.0 and using VIM Incoming Document Handler framework (IDH)
will be able to use new IDH modules to start VIM process.
An option to interact with e-invoice delivery systems such as PEPPOL based on SAP eDocument
Framework and the integration with SAP eDocument Solution is planned to be provided by
OpenText. This will allow the process to be fully automated and will support feedback functions
required by many country standards.
The modules based on BC Inbound are delivered with the component OTBCSL03. The modules
based on IDH are included into the main VIM support package delivery. Provided baseline
configuration supports processing of e-invoices for Italy (FatturaPA) and Germany (XRechnung).
For more information on e-invoice processing, see the latest version of VIM Scenario Guide.
4.17 De-installation option for OTEXVIM 7.5 (VIMI-22263)

It is now possible to technically remove the VIM 7.5 OTEXVIM add-on from the SAP system. Deletion
of an add-on like VIM is considered an exceptional case and all consequences must be considered,
like data loss of transactional data stored in VIM tables. For De-installation of the OTEXVIM 7.5
component OpenText requires customers to open a ticket at OpenText Customer Support for VIM to
discuss details of the planned deletion and get information about the process.
11
5 Packaging and Documentation
Downloads and documentation for OpenText Vendor Invoice Management for SAP Solutions are
available on the OpenText Knowledge Center (https://knowledge.opentext.com/).
5.1 Packaging and Delivery Information

The components and packages updated with this SP are listed below. For a complete list of all
available components please see the VIM 7.5 Installation Guide and the release notes documents for
support packages SP1 through SP9.
5.1.1 ABAP Package

To install SP9, you need the following files:
SAP Version File for Support Package
TB40020073437_0000008.PAT
SAP ECC 6.0
(Follow the KC path: VIM 7.5 SP9 for ECC6.0/S4HANA ->
otexvim_sp9_750.sar)
Location on OpenText My Support:
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=75935214
Note: For S/4 HANA, there is an additional component OTVIMS4, delivered in VIM 7.5 SP4
(installation file OTVIMS4_INST_750_S4.SAR). It has to be installed, but there are no such additional
files delivered with 7.5 SP9. See the Release Notes of VIM 7.5 SP4.
5.1.2 Language Package

16 languages are included in the cumulative language package for VIM 7.5 SPX:
VIM7.5SP9_16Lans.sar (provided in the download file vim7.5sp9_16lans.zip).
NOTE: the language packages will be provided for download by May, 2019.
12
5.1.3 Non-ABAP Packages
Component Packages
Use the files located in

VIM Approval Portal OAP 7.5 SP9
im_approval_portal7_5sp9.zip:
• IM_APPROVAL_PORTAL7_5SP9.sca,
IM_APPROVAL_PORTAL7_5SP9.sda - either. SCA or
.SDA file should be deployed.
• opentext.zip - extract this ZIP into the standard
installation folder specified in VIM Installation Guide.
Use the files located in

VIM Approval Portal OAP 7.5 SP9
im_approval_portal7_5sp9_jco3.zip:
on JCo3
• IM_APPROVAL_PORTAL7_5SP9.sca,
IM_APPROVAL_PORTAL7_5SP9.sda - either. SCA or
.SDA file should be deployed.
Note: For JCo3 1.8, use the files located in
IM_APPROVAL_PORTAL7_5SP9_JCo3_JAVA1_8.zip
• opentext.zip - extract this ZIP into the standard
installation folder specified in VIM Installation Guide.
Notes:
• In VIM 7.5 SP9, no new support package for Supplier Self Service Lean Variant Component
(HANA Cloud) is needed, please continue to use the package delivered with VIM 7.5 SP5.
• In case you need an Approval Portal 7.5 SP9 Java version 1.8 build compatible with JCo2,
there is a special download package. Contact OpenText Customer support referring VIMI-
23469.
• Similarly, for Approval Portal 7.5 SP9 Java version 1.6 JCo2, contact the Customer Support
referring VIMI-23468.
5.1.4 Business Center – VIM upgrade from lower support package level
When upgrading to VIM 7.5 SP9 with an existing BC 10.x / 16.0 installation, upgrade to Business
Center Version 16.3.3 is a must (see the next section) if VIM uses any component of Business Center
(for example Business Center Inbound or the Business Center Fiori App).
13
5.1.5 Business Center for SAP Solutions – Limited Use
OpenText Business Center for SAP Solutions, also known as SAP Digital Content Processing by
OpenText, can be purchased as a standalone product.
Starting with VIM 7.5 SP 2 (VIM 7.0 SP 6), VIM customers are entitled to use OpenText Business
Center for SAP Solution Foundation - ABAP (BCSF) to implement additional aspects of their Accounts
Payable process. For the purpose of the limited use, OpenText Business Center can be downloaded
from OpenText My Support. Note that it is not available for SAP Marketplace unless you purchase a
standalone license - this is not the scope of the limited use.
The VIM license covers usage and support of the BCSF for processing incoming documents of the
following type:
• Invoices, Credit Notes, and similar invoice types plus

• Order Confirmations and Delivery Notes, if you licensed “SAP Inv Mgmt by OpenText for SAP
S/4HANA” (7020106) from SAP or “Vendor Invoice Management for SAP Solutions”
(1000048169) from OpenText.
The limited use of BCSF includes:
• Processing of licensed documents in the SAP “Order-to-Pay” process.

• Adding Business Center processing steps to the workflow for licensed incoming documents.
Examples of use cases are: use of the generic Fiori Task App, use of the Business Center Workplace,
creation or change of vendor master triggered by an incoming document, creation or change and re-
approval of an SAP purchase order triggered by a price difference in the invoice or order confirmation,
creation of goods receipts.
As part of the limited use, VIM 7.5 SP 2 / VIM 7.0 SP 6 and higher are providing VIM Fiori apps.
These Fiori apps are based on the generic Fiori Task App of OpenText Business Center for SAP
Solutions Foundation. Furthermore, an integration of VIM work items and exceptions into Business
Center Workplace is possible.
For the list of supported browsers and mobile devices, check the latest version of the Release Notes
for Business Center for SAP Solutions.
Make sure to review OpenText Business Center 16.3 Release Notes and documentation in addition to
VIM release notes and documentation.
5.1.6 Business Center - downloading components required for different

scenarios
The following table lists components of OpenText Business Center for SAP (BC, also known as SAP
Digital Content Processing by OpenText), that are required to be installed on your systems depending
on the scenarios you use VIM for. It also explains where each component has to be downloaded from.
Two groups of scenarios are to be distinguished, where BC components are required:
14
Inbound – processing of incoming invoices through scanning via OCR (ICC, BCC), email,
IDOC, Ariba Network etc.
Fiori Apps – using Fiori Apps provided with VIM (Approve Invoices, Enter Cost Assignment
and others), with the exception of VIM Invoice Analysis Fiori app.
Note that two components delivered with VIM 7.5 SP4 for VIM Invoice Analysis Fiori app, OTVIMWUI
and OTVIMWSR, have no dependency on BC and are not discussed in this chapter.
The BC components and the components based on BC that are required for each scenario are
marked in the table. The different components are not necessarily to be installed on the same server.
A diagram with a system landscape example later in this chapter will help you to understand that.
BC Fiori Install SPs

component Description Inbound apps
OTBCBAS Business Center Base – Basic Functions and x x SAP/OT OT
Data definitions
OTBCINB Business Center Inbound – Inbound functions x x SAP/OT OT
(OCR, Email, IDOC, etc.)
OTBCFND Business Center Foundation – Process- and x x SAP/OT OT
UI - Framework
OTBCSL00 Business Center Solution Base – Basic x x OT OT
solution functions
OTBCWSR Business Center Web Service – OData service x SAP/OT OT
definition and implementation
OTBCWUI Business Center Web UI – Fiori app and x SAP/OT OT
templates
OTBCSL30 * Business Center VIM Base – Data Dictionary x x OT OT
definitions for VIM BC Inbound (OTBCSL03)
and Fiori Solutions (OTBCSL33)
OTBCSL03 * Business Center VIM Foundation – Inbound x x OT OT
and BCC
OTBCSL33 * Business Center VIM Web Services – OData x OT OT
service definition, implementation and
backend functionality of VIM Fiori apps
OTBCUS03 * Business Center VIM Web UI – VIM specific x OT OT
UI views
Note: The last four components marked with asterisk in the table belong to VIM Solution based on
BC. The corresponding installation files and support packages can be found in VIM patches folders on
Open Text My Support.
Legend for download information (columns Install/SPs):
The column Install indicates where the packages for the initial installation of the component
or upgrade packages need to be downloaded from. The column SPs indicates where the
support packages need to be downloaded from.
SAP/OT: customers who purchase Business Center through SAP (as SAP Digital Content
Processing) receive the packages from SAP Marketplace. Customers who purchase Business
15
Center directly from Open Text or those who plan to use Business Center for invoice
processing within the scope described in the chapter “Business Center Foundation (ABAP) –
Limited Use” download the packages, including installation packages, from Open Text My
Support.
OT: download the packages from Open Text My Support. This includes both scenarios: fully
licensed Business Center (through SAP or Open Text) as well as the limited use scenario.
For your convenience, a directory tree with links for all downloads of BC and BC based VIM solution
is provided on OpenText MySupport, “Patches” area of VIM, in the folder “Business Center for SAP
Solutions 16.3”:
The downloads tree is organized per BC 16.3 release and update package. To download the required
components:
1. Select the packages (including the exact support package level files) according to the
compatibility table in the next section. You will need to select the right BC release and update
package corresponding to your VIM support package level.
2. Starting with the base BC 16.3 installation and going up the eventual BC update packages
(see the next section for updates information) download all components linked there.
3. If installing on S/4HANA, download ACP files. They may also be needed sometimes in
upgrade scenarios.
4. Download language packs. All language packs are cumulative. The links to the latest ones
are provided.
16
5.1.7 Business Center – compatibility and support package information
The following table lists release and support package level of each Business Center component that
is required for specific VIM version and support package level.
VIM release VIM 7.5 SP6 VIM 7.5 SP7 VIM 7.5 SP8 VIM 7.5 SP9
name
BC release name BC 16.0 update BC 16.3 or 16.3.1 16.3.2 16.3.3

2
OTBCBAS 0700_003 SP1 – 0700_004 or 0700_004 SP 0002 0700_004 SP 0003

delivered with BC
16.0 update 1 0700_004 SP 0001
OTBCINB 0700_003 SP1 – 0700_004 or 0700_004 SP 0002 0700_004 SP 0003

delivered with BC
16.0 update 1 0700_004 SP 0001
OTBCFND 0700_003 SP2 0700_004 or 0700_004 SP 0002 0700_004 SP 0003
0700_004 SP 0001
OTBCSL00 0700_003 SP1 – 0700_004 or 0700_004 SP 0002 0700_004 SP 0003

delivered with BC
16.0 update 1 0700_004 SP 0001
OTBCWSR 0740_003 SP1 – 0740_004 or 0740_004 SP 0002 0740_004 SP 0003

delivered with BC
16.0 update 1 0740_004 SP 0001
OTBCWUI 0740_003 SP3 0740_004 or 0740_004 SP 0002 0740_004 SP 0003
0740_004 SP 0001
OTBCSL30 0700_003 SP2 0700_004 0700_004 SP 0001 0700_005
Installation package
OTBCSL03 0700_003 SP2 0700_004 0700_004 SP 0001 0700_005
OTBCSL33 0700_003 SP2 0700_004 0700_004 SP 0001 0700_005
17
VIM release VIM 7.5 SP6 VIM 7.5 SP7 VIM 7.5 SP8 VIM 7.5 SP9
name
BC release name BC 16.0 update BC 16.3 or 16.3.1 16.3.2 16.3.3

2
OTBCUS03 0740_003 SP2 0740_004 SP1 – 0740_004 SP 0002 0740_004 SP 0003

installation and SP1 and 0740_004 SP delivered with 7.5
delivered with 7.5 SP7 0003 SP8.No new package
for VIM 7.5 SP9
The packages for Business Center based VIM Solutions are delivered as install/upgrade packages.
The file names for the latest Installation packages of those components, being delivered with VIM 7.5
SP9 are listed in the table below.
Component Release SAP OCS Filename OCS Package Password

Release
OTBCSL30 0700_005 700 QAR0020073437_0000250.PAT SAPK- 8B87CA35AF

005COINOTBCSL30
OTBCSL03 0700_005 700 QAR0020073437_0000246.PAT SAPK- 8B87CA36AC

005COINOTBCSL03
OTBCSL33 0700_005 700 QAR0020073437_0000249.PAT SAPK- 8B87CA35AC

005COINOTBCSL33
The installation package files and language packs for those components can be downloaded from
OpenText My Support, VIM 7.5 SP9 area.
5.1.8 Business Center - installation

Detailed information about the installation steps of Business Center are provided in the Business
Center Installation Guide.
The following two lists display the order in which the BC- and BC-based components have to be
installed, separately for typical gateway (Fiori) server and VIM backend systems. The set of
components to be installed depends on the scenarios – see the overview table earlier in this
document. The installation sequence relates to initial installation. Installation of SPs can either be
done in one step with the initial installation or they can separately be installed in the same sequence
as the installation packages.
Note that for each component installation or support package, there may be additional steps
to be performed like activating BC sets or installing language packs. Read the Release Notes of
each VIM support package and BC update to find those.
18
Order of installation on a gateway system:
1. OTBCWUI
2. OTBCUS03
Order of installation on a VIM backend system:
1. OTBCBAS
2. OTBCINB
3. OTBCFND
4. OTBCSL00
5. OTBCSL30
6. OTBCSL03
7. OTBCWSR
8. OTBCSL33
5.1.9 Business Center - ACP files

In case you are installing VIM, BC or BC based components on an S/4HANA system or performing a
conversion, ACP files will be needed to proceed. Those can be downloaded from Open Text My
Support as described below.
Components OTEXVIM, OTVIMARB, OTVIMCDS, OTVIMS4, OTVIMWSR, OTVIMWUI:
On Open Text My Support, Patches area for Vendor Invoice Management 7.5 – note the separate
folders that exist for S/4HANA 1511 and 1610 and above. Direct link to the Patches area:
Components OTBCBAS, OTBCINB, OTBCFND, OTBCWSR, OTBCWUI:
NOTE: With Business Center 16.3, ACP files normally will not be required anymore for main BC
components. The links below are provided for your information and may be useful for older versions.
On Open Text My Support, Patches area for Business Center 16 Update 1. Direct link to the folder
with ACP files:
Component OTBCSL00:
On Open Text My Support, OpenText Developer Network, Community Library area for Business
Center 16 update 1 Solution Accelerators. Direct link to the folder with ACP files:
Component OTBCSL30, OTBCSL03, OTBCSL33, OTBCUS03:
On Open Text My Support, in the Patches area for Vendor Invoice Management 7.5 SP 5, under
Business Center solution downloads. Direct link to the folder with ACP files:
19
5.1.10 Business Center - system landscape example

Note that depending on your system landscape, different BC components will not be necessarily
installed on the same server. The illustration below provides an overview on where the specific
components are to be installed. For more information, see Business Center Installation Guide
(chapter 4).
Warning
Installing the Business Center Web Services (OTBCWSR) and VIM Web
Services (OTBCSL33) on a different system than the Business Center
Foundation (OTBCFND) and VIM Foundation (OTBCSL03) is not supported.
20
5.1.11 Additional Packages for Fiori Apps
Several additional packages are delivered along with this SP that are required for VIM Fiori apps. The
table below lists the delivered files, specifying the related deployment scenario. All files are to be
found in the same directory where the components packages for VIM BC solution are located.
File Name Description Deployment

scenario
VIM Fiori Apps’ perspectives layouts (a
fiori_perspectives_layouts.zip transport) On-premise
Pre-configured tiles and target mapping for

vendorinvoicemanagement-
VIM Fiori Apps (a transport) On-premise
launchpadcontent.zip
Pre-configured Fiori Launchpad portal site
neo_VendorInvoiceManagement- for VIM Fiori Apps (a package to be
SCP
LaunchpadContent.zip imported on the cloud platform)
VIM Fiori Apps UI (a Fiori app package to be

vim_neo_ui_03.zip imported on the cloud platform) SCP
VIM Supplier Self Service registration UI (a

Fiori app package to be imported on the
otusrregui_neo.zip SCP
cloud platform)
All the above additional packages can be downloaded from OpenText My Support, VIM 7.5 SP9 area.
5.2 Documentation
For the latest updates of the User Guide, Installation Guide, Configuration Guide, Administration
Guide, Reference Guide, and Scenario Guide, refer to the VIM 7.5 SP9 documentation set available
in OpenText Knowledge Center.
The VIM 7.5 SP9 User Guide is available in English language only.
The VIM 7.5 SP4 User Guide is available in the following languages: Chinese, Dutch, English,
French, German, Italian, Japanese, Portuguese, Russian, and Spanish.
21
6 Supported Environments and Compatibility
6.1 Compatibility Matrix
For details on compatibility between OpenText products, refer to the Compatibility Matrix
(https://knowledge.opentext.com/go/matrix ) in the OpenText Knowledge Center.
6.2 Language Support

OpenText™ Vendor Invoice Management for SAP® Solutions 7.5 SP9 is currently localized in the
following 17 languages (including EN).
Component Languages
EN DE JA FR IT ZH ES RU HU RO PT
VIM 7.5 SP9 B UI UI UI UI UI UI UI UI UI UI
NL TR PL CZ SK KO
VIM 7.5 SP9 UI UI UI UI UI* UI
New Language KO (Korean) has been added
UI = user interface only

B = both user interface and configuration screens
UI*: Language SK (Slovakian) is partly available. Components deprecated in VIM 7.5 and all Central
Reports are not translated. In Web Approval Portal and Mobile Approval, SK is only available for the
new Web and Mobile UI.
Together with VIM 7.5 SP9, a new cumulative language pack will be provided. You need this language
pack, if you did not install the initial language pack of VIM 7.5 along with the installation package.
The package can be imported after VIM 7.5 SP9 is installed. Initial language package of VIM 7.5 is
not required.
Language Package name: VIM7.5SP9_16LANS.SAR
The Language Package can be imported using the SMLT transaction. It can be imported multiple
times for several languages.
22
Note
• VIM 7.5 SP9 provides translations in other languages than English only for end
user screens (transactions and reports used in a production system by non-
technical users). Translation (other than English) is not provided for configuration
screens.
• Language packages for the supported languages are available on OpenText My

Support in the corresponding patch area.
• The installation package for VIM 7.5 SP9 contains only English.
• Please see the known issue in the Known Issues section.
• Fiori Apps Approve Invoices, Enter Cost Assignment and Resolve Invoice
Exceptions and others delivered with VIM 7.5 SP9 support only 9 languages as
they are built on BC16.x that currently supports only 9 languages .
• Fiori Invoice Analysis app currently supports only English.
6.3 Approval Portal Downward Compatibility Matrix

The following table lists the supported combinations of the Web Approval Portal (OAP) and the VIM
backend versions.
OAP 7.5 SP4
OAP 7.5 SP5
OAP 7.5 SP6
OAP 7.5 SP7
OAP 7.5 SP8
OAP 7.5 SP9

OAP 7.5 SP1
OAP 7.5 SP2
OAP 7.5 SP3
Compatibility
Matrix VIM 7.5
VIM 7.5
VIM 7.5 SP1
VIM 7.5 SP2
VIM 7.5 SP3

to VIM 7.5
SP9
Legend:
Some of the features are only partially supported. It is strongly recommended to have a
completely supported stack.
23
6.4 Supported Web Browsers
The following table lists the supported combinations of web browsers and the Web Approval Portal
versions:
Web Browser Supported Browsers and Versions

Support Matrix
IE7 IE9 IE10 IE11 IE FF Chrome Safari
Edge
IE8
OAP 7.5 SP1 (new UI)

to OAP 7.5 SP3 (new
UI)
OAP 7.5 SP4 (new UI)

and above
Note
To support HTML5 and the latest web technologies, we are using a new web application
framework since VIM 7.0 SP2, which does not support old browser versions like Internet
Explorer 8 and earlier. If you are still using IE9 or IE10, you may be confronted with
remarkable performance issues as these browsers do not meet the technical
requirements anymore. Therefore, the support of these old browser versions is limited. In
midterm, these browser versions will not be supported anymore.
Firefox is supported for version 17 and later.

Google Chrome is supported for version 22 and later.
Safari is supported for version 5.0 and later.
OpenText recommends using the latest browser version.
24
6.5 Supported Operating Systems for Mobile Devices
The following table lists the supported combinations of the operating systems for mobile devices and
the Web Approval Portal versions:
Mobile devices
OAP 7.5 SP1
OAP 7.5 SP4
OAP 7.5 SP5
OAP 7.5 SP6
OAP 7.5 SP7
OAP 7.5 SP8
OAP 7.5 SP9

OAP 7.5 SP2
OAP 7.5 SP3

matrix
OAP 7.5
iOS (9.0)
iOS (10.0)
iOS (11.0)
iOS (12.0)
Android (> 6.0)
Note
In general, you can view the Mobile Approval Portal inside the browsers on all kind of
Android devices. Due to the diversity of physical Android devices, OpenText cannot
guarantee 100% compatibility on all functionality that the Mobile Approval Portal offers.
Please consider the list of all supported browsers also.
6.6 Web Viewer support

The following table lists the supported combinations of Web Viewer and the OpenText Approval Portal
versions:
Supported Web Viewer versions

Web Viewer
support matrix 10.5 16
Web Mobile Web Mobile
OAP 7.5 SP7 and above
25
Note
Supported document types are JPG, TIF and PDF. For the rest of document types,
OpenText recommends that you test this combination in the test environment before
moving on to the production.
6.7 Brava View support

The following table lists the supported combinations of Brava View and the OpenText Approval Portal
versions:
Supported Brava View versions

Brava View
support matrix 16.2
Web Mobile
OAP 7.5 SP7 and above
Note
Supported document types are JPG, TIF and PDF. For the rest of document types, it is
recommended to test this combination in test environment before moving on to the
production.
6.8 VIM Fiori Apps: Variants

The following table lists the supported variants of VIM Fiori apps:
26
On- Desktop Tablet Smart
Fiori App Cloud
Premise Phone
Approve Invoice
Enter Cost Assignment Simple
Enter Cost Assignment Advanced
My Approved Invoice Fiori App
Quantity and Price Fiori App
Resolve Invoice Exceptions
Supplier Self Service
Bulk Approve
SAP WEBGUI Workplace
SAP WEBGUI Analytics
Note
SAP WEBGUI Workplace and SAP WEBGUI Analytics supported only on SAP Fiori FES
5.0 (SAP Note 2618605)
6.9 VIM Fiori Apps: SAP UI5 Version Compatibility

The following table lists the supported combinations of VIM Fiori app Versions with SAP UI5 version:
SAP UI5 Supported SAP UI5 versions

Version
support matrix 1.4x 1.5x 1.6x
27
VIM 7.5 SP7/
- -
VIM 16.3 SP1
VIM 16.3 SP1 - -
VIM 7.5 SP8/

-
VIM 16.3 SP2
VIM 7.5 SP9/

-
VIM 16.3 SP3
7 Fixed issues
7.1 Document Processing (DP)
VIMI-21644
When PO is having mix of limit and service lines and if one of the limit lines is marked for deletion,
service lines are not proposed. Only open limit lines are proposed.
VIMI-21747
Error M8 416 - "Quantities and units of measure not permitted" occurs when posting a Service PO
invoice in background (BDC 6).
VIMI-21786
PO line determination does not work in case of partial field match when there are several GR’s for the
same PO.
VIMI-21821
Improvements in the logic for determination of RFC destinations for remote calls in VIM.
VIMI-21839
Payment terms in accounting document changed from FB02 transaction are not reflected correctly in
the DP document and in VIM Analytics report.
VIMI-21870
For a blocked invoice, when subsequent credit/debit is posted from the 'Short pay' option, no DP
document is created for subsequent document.
28
VIMI-21954
When using ‘Return to Vendor’ process option, the archived email shows the requester as a recipient,
although the corresponding option was not checked.
VIMI-21961
When saving business place and section code in the indexing screen, an error message "Business
place/Section Code XXXX in company code XXXX does not exist" appears.
VIMI-21971
"Balance not zero (PO)" exception triggers incorrectly for service invoice even when the balance is
shown as zero in indexing screen.
VIMI-22024
When a DP document is created from the transaction /OPT/VIM_7AX1, one-time vendor address
should get auto populated from PO in indexing screen.
VIMI-22063
Even after a Non-PO invoice with three-digit company code is posted, the DP workflow is still in "wait
for confirmation" state.
VIMI-22103
The ‘Currency Mismatch’ exception is incorrectly triggered when the currency of the freight price
condition in a PO is different from the currency stated in the header of a DP document.
VIMI-22143
Short dump occurs when clicking process options while logged in unsupported language.
VIMI-22144
Tax code is displayed twice in indexing screen when global SAP setting “Show keys within drop down
lists” is selected.
VIMI-22149
The re-run rules report (/OPT/DR_BR_WAIT) incorrectly processes the documents although rescan is
not completed.
VIMI-22150
When SRM email is triggered, the document status in process history is incorrectly shown as 'Approval
Cancelled'.
VIMI-22159
In case of service invoice with multiple POs, exception “Service entry required” is only checked for the
first line item PO and not for the second line item with different PO.
VIMI-22180
Customizable tax amount (TAXAMT_1, TAXAMT_2 and TAXAMT_3) field labels and values in
indexing screen are mapped incorrectly.
29
VIMI-22196
Fields in the profitability segment pop up with standard configuration ‘Under not used category’ are
not shown in posted document.
VIMI-22211
When PO invoice posting fails, the next workflow step is sent to the last referred agent instead of the
agent assigned to the corresponding process type.
VIMI-22281
Integrated asset acquisition posting document is not created for Non-PO invoice with assets.
VIMI-22305
The ‘Tolerance exceeded’ exception is triggered incorrectly when processing a GR based invoice with
line items with surcharge in a PO.
VIMI-22360
When entering large amounts in the line item tab in indexing screen for currency with no decimals
(example CLP) system errors out with message ‘CX_SY_CONVERSION_OVERFLOW’.
VIMI-22398
The invoice is getting incorrectly blocked by price or quantity when there are multiple line items in
goods receipt.
VIMI-22399
The tax code search help to display values with respect to chosen reporting country and not others.
VIMI-22415
The BADI ‘/ORS/VALIDATION’ does not check all invoice lines completely and exits after first line item
validation.
VIMI-22433
Background posting of an invoice referring a service PO fails when the distribution indicator for
multiple account assignment is equal to space.
VIMI-22435
The ‘Validate coding’ check in PO Reference tab does not show error messages.
VIMI-22454
The exception ‘Tolerance exceeded’ triggers incorrectly for invoices for custom duty and import
procurement.
VIMI-22455
During PO invoice posting, a warning message 'Terms of Payment in Purchase Order differ from
current terms' appears for multiple service PO’s with the same delivery note.
VIMI-22493
Exchange rate is not getting picked when the country code is not maintained in ‘Characteristic specific
attributes’ configuration.
30
VIMI-22495
During coding upload amount field with negative sign in the Excel file results in a short dump.
VIMI-22498
When subsequent debit document is processed for a PO invoiced in full, tolerance check exception
406 does not get triggered.
VIMI-22504
Translations for the data elements in the 'Propose Lines' sub screen are not maintained for few
languages (DE/ES/FR/PT).
VIMI-22629
Line item proposal for service PO fetches wrong details due to improper sorting of items in the service
entry sheets.
VIMI-22654
The exception ‘Tolerance exceeded’ is triggered for PO price discrepancy and not for quantity
discrepancy.
VIMI-22708
During online posting of PO invoice error occurs if SAP SP level is lower than ECC 6.0 EHP6 and
multiple account assignment is used in the PO.
VIMI-22733
The process history tab view for invoice approvals in Unified Dashboard displays only first comment
even when multiple comments exist against one exception in DP document.
VIMI-22737
When auto-coding is enabled, gross amount is blank and tax amount is filled, the line item amount
becomes negative and short dump occurs.
VIMI-22745
Tax code search help does not bring relevant tax codes when country key is empty for a DP
document.
VIMI-22748
The ‘Generate Preview’ button on the Return to Vendor screen errors with message
‘ILLEGAL_SUBSTRING_MODIFICATION’ when custom fields are used in the RTV mail template.
VIMI-22751
When working on same session on both Non-PO and PO invoices, the system shows incorrect
warning message for non-mandatory fields.
VIMI-22754
When reading the process history from the Unified Dashboard using JAWS screen reader, 'Time zone'
field is incorrectly read as input enabled field.
31
VIMI-22759
The suspected duplicate exception is not triggered for PO invoices due to incorrect condition check on
material document with accounting document.
VIMI-22779
An error occurs while displaying business partner details from indexing screen. A new Z-constant 005
/ FILL_MM_FI_BPROLE has been introduced to allow implementing a user exit for business partner
role determination. The template function module /OPT/VIM_TEMPLATE_FILL_BP_ROLE is to be
used for creating custom logic for filling MM/FI BP Roles.
VIMI-22833
An error occurs if date field values in coding upload file are not in system format YYYYMMDD.
VIMI-22838
A warning is not displayed if the profitability segment data is not saved in the indexing screen.
VIMI-22861
Time out error occurs while posting PO invoice with large number of delivery notes.
VIMI-22917
Using the process option ‘Post Goods Receipt’ from indexing screen for an invoice with multiple
follow-on documents results in incorrect vendor data.
VIMI-22925
During posting of service PO when both GR-based IV flag and S-Based IV flag is enabled, and
distribution indicator for multiple account assignment is set as 3 (Distribution by amount), BDC error
M8-321 ("Document contains same order item more than once") occurs.
VIMI-22938
The Z-Constant DASHBOARD_NO_LOGO does not disable the logo on Unified Dashboard.
VIMI-22981
For scheduling agreement PO invoice error occurs incorrectly "Item XXX delivered quantity smaller
than invoiced quantity" even though the quantity invoiced is same as GR quantity.
VIMI-22996
When processing a service PO invoice with multiple account assignment (based on amount), a
balance error occurs although balance is zero.
VIMI-23011
Balance error message incorrectly appears while posting a PO invoice in background when GR-IV
flag is unchecked in PO Invoice tab and good receipt flag is unchecked in PO delivery tab.
VIMI-23021
For a service PO invoice, material description is not transferred to indexing screen line items when
invoice lines are replaced/copied from PO proposal.
VIMI-23087
32
When a DP document is set to obsolete, the existing comments of that document are added to the
obsolete reason comments.
VIMI-23111
When using PO proposal for line items with category 'E', a short dump occurs in the indexing screen.
VIMI-22753, VIMI-22754, VIMI-22820, VIMI-22355, VIMI-22375, VIMI-22379, VIMI-22516, VIMI-

22795, VIMI-22826, VIMI-22841, VIMI-22883, VIMI-22938 –
Below accessibility improvements of commonly used VIM screens for JAWS screen reader have been
implemented -
•
▪ New VIM Analytics selection screen tool-tips have been added to radio button and
drop-down fields to identify the group it belongs to.
▪ VIM workplace “Execute” option has also been added to the context menu
▪ VIM Workplace comments section, the comment boxes have been pre-appended with
a header stating Process Comments or Approval Comments
▪ Tool-tips with full text have been added to various buttons in Indexing Screen, New
VIM Analytics report screen and VIM Workplace.
▪ Tool tip has been added in Indexing Screen for the Info icon (shown prior to the
exception text) in tab-strip.
▪ In blocked invoice dashboard’s Info section tool-tips have been added to the fields to
identify the group or column it belongs to.
▪ Push buttons handled separately from “read-only” or “menu” buttons.
• New shortcuts have been added in indexing screen to direct the focus to three main parts of
screen - Process options, Tab-strip, Detail pane docker
• Focus is set to first entry for “My Inbox”,” My Pending” and “My Completed” tabs in VIM
Workplace and in VIM Analytics report.
7.1.1 Tax and Withholding tax related issues
VIMI-21847
In withholding tax tab of indexing screen, the base amount is not calculated when there are multiple
withholding tax types based on gross and net.
VIMI-21862
In case of background posting of a PO invoice with Indian GST, the error "The tax amount must not
be greater than the tax base" occurs when assessable value is entered in line items.
VIMI-21939
For Non-PO invoice in context of Indian GST withholding tax amount is calculated incorrectly for TAN
based exemption configured at vendor level.
VIMI-21973
Manually entered withholding tax amounts are overwritten when switching between the tabs in
indexing screen.
33
VIMI-22126
For PO invoice in the context of Indian GST, tax amount is calculated incorrectly when the calculation
is based on quantity.
VIMI-22148
Extended withholding tax table is not enabled for input after clicking 'Retrieve WHT' button in indexing
screen.
VIMI-22179
For PO invoice in the context of Indian GST withholding tax amount is calculated incorrectly for TAN
based exemption configured at vendor level.
VIMI-22251
The withholding tax amount is calculated incorrectly when external tax system is used for calculation.
VIMI-22312
For Non-PO invoices the withholding tax tab in indexing screen shows blank amount when VAT tax
codes are configured as modified tax amount.
VIMI-22361
For PO invoices the withholding tax tab in indexing screen shows blank amounts when VAT tax codes
are configured as modified tax amount.
VIMI-22374
Based on the tax code and the tax rate Canadian tax jurisdiction code is not getting populated in the
indexing screen.
VIMI-22380
Withholding tax amounts changed in logic module are not getting saved and are overwritten by initial
values.
VIMI-22436
Withholding tax values are not re-calculated based on the changes are made in business place or
section code in indexing screen.
VIMI-22584
The tolerance check business rule is not triggered correctly when the configuration for routine ‘362’ in
the tax procedure is changed from ‘CalType’ to ‘BaseType’ or vice versa.
VIMI-22634
For Non-PO invoice in the context to Indian GST withholding tax amount is incorrectly calculated
when threshold value is maintained at CIN level in vendor configuration.
VIMI-22637
The withholding tax amounts are incorrectly calculated and posted when withholding tax rate is
maintained zero.
34
VIMI-22726
For Non-PO invoice with tax base amount entered in line item tab of indexing screen "Balance in
transaction currency” error incorrectly occurs.
VIMI-22766
Withholding tax amount becomes empty when line items in indexing screen are sorted in ascending
order based on amount.
VIMI-22827
For freight invoice withholding tax amount is calculated for vendor not subjected to withholding tax.
VIMI-22909
For SAP basis release 740 or higher, the BAPI PO invoice posting logic for withholding tax calculation
runs into error (PERFORM_PARAMETER_MISSING).
VIMI-22943
Withholding tax items in the indexing screen are not in the same order as in vendor master.
VIMI-23274
PO invoice withholding tax amount is calculated incorrectly when the ‘Base amount reduction” check
box is enabled in the withholding tax type configuration.
7.2 Document Processing (DP) – Logic Modules

VIMI-21864
The logic module for PO processing (G_SPEC_001) also considers deleted PO line items.
7.3 Invoice Approvals
VIMI-21564
Invoice cannot be approved when there are only special handling instructions and no line items.
VIMI-21919
When deleting records via COA file upload report the counter values in COA are not getting adjusted.
VIMI-22015
In case of Non-PO invoice with any line item amount less than the withholding tax amount, approvals
are not possible and error occurs "System error: Amount field is negative. Withholding tax base
amount exceeds amount of customer/vendor line item 001. Invoice ... Save Failed".
VIMI-22104
Incorrect entries are recorded in change logs when modifying entries in the COA maintenance
transaction.
35
VIMI-22167
The empty tax codes in a line item is getting automatically filled with header tax code in approval
screen for Non-PO invoices.
VIMI-22168
Short dump occurs when the coding template is uploaded from web GUI
VIMI-22171
For PO invoice when VAT number is derived from reporting country, the same is not shown in
accounting document.
VIMI-22521
For posted approval invoices rejected comments are not saved.
VIMI-22648
Coder level approval for a Non-PO parked invoice with the profitability segment data leads to system
error “No Batch input data for dynpro SAPLKEAK 0300”.
VIMI-22712
When an existing SAP user is deleted the approval workflow still gets triggered in case the user is
active in COA.
VIMI-22747
In COA approval limit tab the amount field does not allow more than 11 digits.
VIMI-22887
Invoices cannot be approved when Skip Approval Stack setting is set to 'S' in Auto Coding
configuration and single approver is maintained in COA.
VIMI-23024
The report to translate COA user data from lower to upper case does not translate the email field.
7.4 Web Approval Portal
VIMI-21796
History search based on the WBS element does not list invoices having multiple WBS elements in line
items.
VIMI-21867
Web Approval Portal which is hosted on NetWeaver server is generating redundant error message
logs.
VIMI-22260
Negative values entered in quantity field from Web Approval Portal causes short-dump when the
invoice is opened from SAP GUI.
VIMI-22757
The invoice list sorted by name is case sensitive.
36
VIMI-22808
For invoices with mixed credit and debit lines the vendor number and vendor name do not appear
In history search.
VIMI-23071
When customer number is entered in profitability segment popup from Approval Portal screen, the
error message KE 780 “Characteristics value does not exist for Characteristic Customer” appears.
VIMI-23262
The value for business area field is not displayed in bulk list page.
7.5 Fiori Approve Invoices app

VIMI- 22217
Long comments entered in Fiori Invoice Approval app are truncated in invoice history.
VIMI-22621
Substitute not able to open invoice in Fiori/Portal when SAP ID and OPTURA ID are different.
VIMI-22729
Load time is high for Fiori Invoice Approval app due to repetitive database selects on COA user map
table.
VIMI-22879
Fiori Invoice Approval app shows incorrect status message “/OTX/PS03_MSG 009 (Coding cannot be
completed in Fiori)” for invoice with multiple cost objects in line items.
VIMI-23388
Performance issue while loading the Fiori Approval app. New Z-constant IAP:
‘FIORI_BULK_PROCESS’ is introduced to skip the logic for last processed user and last processed
actions.
7.6 Fiori Enter Cost Assignment app

VIMI-22730
Selecting an override approver is not possible from Enter Cost Assignment app even though
approvers are maintained properly in COA.
VIMI-23108
When "auto-coding" option is used for an invoice, override approvers list is not displayed.
7.7 Fiori Confirm Quantity and Price app

VIMI-22391
GR delivery date changed from ‘Fiori Confirm Quantity and Price’ app does not get reflected in PO
history.
37
VIMI-22509
Short dump occurs due to currency conversion in ‘Fiori Confirm Quantity and Price’ app.
7.8 Fiori Exceptions app
VIMI-23355
When packed decimal field is configured for line items display, a short dump occurs in Fiori Exception
app.
7.9 Input Channels

7.9.1 Incoming Document Handler (IDH)
VIMI-21885
The IDH admin tool output layout has few fields labels missing or duplicated.
VIMI-22434
The tax amount does not add-up to total tax amount when incoming IDOC has 2 header lines.
VIMI-22740
Additional attachments are not created in satellite system when processed via email channel.
VIMI-22929
Tax report date is not populated when using IDOC inbound handler
(/OPT/DP_INBOUND_IDOC_PROC).
VIMI-23042
When subsequent credit is processed via IDOC, the runtime error 'CONVT_NO_NUMBER' occurs.
7.9.2 IDF Framework (BC Inbound)

VIMI-21849
The "Enter On" date does not appear in VIM Analytics for invoice processed via BC inbound mail
channel or IDOC.
VIMI-22650
For inbound IDOC unplanned delivery cost debit/credit indicator is not getting populated in DP
document, causing background posting failure.
VIMI-22668
Using the scan option with VIM Workplace with BC inbound framework, the displayed success
message does not include the DP document number.
7.10 Invoice Exception
38
VIMI-21262
When the process option 'Pay as invoiced' is executed for all line items, in the log the processor is
shown as the original user and not the current user.
7.11 VIM Notifications

VIMI-22506
If Z-constant 'REM_MAIL_DOCTYPE' is maintained with value 'RAW' emails are not getting triggered.
7.12 VIM Analytics (new VAN) Report and VAN Liability Report
VIMI-21620
Multi-backend VAN Report does not display the image of a DP document from the satellite system.
VIMI-21637
The aggregation report stops with a short dump TSV_TNEW_PAGE_ALLOC_FAILED when executed
for huge volume of data.
VIMI-21849
The "Enter On" date does not appear in VIM Analytics for invoice processed via BC inbound mail
channel and IDOCs.
VIMI-22765
For invoices in the approval process, the current agent is not displayed in VIM Analytics for non-SAP
user if an invoice is re-assigned.
VIMI-22870
When a wait role is configured for a process type, VIM Analytics does not show the wait role in the
current role when the relevant exception is triggered.
VIMI-22937
The exclude functionality for the ‘Overall Process Status’ field gives wrong results when VIM Analytics
report uses CDS views.
7.13 Central Reporting and Other Reports
VIMI-22624
Documents posted outside VIM are marked as first pass by aggregation report.
7.14 VIM Workplace

VIMI-21911
Invoices are not visible in the “My completed” tab of the final approver. Entries are reflecting only in
the “My pending” tab of the previous approvers.
39
VIMI-22226
When accessing VIM Workplace via WebGUI a short dump occurs after viewing a duplicate invoice.
VIMI-22273
The Execute option is not available in the context menu on VIM workplace output list. The Execute
option is only shown on Inbox tab and not on other tabs.
VIMI-22578
Comments are mandatory while referring invoices in bulk mode even though ‘Comment Required’
checkbox is de-activated.
VIMI-22516
Behavior of cursor is not consistent when switching in between tabs in VIM Workplace.
VIMI-22841
The labels of the text editor are displayed at the bottom after all the comments, creating an ambiguity
on the comments being read aloud by the screen reader.
7.15 Customizing
VIMI-22497
The process option definition maintenance view does not display authorization failure messages for a
user with only display access and trying to change the view data.
7.16 Others
VIMI-21809
The yearend program does not update the DP documents with new document numbers for PO
invoices.
40
8 Post Installation Activities
The following sections describe mandatory and optional configuration steps. The recommended way
to perform configuration changes, including activation of BC sets, is to do that in a reference client
first and then transport the configuration to other clients.
8.1 Activate BC Set /OTEXVIM/VIM75_SP9_CUSTOMIZING

This BC set contains table content changes of the VIM baseline customizing. If you are using the
standard baseline VIM customizing, you can activate the BC set without any concerns. In case you
have changed the VIM, baseline customizing, make sure the BC set will not overwrite any
customizing.
8.2 Activate BC Set /OTX/VIM75_SP9_B1_EXT

This BC set has to be activated in case the Fiori apps are used. In case you have changed the VIM,
baseline customizing for Fiori apps, make sure the BC set will not overwrite any customizing.
From the created customizing transport, manually remove the below table object entries before
releasing the transport to other clients:
/OTX/PF62_T_AALA
/OTX/PF62_T_AALH
/OTX/PF62_T_AALT
/OTX/PF62_T_AIAC
/OTX/PF62_T_AIAD
/OTX/PF62_T_AIAT
/OTX/PF62_T_AIC
/OTX/PF62_T_AIH
/OTX/PF62_T_AIHT
Import the attached transport D9PK902905 to other clients and ensure above table entries are
available the transport is provided in the file fiori_bcset_transportcontent.zip.
8.3 Activate BC Set /OTX/VIM75_SP9_INBOUND

This BC set has to be activated in case of BC inbound. In case you have changed the VIM, baseline
customizing for BC inbound, make sure the BC set will not overwrite any customizing.
8.4 Import transports with perspective layouts for Fiori Apps

Perspective layouts for Fiori apps are not included into 7.5 SP9 package. Unless additionally
imported, VIM Fiori apps item perspective layouts will not be loaded, and error popup will be shown
with the respective error message.
The following transports are provided:
D9PK902583
41
The transport is available as an additional file download in the directory of VIM 7.5 SP9 (similar to the
language transports).
The rest of this chapter describes post installation activities that are delivered with the BC set.
8.5 Support for leasing invoice: Integration between VIM X SAP

leasing solution (VIMI-22546)
To process Leasing Invoices in VIM, certain configuration steps are to be done. This configuration is
delivered with this support package’s BC set. The steps to create the same configuration manually
are described below.
8.5.1 New Role and Template for leasing invoice

Defining Roles
1. Run the /OPT/CP_9CX5 transaction. Alternatively, navigate to OpenText Vendor Invoice
Management > SAP menu> Roles > Role Maintenance.
2. Maintain the role data, using the following parameters:
• Product Code 005

• Role CONTR_MANAGER
• Description Contract Manager
Defining Role Templates
1. Run the /opt/cp_9cx2 transaction. Alternatively, navigate to OpenText Vendor Invoice Management
> SAP menu> Roles > Template Maintenance.
2. Maintain templates using the following parameters:
• Template Id FM_CONTRACT_MANAGER
• Description FM for contract manager
• Template Type Function Module
• Function Module /OPT/BL_ROLE_CONTRACT_MANAGER
42
Assigning Templates to Roles
1. Run the /opt/cp_9cx2 transaction. Alternatively, navigate to OpenText Vendor Invoice

Management > SAP menu> Roles > Template Maintenance.
2. In the Product Role Templates Configuration Overview screen, maintain the Product Role
Templates, using the following parameters:
• Product Code 005

• Responsible Party CONTR_MANAGER
• Template ID FM_CONTRACT_MANAGER
• Active Select the check box
8.5.2 New process types for leasing invoice

To support processing of leasing invoices, the following twenty-two new process types are introduced
to validate leasing related information.
• 450 Process Leasing Invoice (Leasing)

• 451 Invalid or missing Vendor (Leasing)
• 452 Invalid Currency (Leasing)
• 453 Invalid Requester ID (Leasing)
• 454 Suspected Duplicate (Leasing)
• 455 Missing Mandatory Information (Leasing)
• 456 Invalid Vendor VAT Number (Leasing)
• 457 Vendor Address Mismatch (Leasing)
• 458 Missing Invoice Date (Leasing)
• 459 Invalid Recipient VAT Number (Leasing)
43
• 460 Invalid Payment Reference (Leasing)
• 461 Missing Date of Supply (Leasing)
• 462 Invalid Company Address (Leasing)
• 463 Vendor Invoice Reference Missing (Leasing)
• 464 Missing Vendor Name (Leasing)
• 465 Missing Recipient Name (Leasing)
• 466 Validate Bank Details (Leasing)
• 467 Auto coding (Leasing)
• 468 Invalid Vendor Invoice Number (Leasing)
• 469 Validate Accounting Data (Leasing)
• 470 Missing Company Code (Leasing)
• 474 Invalid or missing contract (Leasing)
Note: These new customizing entries are included in the BC set delivered with the SP.
To define the process type:

1. Run the /n/OPT/VIM_8CX1 transaction. Alternatively, navigate to Vendor Invoice Management
> Document Processing Configuration > Process Configuration > Maintain Process Types.
2. To display the Process Type Definition Details screen, double-click a Process Type line.
3. Define the process types using the following parameters:
44
8.5.3 New BDC Procedures for leasing invoice
To support processing of leasing invoices, the following two new BDC procedures are introduced.
• 2201 Display RE contract

• 2202 Leasing Invoice Online Posting
To define the BDC procedure:

1. Run the /n/OPT/CP_9CX1 transaction. Alternatively, navigate to Vendor Invoice Management >
Document Processing Configuration > Process Configuration > Maintain BDC Procedures.
45
Define the BDC procedures with following parameters.
2201 – Display RE Contract
BDC Definition
Parameters
46
Transaction Data
2202 – Leasing Invoice Online Posting

BDC Definition
Parameters
47
Transaction Data
8.5.4 New process options for leasing invoice

To support processing of leasing invoices, the following three new process options are introduced to
perform activities like display real estate contract and post leasing invoice.
• 3003 Refer to Contract manager

• 3004 Display RE Contract
• 3005 Post Leasing Invoice
48
To define the process option: Run the /n/OPT/VIM_8CX2 transaction. Alternatively, navigate to
Vendor Invoice Management > Document Processing Configuration > Process Configuration > Maintain
Process Options.
Define the process options with following parameters.

3003 – Refer to Contract manager
Option Id 3003
Option Button Text Refer
Option Text Refer to Contract manager
Option Type Referral
Document Status Undefined
49
3004 – Display RE Contract
Option Id 3004
Option Button Text Display contract
Option Text Display RE Contract
Option Type BDC Action
BDC Configuration Id 2201
Document Status Undefined
3005 – Post Leasing Invoice

Option Id 3005
Option Button Text Post Leasing Invoice
Option Text Post Leasing Invoice
Option Type BDC Action
BDC Configuration Id 2202
Confirm Check Rules Select the check box
Document Status Document Created
50
8.5.5 Defining user process options
In this step, you define process options for each role. Process options are associated with the process
type.
To define user process options:

1. In the Process Type Definition Overview screen, select the process type and double-click User
Process Option in the navigation pane.
2. Enter the following parameters.
• Option ID: Process option identifier
• Description: Description of the option
• From Actor: Select the source role that gets the work item
• To Actor: Select the target role that receives the work item if the action is performed. This is
only available if the option is a referral.
• Check FM: Enter a check function module to restrict the option for a role.
Process options for process type 450: Process Leasing Invoice (Leasing)
51
Similarly, add the process options for remaining process types as shown in below screenshot.
Process options for all process types: 451 to 474.
52
8.5.6 New document type for Leasing Invoice
The document type is the key object in the DP component of VIM. The document type holds key
information about how the document is created in the system. New document type is introduced
wherein new classifier has been added for processing of leasing invoices in VIM.
To add the new document type REC_75:
Run the /OPT/VIM_1CX1 transaction. Alternatively, navigate to Vendor Invoice Management >
Document Processing Configuration > Document Type Configuration > Maintain Document Types.
53
Define the document type with the following parameters.
54
Adding process types to document type REC_75:
To define the process type determination sequence:

1. Run the /OPT/VIM_1CX1 transaction. Alternatively, navigate to Vendor Invoice Management
> Document Processing Configuration > Document Type Configuration > Maintain Document
Types.
2. In the Document Type Definition Overview screen, select the REC_75 document type and
double-click on Proc. Type. Det. Sequence.
55
To define sequence steps:
1. In the Proc. Type. Det.Sequence Overview screen, select a step and double click
Sequence Steps.
2. Open the Sequence Steps screen for process types and add the Fields or function
modules in following sequence.
Step Id Process type Step Seq. Field name Check Type Table Check Function
10 470 1 BUKRS Required Field
20 451 1 Function Module /OPT/VIM_DETERMINE_PROC_201
30 452 1 WAERS Table Field TCURC
40 463 1 XBLNR Required Field
60 454 1 Function Module /OPT/VIM_DETERMINE_PROC_DUP
110 458 1 BLDAT Required Field
130 461 1 SUPPLY_DATE Required Field
140 464 1 VEND_NAME Required Field
56
170 465 1 RECIPIENT_NAME Required Field
200 467 1 Function Module /OPT/VIM_DETERMINE_PROC_LIB003
210 469 1 Function Module /OPT/VIM_DETERMINE_PROC_LIB004
Configuring Index screen options for REC_75:
Configure the index screen options for leasing process types as shown in the following screenshots.
57
8.5.7 Document Type determination for Leasing Invoice
New document type determination procedure is defined in VIM to identify the leasing invoice type.
To maintain the procedure:
1. Run transaction /OPT/VIM_1CX9. Alternatively, follow the path Vendor Invoice Management >
Document Processing Configuration > Document Type Configuration > Maintain Document
Type Determination Procedure.
2. Create new doc type determination procedure with following step details.
8.5.8 Inbound field mapping for Leasing Invoice
To enable support for leasing invoices, new fields are introduced in VIM and OCR. To send these
details from OCR to VIM, perform the following field mapping.
To perform inbound field mapping:
1. Call transaction /OPT/SPRO and follow the path Vendor Invoice Management > Document
Processing Configuration > General Configuration > Incoming Document Processing > Maintain
Mapping ID > Field Mapping.
2. Select Mapping ID “ICC” and double-click “Field Mapping”. Add new entry with the following values:
58
8.5.9 Logic Module processing for Leasing Invoice
New logic module is introduced to determine leasing invoice data. To maintain the logic module
processing:
1. Call transaction /OPT/SPRO and follow the path Vendor Invoice Management > Document
Processing Configuration > Document Type Configuration > Logic Module Processing.
2. Create new module Id: ‘G_HEAD_021’ with the following details.
3. Select the module id and double click on Module processing steps. Choose the work area as
‘G_MAIN_001’, then add the new counter with above module id as shown in below
screenshot.
4. Click on Processing Mapping and add the new counter with document type and process Id.
59
8.5.10 VIM Analytics (New) configuration for Leasing Invoice
1. Call transaction /OPT/SPRO and follow the path Vendor Invoice Management > Cross
Component Configuration > VIM Analytics (New) > Maintain Customizing Profiles.
2. Select the profile ‘DEFAULT’ and double click on Define Field Mapping. Add the following
entries.
8.6 Support Bill of Lading functionality (VIMI-16647)

To process PO lines based on Bill of Lading, certain configuration steps are to be done. This
configuration is delivered with this support package’s BC set. The steps to create the same
configuration manually are described below.
8.6.1 Activating Bill of lading configuration to document types

Document type configuration – PO_75
The document type is the key object in DP component of VIM. It holds information about how the
document is created in the system.
8.6.1.1 Document Type configuration – PO_75
1. Run the /OPT/VIM_1CX1 transaction.

Alternatively, navigate to Vendor Invoice Management > Document Processing Configuration >
Document Type Configuration > Maintain Document Types.
60
2. At DP document type level select Index header configuration in the Document type definition
screen.
Maintain field BOL_LIST to display Bill of lading list button in main screen Basic Data tab.
Note: Please note to hide field “BOL_LIST” in document type “NPO_75” so that the Bill of lading list
button isn’t displayed for NPO invoices.
61
3. At DP document type level select Index item configuration to maintain field FRBNR.
8.6.1.2 Inbound field mapping for Bill of lading related fields.
BCC 16.6 is added with a new field “InvoiceBOL” in invoice application for all countries, this needs to
be mapped to its corresponding VIM Index screen field as shown.
8.6.1.3 Maintaining field labels for Bill of lading related fields.
Bill of lading screen fields added in VIM Indexing screen should have meaningful labels maintained in
system.
62
(A) Header level fields ->
(B) Item level fields ->
63
8.6.1.4 BDC configuration changes
BDC ID 1 – PO Invoice posting -> Online.
Bill of lading invoice feature in VIM is supported in VIM 7.5 SP 9 with online PO invoice posting
option. Background mode of invoice posting will be supported from VIM 7.5 SP 10.
Online posting -> BDC All screen mode -> Phase 1 -> VIM 7.5. SP 9.
For posting the DP documents with Bill of lading feature, use BDC 200 for online posting.
1. Maintain Process Options:
In VIM Customizing transaction /n/OPT/SPRO, navigate to below path:

Vendor Invoice Management -> Document Processing configuration -> Process Configuration ->
Maintain Process Options.
Process Option 2009 (Post PO Invoice) is configured with BDC configuration ID: 200 => PO Invoice
Posting Online –Special.
2. Enhancement Implementation for VIM Bill of lading invoice online posting functionality:
While posting PO invoice in MIRO transaction BDC for Bill of lading reference option, selected freight
vendor & PO coming from VIM screen must be captured for limiting PO line items proposal. This can
be achieved through enhancement implemented in MIRO transaction.
The following function needs to be plugged in using implicit enhancements:

Note: You must add the code at the begining of the form, just after the FORM statement.
/OPT/VIM_BOL_SELECT_VENDOR_GET
This function is used for fetching freight vendor and thereby filtering only freight vendor PO line items
in the invoice (include LMR1MF4N). Call this function inside the subroutine TAB_MULTIVEN_CHECK
64
********BEGIN OF CODE PIECE**************************
DATA: lv_lifnr TYPE lifnr,
lv_vim TYPE char1.
CALL FUNCTION '/OPT/VIM_BOL_SELECT_VENDOR_GET'

IMPORTING
EV_LIFNR = lv_lifnr
VIM = lv_vim.
IF lv_lifnr IS NOT INITIAL AND
lv_vim IS NOT INITIAL.
DELETE tab_multiven WHERE lifnr NE lv_lifnr.
ENDIF.
********END OF CODE PIECE****************************
65
9 Optional Post Installation Activities
The post installation activities described in this chapter are optional and not delivered with the BC set.
9.1 Change log entries for COA deleted users are maintained
when upload function in full mode is executed (VIMI-19181)
Feature is developed to log the changes of COA deleted user along with new or modified user
records. This is applicable only where uploading of COA User map entries are done in full mode.
New Z-constant ‘IAP / COA_UPLOAD_FMODE_LOG’ to be set in SM30 to enable the functionality.
9.2 Pop up in Web Approval Portal when balance is not equal to

zero (VIMI-21270)
In the Web Approval portal when trying to approve an invoice with non-zero balance warning popup is
issued to decide whether to correct the balance or proceed for next approval.
If the Z-constant IAP / BALANCE_MESSAGE_TYPE is set to ‘W’ approver can correct the balance or
proceed even without correcting the balance to approve the invoice. If the Z-constant is set to ‘E’
approver should correct the balance to proceed.
66
10 Known issues
The following known issues exist in this release.
10.1 VIMI-16647
Processing of invoices with Bill of lading number may cause short dump when using multiple backend
systems with different releases or support packages.
10.2 VIMI-20385
When using OCR option, VIM continues to create DP document even when image is not found due to
network issues in archive server.
10.3 VIMI-23411
Performance issue while loading VIM Fiori approval app and Bulk approval app.
10.4 VIMI-23376
Parked document coding is not supported by Fiori ‘Enter Cost Assignment Advanced’ app.
67
11 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1
OpenText My Support: https://support.opentext.com
For more information, visit www.opentext.com
Copyright © 2019 Open Text. All Rights Reserved.
Trademarks owned by Open Text. 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 or other respective owners.
68

OpenText Vendor Invoice Management 75 SP9 Release Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Vendor Invoice Management 75 SP9 Release Notes

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

for SAP® Solutions

Product Released: 2019-04-30

Release Notes Revised: 2019-05-16

2 About OpenText™ Vendor Invoice Management for SAP® Solutions ..................................... 5

4 New Features .................................................................................................................................. 8

5 Packaging and Documentation .................................................................................................. 12

6 Supported Environments and Compatibility ............................................................................. 22

7 Fixed issues .................................................................................................................................. 28

8 Post Installation Activities .......................................................................................................... 41

9 Optional Post Installation Activities ........................................................................................... 66

10 Known issues ............................................................................................................................... 67

11 Contact information ..................................................................................................................... 68

1.1 Release Notes revision history

Revision date Sections revised Description of revisions

2019-04-30 First release. All new content.

Updated terms of the limited use of Business

2 About OpenText™ Vendor Invoice Management for

Support Package 9 applies to the following versions of VIM 7.5:

2.1 General Data Protection Regulation (GDPR)

3.1 SAP Prerequisites

3.2 Prerequisites on Archive Server (VIMI-4180)

New Z-constant ‘IAP / COA_UPLOAD_FMODE_LOG’ to be set in SM30 to enable the functionality.

4.3 Document rejected from BC workplace is also set to obsolete

4.4 Vendor specific tolerance are also factored for balance

4.6 Populating relevant tax codes based on reporting country

4.7 Display of multiple POs in VIM Analytics (VIMI-21764)

4.9 Improvements in handling different currencies in Mobile

4.11 Enter Cost Assignment Advanced Fiori app (VIMI-22342)

4.12 Debit / Credit indicator in line item of a DP document is preset

4.13 Accessibility of commonly used VIM screens for JAWS user

4.14 Processing of Leasing invoice from VIM (VIMI-22546)

• Automatic determination of Leasing Invoice – with New classifier

4.15 PO proposal support extended for freight invoices through Bill

4.16 E-Invoice processing for Italy and Germany (VIMI-21314)

4.17 De-installation option for OTEXVIM 7.5 (VIMI-22263)

5.1 Packaging and Delivery Information

5.1.1 ABAP Package

SAP Version File for Support Package

Location on OpenText My Support:

5.1.2 Language Package

Use the files located in

Use the files located in

• Invoices, Credit Notes, and similar invoice types plus

The limited use of BCSF includes:

• Processing of licensed documents in the SAP “Order-to-Pay” process.

5.1.6 Business Center - downloading components required for different

Two groups of scenarios are to be distinguished, where BC components are required:

BC Fiori Install SPs

Legend for download information (columns Install/SPs):

BC release name BC 16.0 update BC 16.3 or 16.3.1 16.3.2 16.3.3

OTBCBAS 0700_003 SP1 – 0700_004 or 0700_004 SP 0002 0700_004 SP 0003

OTBCINB 0700_003 SP1 – 0700_004 or 0700_004 SP 0002 0700_004 SP 0003

OTBCFND 0700_003 SP2 0700_004 or 0700_004 SP 0002 0700_004 SP 0003

OTBCSL00 0700_003 SP1 – 0700_004 or 0700_004 SP 0002 0700_004 SP 0003

OTBCWSR 0740_003 SP1 – 0740_004 or 0740_004 SP 0002 0740_004 SP 0003

OTBCWUI 0740_003 SP3 0740_004 or 0740_004 SP 0002 0740_004 SP 0003

OTBCSL30 0700_003 SP2 0700_004 0700_004 SP 0001 0700_005

OTBCSL03 0700_003 SP2 0700_004 0700_004 SP 0001 0700_005

OTBCSL33 0700_003 SP2 0700_004 0700_004 SP 0001 0700_005

BC release name BC 16.0 update BC 16.3 or 16.3.1 16.3.2 16.3.3

OTBCUS03 0740_003 SP2 0740_004 SP1 – 0740_004 SP 0002 0740_004 SP 0003

Component Release SAP OCS Filename OCS Package Password