OpenText™ Business Center for SAP®

Solutions

Installation Guide

This guide describes the installation of OpenText Business

Center for SAP Solutions.

BOCP160300-IGD-EN-01
OpenText™ Business Center for SAP® Solutions
Installation Guide
BOCP160300-IGD-EN-01
Rev.: 2017-Nov-02
This documentation has been created for software version 16.3.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com

Copyright © 2017 Open Text. All Rights Reserved.

Trademarks owned by Open Text.

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.
 Table of Contents
Part 1 About Business Center 5

1 What is Business Center? ........................................................ 7

2 About this document ............................................................... 13

2.1 Target audience .............................................................................. 13
2.2 Document overview ......................................................................... 13

Part 2 Business Center installation 15

3 Checking prerequisites ........................................................... 17

3.1 SAP prerequisites ........................................................................... 17
3.2 OpenText prerequisites ................................................................... 17
3.3 Installation tool ................................................................................ 18

4 Setup for the Fiori Task App .................................................. 19

4.1 Deployment options ........................................................................ 19
4.2 Setting up a multiple backend system ............................................... 23

5 Summary of installation steps ............................................... 25

6 Installing ................................................................................... 29
6.1 Installing packages .......................................................................... 30
6.2 Activating BC sets ........................................................................... 32
6.3 Activating services .......................................................................... 33
6.4 Fiori launchpad content ................................................................... 35

7 Upgrading ................................................................................. 37
7.1 Upgrading Business Center 16 to Business Center 16.3 .................... 37
7.2 Mandatory activities ........................................................................ 37

GLS Glossary 39

OpenText Business Center for SAP Solutions – Installation Guide iii

BOCP160300-IGD-EN-01
 Part 1
About Business Center
Chapter 1
What is Business Center?

OpenText Business Center for SAP Solutions (Business Center) enables receiving
incoming documents, including capturing of relevant data fields, processing of the
incoming documents inside SAP ECC and SAP S/4HANA on Premise, and creating
a new SAP business object or linking the document to an existing business object.

Business processes like processing of incoming sales orders from customers or

incoming delivery notes from suppliers are very good use cases for Business Center.
The product provides the one platform to automate business processes triggered by
incoming documents or events in the system that is tightly integrated into the SAP
solution stack.

Business Center can be connected with various inbound channels, be it paper

through scan, fax, email, or iDoc. The incoming documents are stored using SAP
ArchiveLink®.

OpenText™ Business Center Capture for SAP® Solutions (Business Center Capture)
is part of Business Center. It provides state of the art automated learning methods
based on end user behavior and feedback.

After capturing the documents, the extracted data is validated against a set of
business rules. Though touchless processing is the ultimate goal, user interaction is
required if an exception occurs. Therefore, Business Center provides efficient user
experience within SAP GUI and web/mobile based access, following the design
principles of SAP Fiori®. Once all exceptions are solved, the data can be posted and
saved within the SAP system.

To define the flow and the assignment of the right forms to the right users, the
product provides a simple configuration interface, which allows creation and
maintenance of process models quite efficiently.

Alongside Business Center, a set of pre-configured scenarios are provided as

solution accelerators. A solution accelerator is a pre-configured business scenario for
selected business objects and business processes. It is a simple approach to demo,
Proof of Concept, and to start implementing a business solution atop.

Business Center introduces the following features:

OpenText Business Center for SAP Solutions – Installation Guide 7

BOCP160300-IGD-EN-01
Chapter 1 What is Business Center?

Figure 1-1: Business Center features

Solution Accelerators

Preconfigured processes that ensure a fast implementation phase. Currently, the

following solution accelerators are available.

• Incoming sales orders

• Purchase Order / Purchase Requisition dashboard
• Incoming delivery notes
• Incoming HR documents
• Incoming remittance advices
• Incoming order confirmations

You can also process incoming vendor invoices, in combination with OpenText™
Vendor Invoice Management for SAP® Solutions (VIM). For more information, see
OpenText Vendor Invoice Management for SAP Solutions - Installation Guide (VIM-IGD)
and OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD). On VIM side, Fiori-based applications are available for Approval, DP
Exceptions, and simple coding.

Business Center Foundation

Import
• Enter incoming electronic documents, for example from email, PDF, fax, or the
OpenText Trading Grid.

8 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
 Capture
• Scan and archive incoming paper document.
• OpenText Business Center Capture for SAP Solutions
Automate the capture of paper documents by using OCR to extract document
data. Similar to OpenText™ Invoice Capture Center for SAP® Solutions (ICC).

Dispatch
• Assign incoming documents to the correct target process.
• Classify documents according to the document type.

Process
• Process workflows for documents or objects in a configurable workflow engine.
• Ensure that documents are at the right user at the right time.

Consume
• Browse business objects in the Business Center Workplace in different working
queues.
• Use the Business Center Workplace to access and process workflows.
• Optionally, use the SAP Fiori Task App to access and approve workflows
directly from mobile devices or from the desktop.

SAP Layer
• SAP Business Workflow
• SAP Transactions
• SAP Business Objects
• SAP ArchiveLink
• SAP Fiori
• SAP Gateway

OpenText solutions related to Business Center

OpenText™ Imaging Enterprise Scan
Enterprise Scan is the solution for mass scanning and indexing of documents at
one or more scan stations.
OpenText™ Imaging Web Viewer, OpenText™ Brava!™ View for SAP Solutions
(Brava! View)
Web Viewer is a web application for displaying and printing documents in web-
based scenarios and for appending comments to these documents.
Brava! View is a web application for displaying, exporting and printing
documents as well as for annotating and appending comments to these

OpenText Business Center for SAP Solutions – Installation Guide 9

BOCP160300-IGD-EN-01
Chapter 1 What is Business Center?

documents stored in OpenText™ Archive Center. Brava! View supersedes Web

Viewer in all scenarios built on top of OpenText™ Archiving and Document
Access for SAP Solutions. The feature parity between Brava! View and Web
Viewer is not accomplished yet. Therefore, Brava! View provides many usability
enhancements compared to Web Viewer like multi-page view or responsive UI.

OpenText Vendor Invoice Management (VIM), OpenText Invoice Capture Center

(ICC)
VIM is a packaged business solution that basically solves a business problem –
paying correct amount to vendors on-time. VIM is an add-on to your SAP ERP
system, the majority of its functions and processes run inside the SAP ERP
system.
As an option for VIM, ICC extends VIM’s capabilities to automate the capture of
machine-printed paper invoices.
VIM can be integrated into Business Center as a “Vendor Invoices” solution
integration.
The new simple mode of VIM 16.3 is also based on Business Center
16.3 components.

OpenText™ Archive Center

Archive Center provides a full set of services for content and documents.
You can archive documents that will be processed with Business Center safely
and reliably on Archive Center.

OpenText™ Extended ECM for SAP® Solutions

Extended ECM for SAP Solutions is a combination of a OpenText™ Content
Server module and an SAP package, with which you can integrate Content
Server functionality into SAP business processes.
Extended ECM for SAP Solutions can be integrated in Business Center as a plug-
in. In SAP GUI, Business Center provides a pre-configured plug-in. The Fiori
Task App provides an Extended ECM view that can be integrated. For more
information, see OpenText Extended ECM for SAP Solutions - Customizing Guide
(ERLK-CGD).

OpenText™ Archiving and Document Access for SAP Solutions

Archiving and Document Access for SAP Solutions offers a range of options for
integrating SAP documents and other documents in the different SAP
applications, including emails, faxes, images, and informal correspondence.
Besides archiving documents, it allows you to manage, search, display and edit
them.

OpenText™ DocuLink for SAP Solutions

DocuLink is a fully integrated, cross-module application used for a document-
oriented representation of processes executed with SAP applications.
DocuLink can be integrated in Business Center as a plug-in. Business Center
does not provide a pre-configured plug-in.

10 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
 Technical system landscape
Figure 1-2 shows the technical architecture of Business Center. For a detailed
description of the components, see part II “Customizing Business Center” in
OpenText Business Center for SAP Solutions - Configuration Guide (BOCP-CGD).

“System landscape” on page 20 provides another landscape diagram, including the

particular components and their prerequisites and dependencies.

Figure 1-2: Technical architecture

OpenText Business Center for SAP Solutions – Installation Guide 11

BOCP160300-IGD-EN-01
Chapter 2
About this document

2.1 Target audience

This document addresses those who participate in the installation, administration
and maintenance of OpenText Business Center for SAP Solutions (Business Center).
This includes the following.
• SAP Basis Administrators
• SAP Workflow Administrators
• SAP Configuration and Development Support

2.2 Document overview

This Installation Guide includes the complete installation information for all
Business Center components.

OpenText Business Center for SAP Solutions – Installation Guide 13

BOCP160300-IGD-EN-01
 Part 2
Business Center installation
Chapter 3

Checking prerequisites

Before installing, you must check the following prerequisites.

3.1 SAP prerequisites

Check the latest version of the Release Notes for any version support and
prerequisites.

Prior to installation, check the following prerequisites. For more information about
the overall system landscape, see “System landscape” on page 20.

SAP support Check the latest version of the Release Notes on OpenText My Support for required
packages support packages for the employed SAP system.

OSS notes Check the following OSS notes to avoid known problems with the SAP Add-On
Installation Tool (SAINT):

• SAP 7.00 - OSS note 822380

• SAPCAR tool - OSS note 212876

3.2 OpenText prerequisites

Prior to installation, check the following prerequisites.

Document Archived documents are displayed with the viewing application installed on your
viewer desktop. On your mobile device, they are displayed according to Mime type and
ArchiveLink settings. Alternatively, they are displayed and rendered into PDF with
the OpenText Imaging Web Viewer (Web Viewer) or OpenText Brava! View for SAP
Solutions (Brava! View) if it is installed and configured.

To support the document view in plug-ins for Mime types where no HTML-based
plug-in is installed, Web Viewer 10.0.0 or Brava! View 16.0 is required as a
minimum. However, OpenText strongly recommends employing Web Viewer with
the latest patch. You can download the corresponding software from My Support.

Table 3-1: Display of archived documents

Desktop iPad/iPhone
Web Viewer / Web Viewer / No Web Viewer / Brava!
Brava! View on Brava! View off View support[a]
Display variant Inplace Inplace New tab

OpenText Business Center for SAP Solutions – Installation Guide 17

BOCP160300-IGD-EN-01
Chapter 3 Checking prerequisites

Desktop iPad/iPhone
Web Viewer / Web Viewer / No Web Viewer / Brava!
Brava! View on Brava! View off View support[a]
PDF Web Viewer / Acrobat plug-in Built in
Brava! View
XLS Web Viewer / Not supported Built in
Brava! View
PPT Web Viewer / Not supported Built in
Brava! View
DOC Web Viewer / Not supported Built in
Brava! View
Others Web Viewer / Not supported Not supported
Brava! View
[a]Web Viewer or Brava! View may be used in custom solutions to convert the ArchiveLink document in
a PDF for displaying it on an iOS device.

Integration You can integrate Business Center into other OpenText solutions, like the VIM
solution integration or the Fiori Business Object Browsing for Document Access and
Extended ECM for SAP Solutions solution accelerator. If you do so, make sure to
check dependencies and compatibility. For more information, see the respective
documentation of VIM and Extended ECM for SAP Solutions.

Recent Refer to the most recent product documentation, release notes and patches
information description released on My Support.

3.3 Installation tool

Business Center uses the SAP Add-On Installation Tool (SAINT) for installation.
SAINT uses single PAT files (extension *.PAT) which integrate several transport files;
these collections are also called packages.

Note: The handling of the installation procedure within SAINT differs

depending on the SAP system that is used. For more details, see the respective
SAP documentation.

18 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
Chapter 4
Setup for the Fiori Task App

The settings described in this section are only relevant if you want to use the Fiori
Task App.

4.1 Deployment options

OpenText Business Center for SAP Solutions – Installation Guide 19

BOCP160300-IGD-EN-01
Chapter 4 Setup for the Fiori Task App

4.1.1 System landscape

Figure 4-1: Web Services landscape

The Fiori Task App of Business Center comes with the OpenText Business Center
WebUI (AddOn OTBCWUI). This AddOn requires the SAP component SAP_UI. For
detailed system requirements, check the Release Notes.

The WebUI retrieves data from the technical service /OTX/PF05_DATA. The
activation of this service is described in “Enabling OData service” on page 33.

The /OTX/PF05_DATA service is part of the OpenText Business Center

Webservices (AddOn OTBCWSR). This AddOn requires the SAP component IW_BEP
or SAP_GWFND as well as the Business Center component OTBCBAS. For detailed
system requirements, check the Release Notes.

OpenText recommends that you install the AddOn OTBCWSR on the same system as
the AddOn OTBCFND as shown in Figure 4-1, but other installation variants are also
possible. However, all systems must be connected using trusted RFCs.

Note: The installation of OTBCWSR on the same system as the OTBCFND

component is recommended because of performance reasons. This variant
reduces the number of RFC connections between the systems. RFC connections
need to be opened for handling requests of the Fiori Task App in the backend.
This variant also allows the solutions to handle several requests of the Fiori
Task App in one call.

OpenText Business Center Inbound Configuration (AddOn OTBCINB) formerly

was part of OpenText Business Center Foundation (AddOn OTBCFND). OTBCINB
has the following prerequisite:

20 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
 4.1. Deployment options

• OpenText Business Center Base (AddOn OTBCBAS)

The customizing and data for the /OTX/PF05_DATA web service is defined in
OTBCFND, which has the following prerequisites:

• OpenText Business Center Base (AddOn OTBCBAS)

• OpenText Business Center Inbound Configuration (AddOn OTBCINB)

The OTBCSL* AddOns represent the solution accelerators and the VIM solution
integration. OTBCRM represents the integration of Extended ECM.

OpenText recommends the installation of a Web Dispatcher to prevent direct access

from the client browser to the archive system. However if you want to use the
InteractiveDocument view (Single Click Entry - SCE), a Web Dispatcher is
mandatory. Otherwise the SCE viewer cannot access the document due to cross-
domain constraints.

Note: The protocol for Launchpad access (typically HTTPS) must be the same
for archive access.

The following illustrates a sample configuration for the Web Dispatcher:

wdisp/system_0 = SID=T7H, NR=01, MSHOST=<replace-with-frontend-

server-host>, MSPORT=8101, SSL_ENCRYPT=1, SRCSRV=*:*, SRCURL=/sap/
opu/odata;/sap/bc
wdisp/system_1 = SID=ARC, EXTSRV=http://<replace-with-archive-host>:
8080, SRCSRV=*:*, SRCURL=/archive

4.1.1.1 Compatibility with older Business Center versions

To support an improved interoperability between the Fiori apps and OData services,
versioning has been introduced with Business Center 16 SP1.

For more information, see the following table:

OpenText Business Center for SAP Solutions – Installation Guide 21

BOCP160300-IGD-EN-01
Chapter 4 Setup for the Fiori Task App

OTBCWUI UI 5 Version Task App Task App ID PF05_DATA OTBCWSR

Version URL Version Version
0740_004 1.44.X /sap/bc/ ot.approve.re 003 0740_004
ui5_ui5/ quests03
otbcwui/
pf07_bc_ui_0
3
0740_004 1.44.X /sap/bc/ ot.approve.re 002 0740_003 SP1
ui5_ui5/ quests02
otbcwui/
pf07_bc_ui_0
2
0740_003 SP3 1.38.X /sap/bc/ ot.approve.re 002 0740_003 SP1
ui5_ui5/ quests02
otbcwui/
pf07_bc_ui_0
2

Versioning allows you to run multiple backends with different Business Center
component versions against the latest Business Center frontend component on the
Fiori Server.

The following list shows the delivered BSP applications and the corresponding
OData services with their version:

Fiori Task App (OTBCWUI)

• /OTBCWUI/PF07_BC_UI (version 01)
• /OTBCWUI/PF07_BC_UI_02 (version 02)
• /OTBCWUI/PF07_BC_UI_03 (version 03)

Templates
• /OTBCWUI/PF07_BC_UI_TMPL (version 01)
• /OTBCWUI/PF07_BC_UI_02_T (version 02)

Business Center OData service (OTBCWSR)

• /OTX/PF05_DATA V2 (version 0002)
• /OTX/PF05_DATA V3 (version 0003)

Table 4-1: Version compatibility

Fiori Task App Business Center OData service (OTBCWSR)

(OTBCWUI)
Version 03 Version 0003
Version 02 Version 0002

22 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
 4.2. Setting up a multiple backend system

Fiori Task App Business Center OData service (OTBCWSR)

(OTBCWUI)
Version 01 Version 01 (Business Center 16 without SP)

4.1.2 Configuring network options

You must define which systems must be opened from a network perspective for an
Intranet or Extranet scenario. For more information, see the SAP Help regarding
Deployment Options (http://help.sap.com/fiori_bs2013/helpdata/en/4c/
ca4152fc94b610e10000000a44176d/content.htm) and Multiple Network Zones (http://
help.sap.com/saphelp_nw74/helpdata/en/aa/37ff4fa187622fe10000000a44176d/
content.htm?frameset=/en/1d/300050d5ac612fe10000000a44176d/frameset.htm&
current_toc=/en/f3/780118b9cd48c7a668c60c3f8c4030/plain.htm&node_id=15).

4.1.3 Checking the Fiori landscape

The Fiori system landscape must meet the requirements of the SAP guidelines. For
more information, see the SAP Help (http://help.sap.com/fiori_bs2013/helpdata/en/
ba/f61f533f86ef28e10000000a4450e5/content.htm?frameset=/en/4c/
ca4152fc94b610e10000000a44176d/frameset.htm&current_toc=/en/40/
1b675374bc6655e10000000a423f68/plain.htm&node_id=3&show_children=false).

4.2 Setting up a multiple backend system

Business Center makes use of two concepts to support multiple backend systems.

First, you use the Multi Origin Composition concept on the OData service level. This
concept enables you to instruct the Fiori Task App to fetch the data from a dedicated
backend system. You provide the configured backend system alias in the front-end
server as a URL parameter: &system=<SYSTEM_ALIAS>. This allows you to connect
different backends with one front-end server. However, using only this concept, you
cannot aggregate nodes from different systems.

The second concept addresses this aggregation scenario. A certain selection

described by node customizing should be applied to multiple systems and finally
aggregated into one result. You can achieve this by maintaining multiple logical
systems in the General Settings of the Business Center customizing. For more
information, see OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP-CGD).

OpenText Business Center for SAP Solutions – Installation Guide 23

BOCP160300-IGD-EN-01
Chapter 4 Setup for the Fiori Task App

24 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
Chapter 5
Summary of installation steps

This section summarizes the required installation steps and their sequence for
installing Business Center.

To install Business Center:

1. Install Business Center Foundation:

• Install the Business Center Base (OTBCBAS), Inbound (OTBCINB), and

Foundation (OTBCFND) add-on using the SAINT transaction.
• Activate Business Center BC sets (/OTX/PF00_GENERAL_SET_004, /OTX/
PF01_INBOUND_004, and /OTX/PF02_FOUNDATION_004) using the SCPR20
transaction.

Notes
• You must activate all BC sets using Expert Mode. The user must be
logged in with language EN. For more information, see “Activating BC
sets” on page 32.
• After the installation, some mandatory configuration is required to
enable the business scenarios. The document Mandatory and Optional
Configuration for OpenText Business Center for SAP Solutions - Solution
Accelerators provides the relevant information.
2. Optional Install Business Center solution accelerators:

• Install the Base for Business Center solution accelerators (OTBCSL00) add-on
using the SAINT transaction.

Note: The solution accelerator for incoming HR documents (OTBCSL05)

can also be installed and used without the base for Business Center
solution accelerators (OTBCSL00).
• Activate the BC set of the Base for Business Center solution accelerators (/
OTX/PS00_BASE_004) using the SCPR20 transaction.
• Install the solution accelerators that you want to use:

Note: You find the solution accelerator installation files on My

Support: https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
63029079.

Delivery Notes

• Install the solution accelerator for Delivery Notes (OTBCSL01) add-on

using the SAINT transaction.

OpenText Business Center for SAP Solutions – Installation Guide 25

BOCP160300-IGD-EN-01
Chapter 5 Summary of installation steps

• Activate the BC set of the solution accelerator for Delivery Notes (/OTX/
PS01_DELIVERY_004) using the SCPR20 transaction.

Sales Orders

• Install the solution accelerator for Sales Orders (OTBCSL02) add-on using
the SAINT transaction.
• Activate the BC set of the solution accelerator for Sales Orders (/OTX/
PS02_ORDER_004) using the SCPR20 transaction.

Incoming HR Documents

• Install the solution accelerator for incoming HR documents (OTBCSL05)

add-on using the SAINT transaction.
• Activate the BC set of the solution accelerator for Incoming HR
documents (/OTX/PS05_HR_004) using the SCPR20 transaction.

Remittance Advices

• Install the solution accelerator for Remittance Advices (OTBCSL07) add-

on using the SAINT transaction.
• Activate the BC set of the solution accelerator for Remittance Advices (/
OTX/PS07_REMADV_004) using the SCPR20 transaction.

Order Confirmations

• Install the solution accelerator for Order Confirmations (OTBCSL09) add-

on using the SAINT transaction.
• Activate the BC set of the solution accelerator for Order Confirmations (/
OTX/PS09_ORDCONF_004) using the SCPR20 transaction.

Notes
• For information about the integration of Vendor Invoice
Management, see OpenText Vendor Invoice Management for SAP
Solutions - Installation Guide (VIM-IGD).
• For the solution accelerator for Purchase Order / Purchase
Requisition, no separate installation is necessary. For technical
reasons, this is already included in OTBCSL00.
• When you activate the BC sets for the Foundation and the solution
accelerators, you might get dialog boxes, for example a message for
an Error in Object Editing. Just confirm them with Copy Values or
OK.
3. Optional Required for the Fiori Task App - Install Business Center Web Services:

• Install the Business Center Web Services (OTBCWSR) add-on using the SAINT
transaction on the system where you also installed the Business Center
Foundation (OTBCFND).

26 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
 Important
OpenText advises against installing the Business Center Web
Services (OTBCWSR) on a different system than the Business Center
Foundation (OTBCFND).
• Install the Business Center Web UI (OTBCWUI) add-on using the SAINT
transaction on the system that you want to use for the Web UI.
• If you need to run the Business Center Web Services (OTBCWSR) on the same
system as the Business Center Web UI (OTBCWUI), you also must install the
Business Center Base (OTBCBAS) on this system.

4. Optional Install Business Center ECMLink Integration:

• Install the Business Center ECMLink Integration (OTBCRM) on the same

system as the Business Center Foundation (OTBCFND) add-on using the
SAINT transaction.

OpenText Business Center for SAP Solutions – Installation Guide 27

BOCP160300-IGD-EN-01
Chapter 6
Installing

This section describes the installation of the Business Center packages on an SAP
application server. For general information about installing in an SAP environment,
see also “Checking prerequisites“ on page 17.

During the installation process, the following major packages are used:

Component Release SAP Release OCS OCS Password

Filename Package
OTBCBAS 0700_004 700 QAR0020073 SAPK-004CO 8B96C655BF
437_0000056. INOTBCBAS
PAT
OTBCINB 0700_004 700 QAR0020073 SAPK-004CO 8B9DC944BF
437_0000059. INOTBCINB
PAT
OTBCFND 0700_004 700 QAR0020073 SAPK-004CO 8B92C942BF
437_0000058. INOTBCFND
PAT
OTBCRM 0700_004 700 QAR0020073 SAPK-004CO 8B86CA26BF
437_0000061. INOTBCRM
PAT
OTBCWSR 0740_004 700 QAR0020073 SAPK-004CO 8B83D454BF
437_0000066. INOTBCWSR
PAT
OTBCWUI 0740_004 740 QAT00200734 SAPK-004CO 8B83D24FBF
37_0000005.P INOTBCWUI
AT
OTBCSL00 0700_004 700 QAR0020073 SAPK-004CO 8B87CB36AF
437_0000057. INOTBCSL00
PAT
OTBCSL01 0700_004 700 QAR0020073 SAPK-004CO 8B87CB36AE
437_0000060. INOTBCSL01
PAT
OTBCSL02 0700_004 700 QAR0020073 SAPK-004CO 8B87CB36AD
437_0000062. INOTBCSL02
PAT
OTBCSL05 0700_004 700 QAR0020073 SAPK-004CO 8B87CB36AA
437_0000063. INOTBCSL05
PAT

OpenText Business Center for SAP Solutions – Installation Guide 29

BOCP160300-IGD-EN-01
Chapter 6 Installing

Component Release SAP Release OCS OCS Password

Filename Package
OTBCSL07 0700_004 700 QAR0020073 SAPK-004CO 8B87CB36A8
437_0000064. INOTBCSL07
PAT
OTBCSL09 0700_004 700 QAR0020073 SAPK-004CO 8B87CB36A6
437_0000065. INOTBCSL09
PAT

6.1 Installing packages

The Business Center components are provided as add-on packages. You can
download them from the Business Center 16.0.0 download section on My Support.

The following packages and included Business Center components are available:

Package Component Release

/OTBCBAS/INST_UPG_0700_004 OTBCBAS 0700_004
/OTBCINB/INST_UPG_0700_004 OTBCINB 0700_004
/OTBCFND/INST_UPG_0700_004 OTBCFND 0700_004
/OTBCRM/INST_UPG_0700_004 OTBCRM 0700_004
/OTBCWSR/INST_UPG_0740_004 OTBCWSR 0740_004
/OTBCWUI/INST_UPG_0740_004 OTBCWUI 0740_004
/OTBCSL00/INST_UPG_0700_004 OTBCSL00 0700_004
/OTBCSL01/INST_UPG_0700_004 OTBCSL01 0700_004
/OTBCSL02/INST_UPG_0700_004 OTBCSL02 0700_004
/OTBCSL05/INST_UPG_0700_004 OTBCSL05 0700_004
/OTBCSL07/INST_UPG_0700_004 OTBCSL07 0700_004
/OTBCSL09/INST_UPG_0700_004 OTBCSL09 0700_004

The Business Center components are used as follows:

OTBCBAS
Business Center Base

OTBCINB
Business Center Inbound including Inbound Configuration

OTBCFND
Business Center Foundation including Process Foundation, Process
Configuration, and Workplace Configuration

OTBCRM
Extended ECM for SAP Solutions Integration for Business Center

30 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
 6.1. Installing packages

OTBCWSR
Business Center Web Services

OTBCWUI
Business Center Web UI

OTBCSL00
Base for Business Center solution accelerators

OTBCSL01
Solution accelerator for Delivery Notes

OTBCSL02
Solution accelerator for Sales Orders

OTBCSL05
Solution accelerator for incoming HR documents

Note: The solution accelerator for incoming HR documents (OTBCSL05) can

also be installed and used without the base for Business Center solution
accelerators (OTBCSL00).

OTBCSL07
Solution accelerator for Remittance Advices

OTBCSL09
Solution accelerator for Order Confirmations

To install the packages:

1. Sign in with Client 000 in English.

2. Load the installation packages and support packages from the front end by
selecting the respective SAPCAR file (*.SAR) from the local file system. The
SAPCAR file is decompressed automatically.

3. Carry out the import of the packages and support packages as described in the
SAP documentation.

4. After the import has finished, continue with the activation of the BC sets. For
more information, see “Activating BC sets” on page 32.

OpenText Business Center for SAP Solutions – Installation Guide 31

BOCP160300-IGD-EN-01
Chapter 6 Installing

6.1.1 Removing Business Center add-ons

Business Center add-ons, see list in “Installing“ on page 29, can be deleted. It is
definitely the decision of the customer to delete an add-on and thereby lose data in
the Business Center tables.

Important
• Before deleting Business Center add-ons, always open a ticket at
OpenText Customer Support.
• The customer is responsible to evaluate if data needs to be saved. The
customer is also responsible for actually saving the data that is legally
relevant and should not be deleted.

6.2 Activating BC sets

For every client, you must activate the Business Configuration sets (BC sets) after
installation. Activate the BC set in the specific configuration client of the
development system that contains the business scenarios. Then create a transport
from BC set activation, and move the transport to the required systems.

Do not activate the BC set in the production system. Create a customization

transport in the configuration client of the development system. Therefore, activate
the BC set and move it to the wanted systems.

Important
• For the following procedure, you must sign in in English to avoid
problems with the activation of the BC sets.
• You must activate all BC sets using Expert Mode.

Activate the BC sets only for English language. Other languages are delivered with
specific language packs.

To activate BC sets:

1. Sign in in English and run the SCPR20 transaction.

2. In the Business Configuration Set screen, activate the following BC sets.

a. /OTX/PF00_GENERAL_SET_004 for the basic settings

b. /OTX/PF01_INBOUND_004 for the inbound settings
c. /OTX/PF02_FOUNDATION_004 for the foundation configuration
d. Optional /OTX/PS00_BASE_004 for the basic settings of solution accelerators,
only necessary if you plan to use solution accelerators
e. Optional /OTX/PS01_DELIVERY_004 for Delivery Notes solution accelerator
f. Optional /OTX/PS02_ORDER_004 for Sales Order solution accelerator

32 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
 6.3. Activating services

g. Optional /OTX/PS05_HR_004 for incoming HR documents solution

accelerator
h. Optional /OTX/PS07_REMADV_004 for Remittance Advices solution
accelerator
i. Optional /OTX/PS09_ORDCONF_004 for Order Confirmations solution
accelerator
j. Optional /OTX/PFRM_ECMLINK_004 for ECMLink Integration

6.3 Activating services

The settings described in this section are only relevant if you want to use the Fiori
Task App. This section describes how you register and activate the OData service for
the backend communication and also how you activate the UI5 application on the
Fiori Server. For more information, see “System landscape” on page 20.

6.3.1 Enabling OData service

The Fiori Task App communicates with the ABAP backend using a dedicated OData
service (/OTX/PF05_DATA). To invoke this service using the HTTP protocol, it first
must be enabled. This section describes the necessary steps.

Prerequisite All connection settings must be configured accordingly and the SAP NetWeaver
Gateway must be activated.

Call the /IWFND/MAINT_SERVICE transaction and maintain the backend OData

service for the external service /OTX/PF05_DATA, version 3.

Therefore you might need to connect to the backend system where the AddOn
Package OTBCWSR is installed according to your system landscape setting.

The following screenshot shows an example of /OTX/PF05_DATA, version 2.

OpenText Business Center for SAP Solutions – Installation Guide 33

BOCP160300-IGD-EN-01
Chapter 6 Installing

After that you must activate the registered service. To activate the service, run the
SICF transaction and activate the /sap/opu/odata/OTX/PF05_DATA service.

6.3.1.1 Multiple Origin Composition

The OData service classes (OTBCWSR add-on) can be installed on several backend
systems. In this case, you can configure the service at the gateway system in a way
that data from multiple of the backend systems is requested.

You can perform this using Multiple Origin Composition (MOC). For detailed
information, see the SAP Help (http://help.sap.com/saphelp_nw74/helpdata/en/bc/
f72651c294256ee10000000a445394/content.htm).

To configure the OData service accordingly, run the /IWFND/

MAINT_SERVICE transaction and add the system aliases of the systems that should be
used.

34 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
 6.4. Fiori launchpad content

With regards to MOC, the Fiori Task App provides the additional parameter system
to define which system should be used. If the parameter is not set, the system alias
LOCAL is used.

Important
If several systems are connected, you must set the OData service to error
tolerant, using the following path: SPRO > SAP NetWeaverGateway > OData
Channel > Composition > Flag OData Services to be error tolerant in case
of MDC. If not all users exist in all connected systems, consider using the
SAP “User Role” concept to control the backend system that the users
connect to.

6.3.2 Activating the service

The technical unit of the Fiori Task App in the ABAP Frontend Server is a BSP. A
prerequisite for launching a BSP using the browser is an active service that is bound
to the BSP in the SICF transaction. For UI5 applications, the service is created by
default automatically, nevertheless you must activate it before it can be used.

To activate the service, run the SICF transaction and activate the /sap/bc/ui5_ui5/
otbcwui/pf07_bc_ui_03 service.

6.4 Fiori launchpad content

OpenText provides two transports to deliver the Launchpad content for all Fiori
apps used in Business Center solution accelerators and also for all Fiori apps used in
VIM. For more information, see the related solution accelerator guides and the VIM
guides. You can either use the transports and the predefined tile catalogs or you can
integrate the Fiori Task App into the Fiori Launchpad in your configuration. For
more information, see section 9.1 “Integrating Fiori Task App into Fiori Launchpad”
in OpenText Business Center for SAP Solutions - Configuration Guide (BOCP-CGD).

6.4.1 Transports
You can access the transports on My Support: https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/58879899

Workbench Transport: Business Center Launchpad content

A new entry for semantic object Business Center OTBCWUI_PF07_BC_SEMOBJ is
delivered. Check the /n/UI2/SEMOBJ transaction that there does not exist an
entry with this key for a different object.
Customizing Transport: Business Center Launchpad content
The following Fiori tile catalogs are delivered. You can assign them to the
related role used in the corresponding business scenario.
/OTBCWUI/PF07_BC_ADMIN
Perspective Manager
/OTBCWUI/PF07_BC_SOL_DELIVERY_NOTE
Solution accelerator for incoming delivery notes

OpenText Business Center for SAP Solutions – Installation Guide 35

BOCP160300-IGD-EN-01
Chapter 6 Installing

/OTBCWUI/PF07_BC_SOL_HR_DOCUMENT
Solution accelerator for incoming HR documents

/OTBCWUI/PF07_BC_SOL_ORDER_CONF
Solution accelerator for order confirmation

/OTBCWUI/PF07_BC_SOL_SALES_ORDER
Solution accelerator for incoming order

/OTBCWUI/PF07_BC_SOL_REMITTANCE_ADV
Solution accelerator for remittance advice

/OTBCWUI/PS08_IM_SIMPLE
VIM integration simple mode

/OTBCWUI/PS30_VIM
VIM integration classic mode

6.4.2 SAP system alias

With the delivered launchpad content, also a system alias for the multi origin access
is predefined in the service URL. See <Node parameter> in section 9.1 “Integrating
Fiori Task App into Fiori Launchpad” in OpenText Business Center for SAP Solutions -
Configuration Guide (BOCP-CGD). You must use the system alias OTBCWUI_BACKEND
and configure it for the delivered launchpad content according to your system
landscape in the SAP IMG Manage SAP System Aliases.

36 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01
Chapter 7

Upgrading

Integration You can integrate Business Center into other OpenText solutions, like the VIM
solution integration or the Fiori Business Object Browsing for Document Access and
Extended ECM for SAP Solutions solution accelerator. If you do so, make sure to
check dependencies and compatibility. For more information, see the respective
documentation of VIM and Extended ECM for SAP Solutions.

7.1 Upgrading Business Center 16 to Business

Center 16.3
For the Business Center components, no specific upgrade packages are delivered.
For an upgrade from version 16, install the standard installation packages for the
Business Center components as described in “Installing“ on page 29.

Important
Install the AddOns OTBCBAS, OTBCINB and OTBCFND within one step in the
queue.

7.2 Mandatory activities

After upgrading, you must process the following activities manually:

Note: When upgrading to Business Center 16.3, observe the mandatory

activities in this section but also the mandatory activities in the Release Notes.

New UI version
With Business Center 16.3, a new version (3) of the Fiori Task App and the OData
service is delivered. For more information, see “Compatibility with older Business
Center versions” on page 21. If you are using the standard Fiori apps (delivered with
the solution accelerators or VIM) and you have not created own perspectives or
views, you can just use the new UI version with the new features.

If you have created an own perspective and you want to use the Fiori Task App and
OData Service version 2, no specific upgrade tasks are required as well.

However, if you have created an own perspective or own views and you want to use
the latest Fiori Task App and OData service version 3, some upgrade tasks are
required. Contact OpenText Customer Support and ask for the relevant activities to
upgrade a custom Fiori Task App to version 3.

OpenText Business Center for SAP Solutions – Installation Guide 37

BOCP160300-IGD-EN-01
Glossary
ArchiveLink

Service integrated in the SAP NetWeaver Application Server ABAP for linking
archived documents and the application documents entered in the SAP ERP
system.

Business Center Capture (BCC)

OpenText Business Center Capture for SAP Solutions. Optical character

recognition (OCR) component of Business Center.

Business Center Foundation

Central Business Center unit that serves to import, capture, dispatch, process, and
consume business objects. It comprises Inbound Configuration, Process Foundation,
Process Configuration, Business Center Workplace, and Fiori Task App.

Business Center Workplace

Central tool to process work objects. It provides an inbox with personal and
shared work item lists to the user. It also provides access to different business
objects and status information for all objects in process. The user can switch
between work centers and navigate in a process-dependent tree.

Business Center

OpenText Business Center for SAP Solutions. OpenText product that helps
receiving incoming documents, capturing processes, and filing them within a SAP
system.

Data View (View)

Dynamic part of a perspective. A set of views is shown in the template at specific

locations at runtime. For each perspective, you can define which view appears at
which location in its template. You can insert each view only once in each
perspective.

Fiori Task App

Light-weight web application following the design principles of SAP Fiori. It

provides an inbox showing the items that have been assigned to the logged-in
user. The user then is able to complete items by performing dedicated actions,
entering comments, and editing the data.

Inbound Configuration

Connection to various inbound channels, for example scanned paper documents,

fax, email, or IDoc, and the corresponding configuration. Business Center
Inbound Configuration is also used in VIM.

OpenText Business Center for SAP Solutions – Installation Guide 39

BOCP160300-IGD-EN-01
Glossary

Perspective

Web Services element that defines which item related data is displayed in the
Fiori Task App and where. A perspective defines the content and visual
appearance of items for a specific area of the screen in the Fiori Task App. The
Fiori Task App displays only one perspective at the same time.

Process Configuration

Easy and technically simplified configuration of complex business scenario

aspects. Process Configuration covers profile configuration, profile assignment,
and authorizations.

Process Foundation

Flexible framework to configure and run processes. It utilizes generic workflow

definitions, which are processed by the SAP Business Workflow engine.

Solution Accelerator

Preconfigured business scenario that ensures a fast implementation phase. The

following solution accelerators are available: incoming sales orders, purchase
order / purchase requisition, incoming delivery notes, incoming HR documents,
incoming remittance advices, and incoming order confirmations.

Vendor Invoice Management (VIM)

Packaged business solution that solves a business problem – paying correct

amount to vendors on-time and with the lowest cost. VIM delivers not technology
but best-practice business processes. VIM provides values to customers in process
efficiency, visibility and compliance. Business Center is tightly integrated with
VIM.

Web Services

Underlying technical concept of the Fiori Task App interface. You configure the
complete content of the Fiori Task App either by customizing or by implementing
an interface for the Web Services.

Work object type

Processing object in the Business Center Workplace. It can represent a process

object, a SAP business object, or information from any SAP tables.

40 OpenText Business Center for SAP Solutions – Installation Guide

BOCP160300-IGD-EN-01