VIM 20.4 SPS3 - Release Notes For Invoice Solution

OpenText™ Vendor Invoice Management
for SAP®
Release Notes for Invoice Solution
Version 20.4 SPS3
Product Released: 2022-04-29
Release Notes Revised: 2023-03-29
OpenText™ Vendor Invoice Management for SAP® Invoice Solutions Version 20.4 SPS3 Release Notes
Contents
1. Introduction .................................................................................................................................... 6
1.1. Release Naming Information ..................................................................................................... 6
1.2. Release Notes revision history .................................................................................................. 6
2 New Features .................................................................................................................................. 9
2.1. User Preference Settings Fiori App (VIMI-24555) ..................................................................... 9
2.2. Rejection reasons search help (VIMI-27872) ............................................................................ 9
2.3. "On Behalf" status in the Fiori apps header (VIMI-30444) ........................................................ 9
2.4. E-Invoice implementation for Poland (VIMI-29417)................................................................... 9
2.5. New business rule for check of maximum exchange rate difference (VIMI-29986) .................. 9
2.6. New business rules for VAT ID/flexible tax check (VIMI-29824) ............................................. 10
2.7. Normalization for IBAN, vendor and recipient tax ID fields (VIMI-29972) ............................... 10
2.8. Determining vendor VAT ID/tax number (VIMI-30106) ............................................................ 10
2.9. Supporting Advanced Tax Calculation (VIMI-29801) ............................................................... 10
2.10. Enabled line-item reference fields for Non-PO invoice posting (VIMI-30233) ......................... 11
2.11. Embedded Analytics for IES Extraction (VIMI-30938) ............................................................. 11
2.12. Enhance Extraction Analytics in VIM Central Workplace for Supplier Invoices Solution
(VIMI-30937) ............................................................................................................................ 11
2.13. Support of incoming non-PO invoices sent as SOAP message
InvoiceERPRequest_In (VIMI-28669) ..................................................................................... 12
2.14. Support of incoming invoices sent as SOAP message InvoiceRequest_In (VIMI-
29077)...................................................................................................................................... 12
3 Delta information for VIM 7.5/7.6 customers ............................................................................. 13
3.1. Corresponding Support Package levels .................................................................................. 13
4 Packaging and documentation ................................................................................................... 14
4.1. Packaging and delivery information ........................................................................................ 14
4.1.1. Mandatory packages .................................................................................................. 14
4.1.2. Packages and Transports for Additional Scenarios .................................................... 14
4.2. Related documentation ............................................................................................................ 16
5 Supported environments and compatibility .............................................................................. 17
5.1. Supported systems .................................................................................................................. 17
5.2. Supported ArchiveLink Content Repositories .......................................................................... 19
5.3. OpenText product compatibility ............................................................................................... 19
5.4. SAP Netweaver Version compatibility matrix for OAP 20.4 (OpenText Approval Portal) ........ 19
5.5. Approval Portal Downward Compatibility Matrix ..................................................................... 20
5.6. Approval Portal JCo Compatibility Matrix ................................................................................ 20
5.7. Web browser and mobile device support (Approval Portal) .................................................... 21
5.8. Web Viewer support ................................................................................................................ 22
5.9. Brava View support (OAP) ...................................................................................................... 23
5.10. Language support .................................................................................................................... 23
5.11. VIM Fiori Apps: Variants .......................................................................................................... 24
5.12. VIM Fiori Apps: SAP UI5 Version Compatibility ....................................................................... 27
5.13. Electronic Invoices – Supported Formats ................................................................................ 27
6 Installation and upgrade notes ................................................................................................... 29
6.1. ACP file for adjustment of prerequisites .................................................................................. 29
6.2. Installation notes ...................................................................................................................... 29
6.3. Upgrade notes ......................................................................................................................... 30
6.3.1. ACP files for upgrades from VIM 7.5/7.6 .................................................................... 30
6.3.2. BC sets for upgrades .................................................................................................. 30
6.4. Fiori apps requiring report runs ............................................................................................... 30
7 Support Packages ........................................................................................................................ 31
8 Post Installation Activities .......................................................................................................... 32
8.1. Activate BC Set /OTEXVIM/VIM20_4_UPGRADE_SP3 ......................................................... 32
8.2. Installing transport with IES Analytics customizing.................................................................. 32
8.3. Configuration delivered with BC set ........................................................................................ 32
8.3.1. Check for maximum exchange rate difference (VIMI-29986) ..................................... 32
8.3.2. Checks for Flexible tax/VAT ID (VIMI-29824) ............................................................. 35
8.3.3. Normalization of tax IDs, copying of tax IDs (VIMI-29972, VIMI-30106) .................... 36
8.3.4. E-Invoice implementation for Poland (VIMI-29417) ................................................... 37
8.3.5. Payment split exit function for IES integration (VIMI-30922)...................................... 48
8.3.6. Reminder notification not sent for posted approval invoice with no requester
(VIMI-29524) ....................................................................................................... 49
8.3.7. Avoid locks set by DR BR Wait program (VIMI-29668) .............................................. 49
8.3.8. Determination of HSN/SAC code (VIMI-29523) ......................................................... 50
8.3.9. Advance tax calculation feature (VIMI-29801) ........................................................... 52
8.3.10. Enabled line-item reference fields for Non-PO invoice posting (VIMI-30233) ............ 52
8.3.11. Auto population of bank data based on QR-IBAN (VIMI-30876) ..................... 52
8.4. Optional Post Installation Activities .......................................................................................... 53
8.4.1. Warning message when switching between tabs in the indexing screen (VIMI-
25706) ................................................................................................................. 53
8.5. Review Known Issues ............................................................................................................. 53
9 Known issues ............................................................................................................................... 54
9.1. VIM Classic Mode .................................................................................................................... 54
10 Fixed issues .................................................................................................................................. 54
10.1. Fixed issues for 20.4 SPS3 ..................................................................................................... 54
10.1.1. Document Processing (DP) ........................................................................................ 54
10.1.2. Invoice Approvals ....................................................................................................... 60
10.1.3. VIM Notifications ......................................................................................................... 61
10.1.4. VIM Analytics (new VAN) Report and VAN Liability Report ........................................ 61
10.1.5. Central Reporting and Other Reports ......................................................................... 62
10.1.6. VIM Workplace ........................................................................................................... 63
10.1.7. Web Approval Portal ................................................................................................... 64
10.1.8. Fiori Approve Invoices app ......................................................................................... 64
10.1.9. My Approved Invoices app ......................................................................................... 65
10.1.10. Fiori Enter Cost Assignment Advanced app ....................................................... 65
10.1.11. Supplier Self Service app ........................................................................................... 65
10.1.12. Input Channels .................................................................................................... 65
10.1.13. Others ................................................................................................................. 67
11 Documentation extensions ......................................................................................................... 68
11.1. Installation Guide ..................................................................................................................... 68
11.1.1. Section 13.1 – Selecting components for installation or upgrade .............................. 68
11.1.2. Section 23.1.2.1 – OTVIMARC prerequisites ............................................................. 68
11.2. Configuration Guide ................................................................................................................. 68
11.2.1. Section 25.3 – Integrating Ariba Network using Cloud Integration Gateway ............. 68
11.2.2. Section 25.3.1 – Configuring inbound processing (InvoiceDetailRequest) ................ 68
11.3. Security Guide ......................................................................................................................... 69
11.3.1. Section 7.1 – Specific authorization checks ............................................................... 69
12 Contact information ..................................................................................................................... 69
1. Introduction
These Release Notes provide an overview of OpenText™ Vendor Invoice Management for SAP®
Invoice Solutions Version 20.4 SPS3, 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.
OpenText also recommends 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 SAP Invoice Management 20.4 for SAP S/4HANA that is being
released in 2nd quarter of 2022 is “20.4 SPS3”. The release name for this package is “22.2 for SAP
S/4HANA”. This is the first release of SAP Invoice Management that supports SAP S/4HANA 2021
and S/4HANA 2022.
Note that the corresponding release and technical release names of the current SAP Invoice
Management solution for S/4HANA are “22.2 for S/4HANA” and “20.4 SPS3”. When downloading the
additional components from OpenText MySupport, make sure to navigate to the right folder (S/4HANA
or ECC).
1.2. Release Notes revision history

Revision date Sections revised Description of revisions
2022-04-29 Initial release
2022-05-24 New features Minor changes in the descriptions
5.12 SAP UI5 Version

2022-05-24 Changes for backend SPS3 + UI SPS2
Compatibility
2022-10-18 Support of S/4HANA 2022 added
2022-10-21 Language Support Added information on Russian support
11 Documentation
2023-03-29 Created chapter and added several entries
extensions
VIM Invoice Solution - Simple Mode
Please note that with 20.4 SPS 1 “Simple Mode” will be deprecated
and is not supported for productive installations. Please use Classic
Mode.
Note
OpenText Vendor Invoice Management by SAP Solutions 20.4

supports SAP S/4HANA 1610, 1709, 1809, 1909, 2020, 2021 and
2022.
SAP S/4HANA Cloud, Extended editions (EX) are supported by
OpenText Vendor Invoice Management by SAP Solutions 20.4 on the
releases that correspond to the supported on-premise releases listed
above (also see SAP Note 2962569).
Future SAP S/4HANA versions will typically be supported by the VIM

Update (Support Package) directly after release of the new SAP
S/4HANA release.
The following SAP products are not supported by OpenText
Vendor Invoice Management by SAP Solutions 20.4: SAP ERP,
SAP Suite on HANA, SAP Simple Finance, SAP S/4HANA Finance,
and SAP S/4HANA 1511. SAP ERP and SAP Suite on HANA are
supported by OpenText Vendor Invoice Management by SAP Solutions
7.6.
SAP S/4HANA Cloud, essentials editions (ES) are not supported
by any version of OpenText Vendor Invoice Management by SAP
Solutions.
For a complete list of SAP products supported by different versions of

OpenText Vendor Invoice Management, see SAP Note 2339256.
2 New Features
2.1. User Preference Settings Fiori App (VIMI-24555)
The User Preference Settings Fiori App allows users to personalize their settings: to add substitutes,
enable the options "Show invoices with pending feedback" and "Receive email notification when invoice
is arrived".
This Fiori app can be enabled for all users maintained in COA (Chart of Authority Maintenance). On this
first version, it will display details of all the users, and modification to the settings can be restricted to
the logon user only.
2.2. Rejection reasons search help (VIMI-27872)

Rejection reasons are available in the Enter Cost Assignment Advanced, Approve Invoices, and
Approve Invoices (bulk mode) Fiori apps when rejecting the invoices. Rejection reasons are shown as
part of the invoice approval history with approval comments.
Rejection reasons can be maintained using the transaction code /OTX/PS37_REJREASON.
In this version, the rejection reasons are not language-specific and will be listed based on the
customized sequence.
2.3. "On Behalf" status in the Fiori apps header (VIMI-30444)

The enhanced perspective is introduced for the following VIM Fiori apps: Enter Cost Assignment
Advanced, Approve Invoices, and Approve Invoices (bulk mode). It allows a substitute user to view the
"On Behalf" status on the header section with the username.
Note: the Z-constant IAP/FIORI_BEHALF_ NAME needs to be enabled.
2.4. E-Invoice implementation for Poland (VIMI-29417)

This new feature is a standalone solution to process Poland E-Invoice. New transformation along with
required mappings have been provided in the baseline. VIM Inbound configuration is being delivered
in a BC set. Please refer to the Scenario Guide for more information.
2.5. New business rule for check of maximum exchange rate

difference (VIMI-29986)
A new business rule to check for maximum exchange rate difference has been introduced as the
process type 439. It follows the standard SAP check leading to the SAP message F5 212. See VIM
Reference Guide for more details.
2.6. New business rules for VAT ID/flexible tax check (VIMI-29824)
Flexible tax/VAT ID checks are now supported for the process types "Invalid Vendor VAT Number" and
"Invalid Recipient VAT Number". If the constant 005/FLEXIBLE_TAXID_CHECK is set to X, the checks
will ignore minor differences and typos. See VIM Reference Guide, the entry for the new constant, for
more details.
2.7. Normalization for IBAN, vendor and recipient tax ID fields

(VIMI-29972)
Normalization (removal of spaces) is implemented for IBAN and tax/VAT numbers. IBANs are
normalized in the indexing screen and in the background. Tax/VAT numbers are normalized in the
indexing screen and in the background depending on the characteristic specific configuration. See VIM
Invoice Configuration and Reference Guides for more information.
2.8. Determining vendor VAT ID/tax number (VIMI-30106)

In case the flexible tax number check is enabled with the Z-constant 005/FLEXIBLE_TAXID_CHECK
(VIMI-29824), a new logic module “/OPT/CL_D_LM_FCOPY_VEND_TAX_ID” can be used to copy the
partially matching vendor tax/VAT ID from the master data into VIM document. See VIM Invoice
Reference Guide for more information.
2.9. Supporting Advanced Tax Calculation (VIMI-29801)

OpenText VIM supports the advanced tax calculation feature based on different tax codes/tax
jurisdiction codes maintained at the line-item level. This is done to align VIM with MIRO/FB60 screens
for the tax calculation and to support additional features, for example, posting of mixed debit/credit lines
when the credit line tax amount is more than debit line i.e., a negative tax amount to be posted.
A new table control ‘Tax Split’ is introduced in the DP indexing screen as part of this feature. Availability
of the table control is based on the characteristic specific configuration at country level and index header
configuration at the DP document type level. For more details, please refer to the chapter “Advanced
Tax Calculation” in the Configuration, Scenario, User and Reference guides.
Transaction types supported:
1. Invoices
2. Credit Memo
3. Subsequent Credit Memo
4. Subsequent Debit Memo
BDCs supported:
Background Online
Non-PO scenarios BDC 2200, BDC 42 BDC 40, BDC 41
PO scenarios BDC 2200, BDC 6 BDC 1, BDC 200
Prerequisite: SAP Note 1802858 needs to be implemented for BDC 42 and BDC 2200 to allow
negative tax posting.
Limitations:
• This feature is not supported with BDC 34.
• Business rule ‘Validate accounting Data’ is not supported with advanced tax table control.
• Validate Coding functionality in the line items tab of the indexing screen currently does not
support advanced tax calculation.
2.10. Enabled line-item reference fields for Non-PO invoice posting

(VIMI-30233)
The line-item reference fields XREF1 and XREF2 are now passed to Non-PO invoice background
posting using BDC 2200 / BDC 42. Please refer to post install chapter of this section for more
information.
2.11. Embedded Analytics for IES Extraction (VIMI-30938)

For customers with an SAP S/4HANA backend system, OpenText introduces a set of ABAP Core Data
Services (CDS) views built on top of the analytics database.
In this version CDS Query and OData are provided for creating an IES Extraction analytics report.
CDS query /OPT/VAS4_DEAS_QUERY can be used not only by SAP S/4HANA tools like Query
Browser but also by other SAP reporting tools, which are designed for BW queries, like SAP Lumira
Designer or SAP Analysis Office.
OData query VAS4_DEAS_QUERY_CDS can be used by reporting tools that require OData as data
service.
These are for example tools delivered in SAP Business Analytic frameworks, which are delivered as
SAP S/4HANA content like Smart Business KPI and Smart Business APF.
2.12. Enhance Extraction Analytics in VIM Central Workplace for

Supplier Invoices Solution (VIMI-30937)
The IES Extraction Analytics is enhanced to provides all statistics related to the IES extraction
process not only based on the feedback after validation, but also based on invoice data when process
is ended.
For both kinds of feedback (Validation and Process End) the following statistics are provided:
· Generic key figures relevant for IES Extraction Analytics for Inbound.
· Invoice-specific key figures.
A Plug-In is available to compare extraction results with validation results including visual highlighting
of field value differences.
The function is provided as a new node 'IES Extraction Analytics' in VIM Central Workplace of
Supplier Invoices solution for Analytics.
For more information, refer to VIM Invoice Solution User and Reference Guides.
2.13. Support of incoming non-PO invoices sent as SOAP message

InvoiceERPRequest_In (VIMI-28669)
Support of non-PO invoices sent from Ariba Network via Cloud Integration Gateway as service
messages InvoiceERPRequest_In. See VIM Invoice Configuration Guide for more details. This
feature is delivered in the component OTVIMARC 0700_006 SP2 and is supported only on S/4 HANA
based systems.
2.14. Support of incoming invoices sent as SOAP message

InvoiceRequest_In (VIMI-29077)
Support of incoming invoices sent as SOAP message InvoiceRequest_In has been introduced. This
scenario is currently used for integration with Ariba Network and is also known from SAP public cloud
scope item 42K. See VIM Invoice Solution Configuration Guide for more details. This feature is
delivered as a special correction instruction along with the component OTVIMARC 0700_006 SP2
and is supported only on S/4 HANA based systems starting with S/4HANA 2020.
3 Delta information for VIM 7.5/7.6 customers
3.1. Corresponding Support Package levels
VIM 20.4 versions contain all bugfixes and features from corresponding VIM 7.6 support packages.
The following table lists the corresponding packages:
VIM 20.4 Version VIM 7.6 Version
VIM 20.4 VIM 7.6
VIM 20.4 SPS1 VIM 7.6 SPS1
4 Packaging and documentation
Downloads and documentation for OpenText™ Vendor Invoice Management for SAP® Solutions and
OpenText™ Business Center for SAP® Solutions are available on OpenText My Support
(https://support.opentext.com).
4.1. Packaging and delivery information

The software and documentation for OpenText™ Vendor Invoice Management for SAP® Solutions
includes:
4.1.1. Mandatory packages

For implementing the support package VIM classic mode 20.4 SPS3 including Fiori apps, the following
packages are mandatory:
Component Description Package file name
otbcsl30 _006.SAR _81610_

OTEXVIM_SP03_81610_106.SAR
VIM core package
106.sar
Contains VIM workflows,
transactions, reports,
OTEXVIM
tables, CDS views, BC
Inbound, Fiori solutions and
so on.
Business Center OTBCSL30_SP03_81610_106.SAR
VIM Solution Core:

OTBCSL30 development objects for
integration of VIM with VIM
Framework
otbcsl30_81610_106.sar
4.1.2. 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 20.4 SPS3. A complete list of all additional packages can be found in
VIM 20.4 SPS3 Installation Guide.
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_portal20_4_sps3.zip
Approval Portal based on
JCo3.1 Java1.8
The table below lists other delivered files, specifying the related deployment scenario.
Binary name Description Install on Deployment

scenario
Invoice Solutions_fiori_perspectives_- Fiori perspectives Back end Fiori/On-
layouts.zip layouts premise
Invoice Solutions_fiori_perspectives_- Fiori perspectives Back end Fiori/On-
customizing.zip customizing premise
Invoice Solutions_fiori_persp_- Fiori perspectives Back end Fiori/On-
customizing_semantic.zip customizing for premise
semantic navigation for
Vendor Invoice Report
app
invoice solutions-launchpad content.zip Pre-configured tiles and Front end Fiori/On-
target mapping for VIM premise
Fiori apps
SiteTransport_CF_20.4_SPS03_Invoice Site transport for Cloud Cloud Cloud
Solution.zip Foundry Foundry Foundry
otexvim81610_106_sp3_acp.sar ACP file to adjust Back end All scenarios
attributes of OTEXVIM
component package
Note: in this SP there is no new version of the file Invoice

Solutions_fiori_customizing_entries.zip. The file delivered in SP2 must be used.
The table below lists files with SP specific additional transports (see Post Installation Activities
section).
Binary name Description Install on Deployment

scenario
Invoice_IES_analytics_customizing.zip VIM Central Workplace Back end Inbound
customizing for IES scenario with
Extraction Analytics IES
4.2. Related documentation
For additional information about OpenText™ Vendor Invoice Management for SAP® Invoice Solutions
and for supplemental information about related products, refer to the following documents, which are
available on OpenText My Support: https://knowledge.opentext.com/knowledge/cs.dll/Open/77740777
Document title (Code number) Available languages
OpenText Vendor Invoice Management for SAP 20.4 SPS3 Installation Guide English
(VIM-IGD) *
OpenText Vendor Invoice Management for SAP Invoice Solutions 20.4 SPS3 English
Configuration Guide (VIM-CGD)
Configuration Guide for Foundation
OpenText Vendor Invoice Management for SAP 20.4 SPS3 Administration English
Guide (VIM-AGD) *
Reference Guide (VIM-RGD)
Scenario Guide (VIM-CCS)
OpenText Vendor Invoice Management for SAP 20.4 SPS3 Security Guide English
(VIM-GSM) *
OpenText Vendor Invoice Management for SAP Invoice Solutions 20.4 SPS3
User Guide (VIM-UGD) English **
* Those documents include the information on VIM Framework components, formerly known as Business Center
** Currently only English is provided. The other language translations will be provided on OpenText My Support
later.
5 Supported environments and compatibility
This section provides details about supported platforms, systems, and versions.
5.1. Supported systems

VIM 20.4 is an add-on to the following SAP versions:
• SAP S/4HANA 1610 (all FPS)

SAP S/4HANA Cloud, Extended editions (EX) are supported by VIM 20.4 on the releases that
correspond to the supported on-premise releases listed above (also see SAP Note 2962569).
VIM does not support SAP S/4HANA Cloud, essentials editions (ES).
For details, Support Package levels of SAP platforms, and for dependencies on VIM Foundation add-
ons, see the following tables and the release notes for VIM Foundation.
Minimal
Software
VIM Component Release Support
Component
Package Level
751/752/753/754/
SAP_BASIS 0000
755/756
OTEXVIM
101/102/103/104/
S4CORE 0000
105/106
75B/75C/75D/75E
SAP_ABA 0000
/75F/75G
OTBCSL30 1610_106
S4CORE 101/102/103/104/
OTBCSL30 0000
105/106
SAP_ABA 75B/75C/75D/75E
/75F/75G 0000
SAP_BASIS 751/752/753/754/
755/756 0000
OTBCSL00 0700_006 3)
Requires SAP Document Compliance. See the list of

OTBCSL38
additional SAP Notes below.
S4CORE 101 or higher 0000
SAP_ABA 75B or higher

0000
SAP_BASIS 751 or higher

0000
OTBCBAS 0700_006 1)
OTBCSL08
OTBCSL30 81610_106 1)
SAP Fiori App See full details in VIM 20.4.1

“Manage Installation Guide for prerequisites for
supplier VIM simple mode.
Invoices”
Please note that with 20.4 SPS 1
“Simple Mode” will be deprecated and
is not supported for productive
installations. Please use Classic
Mode.
OTVIMGW SAP_ABA 750

SAP_BASIS 750
SAP_GWFND 750
IM_APPROVAL_PORTAL20_4_SPS3_JCO3 SAP
_1_JAVA1_8 NetWeaver 7.5 0000
Portal
1) Check the support package compatibility matrix in chapter 7 about allowed support package
combinations.
5.2. 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.
5.3. OpenText product compatibility

Details regarding prerequisites and compatibility can be found in OpenText™ Vendor Invoice
Management for SAP® Solutions Version 20.4 SPS3 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.
5.4. SAP Netweaver Version compatibility matrix for OAP 20.4

(OpenText Approval Portal)
SAP Netweaver Version
7.3 7.4 7.5
OAP 20.4 JCo3 Java 1.6

OAP 20.4 SPS1 JCo3 Java 1.6
OAP 20.4 JCo3 or JCo3.1 Java 1.8
OAP 20.4 SPS1 JCo3 or JCo3.1 Java 1.8
OAP 20.4 SPS2 JCo3.1 Java 1.8
OAP 20.4 SPS3 JCo3.1 Java 1.8
5.5. Approval Portal Downward Compatibility Matrix

The following table lists the supported combinations of the OpenText Approval Portal (OAP) and the
VIM backend versions.
Compatibility VIM 20.4 VIM 20.4 SPS1 VIM 20.4 SPS2 VIM 20.4 SPS3
Matrix VIM 20.4
OAP 20.4
OAP 20.4 SPS1
OAP 20.4 SPS2
OAP 20.4 SPS3
5.6. 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 OAP 7.6 SPS1/ OAP 7.6 SPS2/ OAP 7.6 SPS3/
Version 20.4 OAP 20.4 SPS1 OAP 20.4 SPS2 OAP 20.4 SPS3
JCo3 + Java
1.6
JCo3 + Java
1.8
JCo3.1+ Java
1.6
JCo3.1+ Java
1.8
5.7. Web browser and mobile device support (Approval Portal)

The following table lists the supported combinations of web browsers and the OpenText Approval
Portal versions:
Supported Browsers and Versions
IE11 IE Edge FF Chrome Safari

(94.0.992.31: September
29, 2021)
OAP 20.4
OAP 20.4 SPS1
OAP 20.4 SPS2
OAP 20.4 SPS3
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.
The following table lists the supported combinations of the operating systems for mobile devices and
the OpenText Approval Portal versions:
OAP OAP 20.4 OAP 20.4 OAP 20.4

Mobile Devices Matrix
20.4 SPS1 SPS2 SPS3
iOS (9.0) to (14.0)
5.8. Web Viewer support

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

Viewer
support 20.3 21.1 21.4
matrix
Web Mobile Web Mobile Web Mobile
OAP 20.4
OAP 20.4
SPS1
OAP 20.4
SPS2
OAP 20.4
SPS3
5.9. Brava View support (OAP)
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 20.4
OAP 20.4
SPS1
OAP 20.4
SPS2
OAP 20.4
SPS3
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.
5.10. 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 RU * NL PT
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 UI UI UI UI UI UI UI UI
Invoice Management
UI = user interface only
B = both user interface and User Guide
F = Fiori UI
* = Supported with limitations (not all texts may have translations). Import the language
packages included into 20.4 SPS2 first for translations into Russian.
Note
➢ Language packages for VIM Invoice Classic 20.4 SPS3 will be
provided in OpenText My Support by the first week of May 2022.
➢ 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.
5.11. 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
Note
• VIM Workplace and VIM Analytics in SAP GUI for HTML are supported only on
SAP Fiori FES 5.0 (SAP Note 2618605)
• From 20.4 SPS2, “Enter Cost Assignment - Simple Coding” app will be in
maintenance mode and customers need to migrate to “Enter Cost
Assignment - Advanced Coding” app
5.12. 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:
BC UI 16.3.5 VIM UI 20.4 VIM UI 20.4 SPS1 VIM UI 20.4 SPS2 VIM UI 20.4 SPS3
OTBCWUI 0740_004 OTBCWUI OTBCWUI

SP5 OTBCWUI OTBCWUI 0740_006 SP2 0740_006 SP3
OTBCUS03 0740_004 0740_006 0740_006 SP1 OTBCWUI_NEO_07 OTBCWUI_NEO_07
SP4 OTBCWUI_NEO_07 OTBCWUI_NEO_07 40_006_SP02OTBC 40_006_SP03
PF07_BC_VIM_NEO_ 40_006 40_006_SP01 WUI_BTP_CF_0740 OTBCWUI_BTP_CF
UI_03 (16.3.5) _006_SP02 _0740_006_SP03
Invoice Solution
SAP UI5 1.71.*
7.6/20.4 SPS3 NA
NA NA NA SAP UI5 1.84.*
SAP UI5 1.96*
SAP UI5 1.71.*

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

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

VIM 7.5 SP11 / SAP UI5 1.71.* SAP UI5 1.71.* SAP UI5 1.71.* SAP UI5 1.84.*
SAP UI5 1.71.*
16.3.5 SAP UI5 1.84.* SAP UI5 1.84.* SAP UI5 1.96*
5.13. 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
Germany Xrechnung 1.0" /OPT/TRANS_XML_EDOC_CEFACT
/OPT/TRANS_XML_EDOC_CEFACT1
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

/OPT/TRANS_XML_EDOC_UBL
Singapore delivery networks documentation
New Zealand
Australia
Generic UBL format and Check
* /OPT/TRANS_XML_EDOC_UBL
delivery networks documentation
Version 1"
Mexico Factura Version 3” /OPT/TRANS_XML_FACTURA_MX
Version 4”
China OFD OFD format
Poland Faktura /OPT/TRANS_XML_FAKTURA_POL
See VIM Invoice Solution Scenario Guide for more information on electronic invoices.
6 Installation and upgrade notes
This section provides additional installation and upgrade information, including related or third-party
product information and any required critical patches.
6.1. ACP file for adjustment of prerequisites

The component OTBCS4, as part of VIM Foundation, is mandatory for the installation or upgrade of
the invoice solution. An ACP file is provided to adjust the attributes of the package OTEXVIM top
include OTBCS4.
The ACP file for the initial installation package can be downloaded from Open Text MySupport:
Patches > Vendor Invoice Management > Vendor Invoice Management 20.4 > Vendor Invoice
Management 20.4 > Invoice Solutions > ACP Files > otexvim81610_106_acp.sar
With 20.4 SP1 and later support packages, a new SP specific ACP file is provided in the same folder
at Open Text MySupport where the support package files are located.
If you purchased VIM through SAP and you are performing the upgrade with SAP Maintenance
Planner, the component OTBCS4 is included into the Foundation instance of Vendor Invoice
Management.
6.2. Installation notes

The installation of OpenText™ Vendor Invoice Management for SAP® Invoice Solutions is described in
OpenText Vendor Invoice Management 20.4 SPS3 Installation Guide.
Please note that the installation sequence of VIM invoice solution and VIM Foundation add-ons is
important unless you install everything in one step. Always install the latest Support Package for VIM
during the installation. More information about that is provided in the Installation Guide.
SAP Notes required or mandatory for VIM:
• 2353336 - Workflow: Runtime error CREATE_DATA_UNKNOWN_TYPE.

• 2347514 - Workflow: Transaction SWF_CNT_STR_GEN does not include all workflow
structures. (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.
• 2543181 - ArchiveLink file creation fails while using CMIS Repository.
• 2665611 – Saving text without change to information about last change
Consider specific requirements and instructions associated to the VIM gateway component for the
Supplier Self Service (lean). For details, see OpenText Vendor Invoice Management 20.4 Installation
Guide.
6.3. Upgrade notes

The upgrade of OpenText™ Vendor Invoice Management for SAP® Invoice Solutions is described in
OpenText Vendor Invoice Management 20.4 SPS3 Installation Guide.
6.3.1. ACP files for upgrades from VIM 7.5/7.6

NOTE: In case you have purchased VIM directly from Open Text, for upgrades from VIM 7.5/7.6, an
ACP file to modify the installation package attributes is required in case you were using any of the
following additional components:
OTBCSL03, OTBCSL33, OTVIMARB, OTVIMS4, OTVIMCDS
The ACP file can be downloaded from Open Text MySupport: Patches > Vendor Invoice Management
> Vendor Invoice Management 20.4 > SAP S/4HANA > Invoice Solutions 20.4 > ACP Files >
OTEXVIM81610_106_UPG_75.SAR
If you purchased VIM through SAP and you are performing the upgrade with SAP Maintenance
Planner, the package attributes will be adjusted automatically.
6.3.2. BC sets for upgrades

Several BC sets are provided for upgrades. A full BC set containing complete configuration is included
into the main VIM 20.4 installation package. Three delta BC sets are provided with VIM 20.4 SPS3 for
upgrades from VIM 16.3 SP3/SP4/SP5.
/OTEXVIM/VIM1633_204_UPGRADE: Delta BC Set for upgrades from VIM 16.3 SP3 to 20.4.
Note: the complete BC set /OTEXVIM/VIM20_4_BASELINE has been provided in the initial
installation package. Use this BC set for all other upgrade scenarios.
6.4. Fiori apps requiring report runs

The Fiori apps “Enter Cost Assignment – Simple”, “Enter Cost Assignment – Advanced”, and
“Approve Invoices” store draft data for invoices that have been changed in Fiori. If customizing
changes – as by installing updates – the existing draft data might cause a dump in the new version of
the Fiori app.
OpenText recommends that you run the following reports to get rid of old draft data:
- /OTX/PS32_DROP_ALL_DRAFTS
7 Support Packages
VIM 20.4 and Business Center 20.4 support packages (also called “updates”) are published through
OpenText My Support (https://support.opentext.com).
Backend Packages
The following table lists the supported release and support package level of each mandatory backend
component that is required for a specific VIM version and support package level.
VIM release VIM 20.4 VIM 20.4 VIM 20.4 VIM 20.4
name SPS1 SPS2 SPS3
OTBCBAS 0700_006 0700_006 0700_006 0700_006

0001 0002 0003
OTBCSL00 0700_006 0700_006 0700_006 0700_006

0001 0002 0003
OTBCSL30 81610_106 81610_106 81610_106 81610_106

0001 0002 0003
OTEXVIM 81610_106 81610_106 81610_106 81610_106

0001 0002 0003
Frontend Packages
It is possible to install a higher SP level of the frontend packages (OTBCWUI) and connect to
backends with lower SP levels. The following combinations are supported:
VIM release VIM 20.4 VIM 20.4 SPS1 VIM 20.4 SPS2 VIM 20.4 SPS3
name
OTBCWUI 0740_006 0740_006 0740_006 0740_006

0001 0002 0003
OpenText recommends that you check OpenText My Support (https://support.opentext.com) for new
product updates or documentation updates that may have been posted after this release.
8 Post Installation Activities

8.1. Activate BC Set /OTEXVIM/VIM20_4_UPGRADE_SP3
This BC set contains table content changes of the VIM baseline customizing including Fiori and BC
inbound. 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.
Step: Activate BC set: /OTEXVIM/VIM20_4_UPGRADE_SP3
Step: Activate BC set for Fiori Apps: /OTEXVIM/VIM20_4_BASELINE_B5
8.2. Installing transport with IES Analytics customizing

If IES Analytics is going to be used, import the customizing transport provided in the file
Invoice_IES_analytics_customizing.zip. The content provided in the transport must be imported into
every client because the transport contains client specific data.
8.3. Configuration delivered with BC set

8.3.1. Check for maximum exchange rate difference (VIMI-29986)
A new business rule to check for maximum exchange rate difference has been introduced as the
process type 439. It follows the standard SAP check leading to the SAP message F5 212.
Navigate to the following customizing node:
Maintain the new process types 439 as shown below. The fields that are not shown are empty.
Maintain user process options:
Add the new process type for document types PO_S4 and NPO_S4
Enter the new process type in process type determination sequence:
Maintain the determination steps as shown below, with the check function
/OPT/VIM_DETERMINE_PROC_439:
For the document type PO_S4, use step 18, then enter the same function module as shown above in
determination.
For both document types, maintain index screen options:
8.3.2. Checks for Flexible tax/VAT ID (VIMI-29824)

Flexible tax/VAT ID checks are now supported for the process types "Invalid Vendor VAT Number" and
"Invalid Recipient VAT Number".
The new constant 005/FLEXIBLE_TAXID_CHECK if set to X, the checks will ignore minor differences
and typos.
8.3.3. Normalization of tax IDs, copying of tax IDs (VIMI-29972,
VIMI-30106)
Create two new module definitions:
Module Text Class name
G_HEAD_024 Normalization of vendor /OPT/CL_D_LM_NORMALIZE_TAX_IDS

and company code tax
IDs
G_HEAD_025 Copy vendor tax ID after /OPT/CL_D_LM_FCOPY_VEND_TAX_ID

flexible check
Add both modules into the processing definition G_MAIN_001:
Add new steps as shown below and in addition, verify that for the step 130, the relation flag is also set
to AND:
8.3.4. E-Invoice implementation for Poland (VIMI-29417)

This section assumes that all baseline settings like channels and mappings are in place and lists the
additional, project specific steps based on VIM baseline.
Create new archiving document type “/OPT/FACTU” (t-code – OAC2)
Link BC(/OTX/PF01R), VIM(/OPT/V1001) and SAP BOR (BUS2081, BKPF) objects mentioned below
to the new archiving document type: (t-code – OAC3)
Assign the new XML archiving document type(/OPT/FACTU) to workflow (Object /OTX/PF01R,
template WS00297300).
Add a new OAWD upload node (/OPT/FACTU) (t-code OAWS).
Business Center Configuration:
Create new channel OAWD_FACTU as shown below.
Assign handler and other parameters to the new archiving document type.
Module Configuration
Assign modules to “PS03FACTU”.
XML Intermediate Mapping
T-code: /n/opt/xml_map
Add new transformation: /OPT/TRANS_XML_FAKTURA_POL
Root Node: Faktura
Mapping:
VIM Configuration
Channel configuration:
Add channel “OAWD_FACTU” as shown below.
Mapping ID:
Navigate to following customizing node:
Add Field Mapping as shown below:
Add Automated Field Enhancement mapping as shown below:
8.3.5. Payment split exit function for IES integration (VIMI-30922)

In the mapping GENERAL, enter the exit function /OPT/VIM_CONVERT_BOOL_TO_ABAP for the
field SPLITPAYMENT:
8.3.6. Reminder notification not sent for posted approval invoice

with no requester (VIMI-29524)
When an NPO DP is created without requester and the "Invalid Requester Error" is bypassed, then
the approval workflow does not start when clicked on One Step Approval. Due to this reminder are not
sent as there is no process type associated. Existing constant 005/APPROVAL_OPTION can be set
with value "2021" for this purpose.
8.3.7. Avoid locks set by DR BR Wait program (VIMI-29668)

The constant 005/ DR_BR_LOCK_MSG is delivered to avoid locks during PO invoice processing. The
/OPT/DR_BR_WAIT program sets locks for DP’s getting processed with default process types and the
DP’s do not get posted and BDC logs are updated with lock messages. Please add the message id
and message number to the constant to allow the DP for further processing. (If more than one
message is found in BDC log separate them with ':') Example value for Z-constant: M8-007:MK-534.
8.3.8. Determination of HSN/SAC code (VIMI-29523)
Create new module definition:
Module Text Class name
G_CNTRY_04 Country Specifics (India /OPT/CL_D_LM_DETERM_CONT_HSN

GST) - Determine HSN
Code
For PO invoice add the module to the process definition “P_SPEC_002”.
Add the following processing step and save.
For Non-PO invoice add the module to the process definition “N_SPEC_003”.
Add the following processing step and save.
8.3.9. Advance tax calculation feature (VIMI-29801)
A new table control ‘Tax Split’ is introduced in the tax tab of the DP indexing screen in this release.
Availability of the table control is based on the characteristic specific configuration at country level and
index header configuration at the DP document type level. For more details on configuration, please
refer to ‘Chapter 33 - Advanced Tax Calculation’ in the configuration guide and reference guide.
8.3.10. Enabled line-item reference fields for Non-PO invoice

posting (VIMI-30233)
The line-item reference fields XREF1 and XREF2 are now passed to Non-PO invoice background
posting using BDC 2200 / BDC 42. The logic is available in the BTE
“/OPT/BTE_PROCESS_00001120” function.
Enable the BTE as per the below instructions:
Go to t-code “FIBF”.
Navigate to Settings->Process Modules->Partner
Make entry as below
8.3.11. Auto population of bank data based on QR-IBAN

(VIMI-30876)
The constant 005/ SKIP_QR_IBAN_AUTO is delivered for use in function
“/OPT/VIM_ICC_DET_PARTBANKTYPE”. Enabling this will avoid the automatic population of bank
data from vendor master in case if the bank data have QR-IBAN.
8.4. Optional Post Installation Activities
8.4.1. Warning message when switching between tabs in the
indexing screen (VIMI-25706)
In the indexing screen warning message “Posting period XXXXX is not open” appears every time user
moves from one tab to other. New z-constant 005/MESS_ONE_TIME_ONLY has been introduced for
the message to appear only once.
Maintain the constant value as ‘X’ if the message has to appear only once.
8.5. Review Known Issues

Review the section “Known Issues” and verify whether you need to perform additional
adjustments of VIM configuration.
9 Known issues
9.1. VIM Classic Mode
Issue number Issue description
VIMI-31351 Bulk Approve option is not working for the Fiori Approval app on mobile.
VIMI-31373 Posting a subsequent credit/debit or a credit memo for a PO invoice with

sequential or proportional distribution with multi account assignment is failing.
VIMI-31127 During background posting of partial PO invoice with multi account assignment
type “Distribution by Percentage - Partial Inv. Distribution in Sequence”, the line-
item amount distribution is incorrect.
VIMI-31199 When using "Bulk Refer" option in VIM Workplace the process options shown
for referee are incorrect.
VIMI-31473 VIM Central Workplace (/OTX/PF03_WP) does not display any work items in the
Supplier Invoices node, although it shows the count of available work items.
The problem can be solved by maintaining the standard handler

/OTX/PF03_CL_DATA_HANDLER_DYN in the configuration of work object
PS03_MON_VIM and PS03_PRC_VIM. Customizing path /OTX/PF00_IMG >
Workplace Configuration > Work Object Types.
10 Fixed issues
10.1. Fixed issues for 20.4 SPS3
10.1.1. Document Processing (DP)
VIMI-25236
The buttons ‘Display Vendor’ and ‘Display Bank’ in the indexing screen do not work correctly for
business partners in SAP S/4 Hana system.
VIMI-25706
In the indexing screen warning message “Posting period xxxxx is not open” appears every time user
moves from one tab to other.
VIMI-28358
Data on SCE image is not highlighted when user logs in SAP in language other than English.
VIMI-28695
During background posting of PO invoice using BDC 2200 the “Budget _Period” field value is not
passed to BAPI.
VIMI-28953
The exception “Vendor address mismatch” is incorrectly triggered if business partner has more than
one billing address.
VIMI-29000
Pop-up for comments during refer is missing when a DP document already has an existing comment
at header level.
VIMI-29092
Correct tax code is not determined if the header tax rate is zero.
VIMI-29103
For Indian invoice, tax calculation is incorrect if multiple tax rates are maintained against different
HSN/SAC code.
VIMI-29206
Calculation of tax is incorrect for an invoice with unplanned delivery cost with SAP Note 1402621
implemented in the system.
VIMI-29226
For few exceptions the exception icon and description are not shown when navigating to the line
items tab of indexing screen.
VIMI-29245
Logic Module set up as "Activate by Determination" is not working.
VIMI-29246
Subsequent credit / debit memo after posting is changed to credit memo or invoice.
VIMI-29309
While processing the delivery cost of multiple POs in one DP document, the tax calculations is done
for only one PO and not for all.
VIMI-29313
While posting via BDC 2200, the tax reporting country (field EGMLD) is not transferred to posting
BAPI.
VIMI-29354
In the indexing screen drill down navigation to PO line items is possible only for the first PO line item
and not for the selected line item.
VIMI-29361
When posting a PO invoice with return items, the following error is returned: "M8 476 Reverse qty
greater than qty credited so far".
VIMI-29376
When duplicate payment terms are maintained, different payment terms are proposed in VIM as
compared to FB60.
VIMI-29403
For Indian Non-PO invoice withholding tax amount is not recalculated when withholding tax code is
changed in the indexing screen.
VIMI-29432
When changing the withholding tax code, the withholding tax base amount value is cleared if the
withholding tax type is modified net amount or modified tax amount.
VIMI-29435
The functional area is not automatically determined from the cost center and the field remains blank in
the line item of the indexing screen.
VIMI-29445
When using “Change Document Type” process option the drop down list includes current document
type.
VIMI-29475
When processing a PO invoice with a foreign currency the exchange rate is calculated based on
posting date even though the characteristic specific setting for the country is set to “Date on Vendor
invoice “.
VIMI-29485
Performance issues in the Non-PO invoice auto coding function
/OPT/VIM_DETERMINE_PROC_LIB003.
VIMI-29487
After a PO invoice is declared as non-duplicate and posted in background with BDC 6, a workflow
error occurs and an incorrect MM document number is updated in the DP document.
VIMI-29493
XML file processing error occurs while using e-Link invoice interface.
VIMI-29494
Editing of a PO is possible even though the related PO invoice is in the process of background
posting using BDC 2200.
VIMI-29497
Withholding tax is not calculated correctly when tax code is manually added in the DP indexing screen
for PO invoices of Indian company code.
VIMI-29500
Business rule “ISR number mismatch” is not triggered when the vendor master does not contain ISR
number and ESR_CHECK_REQUIRED constant is not set.
VIMI-29505
The freight vendor payment terms are not updated correctly in the DP indexing screen when the
invoice vendor is different from PO vendor.
VIMI-29509
The amount and date fields in the header are not learned when using SCE in the indexing screen.
VIMI-29514
When posting a down payment invoice using BDC 51, partner bank type and permitted payee details
are not transferred to SAP.
VIMI-29515
When posting service PO invoice using BDC 2200, where the service entry sheet is copied from
another and service line item is deleted in the invoice, the BDC error "Error in Account coding
allocation" occurs.
VIMI-29523
When the HSN code is cleared in the DP indexing screen, clicking the ‘Apply Rules’ process option
re-populates the HSN code value.
VIMI-29527
During background posting of a PO invoice using BDC 2200 there is a balance error due to incorrect
rounding of tax amounts.
VIMI-29548
When clicking on ‘Apply Rules’ process option the manually entered tax code is replaced with PO tax
code for the additional cost G/L line item in indexing screen.
VIMI-29627
During automated matching of line items against PO there is a performance issue in an inbound
scenario when DP document number is not yet assigned.
VIMI-29675
For PO invoice posted in background the tax rate and description are missing for few line items.
VIMI-29774
The exception “Validate Bank Details (NPO)” is incorrectly triggered when the bank information is
matching with that of alternative payee of vendor.
VIMI-29776
When invoice is reversed and a new DP document is created for the same PO, the quantity derived is
incorrect.
VIMI-29777
During online posting of the PO invoice the final invoice indicator value from the line item is not
transferred to MIRO.
VIMI-29800
During background posting of Non-PO invoice with non-decimal currencies, BDC error “Inconsistency
between debit/credit indicator and amounts” occurs.
VIMI-29807
During background posting of a PO invoice where main vendor and IP vendor are different, partner
bank type is not updated with IP vendor's partner bank type.
VIMI-29817
When uploading coding data in the indexing screen, material number is not converted to internal
format.
VIMI-29884
During background posting of the Non-PO invoice using external tax system with line items having
both debit and credit lines, the BDC error ‘Error - Tax entered incorrect’ occurs.
VIMI-29898
When the GST tax calculation depends on HSN/SAC codes, tax amounts are distributed incorrectly in
the G/L lines.
VIMI-29908
Cannot post service PO invoice with maintenance order in service sheet using BDC 2200.
VIMI-29920
The “Upload Coding” function in the indexing screen does not work when the SCE tab is active in the
detail pane.
VIMI-29922
During background posting of a lean service PO invoice BDC error ‘"Service number entered
(0000000010) does not exist" occurs.
VIMI-29925; VIMI-29516
For an invoice with 3 decimal currency SCE does not return correct value to the DP indexing screen.
VIMI-29967
There is an error in the DP indexing screen when processing WBS element having sublevel activity in
the line item.
VIMI-30026
For language ‘ES’, clicking “Simulate Rules” does not show the message icons for exceptions.
VIMI-30051
For a PO invoice with mix of debit and credit lines in the G/L tab, balance is incorrectly calculated.
VIMI-30096
The exception “Validate Bank details (NPO)” is triggered incorrectly when bank account number has
18 characters.
VIMI-30105
Performance issue when switching between the tabs in the details pane of the DP indexing screen.
VIMI-30129
During background posting of PO invoice using BDC 6 with account assignment category ‘U’, BDC
error ‘Error in routine MRM_DRSEG_FILL(SAPLMRMH)’ occurs.
VIMI-30222
In DP indexing screen when a new PO number is entered, the value for vendor VAT number field is
not redetermined.
VIMI-30228
For Swiss invoices with normal IBAN scenario and without any ISR or ESR/QR reference, partner bank
type is not updated in the posted document.
VIMI-30242
Same number range for FI and MM invoice number causes incorrect entry in /OPT/VIM_1CLEAR
table causing inconsistency in payment runs.
VIMI-30286
When using “Replace invoice lines” option in the proposal tab of the indexing screen there is an error
“CX_SY_ARITHMETIC_OVERFLOW” when there is a huge number of lines in the PO invoice.
VIMI-30313; VIMI-30130
Posting of a PO invoice in background using BDC 6 does not distribute amounts correctly when the
PO has multi account assignment and distribution in sequence.
VIMI-30324
During background posting of a Non-PO invoice where tax code has zero tax rate, BDC error “Tax
statement Item missing for tax code XX” occurs.
VIMI-30355
If decimals are entered for a non-decimal currency during online posting of Non-PO invoice, error
“Decimal Places are not Permitted” occurs.
VIMI-30383
Changes done to the DP data are not saved when confirming “Not duplicate”.
VIMI-30445
The validation for the “Internal Order” field in the line-item tab is not working correctly.
VIMI-30458
Tooltips for balance fields are not shown in the indexing and approval screens.
VIMI-30459
The exception “PO Not Released or Incomplete” is triggered for active PO having no release strategy.
VIMI-30505
The exception “Tolerance exceeded (PO)” does not display currency or percentage in the message.
VIMI-30539
For Non-PO invoice there is error “Condition type XXXX does not exist tax code XX does not exist”
during coding validation.
VIMI-30574
When using ‘Upload Coding’ function sales document number is not converted to internal format.
VIMI-30575
During background posting of a Non-PO invoice using BDC 34, bank details are cleared when one
time vendor has no IBAN data.
VIMI-30582
When using “Move to G/L” option on the line items tab, PO related fields are also transferred to G/L
lines.
VIMI-30714
The info icon in the indexing screen in all the tabs is not read correctly.
VIMI-30728
When clicking on simulate rules in the indexing screen, there is runtime error if the PO invoice
contains billing plan.
VIMI-30739
The proposal for Transport Management invoices does not work when the business partner and
supplier are different.
VIMI-30762
In the DP indexing screen negative values from SCE cannot be transferred to the invoice.
VIMI-30942
The custom function for determining the baseline date is not working as expected.
VIMI-31042
For a PO invoice when the line-item tax code is changed in the DP Indexing screen and clicking on
‘Apply Rules’ process option, the tax code is replaced by the tax code from PO line items.
VIMI-30876
For Swiss invoice when there is only one partner bank type in vendor master with QR-IBAN, posting
of invoice is failing as bank data is auto populated in the indexing screen.
10.1.2. Invoice Approvals
VIMI-28589
For a Non-PO posted approval invoice, real-estate cost elements are not displayed in the approval
screen.
VIMI-29276
Search help for few fields is not shown in the COA details tab.
VIMI-29367
In COA maintenance transaction (/OPT/AR_COA), the filter settings are not saved when
changing/exiting the screen or even resizing the window.
VIMI-29394
While copying existing AFS ID, the error message appears: ‘Entry 91 does not exist in /OPT/AT_AFS
(check entry)’. In addition, coding fields are not copied to new AFS ID.
VIMI-29397
When triggering Non-PO posted approval of an invoice that has non-decimal currency with tax amount
up to 12 digits, a runtime error happens.
VIMI-29491
Not possible to delete line items in the approval screen when using Simple COA for approvals.
VIMI-29689
Actual agent is empty in the approval history log when users maintained in COA have different OT user
ID and SAP user ID.
VIMI-29821
When forwarding or rejecting a work item, changes made in the approval screen are automatically
saved by default resulting in validation errors.
VIMI-30125
When using COA maintenance transaction (/OPT/AR_COA) to create new user, using the “Copy” option
issues the error ‘"Invalid User Map ID xxxx".
VIMI-30382
For posted approval invoice using inter-company tax procedure, the tax amounts for both credit and
debit line items are summed leading to incorrect net amount and balance.
VIMI-30424
For a posted approval the document status is incorrect when changes to the invoice are made outside
VIM.
VIMI-30449
COA entries are overwritten when two users are working at the same time in COA maintenance
transaction (/OPT/AR_COA).
VIMI-30727
Data is not saved when using custom buttons in the approval screen to perform some actions.
VIMI-31004
In the approval history log the user's name is truncated when it is longer than 12 characters.
10.1.3. VIM Notifications

VIMI-28731
HTML text in email notification does not get translated properly after the Z-constant “HTM1” is enabled.
VIMI-29490
The reminder report considers due date as the cash discount date for cases where invoice is blocked
or in posted approval.
VIMI-29524
The reminder report does not send notification for posted approvals.
10.1.4. VIM Analytics (new VAN) Report and VAN Liability Report
VIMI-27016
VIM Analytics shows incorrect FI document for invoices created with split invoice functionality.
VIMI-28836
When central finance is activated, all blocked Non-PO invoices are shown as posted in VIM analytics
report.
VIMI-29411
In VIM Analytics the payment block is not shown correctly when updated from FB02.
VIMI-29498
In VIM Analytics for a cancelled invoice when navigating to view the document in SAP, the error
“Document does not exist” occurs.
VIMI-29899
The tax reporting date shows incorrect value when Non-PO invoice is posted outside VIM.
VIMI-30027
After migration to VIM 20.4 few DP documents show ‘*’ in the agent column in VIM Analytics though
there is only one agent for that work item.
VIMI-30098
The IRN field shows incorrect value ‘#’ after a Non-PO invoice is posted.
VIMI-30227
It is not possible to execute VIM Analytics for multiple currencies and a value in gross amount.
VIMI-30617
When executing VIM Analytics for DP document whose invoice image size is zero there is a runtime
error.
VIMI-30742
GOS icon is displayed incorrectly in VIM Analytics when clicking the image button.
10.1.5. Central Reporting and Other Reports
VIMI-28139
When using “Cancel and Re-Enter" process option in the blocked dashboard changes made to the
original DP document outside VIM are lost.
VIMI-29341
The vendor staging tabledownload report stops a runtime error when executed for large company code
range.
VIMI-29483
DR BR Wait job stops execution when an error occurs while processing a document and does not
process further documents.
VIMI-29512
There is a run time error when training smart coding data for huge number of suppliers.
VIMI-29636
The PO staging table download program terminates with a time error ‘COMPUTE_BCD_OVERFLOW’
due to large non-decimal values.
VIMI-29668
The DR BR Wait job resubmits every DP document for every run of the program without actually
checking if the exception is resolved or not and also, the same process type is repeated in the history
log.
VIMI-29791
For certain DP documents in the Central Audit report, the SAP document type shows empty value.
VIMI-29806
Smart coding training program output log does not differentiate the existing model statistical data and
current program trained data.
VIMI-30006
When training smart coding basic model for non-unique key field there is a runtime error
‘ITAB_DUPLICATE_KEY’.
VIMI-30200
Training coding statistics report (/OTX/PS302_TRAIN_CODING) ignores company code selection.
VIMI-30250
The Invoice Life Cycle report does not display the “Number of Touches” for a DP document.
VIMI-30290
The rerun rules program “/OPT/CR_RERUN_RULES_JOB” increases the retry counter for every job
run even if the lapsed time is not met.
VIMI-30362
When basic model data is fetched during smart coding for huge volume, the runtime error
“SAPSQL_STMNT_TOO_LARGE” occurs.
VIMI-30562
The PO staging table report does not consider data of freight vendors.
VIMI-30699
Missing translations texts for transaction code /OPT/INV_CANCL_RECRT.
10.1.6. VIM Workplace

VIMI-29453
In VIM workplace “Maintain Groups” transaction (/OPT/VIM_WP_TMG) the agent ID field value
accommodates only 10 chars.
VIMI-29480
The content pane in the VIM workplace keeps reducing when working with external monitor.
VIMI-29633
There is a run time error “OBJECTS_OBJREF_NOT_ASSIGNED” in VIM Workplace when using
custom selection screens.
VIMI-30248
Although the payment terms are manually removed from a DP document, the “Discount Light” and
“Discount due date1” fields are still displayed in VIM WP header line.
VIMI-30734
Performance issue in workplace when data is empty in few text tables.
VIMI-30820
When a posted approval invoice is recalled from VIM Workplace, the document status is set to "Rejected
by Approver" instead of “Approval recalled”.
VIMI-30977
Performance issues in loading VIM Workplace after installing VIM 20.4 SPS2.
10.1.7. Web Approval Portal
VIMI-25470
In bulk mode the values for fields “ACTION_DATE” and “ACTION_TIME” are not displayed in the invoice
details pane.
VIMI-29529
Cannot export coding data for Slovak language.
VIMI-29681
When entering numeric value in the decimal place for currency field with more than 2 decimals, there
is error “Please enter correct format”.
VIMI-29795
There is a performance issue when loading history data in the Web Approval Portal.
VIMI-30232
During invoice approval the "#" character is replaced with special characters (CR/LF) in the line-item
text field.
10.1.8. Fiori Approve Invoices app
VIMI-29549
Issue in selection of approval items in central/satellite system setup.
VIMI-31137
Duplicate line items are being displayed for indirect PO invoices (RMRP) in Approval and Bulk Approval
Fiori Apps.
10.1.9. My Approved Invoices app
VIMI-28679
During the final approval step of an invoice in Fiori release of invoice lock fails resulting in short dump.
VIMI-29622
When viewing a PO invoice with G/L lines, text descriptions for cost elements in the line items are
missing.
VIMI-30577
My Approved Invoices App doesn’t show DP_DOCTYPE values for parked documents.
10.1.10. Fiori Enter Cost Assignment Advanced app

VIMI-30447
Output tax values are missing in tax code input helps.
VIMI-30599
Not possible to forward a DP invoice with empty line items.
10.1.11. Supplier Self Service app
VIMI-30252
Incorrect date and amount format in 3S Supplier Self Service Fiori app details page.
10.1.12. Input Channels

VIMI-28692
During auto posting of an invoice that was went through BCC recognition, the baseline date and due
dates are incorrect when payment terms maintained in vendor master and PO are different.
VIMI-29492
Performance issue in logic module processing when inbound document has large number of line items.
VIMI-29460
Parsing of UN/CEFACT XML fails when element prefix "n0" or "n2" is used.
VIMI-29623
IES extraction reads IBAN value as amount and throws runtime error and in addition fails to start DP
workflow.
VIMI-29678
When using a multi backend setup with different releases in central and satellite systems, runs of IDF
trigger program abort with a runtime error “CALL_FUNCTION_REMOTE_ERROR”, preventing VIM
workflow start and also preventing other documents from being processed in the inbound.
VIMI-29771
Zero tax rates are lost in inbound processing.
VIMI-29805
When processing Fatura invoice for Italy the invoice vendor is not determined if different from PO
vendor.
VIMI-29815
During parsing and transformation of CEFACT invoice, certain end nodes are not included in the
transformation result, resulting in incorrect mapping of data of XML invoice.
VIMI-29980
The total tax amount provided in the IDOC is replaced with the posted value in VIM.
VIMI-30023
There is a short dump ‘DBSQL_DUPLICATE_KEY_ERROR’ when triggering DP workflow in the
inbound processing.
VIMI-30025
During inbound processing of a PO invoice, the line items tax code is not copied from header.
VIMI-30230
Error in triggering DP workflow for a document processed with incorrect HSN/SAC code.
VIMI-30384
Billing reference related nodes are not determined correctly while transforming invoices with
XRechnung format.
VIMI-30403
During inbound processing credit memo is not identified and the transaction type field in VIM is updated
to invoice instead of credit memo.
VIMI-30462
During IES inbound processing for US invoices both the total tax amount and VAT amount fields are
populated resulting in balance error.
VIMI-30464
Runtime error 'ASSERTION_FAILED' during inbound process of Non-PO invoices due to wrong field
name 'MAN_AMT_TCT_LONG'.
VIMI-30593
Error in DP workflow creation if tax rate field in document line items has some unexpected characters.
VIMI-30707
During DP workflow creation process type information is not transferred from central to satellite system.
VIMI-30797
Performance issues in BC inbound trigger job while fetching data from /OPT/VIM_1HEAD table due to
query based on a non-key field.
10.1.13. Others
VIMI-30751
After the installation or upgrade to VIM Invoice Solution 20.4, the client 000 contains test data in VIM
transactional tables and in VIM document type configuration table.
11 Documentation extensions
11.1. Installation Guide
11.1.1. Section 13.1 – Selecting components for installation or upgrade
Change 1:
In step 2 of the procedure To select components and download packages, the following transport
is listed in the table of transports: invoice solutions_fiori_perspectives_customizing.zip
(SPS3)
The corresponding Transport name must be changed to: T8FK900051[a]
Change 2:
In the same table of transports, in the Deployment scenario column, all entries of "On-premise" must
be replaced with "All scenarios".
11.1.2. Section 23.1.2.1 – OTVIMARC prerequisites

In Table 23-1: Ariba Cloud Integration Gateway, column VIM release, the value 7.5 must be
changed to 7.5 SP6.
11.2. Configuration Guide

11.2.1. Section 25.3 – Integrating Ariba Network using Cloud Integration
Gateway
The phrase “Attachments are supported. Comments are currently not supported.” must be
replaced with:
“Attachments are supported. Comments are currently supported only for the standard
invoice scenario (IDoc based).”
11.2.2. Section 25.3.1 – Configuring inbound processing

(InvoiceDetailRequest)
At the end of the section, the following 2 paragraphs must be added:
Support of supplier comments – Supplier comments are supported starting with VIM 7.6 SPS4 and
20.4 SPS4. Note that the OTVIMARC component support package can also be installed with older
VIM releases, 7.5 and 16.3. The minimum service pack level for VIM 7.5 is SP6. Comments support is
enabled similarly to the support of attachments as described above. Add a new inbound handler step
with the step handler class /OPT/CL_VIM_ARB_CIG_GETCOMMENT and place it before the last
processing step. Define a new end status for the new step as needed. Supplier comments will be
shown in the DP document process history.
Support of sending of comments to supplier – Comments that are entered when obsoleting a DP
document can be sent to the supplier. To activate this feature, navigate to Document Processing >
Process Configuration > Maintain Obsolete Reasons and enable Comments visible externally in
the configuration of obsolete reasons. Once enabled, users of the DP indexing screen must confirm
that comments may be visible to suppliers when setting a document to obsolete status and selecting
an obsolete reason with the respective flag enabled.
11.3. Security Guide

11.3.1. Section 7.1 – Specific authorization checks
The following Important note must be added at the end of the section:
VIM invoice solution performs invoice data processing in the background with tasks run by the
technical workflow user WF-BATCH or SAP_WFRT. If the technical user does not have administrator
permissions (the role SAP_ALL), all authorizations for invoice processing must be assigned to
SAP_ALL and such configuration must be thoroughly tested.
Building such authorization profile can be complex and is specific to a project, you can use
authorization check trace to determine the required authorizations.
12 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

VIM 20.4 SPS3 - Release Notes For Invoice Solution

Uploaded by

Copyright:

Available Formats

You might also like

VIM 20.4 SPS3 - Release Notes For Invoice Solution

Uploaded by

Document Information

Original Description:

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 20.4 SPS3 - Release Notes For Invoice Solution

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

Product Released: 2022-04-29

Release Notes Revised: 2023-03-29

1.1. Release Naming Information

1.2. Release Notes revision history

2022-04-29 Initial release

2022-05-24 New features Minor changes in the descriptions

5.12 SAP UI5 Version

2022-10-18 Support of S/4HANA 2022 added

OpenText Vendor Invoice Management by SAP Solutions 20.4

Future SAP S/4HANA versions will typically be supported by the VIM

For a complete list of SAP products supported by different versions of

2.2. Rejection reasons search help (VIMI-27872)

Rejection reasons can be maintained using the transaction code /OTX/PS37_REJREASON.

2.3. "On Behalf" status in the Fiori apps header (VIMI-30444)

Note: the Z-constant IAP/FIORI_BEHALF_ NAME needs to be enabled.

2.4. E-Invoice implementation for Poland (VIMI-29417)

2.5. New business rule for check of maximum exchange rate

2.7. Normalization for IBAN, vendor and recipient tax ID fields

2.8. Determining vendor VAT ID/tax number (VIMI-30106)

2.9. Supporting Advanced Tax Calculation (VIMI-29801)

Transaction types supported:

PO scenarios BDC 2200, BDC 6 BDC 1, BDC 200

2.10. Enabled line-item reference fields for Non-PO invoice posting

2.11. Embedded Analytics for IES Extraction (VIMI-30938)

2.12. Enhance Extraction Analytics in VIM Central Workplace for

2.13. Support of incoming non-PO invoices sent as SOAP message

2.14. Support of incoming invoices sent as SOAP message

VIM 20.4 Version VIM 7.6 Version

VIM 20.4 VIM 7.6

VIM 20.4 SPS1 VIM 7.6 SPS1

VIM 20.4 SPS2 VIM 7.6 SPS2

VIM 20.4 SPS3 VIM 7.6 SPS3

4.1. Packaging and delivery information

4.1.1. Mandatory packages

Component Description Package file name

otbcsl30 _006.SAR _81610_

Business Center OTBCSL30_SP03_81610_106.SAR

VIM Solution Core:

4.1.2. Packages and Transports for Additional Scenarios

Binary name Description Install on Deployment

Note: in this SP there is no new version of the file Invoice

Binary name Description Install on Deployment

Document title (Code number) Available languages

5.1. Supported systems

• SAP S/4HANA 1610 (all FPS)

Requires SAP Document Compliance. See the list of

S4CORE 101 or higher 0000

SAP_ABA 75B or higher

SAP_BASIS 751 or higher

SAP Fiori App See full details in VIM 20.4.1

OTVIMGW SAP_ABA 750

5.2. Supported ArchiveLink Content Repositories

VIM is specifically tested and validated for

• OpenText Archiving and Document Access for SAP Solutions

• OpenText Documentum Archive Services for SAP Solutions

5.3. OpenText product compatibility