OpenText Vendor Invoice Management 75 SP7 Release Notes

OpenText™ Vendor Invoice Management
for SAP® Solutions
Release Notes
Version 7.5 SP7
Product Released: 2017-12-18
Release Notes Revised: 2018-05-03

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

3 Installation................................................................................................................................. 9
3.1 SAP Prerequisites ................................................................................................................. 9
3.2 Prerequisites on Archive Server (VIMI-4180) ......................................................................... 9
4 New Features .......................................................................................................................... 10

4.1 Disabling withholding tax warning message “Withholding tax calculation has
changed” (VIMI-19142) ....................................................................................................... 10
4.2 Fiori Confirm Quantity and Price app: background posting after PO price change
(VIMI-19386)....................................................................................................................... 10
4.3 Spanish localization: SII Support (VIMI-18756).................................................................... 10
4.4 Implementing custom field validation in the DP indexing screen (VIMI-19347) ..................... 11
4.5 Adding the Forward action from VIM Workplace (WP) in the VIM logs (VIMI-19368) ............ 12
4.6 New customizing for mandatory comment when declining an invoice in Fiori Enter
Cost Assignment app (VIMI-19538) ..................................................................................... 12
4.7 New business rule: SCB Indicator / Supplying Country Missing (VIMI-19721) ...................... 13
4.8 Restricting ALV layout for process logs (VIMI-18719) .......................................................... 13
4.9 Changing logical system on VIM tables (VIMI-18607) .......................................................... 14
4.10 Support for branch code – Thailand specific (VIMI-19339)................................................... 14
4.11 Additional accounting data section in coding templates when exporting coding in
Approval Portal (VIMI-16466) .............................................................................................. 14
4.12 Initial sorting in the Approval Portal inbox (VIMI-18087) ....................................................... 14
4.13 Default option to show invoice image in Web Approval Portal (VIMI-18832) ......................... 15
4.14 Configuration of timeout for Approval Portal web requests (VIMI-18925).............................. 15
4.15 Refreshing the Approval Portal inbox after using a custom button (VIMI-19060) .................. 15
4.16 Improvements in the invoice inquiry status display in the Approval Portal (VIMI-
19516) ................................................................................................................................ 15
4.17 Search Help support in additional accounting data area in Approval Portal (VIMI-
19711) ................................................................................................................................ 15
4.18 Search Help support for custom header fields in Approval Portal (VIMI-19732) .................... 15
4.19 Tax code description display in the DP indexing and Approval screens (VIMI-19367) ........... 15
4.20 Support of GST Registration Number for receiving location (VIMI-19408) ............................ 16
2
4.21 Support of HSN Code in PO Line Items Proposal (VIMI-19408)........................................... 16
4.22 User exit to determine default proposal for next approver if not unique (VIMI-19033) ........... 16
4.23 New Fiori app for Supplier Self Service (VIMI-18628) .......................................................... 16
4.24 Cross release multiple backend support (VIMI-19650)......................................................... 17
4.25 Reduction invoice support (VIMI-19274).............................................................................. 17
4.26 iOS 11 support for Mobile Approvals (VIMI-20210) .............................................................. 17
4.27 Support of GST Import Procurement (VIMI-19432) .............................................................. 17
4.28 Full user name in comments (VIMI-17866) .......................................................................... 18
5 Packaging and documentation............................................................................................... 19

5.1 Packaging and delivery information ..................................................................................... 19
5.1.1 ABAP package ....................................................................................................... 19
5.1.2 VIM Business Warehouse Component.................................................................... 19
5.1.3 Language Package ................................................................................................ 20
5.1.4 VIM Gateway Component....................................................................................... 20
5.1.5 Non-ABAP Packages ............................................................................................. 20
5.1.6 Business Center for SAP Solutions – Limited Use................................................... 21
5.1.7 Business Center – VIM upgrade from lower support package level ......................... 21
5.1.8 Business Center - downloading components required for different scenarios .......... 23
5.1.9 Business Center – compatibility and support package information .......................... 25
5.1.10 Business Center - installation ................................................................................. 26
5.1.11 Business Center - ACP files .................................................................................... 27
5.1.12 Business Center - system landscape example ........................................................ 27
5.2 Documentation ................................................................................................................... 28
6 Supported environments and compatibility .......................................................................... 29
6.1 Compatibility Matrix............................................................................................................. 29
6.2 Language support ............................................................................................................... 29
6.3 Approval Portal downward compatibility matrix .................................................................... 30
6.4 Approval Portal Supported SAP Netweaver Versions .......................................................... 32
6.5 Supported web browsers .................................................................................................... 32
6.6 Supported operating systems for mobile devices ................................................................. 33
6.7 Web Viewer support............................................................................................................ 34
6.8 Brava View support (VIM OAP) ........................................................................................... 34
7 Fixed issues ............................................................................................................................ 35
7.1 Document Processing (DP)................................................................................................. 35
7.2 Document Processing (DP) – Logic Modules....................................................................... 42
7.3 Invoice Approvals................................................................................................................ 43
3
7.4 Web Approval Portal ........................................................................................................... 45
7.5 Mobile Approval Portal ........................................................................................................ 46
7.6 Fiori Approve Invoices app .................................................................................................. 46
7.7 Input Channels ................................................................................................................... 46
7.8 Invoice Exception................................................................................................................ 47
7.9 VIM Notifications ................................................................................................................. 47
7.10 VIM Analytics report and VAN Liability report ....................................................................... 48
7.11 Central Reporting and other reports .................................................................................... 49
7.12 VIM Workplace ................................................................................................................... 49
7.13 Supplier Self Service........................................................................................................... 50
7.14 Fixed issues with SP7 for S/4HANA Edition ......................................................................... 50
7.14.1 Customizing ........................................................................................................... 50
8 Post installation activities ...................................................................................................... 51
8.1 Activate BC set /OTEXVIM/VIM75_SP7_CUSTOMIZING .................................................... 51
8.2 Activate BC set /OTEXVIM/VIM75_SP7_B3 ........................................................................ 51
8.3 Import transports with layout variants for VIM Analytics ....................................................... 51
8.4 Import transports with perspective layouts for Fiori Apps ..................................................... 51
8.5 Reduction invoice support – implicit enhancement (VIMI-19274) ......................................... 52
8.6 Spanish localization (VIMI-18756) ....................................................................................... 52
8.7 New business rule: SCB Indicator / Supplying Country Missing (VIMI-19721) ...................... 55
8.8 Reduction invoice support - configuration (VIMI-19274)....................................................... 58
9 Optional Post Installation Activities ....................................................................................... 61
9.1 Add customizing for VIM KPI dashboard in the S/4HANA edition (VIMI-19153) .................... 61
9.2 Steps needed if custom buttons are used in Approval Portal (VIMI-19060) .......................... 61
10 Documentation Extensions .................................................................................................... 62

10.1 Installation Guide ................................................................................................................ 62
11 Known issues.......................................................................................................................... 62
11.1 VIMI-19887 ......................................................................................................................... 62
11.2 VIMI-20392 ......................................................................................................................... 62
11.3 VIMI-20393 ......................................................................................................................... 62
11.4 VIMI-20417 ......................................................................................................................... 62
11.5 VIMI-20433 ......................................................................................................................... 63
11.6 VIMI-20367 ......................................................................................................................... 63
11.7 VIMI-20431 ......................................................................................................................... 63
11.8 VIMI-20226 ......................................................................................................................... 63
11.9 VIMI-20455 ......................................................................................................................... 63
4
11.10 VIMI-20444 ......................................................................................................................... 63
11.11 VIMI-20568 ......................................................................................................................... 63
11.12 VIMI-20550 ......................................................................................................................... 64
11.13 VIMI-20615 ......................................................................................................................... 64
11.14 VIMI-20799 ......................................................................................................................... 64
12 Contact information ................................................................................................................ 66
5
1 Introduction
These Release Notes provide an overview of OpenText™ Vendor Invoice Management for SAP®
Solutions Version 7.5 SP7, including new features, delivery information, and supported platforms.
OpenText recommends that you read these Release Notes in conjunction with the documentation
included with the software package. If any conflicts exist, the Release Notes supersede the other
documentation.
We also recommend that you check OpenText My Support (https://support.opentext.com) for any
patches or documentation updates that may have been posted after the initial release of this product.
1.1 Release Notes revision history

Revision date Sections revised Description of revisions
2017-12-18 First release.
New features, Fixed Several missing entries added, some entries

2017-12-18
issues removed.
Corrected delivery information for OTBCSL03,

Packaging and delivery,
2018-01-11 OTBCUS03. New known issues entry for VIMI-
Known issues
20550, VIMI-20568, VIMI-20615.
Corrected delivery information for main VIM

2018-01-16 Packaging and delivery
package.
Added information about a transport for Fiori

2018-02-05 Post-installation
Apps.
2018-02-09 New features Minor corrections in features details.
2018-02-19 Post-installation Minor corrections regarding BC set activation.
New technical package names for OTBCSL03

2018-02-27 Packaging and delivery
and OTBCSL33.
2018-02-28 Known issues New known issues entry for VIMI-20799
6.4 Supported
2018-03-01 Information on SAP Netweaver versions
environments
5.1.4 VIM Business

2018-03-12 Insert the section for BW Add-On Component
Warehouse Component
10. Documentation Added for BW information missing in VIM

2018-03-12
Issues Installation Guide 7.5 SP7
6
2018-03-13 Packaging and delivery Added compatibility with BC 16.3.1
Correction for details on the new feature, VIMI-

2018-03-20 New features
19650
Change of transport name for Fiori perspectives

2018-03-22 Post installation
layouts
2018-05-03 Fixed issues Removed VIMI-19966
7
2 About OpenText™ Vendor Invoice Management for
SAP® Solutions
This section provides an overview of OpenText™ Vendor Invoice Management for SAP® Solutions
Version 7.5 SP7.
Welcome to OpenText Vendor Invoice Management (VIM). VIM is an add-on that works with existing
SAP ERP systems to streamline accounts payable operations.
Support Package 7 (SP7) contains quality improvements as well as enhancements for OpenText
Vendor Invoice Management 7.5. The installation of SP7 requires the prior installation of VIM 7.5 SP6.
Ensure that you install new Support Package stacks regularly to prevent problems that have already
been corrected, from recurring in the VIM solution.
Caution
Read these Release Notes completely BEFORE applying VIM 7.5 SP7 and follow the
instructions given.
Support Package 7 applies to the following versions of VIM 7.5:
 OpenText Vendor Invoice Management 7.5 for SAP ERP 6.0 (including SAP Suite on HANA, S/4
HANA Finance and SAP Simple Finance)
 OpenText Vendor Invoice Management 7.5 Edition for S/4 HANA: Please see limitations listed in
“OpenText Vendor Invoice Management 7.5 S4HANA Release Notes”
(https://knowledge.opentext.com/knowledge/llisapi.dll/Open/61907298)
8
3 Installation
This chapter gives some hints for the installation of Support Package 7 for Vendor Invoice
Management (VIM) 7.5. For the detailed installation description, read the VIM 7.5 SP7 Installation
Guide.
3.1 SAP Prerequisites

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

VIM 7.5 is able to work with any archive that is compatible with SAP ArchiveLink. If you are using the
OCR option or the Approval Portal, you must have a content repository that supports the SAP Content
Server HTTP 4.5 Interface.
9
4 New Features
4.1 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:
Product Code = 005
Constant = NO_WHT_MESSAGE
Description = If set, withholding tax changes do not create a message on indexing screen
Constant Value = X
4.2 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.
4.3 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.
VIM 7.5 SP7 introduces a new field (LXBLNR) 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.
10
 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 BKTXT & 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.
4.4 Implementing custom field validation in the DP indexing screen

(VIMI-19347)
When standard field validations performed by VIM in the DP indexing screen are not sufficient,
additional validations can be implemented starting with VIM 7.5 SP7, 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 with the exception of
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
11
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:
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.
4.5 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.
4.6 New customizing for mandatory comment when declining an

invoice in Fiori Enter Cost Assignment app (VIMI-19538)
12
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‟.
4.7 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_75) and 290 for Non-PO invoices (document type NPO_75). The corresponding customizing
is delivered in the BC set provided with this support package. Steps required for manual configuration
are described in the “Post installation” chapter.
4.8 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
13
/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).
4.9 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”

 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.
4.10 Support for branch code – Thailand specific (VIMI-19339)

Branch code can now be used in DP documents to post Non-PO and PO invoice 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 background BDC IDs (6, 34, 42).
4.11 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.
4.12 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.
14
4.13 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".
4.14 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.
4.15 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.
4.16 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.
4.17 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.
4.18 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.
4.19 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.
15
4.20 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.
4.21 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.
4.22 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.
4.23 New Fiori app for Supplier Self Service (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.
16
4.24 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:
 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.
4.25 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.
4.26 iOS 11 support for Mobile Approvals (VIMI-20210)

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

GST Import Procurement is now supported in the context of Indian GST.
17
4.28 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..
18
5 Packaging and documentation
Downloads and documentation for OpenText Vendor Invoice Management for SAP Solutions are
available at OpenText My Support (https://knowledge.opentext.com/).
5.1 Packaging and delivery information

The components and packages updated with this support package are listed below. For a complete
list of all available components, see the VIM 7.5 Installation Guide and the Release Notes documents
for the support packages VIM 7.5 SP1 through VIM 7.5 SP6. The download files for VIM 7.5 SP7 are
located on OpenText My Support:
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=70787700
5.1.1 ABAP package

To install VIM 7.5 SP7, you need the following files:
SAP Version File for Support Package
D240020305028_0000042.PAT
SAP ECC 6.0

(Follow the My Support path: VIM 7.5 SP7 for
ECC6.0/S4HANA -> D240020305028_0000042.zip)
Location on OpenText My Support:

Note: For S/4 HANA, there is an additional component OTVIMS4, delivered in VIM 7.5 SP4
(installation file OTVIMS4_INST_750_S4.SAR). It has to be installed, but there are no such
additional files delivered with 7.5 SP7. See the Release Notes of VIM 7.5 SP4.
5.1.2 VIM Business Warehouse Component

From VIM 7.5 SP7 OpenText strongly recommend deploying VIM Business Warehouse (BW) Add-on
on SAP NetWeaver BW 7.5 (also on HANA) onwards.
The following packages are delivered for VIM BW Add-on along with VIM 7.5 SP7:
 Installation package OTVIMBW_INST_VIM700_700.SAR.

 Support package 1: otvimbw_sp1.sar.
 Support package 2: otvimbw_sp2.sar.
All packages are available in the installation CD or in My Support in the following link:
19
https://knowledge.opentext.com/knowledge/llisapi.dll/open/57293448
In case you deploy VIM BW add-on on SAP NetWeaver BW 7.3, the installation package is available
in Installation CD. Please refer to Installation Guide for more information.
5.1.3 Language Package

15 languages are included in the cumulative language package for VIM 7.5 SP7:
VIM7.5SP7_15Lans.sar (provided in the download file vim7.5sp7_15lans.zip).
5.1.4 VIM Gateway Component

Use the OTVIMGW 700 Install Package for a new installation of the VIM Gateway Component up to
SAP NetWeaver 7.31. The package has been delivered with the main installation package of VIM 7.5.
Use the OTVIMGW 740 Install Package for a new installation of the VIM Gateway Component from
SAP NetWeaver 7.40. The package has been delivered with VIM 7.5 SP2 and is located on OpenText
My Support:
Along with SP7 for VIM 7.5, an SP2 is released for the OTVIMGW 740 component. It is delivered in
the file Q5O0020073437_0000118.PAT. (Follow the My Support path Patches > Vendor Invoice
Management 7.5 > SAP NetWeaver 740 Gateway Component Support Package 2 ->
Q5O0020073437_0000118.zip.)
5.1.5 Non-ABAP Packages
Component Packages
Use the files located in im_approval_portal7_5sp7.zip:

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

VIM Approval Portal OAP 7.5 SP7
im_approval_portal7_5sp7_jco3.zip:
on JCo3
 IM_APPROVAL_PORTAL7_5SP7.sca,
IM_APPROVAL_PORTAL7_5SP7.sda - either .SCA or
.SDA file should be deployed.
Note: For JCo3 1.8, use the files located in
IM_APPROVAL_PORTAL7_5SP7_JCo3_JAVA1_8.zip
 opentext.zip - extract this ZIP into the standard
installation folder specified in VIM Installation Guide.
Notes:
20
 In VIM 7.5 SP7, no new support package for Supplier Self Service Component (HANA Cloud)
is needed, please continue to use the package delivered with VIM 7.5 SP5.
 In case you need an Approval Portal 7.5 SP7 Java version 1.8 build compatible with JCo2,
there is a special download package. Contact OpenText Customer support referring VIMI-
20179.
 Similarly, for Approval Portal 7.5 SP7 Java version 1.6 JCo2, contact the Customer Support
referring VIMI-20180.
5.1.6 Business Center for SAP Solutions – Limited Use

OpenText Business Center for SAP Solutions, also known as SAP Digital Content Processing by
OpenText, can be purchased as a standalone product.
Starting with VIM 7.5 SP 2 (VIM 7.0 SP 6), VIM customers are entitled to use OpenText Business
Center for SAP Solution Foundation (ABAP) to implement additional aspects of their Accounts
Payable process. For the purpose of the limited use, OpenText Business Center can be downloaded
from OpenText My Support. Note that it is not available for SAP Marketplace unless you purchase a
standalone license - this is not the scope of the limited use.
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 use of the generic Fiori Task App, use of the Business Center
Workplace, creation or change of vendor master triggered by an incoming invoice, 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) like purchase orders, purchase
requisitions, delivery notes, sales orders etc. 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.
As part of the limited use, VIM 7.5 SP 2 / VIM 7.0 SP 6 and higher are providing VIM Fiori apps.
These Fiori apps are based on the generic Fiori Task App of OpenText Business Center for SAP
Solutions Foundation. Furthermore, an integration of VIM work items and exceptions into Business
Center Workplace is possible.
For the list of supported browsers and mobile devices, check the latest version of the Release Notes
for Business Center for SAP Solutions.
5.1.7 Business Center – VIM upgrade from lower support package level
When upgrading to VIM 7.5 SP7 with an existing BC 10.x / 16.0 installation, you must upgrade to
Business Center Version 16.3 (see the next section) if VIM uses any component of Business Center
(for example Business Center Inbound or the Business Center Fiori App).
21
22
5.1.8 Business Center - downloading components required for different
scenarios
The following table lists components of OpenText Business Center for SAP (BC, also known as SAP
Digital Content Processing by OpenText), that are required to be installed on your systems depending
on the scenarios you use VIM for. It also explains where each component has to be downloaded from.
Two groups of scenarios are to be distinguished, where BC components are required:
Inbound – processing of incoming invoices through scanning via OCR (ICC, BCC), email,
IDOC, Ariba Network etc.
Fiori Apps – using Fiori Apps provided with VIM (Approve Invoices, Enter Cost Assignment,
Confirm Quantity and Price), with the exception of VIM Invoice Analysis Fiori app.
Note that two components delivered with VIM 7.5 SP4 for VIM Invoice Analysis Fiori app, OTVIMWUI
and OTVIMWSR, have no dependency on BC and are not discussed in this chapter.
The BC components and the components based on BC that are required for each scenario are
marked in the table. The different components are not necessarily to be installed on the same server.
A diagram with a system landscape example later in this chapter will help you to understand that.
BC Fiori Install SPs

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

update 1 2
OTBCBAS 0700_003 0700_003 SP1 0700_003 SP1 – 0700_004 or

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

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

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

delivered with BC
16.0 update 1 0740_004 SP 0001
OTBCWUI 0740_003 SP1 0740_003 SP2 0740_003 SP3 0740_004 or
0740_004 SP 0001
OTBCSL30 0700_003 0700_003 SP1 0700_003 SP2 0700_004
OTBCSL03 0700_003 0700_003 SP1 0700_003 SP2 0700_004
OTBCSL33 0700_003 0700_003 0700_003 SP2 0700_004

SP1
OTBCUS03 0740_003 0740_003 0740_003 SP2 0740_004 SP1 –

SP1 installation and SP1
delivered with 7.5 SP7
25
The packages for Business Center based VIM Solutions are delivered as install/upgrade packages.
The file names for the latest SPs of those components, being delivered with VIM 7.5 SP7 are listed in
the table below.
Component Release Support OCS Filename OCS Package

Package
OTBCSL30 0700_004 QAR0020073437_0000072.PAT SAPK-004COINOTBCSL30
OTBCUS03 0740_004 0001 QAT0020073437_0000004.PAT SAPK-004COINOTBCUS03
QAT0020073437_0000006.PAT
The support package files and language packs for those four components can be downloaded from
OpenText My Support, VIM 7.5 SP7 area.
5.1.10 Business Center - installation

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

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

Note that depending on your system landscape, different BC components will not be necessarily
installed on the same server. The illustration below provides an overview on where the specific
components are to be installed. For more information, see Business Center Installation Guide
(chapter 4).
27
Warning
Installing the Business Center Web Services (OTBCWSR) and VIM Web
Services (OTBCSL33) on a different system than the Business Center
Foundation (OTBCFND) and VIM Foundation (OTBCSL03) is not supported.
5.2 Documentation
For the latest updates of the User Guide, Installation Guide, Configuration Guide, Administration
Guide, Reference Guide, and Scenario Guide, refer to the VIM 7.5 SP7 documentation set available
on OpenText My Support.
The VIM 7.5 SP7 User Guide is available in English language only.
The VIM 7.5 SP4 User Guide is available in the following languages: Chinese, Dutch, English,
French, German, Italian, Japanese, Portuguese, Russian, and Spanish.
28
6 Supported environments and compatibility
6.1 Compatibility Matrix
For details on compatibility between OpenText products, refer to the Compatibility Matrix
(https://knowledge.opentext.com/go/matrix ) on OpenText My Support.
6.2 Language support

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

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

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

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

OAP 7.5 SP1
OAP 7.5 SP2
OAP 7.5 SP3
Compatibility
Matrix VIM 7.5
VIM 7.5
VIM 7.5 SP1
VIM 7.5 SP2
VIM 7.5 SP3
VIM 7.5 SP4
VIM 7.5 SP5
VIM 7.5 SP6
VIM 7.5 SP7
30
Legend:
Some of the features are only partially supported. OpenText strongly recommends that you have
a completely supported stack.
31
6.4 Approval Portal Supported SAP Netweaver Versions
The following table lists the supported combinations of SAP Netweaver and the Web Approval Portal
versions:
SAP Netweaver Version

OAP Versions
7.0 7.3 7.4 7.5
7.5 SP1 to 7.5 SP7
7.5 SP3 JCo3 to 7.5 SP7 JCo3
7.5 SP6 JCo3 Java 1.8 to 7.5 SP7

JCo3 Java 1.8
6.5 Supported web browsers

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

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

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

and above
32
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.
6.6 Supported operating systems for mobile devices

The following table lists the supported combinations of the operating systems for mobile devices and
the Web Approval Portal versions:
Mobile devices matrix
OAP 7.5 SP4
OAP 7.5 SP5
OAP 7.5 SP6
OAP 7.5 SP7

OAP 7.5 SP1
OAP 7.5 SP2
OAP 7.5 SP3

OAP 7.5
iOS (9.0)
iOS (10.0)
iOS (11.0)
Android (> 6.0)
Note
In general, you can view the Mobile Approval Portal inside the browsers on all kind of
Android devices. Due to the diversity of physical Android devices, OpenText cannot
guarantee 100% compatibility on all functionality that the Mobile Approval Portal offers.
Please consider the list of all supported browsers also.
33
6.7 Web Viewer support
The following table lists the supported combinations of Web Viewer and the OpenText Approval Portal
versions:
Supported Web Viewer versions

Web Viewer
support matrix 10.5 16
Web Mobile Web Mobile
OAP 7.5 SP7
Note
Supported document types are JPG, TIF and PDF. For the rest of document types,
OpenText recommends that you test this combination in the test environment before
moving on to the production.
6.8 Brava View support (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 7.5 SP7
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.
34
7 Fixed issues
7.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.
35
VIMI-18907
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
36
Discount amount is not updated in the DP document when its value is changed during online posting
of a non-PO invoice.
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.
37
VIMI-19299
Displaying documents with negative tax amounts results in a short dump. Such negative tax amounts
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.
38
VIMI-19459
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.
39
VIMI-19654
Program /OPT/CR_RERUN_RULES_JOBS triggers events after the number of retry limit is reached.
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.
40
VIMI-19804
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
41
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.
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.
7.2 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.
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.
42
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.
7.3 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.
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
43
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
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.
44
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.
7.4 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
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.
45
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.
7.5 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.
7.6 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.
7.7 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
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
46
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.
7.8 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.
7.9 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'
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
47
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.
7.10 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.
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.
48
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.
7.11 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.
7.12 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
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
49
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.
7.13 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.
7.14 Fixed issues with SP7 for S/4HANA Edition

7.14.1 Customizing
VIMI-19153
The customizing for KPI dashboard was missing in the S/4HANA edition, if the system had been
installed as described using BC set /OTEXVIM/VIM75_LEGACY_S4. To add the customizing for KPI
dashboard, activate BC set /OTEXVIM/VIM75_KPI_S4.
50
8 Post installation activities
8.1 Activate BC set /OTEXVIM/VIM75_SP7_CUSTOMIZING
This BC set contains table content changes of the VIM baseline customizing. If you are using the
standard baseline VIM customizing, you can activate the BC set without any concerns. In case you
have changed the VIM baseline customizing, make sure the BC set will not overwrite any
customizing.
8.2 Activate BC set /OTEXVIM/VIM75_SP7_B3

This BC set has to be activated in case the Fiori apps or BC Inbound are used. In case you have
changed the VIM baseline customizing, make sure the BC set will not overwrite any customizing.
Note: this BC, in contrast to corresponding BC sets in the earlier SPs, contains complete customizing
for Fiori apps and BC Inbound, and not only delta changes.
8.3 Import transports with layout variants for VIM Analytics

Due to limitations of the BC set technology, the entries for layout variants cannot be transported in BC
sets. Therefore copy the transport files into the proper transport directories and install the transport
using STMS. You have to install the transport to every client, as the transport contains client specific
data.
The following transports are provided:
EW3K901453 - Layout variants for SAP ERP
EW3K901454 - Layout variants for S/4HANA
The transports are available as an additional file download in the directory of VIM 7.5 SP7 (similar to
the language transports).
8.4 Import transports with perspective layouts for Fiori Apps

Perspective layouts for Fiori apps are not included into 7.5 SP7 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:
TWRK900547 - Perspective Layout for SAP ERP and S/4HANA
The transport is available as an additional file download in the directory of VIM 7.5 SP7 (similar to the
language transports).
51
8.5 Reduction invoice support – implicit enhancement (VIMI-19274)
To be able to process reduction invoices, create an implicit enhancement point at the end of form
“MRM_DRSEG_FILL” in the program “LMRMHF0A” and place the code as shown in the following
screenshot.
Note that there is additional configuration needed, which is delivered in the BC set and can also be
performed manually, as described later in this document.
The rest of this chapter describes post installation activities that are delivered with the BC set.
8.6 Spanish localization (VIMI-18756)

VIM 7.5 SP7 introduces a new field (LXBLNR) to hold the complete/entire „Long invoice number‟ and
a new constant SET_REF_MAPPING_SP, to split and store invoice number into fields XBLNR,
BKTXT in BSEG, aligned with SAP‟s proposal.
Configuration steps:
1. Run the /OPT/VIM_SPRO transaction and navigate to Vendor Invoice Management >
Document Processing Configuration > General Configuration > Incoming Document
Processing > Maintain Mapping ID.
52
2. In the following screen, select the Mapping ID GENERAL.
3. In the Dialog Structure, double click Field Mapping.

4. Click New Entries and add the following entry:
External Field Name: LXBLNR
Field Type: Header
Document Field Name: LXBLNR
5. Save it.
6. Double click Automated Field Enhancement
7. Click New Entries and insert the following entries:
Document
Field Field Field
Counter Type Name Field Processing Type Value Enhanced Field Function Module
42 Header XBLNR Function Module /OPT/VIM_EXIT_MAP_ENH_10
43 Header BKTXT Function Module /OPT/VIM_EXIT_MAP_ENH_10
53
8. Maintain an entry in table /OPT/VIM_ZCONST:
Choose offset length for XBLNR and BKTXT based on requirement. Maximum offset length can be
X10,B25 or B25,X16
After the entry, the screen looks as follows:
9. Perform the following setting for the field LXBLNR for the respective document type:
Run the /OPT/VIM_SPRO transaction and navigate to Vendor Invoice Management > Document
Processing Configuration > Document Types Configuration > Maintain Document Types.
54
8.7 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)
55
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.
NPO Document Type:
PO Document Type:
56
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:
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.
57
Example Germany (DE):
c. Add Process Types 190 and 290 to the Characteristic Specific Process Types:
Important: Use Category Group „12 – Intra-Community, Imports and Triangulati[on]“ because this
Business Rule should be activated for foreign vendors only.
8.8 Reduction invoice support - configuration (VIMI-19274)

To be able to process reduction invoices, several configuration steps must be performed.
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
as shown in the following:
58
The business rule related function module and its configuration is shown in the following screenshot:
The configuration of BDC ID 202 is shown in the following screenshot:
59
60
9 Optional Post Installation Activities
The post installation activities described in this chapter are optional and not delivered with the BC set.
9.1 Add customizing for VIM KPI dashboard in the S/4HANA

edition (VIMI-19153)
The customizing for KPI dashboard was missing in the S/4HANA edition, if the system had been
installed as described using BC set /OTEXVIM/VIM75_LEGACY_S4. To add the customizing for KPI
dashboard, please activate BC set /OTEXVIM/VIM75_KPI_S4.
9.2 Steps needed if custom buttons are used in Approval Portal

(VIMI-19060)
The change to support inbox refresh when using custom buttons has introduced a new parameter into
the function call performed when the button is clicked. If such function-based buttons are used, it is
necessary to add the new parameter into the function module interface:
Exporting parameter name: ex_refresh_list
Type: CHAR1
The custom button definitions can be found under the following node in VIM customizing:
61
10 Documentation Extensions
10.1 Installation Guide
In VIM Installation Guide 7.5 SP7 it states that VIM BW Add-on component is not supported when
source (OLTP) system is running on HANA database.
This has been changed meanwhile.
From VIM 7.5 SP7 running on non-HANA or on HANA database, the VIM BW Add-On is supported.
The following combination is supported:
Source (OLTP) system BW (OLAP) System VIM BW Add-On Version
VIM 7.5 SP 0-7 non-HANA DB BW 7.x on Non-HANA VIM BW Add-On 7.0 or 7.3 (*)
VIM 7.5 SP7 non-HANA DB BW 7.5 SP4 on HANA VIM BW Add-on 7.0
VIM 7.5 SP7 on HANA DB onwards BW 7.5 SP4 on HANA VIM BW Add-on 7.0
(*) : BW add-on version 7.3 is explicitly created for OLAP system running on SAP NetWeaver BW 7.3.
Furthermore, for SAP NetWeaver BW 7.5 on Non-HANA or on HANA, the BI add-on BI_CONT 7.5.7
must be installed
11 Known issues
The following known issues exist in this release.
11.1 VIMI-19887
Supplier Self Service based on Fiori - Launchpad login page is improper in Internet Explorer 11.
11.2 VIMI-20392
Supplier Self Service based on Fiori - User Name is not case sensitive during the user registration
process.
11.3 VIMI-20393
Supplier Self Service based on Fiori - Error pop up is continuously displayed when an invalid search
is performed.
11.4 VIMI-20417
Supplier Self Service based on Fiori - Bubble Count is changing to max value when search, sort and
filters are applied and it is not matching with initial load count.
62
11.5 VIMI-20433
Supplier Self Service end user Fiori app and Supplier Accountant Fiori app only supported on desktop
with Chrome browser.
11.6 VIMI-20367
Supplier Self Service and VIM Fiori apps: Error pop up is in place when trying to perform a wildcard
search.
11.7 VIMI-20431
VIM Fiori apps: Search, filter and sort may work incorrectly on date and amount fields. Until the fix is
available, the values must be entered as they are displayed and formatted on screen, with separators
like comma or point.
11.8 VIMI-20226
Payment data is not shown in Supplier Self Service, when the flag “Document Date Required” is set in
company code definition in Supplier Self Service customizing.
11.9 VIMI-20455
The entries that are not relevant for the Supplier Accountant app must be deleted from "Options for
Last X Days" in Supplier Self Service configuration. If this is not done, the Document Date filter will
not work as expected.
For more information about the valid entries, which need to be maintained, refer to "Configuring
Layout" section of "Configuring the Supplier Accountant app in VIM" in VIM Configuration Guide.
11.10 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. OpenText is working on a fix of this problem. Contact OpenText
Customer Support for more information, referring the issue number VIMI-20444.
11.11 VIMI-20568
After upgrade to VIM 7.5 SP7, a short dump can happen in VIM DP indexing screen (called from DP
workflow or to display a document from VIM Analytics). The runtime error is
CX_SY_RANGE_OUT_OF_BOUNDS and it happens in the program /OPT/SAPLCP_FG9C1.
OpenText provides a correction instruction for this problem. Contact OpenText Customer Support for
more information, referring the issue number VIMI-20568.
63
11.12 VIMI-20550
After upgrade or installation of VIM BC Solution OTBCSL03 delivered with VIM 7.5 SP7, a short dump
can happen during BC inbound processing. The runtime error is CX_SY_DYNCALL_ILLEGAL_FUNC
and it happens in the program /OTX/PS03_CL_VIM_MODULE_CC_VAL. OpenText provides a
correction transport for this problem. Contact OpenText Customer Support for more information,
referring the issue number VIMI-20550.
11.13 VIMI-20615
Some translation in Fiori Apps like Enter Cost Assignment are missing. They will be delivered in
Support Package 8.
11.14 VIMI-20799
Do not use check setting “S” for Enter Cost Assignment App:
In VIM customizing /n/OPT/SPRO transaction - navigate to Vendor Invoice Management > Fiori
Configuration > Enter Cost Assignment > Enter Cost Assignment Check Settings:
Do not use S: stronger check.
It might lead to dumps when opening documents in the App (due to missing SAP customizing).
64
65
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 © 2017 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.
66

OpenText Vendor Invoice Management 75 SP7 Release Notes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Vendor Invoice Management 75 SP7 Release Notes

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

for SAP® Solutions

Product Released: 2017-12-18

Release Notes Revised: 2018-05-03

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

4 New Features .......................................................................................................................... 10

5 Packaging and documentation............................................................................................... 19

10 Documentation Extensions .................................................................................................... 62

1.1 Release Notes revision history

2017-12-18 First release.

New features, Fixed Several missing entries added, some entries

Corrected delivery information for OTBCSL03,

Corrected delivery information for main VIM

Added information about a transport for Fiori

2018-02-09 New features Minor corrections in features details.

2018-02-19 Post-installation Minor corrections regarding BC set activation.

New technical package names for OTBCSL03

2018-02-28 Known issues New known issues entry for VIMI-20799

5.1.4 VIM Business

10. Documentation Added for BW information missing in VIM

Correction for details on the new feature, VIMI-

Change of transport name for Fiori perspectives

2018-05-03 Fixed issues Removed VIMI-19966

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

3.1 SAP Prerequisites

3.2 Prerequisites on Archive Server (VIMI-4180)

4.1 Disabling withholding tax warning message “Withholding tax

Product Code = 005

4.3 Spanish localization: SII Support (VIMI-18756)

Option 3) Based on a custom field in BKPF

4.4 Implementing custom field validation in the DP indexing screen

*" 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

*" INDEX_ITEMS STRUCTURE /OPT/CIDX_ITEMS

*" INDEX_WTAX STRUCTURE /OPT/CIDX_EWHTAX

*" RETURN STRUCTURE BAPIRET2

Description: DP indexing screen - validation exit

Value: user exit function module name

Sample function module source code:

ls_return TYPE bapiret2,

lv_mesg TYPE sy-msgv2.

CHECK ok_code(4) <> '%_GC'. "skip plug in commands

CALL FUNCTION 'BALW_BAPIRETURN_GET2'

APPEND ls_return TO return.

4.6 New customizing for mandatory comment when declining an

 In “Custom1-Name” enter: COMMENT_AT_REJECT.

4.7 New business rule: SCB Indicator / Supplying Country Missing

4.8 Restricting ALV layout for process logs (VIMI-18719)

This is implemented at the following locations:

 Display of DP process and approval logs in VIM Workplace

The recommended approach to restricting the ALV display:

4.9 Changing logical system on VIM tables (VIMI-18607)

Program name: /OPT/VIM_REPLACE_LOGSYS (no transaction code)

 Logical system “From” and “To”

The results log will be shown as output.

4.10 Support for branch code – Thailand specific (VIMI-19339)

4.11 Additional accounting data section in coding templates when

4.12 Initial sorting in the Approval Portal inbox (VIMI-18087)

4.14 Configuration of timeout for Approval Portal web requests

4.15 Refreshing the Approval Portal inbox after using a custom

4.16 Improvements in the invoice inquiry status display in the

4.17 Search Help support in additional accounting data area in