VIM 7.6 SPS4 - Release Notes For Invoice Solution

OpenText™ Vendor Invoice Management
for SAP®
Release Notes for Invoice Solution

Version 7.6 SPS4
Product Released: 2022-10-31
Release Notes Revised: 2023-07-17

OpenText™ Vendor Invoice Management for SAP® Solutions Version 7.6 SPS4 Release Notes
2
Contents
1 Introduction .................................................................................................................................... 5
1.1 Release Naming Information ..................................................................................................... 5
1.2 Release Notes revision history .................................................................................................. 5
2 About OpenText™ Vendor Invoice Management for SAP® Invoice Solutions ........................ 6
2.1 General Data Protection Regulation (GDPR) ............................................................................ 6
3 Installation ...................................................................................................................................... 7
3.1 Supported ArchiveLink Content Repositories ............................................................................ 7
3.2 Additional Installation Prerequisites .......................................................................................... 7
4 New Features .................................................................................................................................. 8

4.1 VIM Business Warehouse content for Invoice Life Cycle (VIMI-30441) .................................... 8
4.2 Improved PO line-item matching (VIMI-32130) ......................................................................... 8
4.3 Inbound: Validation decision based on Supplier Profiles (VIMI-33089) .................................... 8
4.4 UI update of Confirm Quantity and Price app (VIMI-24549) ..................................................... 8
4.5 Editable Email templates for VIM Supplier Self Service Registration (VIMI-30287) ................. 9
4.6 Display of Vendor Name in Vendor Invoices Report Fiori App Full-Screen list page
(VIMI-31386) .............................................................................................................................. 9
4.7 New processing model for electronic invoices (VIMI-31637) .................................................... 9
4.8 Swiss QR Bill - XML support using the parsing class (VIMI-31527) ....................................... 10
4.9 Support for China E-Invoice (VIMI-33285) .............................................................................. 10
4.10 Improvements for the Central Reporting for VIM Invoice (VIMI-31906) .................................. 10
4.11 Performance improvements on /OPT/DR_BR_WAIT program (VIMI-31905) ......................... 11
4.12 Performance improvements for validating the coding data of NPO and PO invoices
(VIMI-31640) ............................................................................................................................ 12
4.13 Implementation of QR code for Portugal (VIMI-32739) ........................................................... 12
4.14 QR Code Digital Signature Validation for India - Simple Check (VIMI-32444) ........................ 13
4.15 Inclusive Language - Change Customizing (VIMI-30674) ....................................................... 13
4.16 Support of long reference numbers by Ariba CIG integration (VIMI-31878) ........................... 14
4.17 Support of comments for obsoleted invoices by Ariba CIG integration (VIMI-31536) ............. 14
4.18 Support of vendor comments by Ariba CIG integration (VIMI-32034) ..................................... 14
5 Packaging and Documentation .................................................................................................. 14

5.1 Packaging and Delivery Information ........................................................................................ 14
5.1.1 ABAP Packages ......................................................................................................... 14
2
5.1.2 Language Support ...................................................................................................... 15
5.1.3 Non-ABAP Packages ................................................................................................. 16
5.1.4 Business Center – VIM upgrade from lower support package level .......................... 16
5.1.5 VIM Foundation and Additional Components ............................................................. 17
5.1.6 Packages and Transports for Additional Scenarios .................................................... 17
5.1.7 Compatibility and support package information ......................................................... 20
5.1.8 Flexible installation of Framework and Inbound components .................................... 20
5.2 Documentation ........................................................................................................................ 25
6 Supported Environments and Compatibility ............................................................................. 25

6.1 Compatibility Matrix ................................................................................................................. 25
6.2 Language Support ................................................................................................................... 25
6.3 Approval Portal Downward Compatibility Matrix ..................................................................... 26
6.4 Approval Portal JCo Compatibility Matrix ................................................................................ 27
6.5 Supported web browsers ......................................................................................................... 27
6.6 Supported Operating Systems for Mobile Devices.................................................................. 29
6.7 Web Viewer support ................................................................................................................ 29
6.8 Brava View support.................................................................................................................. 30
6.9 VIM Fiori Apps: Variants .......................................................................................................... 31
6.10 VIM Fiori Apps: SAP UI5 Version Compatibility ....................................................................... 33
6.11 Electronic Invoices – Supported Formats ................................................................................ 34
7 Fixed issues .................................................................................................................................. 36

7.1 Document Processing (DP) ..................................................................................................... 36
7.2 Invoice Approvals .................................................................................................................... 41
7.3 Invoice Exception .................................................................................................................... 42
7.4 VIM Notifications ...................................................................................................................... 42
7.5 VIM Analytics (new VAN) Report and VAN Liability Report. .................................................... 42
7.6 Central Reporting and other reports ........................................................................................ 43
7.7 VIM Workplace ........................................................................................................................ 44
7.8 Web Approval Portal ................................................................................................................ 44
7.9 Fiori Approve Invoices app ...................................................................................................... 45
7.10 My Approved Invoices app ...................................................................................................... 45
7.11 Fiori Enter Cost Assignment Simple app ................................................................................. 45
7.12 Fiori Enter Cost Assignment Advanced app ............................................................................ 45
7.13 Resolve Exceptions app .......................................................................................................... 45
7.14 Vendor Invoices Report app .................................................................................................... 46
7.15 IDF Framework (BC Inbound) ................................................................................................. 46
3
7.16 Others ...................................................................................................................................... 47
8 Post Installation Activities .......................................................................................................... 48

8.1 Activate General Invoice Solution BC Set ............................................................................... 48
8.2 Activate BC Set for Inbound .................................................................................................... 48
8.3 Adjust the IES mapping for VIM Foundation ........................................................................... 48
8.4 Activate BC Set for Fiori Apps ................................................................................................. 49
8.5 Mail templates for VIM 3S User Registration .......................................................................... 50
8.6 Installing transport with layout variants ................................................................................... 50
8.7 Configuration delivered with BC set ........................................................................................ 50
8.7.1 Implement the next generation model for E-Invoice in VIM (VIMI-31637) ................. 50
8.7.2 Improvements for the Central Reporting for VIM Invoice (VIMI-31906) ..................... 55
8.7.3 QR code for Portugal (VIMI-32739) ............................................................................ 57
8.8 Configuration not delivered with BC set .................................................................................. 61
8.8.1 IES Extraction Analytics for invoice – manual changes required related to
obsolete table /OTX/PF08_T_DEAP .................................................................. 61
8.9 Optional Post Installation Activities .......................................................................................... 62
8.9.1 Improved PO line-item matching (VIMI-32130) .......................................................... 62
8.10 Review Known Issues ............................................................................................................. 64
9 Known issues ............................................................................................................................... 65
10 Documentation extensions ......................................................................................................... 66

10.1 Installation Guide ..................................................................................................................... 66
10.1.1 Section 13.1.1 – Selecting and downloading the required components for
different scenarios .............................................................................................. 66
11 Contact information ..................................................................................................................... 67
4
1 Introduction
These Release Notes provide an overview of OpenText™ Vendor Invoice Management for SAP®
Invoice Solutions Version 7.6 SPS4, 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 Naming Information

Since 2020 OpenText has adopted release numbers using the format „<Calender Year><Quarter>“
e.g. “20.4”. In general an OpenText VIM release number might translate into a major release or
translate into a Support Package Stack for an existing release. In case of a Support Package Stack
(SPS) the “technical” version number will then be „<major release> SPS <SPS counter>“. For more
information on release names, see the SAP Note 2339256.
The technical release number of Vendor Invoice Management for SAP 7.6 that is being released in
4th quarter of 2022 is “7.6 SPS4”. The release name for this package is “22.4 for ECC”.
Note that the corresponding release and technical release names of the current Vendor Invoice
Management solution for S/4HANA are “22.4 for S/4HANA” and “20.4 SPS4”.
1.2 Release Notes revision history
Revision date Sections revised Description of revisions
2022-11-09 Initial version
New delivery file for Cloud Foundry multitarget

2022-11-23 Packaging
deployment scenario
Documentation
2023-07-17 Added one entry
extensions
5
2 About OpenText™ Vendor Invoice Management for
SAP® Invoice Solutions
Welcome to OpenText Vendor Invoice Management (VIM). VIM is an add-on that works with existing
SAP ERP systems to streamline accounts payable operations.
This section provides an overview of OpenText™ Vendor Invoice Management for SAP® Invoice
Solutions Version 7.6 Support Package Stack 4.
The support 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.
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.
6
3 Installation
This chapter gives some hints for the installation of Support Package Stack 4 for Vendor Invoice
Management (VIM) 7.6 Invoice Solution. For the detailed installation description read the VIM 7.6 SPS4
Installation Guide.
3.1 Supported ArchiveLink Content Repositories

OpenText™ Vendor Invoice Management for SAP® Solutions is in general compatible and supported
with any archive solution that is compatible with SAP ArchiveLink and certified by SAP.
VIM is specifically tested and validated for

• OpenText Archiving and Document Access for SAP Solutions
• OpenText Documentum Archive Services for SAP Solutions
Some specific functions (for example the input channel batch pipeline) are only supported for
OpenText Archiving and Document Access for SAP Solutions.
3.2 Additional Installation Prerequisites

An ACP file is required to install the main package OTEXVIM on SAP_BASIS levels from 700 SP13 to
SP34 (SPs lower than 13 are not supported). If you purchased VIM through SAP, the ACP file can be
downloaded from SAP Marketplace, and it will be also automatically taken into account by
Maintenance Planner. If you purchased VIM directly from OpenText, the file is provided within the post
installation ZIP file (ACP Files > otexvim80700_006_acp.sar) available for download at
https://support.opentext.com/csm?id=kb_article_view&sysparm_article=KB0739330.
SAP Notes required or mandatory for VIM (if relevant for the used release of SAP_BASIS or other
respective components):
• 2353336 - Workflow: Runtime error CREATE_DATA_UNKNOWN_TYPE.

• 2347514 - Workflow: Transaction SWF_CNT_STR_GEN does not include all workflow struc-
tures. (The report RSWF_CNT_PREPARE_STRUCTURE needs to be run as indicated in the
note.)
• 2339460 - Exception "Invalid or no mapping to system data types found" occurs when calling
a service with multi origin (mo) query option.
• 2665611 – Saving text without change to information about last change
Before installing VIM 7.6 invoice Fiori apps (component OTBCSL33), the SAP Note 1680583 – “Field
names for tables and views with more than 16 char” must be, if applicable, implemented.
7
4 New Features
4.1 VIM Business Warehouse content for Invoice Life Cycle
(VIMI-30441)
The VIM Business Warehouse (BW) content is extended with the content of Invoice Life Cycle report.
With the provided multiprovider the customer can create their own query, that in turn can be consumed
by SAP BW report tools like SAP Lumira, SAP Business Object for Analysis, or SAP Analytics Cloud to
build analytics report according to the customer requirements. An example query is delivered in the
content that shows all invoice life cycle data.
The BW data extractor for Invoice Life Cycle table /OPT/VT_ILC_SRC as well as extractors for required
text tables are provided in ERP system (OLTP system). These can be consumed by customer to build
up their own BW content on OLAP system.
The provided BW content can be deployed on BW system from 7.5 upwards with non-HANA or HANA
database.
For more information about the content and how to use it please refer to Configuration Guide.
4.2 Improved PO line-item matching (VIMI-32130)

For PO Line Determination Setting “OK – Use OCR lines as basis without deletion of incomplete lines”,
an improved determination logic is available. Matching is more relaxed: quantity and price can be
smaller than in PO line items. Parts of the invoice material text are matched against PO / GR material
text and number.
4.3 Inbound: Validation decision based on Supplier Profiles

(VIMI-33089)
A supplier-based configuration (“Supplier Profile”) to control the OCR validation step is added to the
VIM Central Workplace. Validation can be configured based on supplier, company code or vendor
group.
4.4 UI update of Confirm Quantity and Price app (VIMI-24549)

Confirm Quantity and Price app has been updated to use the latest features from VIM Foundation
Framework and new perspective has been introduced with Flex column layout.
In the new perspective of Confirm Quantity and Price app, line items, process history, and approval
history are displayed in tabular responsive format. User entered comments can be viewed with
8
translated text based on the language selected by the user, using Translate option in the comments
section. Flex column layout allows to view the documents in Fullscreen mode.
4.5 Editable Email templates for VIM Supplier Self Service

Registration (VIMI-30287)
Two email templates for VIM Supplier Self Service registration are introduced and can now be
editable from SO10 Standard texts.
Registration mail template - /OPT/VIM_3S_REGISTRATION
Confirmation mail template - /OPT/VIM_3S_CONFIRMATION
Transaction /n/OTX/PS34_SENDEMAIL is introduced to resend registration emails to suppliers, instead

of directly executing program /OTX/PS34_RESEND_USRREG_EMAIL.
A maintenance view is created for /OPT/WT_3S_SLREG table and that can also be accessed from
transaction /n/OPT/3S_REGISTER.
The mail templates are being provided in English as an additional transport. See the post installation
section.
4.6 Display of Vendor Name in Vendor Invoices Report Fiori App

Full-Screen list page (VIMI-31386)
The additional column Vendor Name (LIFNR_FULLNAME) in Vendor Invoices Report Fiori App full-
screen list is now supported to view the name of the corresponding vendor.
4.7 New processing model for electronic invoices (VIMI-31637)

Processing of E-Invoice using New ABAP Class Based Parsing:
As part of E-invoice XML document processing, in VIM presently parsing of fields are done using
transformations. For every new format introduced or revision made in the existing version of XML
document, new transformation must be developed. Creating new transformation and separate handler
for each country is both effort and time taking process.
Hence, new ABAP class /OPT/VIM_CL_PARSE_XML has been introduced to process the XML
regardless of the specific format. In order to support new or revised XML format simple configurations
are to be maintained by the customer along with mapping of new XML fields with semantic fields.
9
New Class based parsing supports any country E-invoice in XML format without any need to create
specific transformations and configure module for every country. Only one handler can be used to
process all XML E-invoices.
For more information, refer to Scenario Guide for Invoice Solution.
Tool for proposal of E-Invoice mapping:
To process an E-Invoice, two mappings are required. One is semantic mapping other one is mapping
to VIM fields. In case of semantic mapping, we are assigning a semantic name to a combination of
nodes. This tool proposes the combination of nodes and its relevant values. User has to enter the
semantic name and the relevant fields type. This tool reduces the effort of intermediate mapping.
This tool simplifies the semantic mapping. We have to provide either the XML file or Regid as input.
Based on the input, system proposes all possible node combinations and its relevant values. For the
given XML file if already mapping is available for some fields, system shows the relevant semantic
names as well. User has to enter any missing semantic names and select the update check box and
save. This tool is basically useful either to enhance the existing semantic mapping or for mapping of
new file.
For more information, refer to Configuration Guide for Invoice Solution.
4.8 Swiss QR Bill - XML support using the parsing class

(VIMI-31527)
Swiss QR Bills in the form of XML invoices are now supported.
Support is provided for ESR, IBAN and QR-IBAN formats. The XML mappings for the document format,
required configurations for ESR number, ESR reference number and IBAN/QR-IBAN in mapping ID
XML_EINV are delivered as part of baseline configuration.
For more information, refer to Scenario Guide for Invoice Solution.
4.9 Support for China E-Invoice (VIMI-33285)

This feature now supports the processing of OFD invoice for China in 7.6. The configuration for XML
mapping is available in the BC set delivered in this SP.
4.10 Improvements for the Central Reporting for VIM Invoice

(VIMI-31906)
Tool for Scheduling of Central Reports:
This functionality simplifies scheduling of central report jobs for collection and aggregation reports. With
this feature, it is possible to maintain the sequence of jobs with variants to be scheduled and automate
the jobs scheduling.
10
A new node “Maintain Job Utility” is provided as part of this version.
This contains two steps with which central reports job scheduling will be easy.
• Maintain the created variants using the first node “Maintain Job Sequence”. The variants
created as per the configuration section 31.4 for all central reports are to be maintained in this
node.
• Once the variants are maintained with user preferred job prefix in the first column, job can be
scheduled using the second node “Central Report Job Schedule”.
For more information, refer to Administration guide and Configuration Guide for Invoice Solution.
Using the Intermediate Data Report:
This report provides an option to view the intermediate processing data for Central reports, before
aggregation of data.
This includes display of intermediate data for below individual reports:
• Aging Report
• Summary Report
• Audit Report
• Exception Analysis Report
• Key Process Analytics Report
• Productivity Report
For more information, refer to Reference Guide for Invoice Solution.
4.11 Performance improvements on /OPT/DR_BR_WAIT program

(VIMI-31905)
When executing the /OPT/DR_BR_WAIT program or /OPT/VIM_RULERUN transaction, system checks
only the current process type (business rule), but all the logic modules get executed which were
configured as rerun. To validate the current process type, either none or few logic
modules need to be executed instead of running all logic modules.
With this feature the following were introduced:
1. A new flag option ‘Skip logic modules’ is added on the selection screen for skipping the call for
Logic Modules. If this is checked, all logic modules will be skipped.
11
2. A new customizing option for the logic module is added, where process type can call specific
logic modules. The program /OPT/DR_BR_WAIT will execute only the logic modules configured
against the current business rules of a DP document.
For more information, refer to Configuration Guide for Invoice Solution.
4.12 Performance improvements for validating the coding data of

NPO and PO invoices (VIMI-31640)
This feature focuses on performance improvements for validating the coding data for both NPO and PO
invoices of level-based approval process at coder level.
NPO class /OPT/NON_PO_INVOICE_22_4 and PO class /OPT/PO_INVOICE_22_4 have been

introduced with optimized versions of existing classes /ORS/NON_PO_INVOICE_NEW and
/ORS/PO_INVOICE_NEW. These new classes can be configured at AFS ID settings, for more
information refer section 11.4.4 Configuring approval flow settings in Configuration Guide for Invoice
Solution.
The performance improvement is achieved by reducing the response times for following actions -
• Execute work item from VIM workplace
• Approval confirmation
• Cancel
• Return to inbox
4.13 Implementation of QR code for Portugal (VIMI-32739)

VIM now supports and includes the field ATCUD on Portuguese invoices.
A two-dimensional QR code must be included on invoices and other tax relevant documents. QR codes
on Portuguese invoices contain all the data about a particular invoice coded in line with technical
requirements provided by the tax authorities. These codes will be structured to have components A
through S, each indicating a particular document detail.
Information about the ATCUD is presented in code H. The field is included as a display only field on the
indexing screen (on the Basic Data tab), and its value will have to be passed from the OCR.
12
Two business rules/process types have been configured “Missing QR Code/ATCUD (NPO)” and
“Missing QR Code/ATCUD (PO)” which trigger when no value in the ATCUD field is passed if it’s a
Portuguese invoice. For more details, please refer the Scenario guide for Invoice Solution and/or
Reference guide for Invoice Solution.
4.14 QR Code Digital Signature Validation for India - Simple Check

(VIMI-32444)
QR code is mandated on invoices with a threshold amount for India. For supporting and validating this,
new generic field is created to capture the signature validation flag from inbound. This generic field is
mapped to inbound to get the data and validation will be done with new business rules.
Two business rules have been created “India - Digital Signature check (NPO)” and “India - Digital
Signature check (PO)”. These will trigger when the signature on the invoice is not verified. This is
handled using BRF configuration where in the threshold amount can be maintained by customer.
For more details, please refer the Configuration guide for Invoice Solution.
4.15 Inclusive Language - Change Customizing (VIMI-30674)

Being committed to diversity and inclusion, OpenText is adjusting insensitive terms in the software
products and their documentation. The vendor grouping IDs used in Business Rules Framework (BRF)
have been replaced with the new ones according to the table below. Note that the old IDs will not be
deleted when upgrading to this support package. The final deletion will be done in the next major release
and will be applicable only to new installations.
Old ID New ID
BLACK NEW
WHITE TRUSTED
GREY ALLOWED
The new definitions do not affect the product functionality and do not introduce any new features, being
just changes in the terms. If you decide to use the new IDs, the rest of BRF settings must be adjusted
accordingly.
13
4.16 Support of long reference numbers by Ariba CIG integration
(VIMI-31878)
Ariba CIG integration is now able to support invoice status update for invoices with reference numbers
longer than 16 characters. The reference number must be mapped into the dedicated "long reference"
field LXBLNR.
4.17 Support of comments for obsoleted invoices by Ariba CIG

integration (VIMI-31536)
Comments entered in the DP indexing screen when obsoleting an invoice that originated in Ariba (CIG
scenario) can now be sent into Ariba Network to be visible by suppliers.
4.18 Support of vendor comments by Ariba CIG integration

(VIMI-32034)
Comments entered by Ariba suppliers are now supported in standard (IDOC based) invoice scenario.
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 SPS4 Installation Guide.
5.1.1 ABAP Packages

To install VIM 7.6 SPS4 Invoice Solution, you need the files listed in the table below. Depending
on scenarios, different packages may be needed to be installed. You will find the information on
VIM Framework and Solution Base components in their respective release notes.
Component Package file name
OTEXVIM_SP04_80700_006.SAR
OTEXVIM
OTBCSL30_SP04_80700_006.SAR
OTBCSL30
OTBCSL33_SP04_80700_006.SAR
OTBCSL33
The following optional support package is provided for Ariba CIG integration:
14
Binary name Description Version Support
package
OTVIMARC_SP03_0700_006.SAR VIM Invoice Ariba CIG 80700_006 0003
Integration 7.6 SP3
5.1.2 Language Support

OpenText™ Vendor Invoice Management for SAP® Invoice Solutions is localized in the following
languages.
Component Languages
EN DE JA FR IT ZH ES NL PT *RU
OpenText Vendor B, F B, F B, F B, F B, F B, F B, F B, F B, B,
Invoice
F F
Management
Component Languages
HU RO TR PL CS SK KO SV FI
OpenText Vendor UI, UI, UI, UI, UI, UI, UI, UI, UI,
Invoice F F F F F F F F
F
Management
*Supported with limitations (not all texts may have translations)
UI = user interface only
B = both user interface and User Guide
F = Fiori UI
15
Note
➢ VIM provides translations in other languages than English only for
end user screens (transactions and reports used in a production sys-
tem by non-technical users). Translation is not provided for configu-
ration screens.
➢ The installation package does not contain full language support ex-
cept for English. Language packages for the supported languages
are available on OpenText My Support in the corresponding patch
area.
5.1.3 Non-ABAP Packages

The following packages are required to implement the VIM Approval Portal for invoice coding and
approval based on SAP NetWeaver Java and SAP NetWeaver Portal:
Component Packages
im_approval_portal7_6_sp4.zip
Approval Portal based on
JCo3.1 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.x installation, upgrade to VIM Foundation
Version 7.6, which is a successor of Business Center, is a must (see the next section).
16
5.1.5 VIM Foundation 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 Foundation 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 Foundation 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 Packages and Transports for Additional Scenarios

Several additional packages are delivered along with the product. This section lists those that are
updated and provided with VIM 7.6 SPS4. A complete list of all additional packages can be found in
VIM 7.6 SPS4 Installation Guide.
17
Binary name Description Install on Deployment
scenario
additional_transport_withlay Additional transport with layouts Back end Core invoice
out_for_ecc6.0.zip for VIM Analytics SP2
Invoice Fiori perspectives layouts Back end Fiori/On-

Solutions_fiori_perspectives premise
_layouts.zip
Invoice Fiori perspectives customizing Back end Fiori/On-

Solutions_fiori_perspectives premise
_customizing.zip
18
Binary name Description Install on Deployment
scenario
invoice solutions-launchpad Pre-configured tiles and target Front end Fiori/On-
content.zip mapping for VIM Fiori apps premise
SiteTransport_CF_20.4_SPS03_I
Site transport for Cloud Foundry Cloud Foundry Cloud Foundry
nvoice Solution.zip
for standalone AppRouter
deployment
sitetransport_cf_mta_20.4_sps
Site transport for Cloud Foundry Cloud Foundry Cloud Foundry
04_invoice solution.zip
for multitarget application
deployment
invoice Email template files for Supplier Back end Supplier self
solutions_3s_email_templates self service registration service
.zip
19
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 VIM 7.6 SPS1 VIM 7.6 SPS2 VIM 7.6 SPS3 VIM 7.6 SPS4
and SP
OTBCBAS 0700_006 0700_006 0700_006 0700_006 0700_006
0001 0002 0003 0004
OTBCSL00 0700_006 0700_006 0700_006 0700_006 0700_006
0001 0002 0003 0004
OTEXVIM 80700_006 80700_006 80700_006 80700_006 80700_006
0001 0002 0003 0004
OTBCWUI 0740_006 0740_006 0740_006 0740_006 0740_006
0001 0002 0003 0004
OTBCSL30 80700_006 80700_006 80700_006 80700_006 80700_006
0001 0002 0003 0004
OTBCSL33 80700_006 80700_006 80700_006 80700_006 80700_006
0001 0002 0003 0004
When using Fiori apps, refer to the section VIM Fiori Apps: SAP UI5 Version Compatibility for more
information related to Fiori / UI5.
5.1.8 Flexible installation of Framework and Inbound components
OpenText recommends updating all components of VIM regularly. Ideally the versions correspond to
the combinations listed in VIM component compatibility and support package information. If upgrading
VIM Invoice Solution is not possible, VIM supports (starting with version 7.6) the use of more recent
20
versions of VIM Foundation and Inbound components with older versions of VIM 7.5/7.6 Invoice
Solution and, optionally, VIM Invoice Fiori apps. This currently supports the following scenarios:
• 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
The SP level of the VIM Invoice Inbound component OTBCSL30 must correspond to the
same Support Package Stack of the VIM Foundation component
• VIM Invoice Fiori apps.
This scenario is supported starting with VIM Invoice main component of 7.6, with higher levels
of VIM Foundation and Inbound. If you use VIM Invoice Fiori apps, you can upgrade VIM
Foundation and VIM Invoice Inbound components to a higher SP level. This way, you can
update VIM Foundation and, if applicable, VIM Solutions Beyond Invoice components. The SP
level of the VIM Invoice Inbound component OTBCSL33 must correspond to the same Support
Package Stack of the VIM Invoice Solution main component. Because of this restriction, the
special installation steps described later in this section deal only with the inbound scenario. No
special steps apart from updating the Foundation and Inbound are required.
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.
In case of a flexible installation, the SP level of the inbound component “aligns” with VIM Foundation
(higher level), while the SP level of VIM Invoice Fiori apps “aligns” with the VIM Invoice main
component (lower level). For VIM Invoice Fiori apps, you must use the versions as described in the
section “Compatibility and support package information”. The table below shows the supported
combinations starting with VIM 7.6.
21
VIM 7.6 SPS4:
VIM 7.6 SPS0: VIM 7.6 SPS1: VIM 7.6 SPS2: VIM 7.6 SPS3:
OTBCBAS
OTBCBAS OTBCBAS OTBCBAS OTBCBAS
OTBCSL00
OTBCSL00 OTBCSL00 OTBCSL00 OTBCSL00
OTBCSL30
OTBCSL30 OTBCSL30 OTBCSL30 OTBCSL30
VIM 7.6 SPS0:

X X X X X
OTEXVIM SPS0
OTBCSL33 SPS0 (*)
VIM 7.6 SPS1:

X X X X
OTEXVIM SPS1
OTBCSL33 SPS1 (*)
VIM 7.6 SPS2:

X X X
OTEXVIM SPS2
OTBCSL33 SPS2 (*)
VIM 7.6 SPS3:

X X
OTEXVIM SPS3
OTBCSL33 SPS3 (*)
VIM 7.6 SPS4:

x
OTEXVIM SPS4
OTBCSL33 SPS4 (*)
* OTBCSL33 is the optional Fiori Component.
The flexible installation is supported for VIM 7.5 SP5 and later Support Packages. VIM Foundation
and VIM Foundation based components like 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 perform the flexible installation:

1. Before installing the VIM Foundation and Inbound components, implement manual correction
instructions if mentioned in the table below. If activation of the changed objects results into
errors, perform the activation after the import of compatibility transports (step 3).
2. Install VIM Foundation 7.6: components OTBCBAS and OTBCSL00. Install SP1 of VIM Foun-
dation 7.6.
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. Install VIM 7.6 Invoice Solution Inbound: component OTBCSL30. Install SP1 of OTBCSL30.
6. 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.
Note: Depending on the support package level of components, it might be necessary to install the
component OTBCSL30 before importing the compatibility transports and to ignore errors during
22
the installation. That means to exchange step 3 and step 5. This also applies to the steps of the
Installation examples.
Table 11-1: Transports for flexible installation

Compatibility
transports to
Current VIM OTBCSL30 based on
Manual correction import in case OTBCSL30 based on
Support VIM 7.6 SP2
instructions of OTBCSL30 VIM 7.6 SP1
Package level
based on VIM
7.6
TW9K900010,
VIM_7.5_SP11-
7.5 SP5 TW9K900010 TW9K900010 TW3K900021
VIMI-24759_CI-97
TW9K900010,
VIM_7.5_SP11-
7.5 SP6 TW9K900010 TW9K900010 TW3K900021
VIMI-24759_CI-97
7.5 SP7
7.5 SP8 TW9K900010,
7.5 SP9 TW9K900010 TW9K900010 TW3K900021
7.5 SP10
7.5 SP11
TWRK901062
7.6 TWRK901062
TWRK901062
7.6 SP1
All transport files listed in the table, along with the correction instructions can be downloaded from
OpenText My Support: https://knowledge.opentext.com/knowledge/cs.dll/Open/79096991
The compatibility transports may overwrite manual correction instructions that might be
implemented in your systems. To prevent problems caused by that, verify whether you have done
any modifications to affected objects.
To find the objects common to your modifications, use SAP Modification Browser (transaction
SE95) and transport object list display in the transport management system (for example
transaction STMS).
If you identify objects affected by the compatibility transports, verify and potentially redo the
manual changes. Do not reuse the repair transport(s) created earlier during the implementation of
correction instructions.
Installation examples
Example 1.
23
You currently use VIM 7.5 SP10. You want to use IES for OCR extraction and you decide to use
the inbound components delivered with VIM 7.6 SPS2. Perform the following steps:
To perform a flexible installation:

1. Install VIM Foundation 7.6: components OTBCBAS and OTBCSL00. Install SP1 and SP2 of
VIM Foundation 7.6.
2. Import the transports TW9K900010 and TW3K900021.
3. Install the VIM Invoice solution for VIM 7.6: component OTBCSL30. Install SP1 and SP2 of
OTBCSL30.
4. Activate the BC sets of VIM Foundation 7.6: /OTX/PF00_BASE_006 and
/OTX/PS00_BASE_006. Activate the SP1/SP2 BC sets: /OTX/PF00_BASE_006_01,
/OTX/PS00_BASE_006_01, /OTX/PF00_BASE_006_02, /OTX/PS00_BASE_006_02.
5. Activate the BC sets for Inbound of the VIM 7.6 Invoice solution:
/OTX/VIM76_SP_INBOUND_DELTA and then /OTX/VIM76_SP_INBOUND. Activate the
SP1/SP2 BC sets: /OTX/VIM76_SP1_INBOUND.
Example 2.
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 SPS1. 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 VIM Foundation 7.6: components OTBCBAS and OTBCSL00. Install SP1 and SP2 of
VIM Foundation 7.6.
3. Import the transport TW9K900010 and TW3K900021.
4. Install the VIM Invoice solution for VIM 7.6: component OTBCSL30. Install SP1 and SP2 of
OTBCSL30.
5. Activate the BC sets of VIM Foundation 7.6: /OTX/PF00_BASE_006 and
/OTX/PS00_BASE_006. Activate the SP1/SP2 BC sets: /OTX/PF00_BASE_006_01,
/OTX/PS00_BASE_006_01, /OTX/PF00_BASE_006_02, /OTX/PS00_BASE_006_02.
6. Activate the BC sets for Inbound of the VIM 7.6 Invoice solution:
/OTX/VIM76_SP_INBOUND_DELTA and then /OTX/VIM76_SP_INBOUND. Activate the
SP1/SP2 BC sets: /OTX/VIM76_SP1_INBOUND, /OTX/VIM76_SP2_INBOUND.
24
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 SPS4
documentation set available in the OpenText Knowledge Center:
https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=10151494
The VIM 7.6 SPS4 User Guide is available in English language only.
6 Supported Environments and Compatibility

6.1 Compatibility Matrix
Details regarding prerequisites and compatibility can be found in OpenText™ Vendor Invoice
Management for SAP® Solutions Version 7.6 SPS4. Release Notes for Foundation.
Note: For the latest compatibility information for OpenText products, refer to the Compatibility
Matrix (https://knowledge.opentext.com/go/matrix) on OpenText My Support.
6.2 Language Support

OpenText™ Vendor Invoice Management for SAP® Invoice Solutions is localized in the following
languages.
Component Languages
EN DE JA FR IT ZH ES NL PT *RU
OpenText Vendor B, F B, F B, F B, F B, F B, F B, F B, F B, F B, F
Invoice Management
Component Languages
HU RO TR PL CS SK KO SV FI
OpenText Vendor UI, F UI, F UI, F UI, F UI, F UI, F UI, F UI, F UI, F
Invoice Management
* Supported with limitations (not all texts may have translations)
25
UI = user interface only
B = both user interface and User Guide
F = Fiori UI
Note
➢ VIM 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 is not provided for configuration screens.
➢ The installation package does not contain full language support except for English.
Language packages for the supported languages are available on OpenText My
Support in the corresponding patch area.
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 OAP 7.6 OAP 7.6 OAP 7.6 OAP 7.6
Matrix VIM 7.6 SPS1 SPS2 SPS3 SPS4
VIM 7.6
VIM 7.6 SPS1
VIM 7.6 SPS2
VIM 7.6 SPS3
VIM 7.6 SPS4
Legend:
26
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 OAP 7.6/ OAP 7.6 OAP 7.6 OAP 7.6 OAP 7.6
Version OAP 20.4 SPS1/ OAP SPS2/ OAP SPS3/ OAP SPS4/ OAP
20.4 SPS1 20.4 SPS2 20.4 SPS3 20.4 SPS4
JCo3 + Java
1.6
JCo3 + 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
IE11 IE Edge FF Chrome Safari

(94.0.992.31:
September 29)
OAP 7.6
OAP 7.6 SPS1
27
OAP 7.6 SPS2
OAP 7.6 SPS3
OAP 7.6 SPS4
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.
28
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 OAP 7.6 OAP 7.6 OAP 7.6 OAP 7.6 OAP 7.6
Devices SPS1 SPS2 SPS3 SPS4
Matrix
iOS (9.0) to
(14.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
20.3 21.1 21.4 22.4
Web Mobile Web Mobile Web Mobile Web Mobile
OAP 7.6
OAP 7.6
SPS1
OAP 7.6
SPS2
OAP 7.6
SPS3
OAP 7.6
SPS4
29
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.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
OAP 7.6 SPS1
OAP 7.6 SPS2
OAP 7.6 SPS3
OAP 7.6 SPS4
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.
30
6.9 VIM Fiori Apps: Variants
The following table lists the supported variants of VIM Fiori apps:
NEO Cloud Desktop Tablet Smart

On-
Fiori App Phone
premise
Cloud Foundry
Approve Invoice
Enter Cost Assignment Simple
Enter Cost Assignment Advanced
Vendor Invoices Report App
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
Invoice Approval Workplace
Accounts Payable Workplace
User Preferences Settings App
31
Note
• VIM Workplace and VIM Analytics in SAP GUI for HTML are supported only on
SAP Fiori FES 5.0 (SAP Note 2618605)
• From 7.6 SPS2, “Enter Cost Assignment - Simple Coding” app will be in
maintenance mode and customers need to migrate to “Enter Cost
Assignment - Advanced Coding” app
32
6.10 VIM Fiori Apps: SAP UI5 Version Compatibility
The following table shows the compatibility matrix of VIM/Invoice Solutions Fiori Apps- BC/VIM UI –
SAP UI5:
VIM UI 20.4 VIM UI 20.4 SPS1 VIM UI 20.4 SPS2 VIM UI 20.4 SPS3 VIM UI 20.4 SPS4
OTBCWUI
OTBCWUI 0740_006 SP4
OTBCWUI 0740_006 SP3
OTBCWUI OTBCWUI 0740_006 SP2 OTBCWUI_NEO_07
0740_006 0740_006 SP1 OTBCWUI_NEO_07 OTBCWUI_NEO_07 40_006_SP04
OTBCWUI_NEO_07 OTBCWUI_NEO_07 40_006_SP02OTBC 40_006_SP03
40_006 40_006_SP01 WUI_BTP_CF_0740 OTBCWUI_BTP_CF
_006_SP02 OTBCWUI_BTP_CF _0740_006_SP04
_0740_006_SP03
SAP UI5 1.71.*

SAP UI5 1.71.*
Invoice Solution
SAP UI5 1.84.*
7.6/20.4 SPS3
NA NA NA SAP UI5 1.84.*
SAP UI5 1.96*
SAP UI5 1.96*
SAP UI5 1.71.* SAP UI5 1.71.*
SAP UI5 1.84.* SAP UI5 1.84.*

Invoice Solution SAP UI5 1.71.*
NA NA
7.6/20.4 SPS2 SAP UI5 1.84.*
SAP UI5 1.96* SAP UI5 1.96*
SAP UI5 1.71.* SAP UI5 1.71.*
SAP UI5 1.84.* SAP UI5 1.84.*

Invoice Solution SAP UI5 1.71.*
NA SAP UI5 1.71.*
7.6/20.4 SPS1 SAP UI5 1.84.*
SAP UI5 1.84.* SAP UI5 1.96* SAP UI5 1.96*
SAP UI5 1.71.* SAP UI5 1.71.* SAP UI5 1.71.*

Invoice Solution SAP UI5 1.71.* SAP UI5 1.71.*
7.6/20.4 SAP UI5 1.84.* SAP UI5 1.84.*
SAP UI5 1.84.* SAP UI5 1.84.*
33
SAP UI5 1.96* SAP UI5 1.96*
SAP UI5 1.71.* SAP UI5 1.71.*
SAP UI5 1.71.* SAP UI5 1.84.* SAP UI5 1.84.*

VIM 7.5 SP11 / SAP UI5 1.71.* SAP UI5 1.71.*
16.3.5 SAP UI5 1.84.* SAP UI5 1.84.*
SAP UI5 1.96* SAP UI5 1.96*
6.11 Electronic Invoices – Supported Formats

The following table lists the supported XML invoice formats:
Country XML Format Version Transformation

1.1"
Italy FatturaPA 1.2.1" /OPT/TRANS_XML_FATTURA
FPA12"
/OPT/TRANS_XML_EDOC_UBL
Xrechnung 1.0" /OPT/TRANS_XML_EDOC_CEFACT
/OPT/TRANS_XML_EDOC_CEFACT1
Germany
ZUGFeRD 1.0"
ZUGFeRD 2.0" /OPT/TRANS_XML_EDOC_CEFACT
ZUGFeRD ZUGFeRD 2.1" /OPT/TRANS_XML_EDOC_CEFACT1
ZUGFeRD 2.1.1"
Netherlands
Belgium Generic UBL format and

Check documentation /OPT/TRANS_XML_EDOC_UBL
Singapore delivery networks
New Zealand
Australia
Generic UBL format and
* Check documentation /OPT/TRANS_XML_EDOC_UBL
delivery networks
Version 1"
Mexico Factura Version 3” /OPT/TRANS_XML_FACTURA_MX
Version 4”
China OFD OFD format
Poland Faktura Check documentation /OPT/TRANS_XML_FAKTURA_POL
No transformation, used new parsing

Switzerland Envelope Version 2.0
class
34
See VIM Invoice Solution Scenario Guide for more information on electronic invoices.
35
7 Fixed issues
7.1 Document Processing (DP)

VIMI-30427
For alternate payee with multiple partner bank types, the first bank type is automatically populated in
indexing screen instead of blank value.
VIMI-30652
Due date in the indexing screen is incorrectly calculated when payment terms are changed.
VIMI-30874
In the indexing screen changing vendor number does not change vendor name.
VIMI-30917
In the indexing screen for a business partner with more than one address, there is an error when
entering country information.
VIMI-30920
The withholding tax amount is not rounded correctly when the base amount is manually entered in the
indexing screen.
VIMI-30921
When parking Non-PO invoice using BDC 14 with more than 6 withholding tax codes, withholding tax
calculation is incorrect.
VIMI-30973
For PO invoice in context to India GST with unplanned delivery costs tax calculation is incorrect.
VIMI-31002
The business rule ‘Cannot Verify Quantity/Price Exceptions (PO)’(process type 425) updates the data
when simulate rules option is executed.
VIMI-31089
Single Click Entry does not work when the archive function to retrieve the binary content has component
other than 'data'.
VIMI-31099
In the indexing screen tax number is not changed automatically when you change the vendor number.
VIMI-31133
During online posting of PO invoice in context to India GST, there is balance error due to incorrect GST
tax calculation.
VIMI-31134
36
For PO invoice with multiple GR's and posting with partial quantities the exception 'Manual check
needed' (process type 113) is incorrectly triggered.
VIMI-31199
After referring to another role using bulk option, the process options shown to the referee are incorrect.
VIMI-31327
During background posting of Non-PO invoice with Non-QR IBAN and empty ISR BDC error "Specify
the ISR/QR reference number or delete QR-IBAN" occurs.
VIMI-31330
In the indexing screen when vendor is changed the house number of the new vendor is not updated.
VIMI-31341
When choosing multiple lines in the smart coding proposal window, the line items are updated
incorrectly.
VIMI-31377
The exception ‘Currency mismatch (PO)’ (process type 155) is incorrectly triggered when PO currency
and freight condition currency are different and the DP header currency does not match PO currency.
VIMI-31407
Runtime error occurs in function "/OPT/VIM_FILL_EKSEL_PROP".
VIMI-31436
The amount and quantity in the line-items are swapped when BDC 200 is used to post the invoice in
foreground.
VIMI-31437
Background posting of a PO credit memo fails when the DP document has return items.
VIMI-31520
Change documents are not getting created when vendor VAT number is changed in the indexing screen.
VIMI-31521
GST partner field is not getting updated in the indexing screen when vendor number is changed.
VIMI-31580
Change documents are not getting created when data in process tab of the indexing screen is changed.
VIMI-31592
Error while starting Single Click Entry control in multibackend scenario when IES profile is not active in
the satellite system.
VIMI-31593
Non QR IBAN is causing posting error when ISR number is entered in Swiss invoice.
VIMI-31601
37
Performance issue when multiple withholding tax types are maintained and DP has more number of
lines items.
VIMI-31606
In the indexing screen the search help on “Requester E-mail" does not work properly when executed
more than once without exiting the search screen.
VIMI-31616
During online posting of down payment invoice (using BDC 51) with no line items partner bank type is
not transferred to SAP accounting document.
VIMI-31627
When working with SCE for SAPGUI, some country specific units of measure cannot be selected on
the invoice image.
VIMI-31725
The net price in the line items tab of the indexing screen displays the amount multiplied by 100 for PO
invoice with non-decimal currency.
VIMI-31754
Smart coding line-item proposal displays incorrect company code if the company code value consists
of only two characters.
VIMI-31772
Withholding tax is not recalculated when posting date is changed in the indexing screen.
VIMI-31921
With maintenance of particular exemption certificate number TDSU/S194Q in vendor master, TDS
amount is calculated incorrectly.
VIMI-31923; VIMI-32197
The exception ‘Tolerance exceeded’ (process type 406) is incorrectly raised when currency in PO and
in the DP are different.
VIMI-31950
Performance improvement in the proposal function when proposing open PO line items for invoice.
VIMI-31958
The vendor address details are not reflected in the indexing screen when vendor master address data
is updated from VIM.
VIMI-32023
For Canadian invoice, tax code is not correctly populated when “'Tax determination using OT tax table' is
selected for DP document type.
VIMI-32024
In indexing screen when line items are filled, tax jurisdiction code is incorrectly populated.
38
VIMI-32159
For a service PO Invoice, ‘Tolerance exceeded’ (process type 406) exception is not triggered when
amount is greater than GR amount and both SR-IV and GR-IV are checked.
VIMI-32167
When using process option 'Send Email to SRM', e-mail content is truncated when an e-mail ID is longer
than 120 characters.
VIMI-32190
For a Non-PO invoice cash discount base amount is displayed as gross amount even though discount
base is configured as net amount and “Plants Abroad Active” is activated.
VIMI-32201
When a DP document is set to obsolete, actual role is not updated in the process log.
VIMI-32215
During online posting of PO invoice with multiple POs incorrect PO is shown in header in MIRO.
VIMI-32278
For Non-PO invoice tax calculation is incorrect when lines in DP document are interchanged in the
indexing screen.
VIMI-32369
The exception 'Tolerance Exceeded' (process type 406) is raised when there is PO with a Service item
type and GR-Based IV flag is checked instead of S-Based IV flag.
VIMI-32401
Performance issues due to the lock requests when using PO proposal function.
VIMI-32499
While posting a service PO Invoice using BDC 6 error ''Acct assgnt XX for order item XXXXXXXX
XXXXX does not exist" occurs.
VIMI-32501
The 'Vendor address mismatch' (process type 122) exception is getting incorrectly triggered even after
having the correct vendor address in the DP indexing screen.
VIMI-32506
WBS element value from smart coding proposal is not transferred to DP indexing screen.
VIMI-32512
The exception ‘Manual Check needed/Missing Data for indexing lines’ (process type 113) is incorrectly
triggered for partial PO invoice having both material lines and freight lines.
VIMI-32525
39
Dummy DP documents are not created for MM invoices posted outside of VIM or DP document data is
not synchronized when transactions other than MIRO / MIR7 / MR1M are used. A new Z-constant
005/TCODE_ON_BADI has been introduced to store possible transaction codes.
VIMI-32578
During background posting of a Non-PO invoice house bank account value is not transferred to SAP.
VIMI-32601
For a PO invoice with inverted tax rate, after posting the tax rate is visible as direct tax rate in the SAP
invoice.
VIMI-32684
During background posting of Brazilian PO Invoice, the series number is not passed to SAP invoice.
VIMI-32686
While posting a Non-PO invoice using BDC ID 41, there is error for few fields in profitability segment.
VIMI-32746
The “Display Log” button is not shown in the DP document after executing /OPT/DR_BR_WAIT report.
VIMI-32775
Delivery note proposal is not showing open invoice lines if posting period is not open.
VIMI-32903
Payment Date for PO and Non-PO invoice is not updated when the posted SAP document is cancelled.
VIMI-32911
For Non-PO invoice when amounts are changed in the indexing screen to adjust the balance, run time
error occurs when using third party tax calculations.
VIMI-32949
Exception ‘Down Payment Clearing (PO)’ (process type 416) is raised incorrectly for a reversed down
payment document.
VIMI-32981
NFE values are erased from line-Item data when any action done on the DP indexing screen.
VIMI-33106
The exception ‘Unit of Measure Mismatch’ (process type 156) is triggered even though unit of measure
in the DP is same as in PO.
VIMI-33332
Error message "Enter a Controlling area" appears when cost center is entered in line-item tab of the
indexing screen.
VIMI-33364
40
‘Suspected duplicate’ (process type 105) exception is not triggered when DP has IP vendor and already
an invoice is posted against main PO vendor.
VIMI-33431; VIMI-33432
Background posting of Non-PO invoice using BDC 41 fails for OTV vendor with QR-IBAN.
VIMI-33666
When changing the document type from Non-PO to PO, subsequent credit/debit options are not
appearing in the transaction type (VORGANG) dropdown in the basic data tab of the indexing screen.
VIMI-33790
During online posting the partner bank type value changed in MIRO/FB60 is not updated back to VIM.
7.2 Invoice Approvals
VIMI-31253
After removing manager ID for a user in COA maintenance transaction (/OPT/AR_COA), the change
is not saved.
VIMI-31400
There is runtime error when opening an approval workitem that has negative quantities in line items.
VIMI-31775
During approvals there is a short dump when line item has incorrect HSN code.
VIMI-31954
Posted Approval is not triggered for Non-PO invoice when the amount exceeds check limit for
Tolerance Key "AN".
VIMI-32026
In workflow history PDF log last approver is not displayed in certain scenarios.
VIMI-32526
Runtime error 'DYNPRO_FIELD_CONVERSION' occurs while executing approval workflow when
line-item quantity is greater than 10 digits.
VIMI-33078
Performance issues when using 'Display changes' button in COA maintenance transaction
(/OPT/AR_COA).
VIMI-33436
41
When using COA report download functionality, the values for the amount limit in Approval Limit view
are not downloaded in proper user format.
7.3 Invoice Exception

VIMI-31076
The user name and timestamp is missing for the most recent comment saved in the blocked
dashboard.
VIMI-31287
Blocked invoice workflow is not triggered for PO with outline agreement (SAP document type WK).
7.4 VIM Notifications

VIMI-31077
The reminder notification report shows incorrect current agent in the notification email when there are
more than one substitutes for user in COA.
VIMI-32289; VIMI-31458
Hyperlink is not displayed properly in approval and referral notifications.
7.5 VIM Analytics (new VAN) Report and VAN Liability Report.
VIMI-29537
Special characters are not displayed when viewing the archived mail originated from RTV process
option.
VIMI-30752
VIM Process Status text is incorrect when payment block is removed from accounting document in
SAP and document is posted.
VIMI-30851
The start date and start time are incorrect in the history log when user time zone is different to server
time zone.
VIMI-30890
User details of current agent is not displayed when approver user ID and SAP user ID are different.
VIMI-30901
There is runtime error when executing VIM Analytics for specific statuses.
VIMI-30960
42
Clearing date and time are showing incorrect in VIM Analytics for documents cleared in Australian
time zone.
VIMI-31683
Multiple entries for the same DP document if the same DP document number is entered more than
once in the report selection option.
VIMI-31756
For a credit memo discount amount changed during payment run is not reflected.
VIMI-31959
Time stamps are not displayed correctly when user cancels processing of a DP document and posts it
in next step.
VIMI-31994
Image cannot be displayed in VIM when CMIS repository is used for archiving documents.
VIMI-32050; VIMI-33658
Runtime error occurs in VIM analytics when in selection screen small number is entered as maximum
records after implementing correction of VIMI-32050.
VIMI-33007
DP document sent back to central system still reports target key as satellite system.
7.6 Central Reporting and other reports

VIMI-28680
The automation report and KPA report show different count for the first pass documents.
VIMI-31110
Performance issues in DR BR wait program when writing change logs for DP document with many
line items.
VIMI-31317
When using exclude single PO values with open only check box in the PO staging download program,
some open POs are not downloaded.
VIMI-31517
Display log option is missing after rerun program is executed for a DP document with background error.
VIMI-31610
Productivity report includes background processing time and shows incorrect wait time.
VIMI-31737
In KPA report, DP documents that are auto posted in VIM are considered to be posted outside VIM.
43
VIMI-31738
Exception reason is incorrectly updated in KPA report when agent remains the same and exception
moves to another one.
VIMI-32345
In ILC Report when length of text is beyond 40 characters, "Activity" in VIM Analytics & “Text” are not
displayed in full.
VIMI-32379
For posted approval documents new DP document is not getting created when using report
/OPT/INV_CANCL_RECRT to cancel existing DP and create new one.
VIMI-32500
The re-run rules program does not exclude DP documents with obsolete status.
VIMI-32580
When executing DR BR report(/OPT/DR_BR_WAIT) for DP document in wait status there is no role
change from wait role to initial role when time limit is reached.
7.7 VIM Workplace

VIMI-31511
Performance issue with VIM Workplace when working with filters.
VIMI-31760
My pending tab entries for current agent is not consistent with VIM Analytics when bulk entries are
fetched.
VIMI-32220
While using bulk refer option workitem ID is not saved in VIM 1Log table.
VIMI-32292
Runtime error 'DYNPRO_FIELD_CONVERSION' occurs while opening a DP which has large amount
values (> 15 digits).
7.8 Web Approval Portal
VIMI-30710
Information/Error messages related to earmarked funds are not shown in approval portal while
performing approval.
44
7.9 Fiori Approve Invoices app
VIMI-31343
In Fiori Approval app the text data for few line items fields is missing.
VIMI-32343
The data for WBS Element is not displayed for PO Invoices.
VIMI-33128
Timestamp for main invoice image is incorrect.
VIMI-33657
The Fiori Approve invoices app is showing just blank page after launching.
7.10 My Approved Invoices app

VIMI-31619
The net amount is shown as the gross amount for Non-PO invoice.
VIMI-32200
The invoice list does not display values for few fields.
VIMI-32898
My Approved Invoices app is not showing line-item descriptions for PO invoices.
7.11 Fiori Enter Cost Assignment Simple app

VIMI-31736
The bulk approval icon is not enabled due to an issue in sorting the invoice list.
7.12 Fiori Enter Cost Assignment Advanced app

VIMI-31387
The username in the comments section is abbreviated with three dots, even though enough space is
provided on the screen.
VIMI-32881
The header field “On behalf of” is left blank when OPT user id is different from SAP user id.
7.13 Resolve Exceptions app

VIMI-33399
45
Sort feature causes runtime error for all sort fields except for DOCID.
VIMI-33406
Unable to search with Vendor name (VEND_NAME) field.
7.14 Vendor Invoices Report app

VIMI-31269
Timeout error in /OPT/CL_V_VA2_DATA_PROV_BE when executing the Vendor Invoices Report app
from Fiori.
7.15 IDF Framework (BC Inbound)

VIMI-30902; VIMI-33396
When the line-item amounts from OCR have large values or negative values there is error when
viewing the DP document.
VIMI-30941
Transformation for Mexico invoice format CFDI version 4.0 is not working.
VIMI-31108
During inbound processing of IDOC the value for Tax Amount in Local Currency ( field HWSTE) is not
transferred to VIM.
VIMI-31112
During inbound processing of XML invoice having more than one line item with different units of
measure the PDF visualization display incorrect quantity units.
VIMI-31176
For Indian invoices in context to GST, the tax amount and total tax amounts values are not getting
determined during inbound processing.
VIMI-31254
For a PO invoice with non-decimal currency the amounts field values are not converted to internal
format.
VIMI-31935
During inbound processing of credit memos fields related to original invoice reference are not auto
populated.
VIMI-31976
When creating DP documents from inbound channels 2HEAD table fields are not properly updated
when using custom logic modules.
VIMI-32036
46
Runtime error COMPUTE_BCD_OVERFLOW occurs when large amount in PO line items is delivered
from IES.
VIMI-32176
Runtime error 'DUPLICATE_KEY_ERROR' occurs while storing OCR result.
VIMI-32218
For invoices created using inbound channel currency field is stored without proper conversion in case
of non-decimal currencies.
VIMI-32344
While creating DP documents from IDOC channel large reference number does not split.
VIMI-32395
The Unit (BTSME) value of last line item in the IES result table is filled into field Unit (BPMRE) of
another line item in the DP indexing screen.
VIMI-32547
The vendor VAT number is not auto determined as the field value for ‘EGMLD’ does not pass to VIM
during inbound processing.
VIMI-32708
Invoices uploaded from IDOC input channel are created as Credit Memo.
VIMI-32795; VIMI-33639
During inbound processing DP workflow is not triggered due to corrupt ICC value in line-item tax rate
fields.
VIMI-32958
While creating a PO DP document without company code, if vendor determination fails, DP workflow
goes into error.
7.16 Others
VIMI-32375
When upgrading to VIM 7.5 SP11 there is error due to key conflicts for the BC Sets
/OTEXVIM/VIM75_SP9_CUSTOMIZING.
VIMI-32931
Performance issues due to standard BTE (/OPT/BTE_IF_00005010) when clearing posted
documents.
VIMI-33087
47
Translations for few process options are incorrect.
VIMI-32194
Labels for posting date field are missing for Swedish and Finnish languages.
VIMI-33209
The XML visualization in the attachment list does not translate headings into different languages.
VIMI-33410
When using RTV option if multiple versions for RTV templates are maintained in constants latest
version is not considered.
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 General Invoice Solution BC Set

Activate the BC set /OTEXVIM/VIM76_SP4
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. If you have
changed the VIM baseline customizing, make sure the BC set will not overwrite any customizing.
8.2 Activate BC Set for Inbound

Activate the BC set /OTX/VIM76_SP4_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.
8.3 Adjust the IES mapping for VIM Foundation

This step is mandatory after the activation of the BC set /OTX/VIM76_SP4_INBOUND.
Navigate into the data model definition customizing of VIM Foundation (/OTX/PF00_IMG):
48
Select the data model PS03_VIMCL and navigate further into External Data Mapping > Level
Mapping. Select the level 1 (ExtractionResult) and navigate into Field Mapping. Delete the four entries
for TaxBlocks highlighted below:
Save the changes into a transportable customizing request. That needs to be transported further
along with the transports for BC set activation.
8.4 Activate BC Set for Fiori Apps

The BC set /OTX/VIM76_SP4_FIORI 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.
49
8.5 Mail templates for VIM 3S User Registration
Import the transport for the Mail templates for VIM Supplier Self Service User Registration under the
folder Mail templates for VIM 3S Registration.
For more information about the content and how to use it please refer to Configuration Guide
8.6 Installing transport with layout variants

Update transport with layout variants for VIM Analytics is provided in the file
additional_transport_withlayout_for_ecc6.0.zip. The content provided in the transport must be
imported into every client because the transport contains client specific data.
8.7 Configuration delivered with BC set

8.7.1 Implement the next generation model for E-Invoice in VIM
(VIMI-31637)
Processing of E-Invoice using New ABAP Class Based Parsing:
Configuring XML mapping using direct XML Parsing:
Semantic Mapping:
Execute /n/OPT/XML_MAP transaction. Alternatively run /n/OPT/SPRO -> Document processing

configuration -> General configuration -> Incoming document processing -> Processing of electronic
invoices -> Semantic mapping
Maintain the root node by clicking on new entries
50
Select the newly added entry and double click on “Mapping of XML data and Semantic data”
In the next screen enter the root node, sequence, combination of nodes, field type and semantic name.
1. Root node: Root node of the XML document
2. Serial number: Enter the sequence number
3. External field: Enter the combination of nodes
4. Field type: Enter field type as either header or item
5. Semantic Name: enter the semantic name (while entering the semantic names use the common
names across all common fields)
Note: Instead of using it directly use proposal tool /OPT/XML_MAP_PROP, with minimum effort system
proposes the external names, user has to enter the semantic name and field type.
Handling of additional fields:
Configure the XML formats:
Navigate to the path /n/OPT/SPRO -> Document processing configuration -> General configuration ->
Incoming document processing -> Processing of electronic invoices -> XML formats configuration
51
Enter the XML format name (I.e. meaningful name in short form to identify an XML format), enter the
country, usage name of XML format in the respective country, root node of the document.
XML nodes enhanced mapping:
Navigate to the path /n/OPT/SPRO -> document processing configuration -> general configuration ->
Incoming document processing -> Processing of electronic invoices -> XML nodes enhancement
mapping configuration
In this configuration maintain the fields which required to handle additional functionality. As of now
handling only attachments and date fields as part of this configuration.
52
Handling of Attachments:
To handle attachments, need to maintain the attachments related attributes in this configuration.
Maintain the following semantic names related to attachments and its relevant node names.
1. AttachedDocument – this semantic name holds the content of the attachment
2. AttachedDocumentFilename – file name of the attachment
3. AttachedDocumentMimecode – Mime type of the attached document (optional)
Semantic name: Maintain the above semantic names to handle attachments

XML format: Maintain the XML format
Country: Maintain the country code
Data Type: R – Attachments
Node of XML documents: Node in the XML document related the above-mentioned semantic names
Note: In some cases, mime type not mentioned explicitly. It is part of file name in this case no need to
maintain the mime type explicitly in this configuration
Handling of Date formats:
This configuration is used to handle different date formats. By default, the following semantic names
are delivered as part of baseline which are using for different dates using in VIM. By default, system
process the following formats.
Default delivery of semantic names related to dates:
1. ActualDeliveryDate
2. InvoiceIssueDate
3. InvoicingPeriodEndDate
4. InvoicingPeriodStartDate
5. PaymentDate
6. PaymentDueDate
7. PaymentTermsReferenceDate
8. PrecedingInvoiceIssueDate
9. ValueAddedTaxPointDate
Default date formats supporting:
53
1. YYYYMMDD
2. YYYY-MM-DD
3. YYYY/MM/DD
4. YYYY.MM.DD
If any of the XML document using other than the above-mentioned formats, need to maintain in the
configuration. To maintain the dates with different formats, do the following.
Semantic name: Maintain the date related semantic names

XML format: Maintain the XML format
Country: Maintain the country code
Data Type: D – Date
Date format: choose the date format
XML Mapping Proposal:
Navigate to the path /n/OPT/SPRO -> document processing configuration -> General configuration ->
Incoming Document Processing -> Processing of electronic invoices -> XML Mapping proposal
54
8.7.2 Improvements for the Central Reporting for VIM Invoice (VIMI-
31906)
Tool for scheduling of Central reports:
Execute /OPT/SPRO transaction and navigate to Vendor Invoice Management > Cross Component
Configuration > Central Reporting > Maintain Job Utility > Maintain Job Sequence Or directly execute
the transaction /OPT/VIM_CEN_JOB.
55
After executing the above function, a maintenance view will be opened to maintain the job sequence
and variants as below.
Job prefix: Enter any free text in ‘Jobprefix’ column. Job name will be starting with prefix text, followed
by the timestamp
Program name: Enter the program name (aggregation or collection report)
Variant name: Enter the variant name of corresponding program
56
Sequence: Enter the step sequence of job
Function module: This function module is used to modify the variant values of report. The template for
this function module is /OPT/V_CR_GET_VARIANT_VALUES.
8.7.3 QR code for Portugal (VIMI-32739)

To configure process types for Portuguese invoices:
1. Run the OPT/VIM_8CX1 transaction.
Alternatively, run the /OPT/SPRO transaction and navigate to OpenText Vendor Invoice Management
Invoice Solution > Document Processing Configuration > Process configuration > Maintain Process
Types.
2. Maintain process type 574 - Missing QR Code/ATCUD (NPO) as an exception.
3. Configure the following user process options to the process type:
4. Maintain process type 573 - Missing QR Code/ATCUD (PO) as an exception.
5. Configure the following user process options to the process type:
57
Configuring document types:
In this step, you configure the business rules specific to Portuguese invoices for baseline document
types NPO_75 & PO_75.
To assign the business rule to document type PO_75:
1. Run the /OPT/VIM_1CX1 transaction.
Invoice Solution > Document Processing Configuration > Document Type Configuration > Maintain
Document Types.
2. On the Document Type Definition Overview screen, mark the document type PO_75 and double-click
Document Processes in the Dialog Structure.
3. Configure process type 573 - Missing QR Code/ATCUD (PO).
4. Mark process type 573 and double-click Proc. Type. Det. Sequence in the Dialog Structure.
5. On the Proc. Type. Det. Sequence Overview screen, maintain process type 573.
6. Mark the process type and double-click Sequence Steps in the Dialog Structure.
7. On the Sequence Steps Overview screen, configure field INV_REF_NUM as a required field.
8. Double-click Index Screen Options in the Dialog Structure.
9. On the Index Screen Options Overview screen, configure the DP document process type.
58
10. On the Index Header Configuration, add the entries for ATCUD and ATUCD_VAL as display only
fields.
To assign the business rule to document type NPO_75:
1. Run the /OPT/VIM_1CX1 transaction.
Invoice Solution > Document Processing Configuration > Document Type Configuration > Maintain
Document Types.
2. On the Document Type Definition Overview screen, mark the document type NPO_75 and double-
click Document Processes in the Dialog Structure.
3. Configure process type 574 - Missing QR Code/ATCUD (NPO).
4. Mark process type 574 and double-click Proc. Type. Det. Sequence in the Dialog Structure.
5. On the Proc. Type. Det. Sequence Overview screen, maintain process type 574.
59
6. Mark the process type and double-click Sequence Steps in the Dialog Structure.
7. On the Sequence Steps Overview screen, configure field INV_REF_NUM as a required field.
8. Double-click Index Screen Options in the Dialog Structure.
9. On the Index Screen Options Overview screen, configure the DP document process type.
10. On the Index Header Configuration, add the entries for ATCUD and ATUCD_VAL as display only
fields.
To configure characteristic specific document type for Portugal:
1. Run the /OPT/SPRO transaction and navigate to OpenText Vendor Invoice Management Invoice
Solution > Document Processing Configuration > Document Type Configuration > Characteristic
Specific Document Type Configuration.
2. On the Characteristic Specific Attributes Overview screen, mark the PT characteristic and double-
click Characteristic Specific Process Types in the Dialog Structure.
60
3. On the Characteristic Specific Process Types Overview screen, configure the process types 573 and
574.
To map the IES and VIM fields:
1. Run the SM30 transaction.
2. Enter /OTX/PS03_IESMAP as the table name and maintain the highlighted entry.
8.8 Configuration not delivered with BC set

8.8.1 IES Extraction Analytics for invoice – manual changes
required related to obsolete table /OTX/PF08_T_DEAP
Some changes in the analytics infrastructure require changes in Customizing of VIM Invoice Solution.
Table /OTX/PF08_T_DEAP will not be used in IES Analytics Report anymore, therefore all configuration
entries related to this table must be deleted manually.
Please do the following steps for solution Supplier Invoice. Changes can be saved in a customizing
Transport request, which can be transported to another system.
1. Call Transaction Code /OTX/PF00_IMG. Navigate to Workplace Configuration -> Dynamic Data
selection.
2. Select Work Object Type PS03_DEA_INV.
3. Double click on menu ‘Tables’ on the left side. On the right side delete the line for Table
/OTX/PF08_T_DEAP in the table.
61
4. Double click the menu ‘Table Joins’ on the left side. On the right side delete the line with Right Table
is /OTX/PF08_T_DEAP. In the pop up click the button ‘all entries’. If no such line exists, please ignore
this step.
5. Double click the menu ‘Table Fields’ on the left side. On the right side delete all lines where column
Table Name is /OTX/PS08_T_DEAP.
6. Run report /OTX/PF08_P_DEAS_MIGRATE for the given solution in productive mode. This report
will copy values from /OTX/PF08_T_DEAP into the /OTX/PS03_T_DEAS Tables.
8.9 Optional Post Installation Activities

8.9.1 Improved PO line-item matching (VIMI-32130)
If you are using PO Line Determination Setting “OK – Use OCR lines as basis without deletion of
incomplete lines”, the new determination logic should be assigned.
Navigate to the following customizing node:
Check whether new PO line determination ID 104 is available on system (delivered with BC Set).
62
Select ID 104 and Double-click to check detail settings
Double-click PO Line Determination Fields in the Dialog structure to check steps:
The new matching process is used in PO line based processing / enrichment / matching.
The matching process first tries to match 3 fields within step ID 1 (MAKTX / MENGE / NETPR /
WRBTR) for each index line against the PO and the GR. If no unique match is found, step ID 2 is
processed. Now, the process match is more relaxed with the same fields (MAKTX / MENGE / NETPR
63
/ WRBTR): quantity can be smaller or the same as in PO / GR. Parts of the material text are matched
against PO / GR material text and material number. If again no unique match is found, the process
takes step ID 3 with an even more relaxed match for the fields MAKTX / MENGE / NETPR: the price
can be smaller or the same as in PO / GR. Various steps with different detail levels are used to find a
unique match.
Navigate to the following customizing node:
Assign new PO line determination ID to PO document type(s) with “OK” setting using line item data:
Select a PO related DP Document Type that has “OK” determination setting and press “Details”.
Scroll down to “Line Item Configuration” - PO Line Automation.
Change the Determination Logic ID (PO Line Determination ID) to 104.
Repeat for all PO related DP Document Types with “OK” determination
Save your settings to finish the process
8.10 Review Known Issues

Review the section “Known Issues” and verify whether you need to perform additional adjustments of
VIM configuration.
64
9 Known issues
The following known issues exist in this release.
Issue number Issue description
VIMI-33698 In case company code is not determined by the IES and not entered during the
OCR validation, or if the company code is cleared during invoice DP processing,
tax blocks data (multiple tax entries in invoice header) is deleted from the
invoice.
VIMI-34130 In the Enter Cost Assignment app when selecting tax code at line items level
there is error "Object Not Found". Issue is fixed and will be released for SPS5.
VIMI-33848 In the "My Approved Invoices" app search results list is not same as the
displayed count and also pagination is not aligned.
VIMI-33977 In the "My Approved Invoices" app there is no result when input search
character length is greater than 14.
BOB-7545 When downloading the line-item data from the Fiori "Enter Cost Assignment
Advanced Coding" app, there is an issue with the decimal separator format.
Also, when uploading the same data the line-item net amount remains zero.
VIMI-34144 In the e-invoice mapping proposal tool delivered in this SP when navigating
using mouse scroll down option or with a page down action all the characters
within the columns External field name, Value, Semantic Name are changing to
capital letters.
VIMI-34365 When using SAP GUI for HTML, tooltips are not working for few UI elements.
Native SAPGUI can be used as a workaround in case you are affected by the
problem.
VIMI-34369 When using SAP GUI for HTML, some interactive UI elements are not navigable
and accessible using keyboard. Native SAPGUI can be used as a workaround in
case you are affected by the problem.
VIMI-34371 When using SAP GUI for HTML, screen reader does not read the corresponding
label for some UI elements. Native SAPGUI can be used as a workaround in
case you are affected by the problem.
VIMI-34367 For Approve Invoices and Enter Cost Assignment Advanced Fiori App, some
icon column labels are missing.
65
10 Documentation extensions
10.1 Installation Guide
10.1.1 Section 13.1.1 – Selecting and downloading the required components
for different scenarios
In step 1 of the procedure, the following table must be added:
Table 13-6: Support package 4
Support
Component SAR File Version
Package
OTEXVIM OTEXVIM_SP04_80700_006.SAR 80700_006 4
OTBCSL30 OTBCSL30_SP04_80700_006.SAR 80700_006 4
OTBCSL33 OTBCSL33_SP04_80700_006.SAR 80700_006 4
OTVIMARC OTVIMARC_SP03_80700_006.SAR 80700_006 3
OTVIMBW OTVIMBW_SP01_80700_006.SAR 80700_006 1
66
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
67

VIM 7.6 SPS4 - Release Notes For Invoice Solution

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VIM 7.6 SPS4 - Release Notes For Invoice Solution

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

Release Notes for Invoice Solution

Product Released: 2022-10-31

Release Notes Revised: 2023-07-17

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

5 Packaging and Documentation .................................................................................................. 14

6 Supported Environments and Compatibility ............................................................................. 25

7 Fixed issues .................................................................................................................................. 36

8 Post Installation Activities .......................................................................................................... 48

9 Known issues ............................................................................................................................... 65

10 Documentation extensions ......................................................................................................... 66

11 Contact information ..................................................................................................................... 67

1.1 Release Naming Information

1.2 Release Notes revision history

Revision date Sections revised Description of revisions

2022-11-09 Initial version

New delivery file for Cloud Foundry multitarget

2.1 General Data Protection Regulation (GDPR)

3.1 Supported ArchiveLink Content Repositories

VIM is specifically tested and validated for

3.2 Additional Installation Prerequisites

• 2353336 - Workflow: Runtime error CREATE_DATA_UNKNOWN_TYPE.

4.2 Improved PO line-item matching (VIMI-32130)

4.3 Inbound: Validation decision based on Supplier Profiles

4.4 UI update of Confirm Quantity and Price app (VIMI-24549)

4.5 Editable Email templates for VIM Supplier Self Service

Registration mail template - /OPT/VIM_3S_REGISTRATION

Confirmation mail template - /OPT/VIM_3S_CONFIRMATION

Transaction /n/OTX/PS34_SENDEMAIL is introduced to resend registration emails to suppliers, instead

4.6 Display of Vendor Name in Vendor Invoices Report Fiori App

4.7 New processing model for electronic invoices (VIMI-31637)

For more information, refer to Scenario Guide for Invoice Solution.

Tool for proposal of E-Invoice mapping:

For more information, refer to Configuration Guide for Invoice Solution.

4.8 Swiss QR Bill - XML support using the parsing class

For more information, refer to Scenario Guide for Invoice Solution.

4.9 Support for China E-Invoice (VIMI-33285)

4.10 Improvements for the Central Reporting for VIM Invoice

Using the Intermediate Data Report:

This includes display of intermediate data for below individual reports:

• Exception Analysis Report

• Key Process Analytics Report

For more information, refer to Reference Guide for Invoice Solution.

4.11 Performance improvements on /OPT/DR_BR_WAIT program

With this feature the following were introduced:

For more information, refer to Configuration Guide for Invoice Solution.

4.12 Performance improvements for validating the coding data of

NPO class /OPT/NON_PO_INVOICE_22_4 and PO class /OPT/PO_INVOICE_22_4 have been

• Execute work item from VIM workplace

4.13 Implementation of QR code for Portugal (VIMI-32739)

4.14 QR Code Digital Signature Validation for India - Simple Check

4.15 Inclusive Language - Change Customizing (VIMI-30674)

4.17 Support of comments for obsoleted invoices by Ariba CIG

4.18 Support of vendor comments by Ariba CIG integration

5 Packaging and Documentation

5.1 Packaging and Delivery Information

5.1.1 ABAP Packages

Component Package file name

5.1.2 Language Support

*Supported with limitations (not all texts may have translations)

UI = user interface only

B = both user interface and User Guide

5.1.3 Non-ABAP Packages