OpenText™ Vendor Invoice Management

for SAP®

Release Notes for Invoice Solution

Version 7.6

Product Released: 2020-10-30

Release Notes Revised: 2020-11-10

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

2 About OpenText™ Vendor Invoice Management for SAP® Invoice Solutions ........................ 5
2.1 General Data Protection Regulation (GDPR) ............................................................................ 5

3 Installation ...................................................................................................................................... 7
3.1 Prerequisites on Archive Server (VIMI-4180) ............................................................................ 7

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

4.1 Adjustment of business rules 170/270 “Validate Bank Details" for Swiss QR invoices
(VIMI-25852) .............................................................................................................................. 8
4.2 Support for handling of QR bill info (VIMI-25674) ..................................................................... 8
4.3 New business rule to validate Swiss QR Bills (VIMI-25758) ..................................................... 8
4.4 IDOC support enabled for Swiss QR Bills (VIMI-25780) ........................................................... 8
4.5 Support of tax amount in local currency for PO and Non-PO invoices (VIMI-17473) ............... 8
4.6 Support the process of the electronic invoice in VIM for India (VIMI-25653) ............................ 8
4.7 Support for online dynamic translation between languages of user comments (VIMI-
24561)........................................................................................................................................ 9
4.8 Smart coding for Non-PO invoices (VIMI-24558) ...................................................................... 9
4.9 IES enablement for China (VIMI-26105) ................................................................................... 9
4.10 IES enablement for Russia (VIMI-26106) .................................................................................. 9
4.11 PDF rendering for XML invoices (VIMI-25041).......................................................................... 9
4.12 Fiori New Invoices Report App (VIMI-26174) ............................................................................ 9
4.13 Performance improvements in Fiori Enter Cost Assignment Advanced App and Fiori
Invoice Approval App (VIMI-25657) ........................................................................................... 9
4.14 Enablement of "Allow Substitutions" filter in the "My Approved Invoices" app (VIMI-
25100)...................................................................................................................................... 10
4.15 Support to Approval Portal migration to JCo 3.1 and SAP NetWeaver 7.5 (VIMI-
25082)...................................................................................................................................... 10
4.16 Enabling the option for maintaining the workflow substitutes in Fiori (VIMI-24552)................ 10
4.17 Integration of dynamic translations API for comments in Fiori Enter Cost
Assignment Advanced App and Fiori Invoice Approval App (VIMI-25971) .............................. 10
4.18 Improved display of the last processor and comments in Fiori Invoice Approval Bulk
Mode App (VIMI-24872) .......................................................................................................... 10

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
2
4.19 Update of the Fiori Invoice Approval app to use the latest Fiori features from the BC
framework (VIMI-24548) .......................................................................................................... 10

5 Packaging and Documentation .................................................................................................. 11

5.1 Packaging and Delivery Information ........................................................................................ 11
5.1.1 ABAP Packages ......................................................................................................... 11
5.1.2 Language Package ..................................................................................................... 11
5.1.3 Non-ABAP Packages ................................................................................................. 12
5.1.4 Business Center – VIM upgrade from lower support package level .......................... 12
5.1.5 VIM Framework and Additional Components ............................................................. 13
5.1.6 Components required for different scenarios ............................................................. 13
5.1.7 Compatibility and support package information ......................................................... 15
5.1.8 Flexible installation of Framework and Inbound components .................................... 15
5.1.9 Additional Packages for Fiori Apps ............................................................................. 18
5.1.10 Packages and Transports for Additional Scenarios .................................................... 19
5.2 Documentation ........................................................................................................................ 19

6 Supported Environments and Compatibility ............................................................................. 20

6.1 Compatibility Matrix ................................................................................................................. 20
6.2 Language Support ................................................................................................................... 20
6.3 Approval Portal Downward Compatibility Matrix ..................................................................... 21
6.4 Approval Portal JCo Compatibility Matrix ................................................................................ 21
6.5 Supported web browsers ......................................................................................................... 22
6.6 Supported Operating Systems for Mobile Devices.................................................................. 23
6.7 Web Viewer support ................................................................................................................ 23
6.8 Brava View support.................................................................................................................. 24
6.9 VIM Fiori Apps: Variants .......................................................................................................... 24
6.10 VIM Fiori Apps - BC UI - SAP UI5 Version Compatibility......................................................... 26

7 Fixed issues .................................................................................................................................. 26

7.1 Document Processing (DP) ..................................................................................................... 26
7.2 Invoice Approvals .................................................................................................................... 32
7.3 Invoice Exception .................................................................................................................... 33
7.4 VIM Notifications ...................................................................................................................... 34
7.5 VIM Analytics (new VAN) Report and VAN Liability Report ..................................................... 34
7.6 Central Reporting and other reports ........................................................................................ 36
7.7 VIM Workplace ........................................................................................................................ 37
7.8 Web Approval Portal ................................................................................................................ 38
7.9 Fiori Approve Invoices app ...................................................................................................... 38

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
3
7.10 My Approved Invoices app ...................................................................................................... 39
7.11 Fiori Enter Cost Assignment Advanced app ............................................................................ 39
7.12 Fiori Invoice Exceptions app.................................................................................................... 39
7.13 Fiori Confirm Quantity or Price app ......................................................................................... 39
7.14 Incoming Document Handler (IDH) ......................................................................................... 39
7.15 IDF Framework (BC Inbound) ................................................................................................. 40
7.16 Others ...................................................................................................................................... 41

8 Post Installation Activities .......................................................................................................... 42

8.1 Activate General Invoice Solution BC Set(s) ........................................................................... 42
8.2 Activate BC Set /OTEXVIM/VIM76_FIORI .............................................................................. 42
8.3 Activate BC Set for Inbound .................................................................................................... 42
8.4 Review Known Issues ............................................................................................................. 43

9 Known issues ............................................................................................................................... 43

10 Contact information ..................................................................................................................... 45

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
4
1 Introduction
These Release Notes provide an overview of OpenText™ Vendor Invoice Management for SAP®
Invoice Solutions Version 7.6, 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

2 About OpenText™ Vendor Invoice Management for

SAP® Invoice Solutions
This section provides an overview of OpenText™ Vendor Invoice Management for SAP® Invoice
Solutions Version 7.6.

Welcome to OpenText Vendor Invoice Management (VIM). VIM is an add-on that works with existing
SAP ERP systems to streamline accounts payable operations.

The major package contains quality improvements as well as enhancements for OpenText Vendor
Invoice Management 7.6.

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 regulates 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 with the GDPR.

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.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
5
Software solutions like VIM cannot be or not 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.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
6
3 Installation
This chapter gives some hints for the installation of Support for Vendor Invoice Management (VIM) 7.6.
For the detailed installation description read the VIM 7.6 Installation Guide.

3.1 Prerequisites on Archive Server (VIMI-4180)

VIM 7.6 can 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.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
7
4 New Features
OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 includes the following new
features and changes compared to OpenText™ Vendor Invoice Management for SAP® Solutions 7.5.

4.1 Adjustment of business rules 170/270 “Validate Bank Details"

for Swiss QR invoices (VIMI-25852)
For Swiss QR invoices the business rule 170/270 is applicable only when the invoice bank details are
available in vendor master. When the invoice bank details are new and different from vendor master
the business rule will not trigger exception.

4.2 Support for handling of QR bill info (VIMI-25674)

Two new fields have been introduced for Swiss QR invoices (PO and Non-PO) to support structured
and unstructured information in basic data tab. The two fields are available in the table
/OPT/VIM_1HEAD as QR_STRUC_INFO and QR_UNSTR_INFO. Standard mappings are provided
for OCR scenarios. Information on the mapping is available in the Post Installation Activities section
(chapter 9) of this document and in the Scenario Guide.

4.3 New business rule to validate Swiss QR Bills (VIMI-25758)

A new business rule "Invalid QR Bill data " is provided to validate data of Swiss QR Bills. See VIM
Scenario and Reference Guides for more information.

4.4 IDOC support enabled for Swiss QR Bills (VIMI-25780)

IDOC field mappings are now provided for Swiss QR Bills, according to the IDOC format introduced
by the SAP Note 2913397.

4.5 Support of tax amount in local currency for PO and Non-PO

invoices (VIMI-17473)
Support of tax amount in local currency for PO and Non-PO invoices is provided in this release. The
new field is implemented to follow SAP customizing settings "Switch Off Tax Translation between Local
and Document Currency". This new function supported in online posting. For background posting,
implemented for BDC IDs 1, 42, and (on VIM 20.4) 2200, SAP note 276866 must be implemented.
Background posting support is currently limited to countries where tax base amount can be set
changeable (setting "Change Field Control for Tax Base Amount").

4.6 Support the process of the electronic invoice in VIM for India
(VIMI-25653)
As part of this feature new "Invoice Reference Number" field is introduced in basic data tab for
processing India GST data. This field holds 64 characters. Two new business rules are introduced which
are triggered if the field value is less than 64 characters: For PO (510) "Missing/Invalid Invoice

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
8
Reference Number (PO)" and for Non-PO (511) "Missing/Invalid Invoice Reference Number (NPO)".
BDC's 1, 6, 34, 40, 41 are enhanced to support posting of IRN into SAP.

4.7 Support for online dynamic translation between languages of

user comments (VIMI-24561)
VIM now supports users to translate the comments into preferred language using any online platforms
like Google APIs or SAP Translation Hub. This will help users understand the comments and process
the invoice accordingly. Support provided for the integration of an external web service for translation
of the process comments and approval comments maintained for the DP Documents in VIM Workplace,
VIM Analytics and VIM Indexing Screen. Information on the configuration is available in the Post
Installation Activities section (chapter 9) of this document.

4.8 Smart coding for Non-PO invoices (VIMI-24558)

Smart coding automatically searches and analyses historical data to propose account assignment for
non-PO invoices. The system learns from posted invoices and detects similar invoices to apply
account assignment automatically based on confidence. Dialog users can call the proposal in Fiori
and SAPGUI screens. Machine Learning assists end users and provides increased automation.

4.9 IES enablement for China (VIMI-26105)

Country specific fields for China are now supported in IES recognition and extraction, with VIM
mappings provided in baseline configuration.

4.10 IES enablement for Russia (VIMI-26106)

Country specific fields for Russia are now supported in IES recognition and extraction, with VIM
mappings provided in baseline configuration.

4.11 PDF rendering for XML invoices (VIMI-25041)

New functions to create PDF rendering of electronic (XML) invoices have been introduced in this
release. See VIM Reference Guide for more details.

4.12 Fiori New Invoices Report App (VIMI-26174)

Vendor Invoices Report Fiori App provides comprehensive invoice details like VIM Analytics. This Fiori
App allows to navigate into standard SAP Fiori to view for purchase order and vendor using semantic
objects. Vendor Invoices Report provides invoice process history, approval history and comments with
translation capabilities.

4.13 Performance improvements in Fiori Enter Cost Assignment

Advanced App and Fiori Invoice Approval App (VIMI-25657)
This feature is introduced to speed up the inbox loading time and invoice detail page loading of the
Enter Cost Assignment Advanced and Invoice Approval Fiori Apps.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
9
4.14 Enablement of "Allow Substitutions" filter in the "My Approved
Invoices" app (VIMI-25100)
Invoices approved on behalf are displayed in the "My Approved Invoices" app using the new "Allow
Substitutions" filter.

4.15 Support to Approval Portal migration to JCo 3.1 and SAP

NetWeaver 7.5 (VIMI-25082)
From this release, Approval Portal Java 1.8 version is upgraded to JCo3.1 from the version JCo3.

4.16 Enabling the option for maintaining the workflow substitutes in

Fiori (VIMI-24552)
User can now manage their substitutes using the “Maintain substitutes” option which appears at user
level settings in Enter Cost Assignment Advanced, Enter Cost Assignment Simple, Invoice Approval,
Invoice Bulk Approval Fiori apps. This feature is as per standard SAP Manage Substitute from My
Inbox.

4.17 Integration of dynamic translations API for comments in Fiori

Enter Cost Assignment Advanced App and Fiori Invoice
Approval App (VIMI-25971)
In the Enter Cost Assignment Advanced and Invoice Approvals Fiori Apps, the user entered
comments can be viewed with translated text based on the language selected by the user at the
Translate option in the Comments section.

4.18 Improved display of the last processor and comments in Fiori

Invoice Approval Bulk Mode App (VIMI-24872)
The last invoice processor and corresponding comments are now supported in additional use cases
and not only for higher level approvers.

4.19 Update of the Fiori Invoice Approval app to use the latest Fiori
features from the BC framework (VIMI-24548)
Invoice Approval app has been updated to use the latest FIORI features from BC Framework. This
also includes improvements of usability on mobile devices.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
10
5 Packaging and Documentation
Downloads and documentation for OpenText Vendor Invoice Management for SAP Invoice Solutions
are available on the OpenText Knowledge Center. (https://knowledge.opentext.com/).

5.1 Packaging and Delivery Information

For a complete list of all available components please see the VIM 7.6 Installation Guide.

5.1.1 ABAP Packages

To install VIM 7.6 Invoice Solution, you need the files listed in the table below. Depending on
scenarios, different packages may be needed to be installed. The later sections in this document
will help you to understand what is required for each scenario. You will find the information on VIM
Framework and Solution Base components in their respective release notes.

Component Package file name and OCS package name Installation password

OTEXVIM_80700_006.SAR 9082CC4BB8
OTEXVIM

OTBCSL30_80700_006.SAR 8B87C935AF
OTBCSL30

OTBCSL33_80700_006.SAR 8B87C935AC
OTBCSL33

5.1.2 Language Package

9 languages (DE, ES, FR, IT, JA, KO, NL, PT, RU) are included in the cumulative language package for
VIM 7.6: VIM7.6_9Lans.sar (provided in the download file vim7.6_9lans.zip).

NOTE: The language packages will be provided for download by end of November 2020.

The remaining language packages will be delivered later.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
11
5.1.3 Non-ABAP Packages

Component Packages

im_approval_portal7_6_jco3.zip
Approval Portal based on JCo3
Java1.6

im_approval_portal7_6_jco3_1_java1_8.zip
Approval Portal based on
JCo3.1 Java1.8

vim_20.4_vimi-26696_ci-16.zip
Approval Portal fix for JCo3
Java1.8

5.1.4 Business Center – VIM upgrade from lower support package level
When upgrading to VIM 7.6 with an existing BC 10.x / 16.0 installation, upgrade to VIM Framework
Version 20.4, that is a successor of Business Center, is a must (see the next section).

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
12
5.1.5 VIM Framework and Additional Components
VIM 7.5 customers could implement additional scenarios like inbound processing or Fiori apps based
on Open Text Business Center (also known as SAP Digital Content Processing). That also included
business solutions based on Business Center, for example for sales order processing.

Starting with VIM 7.6, all components that were formerly part of Business Center are now included
into VIM and are being sold as one product, for invoice and non-invoice solutions. This also includes
VIM Framework components, formerly BC Base and Foundation, now mandatory to be installed for all
scenarios.

The license unit of VIM has been changed from “invoices” to “documents”.

Note that in case you have installed Business Center 16.3 or older version, the technical components
like OTBCBAS will be replaced with ones containing “7.6” in their names.

The commercial license for VIM does not include any OCR options, that requires a separate license.

Make sure to review OpenText VIM Framework 7.6 Release Notes and documentation in addition to
VIM Invoice Solution Release Notes and documentation.

The following sections refer to invoice scenarios, and the term VIM will be used to refer to the
technical VIM product that automates and processes invoices.

5.1.6 Components required for different scenarios

In addition to the general invoice scenario, two groups of Accounts Payable scenarios are to be
distinguished, where BC components are required:

Inbound – processing of incoming invoices through scanning via OCR (ICC, BCC), email,
IDOC, Ariba Network, and so on.

Fiori Apps and BC Workplace – using Fiori Apps provided with VIM (Approve Invoices,
Enter Cost Assignment and others) and executing VIM invoice workitems from BC Workplace.

The components 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 is provided in VIM Installation Guide.

BC component Description General Inbound Fiori apps

invoice / WP
OTBCBAS Process Base (Framework) x x x
OTBCSL00 Solution Base - Basic solution x x x
functions
OTEXVIM VIM Invoice Classic x x x
OTBCWUI Web UI - Fiori app and x
templates

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
13
 BC component Description General Inbound Fiori apps
invoice / WP
OTBCSL30 Inbound solution x x
OTBCSL33 Fiori apps and BC Workplace x

Note that BC-based packages existing prior to VIM 7.6 have been reorganized:

• OTBCFND, OTBCINB and OTBCWSR – included into OTBCBAS

• OTBCUS03 – included into OTBCWUI

• OTBCSL03 – included into OTBCSL30

This reorganization is reflected in respective installation package attributes. The components that
have been moved to other components will be “removed” from your system once successor
components are installed, with all objects being kept.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
14
5.1.7 Compatibility and support package information
The following table lists release and support package level of each VIM component that is required for
specific VIM version and support package level.

VIM release VIM 7.6

and SP

OTBCBAS 0700_006

OTBCSL00 0700_006

OTEXVIM 80700_006

OTBCWUI 0740_006

OTBCSL30 80700_006

OTBCSL33 80700_006

5.1.8 Flexible installation of Framework and Inbound components

OpenText recommends to update all components of VIM regularly. Ideally the

versions correspond to the combinations listed in the previous section. If upgrading
VIM Invoice Solution is not possible, VIM supports the use of more recent versions of
VIM Foundation and Inbound components with older versions of VIM Invoice
Solution. This currently supports the following scenario:
• VIM Inbound component.
This allows you to use recently introduced inbound scenarios like integration
with OpenText™ Information Extraction Service for SAP® Solutions (IES) or
electronic invoices without upgrading VIM, by using the technical component
OTBCSL30.

Note: “Information Extraction Service” (“IES”) is used in this documentation

as a common technical term for both of the following OpenText products:
• OpenText™ Intelligent Capture for SAP® Solutions, formerly known as
OpenText™ Information Extraction Service for SAP® Solutions (IES on
premise)
• OpenText™ Core Capture for SAP® Solutions

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
15
 Notes:
• Flexible installation is not reflected in the SAP Maintenance Planner. If you
are using exclusively Maintenance Planner to manage your systems, flexible
installation is not possible. You must install components by downloading
them from OpenText MySupport and proceeding with SAINT or SPAM
transactions.
• If you use VIM only for non-invoice processes and it is not used for VIM
inbound scenarios for invoices, there are no restrictions on the combination
of VIM Invoice Solution and VIM Foundation versions.
• The flexible installation option does currently not support scenarios with
VIM Fiori apps. For VIM Fiori apps, you must use the versions as described
in “Selecting required components” on page 93 and “Compatibility and
support package information”.
The flexible installation is supported for VIM 7.5 SP5 and later Support Packages.
Business Center and Business Center based components like OTBCSL03 and OTBCSL30
must be based on VIM 7.5 SP10 and Business Center 16.3.4 or later, including VIM 7.6
Foundation. For more information, see the table below.

To import the transports for flexible installation:

2. Before installing the VIM Foundation and Inbound components, implement
manual correction instructions if mentioned in the table below.
3. Import the transports listed in the table, according to your current VIM version.
4. Activate the BC sets listed in the corresponding version of VIM Foundation. For
more information, see the VIM Foundation documentation.
5. Activate the BC sets listed for the VIM Invoice Solution Inbound scenario in the
VIM Release Notes that correspond to the Support Package level of the
components OTBCSL30.

Table 11-1: Transports for flexible installation

Compatibility
transports to
Current VIM Support Manual correction
import in case of
Package level instructions
OTBCSL30 based
on VIM 7.6
TAWK900022,
VIM_7.5_SP11- TAWK900010,
7.5 SP5, 7.5 SP6
VIMI-24759_CI-97 DM1K900314,
DW3K913415
TAWK900022,
TAWK900010,
7.5 SP7 TAWK900027,
DM1K900314,
DW3K913415
TAWK900032,
7.5 SP8 DM1K900314,
DW3K913415

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
16
 Compatibility
transports to
Current VIM Support Manual correction
import in case of
Package level instructions
OTBCSL30 based
on VIM 7.6
D9PK903015,
DM1K900314,
7.5 SP9
DM1K900314,
DW3K913415
7.5 SP10

7.5 SP11

All transport files listed in the table, along with the correction can be downloaded
from OpenText My Support:
https://knowledge.opentext.com/knowledge/cs.dll/Open/77743630

Installation examples
Example 1.
You currently use VIM 7.5 SP5. You want to use IES for OCR extraction and you
decide to use the inbound components delivered with VIM 7.5 SP10. Perform the
following steps:

To perform a flexible installation:

1. Implement the manual corrections from VIM_7.5_SP11-VIMI-24759_CI-97,
available for download in the same folder where you find the compatibility
transports.
2. Install the transports as listed in the table for VIM 7.5 SP5: TAWK900022,
TAWK900010, DM1K900314, DW3K913415.

3. Install Business Center 16.3 with Support Packages up to SP4: components

OTBCBAS, OTBCINB, OTBCFND, and OTBCSL00.

4. Install the VIM and Business Center based solution for VIM 7.5 SP10. This
includes the installation packages of OTBCSL03, 0700_005, and OTBCSL30,
0700_005, and the SP1 package of those components.
The installation packages are available in VIM 7.5 SP9. The SP1 packages are
available in VIM 7.5 SP10.
To be able to install the packages, you also need the ACP file provided in the
same download folder as the compatibility transports.
5. Activate the BC sets of Business Center 16.3.4 according to the Business Center
documentation.
6. Activate the BC sets for Inbound of the VIM and Business Center based solution.
The names are stated in the Post-Installation section of the VIM 7.5 SP9 and SP10
Release Notes: BC sets /OTX/VIM75_SP9_INBOUND for SP9 and /OTX/VIM75_-
SP10_INBOUND_EXT for SP

Example 2.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
17
 You currently use VIM 7.5 SP5. You want to use IES for OCR extraction and you
decide to use the inbound components delivered with VIM 7.6. Perform the
following steps:

To perform a flexible installation:

1. Implement the manual corrections from VIM_7.5_SP11-VIMI-24759_CI-97,
available for download in the same folder where you find the compatibility
transports.
2. Install the transports as listed in the table for VIM 7.5 SP5: TAWK900022,
TAWK900010, DM1K900314, DW3K913415.

3. Install VIM Framework 7.6: components OTBCBAS and OTBCSL00.

4. Install the VIM Invoice Base 7.6 component OTBCSL30.
6. Activate the BC sets for Inbound: /OTX/VIM76_SP_INBOUND_DELTA and then
/OTX/VIM76_SP_INBOUND.

5.1.9 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 Install on Deployment

scenario
Invoice Solutions-Launchpad Content.zip Pre-configured tiles and Front end On-premise
target mapping for VIM
Fiori apps (a transport)
neo-Invoice Solutions-Launchpad Pre-configured Fiori Cloud SCP
Content.zip Launchpad portal site
for VIM Fiori apps (a
package to be imported
on the SAP Cloud
Platform (SCP))
neo-Invoice Solutions_otusrregui.zip VIM Supplier Self Cloud SCP
Service registration UI
(a Fiori app package to
be imported on the SAP
Cloud Platform)
Invoice VIM Fiori perspectives Backend On-premise
Solutions_fiori_perspectives_layouts.zip layouts (transport)

Invoice VIM Fiori Customization Backend On-premise

Solutions_fiori_customizing_entries.zip entries (transport)

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
18
All the above additional packages can be downloaded from OpenText My Support, VIM 7.6.

5.1.10 Packages and Transports for Additional Scenarios

Several additional packages are delivered along with the product. The table below lists their technical
details. See the Installation and Configuration Guides for more information.

Component Description Package file name Installation

password

Integration with SAP Document OTBCSL38_80700_006.SAR 8B87C935A7

OTBCSL38 Compliance, based on VIM
Framework (BC Inbound)

Ariba Integration – for Business OTVIMARB_80700_006.SAR 2CE7D0734B

OTVIMARB Suite Adapter

Ariba Integration – for Cloud OTVIMARC_80700_006.SAR 8199C454C8

OTVIMARC Integration Gateway, based on
VIM Framework (BC Inbound)

Gateway component for Supplier OTVIMGW_80700_006.SAR 8199C251AB

OTVIMGW Self Service

VIM Invoice BW component OTVIMBW_INST_VIM700_700.SAR F17CB370FA

OTVIMBW
(includes 2 support packages) otvimbw_sp1.sar
otvimbw_sp2.sar

All the above additional packages can be downloaded from OpenText My Support, VIM 7.6.

Due to different technical limitations, some functions are being delivered as transports, to be
downloaded from OpenText MySupport:

additional_transport_withlayout_for_ecc6.0.zip – Transport EW3K901985 with ALV layouts for VIM

Analytics.

additional_transport_vatdate.zip - Transport TW6K900712 for VAT date BADI implementation.

vim-7.5-e-invoicing-idh-sap-dc.zip - Transport D5EK900398 for Integration with SAP Document

Compliance based on VIM 7.5 IDH.

5.2 Documentation
For the latest updates of the User Guide, Installation Guide, Configuration Guide, Administration
Guide, Reference Guide, Scenario Guide, and Security Guide, refer to the VIM 7.6 documentation set
available in the OpenText Knowledge Center:
https://knowledge.opentext.com/knowledge/cs.dll/Open/77741752

The VIM 7.6 User Guide is available in English language only.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
19
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® Invoice Solutions 7.6 is currently localized in the
following 17 languages (including EN).

For this SP, initially 9 language packs (DE, ES, FR, IT, JA, KO, NL, PT, RU) will be delivered as
cumulative package by end of November 2020. The remaining language packs will be delivered later.
See the known issues section.

Component Languages

EN DE JA FR IT ZH ES RU HU RO PT

VIM 7.6 B UI UI UI UI UI UI UI UI UI UI

NL TR PL CZ SK KO

VIM 7.6 UI UI UI UI UI* UI

UI = user interface only

B = both user interface and configuration screens
UI*: Language SK (Slovakian) is partly available. Components deprecated in VIM 7.6 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.6, a new cumulative language pack will be provided. The package can be imported
after VIM 7.6 is installed.

Language Package name: VIM7.6_9LANS.SAR

The Language Package can be imported using the SMLT transaction. It can be imported multiple times
for several languages.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
20
 Note
• VIM 7.6 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.6 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 SP11 support only 10 languages
as they are built on BC16.x that currently supports only 10 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 OpenText Approval Portal (OAP) and the
VIM backend versions.

Compatibility OAP 7.6

Matrix VIM 7.6

VIM 7.6

Legend:

Some of the features are only partially supported. OpenText strongly recommends to have a
completely supported stack.

6.4 Approval Portal JCo Compatibility Matrix

The following table lists the supported combinations of the OpenText Approval Portal (OAP) JCo
versions.

VIM OAP Version OAP 7.6/ OAP 20.4

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
21
 JCo3 + Java 1.6

JCo3 CI+ Java 1.8

JCo3.1+ Java 1.6

JCo3.1+ Java 1.8

6.5 Supported web browsers

The following table lists the supported combinations of web browsers and the Web Approval Portal
versions:

Supported Browsers and Versions

IE10 IE11 IE FF Chrome Safari

Edge

OAP 7.6

Note
If you are still using 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.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
22
6.6 Supported Operating Systems for Mobile Devices
The following table lists the supported combinations of the operating systems for mobile devices and
the OpenText Approval Portal versions:

Mobile Devices Matrix OAP 7.6

iOS (9.0) to (13.0)

6.7 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 20.3

Web Mobile Web Mobile Web Mobile

OAP 7.6

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.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
23
6.8 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.6

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.9 VIM Fiori Apps: Variants

The following table lists the supported variants of VIM Fiori apps:

On- Desktop Tablet Smart

Fiori App Cloud
premise Phone

Approve Invoice

Enter Cost Assignment Simple

Enter Cost Assignment Advanced

Vendor Invoices Report App

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
24
 My Approved Invoice Fiori App

Quantity and Price Fiori App

Resolve Invoice Exceptions

Supplier Self Service

Bulk Approve

SAP GUI for HTML - Workplace

SAP GUI for HTML - Analytics

Note
VIM Workplace and VIM Analytics in SAP GUI for HTML are supported only on SAP
Fiori FES 5.0 (SAP Note 2618605)

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
25
6.10 VIM Fiori Apps - BC UI - SAP UI5 Version Compatibility
The following table lists the supported combinations of VIM Fiori app versions with BC UI and SAP
UI5 version:

VIM Fiori - BC UI - SAP UI5 Compatibility Matrix

Frontend
OTBCWUI 0740_006
Backend

SAP UI5 1.52.*

VIM 7.6/VIM SAP UI5 1.60.*
20.4 SAP UI5 1.71.*

7 Fixed issues

7.1 Document Processing (DP)

VIMI-23331
Clicking on any text in SCE control for copying to “SGTXT” field in the line item of the indexing
screen is not working.

VIMI-24370
The rerun rules job goes into error as agents are not resolved when self-directed role is configured.

VIMI-24840
For a down payment invoice the expense type is not correctly derived when using the "Change
document type" process option.

VIMI-25011
The field “Requester E-mail” cannot hold more than 80 characters in the indexing screen.

VIMI-25046
When using process option "Delete and Restart", the new archive document type retains the value
from the old DP document for cases where there is a change in the country/company code.

VIMI-25078
The exception "Wait for GR - Enhanced Check (PO)" is triggered incorrectly when the PO invoice
includes GR line and Freight condition line for same PO item.

VIMI-25094

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
26
In the indexing screen, proposal for multiple service entry sheets fetches duplicate entries.

VIMI-25128
The duplicate records in the process tab are empty for PO invoices when the duplicate check
extension function is used.

VIMI-25163
In the indexing screen the process option “Change document type” takes long time to execute due to
locking of database tables.

VIMI-25214
During posting of a non-PO invoice BDC error "Balance in transaction currency" occurs for
mixed debit and credit line items when US tax jurisdiction codes and external tax system is
used.

VIMI-25229
The exception "Down payment clearing" does not get triggered for a reversed PO invoice.

VIMI-25260
The exception “Validate Bank Details” is not triggered when IBAN in the invoice is different from the
IBAN in the vendor master.

VIMI-25319
Performance improvements through enabling of buffering of the customizing tables.

VIMI-25330
When posting an invoice that refers to a service PO with multiple account assignment
distributed by percentage and proportionally, the amounts at the line item level are not split
correctly.

VIMI-25339
In DP indexing screen tax code determination is not fetched as per the reporting country.

VIMI-25408
The SAP document type for credit memo invoice is not determined correctly when using custom
function.

VIMI-25346
The exception "Invalid Tax Info" is incorrectly triggered when a G/L account is not tax relevant and tax
code in the line item of the indexing screen is blank.

VIMI-25431
When posting PO invoice in background using BDC 6, sporadically the invoice document number is
seen in VIM Analytics but the invoice document is missing in SAP and the workflow goes into error.

VIMI-25436

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
27
Posting of a PO invoice created using costing material in the purchase order is not possible due to
locks on material objects.

VIMI-25439
The exception “Tolerance exceeded” triggers incorrectly for a PO invoice when the invoice line item
and the PO line item have different order unit.

VIMI-25446
Tax is calculated twice when unplanned delivery cost is entered in the indexing screen.

VIMI-25463
The exception “GR Not Done - Simple Check (PO)” takes longer time than expected during simulation
of PO invoice.

VIMI-25472
Duplicate check functionality is not working for Non-PO invoices when multiple combinations are used
in duplicate check groups.

VIMI-25499
The exchange rate type 'M' is always used instead of the rate configured in the SAP
customizing to calculate invoice balance.

VIMI-25518
When the setting "SAP Tax Determination Logic with OT Tax Table" is used for tax
determination, and there are several tax codes with the same tax rate, the last maintained
tax code is always determined instead of the correct tax code.

VIMI-25528
An additional line item is added in the indexing screen when the line item with only value in amount
field is added and deleted at the same time.

VIMI-25538
Logic modules are not processed correctly when they are setup to activate by determination.

VIMI-25539
It is not possible to move from line item tab to other tab when profitability segment is enabled and one
of the fields in the line item tab of the indexing screen is mandatory.

VIMI-25594
QR IBAN value entered in the indexing screen does not get saved when bank data is not
available in vendor master.

VIMI-25605

Incorrect balance shown in the indexing screen when cash discount is enabled in company
code configuration.

VIMI-25620

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
28
Plug-in divider ratio is decreasing every time the indexing screen is loaded, reducing visible
area.

VIMI-25660

Time out occurs in the PO event receiver function when posting documents outside VIM.

VIMI-25666
When processing a service PO with discount-based condition types the exception “Tolerance
exceeded (PO)” is triggered incorrectly.

VIMI-25672
Delivery note based proposal does not consider payment terms maintained in the
purchasing tab of vendor master.

VIMI-25681
Search help for field “Requester E-mail" is not working for the mail id whose length is greater
than 33 characters.

VIMI-25683
Due date gets incorrectly calculated when option “SAP Logic” is set for calculation of
baseline date when processing DP document after few days from creation.

VIMI-25709
VIM proposal for PO item with item category as B(Limit) is deriving quantity not same as
MIRO.

VIMI-25710
For a PO invoice tax jurisdiction code changed in the indexing screen gets replaced with old
value after clicking apply rules.

VIMI-25737
The re-run rules program aborts with the short dump error
“TSV_TNEW_PAGE_ALLOC_FAILED” when executed for large number of invoices.

VIMI-25750
When posting Non-PO invoice with profitability segment data BDC error “Field RKEAK-
FIELD (14) does not exist in the screen SAPLKEAK 0300” occurs.

VIMI-25800
The posting of a Non-PO invoice in both online and foreground mode fails when few of the
profit segment data fields are in display mode.

VIMI-25812
During online and background posting of invoice, ISR number is not transferred to SAP
though company code configuration is enabled for both ISR and QR-IBAN.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
29
VIMI-25813
When posting invoices with QR-IBAN or ISR number BDC error “Do not enter a partner bank
type when posting with QR-IBAN" occurs.

VIMI-25817
During delivery note proposal using "Match Lines" button in the line item tab of the indexing
screen the delivery note number is not copied to the line items.

VIMI-25819
During processing the line items tab in the indexing screen, the functional area in the
profitability segment is derived from cost center instead of G/L account.

VIMI-25849
The comma separator is replaced with invalid character " < (>, <)>” when entering
comments in the indexing screen.

VIMI-25862
When processing Non-PO invoices with large amounts and non-decimal currency run time
error occurs while applying rules or approving invoices.

VIMI-25848
When posting a Non-PO invoice short dump “Exception condition "READ_FAILED"
triggered” occurs in the event receiver function module “/OPT/VIM_RPT_RECEIVER_FM”.

VIMI-25868
For a posted PO invoice, the exchange rate flag is automatically checked though it was not
determined manually.

VIMI-25890
Performance issue in PO background posting when both PO & Delivery Note information is
passed to the DP line item and PO having thousands of invoiceable lines.

VIMI-25919
In the indexing screen for QR-IBAN invoices additional information fields (structured and
unstructured information) it is not possible to enter maximum allowed characters (140).

VIMI-25937
For a document processed via IES when the work item is opened in inbox the message “No
data found in VIM 1 Head for requested conditions” appears.

VIMI-25941
When posting PO freight invoice with freight vendor different from PO Vendor, the payment
term is not derived from freight vendor but from the PO vendor.

VIMI-25964
During online or background posting of PO invoice the cash discount flag value is not
transferred to SAP.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
30
VIMI-25966
When posting invoices with ISR number the partner bank type is missing.

VIMI-25967
During posting of a PO invoice with multiple account assignment and line item GR indicator
not checked, BDC error “Balance not equal to zero” occurs.

VIMI-26030
GST Partner field does not get refreshed when vendor number is changed in the indexing
screen for India invoices.

VIMI-26035; VIMI-25945
During posting of a PO invoice with invalid QR-IBAN, short dump “CONVT_NO_NUMBER”
occurs.

VIMI-26037
While posting a Non-PO Invoice in background with multiple line items with multiple tax
codes not in sorted order, error message " Condition type xxx tax code xx does not exist "
appears.

VIMI-26054
During posting of a QR-IBAN invoice with empty structured and unstructured information, the
posted document has characters ‘//’ saved in the additional information.

VIMI-26065
When posting a Non QR-IBAN invoice the payment method is set to ‘X’ incorrectly.

VIMI-26072
During online posting of Indian invoice with context to GST using BDC 200 the field data
‘Assessable value’ is not passed to MIRO.

VIMI-26116
When posting PO invoice in background with delivery note having several plants with
material ledger activated for few BDC error occurs.

VIMI-26117
“Tolerance Exceeded” exception always displays “Price too high” message even though the
price is low.

VIMI-26142
The exception “Invalid Vendor VAT Number” is triggered incorrectly though the vendor tax
number is maintained.

VIMI-26146
Wrong amounts are posted against G/L accounts with non-deductible tax for Non-PO invoice posted
with BDC 34.

VIMI-26177
Dump occurs when entering one-time vendor details with company code field kept blank in
the DP document.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
31
VIMI-26157
Vendor address data is missing in posted document as it is not transferred for documents
which contain additional information and QR reference type as NON.

7.2 Invoice Approvals

VIMI-23857
When using two COA online transactions (/OPT/AR_COA_MAINT and /OPT/AR_COA) in parallel,
data of only one transaction is updated though the Z-constant “COA_INDIVIDUAL_LOCK” is set.

VIMI-25181
Symbol ‘#' is appended to lines entered as comments through Fiori Approval apps.

VIMI-25238
When approving a Non-PO invoice, a short dump ‘DUMP TABLE_INVALID_INDEX’ occurs if AFS ID
configuration is not maintained.

VIMI-25331
When using COA Upload report, validation of company code and user id is not done.

VIMI-25513
The new COA maintenance transaction /OPT/AR_COA_MAINT allows duplicate records as opposed
to the online transaction /OPT/AR_COA.

VIMI-25516
The message “Invoice date is in future” appears as information message instead of error message
when approving a PO invoice.

VIMI-25522
For Non-PO posted approval invoice payment terms are missing in the approval screen.

VIMI-25597, VIMI-25079
When approving a credit memo having both credit and debit lines, error F5 704 "Inconsistent
amounts" appears.

VIMI-25598
The report “Invoices Processed by me” (/ORS/PROCBYME) is showing technical field names instead
of labels.

VIMI-25648
In COA maintenance transaction (/OPT/AR_COA) entering and saving 13 digits value in approval limit
tab leads to short dump.

VIMI-25652

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
32
Incorrect amount is displayed on the forwarding screen for invoices with 3 or more decimal
currencies.

VIMI-25735
When uploading new records using COA File Upload report existing records are replaced with the
new records.

VIMI-25853
For posted approval scenario of a credit memo with mixed credit and debit lines the balance shown
on the approval screen is incorrect.

VIMI-25873
When approving a Non-PO invoice error message "Check - document date is in future" appears.

VIMI-25938
In COA maintenance transaction the expense type column has incorrect column name “Expense Type
from”.

VIMI-26056
No option to disable message KI 339 "Profit center was set to XXX " in approval screen.

VIMI-26063
The approval screen is not in editable mode when using simple approvals starting from
requester level for VIM 16.3 SP5 version only.

VIMI-26103
It is not possible to copy rows in COA maintenance transaction (/OPT/AR_COA_MAINT) even
though create or generate permissions are enabled in J_6NIM_CA5 authorization check
configuration.

VIMI-26584
When creating multiple users in "User details" tab of COA maintenance transaction only the first
entry is saved and other records are not updated.

7.3 Invoice Exception

VIMI-24202; VIMI-25525
The background job for program “/OPT/VIM_TRIGGER_HEADER_WF” aborts with time out error
when processing large volume of data.

VIMI-24365
For a posted PO invoice, the net price and delivery note number at line item level is missing
in the DP document.

VIMI-25294
When trying to open a PO from the header level dashboard the error "You are not authorized to use
transaction ME23N" is displayed.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
33
VIMI-25569
In the indexing screen incorrect message “Purchase Order xxxxx: Item 000XX was deleted”
appears for line items that are set to block in the PO.

VIMI-25579
When using “Cancel and Re-enter" option for a Non-PO invoice, the type of the created DP
document is incorrectly determined as Down Payment.

VIMI-25607
Invoice reference number is cleared from parked MM document for Non-PO credit memo.

VIMI-25638
When posting the Non-PO invoice using PO BAPI the document is getting blocked due to
configuration of tolerance key "AN”.

VIMI-25678
The header workflow is incorrectly completed by the workflow cleanup job
(/PTGWFI/R_LIX_CLEANUP_WFS_NEW) though there is still block at header level.

VIMI-25814
Misleading message about unsuccessful result is shown when cancelling and re-creating a PO
invoice using t-code /OPT/INV_CANCL_RECRT.

VIMI-25832
The document status and block reason of a credit memo invoice do not change even after resolving
the block and posting the document.

VIMI-25917
When cancelling an invoice using t-code /OPT/INV_CANCL_RECRT there is a short dump due to
enhancements in /OPT/VIM_1HEAD and /OPT/VIM_BL_1RIDX_OCR_DATA.

VIMI-25963
Comments entered during parking of a Non-PO invoice are appearing under approval history log.

VIMI-26036
Comments are not visible for the Activity Type "Workflow Start" in the approval history Log.

7.4 VIM Notifications

VIMI-24877
For Non-PO posted approval documents reminder mails are sent earlier than expected according to
the configuration.

7.5 VIM Analytics (new VAN) Report and VAN Liability Report
VIMI-24312

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
34
For documents processed via IES, status in VIM Analytics is not in sync with status in BC workplace.

VIMI-24897
Approval history for the line items is incorrect in some cases in history tab of VIM Analytics.

VIMI-25026
When internal (“Optura”) approval user ID and SAP user ID in COA are different, the current agent
field in VIM Analytics displays SAP user ID instead of internal user ID.

VIMI-25072
VIM Analytics displays wrong “Transaction/Event” status for posted Credit Notes.

VIMI-25314
Search criteria to exclude range of document status along with SAP status is fetching incorrect results
in VIM Analytics.

VIMI-25321
It is not possible to view vendor details when clicking on vendor number in header line when partner
role customer function is used.

VIMI-25326
It is not possible to view the PDF attachment from the attachment list for an XML invoice processed
with PDF attachment.

VIMI-25341
In VIM Analytics the comments tab does not display the user name with prefix if maintained in SAP
user address.

VIMI-25345
For invoices processed via Ariba channel, “cycle time” value is empty/blank in VIM Analytics.

VIMI-25506
In VIM Analytics the reporting currency in the standard variant overwrites the currency maintained in
user settings.

VIMI-25515
The value in “Days to Due” column is incorrect for DP documents with status “OCR Validation
Rejected” or “Rescan Complete”.

VIMI-25555
Username is not displayed when reading the process comments from history tab in VIM
Analytics.

VIMI-25585
In VIM Analytics DP documents with empty company codes are displayed in addition to the
documents the user is authorized for.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
35
VIMI-25801; VIMI-25950
In VIM Analytics header data, the current agent field value shows ‘*’ instead of the user name.

VIMI-25734
There is a short dump with message “/OPT/VVA2_POI cannot be activated” when executing
VIM Analytics.

VIMI-25914
When using range of PO documents and purchasing group in the selection criteria of VIM Analytics,
Non-PO invoices are also listed.

VIMI-26113
SES list button in the DP basic data tab is in grey mode when invoice is opened from VIM analytics or
from VIM workplace.

VIMI-26185
In VIM analytics the block status is not updated when block is removed on the FI document using
FB02 for Non-PO invoice posted with BDC 2200.

7.6 Central Reporting and other reports

VIMI-24984
When “Open only” option is used in PO download report the staging table also contains completed
PO line items.

VIMI-25053
The Automation report (/OPT/VIM_ATM) does not provide the details on any change/fields updated
during extraction and validation for documents processed using IES.

VIMI-25277
In KPI dashboard the amount classification is not derived as per configuration, leading to incorrect
reporting.

VIMI-25420
The KPA dashboard report does not include DP documents having status
‘Deleted/Obsolete/Cancelled/Confirmed Duplicate/Rescan Complete’.

VIMI-25504
When executing the KPA report, the option “Exclude DPs outside VIM” does not fetch
correct DP documents.

VIMI-25606
The titles of Aging report are incorrect for Portuguese language.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
36
VIMI-25749
Hard coded restrictions for status selection in report /OPT/ARC_REP_WRITE is removed and Status
16 (Deleted) and Status 17 (Cancelled) are added.

7.7 VIM Workplace

VIMI-25491
In VIM workplace after some action is performed on the work item, the respective line is shifted to the
bottom of the grid.

VIMI-25232
For blocked PO invoices under 'My Pending' tab of VIM workplace, values for fields Exception reason,
Current Agent and Current Role are not shown.

VIMI-25574
It is possible to view images from VIM Workplace even though user authorization is restricted.

VIMI-25482
After posting a PO invoice in foreground, information message “Document xxx was posted in
company code xxx" is not displayed in VIM Workplace.

VIMI-25639
Invoices rejected from BC workplace appear in “My Pending” tab instead of “My Completed’ tab.

VIMI-25575
It is not possible to view vendor details when clicking on vendor number in header line from VIM
Workplace when partner role customer function is used.

VIMI-25777
Custom enhancement logic in VIM workplace is affected in some scenarios after VIM 7.5 SP 10.

VIMI-25885
It is not possible to open a scheduling agreement from header line in VIM Workplace.

VIMI-26040
Current role is shown incorrectly in VIM workplace when wait role is configured for a process type.

VIMI-26080
Different behavior in SAP business workplace and VIM workplace while accessing work items by
substitute of substitute.

VIMI-26129
Change tag is appearing twice when comments are added in VIM Workplace for the second time.

VIMI-26184

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
37
The document status in VIM workplace is incorrect when a Non-PO invoice is cancelled.

7.8 Web Approval Portal

VIMI-24624
Error in next approver determination when line items are copied multiple times in cost assignment tab.

VIMI-25247
Error message appears on entering a valid profit center when the cost center field is blank in the line
item.

VIMI-25267
Application loads a blank page when an invoice contains invalid receipt date format.

VIMI-25470
In bulk approval mode the action date and action time fields are blank in the details pane even though
the values are present in the invoice.

VIMI-25527
Reassigning of invoice fails using Reassignment tool (/ORS/UMREASSIGNED) for portal-only users
when the dialog user is WF batch.

VIMI-25570
Creation date is displayed blank for all DP documents although in /OPT/VIM_1HEAD, the field
“Document Create Date” is filled.

VIMI-25798
Performance Issues while loading and viewing the invoice history.

VIMI-25887
Error page appears when using export coding button in Cost Assignment section only for VIM 7.5
SP11 Jco3 1.6 version deployed on SAP Net weaver Server with Java 1.6 version.

VIMI-26127
CSV Formula Injection characters like +, -, = and @ are not validated when user performs upload or
export coding in the cost assignment section.

VIMI-26140
SALES_DOC_ITEM field in the line items of cost assignment section appears with leading zeros in Web
Approval Portal.

7.9 Fiori Approve Invoices app

VIMI-25512
A runtime error occurs when a passive substitute opens an invoice document.

VIMI-25797

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
38
Even though the net amount value is present, incorrect value of 0.00 is displayed in invoice data for
all Parked PO Invoices.

VIMI-25954
While uploading document the dialog box shows an option to browse two files at a time followed by an
error message.

VIMI-26077
It is not possible to delete attachments added by a substitute.

7.10 My Approved Invoices app

VIMI-25637
"DOCID" field value is not populated for parked PO invoices.

VIMI-25778
For Parked PO invoice each line item appears twice.

VIMI-25797
Even though the net amount value is present, incorrect value of 0.00 is displayed in invoice data for
all parked PO Invoices.

7.11 Fiori Enter Cost Assignment Advanced app

VIMI-26046
Spanish translation for Debit/Credit Indicator field name is missing for 16.3 SP4 and SP5.

VIMI-26175
The Cost center field configured as mandatory field is not validated on click of approval actions.

7.12 Fiori Invoice Exceptions app

VIMI-25600
"Refer Back" buttons in the Fiori Invoice Exceptions app are not matching with the buttons displayed
in SAP GUI.

7.13 Fiori Confirm Quantity or Price app

VIMI-25949
In the invoice detail page, the semantic navigation for PO Number is not working.

VIMI-26038
Error message appears when saving empty date field with French logon language.

7.14 Incoming Document Handler (IDH)

VIMI-23769
When processing documents via inbound channel there is error in triggering DP workflow if exchange
rate is not maintained in SAP.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
39
VIMI-25105
For documents processed through (ICC/ BCC), Invoice category is not transferred to DP document.

VIMI-25588
During inbound processing the execution of automated field enhancements is not happening as per
the sequence maintained in the configuration.

VIMI-25965
When the incoming invoice document has blanks or empty spaces in the IBAN, posting is not
possible.

7.15 IDF Framework (BC Inbound)

VIMI-23769
When processing documents via inbound channel there is error in triggering DP workflow if exchange
rate is not maintained in SAP.

VIMI-24327
When large amounts are passed in the amount fields in an IDOC for non-decimal currency, the BC
inbound process breaks, and the workflow is not triggered.

VIMI-25222
Fields of Swiss QR Bills are not mapped into VIM due to incorrect paths in the standard
mapping.

VIMI-25259
Upon clicking on 'Create incoming invoice' button from eDocument cockpit short dump occurs when
archiving fails.

VIMI-25291
When processing an E-invoice for Italy, the company code is not determined if VAT number is missing
in the XML.

VIMI-25395
The IDF trigger job fails to start DP workflow in multi backend scenario when either company code is
not configured or when tax configuration for company code is missing in the central system.

VIMI-25405
If the content repository for OCR result XML file is different from one used for invoice image, SCE
control does not work.

VIMI-25442
While processing documents via BC inbound, document type determination based on channel id is
not working correctly resulting in incorrect DP document type.

VIMI-25537

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
40
When using bulk option to change status of the documents short dump occurs when few of the
registered documents do not have target keys.

VIMI-25624
Long lists of PO numbers or delivery notes were not supported with IES integration and also
with BCC integration in case of multi backend scenario.

VIMI-25651
During IES processing error occurs when a non-numeric value is extracted into a numeric field even
when “IgnoreMappingError” flag is set.

VIMI-25691
When processing an XML file with UBL format, transformation of nodes is incorrect and thus mapping
for many fields is missing.

VIMI-25719
When documents are processed from document pipeline channel the DP documents have reg id and
IDOC number copied from the previous DP document.

VIMI-25825
The IBAN value in DP document is either replaced with vendor master IBAN or remains empty when
the inbound document has an IBAN different from the vendor IBAN.

VIMI-25859
In some scenarios when processing inbound IDOCs, duplicate DP workflows are created.

VIMI-25860
UN/CEFACT (CII) transformation does not process attachments and also few fields are not mapped
during transformation.

VIMI-25870
The scan date and scan time are blank in the DP document for documents processed via email
channel.

VIMI-25925
When processing an XML document with attachments via email channel, error “"Error archive
processing for method ARCHIVOBJECT_CREATE_TABLE” occurs.

VIMI-25944
During BC inbound Email processing with additional attachments, the BC inbound trigger job aborts
with a short dump due to performance issue in archiving.

7.16 Others
VIMI-25381
For a Non-PO invoice posted via BDC 2200 or 42 it is not possible to open the Unified dashboard
from GOS menu.

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
41
VIMI-25889
When executing the sub nodes of “Customer Specific Cost Handling” from configuration message “No
transaction found” appears.

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.

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 General Invoice Solution BC Set(s)

If you are performing initial installation of VIM 7.6 or if you upgrade from VIM 7.5 initial release up to
and including SP8, activate /OTEXVIM/VIM76_BASE.

If you upgrade from VIM 7.5 SP9 or SP10, activate /OTEXVIM/VIM76_DELTA_V2 and then
/OTEXVIM/VIM76_BASE_ONE.

If you upgrade from VIM 7.5 SP11, activate /OTEXVIM/VIM76_BASE_ONE only.

8.2 Activate BC Set /OTEXVIM/VIM76_FIORI

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.

In order to release activated BC set to other clients, please ensure following SAP Notes is imported
before activating the BC set.

https://launchpad.support.sap.com/#/notes/2323541

2323541 - SE09: Unnecessary check for "_" in table key.

8.3 Activate BC Set for Inbound

Those BC sets have to be activated in case you are using inbound scenarios. In case you
have changed VIM baseline customizing for BC inbound, make sure the BC set will not
overwrite any customizing.

Activate the BC set /OTX/VIM76_SP_INBOUND_DELTA and then

/OTX/VIM76_SP_INBOUND

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
42
Note: In case you are upgrading from VIM 7.5 SP11, you need to activate only
/OTX/VIM76_SP_INBOUND.

8.4 Review Known Issues

Review the section “Known Issues” and verify whether you need to perform additional
adjustments of VIM configuration.

9 Known issues
The following known issues exist in this release.

Issue number Issue description

VIMI-26675 Comments added during DP are not displayed in the approval screen.

VIMI-26249 In the Vendor Invoices Report app, pagination for invoices list display is not
working as per the given page size.

VIMI-26760 In the Vendor Invoices Report app, a message is displayed that search results
in 200 invoices shown, while more is actually found.

VIMI-26251 In the Vendor Invoices Report app, quantity values in the line item section are
displayed with decimal places when it is not needed.

VIMI-26800 DP document picking the smart coding proposal, even though NPO auto
coding is configured for vendor and company code.

VIMI-26616 When an invoice is in status ‘Submitted for approval’, the process time is shows
negative value in ILC report.

VIMI-26734 Text label may be missing for the new field “Tax amount in local currency”. If
using that field, enter the label following the customizing path in /OPT/SPRO:
Document Processing > General Configuration > Translation/Labels for Header
Fields, for field name HWSTE.

VIMI-26820 VIM invoice inbound module exit /OTX/PS03_CL_VIM_HANDLER_EXIT

missing for handler PS03_IES. This may result in document status differences
between BC Workplace and VIM Analytics. To solve the problem, enter the exit
following the customizing path in /OTX/PF00_IMG: Inbound Configuration >
Document Handler > Modules:

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
43
 Issue number Issue description

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 Release Notes
44
10 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 © 2020 Open Text. All Rights Reserved.

Trademarks owned by Open Text. One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept
no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.

45