OpenText Vendor Invoice Management

for SAP Solutions

Release Notes for Foundation
Version 7.6

Product Released: 2020-10-30

Release Notes Revised: 2020-11-10

Contents

1 Introduction .................................................................................................................................... 3
1.1 Release Notes revision history .................................................................................................. 3

2 Package introduction..................................................................................................................... 4
2.1 New features.............................................................................................................................. 4
2.1.1 Enhancements to Inbound component ......................................................................... 4
2.1.2 Enhancements to Process component ......................................................................... 6
2.1.3 Enhancements to Fiori component ............................................................................... 7

3 Packaging and documentation ..................................................................................................... 8

3.1 Packaging and delivery information .......................................................................................... 8
3.2 Related documentation .............................................................................................................. 9

4 Supported environments and compatibility .............................................................................. 10

4.1 Supported systems .................................................................................................................. 10
4.2 Supported clients for VIM Fiori Web UI ................................................................................... 12
4.3 Compatibility between UI and backend versions ..................................................................... 12
4.4 OpenText product compatibility ............................................................................................... 13
4.5 Archive solution prerequisites.................................................................................................. 14
4.6 OCR prerequisites ................................................................................................................... 14
4.7 Invoice Solution prerequisites.................................................................................................. 14
4.8 Language support .................................................................................................................... 14

5 Installation and upgrade notes ................................................................................................... 15

5.1 Installation notes ...................................................................................................................... 15
5.2 Upgrade notes ......................................................................................................................... 15
5.3 Mandatory post installation steps ............................................................................................ 15
5.3.1 Interface change function /OTX/PF01_UTIL_EXIT_APPL ......................................... 15
5.3.2 Calculate model size in ML repository ........................................................................ 15
5.3.3 Method parameter changes in class /OTX/PF31_CL_BPF_WI_WEB_PERS ........... 15
5.3.4 Obsolete data enrichment points ................................................................................ 16
5.3.5 Sort criteria for Store Documents Fiori App ................................................................ 16

6 Fixed issues .................................................................................................................................. 17

7 Known issues ............................................................................................................................... 18

8 Contact information ..................................................................................................................... 19

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
2
1 Introduction
These Release Notes for Foundation provide an overview of OpenText Vendor Invoice Management
for SAP Solutions Version 7.6, including new features, delivery information and supported platforms.

OpenText recommends that you read these Release Notes in conjunction with the documentation
included with the software package. If any conflicts exist, the Release Notes supersede the other
documentation.

We also recommend that you check OpenText My Support (https://support.opentext.com) for any
patches or documentation updates that may have been posted after the initial release of this product.

1.1 Release Notes revision history

Revision date Sections revised Description of revisions

15.10.2020 Initial version

10.11.2020 4.1 Supported systems Versions

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
3
2 Package introduction
This section provides an overview of OpenText Vendor Invoice Management for SAP Solutions
Version 7.6.

Caution
Read these Release Notes completely BEFORE applying the SP and follow the given
instructions.

OpenText Vendor Invoice Management for SAP Solutions helps receiving incoming documents,
capturing, processing and filing them within an SAP system. Business processes like the processing
of incoming invoices from vendors or incoming sales orders from customers are typical use cases for
OpenText Vendor Invoice Management for SAP Solutions. The product provides one platform to
automate any business process that is tightly integrated into the SAP solution stack.

OpenText Vendor Invoice Management for SAP Solutions can be connected to various inbound
channels, be it paper through scan, fax, email or IDoc. The incoming documents are stored using
SAP ArchiveLink.

After capturing the documents, the extracted data is validated against a set of business rules. Though
touchless processing is the ultimate objective, user interaction is required if an exception occurs.
OpenText Vendor Invoice Management for SAP Solutions provides efficient user experience within
SAP GUI and outside, following the design principles of SAP Fiori®. Once all exceptions are solved,
the data can be posted and saved within the SAP system.

The product offers simple configuration interfaces to define and maintain processing aspects as well
as SAP Fiori end user screens based on UI perspectives.

2.1 New features

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 includes the following new
features.

2.1.1 Enhancements to Inbound component

2.1.1.1 Business entity determination

To process business documents within SAP the determination of relevant SAP business entities is
important. A business entity represents for example the corresponding business partner or a legal
entity. Business entity determination can be used to process invoices to determine the supplier and
company code or sales orders to determine the ship-to and sold-to party. This new feature is
supported with scenario version 2 for the IES profile configuration.

2.1.1.2 Field types for custom fields

New field types for custom extraction fields have been introduced.

• barcode

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
4
 • description

2.1.1.3 Authorization for document types

Validation of documents is restricted to corresponding authorization of archive link document type.

Only relevant profiles / applications are shown within validation client.

2.1.1.4 Capture validation work center

The capture validation work center of IES allow users to reserve a document for validation. Once the
document is reserved, it is automatically opened in the Windows Validation Client when using the
Workplace Validation mode.

2.1.1.5 IES configuration

Additional configuration options are available for the document extraction in profile configuration

• Extract first / last pages

• PDF e-Text usage
• Render pages

2.1.1.6 Document registration API

New BAdi in the document registration API (webservice) now supports custom logic.

2.1.1.7 Transfer of machine learning data for IES

A Snapshot of machine learning data for a profile including models and layout can be created. This
snapshot can be used to restore machine learning data for a specific profile. Snapshot data can also
be transferred to other SAP systems. For details see Administration Guide.

2.1.1.8 Pre-learn profiles from validated extraction results of Business Center Capture for non-
invoice solutions

The pre-learning feature was limited to the invoice scenario in earlier releases. This feature is now
also available for other document scenarios, including sales orders.

2.1.1.9 Extraction of embedded information from electronic invoices (ZUGFeRD)

Embedded information of PDF documents is extracted and stored in table /OTX/PF01_T_1IMG for
following standards:

- ZUGFeRD 1.0
- ZUGFeRD 2.0
- ZUGFeRD 2.1
- ZUGFeRD 2.1.1

2.1.1.10 IES extraction result analytics

The “Inbound Administration” work center in SAP GUI includes a new node “IES Extraction Analytics”
offering the following measurements for all finished inbound registration ID’s based on IES:

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
5
 • Number of validated header fields (not blank or initial)
• Number of correctly extracted header fields
• Percentage of correctly extracted header fields
• Number of validated line items
• Number of extracted line items
• Percentage of extracted line items
• Number of validated item fields (not blank or initial)
• Number of correctly extracted item fields
• Percentage of correctly extracted item fields
• Total number of validated fields
• Total number of correctly extracted fields
• Percentage of correctly extracted fields

2.1.1.11 Enhanced “External Data” plug-in

The “External Data” plug-in in the “Inbound Administration” work center in SAP GUI distinguishes
external data results for different extraction/ validation points in case of registration ID’s based on IES:

• Extraction: Before enhancement

• Extraction: After enhancement
• Validation: Before enhancement
• Validation: After enhancement

2.1.2 Enhancements to Process component

2.1.2.1 Integration of translation service

It is possible to translate the comments within the SAPGUI and Fiori screens. A translation service
can be called within a BAdi implementation.

2.1.2.2 Data enrichment types

The configuration of data enrichments clearly distinguishes the following data enrichment types:

• Learning-based data enrichment

• Logic-based data enrichment

2.1.2.3 Data enrichment logic target fields

Target fields can be maintained for logic-based data enrichments. This ensures that learning-based
data enrichments only learn from manual user input.

2.1.2.4 Business rule to check foreign keys and fixed domain values

The class /OTX/PF41_CL_RULE_CHK_KEY_VAL can be used to configure a business rule to check

foreign keys and fixed domain values.

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
6
2.1.3 Enhancements to Fiori component
2.1.3.1 Maintenance of substitutes

Substitution maintenance for the delivered processing Fiori Apps is provided with semantic link
navigation to the standard SAP Fiori App.

2.1.3.2 Upload of additional attachments

New action dialog is provided to upload and archive attachments within Fiori.

2.1.3.3 New views for Fiori Apps

Redesigned comment and history views are available in the perspective manager.

2.1.3.4 Display filenames in the documents view

Depending on the SAP BASIS release (check SAP note 1451769) filenames (if available) are shown
in the documents view.

2.1.3.5 Capture Validation widget integration

A new perspective view is available containing a Capture Validation widget for documents extracted
by IES which can easily be integrated into any perspective layout. The widget integration offers
various capture validation capabilities, including Single Click Entry (SCE), Table Auto Complete (TAC)
and On Image Navigation (OIN).

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
7
3 Packaging and documentation
Downloads and documentation for OpenText Vendor Invoice Management for SAP Solutions are
available on OpenText My Support (https://support.opentext.com).

3.1 Packaging and delivery information

The software for OpenText Vendor Invoice Management for SAP Solutions includes the following
components.

Backend Add-Ons:

Component Delivery Description

OTBCBAS OTBCBAS_0700_006.SAR OpenText Process Base

General technical objects and basic customizing
used by VIM Add-Ons.

OTBCSL00 OTBCSL00_0700_006.SAR OpenText VIM Solution Base

Includes general technical objects for VIM Solutions
and basic objects for Purchase Orders and
Purchase Requisitions.

OTBCRM OTBCRM_0700_006.SAR OpenText VIM xECM Integration

Includes integration points to OpenText Extended
ECM.

Frontend:

Add-On for On Premise Deployment:

Component Delivery Description

OTBCWUI OTBCWUI_0740_006.SAR OpenText Process Fiori Base

Client-side UI framework for SAP ABAP Server with
SAP_UI component to run customized solution Apps
including Perspectives Management and various
views for data presentation and editing.

ZIP File for SAP Cloud Platform Neo Environment Deployment:

Delivery Description

OTBCWUI_NEO_0740_006.ZIP OpenText Process Fiori Base

Client-side UI Framework for SAP Cloud Platform to run

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
8
 Delivery Description
customized solution Apps including Perspectives Management and
various views for data presentation and editing.

3.2 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 OpenText My Support (https://support.opentext.com).

Document title (Code number) Available languages

OpenText Vendor Invoice Management for SAP Solutions 7.6 -

English
Administration Guide (VIME-AGD)

OpenText Vendor Invoice Management for SAP Solutions 7.6 -

English
Installation Guide (VIME-IGD)

OpenText Vendor Invoice Management for SAP Solutions 7.6 -

English
Security Guide (VIME-GSM)

OpenText Vendor Invoice Management for SAP Solutions 7.6 -

English
Configuration Guide for Foundation (BOCPE-CGD)

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
9
4 Supported environments and compatibility
This section provides details about supported platforms, systems and versions.

4.1 Supported systems

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 is an add-on to the following
SAP products and versions:

• SAP ERP 6.0 EHP0 up to EHP 8

• SAP ERP on HANA including SAP Simple Finance

For details Support Package levels of SAP platforms see table below.

VIM Component Software Component Release Support Package

Level

SAP_BASIS 700 0027

IW_BEP 200 0010

OTBCBAS
SAP_GWFND 740 0010
SAP_GWFND 750 0000

OTBCBAS 0700_006 0000

OTBCSL00
SAP_ABA 700 0027

SAP_APPL 600 0000

OTBCBAS 0700_006 0000

OTBCRM
OTEXRL 1050_700 0001

SAP_BASIS 750 0004

SAP_UI 751 0002

OTBCWUI
1.52.*

SAP UI5* 1.60.* -

1.71.*

The Release Notes mention the lowest release and Support Package Level that is supported.
Release and Support Package Levels which are equivalent or higher to the mentioned level can be
used. The exception to this rule is SAP UI5. For SAP UI5 only the versions mentioned below are fully
supported. For more information how to find an equivalent version read SAP Note 1978965.

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
10
If you plan to integrate Core Capture for SAP Solutions (formerly known as Information Extraction
Service for SAP Solutions Cloud Edition), a higher release of the SAP_BASIS component is required.
Older releases restrict the length of usernames in http connections to 32 characters. For details see
SAP note 2020611.

The VIM Fiori Web UI in detail supports the following UI5 versions. Older versions of OTBCWUI
should not be used anymore as they only support UI5 versions that are out of maintenance.

On-Premise:

OTBCWUI Version UI5 Version

0740_006 1.52.* / 1.60.* / 1.71.*

0740_004 SP5 1.52.* / 1.60.* / 1.71.*

0740_004 SP4 1.52.* / 1.60.*

0740_004 SP3 1.52.* / 1.60.*

0740_004 SP2 1.52.*

You can check the installed version by following the relative URL
/sap/public/bc/ui5_ui5/index.html.

SAP Cloud Platform Neo Environment:

Release Version UI5 Version

20.4 1.52.* / 1.60.* / 1.71.*

16.3.5 1.52.* / 1.60.* / 1.71.*

16.3.4 1.52.* / 1.60.*

16.3.3 1.52.* / 1.60.*

16.3.2 1.52.*

On the SAP Cloud Platform, the UI5 version can be set in the Fiori Launchpad Site settings.

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
11
4.2 Supported clients for VIM Fiori Web UI
Client OS Browsers

Desktop Windows 7, 8.1 Internet Explorer >= 11.0

Google Chrome [Latest version]
Mozilla Firefox [Latest version]

Windows 10 Internet Explorer >= 11.0

Microsoft Edge [latest current
branch for Business]
Google Chrome [Latest version]
Mozilla Firefox [Latest version]

Smartphone / Tablet iOS (iPad, iPhone) [Latest 2 Safari in “normal” mode

versions] Safari Home-Screen bookmark**
SAP Fiori Client App

Android >= 5 * Google Chrome [Latest version]

*See supported reference devices:

https://sapui5.netweaver.ondemand.com/sdk/#/topic/74b59efa0eef48988d3b716bd0ecc933

** Requires the optional configuration “Enable Inplace Document View for iPhone and iPad”

Note: The Fiori Web UI also supports the Compact/Cozy mode provided by the UI5 toolkit for
adopted content density depending on the touch support of a device.
This means that in contrast to older Fiori Web UI versions more data is displayed at the same
screen resolution, when you use the ‘Compact-Mode’.

4.3 Compatibility between UI and backend versions

To support an improved interoperability between the Fiori apps and OData services, versioning has
been introduced. The Fiori App and OData service have both a major and a minor version. In general,
the Fiori App supports all OData service versions that have the same major version and an equal or
lower minor version.

For more information, see the following table:

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
12
 OTBCWUI version Supported Minimum OTBCWSR/ Maximum OTBCWSR/
File for SCP NEO UI5 OTBCBAS version OTBCBAS version
versions
0740_006 1.71.X OTBCWSR 0740_004 OTBCBAS 0700_006
OTBCWUI_NEO_0740_006 1.60.X
1.52.X
0740_004 SP5 1.71.X OTBCWSR 0740_004 OTBCWSR 0740_004 SP4
PF07_BC_NEO_UI_03_16.3 1.60.X
.5 1.52.X
0740_004 SP4 1.60.X OTBCWSR 0740_004 OTBCWSR 0740_004 SP4
PF07_BC_NEO_UI_03_16.3 1.52.X
.4
0740_004 SP3 1.60.X OTBCWSR 0740_004 OTBCWSR 0740_004 SP3
PF07_BC_NEO_UI_03 1.52.X
0740_004 SP2 1.52.X OTBCWSR 0740_004 OTBCWSR 0740_004 SP2
PF07_BC_NEO_UI_03

It is recommended to use the latest version of the Fiori App (OTBCWUI) that is compatible with your
system landscape.

Versioning allows you to run multiple backends with different VIM component versions against the
latest VIM frontend component on the Fiori Server. In this case it must be guaranteed that the
metadata for the OData services are always retrieved from the system with the highest backend
version.

4.4 OpenText product compatibility

The section provides details about the versions of other OpenText products that are compatible with
OpenText Vendor Invoice Management for SAP Solutions Version 7.6.

Note: For the latest compatibility information for OpenText products, refer to the Compatibility
Matrix (https://knowledge.opentext.com/go/matrix) on OpenText My Support.

Product name Version Notes

10.5 SP1

16.0
OpenText Extended ECM for SAP Solutions 16.2

16.2.10

20.4

OpenText Imaging Web Viewer* 10.0.0 Minimum version

OpenText Brava! View for SAP Solutions* 16.0.0 Minimum version

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
13
* The viewer products integration is only supported in the Fiori Web UI On-Premise deployment
scenario.
4.5 Archive solution prerequisites
OpenText Vendor Invoice Management for SAP Solutions is in general compatible and supported with
any archive solution that is compatible with SAP ArchiveLink and certified by SAP.

VIM is specifically tested and validated for

• OpenText Archiving and Document Access for SAP Solutions

• OpenText Documentum Archive Services for SAP Solutions

4.6 OCR prerequisites

For OCR prerequisites and compatibility, refer to the corresponding OpenText Intelligent Capture for
SAP Solutions or OpenText Core Capture for SAP Solutions documentation and release notes.

4.7 Invoice Solution prerequisites

For Invoice Solution prerequisites and compatibility, refer to the corresponding OpenText Vendor
Invoice Management for SAP Solutions Version 7.6 documentation and release notes.

4.8 Language support

OpenText Vendor Invoice Management for SAP Solutions is currently localized in the following
languages. Additional languages may be available in future releases.

Add-on EN DE JA FR IT ZH ES RU NL PT KO CS FI HU PL RO SK SV TR

OTBCBAS B UI UI UI UI UI UI UI UI UI UI UI UI UI UI UI UI UI UI

OTBCWUI B UI UI UI UI UI UI UI UI UI UI UI UI UI UI UI UI UI UI

UI = user interface only

B = both user interface and documentation

OTBCWUI is translated within the add-on in all languages without additional language packs. This is
also applicable for the cloud delivery of the Fiori Web UI.

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
14
5 Installation and upgrade notes
This section provides additional installation and upgrade information, including related or third-party
product information and any required critical patches.

5.1 Installation notes

The installation of OpenText Vendor Invoice Management for SAP Solutions is described in the
OpenText Vendor Invoice Management for SAP Solutions Version 7.6 Installation Guide.

5.2 Upgrade notes

The upgrade of OpenText Vendor Invoice Management for SAP Solutions is described in the
OpenText Vendor Invoice Management for SAP Solutions Version 7.6 Installation Guide.

5.3 Mandatory post installation steps

5.3.1 Interface change function /OTX/PF01_UTIL_EXIT_APPL
When you use the exit to trigger after the inbound processing an own application you need adopt your
interface according to the template function /OTX/PF01_UTIL_EXIT_APPL.

5.3.2 Calculate model size in ML repository

To use new features of the IES integration it is essential that the size of each model is available in the
ML repository.

To initiate the calculation, you must execute report /OTX/PF12_P_FILL_MODEL_SIZE. This report is
just needed if you already used IES before the upgrade / installation.

The report offers two operation modes. One mode to verify if there are models without model size
information (option: Check for missing model size) and one mode to calculate and set the model size
(option: Set missing model size). The parameter OCR Profile Id is not needed.

First execute the report in check mode and if there are some findings listed in the result screen
execute the report in set mode.

Please be aware that for execution of the report the authorization object J_6NPF_ADM with
component 1 (Inbound) is checked.

5.3.3 Method parameter changes in class

/OTX/PF31_CL_BPF_WI_WEB_PERS
The following class methods use new mandatory import parameters which potentially requires to
review existing redefinitions:

• CHANGE_TABLE_CUSTOMIZING
• CHANGE_TABLE_COLUMN_SETTINGS
• TRANSFORM_ATTRLST_DATA_SAVE
• TRANSFORM_ATTRLST_DATA_BY_VIEW
• TRANSFORM_TABLE_DATA_SAVE
• TRANSFORM_TABLE_DATA_BY_VIEW

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
15
The parameter PIS_RECEIVER_TABLE_LINE of method UPD_TABLE_LINE_FROM_REL_FLD is
obsolete now and will not be populated anymore.

5.3.4 Obsolete data enrichment points

The following data enrichment points are obsolete:

• “RULE - Enrichment during business rules run”

• “PROC - Enrichment during business rules run & dialog indexing”

In case one of these obsolete data enrichment points is used please switch to another enrichment
point and review corresponding custom data enrichment implementations if applicable.

5.3.5 Sort criteria for Store Documents Fiori App

When you want to use the Store Documents App you need to maintain a sort criteria for the related
node. Access the configuration path Workplace Configuration → Navigation → Nodes and enter for
NodeID PF31_ARCHIVEan entry within Order by for table /OTX/PF01_T_SEAR with field
AR_OBJECT in ascending order.

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
16
6 Fixed issues
This section provides information about past issues that have been fixed in this release.

Issue number Issue description

BOB-4707 Connection to Core Capture for SAP solutions cannot be established (message:
'Error determining relative URI'.

BOB-5139 Incorrect node selection in Business Center Workplace

BOB-4939 / Fiori app encoding issues in lower versions

BOB-4734

BOB-4416 Increasing number of entries in cleanup program /OTX/PF01_P_IDF_CLEANUP

causes dump

BOB-4563 Inconsistent status within IES validation

BOB-3954 Fiori screen not refreshed when an attachment is uploaded

BOB-4467 Business center workplace cannot open old emails from link

BOB-4199 Documents remain in status 72 after extraction

BOB-4742 Maintaining evaluation path is not possible for validation agent administration

BOB-4461 Extraction steps are not sorted correctly

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
17
7 Known issues
The following known issues exist in this release.

Issue number Issue description

BOB-4856 The following field types are not supported for custom business entity
determination attribute fields in profile configuration:
• email
• iban_number
• range
• tax_number
• url
• address

BOB-5013 The profile description is not available in display mode of profile maintenance
screen and document type assignment screen for IES if the profile description
was maintained before the upgrade to Foundation 7.6.

If the profile description is changed at least once after upgrading to Foundation

7.6 the profile description will also be available in display mode.

BOB-5171 Field type entity_matcher and attribute_extractor for custom business entity
IES-4927 determination not fully supported. Feedback after validation is not processed and
alternative candidates are not shown.

BOB-5048 Feedback results after process end are not shown in the Inbound External Data
plugin.

BOB-4311 The comments view in the Fiori Web UI does not consider the logon user’s time
zone.

BOB-4805 With SAP UI version 1.71* in popups with table entries that can be selected, the
check buttons are not getting checked for the selected entries. These entries are
still marked and are highlighted. There is no impact regarding the functionality.

OpenText Vendor Invoice Management for SAP Solutions Version 7.6 - Release Notes for Foundation
18
8 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1

OpenText My Support: https://support.opentext.com

For more information, visit www.opentext.com

Copyright © 2019 Open Text. All Rights Reserved.

Trademarks owned by Open Text. One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
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.

19