You are on page 1of 53

OpenText Vendor Invoice Management

Release Notes
7.5 SP2
Product Released: May 8, 2015

Contents
OpenText Vendor Invoice Management Release Notes .................................................................... 2
1

Introduction .................................................................................................................................... 5
1.1 Release Notes Revision History ................................................................................................ 5

Support Package Introduction ...................................................................................................... 6

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

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


4.1 VIMI-14220 Automatic Vendor Group Change .......................................................................... 8
4.2 VIMI-14496 New VAN Selection with specific scenario Fiscal Year Changed ..................... 8
4.3 VIMI-15019 Column sequence in vendor data download ......................................................... 8
4.4 VIMI-14759 VIM version switch for technical upgrades to VIM 7.5 ........................................... 8
4.5 VIMI-14181. Changed behavior of duplicate check .................................................................. 9
4.6 VIMI-14361. Letting a business rule (process type) run only once per document .................... 9
4.7 VIMI-14279 User exit to provide data for the metadata interface at ICC extraction ................ 10
4.8 VIMI-14454 Metadata interface for ICC validation .................................................................. 10
4.9 VIMI-14453 Better interface for customer sort of extraction and validation queue ................. 10
4.10

VIMI-3193 Move document to workflow after ICC retry limit reached ........................ 10

4.11

VIMI-14525, VIMI-14577: Multi Refer ......................................................................... 11

4.12

VIMI-14625 Posting withholding tax with zero values ................................................ 12

4.13

VIMI-12253 Tax Jurisdiction Code determination based on WBS .............................. 12

4.14

VIMI-14513 Mark for Training (ICC) button in Indexing Screen ................................. 12

4.15

VIMI-14984: New version of license report ................................................................ 13

4.16
VIMI-14579 Support of PO number and invoice category in Incoming
Document Handler ................................................................................................................... 13

4.17

VIMI-14904 Automatic display of invoice image in Approval Portal ........................... 13

4.18

VIMI-13372 SAML Authentication method for Web Approval Portal .......................... 13

4.19

VIMI-14309 Support of iOS8 by VIM Mobile Solution ................................................ 13

4.20

VIMI-14213 Supplier Self-Service On-Premise Solution ............................................ 13

4.21

VIMI-14916/14978 Changed behavior of withholding tax processing ........................ 14

Business Center Foundation (ABAP) Limited Use. ............................................................... 16


5.1 General Information ................................................................................................................. 16
5.2 Invoice Approval on FIORI application .................................................................................... 16

OpenText Vendor Invoice Management 7.5 SP2 Release Notes


2

Packaging and Documentation .................................................................................................. 18


6.1 Packaging and Delivery Information ........................................................................................ 18
6.1.1

ABAP Package ........................................................................................................... 18

6.1.2

VIM Gateway Component .......................................................................................... 18

6.1.3

Non-ABAP Packages ................................................................................................. 19

6.2 Documentation ........................................................................................................................ 20


6.3 Related Documentation ........................................................................................................... 20
7

Supported Environments and Compatibility ............................................................................. 22


7.1 OpenText Product Compatibility .............................................................................................. 22
7.2 Language Support ................................................................................................................... 22

Installation, Upgrade, and Patch Notes ..................................................................................... 23


8.1 Installation Notes ..................................................................................................................... 24
8.2 Prerequisites of the Approval Portal ........................................................................................ 24
8.3 OCR Prerequisites ................................................................................................................... 24
8.4 Prerequisites on Archive Solution ............................................................................................ 25
8.5 SAP Installation ....................................................................................................................... 25
8.6 Business Configuration sets activation .................................................................................... 25
8.7 Approval Portal Downward Compatibility Matrix ..................................................................... 25
8.8 Supported Web Browsers ........................................................................................................ 26
8.9 Supported Operating Systems for Mobile Devices.................................................................. 27

8.10

Upgrade Notes ........................................................................................................... 27

8.11

Critical Patches ........................................................................................................... 28

Fixed Issues .................................................................................................................................. 29


9.1 Document Processing (DP) ..................................................................................................... 29
9.2 Invoice Approvals .................................................................................................................... 35
9.3 Web Approval Portal ................................................................................................................ 38
9.4 Incoming Document Handler (IDH) ......................................................................................... 40
9.5 Invoice Exception .................................................................................................................... 40
9.6 VIM Notifications ...................................................................................................................... 41
9.7 VIM Analytics (new VAN) Report and VAN Liability Report ..................................................... 41
9.8 Central Reporting and Other Reports ...................................................................................... 42
9.9 VIM Workplace ........................................................................................................................ 43
9.10

Customizing ................................................................................................................ 44

9.11

KPI Dashboard ........................................................................................................... 44

9.12

Business Warehouse .................................................................................................. 44

10 Mandatory Post Installation Activities ....................................................................................... 46

OpenText Vendor Invoice Management 7.5 SP2 Release Notes


3

10.1

Activate BC Set /OTEXVIM/VIM75_SP2_CUSTOMIZING ........................................ 46

11 Post Installation Activities .......................................................................................................... 47


11.1

Resolve conflict with customizing related to ARIBA integration ................................. 47

11.2

Install transport with layout variants (VIMI-14877) ..................................................... 47

11.3

Update Database for New VIM Analytics (VAN) Report ............................................. 47

11.4

Changes in BDC 41 (VIMI-12977) .............................................................................. 47

11.5

Mapping for WBS element (VIMI-14605) ................................................................... 48

12 Documentation Extensions ......................................................................................................... 49


12.1

Upgrade Guide ........................................................................................................... 49

12.2

User Guide ................................................................................................................. 49

12.2.1 Change Chapter 4 Working with the DP Dashboard ............................................... 49


12.2.2 Change Chapter 4 Working with the DP Dashboard ............................................... 49
12.2.3 Add chapter 9 - Approving Invoices Using the Fiori Invoice Approval
Application .................................................................................................................. 51
13 Known Issues ............................................................................................................................... 52
14 Contact Information ..................................................................................................................... 53

OpenText Vendor Invoice Management 7.5 SP2 Release Notes


4

1 Introduction
These Release Notes provide an overview of OpenText Vendor Invoice Management 7.5 SP2,
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 the OpenText Knowledge Center
(https://knowledge.opentext.com/) for any patches or documentation updates that may have been
posted after the initial release of OpenText Vendor Invoice Management 7.5 SP2.

1.1 Release Notes Revision History


Revision Date

Sections Revised

Description of Revisions

11-May-2015

Packaging and Delivery

Minor changes for Business Center

Information

13-May-2015

Business Center

Change in the description of limitations of the Fiori

Foundation

approval app.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

2 Support Package Introduction


Welcome to OpenText Vendor Invoice Management (VIM). VIM is a prepackaged composite
application that works with existing SAP ERP systems to streamline accounts payable operations.
Support Package 2 (SP2) contains quality improvements as well as enhancements for OpenText
Vendor Invoice Management 7.5. Therefore the installation of SP2 requires the prior installation of
VIM 7.5 SP1. 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 SP2 and follow the
instructions given.

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

SAP ERP 6.0 of OpenText Vendor Invoice Management 7.5

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

3 Installation
This chapter gives some hints for the installation of Support Package 2 for Vendor Invoice
Management (VIM) 7.5. For the detailed installation description read the VIM 7.5 Installation Guide. If
you are upgrading to VIM 7.5 from older VIM versions, please also read VIM 7.5 Upgrade Guide.

3.1 SAP Prerequisites


Make sure that you already have VIM 7.5 SP1 installed.

Caution
Any repairs made to the VIM objects will be overwritten by SP2.

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.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

4 New Features
OpenText Vendor Invoice Management 7.5 SP2 includes the following new features.

4.1 VIMI-14220 Automatic Vendor Group Change


The vendor group is automatically updated on the indexing screen if vendor number or
company code are changed.
It is also automatically updated during business rule run.

4.2 VIMI-14496 New VAN Selection with specific scenario Fiscal


Year Changed
In the VIM Analytics (VAN) report, a new scenario is available in the drop down list of
selection field Specific Scenario: Fiscal Year Changed. With this additional scenario it is
possible to select all invoice documents that ran through the year end program of VIM. In
other words: It is possible to select all invoice documents whose SAP invoice documents
were deleted due to a change in the year end posting period.
The SAP status Fiscal Year Changed is no longer available in the drop down list of selection
field Selected Status.

4.3 VIMI-15019 Column sequence in vendor data download


The column for IBAN has to be the first column of the bank data in the transfer structure. Due to ICC
design (bulk load) and ICC snap match, this is a way to improve vendor recognition.

4.4 VIMI-14759 VIM version switch for technical upgrades to VIM


7.5
A new Z-constant is introduced with VIM 7.5 SP2 to allow technical upgrades. To make your VIM 7.5
system behave in the same way as 6.0/7.0 in regard to Business Rules Framework / Logic Modules,
create a new entry in the table /PTGWFI/Z_CONST, using the transaction SM30 (Technical Version
Switch):

Product code: 005


Version: empty
Constant name: VIM_VERSION_SWITCH
Constant description: VIM version switch for 7.5 upgrade
Constant value: 700

If the constant is set to 700, the logic modules will not be called even for 7.5-specific document types.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

The business rules (document process types) will be called according to their definition. To return to
standard 7.5 behavior, make the constant value empty or completely delete the record from the table.
More information on upgrade options is provided in the VIM 7.5 Upgrade Guide.

4.5 VIMI-14181. Changed behavior of duplicate check


In older versions, the duplicate check automatically included the field currency when an amount was
configured in the duplicate check customizing.
Since VIM 7.0 SP6/VIM 7.5 SP2 this automatism is removed. Field currency is not automatically
checked during duplicate check, it has to be customized explicitly.
This change was done to avoid duplicate postings which occurred if a wrong or empty currency was
delivered, for example during OCR recognition or other input channels. In these cases, it could
happen that a duplicate was not found due to the wrong currency check.
The new default delivery is a duplicate check without currency which differs from earlier version. This
can lead to a higher amount of possible candidates for duplicate check. For upgrade customers, it is
recommended to review the current duplicate check settings and include the field currency (WAERS)
to the customizing, if necessary.

4.6 VIMI-14361. Letting a business rule (process type) run only


once per document
VIM executes each process type check every time business rules are run with finer control available
with Business Rules Framework. If in some cases, it is needed to let a business rule (process type
check function) run only once per document, a new function module is now available to achieve this. A
configuration change is required for each DP document type:
In VIM customizing, Process type determination sequence, enable Bypass for your process type and
in the sequence steps, insert the function module /OPT/VIM_BR_RUN_ONCE as the first step,
moving the standard check function to the second step (the example below is with the process type
413):

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

4.7 VIMI-14279 User exit to provide data for the metadata interface
at ICC extraction
A new user exit 005 ICC_ADD_METADATA was created to provide data for the metadata interface at
ICC extraction immediately after document creation. The template function is
/OPT/VIM_ADD_METADATA_TEMPLATE.

4.8 VIMI-14454 Metadata interface for ICC validation


The metadata interface was implemented for ICC validation.

4.9 VIMI-14453 Better interface for customer sort of extraction and


validation queue
New user exits 005 CUSTOM_ICC_EX_SORT_N and 005 CUSTOM_ICC_VA_SORT_N were created
to allow a more performant sort of the queues. The template functions are
/OPT/VIM_IF_GET_NEW_TEMPLATE for the extraction queue and
/OPT/VIM_IF_GET_VAL_TEMPLATE for the validation queue.

4.10 VIMI-3193 Move document to workflow after ICC retry limit


reached
A new option was introduced to move the document automatically to workflow after the retry limit for
ICC extraction or ICC validation has been reached. This option can be activated by a new field in
table /OPT/VIM_RETRY where the retry parameters are maintained. Activation is possible separately
for extraction and validation.
This flag is considered by the DP_TRIGGER program and if the flag is active, any documents in the
Retry limit reached status will be moved to workflow.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

10

Notes:
If you want to move a document from the Retry limit reached state to workflow using
the IDH admin tool, you have to use the Change status button. The Trigger button is
not accepted in this case.
If you activate the flag for automatic move to workflow it will work on all documents in the
Retry limit reached status. So be sure, that you have no old and forgotten documents in
this state, which you do not want to be moved. If you have such documents, remove
them using Discard image.

4.11 VIMI-14525, VIMI-14577: Multi Refer


It is now possible to refer an approval step to several referees at once.
This function is available in web approval (new UI) and SAP approval:

When using the Wait for Feedback option, the approval step waits till all refers are done.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

11

4.12 VIMI-14625 Posting withholding tax with zero values


In certain cases when posting PO invoices, it may be necessary to post some lines of withholding tax
with zero values, although the value calculate according to customizing is not zero. This is now
supported by VIM, provided that OSS note 1803535 or the corresponding SAP support package is
implemented in your SAP ERP system.
Enabling the posting of withholding tax values with zero functions in the following way:
It first needs to be enabled in VIM settings by creating a Z-constant entry in the table
/PTGWFI/Z_CONST (in the transaction SM30):
Product Code:
Product Version:
Constant name:
Description:
Constant Value:

005
empty
WHT_POST_ZERO
Set to X to post zero WHT amount if WHT code is not entered
X

To post zero withholding tax amount for a specific withholding tax line, you need to remove the
corresponding withholding tax code in the DP indexing screen. In this case, the line will still be posted
by VIM with withholding tax code, found using the withholding tax type entry in the respective vendor
master record, but the tax amount value will be set to zero and the zero flag in SAP BAPI will be set
according to the OSS note 1803535.

4.13 VIMI-12253 Tax Jurisdiction Code determination based on WBS


The tax jurisdiction code is determined automatically when entering a WBS element in the approval
screens.

4.14 VIMI-14513 Mark for Training (ICC) button in Indexing Screen


The ICC function Mark for Training is now available in the indexing screen, tab "Process". To mark
an invoice for training, the Button Training needs to be pushed:

Next to the button, the current training status is shown. If the training process has already started, the
button Training will not be active.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

12

In the index header configuration, (Document Types --> Index Header Configuration), the field
"MARK_TRAINING" needs to be set to "Display Only", "Input" or "Required".

Other prerequisites to be displayed: field DOC_ARC_DOC_ID (XML data from ICC) is filled for this
work item. Please refer to configuration guide, chapter 16.3.2 (constant XML_AR_DELETE_EARLY)

4.15 VIMI-14984: New version of license report


The VIM license report is enhanced to integrate the Business Center Foundation licensing report.

4.16 VIMI-14579 Support of PO number and invoice category in


Incoming Document Handler
Incoming Document Handler classes now support PO number and invoice category in the IDH header
data. This allows, in particular, to transfer those fields from the Document Pipeline directly without
using the dynamic mapping.

4.17 VIMI-14904 Automatic display of invoice image in Approval


Portal
A flag for automatically opening the invoice document on opening an invoice has been implemented
for the Approval Portal (new UI).

4.18 VIMI-13372 SAML Authentication method for Web Approval


Portal
Web Approval Portal (new UI) now supports SAML authentication.

4.19 VIMI-14309 Support of iOS8 by VIM Mobile Solution


VIM Mobile Solution has been adapted to support iOS8.

4.20 VIMI-14213 Supplier Self-Service On-Premise Solution

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

13

Supplier Self Service On-Premise Deployment is a new feature released. The Supplier Self Service UI
is completely available on SAP NetWeaver Gateway UI Repository stack.
SAP Gateway Services delivered as part of the On-Premise solution also work for Supplier Self
Service HANA Cloud deployment as Java Application.
The Supplier Self Service On-Premise Solution configuration is now documented in latest version of
VIM Configuration Guide.

4.21 VIMI-14916/14978 Changed behavior of withholding tax


processing
A new business rule Check Withholding Tax Data has been introduced to prevent documents to be
posted in background without anybody checking the withholding tax (WHT) data and confirming the
check in field Withholding Tax Checked. If relevant data are changed on the indexing screen or
during coding the field entry Withholding Tax Checked is removed.
It is now possible to post SAP standard WHT base amount and amount instead of the values on the
indexing screen by clearing WHT base amount and amount. The WHT code will then be used to
retrieve standard values.
For posting of WHT types without withholding tax the WHT code has to be removed.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

14

FI or MM

WHT Code

WHT Base
Amount

WHT Amount

Index screen

Filled

Filled

Filled

POSTED

Filled from
Index screen

Filled from Index


screen

Depending on Zconstant

Delta to
SAP

WHTAX_AMT_TR

(from index
screen or
calculated)
FI or MM

Index screen

Filled

Empty

Empty/Filled

POSTED

Filled from
Index screen

Retrieved from
vendor

Depending on zconstant
WHTAX_AMT_TR

(from index
screen or
calculated)
FI or MM

Index screen

Empty

Empty/Filled

Empty/Filled

POSTED

Empty

Empty

Empty

The following new Z-constants have been introduced:


Product
Code
Constant
005

Description

Default
Value

WHT_EXIT_BAPI Exit FM for WHT data BAPI transfer


User Exit for customer specific determination whether withholding tax data are
transferred to background posting from VIM or from SAP. The template for this
function module is /OPT/VIM_WT_BAPI_TRANS.

005

Set to X to calculate WHT net amount from gross and


WHT_CALC_NET tax instead of using header net amount.
X

005

Set to X to transfer indexing screen WHT amount


value to posting. If empty the WHT amount is
WHTAX_AMT_TR calculated from WHT base amount.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

15

5 Business Center Foundation (ABAP) Limited Use.


5.1 General Information
Starting with VIM 7.5 SP 2 and VIM 7.0 SP 6 customers are entitled to use OpenText Business Center
for SAP Solution Foundation (ABAP) to implement additional aspects of their Accounts Payable
process.
As part of this limited use, VIM 7.5 SP 2 and VIM 7.0 SP 6 are providing a Fiori app for Invoice
Approval. This Fiori app is 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.
Definition of limited use of Business Center Foundation ABAP:

Clients are only allowed to use OpenText Business Center for SAP Solutions Foundation
(ABAP) for processing of invoice documents inside the SAP Accounts Payable process.
Clients 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 e.g. use of the generic Fiori Task App, use of the Business Center
Workplace, creation or change of vendor master triggered by an incoming invoice, reapproval 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.

For the list of supported browsers and mobile devices, check the latest version of Release Notes for
Business Center for SAP Solutions.

5.2 Invoice Approval on FIORI application


Invoice Approval is now available on web and mobile UI enabled for SAP FIORI. The functionality is
limited to approval of invoices that have been completely coded. Coding of invoices is not supported.
Although any bulk functionality is currently not available, it will be supported with a following Service
Package.
Please note that the Fiori app can be used only by users with a corresponding SAP account.
For improvement of the overall performance, changes have been implemented on the function
modules that are used for invoice approval which are described in VIMI-14792, VIMI-14793 and VIMI14929.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

16

Known problems with the application:

Action description is not fully displayed in the History log (VIMI-15146)


No data is shown in the 10th column of the item table (VIMI-15154)
Application title which is shown in the browser tab header shows default entry OpenText
Business Center (VIMI-15153)
When showing approval confirmation screen, next approver information cant be retrieved if
the invoice is locked by some other user. (VIMI-15211)
Possible to send invoice for inquiry to more than one user in same approval step (VIMI15223)
Inbox not getting refreshed after error message has been confirmed (VIMI-15224)

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

17

6 Packaging and Documentation


Downloads and documentation for OpenText Vendor Invoice Management are available on the
OpenText Knowledge Center (https://knowledge.opentext.com/).

6.1 Packaging and Delivery Information


The components and packages updated with this SP are listed below. For a complete list of all
available components please see VIM 7.5 Installation Guide.

6.1.1 ABAP Package


To install SP2, you need the following files:
SAP Version
SAP ECC 6.0

File for Support Package


D240020305028_0000018.PAT (OTEXVIM)
Q5H0020776277_0000006.PAT (HANA)

6.1.2 Language Package


15 languages are included in the cumulative language package for VIM 7.5 SP2:
VIM7.5SP2_15LANS.SAR (provided in the download file vim7.5sp2_15lans.zip).

6.1.3 VIM Gateway Component


To install VIM Gateway Component (OTVIMGW_740), please use
OTVIMGW_INST_VIM750_740.SAR

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

18

6.1.4 Non-ABAP Packages


Component

Packages
Please use the files located in
im_approval_portal7_5sp2.zip:

VIM Approval Portal

Supplier Self Service (HANA


Cloud)

IM_APPROVAL_PORTAL7_5SP2.sca,
IM_APPROVAL_PORTAL7_5SP2.sda - either .SCA
or.SDA file should be deployed.

opentext.zip - extract this ZIP into standard installation


folder specified in guides.
Please use the files located in
vim_supplierselfservice _7.5sp2.zip

6.1.5 Business Center for SAP Solutions


The table below lists all components of Business Center (BC) for SAP Solutions that are available for
use by VIM customers. Please refer to the BC Installation Guide for further information about the
installation steps, available in OpenText Knowledge Center.
Component

Packages

Business Center - Foundation


components

Please use the files located in the ISO image


OTBCFND_10.iso. The README.txt file and the BC 1.0
Release Notes provide information about the installation
of the BC components.

Solution Accelerator for Business


Center Base component

Please use the files located in


otbcsl00_inst_upg_0700_001.zip.

Solution Accelerator Invoices


component

Please use the files located in


otbcsl03_inst_upg_0700_001.zip and
otbcsl03_sp_0700_001_01.zip. The Release Notes for
Solution Accelerator for Invoices are provided in the same
download folder. Please refer to that document for more
information.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

19

6.2 Documentation
For OpenText Vendor Invoice Management 7.5 SP2, the following guides are available:

Document title
(Code number)

Available languages
English

OpenText Vendor Invoice Management for SAP Solutions 7.5 SP2 Installation
Guide (VIM-IGD)

OpenText Vendor Invoice Management for SAP Solutions 7.5 SP2


Configuration Guide (VIM-CGD)

OpenText Vendor Invoice Management for SAP Solutions 7.5 SP2


Administration Guide (VIM-AGD)

OpenText Vendor Invoice Management for SAP Solutions 7.5 SP2 Reference
Guide (VIM-RGD)

Others*

OpenText Vendor Invoice Management for SAP Solutions 7.5 SP1 User Guide
(VIM-UGD)
Note: The User Guide is not updated for VIM 7.5 SP2. User Guide 7.5 SP1 is
still valid.

OpenText Vendor Invoice Management for SAP Solutions 7.5 SP2 Scenario
Guide (VIM-CCS)

OpenText Vendor Invoice Management for SAP Solutions 7.5 SP2 Upgrade
Guide

OpenText Vendor Invoice Management for SAP Solutions 7.5 SP1 User Guide will be available in
German, French, Spanish, Japanese, Portuguese, Italian, Dutch, Russian and Chinese with VIM 7.5,
Support Package 2.

6.3 Related Documentation


For additional information about OpenText Vendor Invoice Management, or for supplemental
information about related products, refer to the following documents, which are available on the
OpenText Knowledge Center (https://knowledge.opentext.com/).

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

20

Translation Guide VIM 7.0 which provides general information around translation of VIM product:
https://knowledge.opentext.com/knowledge/cs.dll/properties/46423475

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

21

7 Supported Environments and Compatibility


7.1 OpenText Product Compatibility
For the latest compatibility information for OpenText products, refer to the Compatibility Matrix
(https://knowledge.opentext.com/go/matrix) on the OpenText Knowledge Center.

7.2 Language Support


OpenText Vendor Invoice Management is currently localized in the following languages. Future
releases may add additional languages.

Component

Languages
EN

DE

JA

FR

IT

ZH

ES

RU

NL

PT

HU

OpenText Vendor
Invoice Management

UI

Component

Languages

OpenText Vendor
Invoice Management

RO

TR

PL

CZ

SK

UI

UI

UI

UI

UI

UI = user interface only


B = both user interface and User Guide.

VIM 7.5 provides translations in other languages than English only for end user screens
(transactions and reports using in a production system by non-technical users). Translation is not
provided for configuration screens.
Language packages for the supported languages are available in the OpenText Knowledge
Center in the corresponding patch area.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

22

8 Installation, Upgrade, and Patch Notes


This section provides additional installation and upgrade information, including related or third-party
product information and any required critical patches.
VIM 7.5 contains of 6 add-on components with one to three packages each. Only the main
component (OTEXVIM) is mandatory, the other components are optional.

Component

Version

Usage

Latest Delivery

OTEXVIM

750

Main component

SP2, new

OTVIMHNA

750

HANA add on

SP2, new

OTVIMARB

750

ARIBA integration

SP1, new
Note: OTVIMARB 7.5 SP1 will
be delivered one week after the
delivery of VIM 7.5 SP2

OTVIMGW

700

Gateway component used for Supplier Self


Service (3S) for NetWeaver/SAP_BASIS up
to 7.31

(with VIM 7.0 SP3)

OTVIMGW

740

Gateway component used for Supplier Self


Service (3S) for NetWeaver/SAP_BASIS 7.40
and higher

new

OTVIMBW

700

BW component, for BW 7.0, 7.31 and 7.4

(with VIM 7.0)

OTVIMBW

700_730

BW component, for BW 7.3

(with VIM 7.0)

OTVIMSSF

600

CRM component, for Shared Service


Framework (SSF)

SP2, (with VIM 6.0 SP4)

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

23

8.1 Installation Notes


The installation of Vendor Invoice Management 7.5 is described in OpenText Vendor Invoice
Management for SAP Solutions 7.5 SP2 - Installation Guide (VIM-IGD).

8.2 Prerequisites of the Approval Portal


The approval portal is an optional component to provide invoice approval to non-SAP GUI users
through web browser applications on their desktops and mobile devices.
1

A complete installation and configuration of the VIM SAP ERP component is needed for installing
and testing the Approval Portal. Although it is possible to install the Approval Portal before the
installation and configuration of the VIM SAP ERP component, you will not be able to verify if the
installation of the Approval Portal is completed and correct.

All operating systems supported by SAP NetWeaver versions are also supported for the Approval
Portal:

Windows

UNIX

Linux

The following SAP NetWeaver environments are supported:


o

SAP NetWeaver Application Server Java 7.0 SP9 or above (including all EHP levels) with
SPNegoLoginModule

SAP NetWeaver Application Server Java 7.3 and 7.4 (including all EHP levels) with
SPNegoLoginModule

SAP NetWeaver Portal 7.0 SP9 or above (including all EHP levels)

SAP NetWeaver Portal 7.3 and 7.4 (including all EHP levels)

OpenText recommends implementing SSL (HTTPS) if security is of concern. Basic Authentication


in SPNego is using Base64 encryption which can be easily decrypted. See
http://msdn.microsoft.com/en-us/library/aa292114(VS.71).aspx for further information.

Standard sizing requirements for SAP NetWeaver Application Server Java or SAP NetWeaver
Portal 7.0 / 7.3 / 7.4 apply.

8.3 OCR Prerequisites


OpenText Vendor Invoice Management 7.5 is compatible and supported with OpenText Invoice
Capture Center (ICC) 7.5. Lower versions of ICC are not supported for VIM 7.5.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

24

8.4 Prerequisites on Archive Solution


VIM 7.5 in general is compatible and supported with any archive solution that is compatible with SAP
ArchiveLink and certified by SAP. If you are using the OCR option or the VIM Approval Portal or the
VIM Mobile Approval Portal, you must have an archive solution, which supports the SAP Content
Server HTTP 4.5 Interface.
Some specific functions (e.g. input channel batch pipeline) are only supported for OpenText Archiving
and Document Access for SAP Solutions.

8.5 SAP Installation


The description how to install the Add-on Packages is available in the VIM 7.5 SP2 Installation Guide.

8.6 Business Configuration sets activation


Activate the BC sets in the configuration client and create a transport from the BC set. Move that
transport to the desired test systems. Do not activate BC sets in the test and production environment.
Log on in English language to activate the BC sets and use the expert mode. See the Installation
Guide for more details.

8.7 Approval Portal Downward Compatibility Matrix

OAP 7.5 SP2

OAP 7.5 SP1

Compatibility
Matrix VIM 7.5

OAP 7.5

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

VIM 7.5
VIM 7.5 SP1
VIM 7.5 SP2

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

25

8.8 Supported Web Browsers


The following table lists the supported combinations of the Web Browsers and the Web Approval
Portal Versions.
Web Browser
Support Matrix

Supported Browsers and Versions


IE7

IE8

IE9

IE10

IE11

FF

Chrome

Safari

OAP 7.5

Note
To support HTML5 and the latest web technologies, we are using a new web application
framework in VIM 7.5, which does not support old browser versions like Internet Explorer
8 and below.
Firefox is supported for version 17 and higher.
Google Chrome is supported for version 22 and higher.
Safari is supported for version 5.0 and higher.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

26

8.9 Supported Operating Systems for Mobile Devices

OAP 7.5

Mobile Devices Matrix

OAP 7.5 SP2

The following table lists the supported combinations of the Operating Systems for Mobile Services
and the Web Approval Portal Versions.

iOS (5.0 & 6.0)


iOS (7.0)
iOS(8.0)
Android (> 4.0)
BlackBerry BBOS 6.0
BlackBerry BBOS10
Windows 8 Phone
Windows 8 Surface

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.

8.10 Upgrade Notes


See the upgrade section in the Installation Guide for more details.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

27

8.11 Critical Patches


OpenText
recommends
that
you
check
the
OpenText
Knowledge
Center
(https://knowledge.opentext.com/) regularly for any patches or documentation updates that may have
been posted after this release.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

28

9 Fixed Issues
This section provides information about past issues that have been fixed in this SP.

9.1 Document Processing (DP)


VIMI-9220
Amount rows changed to be displayed right aligned in the indexing screen.
VIMI-11121
You have set up your company code so that discount base amount for Non-PO invoices must be
posted as gross amount by default, but it is still being posted as net amount.
VIMI-11633
Document type determination does not work as expected when a logical expression AND is used in
the customizing.
VIMI-11654
Business Rule Invalid vendor (201) enhanced to account for deleted vendors and vendors blocked
for posting. Warning message added to the indexing screen to be shown when entering a deleted
vendor or a vendor which is blocked for posting.
VIMI-12171
CPD vendor popup is automatically opened if a CPD vendor number is entered and the name of the
vendor is not given yet.
VIMI-12453
The layout of the line items table control cannot be saved in a layout variant. The column sequence is
reset on the next call of the indexing screen (or by another user, if global variants are used).
VIMI-12977
Posting some invoices e.g. credit memos in background with BDC 41 failed since baseline date was
not correctly populated. This can be observed for invoices where the baseline date is not calculated
and entered automatically by SAP and must be entered manually while posting in dialog with FB60.
VIMI-13330
You cannot open a DP document from VAN report or cannot execute a DP work item because of an
error message displayed in a popup. The message is apparently coming from external tax system.
VIMI-13971
If a DP document has additional costs lines and the process type 107 (Unable to Match PO lines) is
active, the document stops at this process type and does not proceed to further steps.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

29

VIMI-13993
Payment terms are not refreshed, when vendor is changed in ICC validation.
VIMI-13995
Proposal function is not returning any lines if the PO vendor is not extended to the company code of
PI vendor.
VIMI-14017
Balance showing in the indexing screen is incorrect when compared with MIRO for a condition based
taxes due to wrong tax calculation.
VIMI-14029
Wrong line item proposal returned when line item delivery note exists on indexing screen.
VIMI-14045
The withholding tax handling on the indexing screen has changed:

Vendor master related search help for withholding tax code has been introduced
Add/delete buttons for withholding tax lines have been removed as they caused issues with
BDC.

VIMI-14077
Work items are not visible for substitutes after upgrade from VIM 7.0 SP2 to SP3 or SP4. This
problem is happening when substitutes for positions are used.
VIMI-14126
When changing the document type, the payment terms were not recalculated.
VIMI-14161
When auto coding is enabled for a credit memo, all credit lines are converted to debit line items.
VIMI-14199
If an exception class is entered in the Business Rule Framework schemata assignment, it is not used
during rule run.
VIMI-14218
Credit memo can be posted with payment terms different from those entered in the indexing screen.
VIMI-14246
Performance problems when executing DP workitems. The problems are caused by the updates of
the table /opt/vt_work in the function module /OPT/VIM_REPORT_BINDING.
VIMI-14256

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

30

Deleted requester ID in COA is considered while sending for Approval process from new Indexing
screen.
VIMI-14277/14267/12413/13604
Search help and value check added for several index item fields
VIMI-14272
Balance is showing incorrectly in case of DP PO Credit Memo.
VIMI-14282
Several accessibility improvements in VIM screens
VIMI-14297
Short dump is happening in some cases when executing a DP work item. The runtime exception is
CONVT_OVERFLOW with the message: Overflow when converting from "999.999".
VIMI-14323
DP workflow does not start when a document is coming from ICC with a vendor number that is
configured for withholding tax and the document has no value in the currency field.
VIMI-14334 / VIMI-14841
Archive document type is changed to default when processing IDOC documents.
VIMI-14342
Short dumps because of database deadlocks, caused by updates made by concurrent processes.
VIMI-14344
When processing several documents in a row, line item data in some invoices can be overwritten with
wrong values.
VIMI-14345
An alternate payee entered in the indexing screen is cleared, when there is no bank data for this
alternate payee but partner bank type (BVTYP) is entered in the indexing screen.
VIMI-14353
The logic module Generic: Calculate / Add bank data does not fill bank data if vendor is a payee.
VIMI-14356
You are getting an error Invalid number when executing the process option Delete & Restart DP
process, if in the same session you cancelled some other document before.
VIMI-14392
When extended withholding tax code has some exemption maintained, withholding tax is not
calculated correctly.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

31

VIMI-14393
After performing year end conversion, parked document is not posting automatically because of
incorrect posting date or because of incorrect checks in the posting routine.
VIMI-14411
The validation information interface introduced for ICC 7.0 and VIM 7.0 / 6.0 SP6 / 5.2 SP11 is
causing performance problems when a lot of documents (thousands) are waiting to be validated.
VIMI-14418
Line items of DP document can get wrong item numbers assigned when processing several invoices
in one session.
VIMI-14435
When you delete some lines in a parked PO invoice via MIR4, the corresponding DP document may
get wrong item numbers assigned.
VIMI-14440
When posting a PO invoice referring a service PO in background, the error M8 892 is shown: There
is different account assignment information in item 000001.
VIMI-14443
In case of intercompany posting, you are getting errors because GL account field status is being
checked incorrectly, although all entered data is correct.
VIMI-14456
The program to create the staging table for PO download did not consider the From date when
running in delta mode.
VIMI-14459
New Indexing Screen - Barcode is not meeting technical characteristics.
VIMI-14477
All translations for the selection values of the baseline date setting were missing.
VIMI-14479
After upgrade from VIM 7.0 SP4 to SP5, you are getting short dumps in the function module
/OPT/C_APP1_DETERMINE_PROC_918.
VIMI-14482
The search in indexing screen line items now working for amount and quantity fields.
VIMI-14506
The translations for index field Transaction (VORGANG) was missing for the Japanese language.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

32

VIMI-14541
PO proposal returns incorrect value if currencies without decimals are used in the PO and the header
currency is not entered in the DP document.
VIMI-14563
Improvements when ambiguous delivery notes are used. Now the material document numbers which
have already been assigned will be used to reduce the ambiguity in the internal proposals used in PO
posting BAPI.
VIMI-14588
Validate coding button missing in SP5.
VIMI-14599
When a DP document with OTV vendor is being posted in dialog, a short dump is generated if no
IBAN is provided.
VIMI-14603
ICC validation interface shows a difference between the counters shown as Pending Items and
Open Items.
VIMI-14605
The mapping change for WBS element made with VIMI-13968 (VIM 7.0 SP5) is causing problems
with saving and approvals of parked invoices. That configuration change has now been reverted and
the original problem is solved with a code change. Please see the Post installation section for details
about the configuration change.
VIMI-14611
In VIMI-8527, a switch was introduced in VIM 6.0 SP6 to control the action sequence within the
delete-and-reenter and cancel-and-reenter programs. This switch was not available anymore in VIM
7.0 for the delete-and-reenter scenarios.
VIMI-14626
When you enter profitability segment data in a parked document, the corresponding line item numbers
are not updated correctly in VIM tables. As the result of this, you may get wrong PS assignment to line
items.
VIMI-14641
Bulk refer in VIM Workplace or IIC not proposing any recipient (i.e. showing empty recipient list).
VIMI-14679
When using the display button in the DP indexing screen after the change of alternate payee, wrong
bank account number is displayed.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

33

VIMI-14685
Some bugs in logic of determination of archive document type have been fixed.
VIMI-14695
When you change the company code in a DP document and then try to post it in dialog, the old
company code may still appear in the batch input session.
VIMI-14704
When a DP PO invoice is getting posted in background, duplicate invoices can be posted if several
invoices for same PO are posted in parallel.
VIMI-14709
If you try to enter invoice currency in a DP document whose currency is empty, and the currency you
are entering is one that has no decimals, an error message Use the Change currency button is
displayed.
VIMI-14712
PO invoice fails to post or park in background in the following scenario.
1) PO line item level GR-IV unchecked in the Invoice Tab and Goods Receipt is unchecked in
Delivery Tab
2) Multiple account assignment with Distribution by percentage and Distribute in
sequence/Distribute to Following Row.
VIMI-14714
When you change data of a DP document that is recognized as a duplicate, and let the rules run
again, the DP process stops with another exception but the status is still Suspected duplicate.
VIMI-14736
User name and date/time are missing in the saved comment after you use the refer option.
VIMI-14741
Exchange rate of parked PO invoice document is not inherited from GR date (or supply date), as set
up in customizing of characteristic specific settings.
VIMI-14770
Issue in document type determination after upgrade to VIM 7.0/7.5 when check type B (constant
value) was used.
VIMI-14781
Indexing type not considered correctly in some scenarios to start DP workflow.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

34

VIMI-14806
Exception "Unable to Match PO Lines" is triggering incorrectly for a GR-IV PO lines with a multiple
GR lines for same line
VIMI-14815
The entered values of the delivery note list in the old indexing screen are getting lost after a business
rules rerun.
VIMI-14838
Short dump could be happening when processing DP documents.
VIMI-14868
When parking PO invoices in background, you are getting the error Quantities and units of measure
XXXX not permitted (error M8 416) in case you are using blanket POs.
VIMI-14921
DP document posting date changed during the withholding tax retrieval.
VIMI-14946
Business rule Tolerance check exception (function module /OPT/VIM_DETERMINE_PROC_406)
not stopping when exception occurs.
VIMI-14977
Field Functional Area (/OPT/VIM_1ITEM-FKBER) cleared after posting, if the functional area is longer
than 4 characters.
VIMI-14989
Tax is calculating incorrectly and causing non-zero balance on some invoices without automatic tax
calculation.
VIMI-15046
Tax auto calculation flag is not set when a DP document is created using transaction OAWD or DP
test program (transaction /opt/vim_7ax1).
VIMI-15102
Background posting of down payment invoice failed due to error: 'Field BSEG-MWSKZ does not exist
in the screen'.

9.2 Invoice Approvals


VIMI-8252
SAPGUI screens for NPO and PO approval have been unified. More space is now provided for coding
area.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

35

VIMI-8253
In the approval dashboard for posted PO documents, the fields Tax Code and Payment Terms are
displaying wrong values.
VIMI-12622
/OPT/COA_UPLOAD_REPORT does not consider cost center conversion exits and loads cost center
values without leading zeroes.
VIMI-13132
Bulk action Refer creates duplicate comments.
VIMI-13249
When you save the data in the substitutes assignment and try to exit the transaction, it is displaying a
data loss warning, although the data is already saved.
VIMI-13918
Performance improvements in the COA maintenance transaction for simple approvals
(/OPT/VIM_7CX1).
VIMI-13970
In the SAPGUI approval screen, a line filled with only WBS element or order can be entered now.
VIMI-14048
If no amount is entered on a line item, but some costs elements are entered, all entered data is lost
when saving.
VIMI-14107
The work item was not terminated properly after displaying the error message Invoice has been
processed already. The work item appeared again in the inbox of the approver.
VIMI-14200
If the same approver (for example with the same E-Mail ID, when E-Mail IDs are used for approver ID
creation) was deleted and created several times, the COA maintenance transaction could hang, going
into an endless loop in the method /OPT/CL_IAP_USERMAP_BL~COMPOSE_OPT_ID.
VIMI-14226
You have upgraded to 7.5 from older release and you are trying to approve invoices that were sent
into approvals before the upgrade. After you approve an invoice, the next approver has problems to
approve, that the next (i.e. third in the sequence) is not being found, although COA is maintained
properly.
VIMI-14227
When approving an invoice with the profitability segment, system is displaying an error Company is
not defined.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

36

VIMI-14249
You cannot save field status or field label in the approval detail field configuration.
VIMI-14373
When you try to add an attachment but cancel the process, the approval dashboard would still show
the message that the file is attached successfully.
VIMI-14374
Recent user drop down should not include deleted or deactivated user.
VIMI-14409
In Approval workflow, if some cost element in the coding line is empty, no approver was found,
although there are approvers who are allowed to approve all possible values of cost element. This is
maintained as * in the COA (VIMI-11863).
Additionally, if some cost element in the coding line is space, no entry is maintained with space or
asterisk in COA, no adequate error message was given.
VIMI-14426
Error message Invoice XXXX has no accounting info or special handling instruction occurs during
parked approvals, even if data is correctly maintained.
VIMI-14428
Error in parked NPO approvals "Invoice is not balanced. Please enter comments." occurs, even if
comments are entered.
VIMI-14540
If requester Email ID is empty in the DP document, wrong requester can be determined by VIM.
VIMI-14562
Wrong or missing accounting data prevents an invoice from being saved, although the Z-constant Do
not validate on save is enabled.
VIMI-14601
In some cases, VIM is allowing the same person to approve an invoice multiple times if they are
acting as a substitute.
VIMI-14658
PDF history doesn't include comments for posted approval scenario.
VIMI-14708
If a posted invoice does not have header tax code (asterisk is used in this case) and some line items
do not have tax code, the dummy tax code ** is propagated to such lines during invoice validation,
resulting into errors.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

37

VIMI-14723
Missing of log entries for event Approval process finished.
VIMI-14746
When you exclude some error messages in validation step and one of the excluded messages is
being returned from validation, some other error message could still be shown.
VIMI-14903
When you are entering profitability segment data in a NPO parked document, system is showing the
error message New line item needs to be saved first, before you are given a chance to save the
data.
VIMI-14919
Clicking on a custom URL function button changes the invoice amount by 100 times.
VIMI-14932
When you have configured more than one DP process option to start the approval process, the DP
workflow creates a dialog work item instead of a waiting step when starting an approval workflow. As
the result of this, after the final approval, the control does not properly return to DP workflow and the
invoice cannot be posted automatically.
VIMI-14942
Invoice lock is unexpectedly released, potentially allowing a substitute to lock the invoice while the
actual approver is waiting on the confirmation page.
VIMI-14975
If a G/L account assigned to a tax code is blocked for posting while the tax code configuration should
result in zero tax amount and therefore the account block should not be the problem, you are getting
the error message Account 13303003 TSKY is blocked for posting in DP NPO approval.
VIMI-15064
Sometimes, when using the search help for unit of measure in the details screen, the selected UOM
was not entered correctly into the document, but was replaced by *** .

9.3 Web Approval Portal


VIMI-10101
The simple Inquiry buttons are labeled as Refer and Refer Back. To make the intended action
more clear, the buttons will be renamed. The corresponding entries in invoice history will also be
changed.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

38

VIMI-13890
Wrong invoice status shown in the web approval portal for processed invoice list.
VIMI-14451 (new UI)
Save Comments is not updated in the screen, user has to navigate to different invoice and back to
see the comments.
VIMI-14587 (new UI)
Coding screen field title text is misaligned after applying SP5.
VIMI-14655
If an action user exit is used in the approval action function, and an error is returned from the exit
function, the message is shown in the portal, but when you close the message window, the invoice
data is all empty and on saving, you are getting the message Invoice not found in the stack.
VIMI-14666 (new UI)
"Handling Function" and "URL function Module" custom buttons functionality is not working from
Comments and Attachments sections.
This is a usability issue, where custom actions do not have importance on Comments and
Attachments. Now, custom actions are not visible in other action menu for Attachments and
Comments sections.
VIMI-14669 (new UI)
VIM Portal: Content of added fields is cleared when approval is aborted in the 'add comment' popup.
This fix has dependency with ABAP changes mentioned in VIMI-14655.
VIMI-14747 (new UI)
Sort on Creation Date not working
VIMI-14760
List of tax codes shown in the search help results is not determined in the same way as in SAPGUI
approval screen.
VIMI-14772 (new UI)
Image In-line is not utilizing all the spaces and has many scroll bars.
Invoice document container is adjusted to utilize the space available.
VIMI-14785 (new UI)
User is not able to see next approver when having multiple approvers in new UI.
VIMI-14899 (new UI)
PO's Cost Assignment layout is not dynamic and will not align if the screen size is reduced.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

39

VIMI-14979 (new UI)


Web Approval search returns zero invoices when COST_CENTER and GL_ACCOUNT fields are set
to drop down type in History Search fields configuration table /ORS/SCH_FLD_CFG.

9.4 Incoming Document Handler (IDH)


VIMI-13863
Some fields that are received through IDH mapping are being overwritten with blank values when the
DP workflow starts. Example fields are: tax code, VAT amount, PO number, and some others.
VIMI-14208
It was possible to reset a document that was already processed to the initial state Registered.
VIMI-14290
Program /OPT/VIM_IDH_TRIGGER creates duplicate documents.
VIMI-14407
Windows ID is not transferred from register table to /OPT/VIM_1HEAD table.
VIMI-14430
If ICC delivers a currency that is not customized in SAP exchange rates, the DP trigger stops with
mapping error.
VIMI-14471
Technical and non-technical fields are not transferred from registration table to OPT/VIM_1HEAD
table.
VIMI-14582
If some configuration is incomplete, and an IDH document cannot be processed properly, there is no
corresponding error message displayed and the document itself is not shown in the IDH monitor.
VIMI-14703
When a lot of documents are waiting to be validated or extracted, and the queue is filled up constantly
by new documents, and the standard sort is used, there is a possibility that some documents will
never be selected to be extracted/validated.
VIMI-14914
Wrong Number Range (/OPT/DOCID) used in /OPT/C_IDH_REGISTER_DOC when accessing
remote systems via RFC. Now /OPT/REGID is used and must be maintained in the called system.

9.5 Invoice Exception

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

40

VIMI-14225
Role resolution fails when using the template DOCTYPE_CC_PLANT_SCANLOC for parked FI
invoices.
VIMI-14394
No error messages are recorded in the log if background posting fails for an invoice.
VIMI-14681
Table /OPT/VIM_HD_PO (or NPO) is updated with incorrect data in some situations.
VIMI-14682
Update point numbering for entries in tables /OPT/VIM_HD_PO and /OPT/VIM_HD_NPO was not
used in a consistent way.

9.6 VIM Notifications


VIMI-14202
Agents manager doesnt receive any reminder email notifications.
VIMI-14550
Notification report ignores Days before due setting.
VIMI-14684
Short dump is generated in the notification report when an invalid Email ID is configured in the agents
user master record.
VIMI-14756
Notifications program is removing the decimals from amount values if HTML format is enabled.

9.7 VIM Analytics (new VAN) Report and VAN Liability Report
VIMI-14027
Liability Report - Wrong sort order of cost center
VIMI-14414
VAN is not showing correct status when NPO parked document is posted after the completion of
approvals.
VIMI-14391
Image is not displayed for a down payment document.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

41

VIMI-14510
Field block_pa is not updated in case a Non-PO invoice is released outside of VIM workflow.
VIMI-14520
Selection using a PO number is not working if a list of several POs is used in a DP document.
VIMI-14598
When running report only on the DP document number, the exception reason is not displayed.
VIMI-14647
Sometimes the reversal document number for a cancelled invoice is missing in the views of VIM
Analytics.
VIMI-14648
Field block_pa is not updated in case a PO invoice is released outside of VIM workflow.
VIMI-14737
xECM Integration view not displaying business workspaces for parked processes.
VIMI-14765
Update Date field is not displaying a correct value for Refer Back action in approvals after having the
VAN sync job program run.
VIMI-15124
The amount fields in the result list of the new VAN report like Gross invoice amount or Discount
Amount 1 and 2 cannot only be displayed in document currency but additionally in any user-defined
reporting currency. The reporting currency is entered in selection field Reporting Currency. The
default reporting currency was not taken from user parameter FWS properly but was USD always.

9.8 Central Reporting and Other Reports


VIMI-7337
Report for bulk change of the posting date in DP document could not be scheduled in background
because of confirmation popup.
VIMI-13646
When entry SWW_WI_EXIT_ACTIVATED in table SWLFBASHOW is activated (see SAP Notes
1755985), the Collection Report /OPT/VR_COLLECTION_REPORT does not work correctly. This
leads to wrong aggregated data after Aggregation Report is run.
VIMI-13765
The Central Audit report provides a button Link to VAN to go to the VAN report for a selected invoice

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

42

document. The new VAN report is launched instead of the old VAN report now. The old VAN report
was replaced by the new VAN report with VIM 7.5 SP1.
VIMI-14370
The year-end report does not update all approval waiting events. After the report has run, some work
items do not continue after the approval step has been carried out, but stay in status waiting for
approval.
VIMI-14485
/OPT/CL_C_PDF_LOG is deleting invoice image if the PDF log document type is the same as used
for the invoice document. An additional check is implemented. The report will cancel with error
message Archive Doc type of PDF Log must be different from invoice doctype if the customizing is
wrong
VIMI-14649
Central reports are showing incorrect data when running it in different time zones.
VIMI-14650
Exception Invalid Requester ID is triggered when copying an existing DP document with the test
program /OPT/VIM_7AX2.
VIMI-14672
Performance improvements in the data collection for automation report
VIMI-14745
Year end program changes the comments data (changed by, changed on) in parked workflow.
VIMI-14790
If the checkbox Invoices With Goods Receipt is not checked in the liability report selection screen,
and some invoices have multiple POs, the report is still showing entries with GRs.

9.9 VIM Workplace


VIMI-11975:
Added error long text for message /OPT/C_PMC_MESSAGE 071 (Workplace customizing not
complete)
VIMI-14350
When applying an ALV filter, no information is shown that the selected hits have been additionally
restricted. Also the Select All/ Deselect All buttons are not working correctly.
VIMI-14627
When changing the selected process line, the currently applied ALV variant for the line item plug-in
gets reset.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

43

VIMI-14738
When DP is supposed to process by multiple users, if any of the users reserved or started the
process on the work item, then the current agent is showing incorrectly in the VIM Workplace.

9.10 Customizing
VIMI-14574
It is not possible to copy the document type PO_75 without errors.
VIMI-14575
An error occurred in template based role maintenance when the first entry was done for a role (e.g.
VALIDATOR) where the column "Agent type" is not displayed.
VIMI-14652
The entry for log event 20100 DP document enriched was missing in table /OPT/CT_LG_EVT.
VIMI-14854
There is a short dump LOAD_PROGRAM_NOT_FOUND for program
/OPT/VR_DETAIL_FIELDS_CONFIG in the approval configuration, node Maintain Invoice Detail
Fields.

9.11 KPI Dashboard


VIMI-14363
When using the KPI collection report (/OPT/VR_KPI_COLLECTION) in delta mode, invoices that have
been finished during the last run of the KPI collection report can be skipped from data collection.
VIMI-14959
After making a multiple selection of any of the selection screen fields in KPI report, or after pressing
Enter in the selection screen, the report starts executing without giving a chance to enter other data in
the selection screen.

9.12 Business Warehouse


VIMI-14555
When extracting VIM document headers using the DataSource /OPT/VIM_DPDOC_H_TRAN, the
extraction process stopped if there were documents without currency. There were the following error
messages from the source system:
Conversion to currency &1 not possible (message class /OPT/V_REPORTS, message ID 008)
and
Enter rate & / & rate type & for & in the system settings (message class SG, message ID 105).

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

44

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

45

10 Mandatory Post Installation Activities


10.1 Activate BC Set /OTEXVIM/VIM75_SP2_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.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

46

11 Post Installation Activities


The post installation activities related to baseline customizing changes described in this chapter are
also delivered with the BC set

11.1 Resolve conflict with customizing related to ARIBA integration


If you are using ARIBA integration, and if you are using document type PO_75, you have to repeat the
configuration of steps for process type 403 and reenter the correct function module name
/OPT/VIM_DETERMINE_PROC_IDHERR (see Configuration Guide, section 24.1.1.6).

11.2 Install transport with layout variants (VIMI-14877)


Due to limitations of the BC set technology, the entries for layout variants cannot be transported in BC
sets. Therefore copy the transport EW3K900672 into the transport directory and install the transport
using STMS. You have to install the transport to every client, as the transport contains client specific
data.
The transport is available as an additional file in the directory of VIM 7.5 SP2 (similar to the language
transports).

11.3 Update Database for New VIM Analytics (VAN) Report


With the new VIM Analytics (VAN) report, new database tables have been introduced. With VIM 7.5
SP2, changes to these database tables are needed.
In case you have already VIM invoice documents created on your system, you have to get the records
in these new database tables updated. Run report /OPT/VR_ANALYTICS_750_INIT for all your VIM
documents that are of interest for the new VAN report. This report will update the records in the new
database tables accordingly. For details about report /OPT/VR_ANALYTICS_750_INIT and how to
use it, see Configuration Guide, chapter 14.1. One-time Report for Data Upload of Documents.

11.4 Changes in BDC 41 (VIMI-12977)


Perform the following changes in the BDC definitions customizing for BDC 41:
Add the following entry in Transaction Data of BDC 41:
Index: 172
BDC Field Value : /OPT/VIM_BDC_FILL_ZFBDT

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

47

After changes the transaction data looks like the following:

11.5 Mapping for WBS element (VIMI-14605)


Using the transaction SM30, change the mapping for field PS_POSID (entries with FIELDNAME =
PS_POSID) in the table /OPT/CODING_V. Enter PROJK in the field BSEG field name for all existing
entries.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

48

12 Documentation Extensions
12.1 Upgrade Guide
In case you are upgrading to VIM 7.5 from older VIM versions, the new VIM 7.5 Upgrade Guide
provides you with useful information about the upgrade options and process. It complements the
information about the upgrade provided in the Installation Guide.

12.2 User Guide


The User Guide will not be updated for version VIM 7.5 SP2. The User Guide VIM 7.5 SP1 is still in
use. However, there are some changes necessary. Please see them in this section.

12.2.1 Change Chapter 4 Working with the DP Dashboard


Add the following section to this chapter:
4.3 Marking invoices for training
Starting with VIM 7.5 SP2, the ICC function Mark for Training is available as a Training button in the
VIM indexing screen, Process tab. For more information about the function, see section Marking
Documents for Training in Invoice Capture Center Users Guide.

12.2.2 Change Chapter 4 Working with the DP Dashboard


Add the following section to this chapter:
4.6 Changing and posting extended withholding tax
The tax folder shows extended withholding tax data for appropriate company codes and vendors.
Minimum data requirement:
For PO related documents, the extended withholding tax base amount and the amount are filled if this
is customized and enough document data is available in the document:
-

Company code
Vendor
Total gross amount
PO number
Tax code for net or tax based withholding tax type

For non PO related documents, the required data is the following:


-

Company code
Vendor

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

49

Total gross amount


Currency
Posting date
At least one line item

The Withholding Tax Checked check box is available above the withholding tax table. It is important
if the business rule Check Withholding Tax Data has been activated. To successfully pass the
business rule, you must manually select this check box.
Five buttons are available in the withholding tax data section. Four buttons are for navigation within
the withholding tax table. The RETRIEVE button fills the withholding tax table with calculated
withholding tax data based on the vendor master data. It is overwriting the whole table. If manual
entries have been created before, they will be overwritten. Data retrieval requires that vendor master
and document data contain sufficient data.

Automatic indexing screen updates:


All extended withholding tax data (type, code, base amount, and amount) is automatically updated
after changing at least one of the following document fields:
-

Company code
Vendor
PO number (for PO based documents)

All extended withholding tax amounts are automatically updated after changing at least one of the
following document fields:
-

Total gross amount


Currency
Tax code
Vat amount
Auto-calc flag
Withholding tax code
Withholding tax base amount

Overview posting of withholding tax (WHT) data by VIM (if available on the DP indexing screen):
If all 3 fields (WHT code, WHT base amount, and WHT amount) are filled, the indexing screen values
are posted (not valid for amount).
If WHT base amount is missing and WHT code is filled, the data is retrieved from SAP.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

50

If WHT code is empty => no WHT is posted for this WHT type.

FI or MM

WHT Code

WHT Base
Amount

WHT Amount

Indexing
screen

Filled

Filled

Filled

POSTED

Filled from
indexing
screen

Filled from
indexing screen

Depending on Z-constant
WHTAX_AMT_TR.

Z-constant empty = calculated


from base amount
Z-constant filled = filled from
indexing screen
FI or MM

FI or MM

Indexing
screen

Filled

Empty

Empty/Filled

POSTED

Filled from
indexing
screen

Retrieved from
vendor

Calculated from WHT base


amount retrieved from vendor

Indexing
screen

Empty

Empty/Filled

Empty/Filled

POSTED

Empty

Empty

Empty

12.2.3 Add chapter 9 - Approving Invoices Using the Fiori Invoice Approval
Application
VIM 7.0 SP6 introduces the Fiori Invoice Approval Application. For a description of the Fiori Task App
(which is identical), see OpenText Business Center for SAP Solutions User Guide 10.0, Chapter 6 Fiori
Task App: Executing process steps from a mobile or web device.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

51

13 Known Issues
The following known issues exist in this release.
VIMI-14947
Compatibility mode settings are not supported for Approval Portal New Web UI.
VIMI-15112
Approval Portal New Web UI: Unwanted horizontal scroll bar is visible in Basic Data tab, when viewed
in Chrome browser. When scrolling this, unnecessary white space will be shown.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

52

14 Contact Information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1
Support: https://support.opentext.com
Knowledge Center: https://knowledge.opentext.com
For more information, visit www.opentext.com

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.

Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA and/or Open Text ULC or other respective owners.

53