OpenText Business Capture Center for

SAP® Solutions
Release Notes
16.7

Product Released: 2019-10-29

Contents

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

2 About Business Center Capture ................................................................................................... 4

2.1 New features.............................................................................................................................. 5

3 Packaging and documentation ..................................................................................................... 5

3.1 Packaging and delivery information .......................................................................................... 5
3.2 Related documentation .............................................................................................................. 5

4 Supported environments and compatibility ................................................................................ 6

4.1 Supported systems .................................................................................................................... 6
Hardware requirements ................................................................................................ 6
Software requirements ................................................................................................. 7
SQL Server ................................................................................................................... 8
Network requirements .................................................................................................. 9
Private cloud ................................................................................................................. 9
4.2 OpenText product compatibility ................................................................................................. 9
4.3 Language support ...................................................................................................................... 9
Business Center Capture ............................................................................................. 9
Language support for BCC applications ..................................................................... 10

5 Installation and upgrade notes ................................................................................................... 11

5.1 Installation notes ...................................................................................................................... 11
5.2 Upgrade notes ......................................................................................................................... 11
Upgrading BCC applications ...................................................................................... 11
Updating applications of type Custom ........................................................................ 11

6 Patches ......................................................................................................................................... 11

7 Fixed issues .................................................................................................................................. 12

8 Known issues ............................................................................................................................... 13

9 Contact information ..................................................................................................................... 14

Business Center Capture 16.7 Release Notes

2
Business Center Capture 16.7 Release Notes

3
1 Introduction
These Release Notes provide an overview of Business Center Capture 16.7, 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

Release 16.7 – new

2019-10-29 All new content.
version

2 About Business Center Capture

OpenText Business Center for SAP Solutions (BCC) can help to process incoming documents, to capture
data, and to file them within SAP. Business processes like the processing of incoming sales orders from
customers or incoming delivery notes from suppliers are very good use cases for Business Center. The
product provides a platform for automation of any business process and is tightly integrated into the SAP
solution stack.

Business Center can be connected with various inbound channels, such as paper via scan, fax, email, or
IDOC.

OpenText Business Center Capture (Business Center Capture) is the input channel for paper
documents and email attachments, for example PDF documents. Business Center Capture provides, in
addition to the established methods, new automated learning methods based on end user feedback when
doing data entry or data completion. Business Center Capture processes all types of machine-printed
paper documents. OCR/ICR and document analysis technology extract data from scanned paper
documents or PDF email attachments and transfer it to Business Center data tables. These data
allow Business Center to automatically create SAP documents or to assign documents to specific
objects in SAP business context.

Business Center Capture comes with powerful customizing features for implementing custom
document capture solutions, which include all classical OCR features well known from Invoice
Capture Center customizing. Business Center Capture goes beyond and adds completely new
adaptive methods for continuous learning from user feedback. These methods will reduce
implementation time for new capture solutions dramatically, and yield excellent recognition results due
to perfect adaptation to customer environment.

Business Center Capture 16.7 Release Notes

4
Alongside Business Center, a set of pre-configured scenarios are provided as Solutions. A Solution is a
pre-configured business scenario for selected business objects and business processes and is a simple
approach to demo, POC and start implementing a business solution atop.

Business Center Capture is the OCR option to OpenText Business Center for SAP Solutions and
Vendor Invoice Management for SAP Solutions. Installing the Invoice Solution permits to process
invoices with Business Center Capture in the same way as with Invoice Capture Center, if Invoice
Capture Center is licensed. Invoice Solution is available for download in MySupport, Invoice Capture
Center folder. Business Center Capture delivery includes a corresponding set of solutions for all
Business Center Solutions. With that end to end processing for the supported Business Scenarios is
preconfigured for OCR and ABAP add-on.

2.1 New features

Business Center Capture 16.7 includes the following new features:
- Enhance handling of multiple tables (ICC-6146)
- ESR number in Switzerland will be obsolete - support ISO 20022 code (ICC-3126)
- Activating Table grid consumes too much place of the window (ICC-6081)

3 Packaging and documentation

Downloads and documentation for Business Center Capture are available on OpenText My Support
(https://support.opentext.com).

3.1 Packaging and delivery information

The software and documentation for Business Center Capture includes:
• BCC 16.7 Installation package

• BCC 16.7 Delivery Notes solution plug-in

• BCC 16.7 Sales Order solution plug-in

• BCC 16.7 Mailroom for HR solution plug-in

• BCC 16.7 Order Confirmation solution plug-in

• BCC 16.7 Remittance Advice solution plug-in

• BCC 16.7 Incoming Quotation solution plug-in

3.2 Related documentation

For additional information about Business Center Capture, or for supplemental information about
related products, refer to the following documents, which are available on OpenText My Support
(https://support.opentext.com).

• Administration Guide
• Customizing Guide
• User Guide
• Business Center for SAP Solutions Configuration Guide

Business Center Capture 16.7 Release Notes

5
4 Supported environments and compatibility
This section provides details about supported platforms, systems, and versions.

4.1 Supported systems

Hardware requirements
Recognition Server and Recognition Node

• X86-compatible processing unit, current design

• 3 GB RAM
• 20 GB disk space

These are minimum requirements.

For each processor node, 3 GB RAM should be available. Therefore, on a computer with four
processing nodes, 12 GB RAM should be available. Also make sure that always one CPU is left for
the Microsoft Windows operating system, that is if you have a four CPU computer, then configure only
three processing nodes.

The disk space required for production depends on the size of the documents (medium number of
pages), and the number of applications.

On the Recognition Server and each Recognition Node, Recognition use a separate cache per
application where data of the recently processed items are stored. In each cache the newest 32
entries are kept. When the number of entries reaches 64, the oldest entries are deleted. As default,
the caches reside below the temporary files folder of the user used for the Load Manager service (or
the Windows\temp folder for a standalone test system where Local System has been specified as
user account for the services) on the system drive.

For recognition you should plan 150 MB disk space for processing single page documents per
application. Thus, if you have five applications with four pages per document on average, you should
plan 5 * 4 * 150 MB = 3 GB.

For PO download data you should plan 300 MB disk space for 100,000 data records per download for
a single application. Thus, if you have five applications and 400,000 data records to be downloaded
on average, you should plan 5 * 4 * 300 MB = 6 GB for download data.

In addition, you should plan several GB disk space for trace files, and for data of documents waiting
for processing.

Add these requirements to the minimum of 20 GB. For the above examples, you should have at least
35 GB available on the system drive.

Validation Client
• X86-compatible processing unit, current design
• 1.5 GB RAM
• 1 GB disk space

Business Center Capture 16.7 Release Notes

6
These are minimum requirements for applications processing documents of up to 10 pages. Provide 4
GB RAM for applications processing documents of up to 35 pages. If documents with more than 35
pages may occur, provide 6 GB RAM and activate Windows 4-Gigabyte Tuning.

Software requirements
4.1.2.1 Business Center

The following table shows the required updates of OpenText Business Center:

BCC

16.3 SP1
16 SP 1

16 SP 2

16.3

16.5

16.6

16.7
16

16 x x 1) x 1) x 1) x 1) x 1) x 1) x 1)
Business
16 Update 1 x x 1) x 1) x 1) x 1) x 1) x 1)
Center
16 Update 2 x x 1) x 1) x 1) x 1) x 1)
16.3 x x 1) x 1) x 1) x 1)
16.3 SP1 x x 1) x 1) x 1)
16.3 SP2 x x 1) x 1)
16.3 SP3 x1) x x1)
16.3 SP4 x

1) Combination is supported, but some new features cannot be used.

4.1.2.2 Vendor Invoice Management

If the Invoice Solution should be used, a suitable version of OpenText Vendor Invoice Management for
SAP Solutions (VIM) is required on SAP ERP. For more information, see OpenText Invoice Capture
Center for SAP Solutions Release Notes Version 16.7. Invoice Capture Center is equivalent to
Business Center Capture with the Invoice Solution provided with BCC 16.7.

4.1.2.3 Microsoft Windows platform

The following Microsoft Windows versions are supported (including 64-bit versions: WOW64):
• Microsoft Windows 2016 Server 1) 4)

• Microsoft Windows 2019 Server 1) 4)

• Microsoft Windows 10 (for the Validation Client) 2) 3)

1) Terminal Server is supported.

2) To be able to use Business Center Capture on Microsoft Windows 10 Creators Update, the Microsoft Patch
KB4025342 must be installed.
3) Released also for Microsoft Windows 10 version 1803.
4) BCC 16.7 is not supported in a docker environment using docker image "microsoft/windowsservercore”.

Take care to install all available important updates.

Business Center Capture 16.7 Release Notes

7
 Caution
For Asian languages, some restrictions have to be taken into account:
- On the BCC Server, on Recognition Nodes, and on stand-alone systems, Asian-
language Microsoft Windows cannot be used. In addition, the language for non-Unicode
programs must be set to a non-Asian language.
- Asian characters are not allowed in all internal names, such as field names, or column
names of database files.

Note: Business Center Capture 16.3 SP1 was the last version supporting Microsoft
Windows 8.1 and Microsoft Windows Server 2008 R2. Thus the operating system
versions are no longer supported with this version of BCC.

Business Center Capture can be used with VMWare (ESX-Server).

4.1.2.4 Prerequisites for installation

Business Center Capture requires a database in an instance of Microsoft SQL Server (2016, 2017).
This database is only used for runtime data of BCC outside SAP. It is recommended to use the
Express edition of Microsoft SQL Server, which is free of charge. Other editions can also be used.
Microsoft Visual C++ 2013 x86 Redistributable (minimum version 12.0.30501)
Microsoft Visual C++ 2015 x86 Redistributable (minimum version 14.0.24215)
Microsoft .NET Framework version 4.8 is required.
SAP Connector for Microsoft .NET (Version 3.0.18 or higher) for Windows 32-bit, compiled with .NET
Framework 4.0 is required. Take notice that on 64-bit Windows also the version for Windows 32-bit
has to be installed.
Business Center Capture 16.7 needs access to a SAP system where Business Center or Vendor
Invoice Management are installed.
Business Center Capture 16.7 supports the same SAP ERP and S/4HANA versions as Business
Center 16.3.4.

SQL Server
During ICC installation, a dialog box will open where you must specify the instance and the database
that should be used. If you install BCC for the first time, you must prepare an instance and a database
before you install BCC; there are no restrictions for the names of instance and database in this case.
If you upgrade from an earlier version, specify the previously used database, typically it will be an
instance DOKUSTAR with a database RdaDb10.

BCC allows you to connect to any Microsoft SQL database which is offered as a cloud service (PaaS
or DBaas).

It is also possible to use a SQL Server installed and hosted in the cloud on Microsoft Windows Server
Virtual Machines (IaaS).

In this case specific prerequisites must be adhered as described in the Administration Guide chapter
“Installing Microsoft SQL Server” and can also be configured using the SQL Server Management
Studio after the database instance has been created.

Business Center Capture 16.7 Release Notes

8
4.1.3.1 Database space requirements

The BCC database contains a separate repository for each application where a Lookup List field is
used. Example:

If a database (CSV file) for a Lookup List field (SnapMatch automation method) is loaded, the growth
of the database amounts to about 5 to 7 times the size of the CSV file.

Network requirements
The TCP/IP protocol must be supported. Recognition Server and the Recognition Nodes require
Microsoft Windows File Sharing.

Private cloud
BCC also runs inside a managed private cloud like Microsoft Azure or Amazon Web Services.

If you want to use a managed private cloud, take care to fulfill the system requirements in chapter 4.1
of this document.

Connection via RFC must be granted in order to connect from VIM SAP on-premise system to the
BCC VM which runs in a managed private cloud. For setting up a secured connection, refer to the
documentation of the service provider.

4.2 OpenText product compatibility

The section provides details about which versions of other OpenText products are compatible with this
release of Business Center Capture 16.7.

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

4.3 Language support

Business Center Capture
Business Center Capture is currently localized in the following languages. Additional languages may
be available in future releases.

Component Languages
CS DE ES FR HU IT NL

Validation Client UI B B B UI B B

Component Languages
PT RU SK TR ZH

Validation Client B B UI UI B

Business Center Capture 16.7 Release Notes

9
 UI = User interface only
B = Both user interface and online help

Language support for BCC applications

For Business Center Capture applications, a character set for character recognition must be
specified. The character sets listed in the table are available that correspond to the most
important Windows codepages.

The following table shows the languages/countries that can be used for the different character
sets:

International Afrikaans Danish Dutch English Finnish

• CP 1252 WinLatin1 French German Icelandic Indonesian Italian

• CP 1250
WinLatin2, Luxembourgish Norwegian Portuguese Spanish Swedish
• Baltic CP 1257)
• Baltic (CP1257) Albanian Bosnian Croatian Czech English
• Greek (Latin)
(CP1253WinGreek)
Hungarian Polish Romanian Serbian Slovak
• Turkey
(Latin)
(CP 1254
WinLatin5) Slovenian

Estonian Latvian Lithuanian

Greek

Azeri (Latin) Turkish Uzbek

(Latin)

Cyrillic Azeri (Cyrillic) Belarusian Bosnian Bulgarian Kazakh

(CP 1251 WinCyrillic) (Cyrillic)

Kyrgyz Macedonian Russian Serbian Tajik

Ukrainian Uzbek
(Cyrillic)

China Mainland China Singapore

(CP 936)

China Traditional Taiwan Hong Kong

(CP 950)

Japan (CP 932) Japan

Korea(CP 949 Korean

Business Center Capture 16.7 Release Notes

10
 Thailand (CP 874) Thai

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

This section provides additional installation and upgrade information, including related or third-party
product information and any required critical patches.

5.2 Upgrade notes

Before you upgrade, review these instructions.

Upgrading BCC applications

The technical field names have been changed with BCC 16.6, therefore in Business Center different
Mapping IDs need to be used for old BCC applications migrated from a version before 16.6, and new
applications created in BCC 16.7:
- For existing BCC application, created before 16.6 and upgraded to 16.7, mapping ID
CAPTURE should be used.
- For BCC applications newly created with 16.7, mapping ID CAPT_BCC should be used

Updating applications of type Custom

At new String fields, the automation methods LSPL and LUPL are also enabled. OpenText
recommends to enable these methods also for respective fields of existing applications.

Existing string fields using rules based method CSE will still be working as before the update.

6 Patches
A patch is a piece of software that is designed to fix or improve a computer program or its supporting
data. These may include repairs to security vulnerabilities or resolutions of bugs, and may also
improve usability or performance. On OpenText My Support you will find two general types of patches.
Hotfixes are also known as quick-fixes or bug fixes. Updates are also known as service packs or
service releases.

OpenText recommends that you check OpenText My Support (https://support.opentext.com) for any
patches or documentation updates that may have been posted after this release.

Check also the patches for the Capture Imaging Plug-In component
(https://knowledge.opentext.com/knowledge/llisapi.dll/Open/61183571) if a newer version is available.

Business Center Capture 16.7 Release Notes

11
7 Fixed issues
This section provides information about past issues that have been fixed in this update.

Issue name Issue description

ICC-6098, ITSM 4124058 Leaving last field (table grid) from Delivery note not
possible with ENTER

ICC-5993, ITSM 4058094 Name cannot begin with the '&' character,
hexadecimal value 0x26. Line 1, position 150.

ICC-6191, ITSM 4251846 When toggeling validation layout with F8 and F6

manually entered item line get lost

ICC-6148, ITSM 4182105, 4213676 Exception triggered in China Mainland app. on line
item

ICC-6176, ITSM 4218839 Date field shows different messages depending on

patch level

ICC-6080, ITSM 4124049 Unhandled Exception after deleting rows

ICC-6162, ITSM 4189692 Unhandled exception error when using rejection

feature

Business Center Capture 16.7 Release Notes

12
8 Known issues
This section provides information about known issues with this update.

Issue name Issue description

RSP-6375 XFA PDF document cannot be loaded into RDS (RSP-

6375). PDF files written by Adobe LiveCycle are in XFA
(XML Forms Architecture) format which is proprietary
and cannot be opened by software other than Adobe
Acrobat. Interactive forms in PDFs are not supported in
CRE because the rendering of such forms is imprecise
by definition.

ICC-5628 Error message "Could not find file '\\...\RdaProjects.rpj'."

is displayed during import of Custom app containing
CSA data.
Workaround:
At first, after the installation, create an application even
as dummy. You can leave or delete it afterwards. Then,
you can import your application without an error.

DSP-5681 Extraction Server process shut down not working in

rare cases and process won’t get killed by the
application.

ICC-6028 The Image format 'old style Tiff' is not supported. In

case of processing such an image format, the Splitter
Transformer is logging an error message in the trace.

Business Center Capture 16.7 Release Notes

13
9 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.

14