Vendor Invoice Management SAP

OpenText™ Vendor Invoice
Management for SAP® Solutions

Release Notes
Version 16.3.2
Product Released: 2018-11-05
Release Notes Revised: 2019-01-24

Contents
1 Introduction .................................................................................................................................... 8
1.1 Release Notes revision history .................................................................................................. 8
2 About OpenText™ Vendor Invoice Management for SAP® Solutions ..................................... 9

2.1 “Classic Mode” versus “Simple Mode” .................................................................................... 11
2.2 General Data Protection Regulation (GDPR) .......................................................................... 13
3 Features ........................................................................................................................................ 14
3.1 New Features in VIM 16.3 ....................................................................................................... 14
MIRO as invoice transaction for all invoices (“unified posting approach”) ................. 14
Processing of parked and held documents ................................................................ 14
Simplified baseline ...................................................................................................... 14
Simple Mode ............................................................................................................... 14
OCR interface for Cloud OCR interface ..................................................................... 14
Central Reporting ....................................................................................................... 15
Multi-backend communication across different versions ............................................ 15
VIM Fiori apps ............................................................................................................ 15
Fiori WebUI framework enhancements ...................................................................... 16
Supplier Self Service (lean variant) ............................................................................ 16
Additional features compared to VIM 7.5 ................................................................... 16
3.2 New Features in VIM 16.3.1 .................................................................................................... 17
New VIM Supplier Self Service Fiori app (VIMI-18628) ............................................. 17
New VIM My Approved Invoices Fiori app (VIMI-20329) ........................................... 17
Attachment Upload for VIM Approve Invoices Fiori app (VIMI-20281) ...................... 17
Attachment Upload for VIM Enter Cost Assignment Fiori app (VIMI-20282) ............. 17
Disabling withholding tax warning message “Withholding tax calculation has
changed” (VIMI-19142) ....................................................................................... 17
Fiori Confirm Quantity and Price app: background posting after PO price
change (VIMI-19386) .......................................................................................... 18
Spanish localization: SII Support (VIMI-18756).......................................................... 18
Implementing custom field validation in the DP indexing screen (VIMI-19347) ......... 19
Adding the Forward action from VIM Workplace (WP) in the VIM logs (VIMI-
19368) ................................................................................................................. 20
OpenText™ Vendor Invoice Management for SAP® Solutions Version 16.3.2 Release Notes
2
New customizing for mandatory comment when declining an invoice in Fiori
Enter Cost Assignment app (VIMI-19538) .......................................................... 20
New business rule: SCB Indicator / Supplying Country Missing (VIMI-19721) .......... 20
Restricting ALV layout for process logs (VIMI-18719) ................................................ 21
Changing logical system on VIM tables (VIMI-18607) ............................................... 21
Support for branch code – Thailand specific (VIMI-19339) ........................................ 22
Additional accounting data section in coding templates when exporting
coding in Approval Portal (VIMI-16466) .............................................................. 22
Initial sorting in the Approval Portal inbox (VIMI-18087) ............................................ 22
Default option to show invoice image in Web Approval Portal (VIMI-18832) ............. 22
Configuration of timeout for Approval Portal web requests (VIMI-18925) .................. 22
Refreshing the Approval Portal inbox after using a custom button (VIMI-
19060) ................................................................................................................. 22
Improvements in the invoice inquiry status display in the Approval Portal
(VIMI-19516) ....................................................................................................... 23
Search Help support in additional accounting data area in Approval Portal
(VIMI-19711) ....................................................................................................... 23
Search Help support for custom header fields in Approval Portal (VIMI-19732) ........ 23
Tax code description display in the DP indexing and Approval screens (VIMI-
19367) ................................................................................................................. 23
Support of GST Registration Number for receiving location (VIMI-19408) ................ 23
Support of HSN Code in PO Line Items Proposal (VIMI-19408)................................ 23
User exit to determine default proposal for next approver if not unique (VIMI-
19033) ................................................................................................................. 23
Cross release multiple backend support (VIMI-19650) .............................................. 23
Reduction invoice support (VIMI-19274) .................................................................... 24
iOS 11 support for Mobile Approvals (VIMI-20210) .................................................... 24
Support of GST Import Procurement (VIMI-19432).................................................... 24
Full user name in comments (VIMI-17866) ................................................................ 24
Usermap and COA Cleanup (VIMI-20317) ................................................................. 25
3.3 New Features in VIM 16.3.2 .................................................................................................... 27
BW4HANA Add-On ..................................................................................................... 27
VIM Fiori Apps Cleanup Program (VIMI-17860) ......................................................... 27
Support of Ariba Cloud Integration (VIMI-21327) ....................................................... 27
Integration with Information Extraction Service (VIMI-21687) .................................... 28
Calculation of Unplanned Delivery Costs – New User Exit (VIMI-19434) .................. 28
Warning message in COA maintenance when email address already used
(VIMI-19590) ....................................................................................................... 28
3
Support of workflow substitution profile when maintaining substitutions for
approvals (VIMI-20808) ...................................................................................... 29
Warning on header level action in blocked invoice dashboard (VIMI-21259) ............ 29
Last user in the process history of the blocked invoice header level
dashboard (VIMI-21260) ..................................................................................... 29
Invoice Reversal and Re-posted document to be connected back to the
original DP (VIMI-19273). ................................................................................... 29
New authorization checks in BC Workplace for VIM items (VIMI-21170) .................. 29
Fiori Supplier Self Service Portal: Download Supplier Invoices in Excel format
(VIMI-21258) ....................................................................................................... 30
On-Premise Mobile Approval Portal as a Tile on Fiori Launchpad (VIMI-
21365) ................................................................................................................. 30
Supplier Self Service Fiori Apps on SAP Cloud Platform (VIMI-21899) ..................... 30
Fiori: Fullscreen view for VIM Approvals (VIMI-20719) .............................................. 30
FIORI Apps: Display of user names in case of substitutes (VIMI-18996) .................. 31
Usability improvement for search in history in Web Approval Portal (VIMI-
21157) ................................................................................................................. 31
Default value for Goods Invoice/Service Indicator on the PO indexing screen
(VIMI-18518) ....................................................................................................... 31
New authorization check in VIM Automation Report and the Year End Report
(VIMI-19532) ....................................................................................................... 31
COA Maintenance - new alternative transaction (VIMI-18099) .................................. 31
Additional Fields in Standard Workplace Configuration (VIMI-20151) ....................... 31
3.4 Delta information for VIM 7.5 customers ................................................................................. 32
Corresponding Support Package levels ..................................................................... 32
Obsolete ABAP add-ons ............................................................................................. 32
Obsolete reports and transactions ............................................................................. 33
Obsolete features ....................................................................................................... 34
Other changes and limitations .................................................................................... 36
3.5 VIM 16.3 ABAP add-ons shared with OpenText Business Center .......................................... 39
4 Packaging and documentation ................................................................................................... 40

4.1 Packaging and delivery information ........................................................................................ 40
Mandatory packages .................................................................................................. 40
Optional packages ...................................................................................................... 41
VIM OCR add-on ........................................................................................................ 42
4.2 Related documentation ............................................................................................................ 43
5 Supported environments and compatibility .............................................................................. 45
4
5.1 Supported systems .................................................................................................................. 45
5.2 Supported clients for VIM Fiori Apps ....................................................................................... 49
5.3 Supported version of Invoice Capture Center ......................................................................... 49
5.4 Supported ArchiveLink Content Repositories .......................................................................... 50
5.5 OpenText product compatibility ............................................................................................... 50
5.6 SAP Netweaver Version compatibility matrix for OAP 16.3 (VIM web portal): ........................ 51
5.7 Approval Portal Downward Compatibility Matrix ..................................................................... 51
5.8 Web browser and mobile device support (VIM web portal) ..................................................... 52
5.9 Web Viewer support ................................................................................................................ 54
5.10 Brava View support (VIM OAP) ............................................................................................... 54
5.11 Language support .................................................................................................................... 55
5.12 VIM Fiori Apps: Variants .......................................................................................................... 56
5.13 VIM Simple Mode Fiori Apps: Variants .................................................................................... 56
6 Installation and upgrade notes ................................................................................................... 57

6.1 Installation notes ...................................................................................................................... 57
6.2 Upgrade notes ......................................................................................................................... 58
Upgrade from Vendor Invoice Management 16.3 to a higher Support
Package .............................................................................................................. 58
Upgrade from Vendor Invoice Management 7.5 SP5 or later on S4HANA
1610 (no SAP upgrade) ...................................................................................... 58
SAP S/4HANA conversion to SAP S/4HANA 1610 .................................................... 58
SAP S/4HANA conversion to SAP S/4HANA 1709 and 1809 .................................... 58
6.3 Fiori apps requiring report runs ............................................................................................... 58
6.4 Add-on deletion ....................................................................................................................... 59
7 Support Package .......................................................................................................................... 60
8 Post Installation Activities .......................................................................................................... 61

8.1 Import transports with perspective layouts for Fiori Apps ........................................................ 61
8.2 Baseline Configuration Changes ............................................................................................. 61
Configuration Changes in VIM 16.3.1 ........................................................................ 61
Configuration Changes in VIM 16.3.2 ........................................................................ 65
9 Optional Post Installation Activities ........................................................................................... 73

9.1 Handling Substitution Profiles in VIM (VIMI-20808) ................................................................ 73
10 Known issues ............................................................................................................................... 73

10.1 Installation / Upgrade / Conversion ......................................................................................... 74
10.2 VIM Simple Mode .................................................................................................................... 75
10.3 VIM Supplier Self Service App................................................................................................. 76
5
10.4 VIM Invoice Approval App ........................................................................................................ 76
10.5 VIM Invoice Approval App – Bulk Mode .................................................................................. 77
11 Fixed issues .................................................................................................................................. 78

11.1 Fixed issues for 16.3.1 ............................................................................................................ 78
Document Processing (DP) ........................................................................................ 78
Document Processing (DP) – Logic Modules............................................................. 85
Invoice Approvals ....................................................................................................... 86
Web Approval Portal ................................................................................................... 88
Mobile Approval Portal................................................................................................ 89
Fiori Approve Invoices app ......................................................................................... 89
Input Channels ........................................................................................................... 89
Invoice Exception ....................................................................................................... 90
VIM Notifications ......................................................................................................... 90
VIM Analytics report and VAN Liability report ............................................................. 91
Central Reporting and other reports ........................................................................... 92
VIM Workplace ........................................................................................................... 92
Supplier Self Service .................................................................................................. 93
Enter Cost Assignment Fiori app ................................................................................ 93
Confirm Quantity and Price Fiori app ......................................................................... 94
Installation and Upgrade ............................................................................................. 94
11.2 Fixed issues for 16.3.2 ............................................................................................................ 94
Document Processing (DP) ........................................................................................ 94
Document Processing (DP) – Logic Modules........................................................... 102
Invoice Approvals ..................................................................................................... 102
Web Approval Portal ................................................................................................. 104
Fiori Approve Invoices app ....................................................................................... 105
Fiori Enter Cost Assignment app .............................................................................. 105
Fiori Confirm Quantity and Price app ....................................................................... 106
Fiori Exceptions app ................................................................................................. 106
Input Channels ......................................................................................................... 106
Invoice Exception ..................................................................................................... 107
VIM Notifications ....................................................................................................... 107
VIM Analytics (new VAN) Report and VAN Liability Report ...................................... 108
Central Reporting and Other Reports ....................................................................... 109
VIM Workplace ......................................................................................................... 109
Customizing .............................................................................................................. 110
6
Supplier Self Service ................................................................................................ 110
Installation and Upgrade ............................................................................................ 111
12 Contact information ................................................................................................................... 112
7
1 Introduction
These Release Notes provide an overview of OpenText™ Vendor Invoice Management for SAP®
Solutions Version 16.3.2, 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 Notes revision history
Revision date Sections revised Description of revisions
2017-10-31 First release. All new content.
2017-11-07 Minor text corrections
2017-11-29 3.1.2 Optional packages Add BW add-on
2018-03-02 All Support Package 16.3.1
2018-11-05 All Support Package 16.3.2
New features,
Packaging and Several updates to expand the information on
2018-11-13
Documentation, Post delivered packages, documentation.
Installation
Added post installation steps for configuration

2018-11-16 Post Installation
changes.
Adjustments due to the passing the SAP

2018-12-14 Premium Qualification. Important SAP Notes for
workflow module added.
Supported environments Added Approval Portal Downward Compatibility

2019-01-07
and compatibility Matrix
Adjusted the date of language packages

2019-01-24 Language support
availablity
8
2 About OpenText™ Vendor Invoice Management for
SAP® Solutions
This section provides an overview of OpenText™ Vendor Invoice Management for SAP® Solutions
Version 16.3.2 (equivalent to Version 16.3 SP2).
OpenText™ Vendor Invoice Management by SAP Solutions (“VIM”) is an add-on solution to SAP
S/4HANA on Premise to optimize and simplify the process of receiving, automating, managing,
routing and monitoring of incoming invoices.
With implementation of Vendor Invoice Management companies achieve:
• Acceleration of AP operations across the enterprise through integration with SAP Business
Suite and SAP S/4HANA
• Boost of productivity and revenue by automating routing, approval, and payment processes
• Improved vendor relations with better access to current, accurate vendor information
• Accurate, on-time financial reporting with automatic access to AP information
• Improved cash flow by streamlining workflows, initiating reminders, and shortening the
payment cycle
• Regulatory compliance with a well-managed process using preconfigured rules, roles and
actions
VIM provides:
• Multi-channel input for digital and non-digital invoice formats like scanned paper invoices,
PDF invoices attached to emails, EDI invoices, network invoices, and so on. This includes
integration of SAP Ariba network based on SAP’s built-in interface with Ariba.
• OCR add-on (Invoice Capture Center) for intelligent and automated capture for invoice data
from scanned and PDF invoices
• Secure storage and archiving of invoice documents and additional documentation including
processing and approval protocol through SAP ArchiveLink
• Deep integration into SAP through building on SAP Enterprise technology like ABAP, SAP
Business Workflow, SAP NetWeaver
• Framework for data enrichment and data checks to achieve automation of specific classes of
invoices based on the input from OCR or electronic channels
• Tools and workflow processes to optimize processing of invoices that cannot be fully
automated by their nature or invoices triggering exceptions during the automated processing.
• Best practice logic to allocate different tasks to the right team and users, for example:
o Review of basic invoice issues by Accounts Payable or Shared Services team
o Allocation of specific exceptions to specialized experts, for example a tax expert
reviewing complex taxes
o Send tasks and notifications to teams outside Accounts Payable like Purchasing
team, Goods-in department and roles like receiver, requester and approvers
• Comprehensive approval workflow
• Unblocking workflows for invoices blocked for payment
• Various UI options (SAP GUI, Web, Fiori) for optimizing user experience for all roles and
users involved in invoice handling and approval
• A suite of reports to monitor the invoice process, create liability figures for invoices not yet
posted, do evaluations to calculate KPI figures, and further optimize the invoice process
9
• Extraction and preconfigured content for SAP Business Warehouse
• A large library of business rules and data mappings and data enrichment modules
• A preconfigured best-practice baseline configuration delivered as SAP customizing set
• Comprehensive extension points through customizing tables, workflow framework, BADIs and
ABAP interfaces to override and extend the baseline and pre-delivered logic to adjust to
special requirements and to implement customer-specific optimizations.
VIM does not replace SAP invoice transactions like MIRO nor the core logic of logistic invoice
verification (MM):
• Many categories of invoices can be automated or treated by manual intervention through VIM
screens.
• For some invoice types, navigation from VIM into SAP invoice transaction (typically MIRO) is
required to fully post the invoice as not all MIRO fields are provided in VIM baseline
• VIM builds on the SAP core logic of invoice blocking reasons (most prominently price and
quantity) to trigger workflows for invoices blocked by SAP invoice verification.
VIM shares some key components with OpenText Business Center for SAP Solutions, which allows to
easily extend the methodology of capturing and onboarding business documents to SAP S/4HANA
beyond invoices.
VIM provides additional value when used in combination with other OpenText SAP-centric solutions
like OpenText Archiving and Document Access for SAP Solutions and OpenText Extended ECM for
SAP Solutions.
10
2.1 “Classic Mode” versus “Simple Mode”
Starting with version 16.3 and only available for SAP S/4HANA 1610 and later, VIM provides two
implementation options.
Classic Mode:
Classic Mode is to a large extent compatible with previous VIM versions 7.0 and 7.5. It offers proven
architecture and a framework and many options to configure and extend the pre-delivered invoice
management logic. For VIM 16.3 the classic approach was updated to meet SAP S/4HANA
requirements and optimizations and follow SAP strategy to post all invoices through one invoice
transaction: Baseline uses transaction MIRO for all invoices types including Non-PO invoices.
Classic mode is the choice for organizations upgrading from SAP ECC and older VIM versions who
want to gradually adopt to new SAP S/4HANA concepts and keep the basic approach to invoice
processing.
Classic mode provides powerful SAP GUI or web GUI based tools like VIM Workplace and VIM
Analytics report, a web portal for invoice coding, and approval that can be integrated with SAP
NetWeaver Portal and Fiori apps for different tasks like simple coding, approval, and confirming price
and quantity on PO related invoices.
Simple Mode:
Simple Mode provides a new invoice process designed according to SAP S/4HANA standards and
concepts like simplification, principle-of-one, digitalization, cloud-first, and new user experience from
the start.
While the “Classic Mode” provides different options, the “Simple Mode” philosophy is about a uniform
best practice approach based on different invoices types:
• Invoices that can be automated by their nature and structure

• Invoices that can be automated with limited manual processing
• Invoices that need manual processing and may use very specific features of SAP’s invoice
app
Features of “Simple Mode”:
• Runs with a minimum of configuration based on pre-delivered best practices settings

• Limited classical customizing (done on DEV box and transported into QA and PROD system)
• Increasing number of settings available through Fiori
• Use of SAP invoice drafts to store preliminary invoice data (instead of separate business
object and header and line items tables of classic mode)
• Built around SAP’s Fiori App “Manage Supplier Invoices”
• End-to-end Fiori
• (future) Cloud OCR extraction and information service
• Advanced machine learning features to optimize data capture (feedback from SAP process
and SAP posting to data recognition)
• Fiori based “validation” screen for entering core invoices fields
11
• More “smart” and self-adapting features like intelligent coding defaults, dynamic auto-
classification of vendors into black, grey and white list, and others.
Processing of invoices through “Simple Mode”
1. Capture of scanned paper invoices and PDF invoices through OCR cloud service with
automated optimization through constant feedback. Other invoices are received from
networks like Ariba or classic IDOCs or other channels.
2. Background: Initial classification of incoming invoice data to control process and flow
(happens in background) – separate in invoices going through automation and invoices that
need manual intervention
3. Automation: Apply automation logic and check of business rules for invoices, leading to auto-
post if there is no exception
4. Manual: An Accounts Payable user processes invoices that need manual intervention in a
Fiori App providing a “processing screen”:
a. Contains main header and line item fields
b. Display of scanned/uploaded invoice
c. Provides option to switch to SAP Fiori App “Manage Supplier Invoices” for invoices
that need complex input (fields that are not available in VIM and cannot be treated by
automation)
5. Background: similar to step 3 – Background logic is now applied to invoices that have been
manually indexed through the Fiori app and auto-posted if there is no exception.
6. Exception handling: AP and other roles get work item tasks to handle invoices that run into
exceptions or need approval.
7. Invoice can be manually posted by navigating from the VIM Fiori apps to SAP’s Fiori App
“Manage Supplier Invoices”.
Limitations of Simple Mode

Vendor Invoice Management 16.3 provides a basic version of the new “Simple Mode.”
A number of features are not yet released and there are further limitations. Future
versions will provide new features to fully provide the scope of the “Simple Mode” as
explained above.
12
Note
OpenText Vendor Invoice Management by SAP Solutions 16.3.
supports SAP S/4HANA 1610 on Premise, 1709 and 1809.
Future SAP S/4HANA on Premise versions will typically be supported by
the VIM Update (Support Package) directly after release of the new SAP
S/4HANA on Premise release.
The following SAP products are not supported by OpenText Vendor
Invoice Management by SAP Solutions 16.3: SAP ERP, SAP Suite on
HANA, SAP Simple Finance, SAP S/4HANA Finance, and SAP
S/4HANA 1511. These SAP versions are supported by OpenText Vendor
Invoice Management by SAP Solutions 7.5.
SAP S/4HANA public cloud editions 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.2 General Data Protection Regulation (GDPR)

The General Data Protection Regulation (GDPR) is a new European Union (EU) law that gives
residents greater protection and control of their personal data. It will regulate the data that companies
in and outside the EU can collect, store, and transfer – as well as how they use it. All companies that
process EU resident data must be ready to comply when the GDPR enforcement starts on May 25,
2018.
SAP S/4HANA provides a superior level of user security and data protection features. VIM as add-on
package profits from the high standard of S/4HANA compared to outside-in solutions with their own
database, duplication of data and lower level security concepts.
Software solutions like VIM cannot be considered to be or not to be GDPR compliant. Every customer
using SAP S/4HANA and VIM is responsible to provide GDPR compliance in their organization.
Several VIM features and additional details listed in product documentation can help clients to
achieve GDPR compliance.
13
3 Features
OpenText™ Vendor Invoice Management for SAP® Solutions Version 16.3.2 includes the following
new features and changes compared to OpenText™ Vendor Invoice Management for SAP® Solutions
7.5.
3.1 New Features in VIM 16.3

MIRO as invoice transaction for all invoices (“unified posting approach”)
Following SAP’s recommendation for SAP S/4HANA, the VIM 16.3 baseline configuration is built around
SAP transaction MIRO and the BAPIs of SAP object type BUS2081 (BAPIs for logistic invoices). This
includes posting of invoices without relation to a purchase order (“Non PO invoices”), which were posted
using FB60 and finance BAPIs or Batch Input on FB60 in older VIM versions.
The Simple Mode is built around SAP’s Fiori App “Manage Supplier Invoices”.
Processing of parked and held documents

Parked and held MM documents can be processed within the VIM Document Processing (“DP”)
workflow.
Simplified baseline
A simplified baseline configuration is delivered as SAP configuration set with the following features:
• Posting all invoices in MIRO and logistic BAPIs

• Processing of parked and held MM documents within VIM Document Processing (“DP”) workflow.
• Simplified baseline roles: core roles are AP processor and AP expert.
• Unified process options: consistent configuration across different roles
• Optimized processing: Sequence of logic modules and business rules reviewed and improved
Simple Mode
“Simple Mode” provides a new invoice process designed according to SAP S/4HANA standards and
concepts like simplification, principle-of-one, digitalization, cloud-first, and new user experience from
the start as described in the introduction.
Note that in this version the Simple Mode has a couple of limitations and some features will be
provided in future support packages and/or new versions.
OCR interface for Cloud OCR interface

A web service based interface for the OCR is delivered with the following features:
• Connection to the (planned) OpenText Information Extraction Services, Cloud edition

• Feedback engine for machine learning capabilities
The web service interface is not a public API as it will be used for the OpenText Information Extraction
Services, Cloud edition in the future. This service is planned to be available in the near future.
14
Central Reporting
VIM Central Reporting is supported on S/4HANA on Premise Editions with the following limitations:
• No cross-system aggregation – use central reports only for local system

• Central reports are not (yet) optimized for running with HANA database – there might be
performance limitations in HANA with higher number of records.
New reports/analytics options are planned in the future based on SAP S/4HANA embedded analytics.
Multi-backend communication across different versions

For customers running several instances of SAP ERP and SAP S/4HANA on Premise, VIM 16.3 offers
multi-system integrations in combination with VIM 7.5 SP 7 (and later) on SAP ERP.
VIM Fiori apps

VIM includes the following Fiori Apps
• VIM Approve Invoices Fiori app

This app can be used by any employee and managers. Requester approves if invoice details
are correct, approval of non-PO and PO invoices by cost center owners, project leads,
managers.
• VIM My Approved Invoices Fiori app
This apps can be used by any employee and managers. It lists all approved invoices of the
user.
• VIM Resolve Invoice Exceptions Fiori app
This app can be used by Accounts Payable to forward invoice queries and exceptions to other
roles (for example: invoice without PO number, Goods Receipt missing, generic Info
Requester query).
• VIM Enter Cost Assignment Fiori app
This app can be used to enter accounting information on header level for non-PO invoices,
includes split and use of templates, supports occasional non-trained coders who can leverage
simple options like “my cost center”, “my project”.
• VIM Confirm Quantity and Price Fiori app
This app can be used to get feedback from the requester of a purchase order around quantity
or price mismatch on line item level, missing goods receipts and confirmation of line items
without GR.
• VIM Supplier Self Service Fiori app
This app allows suppliers to see invoice and payment status of their invoices.
• Integration of VIM approval portal into Fiori
The VIM approval portal (installed on SAP NetWeaver Java) can be integrated into the SAP
Fiori Launchpad as Fiori tile. It provides line-item based invoice coding of Non-PO invoices
and approval of PO and Non-PO invoices.
VIM 16.3 “Simple Mode” includes the following Fiori apps
• VIM My Invoices Fiori app

This app allows the expert accountant to access all invoices within the different process steps
15
(Validate / Process / Code / Approve) according to role assignment. It provides a workplace-
like view on the outstanding and finished processes in a web browser.
• VIM Validate Invoices Fiori app
This app allows the validator to validate the invoice and to enter missing information with
single click entry using a web browser. A limited duplicate check is available: company code,
invoice reference and document date combination must be unique.
• VIM Process Invoices Fiori app
This app allows the accountant to resolve invoice exceptions, to bypass rules, and to access
the invoice in the SAP Fiori app Manage Supplier Invoices.
• VIM Enter Cost Assignment Fiori app
This app allows users to enter cost assignment data for invoices. Several cost objects are
available: cost center, internal order, wbs element. An invoice can be split to different cost
objects.
• VIM Approve Invoices Fiori app
This app allows users to approve their invoices, using web browsers.
Fiori WebUI framework enhancements

The Fiori framework in VIM provided by the add-ons of Business Center was enhanced. For more
details, see section “New Features” in the release notes of OpenText™ Business Center for SAP®
Solutions 16.3.
Supplier Self Service (lean variant)

The VIM Supplier Self Service web app (lean variant) is supported as part of VIM 16.3.
Additional features compared to VIM 7.5

For additional features compared to VIM 7.5 (base release) see the release notes of VIM 7.5 SP 1 to
SP 6.
16
3.2 New Features in VIM 16.3.1
New VIM Supplier Self Service Fiori app (VIMI-18628)
A new Fiori app is now delivered for Supplier Self Service along with accompanying self registration
function.
• Supplier onboarding/off-boarding process (self registration):

o Supplier registration functionality is provided to allow suppliers to register themselves.
o The registration is a completely automated process, using email for communication.
o Suppliers, once successfully onboarded, receive an email with Fiori Launchpad link and
user credentials.
o A program is available to repeat the registration and send a new email.
• Supplier Invoices app:

o Supplier can view the status of invoices for the registered company codes.
o Supplier can view the invoice details, payment details and PO or delivery notes.
o Searching invoices is possible by document number, invoice amount, and reference
number.
o Filtering and sorting function are provided.
• Supplier Accountant app:

o The Supplier Accountant can view all the registered supplier’s invoices and suppliers can
inquire about their invoices’ status.
o The Supplier Accountant can view the invoice details, payment details, and PO or delivery
notes.
o Searching invoices by document number, invoice amount, reference number, and
company code is possible.
o Filtering and sorting functions are provided.
VIM Configuration Guide provides details on the configuration of the delivered functions.
New VIM My Approved Invoices Fiori app (VIMI-20329)

A new Fiori app for displaying approved invoices which were processed by a user is available.
Attachment Upload for VIM Approve Invoices Fiori app (VIMI-20281)

The existing VIM Approve Invoices Fiori app was enhanced with the capability to upload and delete
invoice attachments.
Attachment Upload for VIM Enter Cost Assignment Fiori app (VIMI-
20282)
The existing VIM Enter Cost Assignment Fiori app was enhanced with the capability to upload and
delete invoice attachments.
Disabling withholding tax warning message “Withholding tax calculation

has changed” (VIMI-19142)
A new Z-constant has been introduced that disables the indexing screen warning message
“Withholding tax calculation has changed”.
Use transaction SM30 to add the following entry into the table /PTGWFI/Z_CONST:
17
Product Code = 005
Constant = NO_WHT_MESSAGE
Description = If set, withholding tax changes do not create a message on indexing screen
Constant Value = X
Fiori Confirm Quantity and Price app: background posting after PO price
change (VIMI-19386)
A PO based invoice without GR required but with price discrepancy, which has been “price confirmed”
in the app and which has been referred to the buyer, will be posted in the background after buyer
changes the PO accordingly.
Limitations: only if there are no more exceptions after the ‘Confirm Quantity/Price Confirmation
Required” step.
Spanish localization: SII Support (VIMI-18756)

As part of “Support for SII” ("Immediate Supply of Information"), SAP proposes to store long invoice
numbers in more than one field, this means XBLNR or BKTXT or Custom in BKPF. See the SAP
note 2409025 ver. 6.
A new field (LXBLNR) is introduced to hold the complete/entire ‘Long invoice number’ in VIM. During
DP processing/posting, VIM supports the following two options, aligned with SAP’s proposal, this
means based on XBLNR, BKTXT in BKPF.
Option 1) Prefix part => XBLNR; Sequence Number part => BKTXT
Option 2) Prefix part => BKTXT; Sequence Number part => XBLNR
Two parts of the long invoice number, this means Prefix + Sequence Number, can be configured
(using a Z-constant) to split into fields (XBLNR, BKTXT) and post invoices accordingly.
• The Z-constant (005/ SET_REF_MAPPING_SP) allows the customer to choose option 1 or 2,

along with offset length for prefix part and sequence number part.
Option 1) Example value: X10,B25 => First 10 characters of long invoice number are
mapped to XBLNR & next 25 characters are mapped to BKTXT.
Option 2) Example value: B20,X16 => First 20 characters of long invoice number are
mapped to XBLNR & next 16 characters are mapped into BKTXT.
Option 3) Based on a custom field in BKPF
If you choose the third option, a custom field in BKPF, to store either partial or complete invoice
number, no support is available for this. However, it is still possible to customize standard BDC/BAPIs
to save the invoice number into a custom field, while posting invoices.
18
Implementing custom field validation in the DP indexing screen (VIMI-
19347)
If standard field validations performed by VIM in the DP indexing screen are not sufficient, additional
validations can be implemented, in the form of a function module called like a user exit.
The validation will be called in change mode for all indexing dashboard actions except the exit type
functions located in the dashboard toolbar. (Those exit type functions are used for special processing
that does not allow to read the current screen data.)
Note also that actions performed in the plug-in toolbar, typically in the right panel, will result into the
validation call, but the corresponding actions cannot be stopped by passing the error message type
back from the user exit, because of technical limitations. In case you would like to skip validation on
plug-in toolbar actions, or on any other actions, you can implement a check of the OK code in your
user exit. The example source code at the end of this section shows how to do this.
To activate and perform the data validation, a function module must first be created with the following
interface:
*" IMPORTING
*" VALUE(INDEX_DATA) TYPE /OPT/VIM_1HEAD
*" VALUE(INDEX_DATA2) TYPE /OPT/VIM_2HEAD
*" VALUE(OK_CODE) TYPE SY-UCOMM

*" VALUE(PROC_OPT) TYPE /OPT/VIM_1RACTION
*" TABLES
*" INDEX_ITEMS STRUCTURE /OPT/CIDX_ITEMS

*" INDEX_WTAX STRUCTURE /OPT/CIDX_EWHTAX
*" RETURN STRUCTURE BAPIRET2
The function module logic receives, in addition to the document data, the active OK code and the
selected process option (if any). It is supposed to return an internal table with messages. All
messages will be shown in a popup. If any error type (A, E, X) messages will be returned, the screen
processing will be stopped once the popup is closed.
To activate the user exit, the following Z-constant entry must be created with the value equal to the
function module name, in the table /PTGWFI/Z_CONST:
Product: 005
Constant: DP_VALIDATE_EXIT
Description: DP indexing screen - validation exit
Value: user exit function module name
Sample function module source code:
19
DATA:
ls_return TYPE bapiret2,
lv_mesg TYPE sy-msgv2.
CHECK ok_code(4) <> '%_GC'. "skip plug in commands
lv_mesg = ok_code.
CALL FUNCTION 'BALW_BAPIRETURN_GET2'
EXPORTING
type = 'W'
cl = '00'
number = '398'
par1 = lv_mesg
IMPORTING
return = ls_return.
APPEND ls_return TO return.
ENDFUNCTION.
Adding the Forward action from VIM Workplace (WP) in the VIM logs
(VIMI-19368)
Until VIM 7.5 SP6 the action of forwarding a workitem was not being logged. From VIM 7.5 SP7
onwards this action is also logged (during bulk and individual processing), provided it is performed
from VIM Workplace. This action will be logged only for non-approval work items.
New customizing for mandatory comment when declining an invoice in

Fiori Enter Cost Assignment app (VIMI-19538)
The VIM Fiori Configuration “Enter Cost Assignment Customizing for Completeness and Changing”
can be used to make the comment in the confirmation popup window mandatory:
• In “Custom1-Name” enter: COMMENT_AT_REJECT.

• In the related “Selected?” field choose ‘true’.
New business rule: SCB Indicator / Supplying Country Missing (VIMI-

19721)
A new process type (business rule) has been added to check for missing SCB indicator and Supply
Country fields in the DP process. The new process types are 190 for PO invoices (standard document
type PO_S4) and 290 for Non-PO invoices (document type NPO_S4). The corresponding customizing
is delivered in the BC set provided with this support package.
20
Restricting ALV layout for process logs (VIMI-18719)
It is sometimes required to limit the amount of information shown to VIM users in the logs of
Document Processing and Invoice Approvals. For example, some columns must be hidden. This can
be solved by creating global ALV layout variants for the selected ALV screens, making those variants
default, and at the same time restricting user authorizations to modify the ALV layouts themselves.
This is implemented at the following locations:
• Display of DP process and approval logs in VIM Workplace

• Display of DP process and approval logs in VIM Analytics
• Display of DP process logs in VIM Unified Dashboard
To activate the checks in general, the value of the Z-constant 009 / ALV_CHECK_ACTIVE must be
set to X in VIM constant table /PTGWFI/Z_CONST. With this activated, the authorization can be
controlled with the authority check object J_6NIM_ALV:
The users authorized for activity = 02 will be allowed to maintain ALV layouts for the mentioned
screens.
The unauthorized users will not have any layout options active in ALV toolbars of the mentioned
screens. The default global variant will be used all the time.
The recommended approach to restricting the ALV display:
• Assign change authorization (J_6NIM_ALV) to certain users who will be responsible for ALV
layout maintenance.
• The authorized users will create a global default variant in each ALV screen.
• All user specific ALV layouts for the following programs will be deleted:
/OPT/CL_C_UI_PLUGIN_DEF_LOG===CP
/OPT/CIDX_OUTPUT_LOG_ST
/OPT/SAPLVIM_RPT_FG_005
Note: The ALV layout deletion can be performed as described in SAP Note 933916.
• The authorization check for ALV layout will be activated (table /PTGWFI/Z_CONST, 009 /
ALV_CHECK_ACTIVE).
Changing logical system on VIM tables (VIMI-18607)

After performing a system or client copy, for example, of production system data into a test system,
many VIM tables will retain original logical system value, and this may break some VIM functions. To
replace the logical system name, a new program is provided:
Program name: /OPT/VIM_REPLACE_LOGSYS (no transaction code)
Selection screen:
• Logical system “From” and “To”
21
• DP document ID
• Test mode – check box
To replace the logical system, enter the name of the original logical system in the “From” field, and
enter the target value in the “To” field. The replacement can be performed on specific DP documents
by using the DP document selection. The test mode, enabled by default, allows to review the potential
replacement results.
The results log will be shown as output.
Support for branch code – Thailand specific (VIMI-19339)

Branch code can now be used in DP documents to post Non-PO and PO invoices in Thailand
company codes. The new field can be enabled in the DP indexing screen and the value will be
passed into background posting with standard VIM posting logic.
Additional accounting data section in coding templates when exporting

coding in Approval Portal (VIMI-16466)
The data from the additional accounting section will now be written into the exported coding template.
Initial sorting in the Approval Portal inbox (VIMI-18087)

Approval Portal users can now personalize the default sort order of the inbox with the option provided
on the Personalization page. This option is not applicable to the history section and for mobile
approvals.
Notes:
• This feature will be available to the users who are using VIM 7.5 SP7 ERP.
• OpenText recommends to perform the metadata cache clearing steps described in VIM
Administration Guide after installing the SP to make sure the function will be active.
Default option to show invoice image in Web Approval Portal (VIMI-

18832)
The default option to open any invoice image in Web Approval portal is modified to “Show invoice in a
separate window on Request only".
Configuration of timeout for Approval Portal web requests (VIMI-18925)

A new field “Request Timeout (in milliseconds)” has been introduced in the Admin console. Through
this field, administrators can configure the timeout of the Approval Portal web requests.
Refreshing the Approval Portal inbox after using a custom button (VIMI-
19060)
Earlier, when using a custom button in the Approval Portal, the inbox was not being refreshed,
although this was necessary in some situations. Now, the handling function configured for the custom
button can fill the new "REFRESH_LIST" parameter of action RFC ('/OPT/OAP_INVOICE_ACTION')
with 'X' to indicate that the Approval Portal has to refresh the inbox.
22
Improvements in the invoice inquiry status display in the Approval
Portal (VIMI-19516)
In the Approval Portal inbox, invoices sent to inquiry with enabling the option “Wait for feedback” will
now be displayed with “Waiting” status. The invoices sent without enabling the waiting option will be
displayed with “Pending” status.
Search Help support in additional accounting data area in Approval

Portal (VIMI-19711)
Search helps are now supported in the additional accounting data area of the invoice detail screen.
Search Help support for custom header fields in Approval Portal (VIMI-
19732)
Search helps are now supported for custom fields in the basic (header) data area of the invoice detail
screen.
Tax code description display in the DP indexing and Approval screens

(VIMI-19367)
Tax code description is now available in the DP indexing screen and approval screens.
Support of GST Registration Number for receiving location (VIMI-19408)

GST Registration Number for receiving location is now supported in the DP indexing screen in the
context of Indian GST.
Support of HSN Code in PO Line Items Proposal (VIMI-19408)

Default value of HSN code will now be set in the PO line items proposal in the context of Indian GST.
User exit to determine default proposal for next approver if not unique
(VIMI-19033)
When the search of the next approver is being performed, and there are several potential approvers
according the COA, it is now possible to implement custom logic to select the next approver. The new
method NEXT_ALT of the approval class can now be implemented to determine the next approver.
This is a further step to the feature implemented in VIM 7.5 SP6, which provided a user exit for line
based sequential approval (VIMI-18022). Now, header based approval is also supported.
Cross release multiple backend support (VIMI-19650)

As of VIM 16.3 and VIM 7.5 SP7 it is possible to run different VIM versions and SP levels in a multiple
backend scenario. Because of complexity, not all possible multiple backend functions are supported.
Support is provided for:
23
• Centrally controlled DP document numbers
• Starting VIM workflows in satellite systems, initiated by central system
• VIM Workplace, when executed on the central system: Executing work items, displaying
document data. Workplace can still be executed in the satellite systems, but to access only
local work items.
• VIM Analytics, when executed on the central system – all functions. VIM Analytics can still be
used in the satellite systems, but to access only local documents.
• Central reporting (only with 7.5 on SAP ERP).
All other multiple backend scenarios are currently not supported, including restarting workflows and
sending documents back into central system, running business rules or duplicate check in remote
systems.
For more information, see VIM Scenario Guide.
Reduction invoice support (VIMI-19274)

To support reduction invoice processing and handle corrections in quantity and value, the
following functions are implemented:
1. New line item fields RBWWR, RBMNG, KZMEK are introduced.

2. New Business rule “Check for Reduction Invoice” was introduced.
3. New BDC ID 202 was introduced to post the reduction invoice in background.
4. Modified BDC ID 200 to post the reduction invoice in online mode.
Functionality: Select the correction ID (KZMEK) as “Vendor Error. Reduce Invoice” from the drop
down list in the line item column “Correction ID” and press ENTER. The original amount and quantity
will be copied into the fields “Invoice Amount FC” (RBWWR) and “Inv.doc.qty” (RBMNG). Then
change the amount and quantity in original amounts and quantity fields.
Configuration: Configure the fields RBWWR, RBMNG, and KZMEK as input fields at item level for
G/L tab only. Configure the business rule and BDC ID for auto posting or background posting of
reduction invoice. The configuration is described in the Post-Installation section of this document and
is also delivered in the BC set.
iOS 11 support for Mobile Approvals (VIMI-20210)

iOS 11 is now supported for Mobile Approval Portal.
Support of GST Import Procurement (VIMI-19432)

GST Import Procurement is now supported in the context of Indian GST.
Full user name in comments (VIMI-17866)

The header line of process comments will now show full user name instead of SAP or internal user ID.
24
Usermap and COA Cleanup (VIMI-20317)
Open Text provides a program to clean personal data from VIM Approvals COA in the context of
GDPR. It supports two functions:
• Cleaning the personal data from the usermap for records marked as inactive, selected by
user. No records are deleted, but the following fields are set to blank: last/first/middle name,
department, email, phone number.
• Deleting the usermap records, COA and coder records, for records marked as inactive,
selected by user.
Notes:
• The program does not check whether there are approval workflows that are still open. Such
check is being performed in the COA maintenance transaction when a user is being
deactivated.
• Approver name can be eventually stored in approval process comments. The comments are
stored as SAPScript objects and are not deleted by the program.
• When personal data is cleared, corresponding change documents are written. The existing
values will then be visible in the change documents created in the process. The change
documents can be deleted later using standard SAP tools.
Program selection screen:
Parameters:
User Mapping Object ID – User selection. The value is in the format internally used by approvals. If
those values are not assigned based on E-mail-IDs (standard setting), it is recommended to use
search help that allows searching by real user names. Note that only records marked as inactive will
be displayed in the search help and will be processed later.
25
Erase personal data – Personal data fields will be set to blank values.
Delete records – Selected usermap records will be deleted along with corresponding COA and coder
entries.
Test run – Use this to verify the potential deletion results.
26
3.3 New Features in VIM 16.3.2
BW4HANA Add-On
From 2016 SAP launched a new product for Business Warehouse – BW4HANA – which is an
evolution of BW that is completely optimized and tailored to SP HANA.
The existing VIM BW add-on 7.0 has been converted and adapted to be compatible for this new
product. A new BW4HANA add-on OTVIMBW4 component is delivered together with VIM 16.3.2.
The component installed on BW4HANA communicates seamless with OLTP system installed with VIM
16.3.2.
The content delivered in VIM 16.3 BW4HANA is the same as the content delivered in VIM BW 7.0.
There are some aspects in the new components:
- On source (OLTP) system, all BW Extractors are replaced by ODP-enabled Extractors, which
allow to use the ODP framework to extract data from source system to be consumed in
BW4HANA system.
- Unsupported objects in BW add-on are replaced by objects designed primary for SAP HANA
database.
- All multiProviders are replaced by Composite Providers. They can be consumed by
advanced, state of the art SAP BusinessObject tools like SAP Lumira or SAP BusinessObject
Design Studio.
Please refer to Configuration Guide, Chapter SAP NetWeaver Business Warehouse for detailed
information.
VIM Fiori Apps Cleanup Program (VIMI-17860)

VIM Fiori Apps are using several database tables to store temporary data. Sometimes, particularly in
cases when the process is overtaken by other users in the same Fiori Apps or in SAPGUI, the
cleanup of those tables cannot be performed automatically. To drop that data, a program must be
scheduled to run in the background periodically. The same program can also be run in dialog mode
on demand.
Program name: /OTX/PS03_FCLEANUP
Selection screen parameter: Test mode (checkbox).
For background run, make sure the test mode is off in the corresponding variant.
Recommended run schedule: once a day.
Support of Ariba Cloud Integration (VIMI-21327)

Ariba Cloud Integration Gateway is a new integration option supported by VIM now.
27
The minimum VIM release and SP levels are VIM 7.5 SP5 with OpenText Business Center (BC) 16.0
update 1, and VIM 16.3 with Business Center 16.3.
Because of dependencies on the SAP ARBCI1 and ARBCI2 components, OpenText delivers the
necessary objects as a separate set of transport files. You find the transport files on Open Text My
Support.
The delivery of the transport files is provided with VIM 7.5 SP7. Integration is supported by other
versions as described above. You can use the provided transport files with the mentioned older VIM
versions and SPs.
For more details on the installation and configuration of Ariba CIG support for VIM, see VIM
Installation Guide and Configuration Guide respectively.
Integration with Information Extraction Service (VIMI-21687)

Starting with VIM 7.5 SP8 and VIM 16.3 SP2, Open Text Information Extraction Service (IES) can be
used in scenarios requiring OCR. The support of IES is built on using the new features delivered with
Open Text Business Center 16.3 SP2. It requires this support package of the Business Center (BC),
as well as BC-based VIM solution, which is delivered for VIM 7.5 SP8 with the component
OTBCSL03, and on VIM 16.3 SP2 it is built into the core VIM delivery.
For more details, see VIM and Business Center Configuration Guides.
Calculation of Unplanned Delivery Costs – New User Exit (VIMI-19434)

The logic to determine whether tax is calculated on unplanned delivery costs is encapsulated in the
pricing procedure configuration. It is not reliable from a VIM perspective to rely on this logic, as it is
code based rather than configuration based.
A new Z-Constant 005 / DETERM_TAX_UDC has been introduced, that can be used by the customer
to encapsulate logic to determine whether tax is to be calculated on unplanned delivery costs.
The interface for the user exit can be found in the function module /OPT/DETERM_TAX_UDC.
Warning message in COA maintenance when email address already

used (VIMI-19590)
Warning message will be shown while creating a new approver in the COA and the mail address is
already used by an inactive approver.
28
Support of workflow substitution profile when maintaining
substitutions for approvals (VIMI-20808)
It is now possible to assign and use substitution profile to VIM users when maintaining substitutes
from Approval portal or /ORS/MAIN_SUBS.
VIM can handle only one substitution profile that will be used for VIM tasks and this profile should be
maintained in the Z-constant IAP / USE_SUBS_PROFILE so that when substitutes are maintained
from Approval portal or with the transaction /ORS/MAINS_SUBS, this profile will be assigned for the
substitutes.
Warning on header level action in blocked invoice dashboard (VIMI-

21259)
A pop-up displaying a warning message will be shown, when a header level action affecting all the
line items is executed on blocked invoices.
Last user in the process history of the blocked invoice header level
dashboard (VIMI-21260)
The user who performed the last action on the blocked line item can now be seen on the blocked
header dashboard directly, in the 'Last Agent' column, without having to click the 'View Log' button.
Invoice Reversal and Re-posted document to be connected back to the

original DP (VIMI-19273).
A new utility has been implemented to allow to select an invoice posted from VIM, cancel it, and start
a new DP workflow with a document containing the same data. DP process log, approval log and
entered comments will be copied and linked to the new DP document. This allows to restart the
process, keeping the history easily available for reference.
Technical Object details:
Transaction code: /OPT/INV_CANCL_RECRT
Program Name: /OPT/INVOICE_CANCEL_DP_CREATE
New authorization checks in BC Workplace for VIM items (VIMI-21170)

Authorization object J_6NIM_WP6 will be checked in BC Workplace when working with VIM
workitems.
To enable authorization checks in BC Workplace on VIM workitems and restrict the execution based
on company codes, new class for dynamic filter is now provided.
Navigate to the path /OTX/PF00_IMG -> Workplace configuration -> Navigation -> Nodes
Select the VIM related node and double click on Filter Criteria and maintain the entry as shown below
29
Attribute BUKRS
Sign Range Limit included
Option Equals
Exit for Dynamic filter criteria /OTX/PS03_CL_03_AUTH_CC_WP
The BC Set delivered with this SP provides the dynamic filter entries for all relevant nodes.
To make the check active, the global authorization check Z-constant 009 / AUTH_CHECK_ACTIVE
must be set to X.
Fiori Supplier Self Service Portal: Download Supplier Invoices in Excel

format (VIMI-21258)
This feature enables the user to download the supplier invoices to Microsoft Excel (.xls and .xlsx
format) from the Fiori Supplier Self Service app.
On-Premise Mobile Approval Portal as a Tile on Fiori Launchpad (VIMI-

21365)
This feature enables the user to access Mobile Approval Portal as a tile from the Fiori Launchpad.
More details on this are provided in VIM Administration guide, the section “Configuring Approval Portal
for launching on Fiori Launchpad”.
Supplier Self Service Fiori Apps on SAP Cloud Platform (VIMI-21899)

From this SP, the Supplier Self Service Fiori apps, including the Registration app, can be deployed on
SAP Cloud Platform.
Further details can be found from Configuration guide, the section “Configuring the Supplier Self
Service app on the cloud”.
Fiori: Fullscreen view for VIM Approvals (VIMI-20719)

The Approve Invoices (bulk mode) app is now available with a fullscreen inbox view. It provides the
following features:
• With the Multi Select button user can select multiple invoices for approval that are ready for
only approval and that are assigned to your inbox by the VIM approval workflow logic.
30
• You can also perform Approve or Reject actions on the invoices from the Invoice List using
Direct Approve and Direct Reject icons that are assigned to your inbox by the VIM approval
workflow logic.
• You can also perform Approve, Reject and other actions on the invoice by navigating to the
detail perspective shown in the Approve Invoices app.
Please refer to the section “VIM Approve Invoices (bulk mode) Fiori app” of VIM Configuration Guide
for further details.
FIORI Apps: Display of user names in case of substitutes (VIMI-18996)

The following feature is related to FIORI Approval/Coding Apps. When the user is acting as a
substitute for one or several people, the user’s name will be displayed along with the “On Behalf” text.
Usability improvement for search in history in Web Approval Portal

(VIMI-21157)
The entered search criteria will be preserved within the search form as long as a user stays in the
history. That is, when opening the search dialog again, the previously used search criteria will be
prefilled.
Default value for Goods Invoice/Service Indicator on the PO indexing

screen (VIMI-18518)
It is now possible to configure default value for Goods Invoice/Service Indicator on the PO indexing
screen. The value is picked from the indexing screen and stored in the user defaults to be retrieved
when the user re-opens the indexing screen.
New authorization check in VIM Automation Report and the Year End
Report (VIMI-19532)
Company code authorization check have been implemented in VIM Automation Report and Year End
Report. See VIM Configuration Guide for more information regarding authorization checks.
COA Maintenance - new alternative transaction (VIMI-18099)

A new transaction is now provided to maintain the Chart of Authority. The transaction supports only
updating of COA, which is the third tab in the COA maintenance transaction available in earlier
SPs/versions. The new transaction can be used to maintain larger amounts of data, compared to the
older one.
Refer to VIM Configuration Guide for more details on the new transaction.
Additional Fields in Standard Workplace Configuration (VIMI-20151)

Few output fields have been enabled for display in VIM Workplace with the standard configuration:
Purchase order, Current agent and Current role.
31
3.4 Delta information for VIM 7.5 customers
This section explains the main differences between VIM 16.3 and VIM 7.5 (and older versions).
Corresponding Support Package levels

VIM 16.3 versions contain all bugfixes and features from corresponding 7.5 service packs. The
following table lists the corresponding packages:
VIM 16.3 Version VIM 7.5 Version
VIM 16.3 VIM 7.5 SP6
VIM 16.3.1 VIM 7.5 SP7
VIM 16.3.2 VIM 7.5 SP8
When planning an upgrade, the target support package version for VIM 16.3 must be the same or
higher than the current corresponding VIM 7.5 support package version.
Obsolete ABAP add-ons

The following table lists VIM ABAP add-ons that were included in older VIM versions but are not
delivered anymore with VIM 16.3:
VIM ABAP Add-Ons Description Details
OTVIMSSF SSF add-on for CRM Integration into SAP Shared Services Framework
system – This feature is currently not (yet) available on
SAP S/4HANA on Premise.
OTVIMHNA, HANA specific add-ons The VIM CDS views are now included into the
OTVIMCDS for SAP Suite on HANA core VIM add-on OTEXVIM.
OTVIMARB Ariba integration Now included into core VIM add-on OTEXVIM
OTVIMS4 SAP S/4HANA specific Now included into core VIM add-on OTEXVIM
objects
OTBCSL03 VIM/BC integration Now included into core VIM add-on OTEXVIM
32
Obsolete reports and transactions
The following VIM reports and transactions are obsolete in VIM 16.3 and therefore not supported:
VIM reports Description Details
Old VIM Analytics Old VIM Analytics – Transaction Replaced by new VIM Analytics
/OPT/VIM_ANALYTICS
Integrated Invoice Integrated Invoice Cockpit (IIC) – Replaced by VIM Workplace and
Cockpit IIC Transaction /OPT/VIM_IIC Business Center Workplace
All reports for Batch All reports applied for Batch Jobs related For example, Sync job for VIM
Jobs of unsupported to unsupported components / features Analytics
components are obsolete.
33
Obsolete features
The following table lists features of older VIM versions that are obsolete in VIM 16.3:
VIM Features Description Details
Simple approval Simple / Manager-based approval flow Replaced by new Level-based

and old COA (transaction approval flow and new COA
/OPT/VIM_7CX1) (transaction /OPT/AR_COA)
Note: this is still supported for
upgrading customers that were using
this feature in VIM 7.0 and earlier
versions.
Old indexing screen Old indexing screen Replaced by new indexing screen
released in VIM 7.0
Incoming Document IDH provides services to receive and Replaced by Business Center Inbound
Handling (IDH) handle most kinds of incoming Configuration
documents.
ICC dispatcher ICC dispatcher provides services like Replaced by Business Center Inbound
storing, retrieving, extracting, validating Configuration
documents for integration with ICC.
Multi backend Following multi backend options are Use local central reports and remote-
Features unsupported: Multi-backend collection enabled VAN Report.
and aggregation in Central Reporting.
Supplier Self Service Old Supplier Self Service component Replaced by new Fiori App
with full variant
Classic Withholding Classic Withholding Tax Only Extended Withholding Tax is

Tax supported (VIM follows core SAP
approach.)
Parked PO Workflow Old workflow templates for Processing Parked documents are now handled
of Parked Workflow for invoices with within the VIM Document Processing
Purchase Order (DP) workflow .
Parked NPO Workflow Old workflow templates for Processing Parked documents are now handled
(FI) of Parked Workflow for invoices within the VIM Document Processing
without Purchase Order (DP) workflow. Parked workflow from
VIM 7.5 is not supported anymore.
34
35
Other changes and limitations
The following table lists further changes and limitations compared to older VIM versions.
VIM Scenario Description Details
Web / Mobile approval Java-based approval portal Web and mobile approval portal is
portal (NetWeaver Portal, stand-alone, supported for VIM 16.3 and SAP
mobile) S/4HANA on Premise.
Support is limited by SAP’s support for
SAP NetWeaver Java and SAP
NetWeaver Portal and SAP JCo
connected to SAP S/4HANA on
Premise.
Strategic direction is Fiori. OpenText

recommends customers who are
adapting SAP Fiori to use the VIM Fiori
Apps instead of VIM web and mobile
approval portal.
Web / Mobile approval Blackberry OS Blackberry OS is not supported

portal - Compatibility
Web / Mobile approval Microsoft Mobile Microsoft Mobile is not supported

portal - Compatibility
OpenText recommends using the built-

Integration with Ariba Ariba Network integration based
in integration with Ariba network in
Network Process on SAP PI and Ariba Cloud
SAP S/4HANA for connecting Ariba
Integration Adapter / Ariba Integration component.
network to VIM. See SAP help for
Cloud Integration (CI)
Business Network Integration – Ariba
Network Integration.
Minimal support version of Ariba Cloud

Integration (CI) in VIM 16.3 is CI 8.
Posting of invoices Per default, all types of invoices Post non-PO and PO invoices through
(with and without purchase order) MIRO and use logistic invoice BAPIs
are posted in logistic invoice for both PO and non-PO invoices.
verification (transaction MIRO and
For some invoice types, navigation
BAPIs of Business Object Type
from VIM into SAP invoice transaction
BUS2081).
(typically MIRO) is required to fully
post the invoice as not all MIRO fields
are provided in VIM baseline.
36
Posting of invoice in FI Posting in the FI module should In the baseline configuration, all
module (FB60) be restricted to special cases. invoices are posted within logistics
invoice verification (MIRO).
For special scenarios, custom specific

document types can be configured to
support posting via FB60 (see below).
Restriction: Parking FI documents is
not supported in this scenario.
Posting of PO invoices in BDC 6 is replaced by the unified Upgrading customers may continue to
Background with BDC 6 posting logic (MIRO and logistic use existing configurations but in
BAPIs). general it is recommended to switch to
the new posting logic.
Posting of NPO in FI Only BDC ID 40 is supported with BDC 40 can be configured to allow
module in Dialog with BDC restrictions (Transaction code posting in FB60 (FI module) in dialog.
40 FB60) (*).
This is only supported for cases, where
posting via unified posting logic in
logistics invoice verification is not
possible.
Posting of NPO in FI Only BDC ID 41 is supported with BDC 41 can be configured to allow
module in Background with restrictions (Transaction code posting in FB60 (FI module) in
BDC 41 FB60) (*). background.

possible.
Posting of non-PO invoices BDC 42 is replaced by the unified Upgrade customers may continue to
in Background with BDC42 posting logic. use existing configurations. It is
recommended to switch to the new
posting logic.
Posting of PO in Dialog Only BDC ID 1 is supported with BDC 1 can be configured to allow
with BDC 1 restrictions (Transaction code posting in MIRO (MM module) in
MIRO) (*). dialog.
possible.
Posting of Down Payment Only BDC ID 50 is supported

in Dialog (Transaction code F-47) (*).
37
Use of “Batch Input” For example: BDC ID 1, BDC ID SAP has indicated that going forward
technology for background 40, BDC ID 41, BDC ID 50 (*) Batch Input technology might not be
postings and calling a supported anymore on SAP S/4HANA.
transaction like MIRO, OpenText will support BDCs
FB60 in dialog mode mentioned here as long as Batch Input
for the relevant product BDCs is still
working in S/4 and as long as SAP still
gives this option.
OpenText will discuss with SAP how

Batch Input can be replaced for critical
features.
VIM 16.3 does not out-of-the-box
Brazilian invoices Country specific features for
support processing of invoices
Brazilian invoices
according to NF-e standard. For more
details, see the VIM 16.3 Scenario
Guide.
* Remark “Batch input and use of FB60 for non-PO invoices”:
SAP has announced that Batch Input is a technology that might be blacklisted in the future for SAP
S/4HANA. Some VIM BDCs using this technology will only be supported as long as SAP is still
supporting Batch Input. But in general, OpenText strongly recommends using VIM BDCs based on
BAPIs for background postings. BDC 34 provides the unified posting logic instead of other BDCs
using batch input or the Finance BAPI.
38
3.5 VIM 16.3 ABAP add-ons shared with OpenText Business Center
The VIM 16.3 delivery includes some ABAP add-ons that are developed as part of OpenText Business
Center for SAP Solutions and used in VIM and other OpenText solutions. These add-ons are
summarized as “OpenText Business Center for SAP Solutions Foundation (ABAP)”. A customer using
VIM does not need to purchase Business Center. The add-ons are provided as part of VIM and are
covered by VIM maintenance and support.
The VIM license covers usage and support of the OpenText Business Center for SAP Solutions
Foundation (ABAP) for processing incoming invoices only (incoming credit notes and other
incoming invoice variants are included).
Definition of limited use of Business Center Foundation ABAP:
• Customers are only allowed to use OpenText Business Center for SAP Solutions Foundation
(ABAP) for processing of invoice documents inside the SAP Accounts Payable process.
• Customers are entitled to add Business Center processing steps to their VIM DP workflow for
incoming invoices.
• A VIM DP document ID must be allocated and the invoice must be visible as entry in VIM
Analytics.
• Examples of use cases are, for example, use of the generic Fiori Task App, use of the
Business Center Workplace, creation or change of vendor master triggered by an incoming
invoice, and re-approval of an SAP purchase order triggered by a price difference of the
invoice.
• Explicitly excluded are processing steps related to creation of transactional SAP business
objects other than invoice postings (SAP Object type BKPF and BUS2081) like purchase
orders, purchase requisitions, delivery notes, sales orders, and so on. Excluded are any
processing steps related to other master data SAP business objects than vendor master or
other SAP objects or document types not related to incoming invoices. Processing of other
SAP objects like mentioned in this bullet point requires a full OpenText Business Center
License.
Note
Use of Business Center components as part of VIM
In addition to VIM 16.3 release notes and documentation, make sure to
review OpenText Business Center 16.3 release notes and documentation
as well.
39
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:
Mandatory packages
For implementing VIM classic mode including Fiori apps the following packages are mandatory:
Component Description
OTEXVIM VIM core package

Contains VIM workflows, transactions, reports, tables, CDS views, and so on.
Business Center
OTBCSL30 VIM Solution Core: development objects for integration of VIM with the Business
Center framework
Business Center Base

OTBCBAS General technical objects and basic customizing used by all Business Center
add-ons
OTBCINB Business Center Inbound

Includes Inbound Configuration.
OTBCFND Business Center Foundation

Process Foundation, Process Configuration, and Workplace Configuration.
OTBCWSR Business Center Web Services (Fiori)

Data and model services for Business Center Web UI.
Business Center Solution Base

OTBCSL00 Includes general technical objects for solutions (like VIM) and solution
accelerators.
40
The following packages are required on the Fiori server (front end) when implementing VIM Fiori Apps
OTBCWUI Business Center Web UI
OTBCUS03 VIM 16.3 UI Package (Fiori)

VIM specific Fiori development objects
Optional packages
VIM – Simple mode

OTBCSL08
Development objects for VIM simple mode based on the Business Center
framework
OTBCRM Business Center Extended ECM Integration

Includes integration to Extended ECM.
OTVIMBW VIM – BW add-on for BW System
OTVIMBW4 VIM – BW4HANA add-on for BW4HANA System
OTVIMGW VIM - Gateway package for Supplier Self Service Lean Variant
The following package is required to implement the VIM web portal for invoice coding and approval
based on SAP NetWeaver Java and SAP NetWeaver Portal:
IM_APPROVAL_PORTAL16.3_Java16
IM_APPROVAL_PORTAL16.3_Java18 VIM Approval Portal OAP 16.3 (JAVA)
Several additional packages are delivered along with this SP that are required for VIM Fiori apps. The
table below lists the delivered files, specifying the related deployment scenario. All files are to be
found in the same directory where the components packages for VIM BC solution are located.
File Name Description Deployment

scenario
VIM Fiori Apps’ perspectives layouts (a
fiori_perspectives_layouts.zip transport) On-premise
41
Pre-configured tiles and target mapping for
vendorinvoicemanagement-
VIM Fiori Apps (a transport) On-premise
launchpadcontent.zip
Pre-configured Fiori Launchpad portal site
neo_VendorInvoiceManagement- for VIM Fiori Apps (a package to be
SCP
LaunchpadContent.zip imported on the cloud platform)
VIM Fiori Apps UI (a Fiori app package to be

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

Fiori app package to be imported on the
otusrregui_neo.zip SCP
cloud platform)
VIM OCR add-on

The VIM option for OCR capture and recognition is a separate product called “OpenText Invoice
Capture Center for SAP Solutions” with separate release notes and documentation.
42
4.2 Related documentation
For additional information about OpenText™ Vendor Invoice Management for SAP® Solutions and for
supplemental information about related products, refer to the following documents, which are
available on OpenText My Support (https://support.opentext.com).
Document title (Code number) Available languages
OpenText Vendor Invoice Management for SAP Solutions 16.3.2 Installation English
Guide (VIM-IGD)
OpenText Vendor Invoice Management for SAP Solutions 16.3.2 English

Configuration Guide (VIM-CGD)
OpenText Vendor Invoice Management for SAP Solutions 16.3.2 English

Administration Guide (VIM-AGD)
OpenText Vendor Invoice Management for SAP Solutions 16.3.1 Reference English
Guide (VIM-RGD)
OpenText Vendor Invoice Management for SAP Solutions 16.3.2 Scenario English
Guide (VIM-CCS)
English,
German, French,
OpenText Vendor Invoice Management for SAP Solutions 16.3.2 User Guide
Spanish, Japanese,
(VIM-UGD)
Portuguese, Italian,
Dutch, Russian,
Chinese*
* The language translations are provided for VIM 16.3 on My Support.
43
Document title (Code number) Available languages
OpenText Business Center for SAP Solutions 16.3.2 Installation Guide English
(BOCP-IGD)
OpenText Business Center for SAP Solutions 16.3.2 Configuration Guide English
(BOCP-CGD)
English
German, French,
OpenText Business Center for SAP Solutions 16.3.2 User Guide (BOCP-
Spanish, Japanese,
UGD)
Portuguese, Italian,
Dutch, Russian,
Chinese*
* The language translations are provided for Business Center 16.3 on My Support.
44
5 Supported environments and compatibility
This section provides details about supported platforms, systems, and versions.
5.1 Supported systems

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

VIM does not support SAP S/4HANA public cloud editions.
For details, Support Package levels of SAP platforms, and for dependencies on Business Center add-
ons, see the following tables:
45
Software Release Minimal Support
VIM Component
Component Package Level
SAP_BASIS 751/752/753 0000 2)

OTEXVIM
S4CORE 101/102/103 0000
SAP_ABA 75B/75C/75D 0000
OTBCSL30 1610_104 1)
S4CORE 101/102/103 0000
SAP_ABA 75B/75C/75D 0000

OTBCSL30
SAP_BASIS 751/752/753 0000
OTBCFND 0700_004 1)
OTBCUS03 OTBCWUI 0740_004 1)
S4CORE 101/102/103 0000
SAP_ABA 75B/75C/75D 0000
SAP_BASIS 751/752/753 0000
OTBCSL08 OTBCFND 0700_004 1)
OTBCSL30 1610_104 1)
SAP Fiori App See full details in VIM 16.3.1

“Manage supplier Installation Guide for prerequisites for
Invoices” VIM simple mode.
OTVIMGW SAP_ABA 750
SAP_BASIS 750
SAP_GWFND 750
IM_APPROVAL_PORTAL16.3_Java16 SAP NetWeaver

IM_APPROVAL_PORTAL16.3_Java18 Java 7.3, 7.4, 7.5
0000
SAP NetWeaver
Portal
46
Business Center Minimum Minimal Support
Software Component
Component Release Package Level
OTBCBAS SAP_BASIS 751/752/753
OTBCINB OTBCBAS 0700_004 1)
OTBCFND OTBCINB 0700_004 1)
OTBCFND 0700_004 1)
OTBCRM
OTEXRL 1620_700
OTBCBAS 0700_004 1)
SAP_BASIS 751/752/753
OTBCWSR
751 0002
SAP_GWFND 752 0000
753 0000
SAP_BASIS 751/752/753
750 0007
751 0002
OTBCWUI SAP_UI
752 0000
753 0000
SAP UI5 1.52.* -
OTBCSL00 OTBCFND 0700_004 1)
SAP_ABA 75B/75C/75D
S4CORE 101/102/103
1) Check the support package compatibility matrix in chapter 7 about allowed support package
combinations
2) We recommend implementing the following two SAP notes in case they are relevant for your
SAP_BASIS SP level:
2660814
2704861
47
The Business Center Fiori Web UI (OTBCWUI) in detail supports the following UI5 versions:
OTBCWUI Version UI5 Version
0740_004 1.52
You can check the installed version by following the relative URL
/sap/public/bc/ui5_ui5/index.html.
48
5.2 Supported clients for VIM Fiori Apps
See also section “4.2 Supported clients for Business Center Fiori Task App” in Business Center
Release Notes.
Client OS Browsers
Desktop Windows 7, 8.1, 10 Internet Explorer >= 11.0

Microsoft Edge [latest current
branch for Business]
Google Chrome [Latest version]
Mozilla Firefox [Latest version]
Smartphone / Tablet iOS (iPad, iPhone) >= 9 * Safari in “normal” mode

Safari Home-Screen bookmark**
SAP Fiori Client App
Android >= 4.4 * Google Chrome [Latest version]
* See supported reference devices:

https://sapui5.netweaver.ondemand.com/sdk/#/topic/74b59efa0eef48988d3b716bd0ecc933
** Requires the optional configuration “Enable Inplace Document View for iPhone and iPad”
Note: The Fiori Apps also support the Compact/Cozy mode provided by the UI5 toolkit
for adopted content density depending on the touch support of a device.
5.3 Supported version of Invoice Capture Center

OpenText Vendor Invoice Management is compatible and supported with specific versions of Invoice
Capture Center (ICC). The following table lists the supported combinations:
VIM Version ICC Version
VIM 16.3 ICC 16.3, BCC 16.3 or higher
VIM 16.3.1 ICC 16.3.1, BCC 16.3.1 or higher
VIM 16.3.2 ICC 16.5 SP2 or higher
49
5.4 Supported ArchiveLink Content Repositories
VIM in general is compatible and supported with any archive solution that is compatible with SAP
ArchiveLink and certified by SAP.
If you are using the OCR option, Web Portal, or Fiori, you must have an archive solution that supports
the SAP Content Server HTTP 4.5 Interface.
VIM is specifically tested and validated for
• OpenText Archiving and Document Access for SAP Solutions.
• OpenText Documentum Archive Services for SAP
Some specific functions (for example the input channel batch pipeline) are only supported for OpenText
Archiving and Document Access for SAP Solutions.
5.5 OpenText product compatibility

This section provides details about which versions of other OpenText products are compatible with
this release of OpenText™ Vendor Invoice Management for SAP® Solutions Version 16.3.2.
Note: For the latest compatibility information for OpenText products, refer to the Compatibility
Matrix (https://knowledge.opentext.com/go/matrix) on OpenText My Support.
Product name Version Notes
All versions
For more details see also release
currently
OpenText Extended ECM for SAP Solutions notes of Business Center 16.3 (xECM
supported
integration in Fiori)
by OpenText
All versions
currently
OpenText Archiving and Document Access
supported
by OpenText
50
5.6 SAP Netweaver Version compatibility matrix for OAP 16.3 (VIM
web portal):
SAP Netweaver Version

OAP Versions
7.0 7.3 7.4 7.5
16.3 SP1
16.3 SP1 JCo3 Java 1.8 and above
5.7 Approval Portal Downward Compatibility Matrix

The following table lists the supported combinations of the Web Approval Portal (OAP) and the VIM
backend versions.
Compatibility VIM 16.3 SP1 VIM 16.3 SP2

Matrix VIM 16.3
OAP 16.3 SP1
OAP 16.3 SP2
51
5.8 Web browser and mobile device support (VIM web portal)
The following table lists the supported combinations of web browsers and the Web Approval Portal
versions:
Web Browser Supported Browsers and Versions

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

Google Chrome is supported for version 22 and later.
Safari is supported for version 5.0 and later.
OpenText recommends using the latest browser version.
52
The following table lists the supported combinations of the operating systems for mobile devices and
the Web Approval Portal versions:
Mobile Devices Matrix OAP 16.3 OAP 16.3.1 OAP 16.3.2
iOS (9.0)
iOS (10.0)
iOS (11.0) (support planned) (support planned) (support planned)
Android (> 4.0)
BlackBerry BBOS 6.0
BlackBerry BBOS 10
Windows 8 Phone
Windows 10 Phone
Note
In general, you can view the Mobile Approval Portal inside the browsers on all kind of
Android devices. Due to the diversity of physical Android devices, OpenText cannot
guarantee 100% compatibility on all functionality that the Mobile Approval Portal offers.
Consider the list of all supported browsers also.
53
5.9 Web Viewer support
The following table lists the supported combinations of Web Viewer and the OpenText Approval Portal
versions:
Supported Web Viewer versions

Web Viewer
support matrix 10.5 16
Web Mobile Web Mobile
OAP 16.3
OAP 16.3.1
OAP 16.3.2
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.
5.10 Brava View support (VIM 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 16.3
OAP 16.3.1
OAP 16.3.2
54
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.11 Language support

OpenText™ Vendor Invoice Management for SAP® Solutions is localized in the following languages.
Component Languages
EN DE JA FR IT ZH ES RU
OpenText Vendor B, F B, F B, F B, F B, F B, F B, F B, F
Invoice Management
Component Languages
NL PT HU RO TR PL CZ SK
OpenText Vendor B, F B, F UI UI UI UI UI UI
Invoice Management
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.
NOTE: the language packages will be provided for download by the beginning of February, 2019.
55
5.12 VIM Fiori Apps: Variants
The following table lists the supported variants of VIM Fiori apps:
On- Desktop Tablet Smart

Fiori App Cloud
Premise Phone
VIM Approve Invoice Fiori App
VIM Enter Cost Assignment Fiori App
My Approved Invoice Fiori App
VIM Quantity and Price Fiori App
VIM Resolve Invoice Exceptions Fiori App
VIM Supplier Self Service Fiori App
VIM Bulk Approve Fiori App
5.13 VIM Simple Mode Fiori Apps: Variants

The following table lists the supported variants of VIM Fiori apps:
On- Desktop Tablet Smart

Fiori App Cloud
Premise Phone
VIM Approve Invoice Fiori App
VIM Enter Cost Assignment Fiori App
VIM Process invoice Fiori App
56
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 Installation notes

The installation of OpenText™ Vendor Invoice Management for SAP® Solutions is described in
OpenText Vendor Invoice Management 16.3.2 Installation Guide.
Please note that the installation sequence of VIM and Business Center add-ons (delivered with VIM)
is important. 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
Consider specific requirements and instructions associated to the VIM gateway component for the
Supplier Self Service (lean). For details see OpenText Vendor Invoice Management 16.3.2 Installation
Guide.
57
6.2 Upgrade notes
The upgrade of OpenText™ Vendor Invoice Management for SAP® Solutions is described in
OpenText Vendor Invoice Management 16.3.2 Installation Guide.
Different scenarios are considered:
Upgrade from Vendor Invoice Management 16.3 to a higher Support

Package
Follow the support package installation section in the Installation Guide.
Upgrade from Vendor Invoice Management 7.5 SP5 or later on S4HANA

1610 (no SAP upgrade)
Follow the upgrade section in the Installation Guide.
SAP S/4HANA conversion to SAP S/4HANA 1610
The S/4 HANA conversion can be done on VIM 7.5 SP5 or later. After the conversion, VIM can be
upgraded to 16.3.
Additional information can be found in the conversion section of the Installation Guide.
SAP S/4HANA conversion to SAP S/4HANA 1709 and 1809
The S/4 HANA conversion should be done with VIM 7.5 SP6 or later. The VIM upgrade package
(same as installation package) must to be provided during the conversion because VIM 7.5 is not
supported on SAP S/4HANA 1709 and 1809.
Additional information can be found in the conversion section of the Installation Guide.
6.3 Fiori apps requiring report runs
The two Fiori apps “Enter Cost Assignment” 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 two reports to get rid of old draft data:
- /OTX/PS32_DROP_ALL_DRAFTS
- /OTX/PS35_DROP_ALL_DRAFTS
58
6.4 Add-on deletion
VIM 16.3 ABAP add-ons can technically be removed from the SAP S/4HANA on Premise system. This
was not possible in older versions. Deletion of an add-on like VIM is considered an exceptional case
and all consequences must be considered, like data loss of transactional data stored in VIM tables. If
any VIM or Business Center add-on should be deleted from your system, then OpenText requires
customers to open a ticket at OpenText Customer Support for VIM to discuss details of the planned
deletion and get in-depth information about how-to-do and potential risks.
59
7 Support Package
VIM 16.3 and Business Center 16.3 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 backend component
that is required for a specific VIM version and support package level.
VIM release name VIM 16.3 VIM 16.3 SP1 VIM 16.3 SP2
BC Release Name BC 16.3 BC 16.3 SP1 BC 16.3 SP2
OTBCBAS 0700_004 0700_004 0001 0700_004 0002
OTBCINB 0700_004 0700_004 0001 0700_004 0002
OTBCFND 0700_004 0700_004 0001 0700_004 0002
OTBCSL00 0700_004 0700_004 0001 0700_004 0002
OTBCWSR 0740_004 0740_004 0001 0740_004 0002
OTBCSL30 1610_104 1610_104 0001 1610_104 0002
OTEXVIM 81610_104 81610_104 0001 81610_104 0002
Frontend Packages
It is possible to install a higher SP level of the frontend packages (OTBCWUI and OTBCUS03) and
connect to backends with lower SP levels. The following combinations are supported:
VIM release name VIM 16.3 VIM 16.3.1 VIM 16.3.2
OTBCWUI 0740_004 0740_004 0001 0740_004 0002

0740_004 0001
OTBCUS03 0740_004 0740_004 0002 0740_004 0003
0740_004 0001
0740_004 0002
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.
60
8 Post Installation Activities
8.1 Import transports with perspective layouts for Fiori Apps
Perspective layouts for Fiori apps are not included into 16.3 SP2 package. Unless additionally
imported, VIM Fiori apps item perspective layouts will not be loaded, and error popup will be shown
with the respective error message.
The following transports are provided:
D9PK901941
The transport is available as an additional file download in the directory of VIM 16.3 SP2 (similar to
the language transports).
8.2 Baseline Configuration Changes

The following sections describe the changes of baseline VIM configuration delivered in each support
package. In case when by some reason you are not using the BC sets delivered with the support
packages, you can review the changes and perform them manually.
Note that the changes in Business Center configuration related to VIM solution (BC Inbound or Fiori
apps) are not described below because of the complexity of performing such steps manually. You
must use the provided BC sets.
Configuration Changes in VIM 16.3.1

8.2.1.1 New business rule: SCB Indicator / Supplying Country Missing (VIMI-19721)
Follow the steps in this section to create the configuration required to use the new business rule “SCB
Indicator / Supplying Country Missing”. Note that in case you are using custom document types, the
steps must be performed for them similarly.
1. Create new Process Types:

a. Go to transaction /OPT/SPRO > Document Processing Configuration > Process
Configuration > Maintain Process Types.
b. Create two new process types (or copy existing process types):
190 | SCB Indicator / Supplying Country Missing (PO)
290 | SCB Indicator / Supplying Country Missing (NPO)
61
c. Make sure that for both process types the characteristic check is active:
2. Assign the Process Types to the Document Type:

a. Go to transaction /OPT/SPRO > Document Processing Configuration > Document Type
Configuration > Maintain Document Types
b. Assign Process Type 190 to the PO Document Type and Process Type 290 to the NPO
Document Type.
c. Add Process Type to Document Type sequence.
62
NPO Document Type:
PO Document Type:
d. Add Sequence Steps in the PO and NPO Document Type.

e. Add Fields „SCB_IND“ and „SUPCOUNTRY“ as „Required Field“ in both Document Types:
63
f. Add Index Screen Options
PO Document Type:
NPO Document Type:
3. Activate the new Business Rules country/characteristic-specific:

a. Go to transaction /OPT/SPRO > Document Processing Configuration > Document Type
Configuration > Characteristic Specific Document Type Configuration
b. Mark the Characteristic (Country) where you want to activate the new Business Rules.
Example Germany (DE):
c. Add Process Types 190 and 290 to the Characteristic Specific Process Types:
64
Important: Use Category Group „12 – Intra-Community, Imports and Triangulati[on]“ because this
Business Rule should be activated for foreign vendors only.
Configuration Changes in VIM 16.3.2

8.2.2.1 GL account and Cost center field are not transferred to MIRO during online posting through
VIM (VIMI-21444).
Navigate to the following customizing note in VIM configuration:
Find the record shown in the screenshot below:
Perform the change as shown below (replace DRSEG_CO-SAKNR with ACGL_ITEM-HKONT):
65
Perform another change for field KOSTL:
Changed content:
8.2.2.2 Support of reduction invoices (VIMI-19274).
66
This section describes the configuration of the new DP process type and BDC ID for the support of
reduction invoice. In addition (and this is neither described below not delivered in the BC set) you will
need to enable your PO document types to display the new input fields RBWWR, RBMNG and
KZMEK.
Configure the new business rule (process type) and BDC ID for auto posting or background posting of
reduction invoice as shown below.
Configure the new DP process type:
Configure the process options:
Add the new process type for your PO DP document types. Note that the BC set delivers the process
type as inactive, and you need to activate it as needed. Provide the new BDC IDs as shown below.
New BDC ID 202 is used to post the reduction scenario document.
67
Configure the process type determination sequence:
Business rule related function module and its configuration is as follows:
Create the new BDC ID 202:
68
An implicit enhancement is used to call VIM logic within MIRO transaction. The enhancement is not
delivered with the BC Set. Create an implicit enhancement point at the end of form
“MRM_DRSEG_FILL” in the program “LMRMHF0A” and place the code as shown below screen shot.
69
8.2.2.3 Subsequent credit incorrectly processed as invoice (VIMI-21731).
To process subsequent credit documents via IDOCs, modify the IDOC mapping:
Go to field mapping for IDOC mapping ID, add an entry for External Field Name - VORGANG
with Field Type - Header and Document Field Name - VORGANG.
In the Automatic Field Mapping for IDOC mapping ID, modify the existing entry with external
Field Name - VORGANG to 'CREDIT_MEMO'.
After modification the entry appears as below.
70
Navigate to the node IDOC data mapping:
For the Field name 'BSART', modify the existing Document Field Name 'CREDIT_MEMO' to
'VORGANG'.
After modification the mapping appears as below for BSART field.
8.2.2.4 Additional Fields in Standard Workplace Configuration (VIMI-20151).
Navigate to the following customizing node to add new output fields in VIM Workplace:
Add three new fields into the DEFAULT profile as shown below:
71
72
9 Optional Post Installation Activities
The post installation activities described in this chapter are optional and not delivered with the BC set.
9.1 Handling Substitution Profiles in VIM (VIMI-20808)
VIM can handle only one substitution profile which can be used for the VIM tasks. The substitution
profile created via SAP standard process, should be maintained in the Z-constant
'USE_SUBS_PROFILE'' so that when substitutes are maintained from Approval portal or
/ORS/MAINS_SUBS, this profile will be assigned for the substitutes.
Please maintain the substitution profile in the constant value of the Z-constant
'USE_SUBS_PROFILE'.
10 Known issues
73
10.1 Installation / Upgrade / Conversion
Issue number Issue description
Important information when planning a system conversion from ERP to

S4HANA.
Currently the SAP Maintenance planner is not allowing the Conversion from
ERP to S4HANA, if VIM 7.5 SP7 (OTEXVIM) and higher is installed together
with Business Center components on version 16.3.
Please make sure, that the BC components (OTBCFND, OTBCINB, OTBCBAS

and others) are still on version 16 when planning a conversion.
This is a temporary issue of SAP Maintenance Planner. If you have already

installed VIM 7.5 SP7 with BC Components on version 16.3, please contact the
SAP Support (Component SAP Maintenance Planner) for the current status.
74
10.2 VIM Simple Mode
VIM Simple Mode: Additional features and critical corrections will be delivered in
Support Package 3
VIMI-22297 On S/4HANA1610: Background posting may fail with error message "Company
Code is not defined".
Reason: Error in component MM-FIO-IV Error in class

CL_MMIV_SI_FIELD_CONTROL, Method
IF_MMIV_SI_FIELD_CONTROL~SET_INITIAL_GL_ITMS_PROP_VAL
Issue is fixed in S/4HANA1709 and higher.
Workaround: Invoice needs to be saved/held or parked once manually in the

Managed Supplier Invoice App
VIMI-22338 On S/4HANA1809: Short Dump during background posting of an invoice draft:

The BOPF runtime has detected a runtime error of business
object MMIV_SUPPLIER_INVOICE.
Reason: Error in component MM-FIO-IV.
Solution: Implement SAP Note 2719086.
VIMI-22345 VIMI-22345
On S/4HANA1809: Background Posting may fail with error message "Invoice

document XXX blocked for processing" or “Invoice is locked. Please retry in 30
Minutes.”
Reproducing: A user edited the held or parked document with the Manage
Supplier Invoice App and closed the app via “Back” Button or by closing the
browser.
Reason: Standard behavior in Managed Supplier Invoice App: Locks are not
removed by the Manage Supplier Invoice app when doing navigation with the
“Back” Button. Locks are removed automatically after 15 Minutes (as default,
see SAP Note 2721633 for details). Feature Request is submitted to SAP
(component MM-FIO-IV) to optimize this behavior.
Workaround: Retry posting (Submit) after the lock was removed.
75
10.3 VIM Supplier Self Service App
VIMI-19761 Supplier Self Service - option for last "X" days is not configurable
Do not configure the option for last "X" days fields in the Supplier Self Service.
VIMI-22163 Read only Company Code field should be greyed out
In Fiori Supplier Self Service registration page, the company code should be
greyed out to indicate its read only status.
10.4 VIM Invoice Approval App

VIMI-22217 Comment text entered in FIORI gets truncated compared with same text in
SAPGUI
Long comments entered in Fiori are truncated when compared with the same
text in SAP GUI.
VIMI-22232 Dump when clicking Approve: RFC error: Overflow when converting 256
Error is shown when trying to approve an invoice with more than 500 line items.
76
10.5 VIM Invoice Approval App – Bulk Mode
VIMI-22302 Error pop up is displayed when trying to approve the same invoice during revisit
to bulk mode
When user clicks on approve and cancels the approve dialog without giving any
comments. Again, enable bulk mode and select the same invoice for bulk
approve then the Error pop-up appears
VIMI-22513 Comments entered using Bulk Approval are not stored and they will not be
visible at the next level of approval.
77
11 Fixed issues
11.1 Fixed issues for 16.3.1
Document Processing (DP)
VIMI-17662
Turkish characters are not displayed correctly in PDF History log.
VIMI-18070
Unplanned costs were not being considered for tolerance check in the process type check “Tolerance
exceeded” (check function module /OPT/VIM_DETERMINE_PROC_406). The display of balance
traffic light in the indexing screen was not in sync with the exception.
VIMI-18357
The line item amount is not split correctly, when posting a PO invoice in online mode if the PO has
multiple account assignment and the amount distribution is set to “Distribution by Amount”.
VIMI-18692
Tolerance check now works as expected for purchase orders without GR based invoice verification.
The process type 406 (“Tolerance exceeded”) was not activating earlier for purchase orders that do
not require a goods receipt.
VIMI-18738
WBS element value is wrong or missing in the posted document after posting a Non-PO invoice using
BDC 42.
VIMI-18752
Material lock on table MBEW is not released after the item proposal call in VIM, which results in an
error when VIM attempts to post the invoice in background.
VIMI-18766
The logic of the "Mandatory check not required" check box in Process Option definition was not
working as expected. The mandatory fields check will be performed whenever a process option is
chosen while the DP process is in "Missing Mandatory Information" exception (or others listed in the
Z-constant 005/REQUIRED_PROC_TYPE). The check will be bypassed when the check box is
active.
VIMI-18850
Document is posted successfully in background even when the tax amount is provided incorrectly.
VIMI-18852
Text of withholding tax indicator (classic WHT) is wrong in the indexing screen.
VIMI-18902
Error message FF 818 ("Taxes by item is activated; consequently, transfer by item is mandatory”)
during the data validation when an external tax system is used.
VIMI-18907
78
Zero tax amount lines are deleted from BAPI tables during background NPO posting.
VIMI-18938
Entry of an invalid WBS element was causing an unexpected exit from DP dashboard after displaying
an error message.
VIMI-18946
The comments header for bypass business rules was stored incorrectly (duplicated header lines).
VIMI-18947
When an invoice is posted directly from MIRO, in some situations the document status is empty in the
table '/OPT/VIM_1HEAD' and in the indexing screen called for document display in VIM Analytics. At
the same time, VIM Analytics’ main output list displays the status correctly.
VIMI-18992
During the posting of a PO invoice in online mode, when the PO has multiple account assignment and
it has been previously fully invoiced, quantities are not distributed correctly and the PO history is not
updated correctly as well.
VIMI-19035
If the vendor number in a DP document differs from the vendor number used in the scheduling
agreement, that scheduling agreement was not considered in line item proposal.
VIMI-19040
“Ignore invoicing partner field” not available on indexing screen.
VIMI-19047
Net Amount field does not get recalculated when there are no line items in index screen and when
gross/tax amount is changed in basic data tab.
VIMI-19070
When there are multiple company codes for a PO invoice, the company code of the FI document
number stored in /OPT/VIM_2HEAD was chosen without respect to the company code of the MM
document. The correction will make sure that the FI document number refers to the same company
code.
VIMI-19071
The posting period validity check will now take into account invoice characteristics maintained for
posting date. (Specifically, whether or not to consider the current system date).
VIMI-19104
Unblocking of posted approval document is not possible in case of multiple vendor items with different
posting keys.
VIMI-19108
Discount amount is not updated in the DP document when its value is changed during online posting
of a non-PO invoice.
79
VIMI-19115
New Z-constant 005 / SHOW_IGNORE_IP introduced. If it is set, the field is available on indexing
screen (for PO based document types).
VIMI-19123
Background osting of NPO invoice fails if G/L account at line item level is non-taxable.
VIMI-19137
F4 Help for business place returns value of company code instead of business place.
VIMI-19141
“Ignore lines from External system" flag set in DP document type settings not working as expected.
The lines added by logic modules were being deleted too.
VIMI-19146
When posting a PO invoice in background, the amounts are distributed based on percentage instead
of amount based distribution.
VIMI-19161
Report /OPT/DR_BR_WAIT stores incorrect status in table/OPT/DT_BR_WAIT for some scenarios.
VIMI-19199
VAT amount showing incorrectly for archived FI documents that were posted through VIM.
VIMI-19238
In case a DP document that has currency without decimals like JPY, stops with the process type 110,
so that the proposal is displayed on the line items tab, the line item amount is displayed incorrectly. It
is 100 times less and also has a decimal point/comma.
VIMI-19243
VIM indexing screen document display mode, which is called from VIM Analytics, displays document
status “Blocked” for documents that are posted without any blocks.
VIMI-19245
DP workflow does not proceed to further steps after an invoice is sent to rescan.
VIMI-19256
On SAP ERP 6.0 EHP8, after entering IBAN in OTV popup from indexing screen and clicking Save, a
short dump occurs.
VIMI-19264
User entry in Permitted Payee field is being overwritten along with the bank detail fields, when only
one permitted payee has bank account details.
VIMI-19280
Column titles in the “Simulate rules” window are not completely translated.
VIMI-19299
Displaying documents with negative tax amounts results in a short dump. Such negative tax amounts
80
can be written into a DP document when synchronizing its values with a posted invoice.
Manual input of negative tax amounts will still not be allowed.
VIMI-19311
DP document type determination according to archive document type did not work in certain
configurations, for example for documents coming in through BC inbound.
VIMI-19316
In the DP indexing screen, payment terms text will be displayed based on the payment terms
conditions if there is no standard text available in table T052U.
VIMI-19322
Displayed balance is changing in the indexing screen when providing the tax rate at line item level
without the line item amount present.
VIMI-19326
Incorrect net amount shown in PDF History log.
VIMI-19338
When PO number is changed using single click entry, terms are not updating automatically.
VIMI-19340
When a custom module pool program is used in document type configuration, line item labels are not
displayed. The label sync function module can now be used for synchronizing the item labels for
custom screens too.
VIMI-19349
The transaction return code was not properly checked during process option execution.
VIMI-19350
Tax code is not determined based on tax rate.
VIMI-19356
Bypass buttons are not available in the indexing screen simulate/bypass popup.
VIMI-19360
Validations added for fields Supplying Country, Business Place, and Section Code in the indexing
screen.
VIMI-19363
Background posting of a PO invoice fails when the delivery note belongs to multiple invoicing parties.
VIMI-19404
Cursor focus is not kept on the selected field when scrolling down in the withholding tax table control.
VIMI-19451
Tolerance check function /OPT/VIM_DETERMINE_PROC_406 (process type 406 - Tolerance
Exceeded) does not consider the amount entered in the G/L tab.
VIMI-19459
81
Tolerance check business rule fails for PO invoice with Indian GST, if a G/L line also exists in the
document.
VIMI-19462
Background posting of a PO invoice with Indian GST fails with balance error.
VIMI-19463
Tax is calculated for a line item of a NPO invoice, while the G/L account maintained in the line is not
tax relevant.
VIMI-19464
Background posting of a PO invoice with Indian GST fails.
VIMI-19465
Tax code, tax jurisdiction code, and company code are not populated automatically after using coding
upload.
VIMI-19466
Balance is calculated incorrectly in indexing screen for a PO invoice, if G/L lines exist in the
document.
VIMI-19469
When non-automatic tax calculation is used for credit memos, calculated balance is incorrect in DP
indexing screen.
VIMI-19484
Missing Czech translations in requester entry screen and on plug-in buttons.
VIMI-19570
When DP documents are used to park Non-PO invoices, in addition to the DP document that were
used to create a parked invoice, one more DP document is being created, of the DP document type
set up to the dummy DP documents (Z-constant 005 / DOCTYPE_NPO).
VIMI-19577
You post Non-PO documents with non-deductible tax. Line item amounts are entered as gross
amounts in DP document. In the posted SAP document, discount base amount is not correct.
VIMI-19598
The logic to handle line item fields in /OPT/VIM_OCR_PREPROCESS_NEW (described in Scenario
Guide 10.1 “Adding new fields”) was changed in SP6. The change is reverted due to side effects –
some line item fields were being cleared.
VIMI-19605
Invoice status in the table /opt/vim_1head is set to “Posted” while the invoice is actually posted with
blocks. At the same time, VIM Analytics shows correct status.
VIMI-19654
Program /OPT/CR_RERUN_RULES_JOBS triggers events after the number of retry limit is reached.
82
VIMI-19669
Entering a wrong WBS element causes a short dump when using single click entry.
VIMI-19670
Tax base amount is incorrect in NPO background posting when there are tax lines without G/L
account.
VIMI-19687
Duplicate check executes only if at least one of the fields assigned to the duplicate check group is
populated in the indexing screen.
VIMI-19720
Invoice category is re-determined incorrectly after business rules run.
VIMI-19723
Deleted PO items are present in line item proposal when a DP document refers multiple POs.
VIMI-19727
Posting of an NPO invoice with Indian GST fails in background when the G/L account assigned to tax
code in old tax code configuration is blocked and tax amount is posted to incorrect G/L account.
VIMI-19730
Total tax amount is shown with decimals for zero decimal currencies.
VIMI-19736
For credit memo and subsequent credit documents, net amount value is negative in DP indexing
screen.
VIMI-19746
If “Plants abroad” functionality is active, when one switches between basic data tab and tax tab, a
popup to enter reporting country is displayed.
VIMI-19796
While posting or approving an invoice, the error message FF 707 (“Tax entered incorrect (code XX,
amount YY), correct ZZ”) is shown, when an external tax system is used and automatic tax calculation
is on.
VIMI-19797
For “payment type” withholding tax type, the withholding tax amount was not available in the indexing
screen and in posting. A new Z-constant 005 / WHT_PAY_AMT has been introduced.
Constant Value = X - indicates that the withholding tax amount should be set for indexing screen and
posting, for “payment type” withholding tax type.
Constant Value empty or constant missing - indicates that the withholding tax amount should not be
set for indexing and posting for “payment type” withholding tax type.
VIMI-19804
83
Withholding tax amount is calculated based on gross amount instead of net amount when type of
withholding tax base amount is set to "Modified Net amount".
VIMI-19823
While posting or approving a cross company code NPO invoice, the error message "Specify Tax
Jurisdiction code" is shown when the header company code is set for tax jurisdictions and the item
company code is not.
VIMI-19841
DP document display (during processing or in a popup from VIM Analytics) aborts with a short dump
when opening an invoice with extremely high amounts.
VIMI-19844
Business rule “Vendor mismatch” for PO invoice is raised when a different business partner is
maintained as Invoicing Party in the PO.
VIMI-19856
Changes of Delivery note number (LFSNR) are not recorded in DP document change documents.
VIMI-19863
When a document have many line items, some of them will not be displayed because of table
scrolling. DP indexing screen was not alerting the user if in those line items, a mandatory field is not
populated.
VIMI-19865
The baseline date determination does not retain the value of baseline date derived from custom logic
function when “Keep default” attribute is set in country specific Characteristic configuration.
VIMI-19867
Impossible to post a PO invoice when delivery note used in a DP document is not unique and it refers
also to an unrelated PO, whose company code posting period is not open for the used posting date.
VIMI-19868
Payment method text remains in the DP indexing screen even when no payment method is entered
anymore.
VIMI-19879
Exception "Wait for GR" is triggered for invoice with non GR-IV item.
VIMI-19882
The field HSN_CODE (Indian GST) is not passed into MIRO when posting online.
VIMI-19912
When using “Return to Vendor” function, change documents for DP document are not created.
VIMI-19922
Mass update for payment block with transaction FBL1N is not working for PO related invoices
because of a conflict with VIM logic called in this case.
84
VIMI-19943
Entering data in profitability segment popup results in a short dump.
VIMI-19951
Tax calculation is incorrect when a tax code has several tax types (lines) maintained.
VIMI-19952
Payment terms are not synchronized in DP document with SAP document if payment terms are
changed during the posting.
VIMI-19955
GST Partner field is not changed based on the PO number after a change of the PO number (Indian
GST).
VIMI-19979
The IBAN for a vendor can be overwritten with another IBAN from VIM indexing screen. There is no
check against the IBAN and the corresponding bank details which leads to wrong IBAN entry in the
vendor master.
VIMI-19983
IBAN for one time vendors (OTV) is always calculated and written into the table TIBAN even when
IBAN is not filled/generated in the OTV popup.
VIMI-19993
Background parking for one time vendor failed with BDC ID 14 and 25.
VIMI-19997
When business rule simulation is called from VIM Analytics document display, process type 150
(Approval required) may be shown as active, even when an invoice is already approved.
VIMI-20041
Auto posting of a PO invoice fails when the invoice contains a freight line item.
VIMI-20110
The process type “Service entry required” is not triggered if there are no line items in a DP document.
VIMI-20812
Tax Code Search in indexing screen is not working.
VIMI-20056
The posting logic (BDC 2200) is now allowing background posting in the following cases:
• Multi Account Assignment with Partial Invoices
• Multi Account Assignment with Service POs
Document Processing (DP) – Logic Modules

VIMI-19106
Remit to address data was incorrectly being overwritten with the vendor address data in the logic
module G_HEAD_007.
85
VIMI-19391
SAP document type is not determined for DP PO document type. When there is no PO number in the
invoice and an open single line PO for vendor/company code with the same amount is found in logic
module processing, DP document type is determined but SAP document type is not correct.
VIMI-19926
Content of the Indian GST field “Assessable value” is not transferred from VIM to MIRO screen during
online posting with BDC ID 200.
VIMI-19934
Return to Vendor aborts with a short dump if a one-time vendor is used and the DP document also
has the OTV tax number entered.
Invoice Approvals
VIMI-18772
The existing message shown when some approval process configuration is missing, “No chart of
authority settings maintained”, is replaced with the message "No valid user found in COA. Please
verify COA settings".
VIMI-18788
Unable to save Deal ID in Profitability Segment.
VIMI-18809
It was possible to have multiple approval workflows started in some specific scenario.
VIMI-18883
Reassignment Tool (transaction code /ORS/UMREASSIGNED) does not work correctly for Portal
users who do not have a valid SAP user ID.
VIMI-18937
Changes of invoice data are not saved in some situations for NPO invoices, although a “success”
message is shown.
VIMI-18981
Change documents for type 'I' are not visible in the COA online report.
VIMI-19164
Additional validations on entry of SAP user ID when adding new users in COA maintenance
transaction.
VIMI-19180
In the COA Upload report (full mode), change logs for user map are written in test mode.
VIMI-19189
The user preferred language was not read correctly from COA user preferences.
86
VIMI-19257
Invoice lock is not released when the "No Approvable line items” message is shown in the approval
screen when executing a work item. The lock is cleared now when the error is triggered.
VIMI-19272
If Special Handling instructions are specified for an invoice, it should not be auto posted, but in some
situations, invoice was still being posted. The check on “Auto Post” flag has been enhanced to check
for Special Handling instructions.
VIMI-19325
Rejection comments entered by substitute contained the original user name instead of substitute
name in VIM Analytics report 'History' tab and 'Comments' tab.
VIMI-19327
You are not able to override the next proposed approver when an invoice is being forwarded
(remaining at the same level), if the approval flow is set to parallel approval.
VIMI-19337
Incorrect search help for the field Business entity.
VIMI-19342
It is possible to approve an invoice that does not have any line items at the coder or requester level by
deleting the automatically proposed dummy line. Note: a similar problem was solved with VIM 7.5
SP6, fix VIMI-18148, for the case when invoice has some lines and they are being deleted.
VIMI-19374
Saving or approving an invoice with extremely high amounts (100 billion) terminates with a short
dump.
VIMI-19425
If WBS element is configured to be used in COA, in some cases the COA was not interpreted
correctly due to wrong WBS element value conversion..
VIMI-19440
“HSN Code” column label is missing in approval screen.
VIMI-19571
When an invoice is rejected and the previous approver (or coder) is not valid anymore, the workflow
was still being sent to the invalid agent. Now the work item will be sent to a fall back user based on
the fall back user setting configured for the respective AFS ID in the approval process configuration.
VIMI-19672
COA maintenance transaction does not display some users even though all authorizations are set up
properly. Users whose SAP user ID and internal user ID are not the same are not displayed.
VIMI-19688
Original DP invoice document getting replaced by attachment in approval screen.
VIMI-19824
87
Search help for SUB_NUMBER in approval screen has wrong output.
VIMI-19988
"Delete attachment" button in approval dashboard does not work for PO invoices.
VIMI-20115
“Delete attachment” was missing proper validation with relevant message in approval screen.
VIMI-20150
Double clicking on GL account column opens up attachment list incorrectly.
VIMI-20224
Next approver is not properly determined when header based approval is used.
Web Approval Portal

VIMI-18761
Error with invoice approval when trying to approve an invoice for a substitute using bulk approval in
the Approval Portal. Error appears for the invoice that was open in the portal during bulk approval.
VIMI-18839
Performance improvements for search help for field Internal Order. The search help will be now
fetching the values based on the parameter 'Max number of hits' configured in the portal.
VIMI-18920
Performance improvements for reading the processed invoice history in Approval Portal.
VIMI-18923
In some situations, approvers are required to approve already finally approved line items.
VIMI-18924
WBS element values are displayed in internal format in Approval Portal.
VIMI-19121
Approver override search does not find any alternative approvers if the invoice is currently at the
coder or requester level.
VIMI-19344
Search help request for invoice fields does not deliver any results.
VIMI-19361
Inbox does not show the invoices of other users if passive substitution based on SAP business
workflow is used.
VIMI-19457
Line items are not displayed in PO approval screen.
VIMI-19752
88
Portal Administration page does not save host white list.
VIMI-19791
When clicking a custom button results in a Warning, Info, or Success message, such messages are
not displayed.
VIMI-19833
'Export Coding' button in Approval Portal not working.
VIMI-19893
When DP document posting date determination is set to “Current date”, the invoice detail page might
display not the current date but the date saved in the document during earlier processing.
VIMI-19903
It was not possible to update the InvoiceCfg portal configuration file because it was being constantly
locked by the running application.
VIMI-19914
Decimal format is incorrect in the Approval Portal.
VIMI-20313
WEB Approval Portal - Two sessions in one browser - Coding overwrites invoice in history.
When multi tabs are opened in one browser, the data opened in one tab is overwriting the data in
another tab. To avoid this, now portal is not supporting multi tabs in a browser.
Mobile Approval Portal

VIMI-19417
Approval workflow runs into error after performing approval on a mobile device, but steps are working
with SAPGUI Approval.
VIMI-20135
When rejecting an invoice, the message “Invoice not found in the stack” appears.
Fiori Approve Invoices app

VIMI-19163
Parked invoices in coding step are not available in Fiori Approval app.
VIMI-19263
“Back” button missing on invoice image for Apple devices.
Input Channels
VIMI-19103
Incorrect mapping of amounts when different input channels are used in the same system.
Previously it was possible to set only one field name where the currency code will be contained for
external interfaces. With ICC having the field name “InvoiceCurrency” fixed for most of applications,
there was a conflict with other mappings using other field names. The problem can now be solved by
maintaining several possible currency fields in the Z-constant 005 / OCR_CURRENCY_FIELD. Field
names must be separated with commas without spaces. Example: InvoiceCurrency,WAERS
89
VIMI-19110, VIMI-19423
Inconsistent / wrong selection of SAP document type by business rules and logic modules.
The enhanced mapping for SAP document type (field BLART) will not be done any more. The
determination will only be done by the logic modules.
VIMI-19455
The enhanced mapping for PO numbers in items was not correct. For a document coming in with
multiple PO numbers on header level, the items without PO number were populated with the first PO
number.
VIMI-19501
The enhanced mapping for PO item numbers in the secure line item number scenario was improved.
As the scenario only works for invoices with exactly one PO number, all the PO numbers are checked
for validity and vendor to filter out invalid PO numbers.
VIMI-19512
The enhanced mapping for unit of measure in the secure line item number scenario was improved.
The UOM will be added from the PO item, if it was not found by recognition, if order unit and price unit
are equal, if there are no factors involved, and if the unit price matches the recognition result or the
recognition amount divided by recognition quantity.
VIMI-19514
Additional lines in invoices with lines using the secure/insecure line item number will be removed, if
there is a match between the sum of the line item amounts and the net amount in the invoice header.
VIMI-19660
ICC download job does not consider India GST fields.
Invoice Exception
VIMI-18513
The "Show Detail pane" button was not displayed in the blocked workflow dashboard when logged in
in German, because the translation was not maintained for the button text.
VIM Notifications
VIMI-18808
The reminder report does not take invoices into account when inbox days count is not reached yet,
but “Days before Payment Due” has been reached.
VIMI-19145
When a language for reminders is entered in the VIM notifications customizing transaction
/OPT/VIM_8AX50 and then ENTER is pressed, the entered reminder language is cleared.
VIMI-19287
When VIM notifications (for general and approval steps) are set to HTML, the HTML tags eventually
used in standard texts are misinterpreted, resulting in wrong formatting. To distinguish between plain
text and HTML-contained input in standard texts used for notifications, a new constant value 'HTM1'
90
has been introduced for the existing Z-constant 'REM_MAIL_DOCTYPE' in the table
/PTGWFI/Z_CONST.
• If the new constant value 'HTM1' is set, the standard texts will be considered to contain HTML
tags, and it won’t be formatted additionally.
• If the existing constant value 'HTM' is set, the standard texts will be considered to contain
only plain text. Eventually present HTML format tags will be displayed as text in the output.
VIMI-19735
Runtime error "TSV_NEW_PAGE_ALLOC_FAILED" is triggered while executing the notifications
program.
VIMI-19967
Reminder notifications are not sent in the user preferred language for the portal user, in case there
are several recipients. They are instead sent in the language of the first user in the group.
VIM Analytics report and VAN Liability report

VIMI-17731
Scheduling agreement cannot be opened from VIM Analytics by clicking the PO number.
VIMI-19004
VAN displays a wrong FI document when there are multiple company codes for a PO invoice. The
status information (posted/blocked) can be wrong as well.
VIMI-19013
In VAN report, documents with status “Rescan Completed” were incorrectly shown as open invoices.
VIMI-19077
Document status selection with statuses like SAP_* was not working properly in VIM Analytics.
VIMI-19232
The field “Business place” is always displayed in editable mode, even in the read-only document
display popup.
VIMI-19284
VIM Analytics report shows asset document as accounting document for PO posted invoice.
VIMI-19317
VIM Analytics does not show “Start On Date” even if the value had to and could be calculated.
VIMI-19392
Obsolete/Rescan reason text header is duplicated in VAN report.
VIMI-19530
Not possible to display parked SAP document from VIM Analytics (or VIM Workplace).
VIMI-19696
“Paid at” time is incorrect shown in VAN report due to incorrect time zone conversion.
91
VIMI-19703
Paid on/Paid at fields are still displayed in VIM Analytics after the clearing document has been
reversed and the invoice cancelled.
VIMI-19712
Long run times and time out errors when executing KPI Collection report on a MaxDB system.
VIMI-19815
Paid on/Paid at fields are still displayed in VIM Analytics after the payment has been reversed and the
invoice cancelled.
VIMI-19944
When the option “Open Invoices” is selected in the selection screen, VIM Analytics still shows blocked
invoices with completed workflows.
VIMI-19947
Cycle time is wrong (it continues to increase) for documents in status ‘Image discarded’ and ‘OCR
validation rejected’.
VIMI-20093
Filtering invoices of a single vendor in VIM Analytics result list (ALV filter on Vendor Name) did not
provide an expected result.
Central Reporting and other reports

VIMI-18329
Performance improvements in Collection Report.
VIMI-19498
The Productivity Report stops with an error popup without a meaningful text, when selection ‘Agent’ is
used and the ‘To Date’ is left empty.
VIMI-19403, VIMI-19996
Central reporting reports stop with an error "Data has to be converted".
VIMI-19572
KPA report showing incorrect results in case users have authorizations only on certain company
codes.
VIM Workplace
VIMI-17894
Invoices approved using the Approval Portal or Fiori app are not available in VIM Workplace
“Completed” tab. Only invoices approved from SAP GUI are listed there.
VIMI-18605
92
After using the “Send back” option in header level workflow, the new work items created for line level
workflows are not visible in VIM Workplace.
VIMI-18675
In VIM Workplace, clicking "Cancel" in the comments popup, while performing a bulk action, does not
stop the action but allows the execution to proceed.
VIMI-19792
When performing bulk refer of DP document, the comments pop up is not shown and the next step
role is not assigned.
VIMI-19779
When accessing VIM Workplace from Fiori Launchpad (set up as a Fiori tile), the initial access
attempt results in a short dump.
VIMI-20342
When using Bulk Action for “Approve/Reject” from VIM Workplace, a short dump occurred.
Supplier Self Service

VIMI-18734
Supplier Self Service collection program stops with a short dump.
VIMI-19055
The search function of Supplier Self Service portal is not handling characters beyond standard Latin
character set (like accented characters found in Portuguese).
VIMI-19113
PO document related information is missing or showing incorrectly in the Supplier Self Service portal.
VIMI-19285
Missing Supplier Self Service configuration causes incorrect invoice status display.
VIMI-19439
Payment details and PO details are missing in Supplier Self Service portal.
VIMI-19593
“Paid Date” field was showing the document posting date, and is now replaced by clearing date.
Enter Cost Assignment Fiori app

VIMI-20591
If profit center was automatically filled during accounts payable coding, the invoice has more than one
cost object type filled per line and is considered complex. It does not turn up in the Enter Cost
Assignment app, but in the Approve Invoices app. This has been changed: it will turn up in the Enter
Cost Assignment app provided there is no other reason for being complex.
VIMI-20655
93
If credit/debit flag is missing in line item, the invoice is considered complex. It does not turn up in the
Enter Cost Assignment app, but in the Approve Invoices app. This has been changed: it will turn up in
the Enter Cost Assignment app provided there is no other reason for being complex.
VIMI-20819
Removal of GL account in Fiori app does not work. Only change of GL account.
Confirm Quantity and Price Fiori app

VIMI-20079
Confirm Quantity and Price Fiori App: The following buttons do not work for the inbox: Sort, Search,
and Filter.
Installation and Upgrade

VIMI-20341
Potential issue during upgrades from VIM 7.5 to VIM 16.3: Installation stops with generation error:
Program /OPT/SAPLVIM_FGIIC, Include /OPT/LVIM_FGIICF01.
Update from 7.5 should be done directly to VIM 16.3 SP1.
11.2 Fixed issues for 16.3.2

Document Processing (DP)
VIMI-19577
Discount base amount is not correct in Non-PO invoices with non-deductible tax, if line item amounts
are entered as gross amounts in DP document.
VIMI-19667
Material description is not being populated in the indexing screen.
VIMI-19670
Tax base amount is incorrect in NPO background posting when there are tax lines without G/L
account.
VIMI-20080
Earmarked funds functionality is not working as expected for NPO invoices. It is not verified whether
the earmarked fund is changeable.
VIMI-20083
Transaction type field (VORGANG) is not set in the DP documents created for invoices posted
directly in the MIRO transaction.
VIMI-20114
Comments from bypassing a rule are stored incorrectly after executing a custom process option. This
leads to errors when trying to open the document log in the Unified Dashboard.
VIMI-20117
94
Unable to post a PO invoice if G/L account lines are entered, and the account used is a tax G/L
account.
VIMI-20152
PO invoice line items with zero amount are not transferred into MIRO transaction during online
posting.
VIMI-20194
An error is triggered when trying to display business partner from DP indexing screen because of
hardcoded value (FI/MM Vendor BP Roles). Due to this, it is not possible to navigate into transaction
'BP' based on the custom roles configured for the user.
In order to address the issue, a new customer exit has been introduced, which can be used the
following way:
1) A new Z constant (Product code = '005', Constant = 'FILL_MM_FI_BPROLE' ) is introduced to

allow to configure a custom function module for filling MM/FI BP Role while navigating to
transaction 'BP'.
2) The template function module /OPT/VIM_TEMPLATE_FILL_BP_ROLE can be used for
creating a custom function module to fill MM/FI BP Roles."
VIMI-20198
VAT number was not being transferred to MIRO in foreground posting for one time vendor.
VIMI-20237
Withholding tax amount for payment posting types is deleted after posting. The amount is correctly
transferred to posting but not found in the indexing screen after posting.
VIMI-20293
The scroll buttons on the table control in the line item screen were not functional.
VIMI-20308
The tolerance check business rule triggers erroneously for Credit memos.
VIMI-20379
Payment terms text in the indexing screen will be displayed based on the additional conditions like
'Fixed date' and 'Additional months', when 'Percentage' and 'No. of days' are not maintained.
VIMI-20390
The process determination check popup is triggered erroneously even when a process option is
chosen without changing the data.
VIMI-20437, VIMI-20438
Unable to post the service-based PO invoice in background if the SR-IV flag is enabled, GR-IV flag is
disabled and goods receipt flag is disabled.
VIMI-20457
95
Tax is calculated incorrectly for a PO invoice with Indian GST when “Auto Calculate Tax” flag is
enabled.
VIMI-20469
Project field PROJK is not cleared when clearing the field PS_POSID in the DP indexing screen.
VIMI-20482
Search help missing for HSN/SAC code in indexing and approval screens.
VIMI-20492
The field "Assessable value" (Customs_val) in the DP Indexing line items tab should be enabled only
when the condition type is related to import procurement.
VIMI-20518
Place of supply is not updated when the business place is modified in the DP Indexing screen.
VIMI-20520
Tax is calculated incorrectly in case of GST PO invoices when freight condition is configured with
subtotals.
VIMI-20535
Withholding tax base amount and tax amount are calculated incorrectly for NPO invoices with Indian
GST.
VIMI-20539
When the "Calculate tax on net" is disabled in DP document type configuration, the error message
"FI-CO Interface: Line item entered several times" can be shown in the background posting log or
when using the “Validate” button in the indexing screen.
VIMI-20540
When posting the down payment document by using FB01 transaction, the gross amount is getting
doubled.
VIMI-20559
Group indicator and condition record number are not getting updated for NPO invoice with Indian
GST.
VIMI-20575
Place of supply is not getting populated by default from the business place in case of GST invoice
VIMI-20590
Price per unit is not considered while calculating the tolerance for line items in the Business Rule
"Tolerance Exceeded (PO)".
VIMI-20605
When a DP document has an invalid company code (for example wrong company code populated
from ICC/BCC), it cannot be displayed in indexing screen.
96
VIMI-20663
Withholding tax amount and base amount are calculated incorrectly in case of NPO invoices with
Indian GST.
VIMI-20682
When using the upload coding functionality, after coding is uploaded and saved, values in some
columns are not saved with default values (e.g. company code and debit/credit indicator).
VIMI-20734
During PO Background posting, the field “Commitment item” (FIPOS) is not populated and the error
message from the BAPI log (“No commitment item entered in item”, message FI 311) is shown.
VIMI-20742
Balance is calculated incorrectly in PO invoice when "tax base on net" and "discount base is net
value" check boxes are enabled in company code configuration.
VIMI-20772
For PO based invoices with zero percent withholding tax rate, the withholding tax amount calculation
is wrong.
VIMI-20776
Account assignment in a PO invoice is done incorrectly when posting a partial invoice when the partial
invoice distribution is set to “progressive fill-up basis” (one after another).
VIMI-20785
Document status is set incorrectly for Non-PO documents that are cancelled during or after posted
approval process.
VIMI-20812
Tax code drop down in the indexing screen does not show possible values.
VIMI-20817
Material locks are not cleared after clicking the "Match All" button.
VIMI-20821
PO proposal doesn't return any values when trying to fetch planned delivery costs if PO has multiple
condition types with different vendors.
VIMI-20836
PO invoice amounts are posted incorrectly, when split multiple account assignment is used.
VIMI-20889
The reference number (field BKREF) is not populated/moved to FI document when using one time
vendor.
VIMI-20897
97
In the indexing screen, the flag for Subsequent Debit/Credit in the PO reference tab is not properly
handled, when PO proposal area is switched between shown and hidden.
VIMI-20936
Attachment added in DP indexing screen by substitute can't be deleted by original approver.
VIMI-20979
The “Activity” (VORNR) field is not being propagated from the VIM proposal Functionality into the
indexing screen.
VIMI-20988
The error “Document type not defined” is shown in the indexing screen for a document with
withholding tax.
VIMI-21018
House Bank search help doesn't show results filtered by company code.
VIMI-21039
Fields specific for PO invoice are validated for Non-PO invoices.
VIMI-21048
A document declared to be a non-duplicate returns with “Suspected duplicate” exception.
VIMI-21053
Exchange rate is incorrectly calculated when work items are executed in the same session and the
tax codes are mapped to different reporting countries.
VIMI-21055
Wrong exception ‘Manual check required’ is triggered when doing partial invoice for a service PO,
where the service acceptance (SES) is done once for full amount of PO line.
VIMI-21069
Bank information received using external data mapping needs to be replaced by the bank information
from vendor master if the IBAN is different from vendor master.
VIMI-21070
Balance is calculated incorrectly for a PO invoice when the G/L account maintained in the G/L tab is
not tax relevant.
VIMI-21080
The same tax code is displayed twice in the dropdown on VIM indexing screen.
VIMI-21088
For credit memos, withholding tax amounts are negative after the document is posted.
VIMI-21089
Baseline date gets cached and copied from previous DP documents.
98
VIMI-21113
Withholding tax amount field in DP indexing screen could be open for input while it had to be read
only as per SAP withholding tax configuration.
VIMI-21116
Corrupt value received using external data mapping for the field Taxrate1 causes a short dump in the
class /OPT/CL_VIM_DOC_PROCESSOR, method UPDATE.
VIMI-21141
Tax is calculated incorrectly for PO invoice when tax code is configured with multiple tax rates.
VIMI-21168
Fields “Correction item number” and “Real estate option rate” were not available in VIM item and
approval screens, thus preventing correct posting of some documents.
VIMI-21233
Impossible to maintain a label for the field XREF2 at line item level.
VIMI-21264
When an invoice is posted externally through MIRO transaction, the baseline date field is not
transferred back into the corresponding DP document.
VIMI-21267
Database locks for the /OPT/VIM_HD_PO are generated at table level instead of locking individual
entries.
VIMI-21268
Validation errors are shown for a correct value of reference document (GR) field.
VIMI-21285
Short dump CONV_EXIT_FIELD_TOO_SHORT is triggered when using the upload coding
functionality for the DP document.
VIMI-21294
Wrong search helps assigned for RE-FX related fields in the DP document. Using the F4 Functionality
returns irrelevant results.
VIMI-21302
When the bank information fields are hidden by configuration, the “Display Bank” button is still
available on the indexing screen.
VIMI-21332
The long text of the message /OPT/VIM_701 085 mentioned the constant 005
LINE_ITEM_COUNT_TIME, while the constant 005 NR_ALLOWED_LINEITEMS is actually used in
the code.
99
VIMI-21349
'Approval History' tab is not displaying the 'DP process Step' comments (for actions like bypass
business rule, confirm non-duplicate) in the indexing screen detail pane.
VIMI-21384
The field HKTID (Account ID) field is not passed into BAPI while posting.
VIMI-21382
Unspecific messages were shown in the error log of the indexing screen when the exception "Missing
mandatory information" was triggered. The messages will now display the relevant field names.
VIMI-21416
Withholding tax base amounts are calculated incorrectly when calculated based on net amount.
VIMI-21417
Attachments of type .XLSX are corrupted in emails sent using the option “Return to Vendor”.
VIMI-21444
The GL account and Cost center field are not transferred to MIRO during online posting through VIM.
VIMI-21475
When there are multiple freight based line items in an invoice and the invoice refers to multiple POs,
invoices cannot be posted in the background through VIM.
VIMI-21496
When the upload coding option is deactivated in the indexing screen, the button is still displayed.
VIMI-21524
When a cross company FI document is posted through VIM, the discount base amount is not updated
in the line item of the FI document.
VIMI-21533
After posting an invoice with a one time vendor, vendor details entered in the DP document are
overwritten with dummy data from one time vendor master.
VIMI-21538
The tolerance check function module does not consider the price unit when determining the tolerance
limit for a line item.
VIMI-21558
When using the function module /OPT/VIM_START_DOC_PROCESS_EXT to create a DP document
from external data, the purchase order item number (EBELP) is not transferred into the DP document.
VIMI-21565
"Tolerance exceeded" exception raised incorrectly for service based and limit PO lines having no
quantity.
100
VIMI-21587
Incorrect screen data handling related to earmarked funds for NPO invoices.
VIMI-21589
Move Down and Move Up buttons not working as expected in the line item tab, PO reference area.
VIMI-21598
When using WebGUI to upload coding, it is impossible to upload Excel files. Since WebGUI does not
support Excel integration, VIM now allows to use CSV files instead.
VIMI-21603
Error M8 416 when posting blanket PO using new BDC 2200
VIMI-21628
Baseline date determination is overridden by SAP Logic when the ”Keep default value” check box is
activated for the characteristic in the Characteristic specific attributes node in VIM customizing.
VIMI-21639
The duplicate check partially ignores invoices that have been posted outside of VIM.
VIMI-21640
BDCID 2200 does not work when using scheduling agreements instead of Purchase Orders.
VIMI-21662
Bank information is not transferred from one time vendor data popup back into the indexing screen.
VIMI-21691
Return to vendor Email address length is extended to 241 characters from 80.
VIMI-21733
When the baseline date setting is set to "Manual Entry" in the indexing screen, the due date field is
not updated upon update of the baseline date.
VIMI-21770
When changing the vendor number in the indexing screen to a deleted/blocked vendor, and then
changing it again to a valid vendor, the vendor address is not refreshed on the screen.
VIMI-21841
VIM credit memo is showing negative withholding tax base amount for VAT based withholding tax.
VIMI-21872
Line items data is cleared after entering it for downpayment document.
VIMI-22005
Archived document not assigned to posted PO invoice BUS2081, when document is posted with the
process option 2100 "Post Invoice (MIR4)".
101
VIMI-22007
VIM 16.3 Missing process options 2000, 2012 and 2040 in Process Type 300 Down payment.
Document Processing (DP) – Logic Modules

VIMI-19767
When performing PO invoice matching against GRs, VIM was picking already invoiced items, while it
had to use open ones.
VIMI-20146
The purchase order price unit is not considered when determining the PO invoice item quantity.
VIMI-21296
The tax Jurisdiction code is not automatically picked from the PO when logical modules are executed
to update the DP Document.
VIMI-21303
the expense type is not getting determined when the document type is relevant for down payments.
Invoice Approvals
VIMI-17796
In posted approvals, balance is shown incorrectly and the balance is equals exactly to the tax amount.
VIMI-19307
After the upgrade to VIM 7.5 SP4 you can no longer open invoices, in SAPGUI or in Approval Portal,
which do not have any approvable lines and are at the approver level (level 2 and higher).
NOTE: The earlier change to prevent opening an invoice without approvable lines was implemented
in VIM 7.5 SP4 to accommodate the requirements of some customer projects. The new correction
makes the check for approvable lines configurable. By default, the check will no longer be performed.
The configuration needed to enable it is described later in this document.
VIMI-19988, VIMI-20613
"Delete attachment" button in approval dashboard doesn't work for PO invoices.
VIMI-20378
Search help for Settlement unit returns wrong value in approval screen.
VIMI-20517
Manual exchange rate is not considered when calculating approval limit.
VIMI-20621
Changing substitute "To date" for a substitute creates two entries in transaction /ORS/MAIN_SUBS.
102
VIMI-20879
Tax code dropdown is not showing any tax available codes in approval screen.
VIMI-20911
An error message is shown when opening profitability segment popup for profitability segment data
that has already been saved.
VIMI-20973
Search help for G/L is not consistent between DP indexing screen and Approval screen.
VIMI-21009
Transaction /ORS/PROCBYME_ADMIN does not find PO work items when using filtering based on
company code.
VIMI-21052
Short dump in the approval screen when trying to view the invoice image.
VIMI-21085
When deleting an attachment from GUI you get an error "Not able to Delete the File due to Archiving
error". The attachment is not actually deleted but some related data becomes inconsistent and the
attachment is not shown anymore in the attachment list popup.
VIMI-21158
Some data at line item level (package number, PackNo) for a PO invoice is lost after invoice approval
process.
VIMI-21166
Reassignment utility (transaction /ORS/UMREASSIGNED) is not performing company code based
authorization check at all times.
VIMI-21182
In case of parallel approval, some invoice items can be bulk approved. If another user approves some
remaining lines, this action is wrongly shown at later steps as if this user was acting as a substitute.
VIMI-21298
Check for approver FI tolerance group is missing.
VIMI-21300
Label for the field "Property number” (PROPERTY_NUMBER / SGRNR) is missing in the approval
screen.
VIMI-21329
HSN_SAC field is not available in PO invoice Approval Screen for invoices with Indian GST.
VIMI-21333
CUSTOMS_VAL field is not available in PO invoice Approval Screen for invoices with Indian GST.
103
VIMI-21379
Label is missing for the "HSN/SAC code" field in approval dashboard for Non-PO invoices.
VIMI-21462
Payment term text is not visible in the NPO approval screen.
VIMI-21479
Entering wrong WBS element during coding in Web Approval Portal or in Fiori app may result into
wrong data being saved without validation. This may also lead to short dumps when opening such
document later in VIM Analytics or DP indexing screen.
VIMI-21523
Unit conversion is not performed in baseline coding mapping configuration for PO invoices. A wrong
field is being considered in the code to determine the unit.
VIMI-21546
When an approver's substitute starts an inquiry, it is incorrectly logged in the system. The log
indicates that the inquiry was sent by the original approver.
VIMI-21664
An error "Master record for commitment item /XXXXXXXX does not exist" is triggered when trying to
approve a Non-PO invoice. This error is not encountered when the same data is posted via FB60.
VIMI-21730
In case COA authorization checks are used, the COA maintenance transaction can delete some
entries for which the user is not authorized.
VIMI-21746
When the tax base amount field has been enabled in the invoice approval screen, the description/field
label is not visible.
Web Approval Portal

VIMI-20356
When uploading the attachments in Approval Portal with the backend running S/4 HANA 1610,
documents are not getting archived or the content is corrupted.
VIMI-20434
WBS search help for portal does not have the same results as in SAPGUI.
VIMI-20712
Duplicate DP Comments are seen in the approval portal when rule bypass comments are added.
VIMI-21014
Error in next approver determination when items are copied in cost assignment.
VIMI-21796
104
When performing a history search from the approval portal based on WBS element, the search does
not return the full list of documents.
VIMI-20313
When multiple tabs are opened in one browser, the data opened in one tab is overwriting the data in
another tab. To avoid this, now portal is not supporting multi tabs in a browser.
VIMI-20818
Hungarian translation is too long for some labels, resulting in overlapping text.
VIMI-20907
Attachment list is not properly displayed with the screen resolution set to 1280x800.
VIMI-21568
Thousands separator missing for the field “Tax base amount”.
VIMI-21790
Decimal notations for amount fields are wrong for some currencies.
VIMI-21420
Field values for the field “Settlement date” cannot be cleared.
Fiori Approve Invoices app

VIMI-20579
When an invoice is approved from Fiori Approve Invoices app, the approval log shows the action as
"Data entered and invoice approved" instead of "Invoice Approved".
VIMI-20532
Link in notification E-mail to Fiori Approve Invoices app does not work because of additional space
character in the generated URL.
VIMI-21463
Short dump GETWA_NOT_ASSIGNED in the program /OTX/PS03_CL_DATA_HANDLER_WEB=CP
is generated in the backend when approving in from the Fiori app.
VIMI-21645
Invoice gross amount is displayed multiplied by 100.
VIMI-21755
Invoice image not shown when using the approval app on a mobile device.
Fiori Enter Cost Assignment app
VIMI-20774
When invoice data correspond to an existing non-generic template with one line only and WBS
element is filled, the invoice is not displayed with the correct template name.
VIMI-20819
G/L account value can be changed but cannot be completely cleared.
105
VIMI-20799 / VIMI-20955
The complete accounting data validation can now be used with the app. (Setting “S” in In VIM
customizing: Vendor Invoice Management > Fiori Configuration > Enter Cost Assignment > Enter Cost
Assignment Check Settings).
Fiori Confirm Quantity and Price app

VIMI-20444
In case when invoice accounting data is entered in the Fiori App Enter Cost Assignment, further
approval steps may be running not as expected. In particular, the invoice can be sent back and forth
between two requesters or approvers
VIMI-21866
Invoice image not shown in when using the app on a mobile device.
VIMI-22057
Missing input conversion of quantity causes short dump in the backend.
VIMI-22340
Some function modules of the function group /OTX/PS35_MPOEX_ODATA are not remote enabled,
which leads to short dumps in some system configuration.
Fiori Exceptions app
VIMI-21808
Wrong count of inbox entries shown in the app.
Input Channels
11.2.9.1 IDF Framework (BC Inbound)
VIMI-20309
Archiving user is incorrect in DP document when image uploaded using BC inbound.
VIMI-20528
IDOC number is missing when DP document is created through BC Inbound IDOC channel.
VIMI-20950
When VIM process is started based on IDOC input through BC Inbound processing, document line
item data is wrongly mapped. Some values are mapped into wrong line items.
VIMI-21125
The BC and VIM logs can be out sync when validation is activated in the system. The VIM status
shown “Extraction Completed” while the BC log shown “Sent to/Ready for Validation”.
106
11.2.9.2 Other
VIMI-20362
In the PDF rendering of IDOCs, tax rate is shown as zero, while IDOC itself has non-zero rate. Title
for credit memos is still saying “Invoice”.
VIMI-21297
In the PDF rendering of IDOCS, the IBAN provided in the IDOC was overwritten with the IBAN
present in the vendor master. The IBAN provided in the IDOC will be retained now.
VIMI-21731
Subsequent credit document received through IDOC channel is processed as an invoice.
Invoice Exception
VIMI-19966
Special characters are corrupted in the archived mail that was sent with the Return to Vendor option.
VIMI-20938
If a blocked invoice is released using the transaction MRBR while blocked invoice dashboard for the
document is open, invoice status was not set correctly in VIM Analytics report.
VIMI-21030
Incorrect values for Price/Quantity and Amount were shown in the screen area “SAP invoice” in PO
blocked invoice dashboard.
VIMI-21096
Cancel and re-enter invoice does not work as expected when the Pre-fill Function Module mentioned
in documentation is used.
VIMI-21362
Cancel and Re-enter process option in the PO blocked invoice dashboard doesn't link the image
correctly to the new document that has been created.
VIMI-21505
Header level blocked invoice workflow could be completed unexpectedly while some invoice blocks
were still present.
VIM Notifications
VIMI-21824
When the parameters “Inbox days” and “Days before payment due” are set, the reminder report does
not evaluate both these values for each DP document. Due to this some documents are not
displayed in the final output.
107
VIM Analytics (new VAN) Report and VAN Liability Report
VIMI-17731
When clicking on a hotspot (hyperlink) for a purchasing document, scheduling agreement cannot be
opened.
VIMI-19876
Time out short dump in VIM Analytics.
VIMI-20099
DP Comments are not displayed in the approval history section in the detail page of the new VAN
report.
VIMI-20109
In VIM Analytics report, Update date and update time in the result pane and in the detail pane are not
correct.
VIMI-20196
Program /OPT/VR_ANALYTICS_750_PRECHECK Aborts with the runtime error
"SAPSQL_STMNT_TOO_LARGE".
VIMI-20214
Accounting document shown in VIM Analytics is not correct. The MM document is shown instead of FI
ocument.
VIMI-20230
If payment block is set outside of VIM, the blocking reason may be shown incorrectly in VIM Analytics.
VIMI-20264
Blocked reason and transaction type/event are not shown in VIM Analytics when invoice posted from
MIRO with payment block.
VIMI-20396
An error message is shown when opening the first item in workflow log in multi backend VIM
Analytics(transaction "/opt/vim_va26").
VIMI-20440
Payment terms and baseline date are not updated in DP document if they are changed when posting
a parked invoice in MIR4 transaction.
VIMI-20649
Exception reason incorrect for blocked Invoices in VIM Analytics.
VIMI-20713
Short dump when clicking the "Back" button in KPA report.
108
VIMI-20937Multibackend / remote VIM Analytics (transaction /opt/vim_va26) dumps with the runtime
error TSV_TNEW_PAGE_ALLOC_FAILED.
VIMI-21186
When an Non-PO document is posted in VIM and then reversed, the status in the table
/OPT/VIM_1HEAD still set as posted, but the proper status 'Cancelled' is shown in VIM analytics.
VIMI-21461
When using selection with "Current Agent ID" and “Overdue”, all overdue documents in the system,
including those of other agents, may be displayed.
VIMI-21542
When selecting entries based on the "Selected Status" with the “Excluding” option, not all entries are
displayed in the output.
VIMI-21613
Current approval agent is shown incorrectly in VIM Analytics if an approval workitem is reserved
outside of VIM.
Central Reporting and Other Reports
VIMI-21107
The summary report does not display the payment date and time
VIMI-21239
Clicking on the current role field does not show user for work items which are in the completed status.
VIMI-21403
Exception analysis report includes obsolete documents, leading to a difference in the output of the
KPA report and exception analysis report.
VIMI-21602
Output results differ between the KPA report and the exception analysis report in case documents that
are suspected duplicates are relevant for the selection or if the checkboxes in “Document
characteristics” selection area of the exception analysis report are used.
VIM Workplace
VIMI-20102
Reroute option in VIM Workplace shows inactive roles as blank.
VIMI-20251
Comments should be entered mandatorily when performing a bulk referral action from VIM
Workplace.
109
VIMI-19779
When accessing VIM Workplace from Fiori Launchpad, the initial access results in a short dump.
VIMI-20102
Empty lines are displayed in the "Process re-routing" dialog popup.
VIMI-20251
Comments are not requested, although configured to be mandatory, when doing a bulk referral from
the VIM Workplace.
VIMI-20253
Missing error message that comments are mandatory when re-routing from VIM WP.
VIMI-20728
Short dump when resizing or hiding the selection pane in VIM Workplace.
VIMI-21236
After resizing the content pane in VIM Workplace the new resize percentage is not stored.
VIMI-21317
A short dump is generated in Class /ORS/PO_INVOICE_NEW method VALIDATEACCTDATA when
processing work items from VIM Workplace for DP documents having more than 1000 line items.
VIMI-21612
No DP documents are shown in VIM Workplace.
Customizing
VIMI-21140
When data is pasted into role maintenance screen from an Excel file, it is not properly transferred.
This leads to erroneous entries in the table /PTGWFI/Z_KEYRNG, and to incorrect role resolution for
work items.
Supplier Self Service

VIMI-20939
Supplier Self Service Lean: Search on special characters on reference number (XBLNR) will not
return data.
VIMI-21574
Unable to enhance 3S tables /opt/wt_3s and /opt/wt_3s_pymnt.
VIMI-21729
Navigation attributes (slim-arrow-right) displayed in wrong column in 3S full variant.
110
Installation and Upgrade
111
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
Copyright © 2018 Open Text. All Rights Reserved.
Trademarks owned by Open Text. The list of trademarks is not exhaustive of other trademarks, registered trademarks, product names, company names, brands and
service names mentioned herein are property of Open Text or other respective owners.
112

Vendor Invoice Management SAP

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Vendor Invoice Management SAP

Încărcat de

Drepturi de autor:

Formate disponibile

OpenText™ Vendor Invoice

Management for SAP® Solutions

Product Released: 2018-11-05

Release Notes Revised: 2019-01-24

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

4 Packaging and documentation ................................................................................................... 40

5 Supported environments and compatibility .............................................................................. 45

6 Installation and upgrade notes ................................................................................................... 57

7 Support Package .......................................................................................................................... 60

8 Post Installation Activities .......................................................................................................... 61

9 Optional Post Installation Activities ........................................................................................... 73

10 Known issues ............................................................................................................................... 73

11 Fixed issues .................................................................................................................................. 78

12 Contact information ................................................................................................................... 112

1.1 Release Notes revision history

Revision date Sections revised Description of revisions

2017-10-31 First release. All new content.

2017-11-07 Minor text corrections

2017-11-29 3.1.2 Optional packages Add BW add-on

2018-03-02 All Support Package 16.3.1

2018-11-05 All Support Package 16.3.2

Added post installation steps for configuration

Adjustments due to the passing the SAP

Supported environments Added Approval Portal Downward Compatibility

Adjusted the date of language packages

With implementation of Vendor Invoice Management companies achieve:

• Invoices that can be automated by their nature and structure

Features of “Simple Mode”:

• Runs with a minimum of configuration based on pre-delivered best practices settings

Processing of invoices through “Simple Mode”

Limitations of Simple Mode

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

2.2 General Data Protection Regulation (GDPR)

3.1 New Features in VIM 16.3

Processing of parked and held documents

• Posting all invoices in MIRO and logistic BAPIs

OCR interface for Cloud OCR interface

• Connection to the (planned) OpenText Information Extraction Services, Cloud edition

• No cross-system aggregation – use central reports only for local system

Multi-backend communication across different versions

VIM Fiori apps

• VIM Approve Invoices Fiori app

VIM 16.3 “Simple Mode” includes the following Fiori apps

• VIM My Invoices Fiori app

Fiori WebUI framework enhancements

Supplier Self Service (lean variant)

Additional features compared to VIM 7.5

• Supplier onboarding/off-boarding process (self registration):

• Supplier Invoices app:

• Supplier Accountant app:

New VIM My Approved Invoices Fiori app (VIMI-20329)

Attachment Upload for VIM Approve Invoices Fiori app (VIMI-20281)

Disabling withholding tax warning message “Withholding tax calculation

Spanish localization: SII Support (VIMI-18756)

• The Z-constant (005/ SET_REF_MAPPING_SP) allows the customer to choose option 1 or 2,

Option 3) Based on a custom field in BKPF

*" VALUE(INDEX_DATA) TYPE /OPT/VIM_1HEAD

*" VALUE(INDEX_DATA2) TYPE /OPT/VIM_2HEAD

*" VALUE(OK_CODE) TYPE SY-UCOMM

*" INDEX_ITEMS STRUCTURE /OPT/CIDX_ITEMS

*" RETURN STRUCTURE BAPIRET2

Description: DP indexing screen - validation exit

Value: user exit function module name