Opentext Vendor Invoice Management For Sap Solutions Release Notes

OpenText Vendor Invoice Management for
SAP Solutions
Release Notes
Version 7.5
Product Released: 2014-12-19
Release Notes Revised: 2016-01-12

Contents
OpenText Vendor Invoice Management for SAP Solutions .............................................................. 2
Release Notes ....................................................................................................................................... 2
1 Introduction .................................................................................................................................... 4
1.1 Release Notes Revision History ................................................................................................ 4
2 About OpenText Vendor Invoice Management for SAP Solutions ............................................ 5

2.1 New Features ............................................................................................................................ 8
2.1.1 New VIM Analytics report (VIMI-10922) ....................................................................... 8
2.1.2 Automatic Posting (VIMI-12814) .................................................................................. 9
2.1.3 Business Rule Framework (VIMI-10179) ..................................................................... 9
2.1.4 Logic Modules (VIMI-10178) ...................................................................................... 11
2.1.5 Single Click Entry Integration (VIMI-10467) ............................................................... 12
2.1.6 Invoice references for credit memos (VIMI-3480) ...................................................... 12
2.2 Discontinued and Deprecated Features .................................................................................. 14
3 Packaging and Documentation .................................................................................................. 15

3.1 Packaging and Delivery Information ........................................................................................ 15
3.2 Documentation ........................................................................................................................ 16
3.3 Related Documentation ........................................................................................................... 17
4 Supported Environments and Compatibility ............................................................................. 18

4.1 Supported Systems ................................................................................................................. 18
4.2 OpenText Product Compatibility .............................................................................................. 18
4.3 Language Support ................................................................................................................... 18
4.4 Data base restriction for component OTVIMBW ..................................................................... 19
5 Installation, Upgrade, and Patch Notes ..................................................................................... 20

5.1 Installation Notes ..................................................................................................................... 21
5.1.1 Remove obsolete BDC entries (VIMI-13689) ............................................................. 21
5.2 Prerequisites of the Approval Portal ........................................................................................ 21
5.3 OCR Prerequisites ................................................................................................................... 22
5.4 Prerequisites on Archive Solution ............................................................................................ 22
5.5 SAP Installation ....................................................................................................................... 22
5.6 Business Configuration sets activation .................................................................................... 23
5.7 Approval Portal Downward Compatibility Matrix ..................................................................... 23
5.8 Supported Web Browsers ........................................................................................................ 24
5.9 Supported Operating Systems for Mobile Devices.................................................................. 25
OpenText Vendor Invoice Management for SAP Solutions Version 7.5 Release Notes
2
5.10 Upgrade Notes ....................................................................................................................... 26
5.10.1 Incompatibilities .......................................................................................................... 26
5.10.2 Remove obsolete BDC entries (VIMI-13689) ............................................................. 26
5.11 Critical Patches ...................................................................................................................... 27
6 Fixed Issues .................................................................................................................................. 28

6.1 Document Processing (DP) ..................................................................................................... 28
6.2 Invoice Approvals .................................................................................................................... 31
6.3 Web Approval Portal ................................................................................................................ 32
6.4 VIM Analytics (VAN) Report and VAN Liability Report ............................................................ 33
6.5 Central Reporting and Other Reports ...................................................................................... 33
6.6 Customizing ............................................................................................................................. 34
6.7 KPI Dashboard ........................................................................................................................ 34
6.8 Installation and Upgrade .......................................................................................................... 35
7 Known Issues ............................................................................................................................... 36

7.1 „UI Rendering Problem“ on the new Web UI configured as iView in SAP Netweaver
Portal .................................................................................................................................... 36
8 Contact Information ..................................................................................................................... 38
3
1 Introduction
These Release Notes provide an overview of OpenText Vendor Invoice Management for SAP
Solutions Version 7.5, 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 for SAP Solutions Version
7.5.
1.1 Release Notes Revision History
Revision Date Sections Revised Description of Revisions
2014-12-19 First release. All new content.
2015-01-16 5.7, 5.8, 5.9 Changes related to Web Approval Portal
2016-01-12 4.4 Add restriction for component OTVVIMBW
4
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.
VIM is short for OpenText Vendor Invoice Management.

 VIM is a packaged business solution.
 VIM solves a business problem - paying the correct amounts to vendors on time and with the
lowest processing cost.
 VIM delivers not technology but best-practice business processes.
 VIM provides values to customers in process efficiency, visibility and compliance.
 VIM is SAP centric.
 VIM is an add-on to your SAP ERP system, the majority of the functions and processes run inside
the SAP ERP system.
 VIM deals only with invoices / credit memos that will be posted to SAP ERP.
 VIM uses SAP technology: ABAP and SAP Business Workflow and SAP NetWeaver AS
Java/SAP NetWeaver Portal
 VIM integrates with standard SAP functions: Invoice Verification, Financial Processing, etc.
5
VIM installation landscape (within optional multiple backend scenario):
(Note: Component “Supplier Self Service” is missing in this picture)
ICC Validation
SAP Satellite
System
(S01)
Approval
Portal
ICC
SAP Central System
Extraction SAP CRM SSF
Server (C01)
Mobile
Approval
SAP Satellite Portal
System
(S02)
SAP NetWeaver
BW
Archive Server
VIM will be installed (with the same VIM version) on each of the SAP systems in the landscape (C01,
S01 and S02). VIM consists of the following components:
 ICC (Invoice Capture Center)

o Automate the capture of paper invoices by using OCR to extract invoice data.
 Document Processing
o Capture invoice metadata: header and line item data.
o Handle suspected duplicate invoices and other exceptions that arise before a SAP invoice is
created.
6
o Collaborate with others.
 Invoice Approval
o List invoices to be approved.
o Code and approve invoices.
 Exception Handling (Invoice Exception)
o Handle the exceptions that arise after a SAP invoice is created.
 VIM Analytics
o Monitor the invoices in progress in a unified dashboard.
 Approval Portal
o Approve invoices in a Web based Approval Portal running on SAP Web Application Server or
SAP NetWeaver Portal.
o Similar to Invoice Approval but with Web interface
o Intended for invoice approval by non-SAP GUI users
 Mobile Approval Portal
o Approve invoices on a Mobile based Approval Portal running on SAP Web Application Server
or SAP NetWeaver Portal.
o Similar to Invoice Approval but with HTML5 / Sencha Touch based mobile interface
supporting different mobile devices.
 SAP CRM Shared Services Framework (SSF) Integration
o Integrate VIM with SAP CRM SSF component to create Service Requests from VIM
dashboards.
o Provide VIM invoice information in Vendor Factsheet inside accounting interactions center.
o Link VIM invoices to CRM Service Requests.
 SAP NetWeaver Business Warehouse (BW) Integration
o Deliver SAP ERP extractors for VIM analytics data and SAP BW content like Transformations
and InfoCubes to enable you to define BW reports on VIM process information.
Please note that this version supports SAP ERP 6.0 only. SAP R/3 4.6c, SAP R/3 4.7 and SAP ERP
5.0 are not supported. Support for these SAP versions is available in previous versions of OpenText
Vendor Invoice Management for SAP Solutions. Further on, all SAP ERP 6.0 EHP levels up to EHP 7
are supported. Future SAP EHP levels will typically be supported with the next VIM Support Package
released after General Availability of the new SAP EHP up to one year before end of maintenance of
OpenText Vendor Invoice Management for SAP Solutions 7.5 is reached.
7
2.1 New Features
OpenText Vendor Invoice Management for SAP Solutions Version 7.5 includes the following new
features.
2.1.1 New VIM Analytics report (VIMI-10922)

The new VIM Analytics (VAN) report gives users a clear data report on their open and completed
invoices as well as the VIM workflows. VAN also includes Document Processing documents and
workflows. VAN allows you to track the documents routed through SAP workflows by VIM or even
without any VIM process.
You can use the new VAN report to check the current document status, the current agent and
exception reason of a particular invoice. Besides the result list, displaying invoice header data, there
are further views available that provide detail information to a selected invoice:
 Process View to display open and completed VIM processes together with the current workflow
status, the current agent and exception reason of this particular process
 Image View to display the scanned, linked images
 Line Item View to display the invoice line items
 History View to display the VIM process history
 Comments View to display the comments that have been added during the VIM process and
during the approval process
The new VAN supports all kind of database systems released for SAP ERP.
On a SAP HANA database system, SAP’s new in-memory, column-store database, you have the
choice between two types of data selection:
 Data selection with SAP HANA views and

 Data selection without SAP HANA views, that means using standard DDIC tables and views
The new VAN report replaces the existing VAN report.
The main advantages of the new VAN report to the old VAN report are:
The new VAN
 Is highly optimized for SAP HANA database systems.

 Provides more detail information to selected invoices:
There are several detail views available. In the process view, the user gets information about all
running VIM processes, including parallel approval and referral processes, which are not available
in the old VAN report.
 Provides a completely reworked selection-screen:
The new selection-screen was designed
o to avoid inconsistent combinations of selection fields and unexpected selection results,
8
o to be more intuitive, and
o to provide even more selection fields.
 Allows not only tracking of invoices with running VIM processes but even of invoices without any
VIM process.
 Comes with a central place of configuration in the VIM configuration tree:
The baseline is delivered with default settings for the new VAN.
 Is based on a completely redesigned database schema:
The new VAN is no longer using the database tables /OPT/VIM_HD_DP, /OPT/VM_HD_NPO,
/OPT/VIM_HD_PO, /OPT/VIM_PO_WIH and /OPT/VIM_NPO_WIH, but reading from
/OPT/VIM_2HEAD, /OPT/VIM_1PROC and /OPT/VIM_1WI_AGT instead.
2.1.2 Automatic Posting (VIMI-12814)

VIM 7.5 introduces extended configuration options to control the automatic posting of DP documents.
It is not possible to post each and every NPO or PO related document automatically in background.
There might be some restrictions because the standard SAP BAPI does not support all scenarios that
SAP standard transactions support. There also might be business related reasons that prevent a
document from being posted in background automatically.
With VIM 7.5 and above, the baseline document types PO_GLOBAL, NPO_GLOBAL and DWN_GLOBAL will
no longer get posted automatically. You must activate them to get posted automatically.
To activate the automatic posting configuration, you must configure the document type accordingly: In
the process type definition, you must configure the baseline function module
/OPT/VIM_DETERMINE_AUTOPOST for the default process type or the relevant process types for
automatic posting.
Automatic posting might fail, for example, if the scenario is not supported or if the necessary
configuration has not been implemented. In this case, the DP document is re-routed to the posting
role, which is defined in the DP Document Type.
2.1.3 Business Rule Framework (VIMI-10179)

VIM 7.5 provides a Business Rule Framework which allows customers to configure business rule
processing in a more detailed way. The usage is optional. If nothing is configured in the BRF
Schemata Assignment the business rules are carried out as usual.
In previous VIM versions, a business rule (= process type) was either set active or inactive for a
document type.
9
With VIM 7.5, the settings are more refined with respect to check status, check conditions, vendor
grouping and assignment.
2.1.3.1 Check Type / Check Status Configuration
The following business rule run states can be assigned:
 Random – it might or might not run

 Condition based (function module) - it runs only if a custom function module delivers a success
flag
 Counter based – if the customizable counter is reached, the rule runs
 Blind - the rule runs without stopping in case of an exception
 Off - rule does not run (inactive)
 Check – rule runs (active)
 Periodic - rule runs every x month (customizable) for a vendor
 Once per vendor – rule runs once
2.1.3.2 Check Condition / Check ID Configuration
Each business rule / a subset of business rules / all business rules can be assigned to a check
condition. A check condition can be
 Amount based
o A minimum amount is configured. If a document exceeds the amount, the business rule is
carried out.
 Function module based
o A custom function can be implemented. If it returns a success flag, the business rule is
carried out.
2.1.3.3 Vendor Group Configuration
Vendors can be grouped to white list / grey list / black list vendor groups. For white list vendors, the
running of business rules can be limited to the most important ones. However, grey list vendors can
be checked more intensely and black list vendors can be assigned a very strong rule framework.
2.1.3.4 Business Rule Framework Schemata Assignment Configuration
Check type assignments can be made to:
 Company Code (range)

 Vendor group
 Document Type
10
 Exception Class or Process Type
 Check Condition (ID)
2.1.3.5 Business Rule Test Tool
VIM 7.5 introduces the new /OPT/VIM_CP_TEST transaction. It calls a basic test tool for the BRF.
You can use the test tool for the following purposes:
 to show the processing steps for a group of documents that is defined by:
o DP document type
o Company Code
o Vendor
 to show the processing steps of a DP document.
2.1.4 Logic Modules (VIMI-10178)

To increase the automation of the DP process, you can use logic modules, which are introduced with
VIM 7.5.
The task of logic modules is to check whether data is missing for a document and to add the data
where possible. This data enrichment is scheduled before the business rules run. It might be useful to
also trigger some logic modules at a later point of time, for example if the user has entered data on
the indexing screen and presses Rerun Business Rules. A new business rule has been introduced
that “informs” the user that a logic module has added data to the document. Business rules are
intended to check document data whereas logic modules are intended to also change document data.
Some logic modules replace existing mapping function modules, others are completely new.
 Example for simple mapping

Determination of bank data from vendor master
 Example for complex mapping

Additional cost handling based on line items delivered and marked by OCR.
1. VIM checks whether additional costs have been planned in purchase order.
2. If unplanned additional costs exist, they are moved to header or line items according to VIM
Additional Cost Customizing.
The logic module framework is the underlying technology. It determines which logic module is carried
out at what point(s) of the process.
11
“Best Practice” in VIM 7.5 means that OpenText delivers a set of logic modules/process IDs that you
can use by assigning them to your document types, according to your processes.
2.1.4.1 Logic Module Test Tool
VIM 7.5 introduces the new /OPT/VIM_BPF_TEST transaction. It calls a basic test tool for the Logic
Module Processing. You can use the test tool for the following purposes:
 to show the logic modules

 to run the logic modules
that are configured to be called for a DP document.
2.1.5 Single Click Entry Integration (VIMI-10467)

 This feature offers SAP GUI integrated data capturing functionalities in addition to the existing
ICC validation client.
 A new VIM Indexing Screen Plug-In allows in-place access to the corresponding Single Click
Entry ActiveX control.
 Single Click Entry utilizes the SAP GUI Scripting engine for easy field based capturing of header
and line item indexing fields.
 The Single Click Entry feature only supports SAP GUI for Windows and requires ICC 7.5 as a
prerequisite.
For further documentation of this feature, see the VIM 7.5 SP1 documentation, which will be available
in the Knowledge Center in January 2015:
User Guide: 4.2 – Using the Single Click Entry Feature

Installation Guide: 5 – Installing Single Click Entry for SAP GUI
2.1.6 Invoice references for credit memos (VIMI-3480)

VIM 7.5 introduces the support of invoice references for credit memo. The invoice references can be
used in FI and MM invoices when posting credit memos to establish links to the original invoice
related to the credit memo that is being posted. SAP provides the corresponding fields in standard
transactions like FB60 and MIRO, in the "Payment" tab.
VIM provides invoice reference fields in the new indexing screen, in the header data tab. The two
fields that existed in earlier versions, "CM reference" and "CM reference date", can still be used in the
screen, but the business rules that check the data completeness (process types 121/221, "Incomplete
credit memo") are checking either those "old" fields or the new invoice reference fields, depending on
the screen status (visibility) of the new fields. The posting routines have been adjusted to pass the
new invoice reference fields into SAP documents.
12
To use the new functionality in the business rules, make the fields CM_REF_BEL, CM_REF_GJA,
and (for NPO) CM_REF_ZEI visible in the screen for your document type(s). You can set
CM_REF_NO and CM_REF_DAT to “Hide” or remove them from the field list if needed.
For the process types 121/221, "Incomplete credit memo", the characteristics configuration flag "CM
Ref No / Credit Memo reference invoice number required" can be used to control the checks for all
three new fields. Similarly to the old fields, the flag "CM Data validation" controls the checks of the
entered data against the existing SAP documents.
The posting routines will pass the values from the new fields, if they are populated, regardless of their
display status in the indexing screen.
The following new process types are delivered to use with credit memo reference fields:
 410 - Verify Credit Memo Reference (NPO)

 411 - Verify Credit Memo Reference (PO)
The process types 410 and 411 are trying to find posted invoice documents to use as a reference
through the provided “CM reference” and “CM date” fields, if the new reference fields are empty in the
document. The document number and fiscal year (and NPO line item) can be determined if there will
be exactly one document found using the provided fields and the vendor. The process types have to
be enabled by adding respective process type for DP document or characteristic, with the function
/OPT/VIM_DETERMINE_PROC_410 (same function for 411).
When a reference invoice is found, the new fields are populated and the exception “Verify Credit
Memo Reference” is triggered to allow you to verify the data.
The delivered configuration of both process types 410 and 411 contains predefined process options.
You can adjust the process options list to suit your scenarios.
In addition to enabling the new process types as required for selected DP document types, for the
combination of the process types 410/411 and DP document types, index screen options have to be
maintained for all relevant roles. Refer to the VIM Configuration Guide for more information about
configuring DP document types.
Note: If the process type 410 is not used to populate the new invoice reference fields automatically,
the field "Invoice reference line item" (CM_REF_ZEI) has to be populated manually during indexing,
normally with 1, corresponding to the number of the vendor item in the original invoice, as VIM does
not provide a default value for it like FB60 does.
13
2.2 Discontinued and Deprecated Features
The following features have been discontinued in this release:
 Old VIM Analytics available in VIM 7.0 and earlier versions: Use new VIM Analytics released in
VIM 7.5 SP1.
 Old COA – Chart of Authority available in VIM 7.0 and earlier versions: Use new COA released in
VIM 7.0 SP1/SP2.
 Old Simple /Manager Approval Flow available in VIM 7.0 and earlier versions: Use new Approval
Flow released in VIM 7.0 SP1/SP2.
 Old Indexing available in VIM 7.0 and earlier versions: Use new Indexing released in VIM 7.0
 Integrated Invoice Cockpit (IIC) available in VIM 7.0 and earlier versions: Use VIM Workplace
released in VIM 7.0
 Old UI of Web Portal available in VIM 7.0 and earlier versions: Use New UI of Web Portal
released in VIM 7.0 SP2.
14
3 Packaging and Documentation
Downloads and documentation for OpenText Vendor Invoice Management for SAP Solutions are
available on the OpenText Knowledge Center (https://knowledge.opentext.com/).
3.1 Packaging and Delivery Information

The software for OpenText Vendor Invoice Management for SAP Solutions 7.5 includes:
Component Packages
OTEXVIM  VIM 7.5 Install Package – For a new VIM installation

 VIM 7.5 Upgrade Package – For upgrading an existing VIM installation
 VIM 7.5 Exchange Package – For upgrade of the SAP installation
OTVIMSSF  VIM SSF Install Package – For a new installation

 VIM SSF Support Package 1
 VIM SSF Support Package 2
OTVIMBW  VIM BW 7.0 Install Package – For a new installation

 VIM BW 7.3 Install Package – For a new installation
 VIM BW 7.3 Exchange Package – For a BW upgrade from 7.0 to 7.3
 VIM BW 7.31 Exchange Package – For a BW upgrade from 7.3 to 7.31
OTVIMGW  OTVIMGW 700 Install Package – For a new installation of the VIM
Gateway Component
OTVIMARB  OTVIMARB 750 Install Package – For a new installation of the ARIBA
Integration Component
 OTVIMARB 750 Upgrade Package – For upgrading an existing
OTVIMARB installation
OTVIMHNA  OTVIMHNA 750 Install Package – For a new installation of the VIM
HANA Component
15
For Web Approval Portal and Mobile Approval Portal, the following components are provided
Component Packages
IM_APPROVAL_PORTAL  IM_APPROVAL_PORTAL7_5.sca - For a new installation

of VIM Web/Mobile Approval Component, either
.SCA/.SDA file should be deployed.
 IM_APPROVAL_PORTAL7_5.sda – For a new installation
of VIM Web/Mobile Approval Component,
either .SCA/.SDA file should be deployed.
 opentext.zip - For a new installation of VIM Web/Mobile
Approval, we have to extract this ZIP into standard
installation folder specified in guides.
For Supplier Self Service, the following components are provided
Component Packages
SUPPLIER_SELF_SERVICE  vimsupplierselfservice.war - For a new installation of VIM

Supplier Self Service Component, war file should be
deployed.
3.2 Documentation
For OpenText Vendor Invoice Management version 7.5, the following guides are available:
Document title Available languages

(Code number)
English Others
OpenText Vendor Invoice Management for SAP Solutions 7.5 Installation Guide
X
(VIM-IGD)
OpenText Vendor Invoice Management for SAP Solutions 7.5 Configuration

X
Guide (VIM-CGD)
OpenText Vendor Invoice Management for SAP Solutions 7.5 Administration

X
Guide (VIM-AGD)
16
Document title Available languages
(Code number)
English Others
OpenText Vendor Invoice Management for SAP Solutions 7.5 Reference Guide
X
(VIM-RGD)
OpenText Vendor Invoice Management for SAP Solutions 7.5 User Guide (VIM- See(*)
X
UGD) below
OpenText Vendor Invoice Management for SAP Solutions 7.5 Scenario Guide
X
(VIM-CCS)
(*) OpenText Vendor Invoice Management for SAP Solutions 7.5 User Guide will be available in
German, French, Spanish, Japanese, Portuguese, Italian, Dutch, Russian and Chinese with VIM 7.5,
Support Package (SP) 1.
Please note that the current version of the documentation contains some references and sections
regarding features that are discontinued in version 7.5 and not supported anymore. For more
information, see section Discontinued and Deprecated Features. The documentation set for VIM 7.5
SP1 will fix this.
3.3 Related Documentation

For additional information about OpenText Vendor Invoice Management for SAP Solutions, or for
supplemental information about related products, refer to the following documents, which are
available on the OpenText Knowledge Center (https://knowledge.opentext.com/).
 Translation Guide VIM 7.0 which provides general information around translation of VIM product:
https://knowledge.opentext.com/knowledge/cs.dll/properties/46423475
17
4 Supported Environments and Compatibility
This section provides details about supported platforms, systems, and versions.
4.1 Supported Systems

Please refer to chapter 5.
4.2 OpenText Product Compatibility

The section provides details about which versions of other OpenText products are compatible with this
release of OpenText Vendor Invoice Management for SAP Solutions Version 7.5.
Note: For the latest compatibility information for OpenText products, refer to the Compatibility
Matrix (https://knowledge.opentext.com/go/matrix) on the OpenText Knowledge Center.
No known incompatibility with other OpenText products.
4.3 Language Support

OpenText Vendor Invoice Management for SAP Solutions 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 B B B B B B B B B B UI
Invoice Management
Component Languages
RO TR PL CZ SK …
OpenText Vendor UI UI UI UI UI* …

Invoice Management
UI = user interface only

B = both user interface and User Guide.
UI* = user interface only with following restrictions:
18
For ABAP part the translation of following parts are not supported:
 Translation for all deprecated components (see section 2.2)

 Translation for all central reports.
Regarding the translation for other components:

 Web Portal is translated.
 Mobile is translated
 3S (Supplier Self Service) is translated
 BW is not translated
 CRM is not translated.
Note
 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.
 The installation package for VIM 7.5 does not contain full language support except
for English. Language packs will be available with VIM 7.5 SP1.
4.4 Data base restriction for component OTVIMBW

It is not supported to run component OTVIMBW (Business Warehouse Component) on a SAP HANA
data base.
19
5 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 six ABAP add-on components with one to three packages each and of two non-
ABAP components. Only the main component (OTEXVIM) is mandatory, the other components are
optional.
Component Version Usage Latest Delivery
OTEXVIM 750 Main component new
OTVIMHNA 750 HANA add on new
OTVIMARB 750 ARIBA integration New. Upgrade from

OTVIMARB 700 SP1 to
OTVIMARB 750 is
recommended
OTVIMGW 700 Gateway component (with VIM 7.0 SP3)

used for Supplier Self
Service (3S)
OTVIMBW 700 BW component, for BW (with VIM 7.0)

7.0, 7.31 and 7.4
OTVIMBW 700_730 BW component, for BW (with VIM 7.0)

7.3
OTVIMSSF 600 CRM component, for SP2, (with VIM 6.0 SP4)
Shared Service
Framework (SSF)
IM_APPROVAL_PORTAL 7.5 Approval Portal New
SUPPLIER_SELF_SERVICE 7.0 Supplier Self Service (with VIM 7.0 SP3)
20
5.1 Installation Notes
The installation of Vendor Invoice Management 7.5 is described in OpenText Vendor Invoice
Management for SAP Solutions 7.5 - Installation Guide (VIM-IGD).
5.1.1 Remove obsolete BDC entries (VIMI-13689)

There are some obsolete BDC entries that have to be removed in a post install activity (after the BC
sets have been activated).
Please remove steps 10, 11, and 12 in BDC procedure 1 (if they have the content shown below):
Please remove step 247 in BDC procedure 25 (if it has the content shown below):
5.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.
21
2 All operating systems supported by SAP NetWeaver versions are also supported for the Approval
Portal:
o Windows
o UNIX
o Linux
3 The following SAP NetWeaver environments are supported:
o SAPNetWeaver Application Server Java 7.0 SP9 or above (including all EHP levels) with
SPNegoLoginModule
o SAP NetWeaver Application Server Java 7.3 and 7.4 (including all EHP levels) with
SPNegoLoginModule
o SAP NetWeaver Portal 7.0 SP9 or above (including all EHP levels)
o SAP NetWeaver Portal 7.3 and 7.4 (including all EHP levels)
4 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.
5 Standard sizing requirements for SAP NetWeaver Application Server Java or SAP NetWeaver
Portal 7.0 / 7.3 / 7.4 apply.
5.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.
5.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.
5.5 SAP Installation

The description how to install the Add-on Packages is available in the VIM 7.5 Installation Guide.
22
5.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.
Logon in English language to activate the BC sets and use the expert mode. See the Installation
Guide for more details.
5.7 Approval Portal Downward Compatibility Matrix

The following table lists the supported combinations of the Web Approval Portal (OAP) and the VIM
backend versions.
OAP 7.5
Compatibility
Matrix VIM 7.5
VIM 7.5
23
5.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 doesn't 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.
24
5.9 Supported Operating Systems for Mobile Devices
The following table lists the supported combinations of the Operation Systems for Mobile Services
and the Web Approval Portal Versions.
Mobile Devices Matrix
OAP 7.5
iOS (5.0 & 6.0)
iOS (7.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.
Note
Please remark that iOS8 or later is not supported so far. We plan to support iOS8 with a
future SP.
25
5.10 Upgrade Notes
See the upgrade section in the Installation Guide for more details.
5.10.1 Incompatibilities
Selection variants for (old) VAN (program /OPT/VIM_ANALYTICS) will not be executable after an
upgrade. They have to be generated again and overwritten. So if you have installed your development
system, check the variants in your productive system as long as they are accessible, copy the
settings manually and create them again.
5.10.2 Remove obsolete BDC entries (VIMI-13689)

There are some obsolete BDC entries that have to be removed in a post install activity (after the BC
sets have been activated).
Please remove steps 10, 11, and 12 in BDC procedure 1 (if they have the content shown below):
Please remove step 247 in BDC procedure 25 (if it has the content shown below):
26
5.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.
Caution
It is strongly recommended to install Support Package 1.
For upgrade from lower versions of VIM it is strongly recommended to upgrade to VIM 7.5
SP2.
27
6 Fixed Issues
This section provides information about past issues that have been fixed in this release. The list
contains the fixed issues since VIM 7.0 SP4.
6.1 Document Processing (DP)
Issue Name Issue Description
VIMI-8945 Line item mapping was skipped in case of error in header mapping.
VIMI-12187 Added a new Z Constants DELAY_DOC_CONF, DELAY_DOC_CONF2 to delay the

document confirmation after execution of update through Update API.
VIMI-12295 New value ‘C’ of Z constant VIM_CENTRAL_PROCESS can be used in all locations,
where a workflow is started via /OPT/VIM_START_DOC_PROCESS_ICC. Value ‘C’
means that the DP workflow will be started directly by a function call on the local
system and not via RFC.
VIMI-12615 When the DP workflow is triggered from ICC, if there is any dump that happens in the
RFC after triggering the DP workflow, there is the possibility of creating duplicate
workflows for the same document.
VIMI-12693 Short dumps are being generated in foreground and background processes because
of deadlocks on the tables /OPT/VIM_CWHTAX and /OPT/VIM_WHTAX.
VIMI-12713 Tax on unplanned delivery costs is not taken into account when calculating the
balance of a PO invoice in DP indexing screen.
28
VIMI-12769 You are using line by line tax calculation and SAP OSS Note 1692637 and related (or
corresponding support package) has been implemented in your system. While
approving a Non PO invoice, or in background posting, you are getting an error FF
747 (“The tax amount must not be greater than the tax base”).
This correction enables the use of tax item counters for line-by-line tax calculation. To
enable the new logic, in the transaction SM30, table /PTGWFI/Z_CONST, create an
entry for the constant 005 / USE_ITEM_COUNTER as shown in the screenshot
below. Setting the value to X activates the logic.
VIMI-12827 Liability Report has an issue with DP Line view during interactive display of DP
document.
VIMI-12836 Duplicate check is considering the reversal documents in case of NPO documents.
VIMI-12854 Without entering the line item number, enter the company code or other data, select
the same line and click on insert (+) button. The system is going to dump in the new
indexing screen.
VIMI-12857 If a PO invoice line item intentionally does not have a tax code entered, the tax code
gets defaulted either from the invoice header or from the PO. This can now be
prevented by setting the value of the new constant 005 / NO_DEF_LINE_TAXCODE
to X.
VIMI-12890 In ICC Admin Tool while changing the Status of a particular DP in combination with the
option “Move forward to Workflow”, a DP workflow will be started. But the Channel ID
of the new started DP workflow is always “ICC”, even when the customer uses
another Channel ID like IDOC or ICC_EMAIL.
VIMI-12892 ICC cleanup program “/OPT/VIM_ICC_CLEANUP” is not deleting all the entries from
the agent table.
VIMI-12904 During the DP process, an exception “Vendor Mismatch” (ID 153) triggers incorrectly.
29
VIMI-12945 Test mode of program /OPT/VIM_DP_TRIGGER kept the documents locked.
VIMI-12950 The DP workflow goes into an endless loop and ends with an error when you exit DP
dashboard with the command /END.
VIMI-12960 When using the option “Delete and Re-enter” for a Parked invoice, the new document
item is not created.
VIMI-13033 If no additional costs qualifiers are customized in VIM “Additional Costs Qualifiers –
Definition”, all PO invoice line item texts are set to “Additional Costs”.
VIMI-13054 When viewing a posted DP document, you click on the “Display messages” button
and some messages are being displayed although you do not expect any and the
document is posted without problems.
VIMI-13082 If a vendor has an “head office” entry in vendor master, the withholding tax is not
taken from the head office vendor but from the invoice vendor (which is the branch
office).
VIMI-13103 Definition length of field /OPT/VIM_1RHEAD VEND_NAME is only 31 in screen 3052

of old indexing screen. Changes also extended for Approval screen.
VIMI-13119 In the new indexing screen, it does not allow to execute any process option, if there
are mandatory fields in the screen to be filled. This issue was fixed as mentioned
below.
1. As part of this fix, a new field called “Mandatory Check not Required” is introduced
in the process option configuration.
2. If user enables the check box, system will not stop the user even if the mandatory
fields exist in the current system.
3. If there are any changes done, system will alert the user by showing a popup
message (i.e. when this check box is enabled for the current process option) if clicks
‘Yes’ system stops in the current screen. Once user saved the data then only it allows
further.
VIMI-13191 DP Workitem is created with 0000000000000.
VIMI-13197 When an invalid IBAN was used in the indexing screen while processing a document
for a one time vendor, there was a misleading error message from business rule 270
“Validate Bank Details”.
30
VIMI-13222
You are using an external tax calculation system, and the line item data that is passed
into the external system contains the G/L account number in a wrong field (in SAKNR
and not in HKONT).
VIMI-13223 Posting of non PO credit memos with non-automatic tax calculation fails with the error
“Inconsistent amounts” when tax is posted on vendor line and not on a separate
account.
VIMI-13356 In an FI invoice, some fields can potentially be overwritten with wrong values in the
BTE handler for process RWBAPI01.
VIMI-13370 Tax amount calculated incorrectly in case of non-decimal currencies (ex. JPY, HUF..)
for PO invoices
VIMI-13407 Suppose a PO has one line item with 2 different Unit Of Measure (UOM), the one is
Order Unit and the other is Order Price Unit and multiple goods entries are open for
this PO item. Then posting in BG of this PO was not possible and error message M8
420 "Order Price Quantity leads to incorrect PO history" was thrown.
VIMI-14339 SQL Injection found in Function Module /OPT/VIM_SELECT_DUP has been fixed.
Directory Traversal issue found in Program /OPT/COA_UPLOAD_REPORT has been
fixed. From now on it is not possible to download CAO data to a file in Application
Server or upload COA from a file in Application Server. This is to ensure that no
confidential information will be corrupted by/ disclosed to an unauthorized person.
6.2 Invoice Approvals
VIMI-12810 Sporadically a short dump occurs in SAP due to object initialization of the approval
object when executing an approval task in the approval portal.
VIMI-12863 Unable to select the PO line items in approval screen for non-posted documents
VIMI-13068 Balance calculation is not considering the tax amount in case of PO Parked credit
memo in approval screen
VIMI-13155 A short dump is generated when you attempt to maintain the COA in transactions
31
/opt/vim_7cx1 or /opt/ar_coa.
VIMI-13171 When deleting the entries from table /OPT/COA_UPLCFGC, entry re-appears with
Active flag turned on while executing transaction code /OPT/VIM_UPLCFG.
6.3 Web Approval Portal
VIMI-10632 Calculate does not convert cost centers.
VIMI-10903 The sort order of the invoice list switches to default setting after any update of the list
view has been performed.
VIMI-12677 In Approval Portal Administration the field ‘hostname’ is too short if system connection
needs to be defined through SAP routers.
VIMI-12855 Wrong column titles and formatting are shown in the result list of the Search Help
window for the field FUND_CENTER.
VIMI-12887 The issue is observed in Web Approval Portal: Supposed that the invoice has 2 line
items, only the first one is approvable by agent A, the second one is already approved
by someone else. If the agent A deletes the first line item and saves the invoice, the
second one becomes Approvable, although the agent A is not allowed to approve the
line.
VIMI-12990 The values (due_date, create date and city) show up on the Invoice Approval list but
do not show up on the Processed Invoice list.
VIMI-13085 Every time when search is used to search an invoice, one entry is added to the log.
Changes are applicable for Portal, Mobile and SAP.
VIMI-13101 RFC Runtime exception when saving the line item without company code.
VIMI-13248 The assigned DropDown in the users ‘Delegate’ area remains empty if there is no
SAP UserID assigned to the agent.
32
VIMI-13365 Field ‘earmarked funds document item (EARMARKED_FUNDPOS/KBLPOS) is not

working correctly in portal.
VIMI-13483 Item field ‘Functional Area’ is not displaying any value and data could not be stored on
the ‘Cost Assignment’ area.
6.4 VIM Analytics (VAN) Report and VAN Liability Report

Note: Old VIM Analytics will be discontinued from VIM 7.5. Due to some dependencies the Synch Job
Report will be further supported.
VIMI-12772 Sync Job is not considering the Company Code when the company code is entered in
the selection screen.
6.5 Central Reporting and Other Reports
VIMI-13205 When running reports /OPT/VR_KPI_DELETE_TARGET and

/OPT/VR_KPI_DELETE_SOURCE, if there are no entries found in the tables, it
incorrectly shows error messages.
VIMI-13233 Collection report was modified to reduce the probability of short dumps due to data
base overload issues.
VIMI-13395 VIM 7.0 SP4 did not contain the correct version of the new license report (Transaction
code /OPT/LIC_COUNT).
33
6.6 Customizing
VIMI- 12861 Transaction code /OPT/VIM_SLD open for configuration.
VIMI-13074 Baseline function module /OPT/VIM_BAPI_UE_ITEMTEXT that is used to fill the

header text during posting, was referring to an obsolete table and thus generated an
empty text.
VIMI-13121 In some SAP systems, there was a syntax error in program

/OPT/VIM_BL_M1_SUBSCREENS due to an ambiguity in a JOIN statement.
Depending on configuration, a short dump MOVE_TO_LIT_NOTALLOWED_NODATA
could occur.
VIMI-13128 TAX_EXEMPT_TEXT was configured as hidden in the baseline of the indexing screen
for some countries, although business rule to check for tax exemption text was
configured as active.
VIMI-13371 Baseline mapping for IDOC fields EIGENUINR and KUNDEUINR was not correct.
VIMI-13412
An incorrect mapping entry for a field could lead to wrong mapping results in another
field.
6.7 KPI Dashboard
VIMI-13036 Constant DASHBOARD_START_URL is too short.
To support longer URL, report /OPT/VR_KPI_CALL is enhanced for handling custom

function module. The template for custom function module
‘/OPT/DETERMINE_KPIURL_TEMPLATE’ is introduced.
When URL <=80 characters, the existing functionality remains same. When URL > 80
characters, custom function module is required.
Z constant KPI / DASHBOARD_START_URL has been changed. For more

information, refer to the Reference Guide.
34
6.8 Installation and Upgrade
VIMI-13193 There was a generation error in program /OPT/UPGRADE_ADVISOR, when VIM 7.0
SP3 or VIM 7.0 SP4 was contained in the same installation queue as the VIM 7.0
upgrade package.
35
7 Known Issues
The following known issues exist in this release.
VIMI-12421 „UI Rendering Problem“ on the new Web UI configured as iView in SAP Netweaver
Portal. For more information, see section 7.1 below.
7.1 „UI Rendering Problem“ on the new Web UI configured as

iView in SAP Netweaver Portal
Symptom and Impact:
Users who are accessing the Web Approval Portal through SAP Netweaver Portal may be facing
rendering issues on Microsoft Internet Explorer.
The issues are only related to UI aspects like missing tooltips or similar. Functional aspects are NOT
affected.
Versions affected:
VIM Web UI released with VIM 7.5 when included as iView into SAP Netweaver Portal, all MS IE
version released for the Web UI, all SAP Netweaver Portal versions released for VIM.
Background:
The new Web Approval Portal UI component comes with HTML5 content that won’t be rendered
properly in iView by default, as there are still issues on the SAP Netweaver Portal side. The rendering
issue does NOT affect any functional aspects of the Approval Portal web application. The impact is
that specific UI elements like buttons, icons or tooltips are getting badly viewed or not shown in place.
Solution:
SAP proposed a solution for this issue as described in OSS Note 1737445: SAP proposes to make
use of a new navigation mode which allows running content in a headerless framework page. This
feature will enable the standards mode rendering and therefore displays HTML5 content properly in
SAP Netweaver Portal.
Limitation:
36
When using AJAX framework portal iView can only be shown in default content view initially. It’s not
supported to open up a new headerless framework page after login directly. The prevention of
opening a new window on portal logon is a by-design limitation. The reason is that such behavior will
cause problematic situations in the portal environment. The note that references this is OSS Note
2058249.
Workaround:
The end user can manually switch on the “document mode” setting in their specific browser version:
OpenText recommends a workaround for portal users to adjust Document Mode setting in the Internet
Explorer browser manually. In developer mode (F12 key), the Document Mode parameter can be set
to a specific value that supports rendering of HTML5 content. On IE9, Document Mode should be set
to ‘IE9 standards’; in higher versions of Internet Explorer browser, Document Mode should be set to
‘Standards’ or ‘Edge’.
Note: Changes on the default document mode browser setting could cause side effects to UI of
default Portal Header frame.
It is also possible to change the browser document mode centrally for the portal in the Admin iView
template. This may affect other parts of the SAP Netweaver Portal and should therefore be properly
tested and validated. You should verify that changes don't have any impact on default Portal content
or other applications that also make use of iView technology.
37
8 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 © 2014 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 © 2014 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

Opentext Vendor Invoice Management For Sap Solutions Release Notes

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Opentext Vendor Invoice Management For Sap Solutions Release Notes

Загружено:

Авторское право:

Доступные форматы

OpenText Vendor Invoice Management for

Product Released: 2014-12-19

Release Notes Revised: 2016-01-12

2 About OpenText Vendor Invoice Management for SAP Solutions ............................................ 5

3 Packaging and Documentation .................................................................................................. 15

4 Supported Environments and Compatibility ............................................................................. 18

5 Installation, Upgrade, and Patch Notes ..................................................................................... 20

6 Fixed Issues .................................................................................................................................. 28

7 Known Issues ............................................................................................................................... 36

8 Contact Information ..................................................................................................................... 38

We also recommend that you check the OpenText Knowledge Center

1.1 Release Notes Revision History

Revision Date Sections Revised Description of Revisions

2014-12-19 First release. All new content.

2015-01-16 5.7, 5.8, 5.9 Changes related to Web Approval Portal

2016-01-12 4.4 Add restriction for component OTVVIMBW

VIM is short for OpenText Vendor Invoice Management.

(Note: Component “Supplier Self Service” is missing in this picture)

 ICC (Invoice Capture Center)

2.1.1 New VIM Analytics report (VIMI-10922)

 Data selection with SAP HANA views and

The new VAN

 Is highly optimized for SAP HANA database systems.

2.1.2 Automatic Posting (VIMI-12814)

2.1.3 Business Rule Framework (VIMI-10179)

2.1.3.1 Check Type / Check Status Configuration

The following business rule run states can be assigned:

 Random – it might or might not run

2.1.3.2 Check Condition / Check ID Configuration

2.1.3.4 Business Rule Framework Schemata Assignment Configuration

Check type assignments can be made to:

 Company Code (range)

2.1.3.5 Business Rule Test Tool

2.1.4 Logic Modules (VIMI-10178)

 Example for simple mapping

 Example for complex mapping

2.1.4.1 Logic Module Test Tool

 to show the logic modules

2.1.5 Single Click Entry Integration (VIMI-10467)

User Guide: 4.2 – Using the Single Click Entry Feature

2.1.6 Invoice references for credit memos (VIMI-3480)

 410 - Verify Credit Memo Reference (NPO)

3.1 Packaging and Delivery Information

OTEXVIM  VIM 7.5 Install Package – For a new VIM installation

OTVIMSSF  VIM SSF Install Package – For a new installation

OTVIMBW  VIM BW 7.0 Install Package – For a new installation

IM_APPROVAL_PORTAL  IM_APPROVAL_PORTAL7_5.sca - For a new installation

For Supplier Self Service, the following components are provided

SUPPLIER_SELF_SERVICE  vimsupplierselfservice.war - For a new installation of VIM

Document title Available languages

OpenText Vendor Invoice Management for SAP Solutions 7.5 Configuration

OpenText Vendor Invoice Management for SAP Solutions 7.5 Administration

3.3 Related Documentation

4.1 Supported Systems

4.2 OpenText Product Compatibility

No known incompatibility with other OpenText products.

4.3 Language Support

OpenText Vendor UI UI UI UI UI* …

UI = user interface only

UI* = user interface only with following restrictions:

 Translation for all deprecated components (see section 2.2)

Regarding the translation for other components:

4.4 Data base restriction for component OTVIMBW