OpenText Vendor Invoice Management for SAP Solutions 20.4 - Configuration Guide for Foundation English (BOCP200400-CGD-EN-06) (1)

OpenText™ Vendor Invoice Management
for SAP® Solutions
Configuration Guide for Foundation
This guide describes the general configuration of the

Foundation component of Vendor Invoice Management.
The components of Vendor Invoice Management include

Foundation, Invoice Solution, and Solutions Beyond Invoice.
BOCP200400-CGD-EN-06
OpenText™ Vendor Invoice Management for SAP® Solutions
Configuration Guide for Foundation
BOCP200400-CGD-EN-06
Rev.: 2021-Feb-22
This documentation has been created for OpenText™ Vendor Invoice Management for SAP® Solutions 20.4.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.
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 © 2021 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.
Table of Contents
1 About Vendor Invoice Management for SAP Solutions ......... 7
1.1 Architectural Overview ....................................................................... 9
1.2 About this document ........................................................................ 10
2 Basic configuration ................................................................. 13

2.1 Activating BC sets ........................................................................... 13
2.2 Configuring authorization ................................................................. 14
2.3 Configuring logical systems ............................................................. 15
Part 1 Customizing 17
3 General settings ...................................................................... 19

3.1 Configuring general settings ............................................................ 19
3.2 Configuring logical systems ............................................................. 23
3.3 Configuring plug-in integration ......................................................... 24
3.4 Configuring logging ......................................................................... 29
3.5 Integrating translation services ......................................................... 32
3.6 Configuring Analytics ....................................................................... 33
4 Inbound Configuration ............................................................ 51

4.1 Customizing basic settings for Inbound Configuration ........................ 52
4.2 Configuring channels ....................................................................... 55
4.3 Creating scenario classifications ...................................................... 56
4.4 Customizing incoming documents through the document handler ....... 58
4.5 API for document registration ........................................................... 91
4.6 Add additional logic to standard actions (BAdI /OTX/
PF32_IDF_WOBJ_ACTION) ............................................................ 93
4.7 Rendition management ................................................................... 95
5 Capture Integration ................................................................. 97

5.1 Business Center Capture ................................................................. 97
5.2 Information Extraction Service ......................................................... 99
5.3 Customizing validation ................................................................... 150
5.4 Customizing feedback ................................................................... 154
5.5 Creating reject reasons ................................................................. 155
5.6 Customizing look-ups .................................................................... 155
5.7 Mapping a look-up field ................................................................. 158
6 Process Foundation .............................................................. 161

6.1 Basic Settings ............................................................................... 162
6.2 Data model configuration ............................................................... 163
6.3 Process Foundation profile ............................................................ 172
BOCP200400-CGD-EN-06 Configuration Guide for Foundation iii

Table of Contents
6.4 Business data model assignment ................................................... 173
7 Process Configuration .......................................................... 175

7.1 Profile configuration ...................................................................... 175
7.2 Profile assignment ......................................................................... 223
7.3 Authorizations ............................................................................... 224
8 Workplace Configuration ...................................................... 227

8.1 Work object types ......................................................................... 230
8.2 Exit for dynamic filter criteria .......................................................... 255
8.3 Navigation .................................................................................... 256
8.4 Authorization objects ..................................................................... 265
9 Fiori Task App ........................................................................ 269

9.1 Application modes ......................................................................... 270
9.2 Navigation capabilities ................................................................... 278
9.3 Editing perspectives and layouts .................................................... 281
9.4 Basic settings ............................................................................... 296
9.5 Work object type ........................................................................... 298
9.6 Workplace .................................................................................... 310
9.7 Configuring the data binding of perspectives ................................... 321
9.8 Input helps .................................................................................... 339
9.9 Action dialog box ........................................................................... 341
9.10 Enabling inplace document viewing for iPhone and iPad .................. 370
9.11 Integrating UI5 widgets for Extended ECM or Document Access ...... 371
9.12 Interfaces and exits ....................................................................... 373
9.13 Helper classes for exit methods: /OTX/PF62_CL_UTILITIES ........... 438
9.14 Configuring deprecated views ........................................................ 440
10 Fiori Task App running scenarios ....................................... 449

10.1 On-premises integration ................................................................ 449
10.2 SAP Cloud Platform integration ...................................................... 453
11 Fiori Monitoring and Analytics reports ............................... 459

11.1 Generation and configuration ......................................................... 459
11.2 Custom Extensions ....................................................................... 465
12 Accessing archived documents using a proxy service ..... 467
13 Useful methods ...................................................................... 469

13.1 /OTX/
PF00_CL_UTILITIES=>STRUCTURE_FIELD_VALUE_CONVERT .. 469
13.2 /OTX/
PF00_CL_UTILITIES=>FIELD_VALUE_CONVERT_STRUCTURE .. 469
13.3 /OTX/PF00_CL_UTILITIES=>TABLE_DATA_PACK ........................ 469
iv OpenText™ Vendor Invoice Management for SAP® Solutions BOCP200400-CGD-EN-06

Table of Contents
13.4 /OTX/PF00_CL_UTILITIES=>TABLE_DATA_UNPACK ................... 469

13.5 /OTX/PF00_CL_UTILITIES=>STRUCTURE_DATA_PACK .............. 470
13.6 /OTX/PF00_CL_UTILITIES=>STRUCTURE_DATA_UNPACK ......... 470
14 Document classification ....................................................... 471

14.1 Document type handling ................................................................ 473
14.2 Processing impacts ....................................................................... 474
14.3 Classification integration ................................................................ 476
14.4 BAdI /OTX/PF40_CLASSIFICATION .............................................. 476
15 Troubleshooting .................................................................... 479

15.1 Fiori Monitoring and Analytics reports ............................................. 479
GLS Glossary 483
BOCP200400-CGD-EN-06 Configuration Guide for Foundation v

Chapter 1
About Vendor Invoice Management for SAP

Solutions
OpenText Vendor Invoice Management for SAP Solutions (VIM) is an ABAP add-on
solution to SAP ECC and SAP S/4HANA.
VIM automates the processing of incoming documents into SAP.
Document-centric business processes like the processing of incoming invoices from

vendors or incoming sales orders from customers are typical use cases for VIM.
After capture, data is enriched and validated against predefined business rules.
If no business rules fail, the document is posted in SAP without human intervention.
Although a straight through, no-touch process is the ultimate objective, VIM also
supports the fast and efficient handling and resolution of exceptions.
Exceptions are routed via workflow to the relevant user or user group based on the
role assigned to the exception.
For managers VIM offers a comprehensive suite of operational and analytical

reports. In addition, VIM offers the tools to identify common exceptions that should
be addressed to achieve even higher levels of automation.
VIM includes the following solutions:
• Invoice Solution
• Procure to Pay Solutions
– Order Confirmation
– Delivery Note
– Quotation
• Order to Cash Solutions
– Sales Order
– Remittance Advice
Each solution consists of a best practice implementation for a specific document

scenario. It includes preconfigured mapping rules, enrichment rules, business rules,
user roles and user actions. Learning-based enrichments features embedded easy to
configure machine learning that automates input based on previous user input.
BOCP200400-CGD-EN-06 Configuration Guide for Foundation 7

Chapter 1 About Vendor Invoice Management for SAP Solutions
Since VIM resides inside SAP, enrichments and business rules have direct access to
SAP master and transactional data, which avoids complex interfaces and the
replication and duplication of data.
Each solution offers a Workplace used by end-users and managers to manage and
monitor outstanding and completed work items. Each solution includes a
preconfigured set of analytical measures tailored for the specific document scenario.
Solutions can be enhanced to support company-specific business requirements.
VIM Solutions use features offered by its powerful feature rich Foundation.
The VIM Foundation consists of the following components:
• Inbound
• Process
• Workplace
• Analytics
VIM also supports custom solutions where a preconfigured solution is not available
for a specific, less common business process.
VIM offers a simple and intuitive user interface for end-users, managers and
administrators.
Users can choose between the classic SAP GUI or the modern SAP Fiori interface.
SAP Fiori offers a responsive web-based user interface that supports desktop and
mobile devices.
VIM supports various input channels including scan, fax¸ e-mail and web services.
It also supports various input formats, including paper, PDF, TIFF, IDoc and XML.
VIM requires an ArchiveLink-compliant SAP-certified content repository for the

storage of incoming documents. OpenText recommends OpenText Archiving and
8 OpenText™ Vendor Invoice Management for SAP® Solutions BOCP200400-CGD-EN-06

1.1. Architectural Overview
Document Access for SAP Solutions or OpenText Core Archive for SAP Solutions for
the storage of documents.
VIM integrates seamlessly via its Inbound component with OpenText Intelligent
Capture for SAP Solutions and OpenText Core Capture for SAP Solutions, which
uses advanced machine learning algorithms to extract metadata from imaged-based
documents like PDF and TIFF.
VIM also offers integration with OpenText Extended ECM for SAP Solutions and
OpenText Document Presentment for SAP Solutions.
1.1 Architectural Overview

The following figure gives an overview of the basis architecture. It shows how the
core components of VIM are integrated into SAP and which additional OpenText
components like Document Pipeline, Document Storage, Information Extraction
Service and WebViewer are completing the solution.
Beside the components of this graphic, VIM offers additional components such as
SAP NetWeaver Business Warehouse or BW/4Hana for specific solutions which are
not shown in this basis architectural overview.
Figure 1-1: Technical system landscape

Chapter 1 About Vendor Invoice Management for SAP Solutions
1.2 About this document

This document describes the configuration of the Foundation component of Vendor
Invoice Management for SAP Solutions. It also describes the various implementation
aspects of configuring the Foundation component to suite the specific business
requirements for any organization. Vendor Invoice Management is designed to be
highly configurable to accommodate varied business scenarios.
To learn about the administration tasks of Vendor Invoice Management is designed,

see OpenText Vendor Invoice Management for SAP Solutions - Installation Guide
(VIM200400-IGD).
1.2.1 Target audience

This document addresses those who participate in the customization and
implementation of the Foundation component of Vendor Invoice Management for
SAP Solutions. This includes:
• SAP Basis Administrators

• SAP Workflow Administrators
• SAP Configuration and Development Support
1.2.2 Further information sources

Product docu- The following documentation is available for Business Center on OpenText My
mentation Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/10151494):
• OpenText Vendor Invoice Management for SAP Solutions - User Guide for Invoice
Solution (VIM200400-UGD)
• OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIM200400-CGD)
• OpenText Vendor Invoice Management for SAP Solutions - Administration Guide
(VIM200400-AGD)
• OpenText Vendor Invoice Management for SAP Solutions - Reference Guide for Invoice
Solution (VIM200400-RGD)
• OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide for Invoice
Solution (VIM200400-CCS)
• OpenText Vendor Invoice Management for SAP Solutions - Security Guide
(VIM200400-GSM)
• OpenText Vendor Invoice Management for SAP Solutions - Security Guide
(VIM200400-GSM)
Foundation (BOCP200400-CGD)
Solutions Beyond Invoice (BOCP200400-CCS)

1.2. About this document
• OpenText Vendor Invoice Management for SAP Solutions - User Guide for Solutions
Beyond Invoice (BOCP200400-UGD)
For the particular solutions, guides are available on OpenText My Support.

Documentation for the Solution for Incoming Sales Orders and Solution for
Incoming Quotations is available in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP200400-CCS).
Release Notes Release Notes describe:
• The software supported by the product

• Requirements
• Restrictions
• Important dependencies
• New features
• Known issues
• Fixed issues
• Documentation extensions
The Release Notes are updated continuously . The latest version of the Business
Center Release Notes is available on OpenText My Support (https://
knowledge.opentext.com/knowledge/cs.dll/Open/10151494).

Chapter 2
Basic configuration
Before you start with installation and detailed configuration, make sure that the
following actions have been performed:
• Install and configure an archiving system that supports the SAP HTTP Content
Server interface.
• Create User IDs with appropriate developer and configuration authorizations.
Authorizations need to include developer as well as workflow administrator
authorizations.
• Make sure that the SAP Business Workflow Runtime Engine is configured.
The configuration steps describe the basic mandatory customizing. This customizing
must be done with every installation and for every used solution. For the solution
specific customizing, see the respective parts in this document.
2.1 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.
• When you activate the BC sets, you might get dialog boxes, for example a
message about an error in Object Editing. Just confirm them with Copy
Values or OK.
Activate the BC sets only for English language. Other languages are delivered with
specific language packs. You find the language packs on OpenText My Support.
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:

Chapter 2 Basic configuration
• /OTX/PF00_BASE_006 for the OpenText Process Base.

• /OTX/PS00_BASE_006 for the OpenText VIM Solution Base
• /OTX/PFRM_ECM_004 for OpenText VIM Extended ECM Integration
Important
After updating the backend versions and activating the BC sets, you must
execute the transaction /OTX/PF62_ADMIN in this backend system and clean up
WebIds, search helps and DataCollections.
2.2 Configuring authorization

Foundation component of Vendor Invoice Management for SAP Solutions is
delivered with new authorization objects. SAP authorization object SAP_ALL must
be regenerated to apply the authorizations to this object. The delivered authorization
objects are described in the following sections in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Foundation (BOCP200400-
CGD):
• Workplace Configuration: Section 8.4 “Authorization objects” in OpenText Vendor

Invoice Management for SAP Solutions - Configuration Guide for Foundation
(BOCP200400-CGD)
• Process Configuration: Section 7.3 “Authorizations” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Foundation (BOCP200400-
CGD)
With the Foundation component of Vendor Invoice Management for SAP Solutions,
the following general authorization objects are delivered:
Authority Description Usage

J_6NPF_NAV Checks navigation in workplace according Business Center
to the workplace ID. For more Workplace
information, see Section 8.4
“Authorization objects” in OpenText
Vendor Invoice Management for SAP
Solutions - Configuration Guide for
Foundation (BOCP200400-CGD).
J_6NPF_WTY Checks work object type with related Business Center
actions, functions, and nodes. For more Workplace

2.3. Configuring logical systems
Authority Description Usage

J_6NPF_PRF Checks the process configuration profile Processing Screen
with profile ID, characteristic attribute, Business Process
and process step. For more information,
see Section 7.3 “Authorizations” in
OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide for
J_6NPF_ADM Is checked in all administrative reports, Administration
transactions, and programs. For more
J_6NPF_RFC Is checked in all RFC functions and Processing
executable programs. For more
2.3 Configuring logical systems

The Business Center Workplace can connect to various systems and collect related
data from these systems.
The Inbound Configuration also enables a multiple-system access by starting the

application process on a specific target system when using one system for document
registration.
On each system running VIM Foundation, there must be an entry with LOCAL as
logical system. For every system that needs to be connected, an additional entry is
required. For more information, see Section 3.2 “Configuring logical systems” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for

Part 1
Customizing
Part 1 Customizing
VIM Foundation provides different components, which are each configured in a

special area in the /OTX/PF00_IMG IMG transaction.
Important
• Do not change the delivered customizing entries of BC Sets but create new
profiles and new settings.
• New configuration must have the prefix Z_ or 9xx according to the data
element.

Chapter 3
General settings
The general settings are global settings, which are used in different areas.
The General Settings customizing structure in the /OTX/PF00_IMG transaction

contains all views that are relevant for the different components.
3.1 Configuring general settings

The general settings are used to configure global parameters.
To configure general settings:
1. Run the /n/OTX/PF00_IMG transaction.

2. Click OpenText Business Center for SAP Solutions > General Settings >
General Settings.
3. In the General Settings Overview screen, configure the following global
parameters.
Validity time for locks in seconds

Enter the validity time for lock entries.
Note: The validity time is only used in the context of the Fiori Task
App. Lock entries in SAP GUI only get a timeout if a session timeout
occurs. For more information, see “Configuring locking” on page 20.
Validity for data collections in seconds
Define the validity time for data collections in seconds. Clean up reports
like /OTX/PF62_ADMIN only remove data collections that are not valid
anymore.

Chapter 3 General settings
Logo is displayed in Workplace and Index Screen

Enter X to display the logo in Business Center Workplace and Processing
Screen.
Logo description for accessibility mode
Enter a meaningful description for the logo, which will be used in
accessibility mode, for example by a screen reader software.
Height of logo
Enter the height of the logo if a custom logo must be displayed with
individual height.
URL for logo
Enter the URL for the logo that is displayed in Business Center Workplace
and Processing Screen. You can upload a custom logo with the SMW0
transaction.
Location for Document URL generation for Fiori App
Enter EXTSDOKLOC to define the external location that is used at the URL
generation for a document, if the URL is requested from the Fiori Task App.
For more information, see “Accessing archived documents using a proxy
service“ on page 467.
3.1.1 Configuring locking

A general locking mechanism for SAP GUI transactions and the Fiori Task App is
available. This locking mechanism works comprehensively and independently of
solutions.
This mechanism concatenates the key fields of the object to a key for the object
identification. This key has a maximum length of 117 characters. The Fiori Task App
builds this key as defined in the key definition of the work object type. For more
information, see “Defining keys for the work object type” on page 299.
For the key definition, the Process Configuration always uses the fields PROJECT_ID,
PLKEY, and WI_ID. Work object types for process instances of the Process
Configuration must use exactly these fields. The standard lock is always set in the
logical system of the object.
All locks have a limited validity. By default, the validity is 1800 seconds.
To change the lock validity:

General Settings.
3. In the General Settings Overview screen, change the lock validity using the
parameter Validity time for locks in seconds.
The Fiori Task App can request a change for a lock entry. In this case, a check value
checks if the change applies to the same lock entry that was originally requested by

3.1. Configuring general settings
this instance of the Fiori Task App. This check value is generated and returned to the
requestor at the set of lock entries. You must use the check value as import
parameter for all further changes that are requested for this lock entry.
You can implement additional lock operations using the /OTX/PF00_LOCK BAdI.
This BAdI has the following interface.
CHECK_LOCK_WOBJ method – This method is called to check if an object is

locked. This method is only called if the standard BC check does not find a lock
entry for this object.
Parameter Type Description

PI_ID Importing Object ID
PI_WOBJ_TYPE Importing Work object type
PI_CHECK_VALUE Importing Generated check value created at the set of
the standard lock entry
PIS_LOCK Importing Existing entry in locking table
PC_LOCK_ED Changing Is object locked?
PCS_LOCK_MESSAGE Changing Message
SET_LOCK_WOBJ method – This method is called when an instance of a work

object type is locked.

PI_MODE Importing Mode (Web UI or SAP GUI)
PI_LOGSYS Importing Logical system
PC_LOCK_STATUS Changing Possible values:
SUCCESS - Successfully locked
LOCKED - Foreign lock
TECH_ERROR - Technical error
TIMEOUT - Lock is not valid anymore
PC_LOCK_TIMEOUT Changing This parameter contains the calculated
time when the lock ends. It can be
changed within these BAdI’s methods.
The changed time is then considered by
the standard BC lock / locking mechanism.
SET_LOCK_PROJECT method – This method is called when a process instance is

locked.

For the interface, see “SET_LOCK_WOBJ method” on page 21. Instead of parameter
PI_WOBJ_TYPE, parameter PI_PROJECT is used. It contains the project ID of the
corresponding process instance.
REMOVE_LOCK_WOBJ and REMOVE_LOCK_PROJECT methods – These

methods are called when an instance of a work object type or a process instance is
unlocked.

PI_WOBJ_TYPE or Importing Work object type or
PI_PROJECT Project ID
UPDATE_LOCK_WOBJ and UPDATE_LOCK_PROJECT methods – These

methods are called when the lock for a work object type instance or a process
instance is updated. Time out is exceeded.

PC_LOCK_STATUS Changing Possible values:
SUCCESS - Successfully locked
LOCKED - Foreign lock
TECH_ERROR - Technical error
TIMEOUT - Lock is not valid anymore
PC_LOCK_TIMEOUT Changing This parameter contains the calculated
(UPDATE_LOCK_WOBJ only) time when the lock ends. It can be
changed within these BAdI’s methods.
The changed time is then considered by
the standard BC lock / locking mechanism.
DELETE_LOCK_WOBJ and DELETE_LOCK_PROJECT methods – These methods

are called when the lock entry for a work object type instance or a process instance is
deleted.

3.2. Configuring logical systems

CONVERT_OBJECT_ID_WOBJ and CONVERT_OBJECT_ID_PROJECT

methods – With these methods, you can replace the technical object key with any
other text. These methods are called, for example, before messages are displayed, so
that the user gets a meaningful object description.

PC_ID_TEXT Changing Description of the object instance, which is
used in messages instead of technical
object key
3.2 Configuring logical systems

The Business Center Workplace can connect to various systems and collect related
data from these systems.
The Inbound Configuration enables a multiple-system access, as well. The

application process can start on a specific target system when using one system for
document registration.
Caution
On each system running VIM Foundation, an entry with LOCAL as logical
system must exist. For this entry, no RFC destination must be maintained.
To configure logical systems:
Logical Systems.
3. In the Logical Systems Overview screen, configure logical systems, using the
following parameters.

Logical system
Name of the logical system. See the SAP documentation on how to set up a
logical system.
Description
Enter a description of the system.
RFC for System Communication
Enter the RFC destination for communicating to the system. OpenText
recommends that you use this RFC destination with system or
communication users, not with dialog users. See the SM59 transaction to
create an RFC destination.
RFC for Dialog Communication
Enter the RFC destination for communicating by active dialog screen.
OpenText recommends that you use a trusted RFC destination in this case.
See the SAP documentation on how to set up trusted connections between
SAP ERP systems.
3.3 Configuring plug-in integration

Different end-user screens (Business Center Workplace, Processing Screen) are
enabled to use integrated plug-in views to display detail information for a process.
The following customization steps are necessary:
• Define the plug-in type

• Define the plug-in ID
• Assign the plug-in IDs to plug-in types
• Assigning the plug-in IDs to business objects
Business Center delivers the following application plug-ins:
Processing Screen
• Display archived image: /OTX/PF41_CL_PLUGIN_IDX_IMAGE

• Display Line Items: /OTX/PF41_CL_PLUGIN_IDX_ITEMS
• Display Comments: /OTX/PF41_CL_PLUGIN_IDX_NOTE
• Display History: /OTX/PF41_CL_PLUGIN_IDX_HIST
Business Center Workplace - Process work object
• Display archived image: /OTX/PF31_CL_PLUGIN_BPF_IMAGE

• Display Line Items: /OTX/PF31_CL_PLUGIN_BPF_ITEMS
• Display Comments: /OTX/PF31_CL_PLUGIN_BPF_NOTE
• Display History: /OTX/PF31_CL_PLUGIN_BPF_HIST

3.3. Configuring plug-in integration
• Display Agents: /OTX/PF31_CL_PLUGIN_BPF_AGENT

• Display BPF Process Log: /OTX/PF31_CL_PLUGIN_BPF_LOG
Business Center Workplace - Inbound Configuration work object
• Display External Data: /OTX/PF32_CL_PLUGIN_IDF_EXTDAT

• Display History: /OTX/PF32_CL_PLUGIN_IDF_HIST
• Display Image: /OTX/PF32_CL_PLUGIN_IDF_IMAGE
• Display Application Log: /OTX/PF32_CL_PLUGIN_IDF_LOG
Business Center Workplace - Mixed work objects
• Display SD document flow: /OTX/PS99_CL_SD_DOCFLOW

• xECM Workspace: /OTX/PFRM_CL_PLUGIN_WOBJ
Note: To integrate the xECM Workspace plug-in into the Business

Center Workplace, you must assign the delivered xECM plug-in ID to
the related plug-in types (see “Assigning the plug-in IDs to plug-in
types” on page 28) because this setting is not delivered in a BC set.
The following plug-in IDs are delivered in the xECM Integration BC set.
You can assign them to the corresponding plug-in types:
– PFRM_ECM_CUST - Display Customer Workspace (object KNA1) using

field KUNNR
– PFRM_ECM_CUST2 - Display Customer Workspace (object KNA1) using
field KUNAG
– PFRM_ECM_VEND - Display Vendor Workspace (object LFA1) using
field LIFNR
• GOS Attachment List: /OTX/PF31_CL_PLUGIN_BPF_GOSAT
3.3.1 Defining the plug-in type

To use different plug-ins in different end-user screens, a plug-in type definition is
used to combine all plug-ins within one control.
To define the plug-in type:
1. Run the /n/OTX/PF00_IMG transaction and navigate to OpenText Business

Center for SAP Solutions > General Settings > Processing Plug-In
Configuration > Define Plug-In Types.
2. In the Plug-In Type Definition Overview screen, define the plug-in type, using
the following parameters:

Plug-In Type
Unique ID of a plug-in type to be used within an end-user screen.
Plug-In Type Description
Enter a description of the plug-in type.
3.3.2 Defining the plug-in ID

The plug-in ID definition describes all necessary technical information for the called
plug-in.
To define the plug-in ID:

Configuration > Define Plug-In IDs.
2. In the Plug-In Definition Overview screen, define the plug-in ID, using the
following parameters:
Plug-In ID
Unique ID of the plug-in.
Plug-In title
Enter the title of the plug-in, which is displayed on the button in the plug-in
toolbar.
Plug-In description
Enter the tooltip of the plug-in, which is displayed on the button in the
plug-in toolbar.
Plug-In class
To process the corresponding logic for the plug-in, enter the class to be
called during runtime.
For more information, see “Methods of the plug-in superclass /OTX/
PF00_CL_PLUGIN” on page 26.
Note: You may want to create a completely new plug-in from scratch
for which no suitable standard class implementation is already
available. In this case, you must create your own plug-in class with
superclass /OTX/PF00_CL_PLUGIN.
Plug-In Icon
Enter the icon of the plug-in, which is displayed on the button in the plug-in
toolbar.
Methods of the plug-in superclass /OTX/PF00_CL_PLUGIN

The following methods are available for redefinition. OpenText recommends that
you do not change any other method.

3.3. Configuring plug-in integration
PLUGIN_CONTROL_INIT – You must use this method to initiate a plug-in SAP

GUI control.
Parameter Parameter type Description

PIH_PARENT Importing Parent control to which the plug-in control
must be embedded
PIH_DATA Importing Currently used plug-in data context
PLUGIN_CONTROL_REFRESH – You must use this method to refresh a plug-in

SAP GUI control.

PIH_PARENT Importing Parent control to which the plug-in control
must be embedded
PIH_DATA Importing Currently used plug-in data context
FREE – You must use this method to reset the corresponding plug-in SAP GUI
control and any used data or class attributes.
PLUGIN_ACTIVE_SKIP – Use this method to apply any custom logic in order to

dynamically skip the creation of the corresponding plug-in button during runtime.

PE_SKIP Returning Dynamically skip the plug-in button
creation during runtime.
PLUGIN_BUTTON_MODIFY – Use this method to modify the appearance of the

created plug-in button during runtime.

PC_ICON Changing Button icon
PC_TITLE Changing Button title text
PC_TOOLTIP Changing Button tooltip
PLUGIN_DATA_CONTEXT_SET – You must use this method to set the plug-in

data context.

3.3.3 Assigning the plug-in IDs to plug-in types

You define the possible plug-ins for a plug-in type within the mapping. For each
defined plug-in type, all plug-in definitions are maintained.
To assign plug-in IDs to plug-in types:

Configuration > Assign Plug-In IDs to Plug-In Types.
2. In the Plug-In Type Mapping Overview screen, assign plug-in IDs to plug-in
types, using the following parameters:
Plug-In Type
Unique ID of the plug-in type definition.
Plug-In ID
Unique ID of the plug-in definition.
Plug-In Sequence
Define the order of the buttons for the plug-in.
Handle
Define a unique ID of the Handle.
For one plug-in type you can assign different plug-in definitions that
implement an ALV table control (for example History, Actual Agent or Line
Items). For each ALV table control, you can store an individual layout. To
provide this functionality if there are several plug-in definitions assigned to
one plug-in type, the Handle must be different for the plug-in IDs that
implement an ALV table control.
Note: Special number ranges are used for Handle values, any custom
plug-ins must use the Handle number range 8000 - 9999.
PI Active
Select this check box to activate the plug-in on the screen.
3.3.4 Assigning plug-in IDs to business objects

You can assign plug-in IDs that are used in a different business context to different
business objects. For the Extended ECM for SAP Solutions plug-in and the GOS
attachment plug-in, you must assign the plug-in to the specific business object and
to the related key fields of the business object of the source data structure.
To assign plug-in IDs to business objects:
Processing Plug-In Configuration > Assign Plug-In IDs to Business Object.

3.4. Configuring logging
3. In the Plug-In Business Object Relation Overview screen, assign plug-in IDs to
business objects, using the following parameters.
Plug-In ID
Unique ID of the plug-in definition.
Object Type
Enter the SAP business object type used by the plug-in.
Field List (Key)
Enter key fields of the business object in a comma-separated list. The key
fields are used in the data context provider of the plug-in class to get the
related information.
3.4 Configuring logging

The application log is used to store the status information of each task of the
incoming document handler. Like the Incoming Document Framework (IDF), all
other components create an application log that you can use to check the status in
case of any issue.
To view the application log, run the SLG1 transaction. You can access the whole
application log in the /OTX/PF00 object. To access a specific component of the log,
you can use the related sub-objects.
Sub-objects of /OTX/PF00
• /OTX/PF00: Basic functions logs component OTBCBAS

• /OTX/PF01: Inbound Configuration logs component OTBCFND / OTBCBAS
• /OTX/PF02: Process Foundation logs component OTBCFND / OTBCBAS
• /OTX/PF03: Workplace Configuration logs component OTBCFND / OTBCBAS
• /OTX/PF05: Web Services - Metadata logs component OTBCWSR / OTBCWUI
• /OTX/PF06: Web Services - Data provider logs component OTBCWSR / OTBCWUI
• /OTX/PF08: Analytics Configuration logs component OTBCFND / OTBCBAS
• /OTX/PFRM: Extended ECM Integration logs component OTBCRM
• /OTX/PF61: Web Services - Interface logs component OTBCFND / OTBCBAS /
OTBCWSR / OTBCWUI

3.4.1 Configuring log levels

To configure what information should be logged, you can globally configure a log
level for the related component.
To configure log levels:
Logging > Log Levels.
3. In the Log Levels Overview screen, configure log levels, using the following
parameters.
Object
Name of the log object
Subobject
Name of the detailed log-subobject
Loglevel
Enter the level at which issue types should be logged (this level and higher)
• very important
• important
• medium
• Additional information
• Other
Days to expiry
Number of days until the created log entries expire. This setting is only
used if no detailed setting is found on log point level. If both values are not
maintained a default value of 90 days is used.
3.4.2 Configuring log points

The log point is a unique identifier for application or application area. The log point
helps in finding the area that is generating the message. The log point determines
the program from where the error is generated. Because the system is maintained
using Object and Subobject, the log point also determines them. If the log level is not
maintained at Log Point level, the global log level will be used; see “Configuring log
levels” on page 30.
To configure log points:

3.4. Configuring logging
Logging > Log Points.
3. In the Log Points Overview screen, configure log points, using the following
parameters.
Log Point
Unique log point
Short Text
Enter a description of the log point.
Program Name
Enter the name of the program or the part name of the program where the
log entry is written
Object
Enter the name of the log object
Subobject
Enter the name of the detailed log-subobject
Loglevel
Enter the level at which issue types should be logged (this level and higher)
• very important
• important
• medium
• Additional information
• Other
Days to expiry
Number of days until the created log entries expire. If no value is
maintained the log level setting is used. If both values are not maintained, a
default value of 90 days is used.

3.5 Integrating translation services

You can integrate an external web service for the translation of the process
comments in the Fiori Task App and in the comments plug-in of the Workplace and
SAP Processing Screen.
3.5.1 Configuring languages

To configure languages for the translation service:

Translation Service > Languages.
3. In the Languages Overview screen, configure languages, using the following
parameters:
Language:
SAP language key
Language Key:
Language key used within the translation service
3.5.2 BAdI for translation service

To activate the translation option, you also must implement the following BAdI to
call the web service:
Enhancement spot
/OTX/PF00_ES_SRV_TRANSLATION
BADI
/OTX/PF00_BADI_TRANSLATION
You must implement the following methods. The methods in the example class
maintained in the enhancement spot contain further instructions.
GET_AVAILABLE_LANGUAGES
This method returns the allowed target languages for translations. Required are
the language key in the format for the translation service and the corresponding
SAP language key with the description.
The /OTX/PF00_CL_TRANSLATION_FALL example class B provides logic to read
the available languages from the language configuration. Copy the example
class during your BAdI implementation.
CALL_TRANSLATION_SERVICE
In this method, you can implement the call to the external translation service.
You find examples how to call the web service in the API description of the
chosen service provider.

3.6. Configuring Analytics
You must send the input string (PIV_INPUT) to the external service. You must
export the translated string in export parameter PEV_TRANSLATED_STRING. The
requested language is imported in parameter PIV_LANGUAGE.
Note: As the source language of the comment string cannot be safely
determined from ABAP side, an additional call to a language
determination service might be necessary. Some translation services
include this determination when calling the translation service.
IS_ACTIVE
This method returns whether the Translate action should be displayed in the
Fiori apps. To activate this functionality globally, you can set the export
parameter PEV_ACTIVE to true (X) without any further logic.
The method provides several import parameters for more complex activation
logic, for example to build activation logic based on authorizations.
3.6 Configuring Analytics

Regarding analytic evaluations, different requirements exist.
SAP provides a lot of different tools to create analytic reports, for example SAP
Smart Business, SAP Lumira, SAP BW, SAP Business Objects, or the classic SAP GUI
ALV.
Due to this variety of tools and due to the fact that all customers have different
reporting requirements, OpenText does not provide an Analytics report.
What OpenText provides is a layer with a lot of data, prepared for evaluations. This
data may serve as a base for end user reports, which you can create using your
preferred reporting tool.
You can perform analytic evaluations on database tables that are written throughout
the process. These database tables contain the transactional data.
However, key figures may need to be transformed into different formats or they
need to be calculated “on the fly”.
In these cases, the runtime of analytic reports may decrease very quickly when the
amount of documents is growing. This is the reason, why OpenText decided to
introduce a further set of database tables, especially designed for the purpose of
Analytics. Let us call them Analytics database tables, being part of an Analytics
layer. You can configure whether these Analytics database tables are written or not.
This section describes this and other settings regarding the Analytics layer:
• It provides details how to configure the update of the Analytics layer.

• It provides details of the basic Analytics class that is updating the Analytics
database layer.
• It describes the available characteristics and key figures of the Analytics database
layer.

3.6.1 Introduction: Analytics Database Schema for business

processes
Regarding analytic evaluations for business processes, different requirements may
exist. By configuration, you can activate Analytics database tables Analytics
database tables for business processes. For more information, see “Configuring the
Analytics profile” on page 43. If not activated, the tables will stay empty. With
these tables, a lot of different evaluations are possible. This section gives an
introduction to the most important tables for evaluations for business processes.
The following graphic shows a Structured Entity Relationship (SERM) diagram of

the most important database tables that are available for analytic evaluations for
business processes.
Header related Analytics data

This database table comprises characteristics and key figures on process ledger
header level, like the total duration of the process or the number of touches per
document.
Activity related Analytics data

This database table comprises characteristics and key figures on user activity
level. In this context, an activity is defined as a processing unit of an end user.
This means, an activity starts as soon as an end user opens a work item in the
Business Center Workplace to work on it. It ends as soon as the work item is
closed. An activity also starts as soon as an end user starts editing data in the
Fiori Task App. It ends as soon as the end user clicks the Save button. An
example for a key figure related to an activity is the duration of an activity or the
number of actions done during an activity.
History related Analytics data

This database table comprises characteristics and key figures on history level. A
history logs all the actions of an end user. An example for a characteristic on
history level is the calendar week in which the action was started.
Process Step Log

This database table comprises snapshots of the process steps that failed or were
checked successfully at different points in time during a process.
Rule Log
This database table comprises snapshots of the rules that failed, passed
successfully, or that were inactive, skipped, or bypassed.

3.6.2 Available characteristics and key figures for completed

inbound processes
An inbound process registers and processes the incoming document of most
business processes.
This section gives an overview of the available data of the inbound process which
can be used for analytics of business processes.
Fields which are not described here are either technical fields or not relevant for
business processes. Some fields are reserved for future use.
Table 3-1: Characteristics
Name Description
INB_SYS Inbound Logical System
CHANNEL_ID Inbound Channel ID
REGID Inbound Registration ID
HANDLE_ID Inbound Handle ID
CLASSIFY Inbound Classify
ORIGIN_TIME Inbound Origin Time
ORIGIN_USER Inbound User
EDI_DOCNUM Inbound IDOC Number
EXTRACTION_IND Indicator that extraction is applied
VALIDATION_IND Indicator that validation is applied
EXTRACTION_TYPE Technical field:
• “CLOUD”: IES-API is applied.
• “”: BCC is applied.
CLOUD_EXTRACTION Technical field:
• “x”: IES Cloud is applied.
• “”: IES on Premise is applied.
PROC_FINISHED Indicator that the inbound process is finished
LOGSYS Logical system of the solution system
PROJECT_ID Profile ID of the solution
PLKEY Process ledger key of the solution
START_DATE Start date of the inbound process
START_TIME Start date of the inbound process
START_<...> Start week, month, quarter or year
depending on the <...> name

Name Description
END_DATE End date of inbound process
END_TIME End time of inbound process
END_<...> End week, month, quarter or year depending
on the <...> name
CHANGE_DATE Technical field: Date of the update of the log
entry
CHANGE_TIME Technical field: Time of the update of the log
entry
Note: Timestamps and time characteristics are provided in UTC format.
Table 3-2: Time characteristics
Name Description
TSP_REGISTER Timestamp for the document registration in
the inbound process
TSP_CHANGE Timestamp for an entry change in /OTX/
PF01_T_1REG table.
TSP_FINISH Timestamp for the completion of the
inbound process
TSP_UPDATE Timestamp for an entry update in /OTX/
PF08_T_REGA table
START_DATE Start date of the inbound process
START_TIME Start date of the inbound process
START_<...> Start week, month, quarter or year
depending on the <...> name
END_DATE End date of inbound process
END_TIME End time of inbound process
END_<...> End week, month, quarter or year depending
on the <...> name
CHANGE_DATE Technical field: Date of the update of the log
entry
CHANGE_TIME Technical field: Time of the update of the log
entry

Table 3-3: Key figures
Name Description
DOC_COUNTER The dummy document number is 1. When
cumulated it provides the number of
documents for a certain filtering.
PROC_DURATION_S The total inbound process time in seconds.
PROC_DURATION_M The total inbound process time in minutes.
PROC_DURATION_H The total inbound process time in hours.
PROC_DURATION_D The total inbound process time in days.
3.6.3 Available characteristics and key figures for business

processes
Currently, no UI is provided to display the basics of the Analytics database layer.
However, a lot of tools for that purpose are available. This section gives an overview
of the available data for Analytics and provides some examples.
• Characteristics are descriptions of fields, such as Customer ID, Sales Organization,

Company Code, Unit of Measure, and Purchase Order Date.
• Key figures are numeric values or quantities, such as Per Unit Sales Price,
Quantity Sold, and Order Placement Cycle Time in days.
Note: The guide can only provide some examples to give an idea about
possible evaluations. You can create a lot more evaluations with the existing
key figures.
Time characteristics are calculated using the UTC time zone. Use the available
timestamps in the tables to calculate user-specific time characteristics.
Additionally, you can enhance the Analytics class (see “Analytics class”
on page 48) to provide additional custom or solution specific key figures.
The examples are grouped by the underlying database table.
• “Example evaluations on Header Level” on page 38.
• “Example evaluations on Activity Level” on page 40.

• “Example evaluations on History Level” on page 41.
• “Example evaluations on Process Step Level” on page 42.
• “Example evaluations on Rule Level” on page 43.

3.6.3.1 Example evaluations on Header Level

Name of database table: /OTX/P<+++>_T_PLHA, where <+++> is replaced by 3
characters, for example /OTX/PS02_T_PLHA
With this table, you can design evaluations that deliver key figures on document
level, for example to get the number of documents processed in a given period of
time.
Name of Characteristic Example for usage

CHANNEL_ID Allows grouping and/or filtering by input channel
Example: Number of documents by channel
START_DATE, Time characteristic that allows grouping and/or filtering by
START_DAY, the start of the process
START_WEEKDAY, Example 1: Number of documents by channel last week
START_WEEK, Example 2: Average number of touches per document and
START_YRWEEK, month in the last year
START_MONTH, …
END_DATE, Time characteristic that allows grouping and/or filtering by
END_DAY, the end of the process
END_WEEKDAY, Example: Number of documents finished last month
END_WEEK,
END_YRWEEK, Note: If a business process is still running, the end
END_MONTH, … characteristics are not populated.
PROC_FINISHED Indicator which easily allows to distinguish running and
finished processes
Table 3-5: Key Figures - Process Counts
Name of Key Figure Example for usage

DOC_COUNTER Document Placement (number of documents) or
DOC_COUNTER Document Placement Channels (number of documents by
channel)
NO_ACTIONS Average number of actions per document
NO_CAT_CHECKED Average number of checked manual process steps per
document
NO_CAT_FAILED Average number of failed manual process steps per
document
NO_CAT_FAILED_I Average number of failed manual process steps per
document (at document entry)
NO_MOD_CHECKED Average number of rules needing manual interaction per
document
NO_MOD_BYPASSED Average number of bypassed rules per document


NO_MOD_FAILED Average number of failed rules needing manual interaction
per document
NO_MOD_FAILED_I Average number of failed rules needing manual interaction
per document (at document entry)
NO_DIALOG_ACV Average number of touches per document
NON_TOUCH_IND Perfect Document Placement (number of documents
processed non-touch)
Note: If a business process is still running, the duration key figures are not
populated.
Table 3-6: Key Figures - Timings

PROC_DURATION_D, Document Cycle Time (Total process time from start to end)
PROC_DURATION_S,
PROC_DURATION_H,
PROC_DURATION_M
PROC_DURATION_D, Document Cycle Time when rules failed (Total process time
PROC_DURATION_S, when rules failed)
NO_MOD_FAILED
ACV_DURATION_M, Document Processing Time (Summarized manual
processing time)
ACV_DURATION_D,
Note: The manual processing time cannot be
ACV_DURATION_H,
determined if the dialog step is not finished properly.
ACV_DURATION_S
Example: An end user started editing a document on
his notebook. The user does not close the application
by clicking Save or Cancel but closes the notebook or
terminates the process with operation system means.
In this case, the processing time from the start of the
editing to closing the notebook or terminating the
process is 0.

3.6.3.2 Example evaluations on Activity Level

Name of database table: /OTX/P<+++>_T_ACVA, , where <+++> is replaced by 3
characters, for example /OTX/PS02_T_ACVA
With this table, you can design user and role specific evaluations, for example to get
the number of documents processed by a user or role in a given period of time.

AGENT Allows grouping and/or filtering by user
Example: Number of documents processed by user last
month
ROLE_ID Allows grouping and/or filtering by role
Example: Number of documents processed by role last week
START_DAY, start of the activity
START_WEEKDAY, Example: Average number of activities per role and month
START_WEEK, in the last calendar year
START_YRWEEK,
START_MONTH, …
END_DATE, Time characteristic that allows grouping and/or filtering by
END_DAY, the end of the activity
END_WEEKDAY,
END_WEEK,
END_YRWEEK,
END_MONTH, …

ACV_COUNTER Number of touches by user or role in a period of time
NO_MOD_SUCC_DELT Number of rules solved by user or role in a period of time
NO_MOD_FAIL_DELT Number of rules raised by user or role in a period of time
NO_MOD_BYPA_DELT Number of rules that were bypassed by user or role in a
period of time
NO_ACTIONS Average number of actions per touch by role in a period of
time
Table 3-9: Key Figures - Timings

ACV_DURATION_M, Average processing time for a document by role
ACV_DURATION_S


ACV_DURATION_M, Average time spent by user for a document
ACV_DURATION_S
WAIT_TIME_M, Average time it took until users processed the document
WAIT_TIME_D,
WAIT_TIME_H,
WAIT_TIME_S
ACV_DURATION_M, Breakdown between wait time and work time by role
ACV_DURATION_D,
ACV_DURATION_H
ACV_DURATION_S,
WAIT_TIME_D,
WAIT_TIME_S
3.6.3.3 Example evaluations on History Level

Name of database table: /OTX/P<+++>_T_HISA, where <+++> is replaced by 3
characters, for example: /OTX/PS02_T_HISA
With this table, you can design evaluations providing information about user
actions, for example an evaluation how often a specific action, like the Refer action,
has been performed in a given time period.

PROFILE_ID, VERSION, Allows grouping and/or filtering by action
ACT_ID Example: Top n actions in the last week (most frequently
executed actions)
PROFILE_ID, VERSION, Together with a JOIN operation to the header table /OTX/
ACT_ID P<+++>_T_PLHA, the following evaluation is possible:
Number of documents with a specific action
AGENT Allows grouping and/or filtering by user
Example: Number of a specific action by user in the last
month
ROLE_ID Allows grouping and/or filtering by role
Example: Number of a specific action per role in the last
quarter


START_DAY, point of time when the action was executed
START_WEEKDAY, Example: actions overview (list of actions that were
START_WEEK, executed in a period of time)
START_YRWEEK,
START_MONTH, …

HIST_COUNTER Number of a specific action, for example Refer, by user or
role in a period of time
HIST_COUNTER Together with a JOIN operation to the header table /OTX/
P<+++>_T_PLHA, the following evaluation is possible:
Average number of a specific action, for example Refer, by
document in a period of time
3.6.3.4 Example evaluations on Process Step Level

Name of database table: /OTX/PF08_T_CAT
With this table, you can design evaluations providing information about process
steps, for example an evaluation about the number of documents with a specific,
required process step.

PROFILE_ID, Allows grouping and/or filtering by process step
VERSION, Example: Top n failed process steps at document entry
CHARACTERISTIC,
CAT_ID,
CAT_RUN_STAT = ‘2’,
LOG_POINT = ‘800’
PROFILE_ID, Together with a JOIN operation to the header table /OTX/
VERSION, P<+++>_T_PLHA, the following evaluation is possible:
CHARACTERISTIC, Number of documents with a specific process step failed
CAT_ID,
CAT_RUN_STAT = ‘2’

3.6.3.5 Example evaluations on Rule Level

Name of database table: /OTX/PF08_T_MOD
With this table, you can design evaluations providing information about failed or
bypassed rules.

PROFILE_ID, VERSION, Allows grouping and/or filtering by rule
CHARACTERISTIC, CAT_ID, MOD_ID, Example: Top n bypassed rules at document
MOD_RUN_STAT = ‘5’ entry last month
PROFILE_ID, VERSION, Top n failed rules at document entry last month
CHARACTERISTIC, CAT_ID, MOD_ID,
MOD_RUN_STAT = ‘2’
PROFILE_ID, VERSION, Together with a JOIN operation to the header
CHARACTERISTIC, CAT_ID, MOD_ID, table /OTX/P<+++>_T_PLHA, the following
MOD_RUN_STAT = ‘2’ evaluation is possible: Critical channels regarding
number of failed rules
PROFILE_ID, VERSION, Together with a JOIN operation to the header
CHARACTERISTIC, CAT_ID, MOD_ID, table /OTX/P<+++>_T_PLHA, the following
MOD_RUN_STAT = ‘2’ evaluation is possible: Number of documents
where a specific rule failed
3.6.4 Configuring the Analytics profile

Analytic evaluations can imply different requirements. To enable fast evaluations,
data may need to be prepared and saved on the database. The Analytics
configuration defines these database tables for Analytics purposes and activates or
deactivates the process of writing data to the tables.
To configure Analytics, the following customizing steps are available:
• “Selecting a profile type” on page 44

• “Learning about data levels” on page 44
• “Defining profiles” on page 45
• “Maintaining data tables” on page 45
• “Assigning the Analytics profile to the Process Configuration profile”
on page 48

3.6.4.1 Selecting a profile type

Different scenarios may require the update of database tables for the purpose of
Analytics. One scenario is to prepare and update analytic key figures for business
processes. (Currently this is also the only one.) Each of the scenarios is represented
by a profile type.
The supported scenarios, respectively the profile types, are predefined. Adding new
profile types or deleting existing profile types is not supported.
To select a profile type:

2. Click General Settings > Analytics Configuration > Analytics Configuration.
3. In the Profile Types Overview screen, select a profile type.
Profile Type 1 (Process KPIs) is used for writing Analytics data for business
processes.
3.6.4.2 Learning about data levels

You may need data for the purpose of Analytics for different levels. For example,
there may be key figures on level of the process ledger header or there may be key
figures that are related to single user activities.
To learn about data levels:

3. In the Profile Types Overview screen, mark a profile type, and then double-
click Levels in the Dialog Structure.
4. In the Levels Overview screen, watch the different levels of Analytics data.
The following hierarchy levels for profile type 1 (Process KPIs) are available:
1 - KPIs on Header Level

This level comprises characteristics and key figures on process ledger
header level, for example the total duration of the process or the number of
touches per document.
2 - KPIs on Activity Level
This level comprises characteristics and key figures on user activity level,
for example the processing time from starting to edit a document to leaving
the edit mode by pressing the Save button.
3 - KPIs on History Level
This level comprises characteristics and key figures on history level. A
history entry represents a single user action. This data level allows
evaluations about the different user actions.

3.6.4.3 Defining profiles

A profile within the Analytics Configuration is based on the following questions:
• Which Analytics Profile should be active? This means, it is updating the database
tables for Analytics.
• Which database tables are to be used for the different levels of Analytics data?
Note: With standard delivery, a simple dummy profile DEFAULT is delivered.

This profile is independent from any business scenario data context. You can
use it to start and test the update of example Analytics data.
To define a profile:
3. In the Profile Types Overview screen, mark a profile type, and then double-
click Profiles in the Dialog Structure.
4. In the Profiles Overview screen, define the profile using the following
parameters.
Profile ID
Define the profile with a unique ID.
Active
To set the profile to active, select this check box. If the profile is inactive, no
data is prepared and updated for the purpose of Analytics.
Prof. Desc.
Profile Description. Enter a meaningful profile description.
Analytics Class
Enter the class that is responsible for the preparation of data for Analytic
evaluations. For more information, see “Analytics class” on page 48.
3.6.4.4 Maintaining data tables

In this step, you define the database tables that serve as a base for Analytics
evaluations for a corresponding business scenario implementation.
Before you can maintain the data tables, you must create the business scenario
related data tables. They must fulfill the following mandatory conditions:
Table 3-14: Mandatory key fields for the Analytics header tables
Field Name Data Element

MANDT MANDT


LOGSYS LOGSYS
PROJECT_ID /OTX/PF02_E_PROJECT_ID
PLKEY /OTX/PF02_E_PLKEY
Optional include structure for the Analytics header table:
• /OTX/PF08_S_PLH_ANALYTIC_DATA
Note: The optional include structure comprises several time characteristics to

the process start and process end (field names beginning with START_ or END_).
You can easily include time characteristics for the fiscal year and the fiscal
period in the business scenario context if the company code is available in the
process ledger header table. By appending fields for the company code (field
name: BUKRS), the fiscal year (field names: START_FISCYEAR, END_FISCYEAR),
and the fiscal period (field names: START_FISCPERIOD, END_FISCPERIOD), the
determination of the fiscal year and fiscal period is triggered automatically.
Table 3-15: Mandatory key fields for the Analytics activity tables

MANDT MANDT
LOGSYS LOGSYS
LOG_ENTRY /OTX/PF02_E_LOG_ENTRY
TASK_LINE /OTX/PF02_E_LINE
ACV_LINE /OTX/PF02_E_LOG_ENTRY
Optional include structure for the Analytics activity tables:
• /OTX/PF08_S_ACV_ANALYTIC_DATA

the activity start and activity end (field names beginning with START_ or END_).
You can easily include time characteristics for the fiscal year and the fiscal
period in the business scenario context if the company code is available in the
process ledger header table. By appending fields for the fiscal year (field
names: START_FISCYEAR, END_FISCYEAR), and the fiscal period (field names:
START_FISCPERIOD, END_FISCPERIOD) in the Analytics activity table and by
appending the company code (field name: BUKRS) in the Analytics header table,
the determination of the fiscal year and fiscal period is triggered automatically.

Table 3-16: Mandatory key fields for the Analytics history tables

MANDT MANDT
LOGSYS LOGSYS
LOG_ENTRY /OTX/PF02_E_LOG_ENTRY
TASK_LINE /OTX/PF02_E_LINE
ACV_LINE /OTX/PF02_E_LOG_ENTRY
HIST_LINE /OTX/PF02_E_LINE
Optional include structure for the Analytics history tables:
• /OTX/PF08_S_HIST_ANALYTIC_DATA

the point of time when the action was performed (field names beginning with
START_). You can easily include time characteristics for the fiscal year and the
fiscal period in the business scenario context if the company code is available
in the process ledger header table. By appending fields for the fiscal year (field
name: START_FISCYEAR) and the fiscal period (field name: START_FISCPERIOD)
in the Analytics history table and by appending the company code (field name:
BUKRS) in the Analytics header table, the determination of the fiscal year and
fiscal period is triggered automatically.
To maintain data tables:
1. In the Profiles Overview screen (see “Defining profiles” on page 45), select a
profile, and then double-click Data Tables in the Dialog Structure.
2. In the Data Tables Overview screen, define the data tables using the following
parameters.
Data Hier. Level

Data Hierarchy Level. Enter the hierarchy level to which a data table
belongs. For a list of the available hierarchy levels, see “Learning about data
levels” on page 44.
Table Name
Enter the name of the corresponding Analytics table to be used in the
hierarchy level.

3.6.4.5 Assigning the Analytics profile to the Process Configuration

profile
This step is only required if you want to prepare and update analytic key figures for
business processes.
You have maintained Analytics profiles with profile type 1 (Process KPIs). Assign
these Analytics profiles to the Analytics Profile field in all relevant Process
Configuration profile versions. For more information how to maintain version
settings and especially the Analytics Profile field, see “Maintaining version
settings” on page 178.
3.6.5 Analytics class

For the preparation of data for Analytics evaluations, you must assign each
Analytics class to an Analytics profile. For more information, see “Defining profiles”
on page 45. For every Analytics profile type, a subclass of the basic Analytics class /
OTX/PF08_CL_ANALYTICS_DATA is available. This superclass provides the
ANALYTICS_DATA_INST_CREATE method to create an instance of the profile type
specific subclass. Additionally, it provides some helper methods for general
conversions.
Analytics subclass for Process KPIs

The basic Analytics class for writing data for finished documents is /OTX/PF08_CL_
PROCESS_KPIS, derived from the /OTX/PF08_CL_ANALYTICS_DATA superclass. The /
OTX/PF08_CL_PROCESS_KPIS class prepares general data for analytic evaluations for
business processes and saves the data to the database.
Every business scenario must derive a subclass of the /OTX/PF08_CL_PROCESS_KPIS

class. In this subclass, you may want to adjust the default logic or add your own
logic for additional business scenario specific fields.
Create a subclass of the /OTX/PF08_CL_PROCESS_KPIS class or any of its subclasses.

Redefine the following methods:
HEAD_DEFAULT_TABLE_GET – Usually, you maintain the name of the database

table that contains the process ledger header related data for analytic evaluations in
the configuration, see “Maintaining data tables” on page 45. If no database table is
maintained in the configuration, set the name of a default database table.

PR_TABNAME Returning Default table for Analytics data on header
level
ACV_DEFAULT_TABLE_GET – Usually, you maintain the name of the database

table that contains the activity related data for analytic evaluations in the
configuration, see “Maintaining data tables” on page 45. If no database table is
maintained in the configuration, set the name of a default database table.


PR_TABNAME Returning Default table for Analytics data on activity
level
HIST_DEFAULT_TABLE_GET – Usually, you maintain the name of the database

table containing the history related data for analytic evaluations in the configuration,
see “Maintaining data tables” on page 45. If no database table is maintained in the
configuration, set the name of a default database table.

PR_TABNAME Returning Default table for Analytics data on history
level
HEAD_DATA_DETERMINE (optional) – You may have added custom or solution

specific fields in the database table that contains the process ledger header related
data for analytic evaluations. In this case, redefine this method. With calling method
head_data_determine of the superclass in the beginning of the code, you can
ensure that the standard fields are populated as well. You can also change the
content of the standard fields in your program code.

PIS_HEAD Importing Process ledger header data to be
used but not changed
PIH_ITEM Importing Process ledger item data to be used
but not changed
PES_HEAD_ANALYTICS Exporting Header related Analytics data to be
updated
ACV_DATA_DETERMINE (optional) – You may have added custom or solution

specific fields in the database table that contains the activity related data for analytic
evaluations. In this case, redefine this method. With calling method acv_data_
determine of the superclass in the beginning of the code, you can ensure that the
standard fields are populated as well. You can also change the content of the
standard fields in your program code.

PIS_ACV Importing Activity data to be used but not
changed
PES_ACV_ANALYTICS Exporting Activity related Analytics data to be
updated
HIST_DATA_DETERMINE (optional) – You may have added custom or solution

specific fields in the database table that contains the history related data for analytic
evaluations. In this case, redefine this method. With calling method hist_data_

determine of the superclass in the beginning of the code, you can ensure that the
standard fields are populated as well. You can also change the content of the
standard fields in your program code.

PIS_HIST Importing History data to be used but not
changed
PES_HIST_ANALYTICS Exporting History related Analytics data to be
updated

Chapter 4
Inbound Configuration
This chapter provides details about the Inbound Configuration. It is part of the
Foundation.
With Inbound Configuration, you define how to import or capture incoming

documents and then dispatch them, for example to a subsequent workflow or to
archiving.
Inbound Configuration allows you to configure the classification scenario . The

classification scenario registers documents for further processing according to their
business context, for example Sales Order or Delivery Note. You also configure how
the documents are processed coming from different channels.
Each document runs through defined process steps, which are indicated by the
inbound handler process. Each process step comprises several service modules.
These service modules are integrated components of Inbound that offer the
functionality.
For Inbound Configuration, you define:
• Channels that define the way how a document is imported into the system. This
can be, for example, paper through scan, fax, email, or IDoc. To configure a
channel, you need the registration type.
• Scenario classifications that identify the different types of business scenarios for
incoming documents. They also define the corresponding target application and
target system that are triggered at the end of the incoming document process.

Chapter 4 Inbound Configuration
• Registration types that define the scenario which is used to import documents.
The import can happen, for example, by email, IDoc or Document Pipeline.
Depending on the registration type, standard SAP customizing is needed, for
example, for ArchiveLink or SMTP.
• Document handlers and service modules that route the incoming document
through the incoming documents process. You must customize them to
sequentially process the document, based on the respective document status.
• Business Center Capture that automates the capture of paper documents by

using OCR to extract data. Business Center Capture uses SAP ERP as backend to
store and retrieve image information.
The Inbound Configuration customizing structure in the /OTX/PF00_IMG transaction

contains all customizing screens that are relevant for handling incoming documents.
Some authorizations are needed to monitor the Inbound Configuration. For more
information, see Example 8-1, “Authorizations necessary to monitor the Inbound
Configuration” on page 266.
4.1 Customizing basic settings for Inbound

Configuration
You configure basic parameters for Inbound Configuration that apply to all
incoming document scenarios.
To customize basic settings:
1. Run the /OTX/PF00_IMG transaction.
2. Click OpenText Business Center for SAP Solutions > Inbound Configuration
> Basic Settings.
3. In the Basic Settings Overview screen, configure settings, using the following
parameters:
ArchiveID for XML

This parameter is mandatory. It is only relevant if Business Center Capture
is used for document extraction. Enter the Content Repository for XML
documents. The repository is used to store and archive the extraction result
of the Business Center Capture.
Capture Cancel Code

Status code delivered by Business Center Capture: Extraction/Validation is
canceled.
Capture Error Code

in error.

4.1. Customizing basic settings for Inbound Configuration
Capture Reject Code

rejected.
Capture Success Code
successful.
Default Language
Enter the default language for error messages and fallback.
Delay for Extraction (Minutes)
This parameter is only relevant if Business Center Capture is used for
document extraction.
Enter the delay before sending the document to extraction in minutes.
Use this parameter if there are frequent situations when a document is
selected for extraction but is not yet accessible from the archive.
Exit Extraction Sorting
Enter the exit function module to sort documents for extraction. By default,
sorting is done by registration key. Sorting works according to the available
registration data. After extraction, sorting can also work by the extracted
data. Use template function /OTX/PF01_UTIL_EXIT_EX_SORT.
Exit Validation Sorting
Enter the exit function module to sort documents for validation. By default,
sorting is done by registration key. Sorting works according to the available
registration data. After extraction, sorting can also work by the extracted
data. Use template function /OTX/PF01_UTIL_EXIT_VA_SORT.
Retry Counter Extraction
Enter the maximum allowed number of retries for extraction. When this
number is reached, the document status is set to error Maximum number of
retries reached.
Retry Counter Validation

Enter the maximum allowed number of retries for validation. When this
number is reached, the document status is set to error Maximum number of
retries reached.
Look-up Download Entries in Pack

Enter the number of packs that can be downloaded from the Business
Center Capture server to get data from staging tables. The download is
triggered from the Business Center Capture hotspot by calling the /OTX/
PF01_IF_LOOKUP_DOWNLOAD function. If no value is maintained, a default
pack size of 10,000 is used. For more information, see “To create a look-up:“
on page 156.

Look-up Hits Validation

Enter the number of entries within search in validation.
Enter the default number of entries that can be shown when the user
searches online in the Validation Cient for entries in staging tables. The
look-up is triggered from Business Center Capture Validation Cient by
calling the /OTX/PF01_IF_LOOKUP_VAL function. If no value is maintained
and also no maxhits are provided in the Validation Cient, a default of a
1,000 maximum hits is used. For more information, see “To create a look-up:
“ on page 156.
Auto-Forward Extraction Retry
The setting forwards the document automatically to the target application if
the extraction retry counter is reached.
Set this value to X.
The document is not set to error status within inbound processing.
Auto-Forward Validation Retry
Automatically forwards the document to the target application when the
extraction retry counter is reached.
Set the value to X.
Auto-Forward no Image for Extraction
Automatically forwards the document to the target application, if no image
for extraction exists.
Set the value to X.
Limit for Counting Documents in Validation
Enter the maximum number of documents to be retrieved in the Validation
Cient. The limit provides a performance optimization within the Validation
Cient.
HTTP Connection for Signature Validation Service (AIC)
Intended for future use.
Rendition Server ID
Name of the rendition server which is used in the document handler
process to render documents. For more information, see “Rendition
management” on page 95. The rendition server is configured
within Archiving and Document Access for SAP Solutions.
Rendition Server Profile
Name of the profile to render documents. For more information, see
“Rendition management” on page 95. The rendition server profile (for
example examplePDFA-2b default profile ) is configured within Archiving
and Document Access for SAP Solutions.

4.2. Configuring channels
Reserve for Validation Time Limit (Seconds)

This parameter is only relevant if the Capture Validation Workcenter is
used.
Enter the time limit (in seconds) until a document is reserved for validation
in the Capture Validation Workcenter.
4.2 Configuring channels

Channels define the way how a document is imported into the system. This can be,
for example, paper through scan, fax, email, or IDoc. The channel is assigned to a
specific document registration type. For more information, see “Customizing
registration types” on page 62. You can use the channel in solutions to identify
how documents have been imported into the system.
To configure channels:
> Channels.
3. In the Channels Overview screen, configure channels using the following

parameters:
Channel
Technical ID of the channel
Registration Type
Select the type of the registration used for this channel. According to the
registration type, the channel ID is available in the registration
configuration. The following registration types are available: Early
Archiving, Idoc, Mail, Upload, Custom. For more information, see
“Customizing registration types” on page 62.
In the current version, the Registration Type is only used to control the F4-
Help in the registration configuration. It has no further technical impact for
any other component or processing logic.
Description
Enter a description of the channel.

4.3 Creating scenario classifications

Scenario classifications are used to identify the different types of business scenarios,
for example Sales Order or Delivery Note, for incoming documents. Scenario
classification also defines the corresponding target application and target system.
The classification is assigned to a specific registration type. For more information,
see “Customizing registration types” on page 62.
To create a scenario classification:
> Scenario Classification.
3. In the Scenario Classification Overview screen, configure the scenario

classification, using the following parameters:
Classification Profile
Technical ID of the classified business scenario
Description
Enter a description of the classification.
Application
Select the target application, which is triggered at the end of the Incoming
Document Framework process for the registered document. The following
target applications are available:
Trigger Process Foundation

Start a business process in Process Foundation (see “Process
Foundation“ on page 161).
Trigger Vendor Invoice Management

Start an invoice process in VIM.
Trigger Custom Processing

Start a custom business application. The Exit Application function
module will be triggered.
Profile ID (PF)
Enter the profile ID of the corresponding Process Foundation (PF)
configuration used for Process Foundation trigger. For more information,
see “Process Foundation profile” on page 172.
Exit Application
Enter the exit function to start any business application used for the Custom
Processing trigger. See template function /OTX/PF01_UTIL_EXIT_APPL.
Logical System
Enter the target system where the business application is started.

4.3. Creating scenario classifications
Exit System Determination

Optional: Enter the function that is run to determine the target system. Use
the /OTX/PF01_UTIL_EXIT_TARGET_SYS template.
4.3.1 Assigning document types to classifications

To avoid creating different channels for different scenarios, you must configure
additional document types for scenario classifications. This also allows defining
which document types are classified and which ones are not.
This configuration is only necessary in connection with document classification

scenarios. For more information, see “Document classification“ on page 471,
especially “Processing impacts” on page 474.
To assign document types to classifications:
> Scenario Classification.
3. In the Scenario Classification Overview screen, mark a scenario classification,

and then double-click Classification Document Types in the Dialog Structure.
4. In the Classification Document Types Overview screen, assign document

types to the classification, using the following parameters.
Classification
Selected classification profile
Doc. Type
Enter document types that you want to assign to the classification.
Category
Select the category of the document type from the list.
The following categories are available:
• Classified
• Unclassified

4.4 Customizing incoming documents through the

document handler
The document handler manages the registration types and the process flow of
incoming documents. Thereby, the document handler considers the corresponding
status handling.
Basis for the document handler is a status queueing engine. You must plan the /
OTX/PF01_P_IDF_TRIGGER report as a periodic job to trigger the service modules
accordingly. For more information, see OpenText Vendor Invoice Management for SAP
Solutions - Administration Guide (VIM200400-AGD).
Status When a service module finishes its step, it assigns a status to the document. This
status then triggers the next step in the processing sequence.
The status helps, for example, to identify documents that are ready for validation or
need to get extracted.
Important
• The delivered status must not be changed. For custom service modules, use
a new status in the corresponding customer namespace and number range.
• Do not change the delivered customizing entries of BC Sets but create new
profiles and new settings.
• New configuration must have the prefix Z_ or 9xx according to the data
element.
4.4.1 Creating a document handler process

A service module identifies a processing step in the document handler. The
processing steps are assigned to a document handler, which represents the
document flow in Inbound Configuration.
Important
At the last step of the handler process, the target business application is
triggered. The status is set to 99 (Business application / Process started).
After that, the handler is set to the handler end status.

4.4. Customizing incoming documents through the document handler
4.4.1.1 Configuring the document handler status

The document handler status defines the status of the document during the Inbound
Configuration process. The status is shown on the History tab of the Detail Pane in
Business Center Workplace. With the BC set of the Inbound Configuration, status
entries with values between 1 and 100 are delivered.
Important
Do not change the delivered status! If you need to configure an own status, use
a number starting with 900. For more information, see “Customizing”
on page 17.
To configure the document handler status:
> Document Handler > Status.
3. In the Status Overview screen, configure statuses, using the following

parameters:
Status
Enter a unique status number.
Description
Enter a meaningful description.
4.4.1.2 Creating a document handler

The document handler describes the process flow for each incoming document. The
document handler processes different service modules according to their
registration type. For paper-based documents, there is a document handler for
manual indexing and a document handler for processing documents in Business
Center Capture and Information Extraction Service.
To create a document handler:
> Document Handler > Modules.
3. In the Handler Overview screen, configure the document handler, using the
Handler
Technical ID of the document handler
Description
Enter the description of the document handler.

Start Handle
Enter the start status of the document handler process.
The start status identifies the status when the document handler is triggered
and processed.
End Handle
Enter the end status of the document handler process.
The end status identifies the status when the whole document handler
process is finished.
Handle Class
Optional: Enter an exit class that implements the /OTX/PF01_IF_HANDLER
interface. The EXIT_HANDLER_END method allows you to trigger own logic at
the end of the handler processing after the target application is started or in
error case.
4.4.1.3 Configuring modules for the required processing steps

Modules are the processing steps of the document handler. A module is triggered in
the step sequence. This happens when the end status of the previous module has
been set. This also happens when the corresponding start status is set within the
status engine or outside.
To configure a module:
> Document Handler > Modules.
3. In the Handler Overview screen, mark a row, and then double-click Modules in
the Dialog Structure.
4. In the Modules Overview screen, configure the modules, using the following
parameters.
Module ID
Technical ID of the module
Sequence
Define the sequence how the modules are processed.
Description
Enter the description of the module.
Active
Select this check box to activate the module.
Module Class
Enter the implementation class of the processing logic. Modules must
implement the /OTX/PF01_IF_MODULE interface.

There are possible methods for a custom implementation in the /OTX/PF01_

IF_MODULE interface. For a custom implementation, use a redefinition of
the /OTX/PF01_CL_MODULE_HANDLER class:
PROCESS_MODULE
This method provides logic to process the service module.
The method is called in /OTX/PF01_CL_IDF_TRIGGER within document
handler program /OTX/PF01_P_IDF_TRIGGER
Transformation
Optional: Enter an XSLT transformation program to process an XML
transformation within the module class.
End Status
Enter the status of the module that is set at the end of a module.
The end status must be unique. Do not use status 99. It is reserved for the
business application start.
Start Stat
Enter the start status. You can configure it for modules that must be
triggered only when the start status is set. It is, for example, used in the
communication with Business Center Capture to route documents to the
correct steps, or when steps must be skipped. For example, validation can
be skipped in some cases.
Error Stat
Enter the error status, which is set in error case.
Time limit
Enter the maximum time limit (in seconds) for a module to finish its
processing. If the time limit is reached, the module is set into error status.
The time limit is only taken into account if the document handler is globally
in processing status. Also the No.ofRetry setting is not relevant because the
module is set into error status immediately after the time is reached.
A module waiting for the extraction result of a Business Center Capture
integration should have a time limit of 7200. A module waiting for the
validation result of a Business Center Capture integration should have a
time limit of 3600.
No.ofRetry
Enter the number of retry attempts for a service module in error case. When
the number is reached, the processing handler or document flow is set into
error status.

4.4.2 Customizing registration types

Document registration is the initial touch-point of a document with SAP ERP and
the entry point for Inbound Configuration. Document registration in Inbound
Configuration can be done in different ways. The following registration types are
available:
• Early Archiving
• Inbound IDoc
• Incoming Mail
• Pipeline
• Custom / Others
If you need to configure a custom registration within a completely new incoming
document scenario, you must implement the /OTX/PF01_IF_REGISTRATION
interface. You can use the custom registration type to configure and access
specific settings.
Registration There are possible methods for a custom implementation in the /OTX/PF01_IF_
Class REGISTRATION interface:
REGISTER
This method registers a document in the /OTX/PF01_T_1REG table and sets the
status in the /OTX/PF01_T_STA table.
This method is called in the available registration classes:
• Early Archiving: /OTX/PF01_CL_REGISTER_OAWD
• Inbound IDoc: /OTX/PF01_CL_REGISTER_IDOC
• Incoming Mail/OTX/PF01_CL_REGISTER_MAIL
• Document Pipeline: /OTX/PF01_CL_REGISTER_PIPELINE
All incoming documents are registered within the /OTX/PF01_T_1REG table. The
registration uses a SAP number range object.
To create a number range interval:
1. Run the SNUM transaction for number range object /OTX/PF01.
Note: This object is not delivered in the BC set.
2. Maintain the number range 01 with the range 1 to 999999999999.

4.4.2.1 Customizing the early archiving registration type

The early archiving registration type describes a process in which a scanned
document is archived before the details of the underlying business transaction are
available in the SAP ERP system.
Document registration with early archiving is processed in the standard

ArchiveLink interface. This section describes the document registration, and also the
mandatory settings for the ArchiveLink configuration.
The early archiving registration type is also used when documents are uploaded and
archived with the Fiori App Store Documents, which is available in the /OTBCWUI/
PF07_BC_FOUNDATION tile catalog. For more information, see “Integrating Fiori Task
App into Fiori Launchpad” on page 449.
Note: You can use any scan client and content repository that are certified by
SAP, for example OpenText Imaging Enterprise Scan and OpenText Archive
Center.
4.4.2.1.1 Maintaining general ArchiveLink settings
Incoming paper documents are scanned and archived, using the early archiving
registration type.
In ArchiveLink, every document type is assigned to a workflow. The workflow is

started when a document with the given ArchiveLink document type is uploaded in
the OAWD transaction.
You must perform the following configuration when the content repository (Archive
Center) is installed and the basic ArchiveLink settings are completed. Depending on
your requirements, the number and attributes of the ArchiveLink settings might be
different.
Notes
• For further details about ArchiveLink, see the SAP documentation.

• For the early archiving registration type, use an ArchiveLink document type
that is assigned to the Inbound Configuration workflow task WS00297300
and object type /OTX/PF01R.

4.4.2.1.2 Creating a Content Repository ID
To determine where the scanned document is archived, you must maintain the
Content Repository ID. This is standard ArchiveLink customizing. If you already
have a working ArchiveLink customizing, you can skip this section.
To create a Content Repository ID:
1. Run the OAC0 transaction.
2. In the Change Content Repositories Overview screen, click Create .
3. Enter the following parameters:
Note: For more details on the parameters, see Section 7.2 “Maintaining an
HTTP content repository in the SAP system” in OpenText Archiving and
Document Access for SAP Solutions - Scenario Guide (ER-CCS).
• Content Rep.: Content Repository ID

• Description
• DocArea (Document Area): ArchiveLink
• Storage type: HTTP content server
• Protocol: This setting defines the file source for archiving and image
displaying media.
• Version no.: for example, 0046
• HTTP srvr:port (HTTP server and port)
• HTTP script: archive
• Transfer drctry (Transfer directory)
4. Click .
4.4.2.1.3 Creating the presetting folder
A presetting folder groups document types that are related by workplace or by

application. Grouping document types together in a presetting folder provides a
more effective overview of document types on the initial screen of the storage
process Store Documents in the OAWD transaction.
For each document type, you determine the agents that are responsible for the work
item. You also choose which storage scenario is used. The following storage
scenarios are available for Early Archiving:
• Storing for subsequent entry

• Storing for subsequent assignment
• Store and enter
• Store and assign

The scenario “Storing for subsequent entry”, for example, consists of assigning the
document type and processing the work item.
To create the presetting folder:
1. Run the OAWS transaction.
2. In the Default setting: Overview screen, click New Entries in the application
tool bar.
3. Create the new presetting folder using the following parameters:
Pr
Enter the presetting folder name.
Long text
Enter a description of the new folder.
4. Click .
To add a document type to the presetting folder:
Note: If you store the Archive Document Type in the presetting folder during
its creation, you do not have to perform this action. Nevertheless, if you need
to reassign any Archive Document Type to another folder or you need to
assign Archive Document Types to the presetting folder, you can perform this
action. Assigning all relevant Archive Document Types to the presetting folder
is useful for identifying the Archive Document Types easily. For more
information, see “Creating an ArchiveLink document type” on page 66.
Tip: With the Business Center Foundation BC set, the presetting folder /OTX -
Business Center Inbound is already available.
1. Run the OAWS transaction.
2. Select the presetting folder, and then double-click Entries.
3. In the Entries Overview screen, click New Entries in the application tool bar.
4. Add the Doc. type, for example /OTX/SO4, and select the appropriate storage
scenario check box, for example Storing for subsequent entry.
Note: Optionally, you can select an Object Type in the OT column and an
Agent ID for the document type.
5. Click to save your changes.

4.4.2.1.4 Creating an ArchiveLink document type
In this step, you create an ArchiveLink document type, for example /OTX/SO4, and
store it in the presetting folder created before. For more information, see “Creating
the presetting folder” on page 64. Then, you assign the ArchiveLink document type
to Early Archiving (Storing for subsequent entry).
After the ArchiveLink document type is maintained, every incoming document that
is associated with the given document type will be stored in a predefined archive
and a customized workflow will start afterwards.
To create an ArchiveLink document type:
1. To start the Document Type Customizing Wizard, run the OAD5 transaction.
On the Start screen, click Continue.
2. Document type
Doc.type
Enter a name for the new document type. For example, use archive
document type /OTX/SO4 or another document type for your namespace.
Name
Enter a description.
Click Continue in the upcoming screens until you reach the Workflow
document type screen.
3. Workflow document type

Select the Workflow document type check box, and then click Continue.
4. Document class
Enter Doc. class PDF ,and then click Continue.

5. Object, method and tasks

Enter the following information:
Obj. type
/OTX/PF01R
Entry
Task
WS00297300
Click Continue.
6. In the Workflow Parameter screen, click Continue.

7. Storage system and link table

Click Continue.

8. Selection from available presettings

Select the ID of the delivered presetting folder (available in the Business Center
Foundation BC set), and then click Continue.
9. In the Create new presettings screen, click Continue.
10. Details of presettings
Select the Storing for subsequent entry check box, and then click Continue.
11. End
To save the archive document type /OTX/SO4, click Complete and confirm the
changes.
4.4.2.1.5 Linking an ArchiveLink document type to a registration object
Every incoming document is associated with an ArchiveLink document type and a

business object.
To know where to store the incoming document , you must maintain the links, as
described in this section.
To link the ArchiveLink document type to the registration object:
1. Run the OAC3 transaction.

2. In the Links for Content Repositories Overview screen, click New Entries.

3. Enter the following parameters:
Object Type
/OTX/PF01REG
Document type
Enter /OTX/SO4
Link Status
Enter X
Storage system
Enter the Content Repository ID. For more information, see “Creating a
Content Repository ID” on page 64.
Link
Enter TOA01
4. Click .
You can also link the document to the relevant SAP target business object. To do
this, continue as described in this section for any SAP business object that you want
to link to the document. For details about the related settings and the supported
business objects, see the description in the related solution guides (for example Sales
Order with the related Business Objects for Sales Orders).

4.4.2.1.6 Customizing the ArchiveLink registration
For the registration of documents, the ArchiveLink document type is linked to the
document handler, to a channel, and to the classification profile.
To customize the ArchiveLink registration:
> Document Handler > Registration > Early Archiving.
3. In the Registration - Early Archiving Overview screen, configure the
registration, using the following parameters.
Document Type
ArchiveLink document type used for the registration
Channel
Enter the Channel ID used for this registration type. For more information,
see “Configuring channels” on page 55.
Handler
Enter the Handler ID that represents the processing steps of the service
modules for this document. For more information, see “Customizing
incoming documents through the document handler” on page 58.
Classify
Enter the Classification ID of the incoming document. For more
information, see “Creating scenario classifications” on page 56.
Pre Exit Registration
Optional: Enter the function that is executed before the document is
registered in Inbound Configuration. Use template /OTX/PF01_UTIL_EXIT_
REG_BEFORE.
Past Exit Registration

Optional: Enter the function that is executed after the document is
registered in Inbound Configuration. Use template /OTX/PF01_UTIL_EXIT_
REG_AFTER.
Register synchron
Activate register synchron in order to trigger the inbound handler for the
registered document synchronously

4.4.2.2 Customizing the Inbound IDoc registration type

The Electronic Data Interchange (EDI) scenario is based on the standard SAP
document format Intermediate Document (IDoc). IDocs allow different application
systems to be linked through a message-based interface. The following list shows
some examples of how you can benefit from using IDocs.
• Business documents are exchanged in a structured way in order to process them

automatically.
• The various degrees of structural complexity as displayed by different
application systems can be reduced to a structure that is as simple as possible.
Example: The structure of an SAP application document and the structure of the
corresponding EDI message under the UN/EDIFACT standard
The function module /OTX/PF01_UTIL_IDOC_INPUT for inbound documents creates

a registration entry from incoming IDocs. To enable this, the following configuration
steps are necessary. The configuration describes a possible incoming order
configuration. Depending on your requirements, the number and attributes of the
inbound IDoc settings might be different.
Note: For further details about inbound IDoc processing, see the SAP
documentation.
4.4.2.2.1 Defining settings for the inbound function module
In this step, you choose the input type for the IDocs.
To define settings for the inbound function module:
1. Run the BD51 transaction.
2. In the Characteristics of Inbound Function Modules view, click New Entries.
3. Define the inbound function module, using the following parameters:
Function module (inbound)

Enter /OTX/PF01_UTIL_IDOC_INPUT
Input type
Enter 0 (for Mass processing).
Dialog allowed
If you want to process IDocs in dialog mode, select this check box. With
baseline implementation, the check box is cleared.
4. Click Save .

4.4.2.2.2 Linking the inbound function module to IDoc type and message type
In this step, you establish the link between the inbound function module, the basic
IDoc type, and the message type.
To link the inbound function module to IDoc type and message type:
1. Run the WE57 transaction.

2. In the IDoc: Assignment of FM to Log. Message and IDoc Type view, click
Change .
3. Click New Entries.
4. Configure the assignment using the following parameters:
Function module
/OTX/PF01_UTIL_IDOC_INPUT
Function type
Select Function Module.
Basic type
Enter the basic type, for example ORDERS01.
Message Type
Enter the message type, for example Orders.
Direction
Select Inbound.
Description
5. Click Save .

4.4.2.2.3 Creating a new process code
In this step, you create a new process code and assign the inbound function module
to this process code.
The process code is a logical name for the processing function module. The process
code is used to uniquely determine a function module that processes the received
IDoc data and converts an IDoc to an SAP document.
To create a new process code:
2. In the Inbound process code view, click Change .
4. Define the new process code using the following parameters:
Process code
Enter the process code name.
Note: You can choose a name for the process code that suits your
needs.

Description
Identification
Enter the inbound function module /OTX/PF01_UTIL_IDOC_INPUT.
Option ALE
Click Processing with ALE service.
Processing type
Click Processing by function module.
5. Click .
6. Double-click Logical message in the Dialog Structure.
7. Assign the new process code to the logical message using the following
parameters:
Process code
Process code name as defined in Step 4.
Message type
Enter the message type, for example Orders.
8. Click Save .

4.4.2.2.4 Configuring the partner profile
When data is exchanged between partners, it is important that sender and receiver
define the exact syntax and semantics of the data to be exchanged beforehand. The
partner profile defines the type of data and communication paths of that data
exchange.
In this step, you assign the new process code to the IDoc partner profile. You must
specify partner and partner type. You must also specify whether you define a profile
for inbound or outbound data exchange. You can use an existing partner profile. The
partner type must be Logical system (LS).
Tip: If you want to create a new partner profile, you must first create a new
logical system. See the SAP documentation for details.
To configure the partner profile:

2. Select the partner profile under Partner Profiles > Partner Type LS.
3. Below the Inbound parmtrs. panel, click Add .
4. Configure the inbound parameters.
Partner No.
ID of the partner profile,

Partn. Type
Partner Type: Enter LS for logical system.
Message type
Enter the message type, for example ORDERS.
5. On the Inbound options tab, enter the Process code that you created in
“Creating a new process code” on page 74.
6. Click Save .
4.4.2.2.5 Linking inbound IDoc with document handler, channel, and classification
For the registration of documents, you link the IDoc parameters with the handler
process, a channel, and the classification profile. You also process the relevant field
mapping of the IDoc segments.
To configure the inbound IDoc registration:

> Document Handler > Registration > Inbound IDoc.
3. In the Registration IDoc Details screen, configure the registration, using the
Partner Number, Partner Type, Partner Role, Message Type, Message Code,
Message Function, Test
For these parameters, see the SAP documentation: IDoc Interface /
Electronic Data Interchange (BC-SRV-EDI).
Channel
Enter the Channel ID used for this registration type. For more information,
see “Configuring channels” on page 55.
Module Handler
Enter the Handler ID that represents the processing steps of the service
Classification
Document Type
You can configure a document type that is used to create and archive a
readable PDF out of the IDoc. To create and archive a PDF, you must
implement the Pre Exit Registration.
Document Type Attachment
If the IDoc also delivers an attachment (for example embedded in DOC
segments), you can configure the corresponding ArchiveLink document

type. To archive an attachment, you must implement the Pre Exit

Registration. To support different mime types, leave the document class
empty for this ArchiveLink document type in the OAC2 transaction.

Enter a function that is executed before the document is registered in
Inbound Configuration. Use template /OTX/PF01_UTIL_EXIT_REG_BEFORE.
You can use this function to configure the document type that is used to
create and archive a readable PDF out of the IDoc.

Enter a function that is executed after the document is registered in Inbound
Configuration. Use template /OTX/PF01_UTIL_EXIT_REG_AFTER.
Register synchron
4.4.2.2.6 Mapping IDoc fields to target fields
Each IDoc field can be mapped to a target field. The mapping result is stored in the /
OTX/PF01_T_1EXT table, which collects all extracted data intermediately.
The final mapping of the fields to the target business application is done within the
Data Model Configuration. For more information, see “Data model configuration”
on page 163.
Note: To handle the scenario for the processing of IDOC with an invoice type
that is set to INVO, CRME, SUBC, SUBD, do the following:
• Change the configuration for the field name BSART:

E1EDK01 segment, INVOIC02 object name)
• Use the document field name VORGANG instead of CREDIT_MEMO

• Use the Function Module value /OTX/PS03_EXIT_IDOC_CR_MEMO
These changes are applicable for the INVOIC message type.
To configure the IDoc mapping:
1. Run the /n/OTX/PF00_IMG transaction
> Document Handler > Registration > Inbound IDoc.
3. In the Registration IDoc Details screen, double-click IDoc Mapping in the

Dialog Structure. In the IDoc Mapping Overview screen, double-click an entry.
4. In the IDoc Mapping Details screen, configure the IDoc mapping, using the

Object Name
Development object name: the IDoc type ORDERS01
Segment Type
Segment type in IDoc type
Field Name
Segment field
IDoc Qualifier
Qualifier of the segment
Qualifier Value
Value of the segment qualifier
Field Type
Select either Header or Item type.
External Field Name
Enter the Intermediate field name.
Field Mapping Type
Select one of the following mapping types from the list:
• Segment Field (from IDoc)

• Constant (fixed value)
• System variable
• Function Module
Value
If you have selected Constant (fixed value), System variable, or
Function Module as the field mapping type, enter the corresponding value.
If you have selected Function Module, you can use the /OTX/PF01_UTIL_
EXIT_IDOC_MAP function module as a template.

4.4.2.2.7 Customizing the IDoc hierarchy item
For the item fields, an assignment to an intermediate external table name is

necessary. This table is mapped to the final target business ledger item table. The
mapping is done within the Data Model Configuration. For more information, see
“Data model configuration” on page 163.
To customize the IDoc hierarchy item:
1. In the IDoc Mapping Details screen, double-click IDoc Hierarchy Item in the
Dialog Structure.
2. In the IDoc Hierarchy Item Details screen, customize the IDoc hierarchy item,
using the following parameters.
Object Name
Development object name: the IDoc type, for example ORDERS01
Segment Type
Segment type in IDoc type which represents an item segment (only one item
segment supported)
External Field Name
Enter the intermediate table field name.
4.4.2.3 Customizing the incoming email registration type

SAP NetWeaver Application Server ABAP supports the Simple Mail Transfer
Protocol (SMTP). This enables email exchange between the SAP ERP system and an
SMTP email server, without having to use additional external components.
All information of the incoming email object is logged. This means, all incoming
email data received through the SMTP interface can be viewed in SAPconnect. Later
on, the information can be used, for example, for reporting.
Note: The product standard does not support sending emails back to the
sender or forwarding messages to SAP Business Workplace.
Prerequisites
• The email server must be SMTP-compatible.

• The customized address space for the default domain must match the DNS
address on the external email server.
To enable the incoming email registration, the following customization steps are
necessary.

Note: For further details about incoming SMTP email processing, see the SAP
documentation.
4.4.2.3.1 Checking the SMTP service
1. To check the customizing of the SMTP service, run the SMICM transaction.
2. On the Goto menu, click Services.

The SMTP service is active on port 25.
3. If the port is not set to 25, select the SMTP service. In the Service menu, click
Change.
4. Set the port value to 25 and save the changes.
4.4.2.3.2 Configuring the profile parameters
If you want to use the SMTP function, you must adjust the system profile of the SAP
ERP system.
To configure profile parameters:
1. To access the Edit Profiles screen, run the RZ10 transaction.

2. Choose the instance profile, click Extended maintenance, and then click
Change.
3. Configure the following new profile parameters as a Name = Value pair.
The placeholder <*> stands for the sequence number (starting at zero) of
frequently occurring parameters.
icm/server_port_<*> = PROT=SMTP,PORT=25
This parameter opens a TCP/IP port for receiving emails through the SMTP
plug-in.
Note: After adding this parameter, the ICM service is set
automatically to port 25 when the application server is restarted.
is/SMTP/virt_host_<*> = <host>:<port>, <port>,...;
This parameter defines a virtual email host for receiving emails. If all
incoming emails are received and processed by one single client of the SAP
ERP system, this parameter is not required.
4.4.2.3.3 Creating a service user
You must create a service user for processing incoming emails in every SAP ERP
system client in which you want to receive emails. Every user that receives emails in
an SAP ERP system requires an Internet email address. This is also used as a sender
address.
To create a service user:
1. Run the SU01 transaction.

2. Create a user with type Service and assign the profile S_A.SCON to this user.
3. On the Address tab, under E-Mail, enter the Internet email address for the user.

4.4.2.3.4 Assigning the SAP ERP system client to an SMTP server
Every SAP ERP system client that receives and processes incoming emails must have
an SMTP server. One SMTP server (called SAPconnect) has already been created in
the SICF transaction and is delivered with every SAP ERP system.
To assign the SAP ERP system client to an SMTP server:
1. Run the SICF transaction and open the Virtual Host SAPCONNECT.
2. Select SAPconnect. To display the Create/Change a Virtual Host screen, click

Change .
3. Configure the following settings on the SMTP servers:
Host Data
Enter the sequence number of the is/SMTP/virt_host_<*> parameter from
the profile. For more information, see “Configuring the profile parameters”
on page 81. If you have only created one client and therefore have not
specified this parameter type, enter 0.
Logon Data
Enter the logon data of the system user that you created for the incoming
emails.
Handler List
At position 1, enter CL_SMTP_EXT_SAPCONNECT.
4. For each additional client, create another SMTP server.
Note: You must activate each SMTP server (Service/Virt. Host > Activate)
after creating or changing it. Inactive servers appear dimmed.

4.4.2.3.5 Administering SAPconnect
You must configure SAPconnect settings for every client that is used for send
processes.
To administer SAPconnect:
1. Run the SCOT transaction.
2. On the Settings menu, click Default Domain.
3. Default Domain
Define the domain of the SAP ERP system client.
This action has the following consequences:
• The SMTP plug-in logs on to the email server using this domain as the ID.
• The message ID of the outbound emails is assembled with this domain.
• An SAP user might not have an Internet email address. If such a user sends
an email, a sender address consisting of the SAP user name and this domain
is generated.
Each client has an SMTP node. This node is created by the SAP ERP system and
cannot be deleted.
4. Nodes
Enter the specific customizing data like output format for SAP documents and
other types of documents. See details in the SAPconnect documentation.

5. Inbound Processing
You may want incoming emails that have a particular address or particular
content to automatically start a program that processes these emails. In this
case, configure the following on the menu: Settings > Inbound Processing.
6. Add new entries using the following parameters:
Communication Type
Select Internet Mail.
Recipient Address
Enter email address.
Document Class
Enter the * wildcard.
Exit Name
Enter the default framework class name /OTX/PF01_CL_REGISTER_MAIL.
Call Sequence
Enter the call sequence according to your requirements.
7. Save your settings.
For a more detailed description of how to enable the Simple Mail Transfer Protocol
Service in SAP ERP, see the SAP Help.
4.4.2.3.6 Customizing inbound email registration
For the registration of documents, the email address is assigned to the handler
process, a channel, and the classification profile.
To attach an email as PDF document, you must fill the following attributes:
• recipient mail,
• channel,
• handler,
• classify,
• document type,
• document type mail,

• attach body = X,
• render to PDF = X
• preregistration exit.
The conversion of HTML email document to PDF covers a limited range of special
characters and formatting. Depending on functionality of standard SAP method
cl_crm_email_utility (convert_html_to_plain_text). The PDF document can look
different to the HTML or TXT document
To customize the inbound email registration:

> Document Handler > Registration > Incoming Mail.
3. In the Registration - Mail Overview screen, customize the inbound email
registration, using the following parameters.
Recipient Mail
Email address that receives the email. This address is configured within the
SCOT transaction. For more information, see “Administering SAPconnect”
on page 84.
Channel
Enter the ID of the channel that is used for this registration type. For more
information, see “Configuring channels” on page 55.
Handler
Enter the ID of the document handler that represents the processing steps of
the service modules for this document. For more information, see
“Customizing incoming documents through the document handler”
on page 58.
Classify
Document Type
You can configure a document type that is used to archive the leading
application document, for example order or delivery note. To archive any
document, you must implement the Pre Exit Registration.
Document Type Attachment
You can configure a document type that can be used to archive any
attachment. Leave the document class empty for this ArchiveLink
document type in the OAC2 transaction. To archive any document, you must
implement the Pre Exit Registration.
Document Type Mail
You can configure a document type that can be used to archive the email
body. Leave the document class empty for this ArchiveLink document type

in the OAC2 transaction. To archive any document, you must implement the
Pre Exit Registration.
Attach Body
If this option is selected and the Render to PDF option is not selected, then
the body of the email is archived according to the format configured in the
SAPConnect interface (text/html mail).|
Render to PDF
If this option is selected, then a basic PDF rendition is created that contains
the email body text and the selected email properties (sender, recipient,
subject and others). This feature does not create an exact PDF rendition of
the entire e-mail and is therefore not suitable for OCR purposes. This
feature may not function correctly for all emails, in particular highly
formatted emails with embedded HTML content. This feature requires a
Unicode SAP system. Installation of Adobe Reader Font Packs may be
required to open the PDF document.
Inbound Configuration. Use the /OTX/PF01_UTIL_EXIT_REG_BEFORE
template. For the email processing function, /OTX/PF01_UTIL_EXIT_REG_
MAIL is delivered to process the relevant archiving of the various documents
(leading document / attachments / mail body). The /OTX/PF01_UTIL_EXIT_
REG_MAIL function archives the leading documents according to the mime
type assigned to the ArchiveLink document type. If more than one
document with the mime type of the leading document exists, each
document is registered of its own.
Configuration. Use the /OTX/PF01_UTIL_EXIT_REG_AFTER template.
Register synchron
Note: The email addresses might be different across the system landscape.
Therefore, the /OTX/PF01_ADM_SMAI transaction is available to adjust the
values in test and production systems. In general, production systems do not
allow any configuration changes. The transaction is protected against a special
administration authorization. For more information, see “Authorizations”
on page 224.

4.4.2.4 Customizing the Document Pipeline registration type

You can handle incoming documents using the OpenText Document Pipeline
(Document Pipeline).
You must link the Document Pipeline processing to the defined function module of
the Inbound Configuration inside SAP ERP. You must set a specific RFC mode that
must match the customizing entry on the remote Document Pipeline.
For details about the Document Pipeline, see OpenText Document Pipelines - Overview
and Import Interfaces (AR-CDP).
4.4.2.4.1 Maintaining general settings
Add a new entry to the J_6NGTE26 table with the following values:
RFC_Mode
8
FUNCNAME
/OTX/PF01_UTIL_PIPELINE_INPUT
The Document Pipeline typically requires one COMMANDS and one IXATTR file in
addition to the actual image file (for example image.pdf) and the LOG file. See the
following example:
COMMANDS
R3_CLIENT 800
R3_DESTINATION DW3
USE_VR4WFL 8
DOCTYPE PDF
COMP data PDF image.pdf
ARCHIVID Y4
IXATTR
NEWDOC
ATTRIBUTES /OTX/PS01_T_PLH|MANDT|CC|800|
ATTRIBUTES /OTX/PS01_T_PLH|BLDAT|DD|20141010|
ATTRIBUTES /OTX/PS01_T_PLH|BUKRS|CC|1000|
ATTRIBUTES /OTX/PS01_T_PLH|BUDAT|DD|20141010|
ATTRIBUTES TOAV0|MANDT|CC|800|/OTX/PS01_T_PLH|
ATTRIBUTES TOAV0|AR_OBJECT|CC|/OTX/DN2|/OTX/PS01_T_PLH|
ATTRIBUTES TOAV0|SAP_OBJECT|CC|/OTX/1REG|/OTX/PS01_T_PLH|
ARCHIVIDATTR TOAV0|ARCHIV_ID|CC|%s|/OTX/PS01_T_PLH|
DOCIDATTR TOAV0|ARC_DOC_ID|CC|%s|/OTX/PS01_T_PLH|
The document attributes must be transferred according to the business application

target table settings. For more information, see “Data model configuration”
on page 163. The attributes and values are stored in the /OTX/PF01_T_1EXT table,
which collects all extracted data intermediately.
The final mapping of the fields to the target business application is done within the
Data Model Configuration. For more information, see “Data model configuration”
on page 163.

4.4.2.4.2 Customizing the Document Pipeline registration
For the registration of documents, the ArchiveLink document type is assigned to the
handler process, a channel, and the classification profile.
To customize the Document Pipeline registration:
> Document Handler > Registration > Pipeline.
3. In the Registration - Pipeline Overview screen, customize the Document
Pipeline registration, using the following parameters.
Document Type
ArchiveLink document type that is used for the registration
Channel
Enter the ID of the channel that is used for this registration type. For more
Handler
Enter the ID of the document handler that represents the processing steps of
the service modules for this document. For more information, see
“Customizing incoming documents through the document handler”
on page 58.
Classify
Inbound Configuration. Use the /OTX/PF01_UTIL_EXIT_REG_BEFORE
template.
Configuration. Use the /OTX/PF01_UTIL_EXIT_REG_AFTER template.

4.4.2.5 Customizing a custom registration type

Besides the registration types that are described in the previous sections, you can
customize document registration using a custom registration. You might need to
configure a custom registration within a completely new incoming document
scenario. In this case, you must implement the /OTX/PF01_IF_REGISTRATION
interface. You can use the custom registration type to configure and access specific
settings.
To customize a custom registration:
> Document Handler > Registration > Custom / Others.
3. In the Registration – Custom / Others screen, customize the registration, using

the following parameters.
External Profile
Unique ID to identify the setting and access the setting for the custom
registration type in your custom registration implementation.
Channel
Enter the channel ID that is used for this registration type. For more
Module Handler
Enter the handler ID that represents the processing steps of the service
Classification
Enter the classification ID of the incoming document. For more information,
see “Creating scenario classifications” on page 56.
Document type
You can configure a document type that is used to archive the leading
application document, for example an order or a delivery note. To archive
any document, you must implement the Pre Exit Registration.
Document type att.

Document Type Attachment. You can configure a document type that is
used to archive any attachment. Leave the document class empty for this
ArchiveLink document type in the OAC2 transaction. To archive any
attachment, you must implement the Pre Exit Registration.
Pre Exit Reg.

Pre Exit Registration. Enter a function that runs before the document is
registered in Inbound Configuration. Use the /OTX/PF01_UTIL_EXIT_REG_
BEFORE template.

4.5. API for document registration
Past Exit Reg.

Past Exit Registration. Enter a function that runs after the document is
registered in Inbound Configuration. Use the /OTX/PF01_UTIL_EXIT_REG_
AFTER template.
4.5 API for document registration

Starting with version 16.3.2, Business Center provides an API for the registration of
documents. This allows the start of Business Center processes from none-SAP
systems.
Available services:
• /OTBCINB/PF01_REGIST_DOC
• /OTX/PF01_REGISTER
4.5.1 /OTBCINB/PF01_REGIST_DOC
The service registers the document as customized for the archive object and
document type.
The request is a multipart request that comprises three parts:
• register_document_request
• document
• metadata
The first part register_document_request is a XML structure and contains the key
information for the document.
The XML is transferred using the XML transformation /OTX/PF01_REGIST_DOC_

REQUEST with the /OTX/PF01_S_REGIST_DOC_REQUEST DDIC structure . The the
length restrictions of this DDIC structure apply for all fields.
Element Description
Scan date.
scan_date The format for the scan date is YYYY-MM-DD in the time zone of the
SAP system.
Scan time.
scan_time
The format is hh:mm:ss in the time zone of the SAP system.
scan_user Scan user
ar_object Document type
doc_type Document class

Element Description
Document ID in Archive (only in case the document has already been
arc_doc_id
archived)
archive_id Archive ID
Version of the API that is called. Current version is version 1. If version
version
is not provided in call, then the latest version will be used.
Example 4-1: Example for xml structure
The second part document contains the document and is of type binary. If the
document has already been archived and the parameters ARC_DOC_ID and ARCHIV_
ID have been provided in the first part, you can leave this part empty.
The third part metadata is an XML structure and can contain information from an
extraction service. The provided data is mapped to the structure of the process data
as defined in the data model of the process. This part is only processed if the
document was also provided in the second part. It contains an array with the
following structure:
Element Description
extindex External index of field
Additional field information (for example row information in case of
fieldinfo
line items)
extfield External field name
extvalue Value
As a response, the service returns a multipart structure. This currently comprises

only a “response” part, which has the following XML structure:
Element Description
regid Registration ID of the document
Running the service requires the authorization OTBCINB for authorization object S_
ICF.

4.6. Add additional logic to standard actions (BAdI /OTX/PF32_IDF_WOBJ_ACTION)
4.5.2 /OTX/PF01_REGISTER
You can implement additional logic using the /OTX/PF01_REGISTER BAdI. This
BAdI has the following interface.
PROC- This method is called at the beginning of the API. It allows you to access the
ESS_PRE_RE metadata to process own logic. It is also possible to skip the whole standard logic to
GISTER
method –
register the document

PE_SKIP Exporting Skip processing / registration
PE_RESPNSE_REASON Exporting HTTP response reason which
is sent when the processing is
skipped
PE_RESPONSE_CODE Exporting HTTP response reason which
is sent when the processing is
skipped
PCT_MULTIPART Changing Multipart content
PROC- This method is called at the end of the API when the document was registered. It
ESS_PAST_RE allows you to access the metadata and the response (with the registration ID).
GISTER
method –
PIT_MULTIPART IMPORTING Multipart content
PIS_RESPONSE IMPORTING Response information which
is sent with multipart
4.6 Add additional logic to standard actions (BAdI /

OTX/PF32_IDF_WOBJ_ACTION)
The /OTX/PF32_IDF_WOBJ_ACTION BAdI is part of the /OTX/PF32_IDF_WOBJ_
ACTION enhancement spot and implements the /OTX/PF32_IF_BADI_IDF_WOBJ_ACT
interface.
The BAdl allows to add additional logic to the following standard actions that are
available in the Inbound Administration work center of the Business Center
Workplace:
• Change Status
• Reject
• Reset Retry Counters
• Reset Training
• Submit Handler

For more information, see Section 2.1 “Navigating the Business Center Workplace”
in OpenText Vendor Invoice Management for SAP Solutions - User Guide for Solutions
Beyond Invoice (BOCP200400-UGD).
4.6.1 Add custom code before executing the action

(BEFORE_EXECUTE_ACTION)
This method allows to add custom code before executing the corresponding action.

PI_BULK Importing Indicator that an action is a
bulk action
PI_ACTION Importing Technical ID of the executed
action
PIS_WOBJ_TYPE Importing Corresponding work object
type configuration
PIS_DISPLAY_ Importing Current inbound attribute
ATTRIBUTES data values
PCT_RETURN Changing Returns messages of the
BAdI method.
Any message that returns

with E type stops the
execution of the action and
displays the error message to
the user.
4.6.2 Add custom code after executing the action

(AFTER_EXECUTE_ACTION)
This method allows to add custom code after executing the corresponding action.

PI_BULK Importing Indicator that an action is a
bulk action
PI_ACTION Importing Technical ID of the executed
action
PIS_WOBJ_TYPE Importing Corresponding work object
type configuration
PIS_DISPLAY_ Importing Current inbound attribute
ATTRIBUTES data values
PI_ACTION_SUCCESS Importing Indicator if the action has
been executed successfully or
not

4.7. Rendition management

PIT_ACTION_RETURN Importing Returns messages of the
executed action
PCT_AFTER_RETURN Changing Returns messages of the
BAdI method.
It is not possible to revert the

execution of the standard
action in this stage.
Only return messages other

than E type can be returned
and displayed to the user in
addition to the standard
action return messages.
4.7 Rendition management

The inbound configuration provides the possibility to integrate document rendering
by using the rendition management of OpenText™ Archiving and Document Access
for SAP Solutions. You must therefore, install and configure the corresponding
components of Archiving and Document Access for SAP Solutions. For more
information, see OpenText Archiving and Document Access for SAP Solutions -
Installation and Upgrade Guide (ER-IGD).
For further information about rendition management, see the documentation of

Archiving and Document Access for SAP Solutions.
In some scenarios you will receive a Microsoft Office document and not the PDF
document that you need for processing. This PDF can get processed in the further
processing steps.
To do archiving and extraction for these documents, the rendition management

renders the document into a PDF within the document handler process. For more
information, see “Creating a document handler process” on page 58.
To integrate the rendition management, configure your own document handler

process with a new module. For more information, see “Configuring modules for
the required processing steps” on page 60.
Sequence
Define the sequence how the modules are processed. The Render and archive
image module should be processed before the document is sent to the extraction
service
Module Class
Implement processing logic in /OTX/PF01_CL_MODULE_RENDER class.
Redefine this class to your need.
End Status
Enter the status 35 “Document rendered and archived”.

Additionally to the configuration of a document handler process, you have to

maintain parameters for the rendition server. The rendition server must be set up
according to the documentation of Archiving and Document Access for SAP
Solutions.
For more information see “Customizing basic settings for Inbound Configuration”
on page 52.

Chapter 5
Capture Integration
5.1 Business Center Capture

For solutions that require OCR, you can integrate OpenText Business Center
Capture for SAP Solutions (Business Center Capture).
Business Center Capture automates the capture of paper documents by using OCR
to extract the data. Business Center Capture uses SAP ERP as backend to store and
retrieve image information through the inbound process.
Using service modules of Inbound Configuration, you can control all tasks that are
related to the following actions of Business Center Capture:
• Storing documents
• Retrieving documents
• Extracting documents
• Validating documents
Steps from the paper invoice to document registration with Business Center
Capture (BCC)
1. SAP ERP calls the scan client through the Early Archiving registration type,
using the OAWD transaction.

Chapter 5 Capture Integration
2. The scan client deposits the image to the content repository (Archive).
The OAWD transaction creates a registration entry in SAP ERP using the
registration interface class implementation /OTX/PF01_CL_REGISTER_OAWD.
The registration method inserts an entry to tables /OTX/PF01_T_1REG and /OTX/
PF01_T_1IMG and sets status Registered.
Alternative: Incoming email is used for registration of a new document.
3. The document handler (periodic job for report /OTX/PF01_P_IDF_TRIGGER)
processes the required service modules in SAP ERP and sets the status
accordingly.
4. The BCC Extraction service calls the API function /OTX/PF01_IF_GET_NEW_DOC_
LIST using a scheduled batch job on BCC side and gets new documents for
processing:
• Gets all documents in status Ready for OCR extraction along with secure
URL for image and XML document, which will be created by the BCC
Extraction service.
• Updates the document status to Sent to OCR.
5. The BCC Extraction service picks the documents from step 3 and imports the
corresponding images from the archive.
6. The Export module of the BCC Extraction service calls the API function /OTX/
PF01_IF_OCR_DATA_UPDATE_N with call point EX:
• Updates the status and OCR data appropriately. This API exports the data to
SAP ERP after completion of the extraction phase. Table /OTX/PF01_T_1EXT
will be updated with extracted data.
• Updates the document status to Extraction Completed.
7. The BCC Extraction service sends the detailed results XML file of the exported
data to the Archive using the URL retrieved from SAP ERP in step 4. The BCC
Validation engine uses the XML file.
Results for each data exported to SAP ERP are stored in an XML file and
archived.
8. The document handler picks up the registered items with status Wait for
Extraction completed and checks the time elapsed. If it exceeds the configured
time, the status is set to Error.
9. The document handler picks up the registered items with status Extraction
Completed. The document handler checks if validation is required or not. If
validation is required, the status is set to Ready for Validation. If validation is
not required, the document handler will process the corresponding service
modules and trigger the target application.
10. The BCC Validation service calls the /OTX/PF01_IF_GET_VAL_DOC_LIST API
and gets a list of documents for validation:
• Gets all the documents in status Ready for Validation.

5.2. Information Extraction Service
• For each document, it gets the secure URL for image and XML documents,
which will be used by the BCC Validation Client.
11. The BCC Validation service picks documents (both image and XML) from the
Archive for each validation document, using the URL retrieved from SAP ERP.
12. The BCC Validation service calls the /OTX/PF01_IF_OCR_DATA_UPDATE_N API
with call point VA:
• Updates the status and OCR data appropriately. This API exports the data to
SAP ERP after completion of the validation phase. The /OTX/PF01_T_1EXT
table is updated with validation data.
• Updates the document status to Validation Completed.
13. The document handler picks up registered items with status Wait for
Validation completed, and after elapsed time sets the status to Error.
14. The document handler picks up registered items with status Validation
Completed, processes the corresponding service modules, and triggers the target
application.
5.1.1 Checking archive settings for XML documents

The component type for the XML document that is created by the BCC or IES
Extraction service is assigned to the used archive. Usually, you do not need to
change this entry, except for some cases (according to the used archiving system) to
configure the component ID data for the related content repository.
5.2 Information Extraction Service

5.2.1 Functional Overview
5.2.1.1 Architecture
Information Extraction Service is a Microsoft Windows based data extraction
services which is called by SAP via REST based web services, supporting HTTP and
HTTPS.
Information Extraction Service API provides three services which are called from
SAP:
• Configuration Service: Receives configuration data for recognition profiles

related to business scenarios.
• Extraction Service: Receives requests for extracting data from an image file and
provides result data.
• Learning Service: Receives feedback data.
You can configure the feedback source. It can be sent after validation from the
Validation client. Or after the end of the business process. You can use the
SCESAPGUI or Fiori Validation for the validation within the business process.

The Learning Service processes the feedback data and stores machine learning data
in its repository:
• Intelligent Capture for SAP® Solutions uses the SAP database as repository.
• Core Capture for SAP® Solutions uses the OT2 public cloud as repository.
5.2.1.2 Scenarios and profile concept

The configuration of the scenarios is completely done in the Inbound Configuration,
that means that you need not configure the Information Extraction Server.
Profile configu- A profile is a specific configuration of a scenario and allows the following
ration customizing:
• Definition of preferred format interpretation for dates, amounts, and other

country specific values.
• Definition of additional custom extraction fields.
• Definition of field settings for validation.
To use document capture with IES, you must configure at least one profile for the
used scenario. In a scenario, standard extraction fields and extraction parameters are
defined for one type of document.
The number of profiles per scenario and the overall number of profiles is not limited.
The profile configuration depends on the specific business requirement, such as

different company codes or countries.

The following graphic illustrates the relation between a scenario and a profile:
All settings in the customizing activity “Profile maintenance” are transportable. This
means that they are maintained in a customizing client and then transported to a test
or production system.
Profile activation is executed only in clients where IES is intended to be used.

Usually this is a test or production system.
5.2.1.3 Intelligent field types

Intelligent field types include the knowledge about the data structure, potential local
formats, their meaning in different business contexts, tax compliance and how they
are used in SAP. As an example, a field type specifies date formats, for example
MMDDYYYY, DDMMYYYY, DD.MM.YYYY, DD/MM/YYYY, and date writing styles, for example
month spelled out, without the need of defining it for any solution.
All scenarios are based on intelligent field types which incorporate the knowledge
about identification and interpretation of typical data found in business documents:
dates, amounts, table items and so on.
For all fields of preconfigured scenarios, data transfer and mapping to the fields of
the corresponding VIM scenarios are part of the product.
For a preconfigured scenario, a defined set of fields is provided which cannot be

modified except you select the following options for validation:
• Input: Open for data entry.

• Hide: Not visible.

• Read only: Visible but not open for data entry.
• Required: Mandatory, highlighted in red if no data entered.
Preconfigured scenarios and custom scenarios can be extended by custom fields. For
custom fields the following field types are available:
• Amount
• Currency
• Classification
• Date
• Decimal
• Stringlist
• Lookup
• Partner
• String
• Table
Description
Description
Description is a field type which is specialized to extract text spanning over
multiple lines and columns.
Learning supported
Yes
Layout dependent
Yes
Use case
Extract complex item description text, for example material description from
tables.
Parameters
No parameters
Header/table supported
Table
Amount
Description
The amount field is a specialized decimal field which is limited to two
decimals. The amount field intepretes data with regards to the settings of
the format interpretation list, which defines the correct interpretation of
thousand and decimal separators.

Learning supported
Yes
Layout dependent
No
Use case
Item amount, total amount
Parameters
Format interpretation list
Header/table
Classification
Description
Classification is a string field and learns to determine different classes for
different document types.
Learning supported
Yes
Layout dependent
Yes
Use case
Classification of specific document types (transportation invoices, leasing
invoices), for example for routing to specific VIM workflows.
Parameters
Class name
Header/table
Currency
Description
Currency is a specialized string field which identifies supported currencies
and currency symbols on the document and normalizes it to ISO names for
supported currencies.
Learning supported
Yes
Layout dependent
No
Use case
Document currency, amount currency
Parameters
No parameters

Header/table
Date
Description
A date field is a strucured field which suppports typical date structures
(ddmmyyyy, mmddyyyy, month in letters and so on) for the supported
languages, depending on the settings of the format interpretation list. The
field is learned across layouts, considering typical surrounding keywords,
text and data structure.
Learning supported
Yes
Layout dependent
No
Use case
Document date, delivery date and so on
Parameters
Header/table
Decimal
Description
The decimal field supports up to 4 decimals. The decimal field intepretes
data with regards to the settings of the format interpretation list, which
defines the correct interpretation of thousand and decimal separators (“.” or
“,”). The field is learned across layouts, considering typical surrounding
keywords, text and data structure.
Learning supported
Yes
Layout dependent
No
Use case
Quantity, unit price
Parameters
Header/table

Partner
Description
The partner field is determining the business partner. The partner field
learns an ID for the partner related to the document layout. The partner field
can also learn multiple IDs related to one layout. The partner field is
connected to a staging table, which is used by the validation user for
retrieving the partner ID with F9.
Learning supported
Yes
Layout dependent
Yes
Use case
Supplier, customer
Parameters
Staging table
Header
String
Description
The string field does not have any normalization but learns a string as it is.
Learning supported
Yes
Layout dependent
No
Use case
Text, numbers
Parameters
No parameters
Header/table
Stringlist
Description
The stringlist is a list of strings. The user picks values with SCE and the field
type will then learn to extract all relevant strings of the same structure.
Learning supported
Yes
Layout dependent
Yes

Use case
PO list, DN list
Parameters
No parameters
Header
Table
Description
One profile supports multiple tables. A table is a structure consisting of lines
and columns. For every custom table column a field type needs to be
defined. A table will be learned related to a specific layout.
Learning supported
Yes
Layout dependent
Yes
Use case
Invoice table, sales order table
Parameters
Define field types for columns
Table
For more information about recognition and processing details for the fields of
invoice applications, see Section 9 “Field references for IES” in OpenText Vendor
Invoice Management for SAP Solutions - Scenario Guide for Invoice Solution (VIM200400-
CCS), “Defining custom fields” on page 141, and “Defining custom table fields”
on page 144.
5.2.1.4 Machine learning

The key advantage of Information Extraction Service is the reduction of
implementation and configuration efforts, combined with fast learning success. That
is why Information Extraction Service include preconfigured scenarios. For the
invoice solution the invoice knowledge base has been integrated and runs combined
with the intelligent field types leveraging a learning voting algorithm.

5.2.1.4.1 Learning algorithms
The learning algorithms foundation named CSA (= Continuous Self Adaptation) of

Information Extraction Service uses a combination of learning algorithms: Statistics
based algorithms in combination with artificial intelligence algorithms. All learning
algorithms are developed and owned by OpenText. OpenText has patents pending
for it. The focus of CSA learning algorithms is learning based on a small sample set
of business documents through user feedback or feedback from automated business
rules. CSA starts learning as soon as the first document is processed. Learning is
based on a combination of two different algorithm types and a mixture of both:
• Layout based algorithms, for example business partner determination, and item
table recognition. These work based on the layout. Layout based learning means
that internally a model is computed per document layout. Layout definition is
mostly text based and also considers geometry of the data located on a
document. So typically a document related to a business partner may be
considered as a layout. But in reality multiple business partners are sharing the
same layout, the learning algorithm is also able to handle sublayouts.
Layout based algorithms learn very fast, providing automatic recognition result
from the second pass of the same layout. For complex tables more passes may be
necessary.
• Layout independent algorithms, for example data, such as amounts, dates and
document references. These algorithms identify relevant data structures and
keywords and learn to extract it also on documents with an entirely different
layout.
Layout independent algorithms take more time to learn data structures, related
keywords and surrounding text. What has been learned by this algorithm type
will also be applied to completely unknown documents containing the same data
structures, keywords and surrounding text. With this technique, the data entry
effort diminishes more and more, and the longer the system is in production it
learns more document layouts.
Learning Before using Information Extraction Service, the user manually entered data from
system business documents. With Information Extraction Service, the user continues to do
his daily work, and with this he provides feedback data to the learning service,
which learns to capture the data automatically starting from the second pass of a
document with either the same layout or showing the same data type, for example
date field with the same format and key word.
Learning is permanently active for adapting continuously to the documents

processed in customer environment.
For invoices the user starts from a higher level, because he will get “out of the box”
recognition results from the invoice knowledge base where applicable. A user will
only need to enter data for additional fields that are not supported by the invoice
knowledge base, for example a material number, or fields that could not be extracted
by the invoice knowledge base for some reason, for example complex invoice line
items.

No training phase is required as the system learns unattended in the background.

The business user is the best source of knowledge for the learning process because
he knows exactly which is the relevant data to be captured for creating a business
object in SAP.
5.2.1.4.2 Best practise learning strategy
In general customers want to prepare the system for business users by applying
preparative learning before business users are using the system. For comfortable
optimization of the system before going live, following features are available:
• Validation Client for SAP Solutions: A Microsoft Windows based workplace for
correcting and completing IES result data with Single Click Entry (SCE). In this
worplace the optimal learning data are created including geometry coordinates
of the catured data. When submitting a document in the Validation Client,
feedback data are sent to the learning service, if configured accordingly for the
profile (feedback after validation). Learning service can apply best learning from
feedback data with geometrical information.
• Pre-learning based on historical validated extraction result data from Invoice
Capture Center (ICC) or Business Center Capture (BCC). This feature addresses
customers switching from OpenText Invoice Capture Center / OpenText Business
Center Capture to Information Extraction Service. For more information, see
Section 2.3 “Pre-learning of IES Profiles” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM200400-AGD).
• Creating snapshots of learning data for transporting it between profiles and SAP
systems. This feature allows to, for example reuse learning data from
preproduction system in production system. It also allows to reuse learning data
acquired in a profile version 1, in a profile version 2.
• Validation determination rule. Implementing and adjusting validation
determination rules allows to define which documents go to the Validation
Client. In the starting phase, it is recommended to check every document in the
Validation Client and to apply corrections for creating feedback data for the

learning service. After some weeks or months, depending on when 3 to 5

documents of the same business partner for the main business partners,
representing 70 to 80% of the document volume, have been processed, validation
determination rules should be implemented. Validation determination should
specify rules for routing only specific documents into Validation Client. These
rules can, for example list mandatory fields which need to be filled, but may also
specify more sophisticated rules based on a user exit.
• In addition to Validation Client for SAP Solutions alternative data completion
solutions exist for creating feedback data:
– SCESAPGUI: SCE control for VIM workplace, which allows to create

feedback data with geometry information in VIM workplace. This control just
supports invoice scenario. For more information, see Section 6.2 “Integration
with Information Extraction Service” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide for Invoice Solution (VIM200400-CGD).
– Fiori validation: An extension for workplace for sales order scenario also
providing SCE functionality for sending feedback with geometry information
to learning service.
• Both alternative data completion solutions allow to skip Validation Client and
send feedback data at process end. This means after creation of the SAP business
object, for example posting of an invoice or creation of a sales order. So feedback
for learning is sent later compared to using Validation Client in the inbound
process.
5.2.1.5 Processing steps

You can control the following tasks with service modules of the Inbound
Configuration:
• Storing documents
• Retrieving documents
• Extracting documents
• Validating documents
Steps for document extraction with Information Extraction Service:
1. The document handler processes the required service modules and sends the
image along with parameters for extraction and business data to Information
Extraction Service.
• The status is set to Sent to Extraction.

2. Information Extraction Service processes the document and sends the extraction
result back.
• Extraction result is stored in /OTX/PF11_T_DEXT table.

• Document status is set to Extraction Completed.

3. The document handler picks the registered items with status Extraction
Completed and checks if validation is required.
If validation is required, the status is set to Ready for Validation.

If validation is not required, the document handler processes the corresponding
service modules and triggers the target application.
4. The validation service calls the /OTX/PF11_VAL_GET_DATA API and gets the next
document for validation:
• It gets one document in status Ready for Validation.
• For this document, it gets the extraction result, which is used by the
Validation Client.
5. When the validation is completed by submitting extraction results, the

Validation Client calls the /OTX/PF11_VAL_SET_DATA API:
• It updates the extraction data in table /OTX/PF11_T_DEXT with validation

data.
• It updates the document status to Validation Completed.
6. The /OTX/PF11_VAL_SET_DATA API checks if the feedback should be sent after

validation.
If it should be sent, the validated extraction result is sent to Information
Extraction Service and processed accordingly.
7. The document handler picks the registered items with status Validation
Completed, processes the corresponding service modules, and triggers the target
application.
The following parameters for request time-out, retry of requests, and waiting period
in case of temporary connection problems are set for communication of SAP and
Information Extraction Service:
Request Type Timeout Retries Waiting period for retry (seconds)

(seconds)
Feedback 3600 3 60 (doubled for each retry)
Extract 3600 3 60 (doubled for each retry)
Create profile 60 0 60 (doubled for each retry)
Delete profile 60 3 60 (doubled for each retry)
Update profile 60 0 60 (doubled for each retry)
Note: In contrast to retry configuration, time-out configuration is only relevant

for Information Extraction Service on-premises deployment.

5.2.2 Configure connection

5.2.2.1 On-Premises: Configuring the connection
There is a communication in two directions between SAP and IES. To establish an
outbound as well as an inbound connection, the communication must be configured.
The IES Request handler must be scheduled to monitor timeouts and initiate
automatic retries of requests. For more information, see Section 2.2.4 “IES request
handler” in OpenText Vendor Invoice Management for SAP Solutions - Administration
Guide (VIM200400-AGD).
Note: Configure the relevant HTTP or HTTPS settings within the Information
Extraction Service. For more information, see Section 6.10.1 “Intelligent
Capture for SAP (on-premises)” in OpenText Vendor Invoice Management for SAP
Solutions - Administration Guide (VIM200400-AGD).
From a security perspective, in most cases communication via http or https

without client certificate authentication is sufficient. Be aware that
communication via https with client certificate authentication is much more
complex and additional requirements have to be met.
5.2.2.1.1 On-Premises: Outbound communication
There are several scenarios for the outbound communication:
5.2.2.1.1.1 Scenario 1: Communication using HTTP
To configure the outbound communication using HTTP:
1. Run the SM59 transaction to configure a new RFC connection.
2. Create a new RFC destination of type G (HTTP Connection to External Server)

with the following parameters:
Header parameters
RFC Destination
Technical ID of the connection
Connection Type
Choose type G.
Description
Enter a description for the connection.
Technical Settings tab
Target Host
Full qualified host name of the IES service

Service No.
Port of IES service which should be used to retrieve requests. For HTTP
connections, this is usually 8080.

4. Run a connection test using the corresponding button in the application toolbar.
The test result should include status HTTP response 200.
5.2.2.1.1.2 Scenario 2: Communication using HTTPS w/o SSL client certificate

authentication
To configure the outbound communication using HTTPS w/o SSL client

certificate authentication
1. Run the SM59 transaction to configure a new RFC connection.

2. Create a new RFC destination of type G (HTTP Connection to External Server)
with the following parameters:
Header parameters
RFC Destination
Technical ID of the connection
Connection Type
Choose type G.
Description
Enter a description for the connection.
Target Host
Full qualified host name of the IES service
Service No.
Port of IES service which is used to retrieve requests. For HTTPS port, this is
usually 443.
Note: To trust the IES server certificate, add its intermediate and root
CA certificates to the certificate list of the SSL client PSE of the SAP
system. For details, see SAP Note 510007.
3. On the Login & Security tab , perform the following configuration:
SSL
Select Active.
SSL Certificate
Select the appropriate SSL Client Identity (PSE) which does not use the SSL
client certificate, typically SSL Client (Anonymous). Run a connection test

using the corresponding button in the application toolbar. The test result
should include status HTTP response 200.
5.2.2.1.1.3 Scenario 3: Communication using HTTPS with SSL client certificate
To configure the outbound communication using HTTPS with SSL client

certificate authentication:
1. Perform the first two steps of scenario 2 (“Scenario 2: Communication using

HTTPS w/o SSL client certificate authentication” on page 115).
Notes
• The IES requires the subject name field (CN) of the SSL client certificate
of the SAP system to contain the fully qualified host name of the SAP
system. The default SSL client certificate does not meet this requirement
and therefore must be replaced.
• By default, the SSL client certificate is provided via client PSE SSL client
SSL Client (Standard).
• To trust the IES server certificate, add its intermediate and root CA
certificates to the certificate list of the SSL client PSE of the SAP system.
• For details, see SAP Note 510007.
2. On the tab Login & Security, perform the following configuration:
SSL
Select Active.
SSL Certificate
Select the appropriate SSL Client Identity (PSE) containing the SSL client
certificate, typically SSL Client (Standard).
3. Run a connection test using the corresponding button in the application toolbar.
5.2.2.1.2 On-Premises: Inbound communication
There are several scenarios for the inbound communication:

5.2.2.1.2.1 Scenario 1: Communication using HTTP
To configure the inbound communication using HTTP:
1. Run the PFCG transaction to create a role for processing inbound requests from
IES.
a. Define authorization for object S_ICF (Authorization Check for ICF Access)
with the following values:
• ICF_FIELD: 'SERVICE'
• ICF_VALUE: 'OTBCINB'
b. Add the authorization for the J_6NPF_RFC object (BC RFC calls) with the
values: ACTVT: '03'.
c. Save and generate the role.
2. Run the SU01 transaction to create a user of type Service for processing
inbound requests from IES and assign the authorization role defined in Step 1
on page 114.
3. Run the SICF transaction to create services for processing inbound requests
from IES.
Caution
Do not change any values on the selection screen and press the execute
button to get to the service maintenance screen.
Services are created below a virtual host. For example, default_host.
Align with your SAP basis administrator where to create the services
for inbound requests from IES.
4. Create a new service for repository requests of type Independent Service. For
example, zpf12_repo.
a. On the detail screen of the service, open the Service Data tab and define the
SAP authorization OTBCINB.
b. Switch to the Logon Data tab and set the procedure to Required with
Logon Data. In the logon data section, define the user name and the
password of the service user created in Step 2 on page 114.
c. Switch to the Handler List tab and define class /OTX/PF12_CL_SERVICE_
HNDL_REPO as handler with order number 1.
d. Activate the service and test it. When testing the service, an HTTP 400 error
with message ‘“Failed to load resource: the server responded with a status
of 400 (Request method GET not allowed)” should be displayed in a
browser window. This is the correct reaction because the handler class
blocks HTTP GET requests. If this message is visible, the configuration of
the service is correct, and the handler class is invoked.

5. Create a new service for result requests of type Independent Service. For
example, zpf11_result.
HNDL_RSLT as handler with order number 1.
5.2.2.1.2.2 Scenario 2: Communication using HTTPS w/o SSL client certificate

authentication
To configure the inbound communication using HTTP:
1. Run the PFCG transaction to create a role for processing inbound requests from
IES.
a. Define authorization for object S_ICF (Authorization Check for ICF Access)
with the following values:
• ICF_FIELD: 'SERVICE'
• ICF_VALUE: 'OTBCINB'
b. Add the authorization for the J_6NPF_RFC object (BC RFC calls) with the
values: ACTVT: '03'.
c. Save and generate the role.
2. Run the SU01 transaction to create a user of type Service for processing
inbound requests from IES and assign the authorization role defined in Step 1
on page 115.
3. Run the SICF transaction to create services for processing inbound requests
from IES.
Caution
Do not change any values on the selection screen and press the execute
button to get to the service maintenance screen.
Services are created below a virtual host. For example, default_host.
Align with your SAP basis administrator where to create the services
for inbound requests from IES.

4. Create a new service for repository requests of type Independent Service. For
example, zpf12_repo.
HNDL_REPO as handler with order number 1.
5. Create a new service for result requests of type Independent Service. For
example, zpf11_result.
HNDL_RSLT as handler with order number 1.
5.2.2.1.2.3 Scenario 3: Communication using HTTPS with SSL client certificate

authentication
To configure the inbound communication using HTTPS with SSL client

certificate authentication:
1. Perform the first two steps of scenario 1 (“To configure the inbound
communication using HTTP:“ on page 114).
Notes
• To trust the IES SSL client certificate, add its intermediate and root CA
certificates to the certificate list of the server PSE of the SAP system.
• By default, the server certificate is provided via server PSE SSL server
Standard.

• For details, see SAP Note 510007.
2. Instead of creating two new services for inbound communication, you may
leverage the two provided services /otbcinb/pf11_result and /otbcinb/
pf12_repository as they are. Activate these services if they are not yet active.
Note: As the inbound HTTPS communication requires IES’s SSL client

certificate to be sent, the logon procedure for both inbound services must
be Required with SSL Certificate.
As a result, you cannot test the services from within the SAP system itself.
3. Run the SM30 transaction to assign IES’s SSL client certificate to the service user
created in Step 1 on page 116 for processing inbound requests from IES, using
Table/View
Enter VUSREXTID, and then click Maintain.
External ID type
Select DN and continue.
4. To create a new entry, click New Entries:
a. Export the IES SSL client certificate into a file with suffix .cer.
b. To obtain the External ID from the .cer file, click the import button.
c. Select the service user for inbound communication created during Step 1
on page 116.
d. Enable the Activated flag.
5.2.2.1.3 On-Premises: Connection parameters
Note: Connection parameters are client-dependent and are not transportable.

Therefore you need to maintain connection parameters manually on each client
which you want to connect to IES.
To define connection parameters:
> Capture > Information Extraction Service > Connection parameters.
3. On the Global Settings Overview screen, define connection parameters using

the following keys:
Host name for inbound requests

Full qualified host name of the SAP system processing the inbound requests
from the IES service.

Not needed if the outbound communication to IES uses https with client
certificates. In this case, the host name is extracted from the CN attribute of
the SAP SSL client certificate used for the HTTPS communication from SAP
to IES.
Port for inbound requests (http)
Port of the SAP system which should be used to process http requests from
the IES service. Default is 8000.
Just needed if inbound communication with http is used.
Port for inbound requests (https)
Port of the SAP system which should be used to process https requests from
the IES service. Default is 8443.
Just needed if inbound communication with https is used.
4. Double-click Connection On-premise in the Dialog Structure.
5. On the Connection Overview screen, create a new entry.

Use the following parameters:
Connection ID
Technical ID of the connection to IES
Destination
Technical ID of the RFC destination to IES created in “On-Premises:
Outbound communication” on page 111.
SSL Enabled
Select this check box if SSL should be used for the request sent from IES to
SAP.
URL Path Repository
Enter the path to the service for inbound repository requests configured in
“On-Premises: Inbound communication” on page 113.
Note: Do not forget to start the path with a leading slash (/).
URL Path Result

Enter the path to the service for inbound result requests configured in “On-
Premises: Inbound communication” on page 113.
Note: Do not forget to start the path with a leading slash (/).
6. Save your configuration and return to the Business Center Configuration.
> Capture > Information Extraction Service > Connection test.
8. Execute a connection test for the connection ID that you created in the previous
steps.

The result screen should show that the connection test for all 3 services was
successful.
5.2.2.2 Cloud Edition: Configuring the connection

The communication from SAP to IES Cloud Edition is unidirectional. To establish
the outbound connection, the communication must be configured.
The IES Request handler must be scheduled to enable the unidirectional

communication to IES. Furthermore, this request handler monitors timeouts and
initiates automatic retries of requests. For more information, see Section 2.2.4 “IES
request handler” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM200400-AGD).
Tip: Before you start the configuration in SAP, obtain the client ID and the
client secret for accessing capture services.
5.2.2.2.1 Cloud Edition: Outbound communication
Note: To trust the IES SSL server certificate, add its intermediate and root CA
certificates to the certificate list of the SSL client PSE (Anonymous) of the SAP
system.
For details, see SAP Note 510007.
To retrieve details regarding the SSL server certificate call the respective
services URL in the browser, and then click the security button in the address
bar. The certificate details show for example the certificate chain up to the root
certificate. You can also export/download certificates from there.
To configure the outbound communication:
1. Run the SM59 transaction.

2. Create a new RFC destination for the connection to capture services.
Use the following settings:
RFC Destination
Technical ID of the connection. For example IES_CAPTURE.
Connection Type
Type G (HTTP Connection to External Server)
Description
A description for the connection.
• Target Host: Full qualified host name of capture services

• Path Prefix: Path to the home document of capture services. For
example, /cp-rest.

• Service No.: 443
Logon & Security tab
• Logon Procedure: No Logon

• SSL: Active
• SSL Client Certificates: ANONYM – SSL Client (Anonymous)
3. Click the Connection Test button.

With this test you validate that the URL for the capture service is correct and
that the service can be reached.
Tip: Write down the URL of the OAuth2 token service for the configuration
of the RFC destination to the OAuth2 token service.
You find the URL in the Response Body tab of the test result.
4. Create a new RFC destination for the connection to the OAuth2 token service.
Use the following settings:
RFC Destination
Technical ID of the connection. For example IES_TOKEN.
Connection Type
Type G (HTTP Connection to External Server)
Description
A description for the connection.
• Target Host: Full qualified host name of the OAuth2 token service.
• Path Prefix: Path to the OAuth2 token service . For example /
authserver/oauth/token.
• Service No.: 443
Logon & Security tab
• Logon Procedure: Basic Authentication

• SSL: Active
• SSL Client Certificates: ANONYM - SSL Client (Anonymous)
• Logon - User: Client ID for accessing capture services
• Logon - Password: Client Secret for accessing capture services

5. Click Save.
6. Click the Connection Test button.

The test result should include HTTP response 405 ‑ Method Not Allowed status.
With this test you validated that the URL for the OAuth2 token service is correct
and the service can be reached.
5.2.2.2.2 Cloud Edition: Connection parameters
Note: Connection parameters are client-dependent and are not transportable.

Therefore you need to maintain connection parameters manually on each client
which you want to connected to IES.
To configure the connection parameters:
> Capture > Information Extraction Service > Connection parameters.
3. Double-click Connection – Public Cloud.
4. On the Connection Public Cloud Overview screen, create a new entry.

Connection ID
Technical ID of the connection to IES.
Destination IES
Technical ID of the RFC destination for the capture services. For
example IES_CAPTURE.
The ID is created in the Outbound communication. For more information,
see “Cloud Edition: Outbound communication” on page 119.
Destination Token
Technical ID of the RFC destination for the OAuth2 token service. For
example IES_TOKEN.
The ID is created in the Outbound communication. For more information,
see “Cloud Edition: Outbound communication” on page 119.
5. Save your configuration and return to the Business Center Configuration.
> Capture > Information Extraction Service > Connection test.
7. Execute a connection test for the connection ID that you created in the previous
steps.
The result screen should show that the connection test for all 3 services was
successful.

5.2.2.3 Performing a connection test

After you add a connection to IES, you should perform a connection test.
This connection test verifies, that all the connection settings are correct and that the
end-to-end communication is working.
In contrast to a simple ping to the RFC destination this connection test verifies:
• The credentials that are used to obtain the access tokens (just relevant for cloud
edition).
• The inbound connection (just relevant for on-premises).
• The IES server processing.
To perform a connection test:

> Capture > Information Extraction Service > Connection Test.
3. On the selection screen use the following parameter:
Connection ID
Technical ID of the connection to IES
4. Click Execute.
5. Verify if the connection test was successful.
5.2.3 Customizing
The following mandatory configurations, set up a best practice default to capture
information.
To use Information Extraction Service there are following mandatory tasks in

Inbound Configuration:
1. Reuse existing document handler or create your own module handler. Use:
• CAPTURE_CL for solutions beyond invoice

• PS03_IES for invoice solution
• Module class /OTX/PF11_CL_MOD_REQUEST_SEND to create your own module
handler with Information Extraction Service. For more information, see
“Creating a document handler” on page 59.
2. Create a registration type which is using this document handler. For more
information, see “Customizing registration types” on page 62.
3. Create a profile and assign it to the scenario. For more information, see
“Creating a profile” on page 129.

4. Assign the ArchiveLink document type which is used for your registration type
to the profile. For more information, see “Assigning an ArchiveLink document
type” on page 146.
5. Activate the profile and specify the IES connection. For more information, see
“Activating and updating a profile” on page 147.
Note: OpenText recomments to consider the optional tasks regarding format

interpretation and validation field settings into account.
As learning is one of the central features of Information Extraction Service make sure
that feedback is provided in an optimal way as described in the Best practice
learning strategy. For more information, see “Customizing feedback” on page 154.
To enable validation, see the dedicated configuration. For more information, see
“Customizing validation” on page 150.
If there is a need for additional extraction fields, see:
• “Defining custom fields” on page 141

• “Defining custom table fields” on page 144
You can customize the default Business Entity Determination behavior:
• “Customizing the Business Entity determination” on page 123.

• “Defining custom entity determination fields” on page 133
• “Assigning an entity determination field” on page 136
• “Assigning an entity determination” on page 137
5.2.3.1 Customizing the 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:
Example:
• Order
– Ship-to party
– Sold-to party
• Invoice
– Supplier/Vendor
– Company code

5.2.3.1.1 Processing of the Business Entity determination
Various data (business entity attribute fields) which can appear on business
documents is used to determine business entity candidates in SAP.
Attribute fields which are extracted from a document belong either to the master
data of the business entity, for example name, address, bank details, tax number or
they are related to some transaction data (to a reference document, for example,
purchase order).
Extracted attribute fields are used in SAP to look up possible business entity
candidates. In an additional extraction step, the determined business entity
candidates are matched with a specific confidence against further available
information on the document.
The result is used to determine the business entity on SAP side.
In the past, IES used solely a learning-based method to determine business entities.
This requires some training.

Business entity determination and configuration provides the possibility to consider

SAP master data and/or transactional data for business entity determination in
combination with a learning-based method. The business entity is only determined
based on the result of the related matcher fields. For more information, see
“Configuring the Determination Definition” on page 127.
To use business entity determination with IES, you must configure at least one
profile with the new version 2 scenario for the used scenario. For more information,
see “Scenario 2: Communication using HTTPS w/o SSL client certificate
authentication” on page 112.
In a scenario, standard attribute fields and extraction parameters are defined for the
specific scenario version. The pre-configured attribute fields are used in the business
entity determination configuration which provides a best practice implementation to
determine the business entity. Custom attribute fields to determine the business
entity candidates can also be added to the profile configuration.
Delivered attribute fields for entity determination:
Attribute field Type Description Field Exit

IBANCandidates iban_number IBAN numbers
MailAddresses email Mail addresses /OTX/
PS00_CL_ATTR_CA
ND_MAIL
POCandidates range Purchase order /OTX/
numbers PS00_CL_ATTR_CA
ND_PO
RecipientAddresses address Recipient addresses /OTX/
(company code) PS00_CL_ATTR_AD
DR_BUKRS
RecipientAttributes attribute_extractor Recipient attribute /OTX/
extractor (company PS00_CL_ATTR_EXT
code) R_BUKRS
RecipientMatcher entity_matcher Entity matcher for /OTX/
recipient (company PS00_CL_ATTR_MA
code) TCH_BUKRS
ShipToAddresses address ShipTo addresses /OTX/
PS00_CL_ATTR_AD
DR_SHIPTO
ShipToAttributes attribute_extractor ShipTo attribute /OTX/
extractor PS00_CL_ATTR_EXT
R_SHIPTO
ShipToMatcher entity_matcher Entity matcher for /OTX/
ShipTo PS00_CL_ATTR_MA
TCH_SHIPTO

Attribute field Type Description Field Exit

SoldToAddresses address SoldTo addresses /OTX/
PS00_CL_ATTR_AD
DR_SOLDTO
SoldToAttributes attribute_extractor SoldTo attribute /OTX/
R_SOLDTO
SoldToMatcher entity_matcher Entity matcher for /OTX/
SoldTo PS00_CL_ATTR_MA
TCH_SOLDTO
SupplierAddresses address Supplier addresses /OTX/
PS00_CL_ATTR_AD
DR_LIFNR
SupplierAttributes attribute_extractor Supplier attribute /OTX/
R_LIFNR
SupplierMatcher entity_matcher Entity matcher for /OTX/
supplier PS00_CL_ATTR_MA
TCH_LIFNR
TaxNumberCandidat tax_number VAT IDs
es
URLAddresses url URL addresses /OTX/
PS00_CL_ATTR_CA
ND_URL
The look up of possible business entity candidates from extracted attribute fields is
processed from the staging tables. You must therefore schedule the corresponding
reports to fill the staging tables. For more information, see OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM200400-AGD).
5.2.3.1.2 Migration
In order to migrate a profile of version 1 scenario (learning-based method) to the

new version 2 scenario (using business entity determination), the following steps are
required:
• Create a snapshot of your active profile which you want to migrate. For more
information, see Section 4.1 “Creating a snapshot” in OpenText Vendor Invoice
Copy the profile that you want to migrate to a new profile, and then specify
version 2. For more information, see “Copying a profile” on page 132.
• Activate the newly created profile with restore of snapshot. For more
information, see Section 4.3 “Restoring a snapshot” in OpenText Vendor Invoice
• Execute pre-learning for business entity determination operators. For more
information, see Section 2.3.5.2 “Initiating pre-learning of a selection variant for

BED” in OpenText Vendor Invoice Management for SAP Solutions - Administration

Guide (VIM200400-AGD).
• Assign the archive link document type from the old profile to your newly created
profile to run newly injected documents with the new profile.
• Ensure that the report to fill the related staging tables is executed again. For more
information, see Section 2.2.2 “Staging tables for capture integration” in OpenText
Vendor Invoice Management for SAP Solutions - Administration Guide (VIM200400-
AGD).
5.2.3.1.3 Configuring the Determination Definition
The determination definition is pre-delivered and used within a scenario for the
corresponding business entity fields. An own determination definition can be used,
which is assigned within the profile maintenance to the corresponding entity field.
For more information, see “Assigning an entity determination” on page 137.
To define a determination:

> Capture > Information Extraction Service > Business Entity Determination.
3. On the Determination Definition Overview screen, create a new entry with the
Determination ID
Technical ID of the determination.
Description
Description of the determination.
Confidence
The minimum confidence to select the business entity (integer value
describing a percentage between 0 and 100). If the confidence is not
maintained the business entity with the highest confidence is automatically
used if there does not exist an additional business entity with the same
confidence.
Distance
Distance between matching confidences of different business partners to
select a business entity (integer value). If the distance is not maintained the
highest confidence is used.
Matcher field
Assign the entity matcher field which is used to extract and match the
business entity with additional information on the document with a specific
confidence.
Scenario related matcher
For delivered entity matcher scenario fields (not custom fields) the
checkbox must be selected.

Attribute extractor field

Field which is used to extract learned business attributes from a document.
Scenario related attribute
For delivered attribute extractor scenario fields (not custom fields) the
checkbox must be selected.
5.2.3.1.4 Maintaining the LookUp condition
You have to maintain the LookUp condition for each extracted attribute field which is
used to determine the business entity candidates in SAP.
To configure the lookup:

> Capture > Information Extraction Service > Business Entity Determination.
3. On the Determination Definition Overview screen, mark an entry, and then in
the Dialog Structure, double-click Determination Field LookUp.
4. On the Determination Field LookUp screen, create a new entry using the
Attribute field
Select a scenario-related or a custom attribute field that is used to extract the
information on the document. For more information, see “Assigning an
entity determination field” on page 136.
Scenario related
For pre-delivered attribute scenario fields (not custom fields) the checkbox
must be selected.
LookUp table
Enter the table which is used to look up the values.
LookUp field name
Enter the table field which is used to look up the values.
LookUp entity key field
Enter the table field which is selected and which defines the business entity.
External field name (path)
For extracted attribute fields with a deep structure (for example, fields of
type address) enter the field path of the related field.
Normalize
Mark this checkbox to normalize the extracted value of the attribute field.
This processes the lookup against a value which was normalized in the
same way. The normalization of the value is processed within /OTX/PF11_
CL_UTILITIES=> NORMALIZE_LOOKUP_VALUE method which should be
reused for your own lookup fields.

5.2.3.2 Creating a profile

To create a profile:
2. Click OpenText Business Center for SAP Solutions > Inbound

Configuration > Capture > Information Extraction Service > Profile
Maintenance.
3. On the Profile Overview screen, create a new entry, using the following
parameters:
Profile ID
Technical ID of the profile.
Profile Description
Enter the description of the profile.
Scenario
Assign the scenario.
Version
Assign version of scenario.
Note: For Incoming Supplier Invoice and Incoming Order scenarios

a scenario version 2 exists which uses Business Entity Determination
by default.
Scenario Description
Description of the scenario.
Render Pages
Activate Render Pages to retrieve rendered images and thumbnails for all
pages of a document from the extraction engine. This option needs to be
enabled if the Fiori Capture Validation Widget is used.
Extraction class
Enter the user exit class to implement additional logic that changes the
extraction or validation result. The user exit class implements the interface /
OTX/PF11_IF_HANDLE_RESULT.
Methods of interface /OTX/PF11_IF_HANDLE_RESULT:

PROCESS_EXTRACTION_RESULT
Provides the extraction result. The method is called for each extraction
step.

PI_REGID Importing Registration Id
PI_PROFILE_ID Importing Profile Id


PI_SCENARIO_ID Importing Scenario Id
PI_VERSION Importing Scenario version
PI_STEP Importing Scenario step
PIT_EXTRACTION_RES Importing Extraction result
ULT
PROCESS_VALIDATION_RESULT
Provides the validation result. The method is called for each extraction
step.
Parameter Type
PI_REGID Importing
PI_PROFILE_ID Importing
PI_SCENARIO_ID Importing
PI_VERSION Importing
PI_STEP Importing
PIT_EXTRACTION_RESULT Importing
FORMAT_EXTRACTION_VALUE
Formats the extraction value for each field. The method is called for
each extraction step for each field of type string, date and decimal. You
can change the VALUE of one field (defined with its ID) within the PCS_
EXTRACTION_RESULT structure and access all relevant information of the
whole extraction result within PIT_EXTRACTION_RESULT.

ULT
PCS_EXTRACTION_RE Changing Extraction result field
SULT
FORMAT_VALIDATION_VALUE
Formats the extraction value for each field. The method is called for
each validation step for each field of type string, date and decimal. You
can change the VALUE of one field (defined with its ID) within the PCS_

EXTRACTION_RESULT structure and access all relevant information of the

whole extraction result within PIT_EXTRACTION_RESULT.

ULT
PCS_EXTRACTION_RE Changing Extraction result field
SULT
Caution
• Only the VALUE field of PCS_EXTRACTION_RESULT structure
is processed.
• The value can only be reformatted. A new value no matter
if it is with or without relation to the document and the
extracted raw value is not learned.
• Write the VALUE according to the field types (date, decimal,

string) with the correct internal SAP format, for example:
– type decimal = 3232112.12

– type date = 20181228 (format YYYYMMDD)
Extract first Pages

IES can stop the extraction after a defined amount of pages. Enter the
number of pages which you want to extract. By default this parameter is not
active and full text recognition is done for all pages and relevant data fields
are extracted on these pages.
Single Click Entry (SCE) can only work for documents with fulltext which
may not exceed a certain number of pages. The useful limitation is a value
below internal recognition timeout, that is 60 minutes per document.
Tip: By using Extract first Pages and Extract last Pages together, IES
can read the first pages as well as the last pages of a document. This
will skip the middle part of long documents.
Extract last Pages
IES can also be instructed to read a limited amount of pages at the end of
the document. Here, only the defined amount of pages, beginning from the
end of the document, are extracted. Enter the number of pages which

should get extracted. By default this parameter is not active and full text
recognition is done for all pages and also relevant data fields are extracted
on these pages.
Use PDF e-Text
Uses the e-text from a searchable PDF. The following options are available:
• Ignore (OCR from image):: PDF files are transformed to tiff, regardless
if they are a searchable PDF or not. OCR recognition extracts the data
only from the image, without using e-text.
• Consider (OCR from image voted with e-text): PDF files are
transformed to tiff. e-text is preserved. OCR recognition extracts the data
from the image. The extraction result is rated with e-text. The priority is
OCR data, e-text is just used for supporting OCR.
• Prefer (OCR from e-text or image): PDF files are analyzed page by page:
for pages where e-text is available, OCR recognition is skipped and e-
text is used. Only for pages where no e-text exists, a tif is created and
OCR recognition extracts data from image.
5.2.3.3 Copying a profile

To copy an existing profile and all its dependent settings to a new profile:
2. Click Inbound Configuration > Capture Information Extraction Service >

Copy Profiles.
3. Define the source profile and click enter.

The scenario and the scenario version of the source profile is now displayed.
4. Define the name of the target profile.

The target profile ID must be unique and must not exist.
If you copy a profile, you cannot change the scenario. The scenario version of
the source profile is reused by default for the target profile. But you can specify
a different scenario version manually.

5.2.3.4 Defining custom entity determination fields

You configure custom extraction attribute fields. These fields are used to determine
business entity candidates.
To configure attribute fields

Maintenance.
3. On the Profile Overview screen, double-click Entity Determination Fields in

4. On the Entity Determination Fields Overview screen, maintain new fields,

using the following parameters:
Attribute field
Technical ID of the attribute extraction input field.
Description
Enter a description of the custom field.
Type
Select the field type from the list. The following values are possible:
• – address: Recognizes all addresses and returns a structure with the

following fields:
○ Name1
○ Name2
○ Street
○ House number
○ ZIPCode
○ POBox
○ City
○ Region
○ Country
– email: Extracts a list of all available email addresses.
– iban_number: Extracts a list of all iban numbers of a specific format
with checksum processing.
– range: Extracts a list of all numbers within the provided range.

– entity_matcher: Accesses the entities provided as a list by matching

their attributes against the document. Returns the best matching
entities with confidence as a structured set of data.
– attribute_extractor: Extracts entity attributes from the document as a
structured set via learning.
– tax_number: Extracts a list of all available tax numbers of a specific
format.
– url: Extracts a list of all available URLs.
Attribute field exit

Enter the user exit class to implement logic for specific field types. The user
exit class implements the /OTX/PF11_IF_ENTITY_ATTRMethods interface of
the /OTX/PF11_IF_ENTITY_ATTR interface:
• SET_RANGE_PARAMETER: Sets the parameter for ranges and the type of

the range. This method must be implemented for attribute fields of
range type.

PI_PROFILE_ID Importing Document Profile Id
PI_SCENARIO_ID Importing Document Scenario ID
PET_RANGE Exporting Range
PE_CATEGORY Exporting Category of Range
• SET_ADDRESS_PARAMETER: Sets the category of an address parameter

which identifies the address type. This method must be implemented for
attribute fields of address type.

PI_PROFILE_ID Importing Document Profile Id
PI_SCENARIO_ID Importing Document Scenario ID
PE_CATEGORY Exporting Category of Address
• SET_MATCH_PARAMETER: Sets the attributes which are used to extract the

business entity and additional information. The keys are extracted from
the document based on the canditate keys that are provided within the
lookup. This method must be implemented for the attribute fields of the
entity_matcher.

PI_PROFILE_ID Importing Document profile Id
PI_SCENARIO_ID Importing Document scenario ID


PI_SNAPMATCH_STRUC Importing Data structure of the
entity matcher field
PIT_CANDIDATE Importing Computed candidate keys
PIS_LEARNED Importing Learned candidate with
feedback
PET_SNAPMATCH Exporting Table of business entity
candidates with attributes
PE_CATEGORY Exporting Category of matcher
• SET_MATCH_RESULT: Sets the final business entity key after the

extraction. This method must be implemented for attribute fields of
entity_matcher.

PI_PROFILE_ID Importing Document profile ID
PI_SNAPMATCH_FIELD Importing Field name of the entity
matcher extraction field
PI_SNAPMATCH_PATH Importing Path for the entity
matcher extraction field
in the extraction result
PIT_SNAPMATCH_RESULT Importing Result of the entity
matcher
PIT_EXTDATA Importing Data extraction result
PIS_LEARNED Importing Learned candidate with
feedback
PC_ENTITY_VALUE Changing Determined business
entity key
• SET_MATCH_FEEDBACK: Sets the feedback attributes for the related

business entity key. You determine the same attributes when you use
the SET_MATCH_PARAMETER method of one business entity. This method
must be implemented for attribute fields of entity_matcher.
• SET_LOOKUP_VALUES: Sets the values that are used for the lookup.

PI_PROFILE_ID Importing Document profile Id
PI_LOOKUP_FIELD Importing LookUp fieldname
PI_ATTRIBUTE_FIELD Importing Attribute field


PI_ATTRIBUTE_PATH Importing Attribute field path in the
extraction result
PIT_EXTDATA Importing Data extraction result
PCT_VALUE_LIST Changing Values for the database
lookup
Entity matcher data structure

Data structure to set the fields for the entity candidates for the parameter in
the exit implementation of /OTX/PF11_IF_ENTITY_ATTR=>SET_MATCH_
PARAMETER. See /OTX/PF11_S_MATCH example structure - include /OTX/
PF11_S_MATCH_KEY is required for a custom structure.
5.2.3.5 Assigning an entity determination field

You assign custom extraction attribute fields in the profile of the related profile
extraction step. The custom extraction attribute fields are used in the business entity
determination of the candidates. For more information, see “Maintaining the
LookUp condition” on page 128.
To assign attribute fields:

Maintenance.
3. On the Profile Overview screen, mark an entry.
4. In the dialog structure, double-click Entity Determination Field Assignment.
5. On the Entity Determination Field Assignment screen, assign a field using the
Step
Extraction step when the field is used. It is usually set to step 1. only for the
fields of entity_matcher type step 2 setting is used.
Attribute field
Select the custom attribute field which is used in the scenario.
Note: You cannot update an activated profile if you change the type of a
field.
Update an activated profile, if you add or delete existing entity
determination fields. The changes take effect after the update.

5.2.3.6 Assigning an entity determination

You can use and assign your own business entity determination within the profile. If
you configure an own determination for a business entity field scenario , the
scenario related determination will not be processed.
To assign a determination to an entity field:

Maintenance.
4. In the dialog structure, double-click Entity Determination Assignment.
5. On the Entity Determination Assignment, enter the following parameters:
Entity field
Select the business entity field which is available in the related search help
(scenario or custom field of business_entity type).
Determination ID
Select the configured determination ID which is available in the related
search help. For more information, see “Information Extraction Service”
on page 99.
Note: Update an activated profile, if you add or delete existing entity

determination fields. The changes take effect after the update.
5.2.3.7 Maintaining format interpretation

You can customize the preferred format interpretation for a profile. This impacts the
document extraction within IES as well as the behavior of the Validation Cient.
The configuration of the format interpretation list allows to change the classifier.
Note: When changing character sets, a profile reset is necessary, which means
that learning data will get lost.
When changing a sequence of format interpretation for languages supported

by the same character set, a reset of the profile is not required and learning
data are preserved.
The following classifiers are available:

OCR character sets Supported Languages

International Afrikaans, Danish, Dutch, English, Finnish,
French, German, Icelandic, Indonesian,
Italian, Luxembourgish, Norwegian,
Portuguese, Spanish, Swedish. Albanian,
Bosnian(Latin), Croatioan, Czech, English,
Hungarian, Polish, Romanian, Serbian
(Latin) Slovak, Slovenian, Estonian, Latvian,
Lithuanian Azeri (Latin), Turkish, Uzbek
(Latin)
Cyrillic Azeri (Cyrillic), Belarussian, Bosnian
(Cyrillic), Bulgarian, Kazakh, Kyrgyz,
Macedonian, Russian, Serbian, Tajik,
Ukrainian, Uzbek (Cyrillic), English
Greek Greek, English
China Mainland, China Traditional Simplified Chinese, Traditional Chinese,
English
Japanese Japanese, English
Korean Korean, English
Thai Thai, English
To configure format interpretation:
> Capture > Information Extraction Service > Profile maintenance.
3. On the Profile Overview screen, mark an entry, and then double-click Format
interpretation list in the Dialog Structure.
4. On the Format interpretation list Overview screen, rank the preferred format
interpretation keys, using the following parameters:
Int. key
Interpretation key. Key for format interpretation, for example de-DE.
Sequence
Use the sequence to rank format interpretation. The format interpretation
with the lowest sequence number has highest priority.
Note: The value help for the interpretation key also shows the default
sequence for format interpretation. If no format interpretation is defined
for a profile, this default ranking is used.
If you change format interpretation after a profile is activated, you must
update the profile for the changes to take effect.

5.2.3.8 Maintaining classifications

You can configure a classification which is used for a specific custom field of the
type class.
Use a classification either for a document classification or to classify one document

with a specific attribute (for example, the priority).
The attribute classification can get configured for a custom field or a custom table
field. For the attribute classification values are configured. These classification
values are available within the windows Validation Cient for the custom field. IES
learns the classification after a user validated the document. An attribute of an
document for a classification can for example be the priority or special qualification
of a single line item for example for an invoice where a line represents the freight
costs.
For more information about document classification, see:
• “Defining custom fields” on page 141

• “Defining custom table fields” on page 144
• “Document classification“ on page 471
To configure a classification:
4. In the Dialog Structure, double-click Classification.
5. On the Classification list Overview screen, maintain the classification details,

Classification ID
ID of the classification.
Classification Profile
The classification profile ID is only relevant for document classification. It
represents the ID of the scenario classification. For more information, see
“Creating scenario classifications” on page 56 and “Document
classification“ on page 471.
Document classification does not require classification values as the
assigned document types of the scenario classification are used. For more
information, see “Assigning document types to classifications” on page 57.
6. On the Classification values: Overview screen, define classification values.


Value
Value of the classification.
Description
Description of the classification value.
5.2.3.9 Maintaining validation field settings

If you want to change the standard behavior of the fields, you customize the type
and the label of fields in the Validation Cient.
If an attribute is not defined for a field (description, field status, field sequence) the
default attribute value is used.
To maintain validation field settings:
3. On the Profile Overview screen, mark an entry, and then double-

click Validation field settings in the Dialog Structure.
4. On the Validation field settings Overview screen, define validation fields that
should appear in the Validation Cient, using the following parameters.
Note: If you change validation field settings you have to close the
application in validation and open it again for the changes to take effect.
Validation Fieldname
Select the validation field name from the list of available fields.
Description
Enter a description for the field. This text is used as label for the field in the
Validation Cient.
Fld. stat.
Field status. Select the field status from the list. The following values are
possible:
Display Only
Field is not editable.
Hide
Field is not displayed.
Input
Field is editable.
Required
Field is editable and indicated as required.

Fld. Sequ.
Validation Field sequence. Enter the sequence in which the fields are
displayed in the Validation Cient. The standard scenario fields always have
a sequence with 10 (10, 20, 30). Therefore, you can place custom fields in
between.
Sum Check Field
Enter the fieldname of the header field to do a sum check. The Validation
Cient will sum up the related item field and check against the sum field.
When the item sum does not match the sum field an error is shown in the
Validation Cient.Use the search field to select the sum check fieldname. You
can configure a scenario or a custom field. The sum check is only processed
in the windows Validation Cient.
Note: Make sure that you only configure fields where a sum check
makes sense (for example, amount fields). Also ensure that you assign
a header field to the Sum Check field and not an item field (sum check
field is always the related total field). Incorrect configuration result in
a wrong calculation on the Validation Cient.
5.2.3.10 Defining custom fields

In addition to standard scenario extraction fields, you can define custom extraction
fields. Machine learning is also available for these fields.
To define custom fields:

3. On the Profile Overview screen, mark an entry, and then, in the Dialog
Structure, double-click Custom field definition.
4. On the Custom field definition Overview screen, define custom fields, using
Name
Technical ID of the custom field. The technical ID should not contain any
special characters and no blanks.
Description
Enter a description of the custom field. This text is used as label for the field
in the Validation Client.
Type
date
Structured field, which supports typical date structures for the
supported languages. The structure depends on the settings of the

format interpretation list. For example, ddmmyyyy, mmddyyyy or

month in letters.
decimal
Field which supports up to 4 decimals, and which interprets data in
regards to the settings of the format interpretation list. The format
interpretation list defines the correct interpretation of thousand and
decimal separators (“.” or “,” ).
string
Field which has no normalization.
string_list
Field which contains a list of strings of similar format.
amount
Special decimal field which is limited to two decimals. It interprets data
in regards to the settings of the format interpretation list. The format
inperpretation list defines the correct interpretation of thousand and
decimal separators.
currency
Special string field which identifies supported currencies and currency
symbols on the document. It normalizes the data to ISO names for
supported currencies.
business_entity
Field that determines the business entity which is related to the
document layout.
class
Field which is used to process the document classification or to classify
a field with a specific attribute which is not available on the document.
Document classification is only possible on header level. For more
information, see:
• “Document classification“ on page 471

• “Maintaining classifications” on page 139
barcode
Field which is used to maintain the barcode type. It contains a list of
barcodes of the same type.
The following barcodes are supported:
• A2of5
• Aztec
• BCC32
• Codabar
• Code128

• Code2of5
• Code3of9
• Code3of9Extended
• Code3ofNOSS
• Code93
• CodeQR
• DataMatrix
• EAN13
• EAN8
• FourState
• I2of5
• Matrix2of5
• PDF417
• Patch
• Planet
• Postnet
• UCC128
• UPCA
• UPCE
Fld. stat.
Validation Field Status. Select the field status for the Validation Cient from
the list. The following values are possible:
Display Only
Hide
Input
Field is editable.
Required
Classification ID
Select the classification ID for the field type class which configure when you
maintain classifications. For more information, see:

LookUp ID
Select the look-up ID for the field type class which you configured. The
related look-up is used within the Validation Cient to search for the
business entity.
Fld. Sequ.
Validation Field Sequence. Enter the sequence in which the fields are
between.
Barcode Type
Select the barcode type for the field type barcode which you configured.
Note: If you add or delete existing custom fields after a profile is

activated, you must update the profile for the changes to take effect. You
cannot update an activated profile if you change the type of a field. If you
change the validation field settings of custom fields, close the application
in validation and open it again to apply the changes.
5.2.3.11 Defining custom table fields

In addition to standard scenario extraction fields, you can define custom extraction
table fields. Machine learning is also available for these fields.
To define custom fields:
3. On the Table for custom fields Overview screen, select the table you want to
enhance with custom fields, and then in the Dialog Structure, double-
click Custom field definition.
Important
Only choose a table which is provided with the search help.
4. On the Custom table field definition: Overview screen, define custom fields,
Name
Technical ID of the custom field. The technical ID should not contain any
special characters and no blanks.
Description
Enter a description of the custom field. This text is used as label for the field
in the Validation Client.

Type
date
Structured field, which supports typical date structures for the
supported languages. The structure depends on the settings of the
format interpretation list. For example, ddmmyyyy, mmddyyyy or
month in letters.
decimal
Field which supports up to 4 decimals, and which interprets data in
regards to the settings of the format interpretation list. The format
interpretation list defines the correct interpretation of thousand and
decimal separators (“.” or “,” ).
string
Field which has no normalization.
amount
Special decimal field which is limited to two decimals. It interprets data
in regards to the settings of the format interpretation list. The format
inperpretation list defines the correct interpretation of thousand and
decimal separators.
class
Field which is used to process the document classification or to classify
a field with a specific attribute which is not available on the document.
Document classification is only possible on header level. For more
information, see “Document classification“ on page 471.
description
Field which has no normalization. Provides the best capture result for
longer description texts within a column.
Fld. stat.
Validation Field Status. Select the field status for the Validation Cient from
the list. The following values are possible:
Display Only
Hide
Input
Field is editable.
Required
Classification ID
Select the classification ID for the field type class which configure when you
maintain classifications. For more information, see “Maintaining
classifications” on page 139.

LookUp ID
Select the look-up ID for the field type class which you configured when
you maintain classifications. For more information, see “Maintaining
classifications” on page 139.
Fld. Sequ.
Validation Field Sequence. Enter the sequence in which the fields are
between.
Sum Check Field
Enter the fieldname of the header field to do a sum check. The Validation
Cient will sum up the related item field and check against the sum field.
When the item sum does not match the sum field an error is shown in the
Validation Cient. Use the search field to select the sum check fieldname.
You can configure a scenario or a custom field. The sum check is only
processed in the Microsoft Windows Validation Cient.
Note: Make sure that you only configure fields where a sum check
makes sense, for example amount fields. Also ensure that you assign a
header field to the Sum Check field and not an item field (sum check
field is always the related total field). Incorrect configuration result in
a wrong calculation on the Validation Cient.
Note: If you add or delete existing custom fields after a profile is

activated, you must update the profile for the changes to take effect. You
cannot update an activated profile, if you change the type of a field.
If you change validation field settings of custom table fields, close the
application in validation and open it again to apply the changes.
5.2.3.12 Assigning an ArchiveLink document type

To assign an ArchiveLink document type to a profile:

3. On the Profile Overview screen, in the Dialog Structure, ´double-
click Document Type Assignment.
4. On the Document Type Assignment Overview screen, maintain the
assignment of document types to a profile, using the following parameters:
Doc. type
ArchiveLink document type
Profile Id
Enter the technical ID of a profile which should be used for extraction.

Note: The following parameters depend on the Profile ID and the

scenario: Description, Scenario, Version, and Description. For more
information, see “Creating a profile” on page 129.
If the ArchiveLink document type is not assigned to a profile (or is
deleted), the documents get into error status within inbound
processing and they are not available in the windows Validation Cient
for validation.
5.2.3.13 Activating and updating a profile

Profile activation is mandatory to use a profile for extraction on an SAP system. By
activating a profile, the relevant profile settings are transferred from SAP to IES and
its repository.
Profile update is mandatory to activate the changed profile settings of an activated

and running profile. By updating a profile, the relevant profile settings are
transferred from SAP to IES and its repository.
The option to update a profile is only available if the settings of a profile that is
configured using Profile maintenance activity changed since the last profile
update or profile activation.
To delete a profile setting and all its learning data from the IES repository, you can
reset a profile.
Tip: The profile reset cannot be reverted.
You are only allowed to reset the profile if there are no active sessions for this
profile. You can check for active sessions using the Extraction node in the IES
Administration Work Center in the Business Center Workplace. Furthermore all
processes for inbound documents which are using this profile have to be finished or
cancelled before resetting the profile.
Note: The profile activation and update is processed within the IES
Administration workcenter of the Business Center Workplace. In order to
process this task the relevant authorization for the workplace is required. For
more information, see “Authorization objects” on page 265.
To activate a profile:

> Capture > Information Extraction Service > Profile activation.
In the overview table of the IES Administration, all configured profiles are
listed. Newly created profiles are in status Inactive.
3. To activate a profile, click the Activate profile button in the Action column
of the profile.

4. Select the corresponding connection ID. For more information, see “On-
Premises: Connection parameters” on page 117. You must assign a dedicated
IES server to a profile.
After initiating the activation, the profile is in status Activation in process.
Profile activation usually takes a few seconds.
5. To check if the activation is completed, click the Refresh button in the
application toolbar. The status is Active. If a problem occurred during
activation, the status is Error.
In this case, you can display details about the problem by showing the Error
Log in the Detail pane.
To update a profile:

listed. Active profiles are in status Active.
3. In the Action column, click the Update profile button.
After initiating the update, the profile is in status Activation in process.
Profile update usually takes a few seconds.
4. To check if the update is completed, click the Refresh button in the application
toolbar.
The status switches to Active.
If a problem occurred during activation, the status is Error. In this case, you can
display details about the problem by showing the Error Log in the Detail pane.
Notes
• To get a list with all activities for a profile, display the Detail pane and show
the Activity Log.
• In case of errors, check the log for details in the detail pane and solve the root
cause. After that you can reset the profile using the Reset profile button
and try to activate again.
• You change the connection ID of an active profile using the Change
Connection button in the toolbar.
To reset a profile:

listed.

Active profiles are in status Active.

3. Select the profile that you want tor reset, and then click the Reset profile button
in the toolbar.
4. Confirm the reset.
Note: Profile reset usually takes a few seconds. The profile is in

status Reset in progress.
5. Optional To check if the reset is completed, click the Refresh button in the
application toolbar.
The status switches to Reset.
If a problem occurs, the status is Error. In this case, you can display details
about the problem by showing the Error Log in the Detail pane.
5.2.4 Accessing OCR full text

You cannot additionally script on the capture side, when using an IES integration.
You find various exits and enhancement options withing Inbound Configuration or
Process Configuration of SAP.
Use the /OTX/PF02_CL_UTILITIES=>GET_FULLTEXT static method to access the full

text of the extracted document to integrate additional logic. If you implement this
method within the inbound configuration, you provide the registration key. If you
implement the method within the process configuration, you provide the process
keys.

PI_REGID Importing Registration ID if called within
inbound (optional)
PI_PROJECT_ID Importing Profile of process if called within
process (optional)
PI_PLKEY Importing Process key if called within proces
(optional)
PET_FULLTEXT Exporting Full text for each page as string
with CRLF identifier.

5.3 Customizing validation

The Validation Client is the user interface for data completion and manual data
entry. All user actions contribute to the continuous learning process. You can use the
client itself on an unlimited number of workstations.
The Validation Client provides functions for easy data capture:
• With Single Click Entry (SCE), you can pick the data directly from the image into
the data fields. You do not need to type the data. This avoids errors due to typos.
• With Table Auto Completion (TAC), you only need to pick the data of the first
item line with Single Click Entry (SCE). Table Auto Completion (TAC)
automatically captures the data of all remaining line items.
The image view highlights all data that has been recognized automatically and the
user can see at first glance if data is missing, for example line items.
The validation framework determines whether a document that is captured needs

validation or not. The validation framework also assigns the validation agents to
validate the document. The framework bases on the customizing defined for the
ArchiveLink document type associated with the captured document.
5.3.1 Creating a validation

You can customize if and when an incoming document is validated. The validation
can always be active or only if defined check fields have no values. You can also
define who must manually validate the document.
To create a validation:

> Capture > Validation.
3. In the Capture - Validation Overview screen, configure general validation
settings, using the following parameters:
Validation ID
Technical ID of the validation settings
Description
Enter the description of the validation setting.
Validation Determination
Select the determination from the list. The following values are possible:
Validate always
Validation is always active.
Validate never
Validation is not active.

5.3. Customizing validation
Validate for selected fields

If check fields are missing, validation is run. For more information, see
“Maintaining validation check fields” on page 151.
Validation / Agent Determination

Use this function to control when the validation is run, and also to
determine the validator. Use template function /OTX/PF01_UTIL_EXIT_
VAL_DETERM to create a custom logic.
5.3.2 Maintaining validation check fields

For the validation setting Validate for selected fields, you can customize the
external field names.
To configure validation check fields:
> Capture > Validation.
3. In the Capture - Validation Overview screen, mark an entry, and then double-
click Capture - Validation Check Fields in the Dialog Structure.
4. In the Capture - Validation Check Fields Overview screen, configure check

fields, using the following parameters:
Step ID
Field counter
External Field Name

External field name for the scenario.
Note: You must configure the field name in the same way as it is
delivered (case-sensitive).
IES Field Path for Table or List

The field is only relevant if you use IES for extraction.
Single header fields have to be set to ExtractionResult. All other fields
are specified by the complete path
Note: You must configure the field names and full paths in the same
way as it is delivered (case-sensitive).
Example 5-1: Configuration and result of Validation Check

The following configuration shows the possible configuration for an
extraction of an ínvoice. Four fields are extracted

Table 5-1: Capture – Validation Check Fields
St External Field Name IES Field Path for Table or List

ep
Id
1 PONumber ExtractionResult-PONumber
2 InvoiceNumber ExtractionResult
3 InvoiceAmountBlock-DocumentCurrency ExtractionResult
4 Amount ExtractionResult-Items
The result of a configuration can look as shown below. The fields that are
defined as check fields display the extracted values.
5.3.3 Assigning an ArchiveLink document type to a validation

You must assign the ArchiveLink document type used in the Early Archiving
registration to the validation ID. For more information, see “Customizing the early
archiving registration type” on page 63.
To assign the ArchiveLink document type to the validation ID:
> Capture > Validation Assignment.

5.3. Customizing validation
3. In the Capture - Validation DocType Assignment Overview screen, assign the

ArchiveLink document type to the validation ID, using the following
parameters:
Document type
ArchiveLink document type of registration
Validation ID
Enter the validation ID for processing. For more information, see
Validation ID on page 150.
5.3.4 Assigning an agent to an ArchiveLink document type

If validation is required for an ArchiveLink document type and you do not use a
custom logic to determine the validator, you must assign the corresponding agent to
the ArchiveLink document type.
Note: An agent which is assigned to validate documents must have a

authorization for object S_WFAR_OBJ with the corresonding ArchiveLink
document type.
To assign an agent to an ArchiveLink document type:
> Capture > Validation Assignment.
3. In the Capture - Validation DocType Assignment Overview screen, mark an

entry, and then double-click Capture - Validation Agent Assignment in the
Dialog Structure.
4. In the Capture - Validation Agent Assignment Overview screen, assign the

agent to the ArchiveLink document type, using the following parameters:
Document Type
ArchiveLink document type
Object Type
Enter the organizational object that must be configured. The following
objects are supported:
• Rule
• Organizational Unit
• Center
• Position
• Work Center
• User

Agent ID
Enter the corresponding agent ID for the related organizational object.
Note: The IDs of organizational object assignments might be different
across the system landscape. Therefore, the /OTX/PF01_ADM_VALA
transaction is available to adjust the values in test and production
systems. In general, production systems do not allow any
configuration changes. The transaction is protected against a special
administration authorization. For more information, see
“Authorizations” on page 224.
EvalPath
Maintain the evaluation path. A special evaluation path might be required
for specific object types. As long as no special evaluation path has been set
up, the standard evaluation path WF_ORGUS is always used.
5.4 Customizing feedback

The feedback function for BCC or IES is based on ArchiveLink document types and
predefined feedback points. For each process, feedback is only sent once. BCC or IES
then can use the provided feedback as input for learning.
To activate feedback for BCC or IES:

> Capture > Feedback.
3. In the Feedback Overview screen, activate feedback for document types, using
Document Type
Document type for which feedback shall be activated.
Step
Point of time when feedback should be provided. Possible values:
Validation
Feedback is sent directly after validation is finished.
For IES, it is required to set the feedback after validation, to get best
feedback results. Feedback at process end might not deliver all relevant
information (for example coordinates) required for the best feedback for
IES.
Caution
You must set the feedback after validation, for IES to get best
feedback results. Feedback at process end does not deliver all
relevant information (for example coordinates) that is required
for the best feedback for IES.

5.5. Creating reject reasons
Process end
Feedback is sent after the business process is finished.
Active
Select this check box to activate feedback.
5.5 Creating reject reasons

In validation, users can select a reason when they reject a document manually.
The reject reason is displayed in the document registration table /OTX/PF01_T_1REG.
To create reject reasons:
> Capture > Reject Reasons.
3. In the Capture - Reject Reasons Overview screen, configure reject reasons,

Reject Reason
Reason code of the rejection
Description
Enter the description of the reject reason.
5.6 Customizing look-ups

You can customize look-ups to provide the following features in the BCC or IES
application:
• Searching for any related SAP information in the Validation Cient. If IES is used
only custom fields of business_entity type can be defined with a look-up. For
more information, see “Defining custom fields” on page 141.
• Enabling the access and download of master data to the BCC or IES database. If
IES is used, only access, no download is enabled.
The look-up for business partners is done on staging tables. A staging table collects
all relevant information of vendor, customer, or company code. A staging table can
also collect information from multiple systems, when BCC or IES is connected to one
SAP ERP system as single point of contact.
The staging tables are filled with corresponding reports, which can be planned as
periodic job on SAP ERP side.
/OTX/PS00_P_IDF_COMP_CODE
Report to fill staging table for company codes

/OTX/PS00_P_IDF_CUSTOMER
Report to fill staging table for customers
/OTX/PS00_P_IDF_VENDOR
Report to fill staging table for vendors
For more information, see OpenText Vendor Invoice Management for SAP Solutions -
For more information from BCC side, see Section 4.10 “Configuring a Partner
function” in OpenText Business Center Capture for SAP Solutions - Customization Guide
(CPBC-CGD) and Section 4.12 “Configuring a LookupList function” in OpenText
Business Center Capture for SAP Solutions - Customization Guide (CPBC-CGD).
Look-up fields are used to map the SAP fields of the related data selection fields
structure to the external field names used in the Business Center Capture
application. For more information, see “To map a look-up field:“ on page 158.
To create a look-up:

> Capture > Look-up.
3. In the Look-up Overview screen, configure look-ups, using the following
parameters:
LookUp ID
Describes the technical identification of data search and retrieval in SAP
ERP.
Description
Enter a description of the look-up.
Data selection fields
Enter the structure of the fields. These fields are used within the mapping.
They assign the external field name of BCC or IES to the internal SAP field
name of the corresponding database table or database view. For more
information about the mapping, see “To map a look-up field:“ on page 158.
Source Table Name
Enter the database table or view used for the data retrieval.
Handler class
You can use the handler class to implement custom logic in your own
handler class for a look-up. The handler class needs to implement the /OTX/
PF01_IF_LOOKUP interface. If no custom handler class is configured, the
standard handler class /OTX/PF01_CL_INTERFACE_LOOKUP is called.
The standard class allows to search entries with selection criteria that is
concatenated by AND. All search criteria is character-based and used with
LIKE.

5.6. Customizing look-ups
The function has no special treatment for date or amount values.
Handler Class – The following methods are possible for a custom

implementation in the /OTX/PF01_IF_LOOKUP interface.
Note: The parameter naming in VIM follows the following rules:
1st Character
P fix, indicates a parameter.
2nd character
I (Importing) or C (Changing) or E (Exporting).
3rd character
<empty> (variable) or S (structure) or T (table).
LOOKUP_DOWNLOAD
The LOOKUP_DOWNLOAD method provides a look-up to download data.
This method is used in the BCC API function /OTX/PF01_IF_LOOKUP_
DOWNLOAD.

PIT_QUERY Importing Query attributes from BCC
application
PET_DATA Exporting Look-up result in csv-format
PET_FIELDS Exporting External look-up fields
PE_COMPLETE Exporting Parameter to indicate if all
possible entries have been
processed
PET_RETURN Exporting Return messages
PE_RC Exporting Return error code
LOOKUP_DOWNLOAD_INIT
The LOOKUP_DOWNLOAD_INIT method initializes the download.
This method is used in the BCC API function /OTX/PF01_IF_LOOKUP_INIT.

LOOKUP_DOWNLOAD_COMPLETE
The LOOKUP_DOWNLOAD_COMPLETE method completes the download.
This method is used in the BCC API function /OTX/PF01_IF_LOOKUP_
COMPLETE.


PI_COMPLETE Importing Parameter to indicate if all
processed
LOOKUP_VALIDATION
The LOOKUP_VALIDATION method provides a look-up processed from the
Validation Cient.
This method is used in the BCC / IES API function /OTX/PF01_IF_LOOKUP_
VAL.

PI_MAXHITS Importing Maximum number of hits
PIT_QUERY Importing Query attributes from BCC / IES
application
PET_DATA Exporting Look-up result in csv-format
PET_FIELDS Exporting External look-up fields
PE_COMPLETE Exporting Parameter to indicate if all
processed
PE_RC Exporting Return error code
5.7 Mapping a look-up field

To map a look-up field:

> Capture > Look-up.
3. In the Look-up Overview screen, mark an entry, and then double-click Look-up
Fields in the Dialog Structure.
4. In the Look-up Fields Overview screen, configure look-up fields, using the
External Field Name

Name of the field in the BCC or IES application
Field Name
Enter the name of the SAP field of the configured structure. For more
information, see Data selection fields on page 156

5.7. Mapping a look-up field
Case sens.
Case sensitivity. Select Case-sensitive or Case-invariant from the list.
BCC or IES already provides a search operation for a specific field. For
example, the user can enter search options in the Validation Client. You can
configure how this search is processed. Either the search is case-sensitive or
the search is case-invariant.
Tip: A case-invariant search is the slower search option.
Row number
Enter the column number to identify the related field in BCC or IES.
Index
Mark the index field of the look-up which identifies the business partner/
business entity.
Sort
Define the fields with sort criteria which show the details of the selected
business partner/business entity in the Validation Cient.
Element Name:
Field name of the mapped entity determination fields of the entity matcher
data structure. For more information, see “Defining custom entity
determination fields” on page 133.

Chapter 6
Process Foundation
The Process Foundation is a completely flexible framework to configure and run

processes. It is not a workflow engine but utilizes generic workflow definitions,
which are processed by the SAP Business Workflow engine.
The technical concept assumes that every task in the process will end with a result.
These possible results are defined by the content of single task modules. Linking one
task to another, depending on the result of the previous one, allows to create a
complete process flow.
How a single task of the process flow appears is determined by task types, for
example dialog or background task. You can further control the appearance by usual
concepts like requested start or end conditions and event handling capabilities.
Therefore, the Process Foundation allows an easy configuration of processes without
the need for complex development.
Per design, the Process Foundation does not contain any business data context or
business data processing logic. It expects that these are implemented by each
business scenario using suitable data models and processing modules, which are
executed during runtime. Therefore, the Process Foundation has to be considered as
a pure technical platform to simplify the use of SAP Business Workflow.
Important
The Process Foundation is reserved for internal use only. Any custom
configurations beside the activities described in this document are not

Chapter 6 Process Foundation
supported. With the standard delivery of the product, a pre-configured Process

Foundation profile PF_DEFAULT is delivered. It covers all processing aspects
required for any business scenario and must not be changed at any time.
To add business scenario related content to the generic process patterns, the product
offers the following concepts. They all are mandatory steps that must be performed:
• Data Model Configuration

• Process Foundation Profile Generation
• Data Model Assignment
• Definition and Assignment of a Process Configuration Profile
The definition and assignment of a business configuration profile is part of the

product component Process Configuration. It mainly focuses on how to map
complex business scenario requirements into meaningful business rules, agent roles,
process steps, and process actions. It finally focuses on how to create corresponding
SAP documents without the need to think about the technical background of the
SAP Business Workflow engine.
Important
You must configure the SAP Business Workflow engine to run processes based
on Process Foundation as prerequisite. Additionally, maintain the following
tasks as general tasks in the PFTC transaction:
• Workflow Template 00297300

• Workflow Template 00297330
• Standard Task 00297316
• Standard Task 00297303
6.1 Basic Settings

In this step, you configure basic settings for the Process Foundation.
To configure basic settings:
2. Click Process Foundation > Basic Settings.
3. In the Basic Settings Overview screen, configure basic settings, using the
Default Language
Enter the default language.
The default language is used to read description texts in some customizing
views. This applies if no description texts are found in the current logon

6.2. Data model configuration
language. Set the value to EN because this language is already included in

the standard delivery.
Default Profile
Enter the default profile.
The default profile entered here is used as a template when generating new
process foundation profiles. For more information, see “Process Foundation
profile” on page 172.
6.2 Data model configuration

The data model configuration defines process ledger tables and the relationship
between these tables. Usually a business scenario uses two data tables, one header
data and one item data table.
The following customizing steps are required to configure data models:
• Define data model

• Define levels
• Maintain level key fields
• Define external data mapping
• Assign mapping channel
Note: The data model configuration is used by an internal data handling API.
It automatically reads and writes data to the defined process ledger tables. You
must not perform any database updates manually without using this API. In
general, all usable or extendable interfaces in the product already offer the
corresponding process ledger data. This includes header and item data for use
or to be changed. The interfaces also automatically take care about updates
without the need to use any methods of the data handling API at any point of
time.
6.2.1 Defining a data model

In this step, you define a data model for a corresponding business scenario
implementation.
To define a data model:

2. Click Process Foundation > Data Model.
3. In the Data Model Configuration Overview screen, define the data model
Data Model ID
Define the data model ID, a 10 character unique ID.

Description
Enter a meaningful description to outline for which purpose the data model
is used.
Author
Enter the user name of the creator of the data model or the responsible
person.
Lock Object
Enter the lock object which has been created for the process header ledger
table. If no lock object is provided, no data lock is performed.
6.2.2 Defining levels

Within the level definition, the process ledger header and item tables are maintained
and assigned to data hierarchy levels.
Before you can define the levels, you must create the business scenario related data
tables. They must fulfill the following mandatory conditions:
Table 6-1: Mandatory key fields for the header table
Fieldname Data Element

MANDT MANDT
Mandatory include structures for the header table
• /OTX/PF02_S_PLH_DATA
• /OTX/PF04_S_BCF_DATA
Table 6-2: Mandatory key fields for the item table

MANDT MANDT
ITEM_NR /OTX/PF02_E_ITEM_NR
Table 6-3: Mandatory non-key fields for the item table

EXTINDEX /OTX/PF00_E_EXTINDEX

Note: When creating work object types based on data tables, always make
sure to include the key fields PROJECT_ID, PLKEY and (in case of item tables)
ITEM_NR in the table field list of the corresponding dynamic data selection.
Also make sure to include the non-key field EXTINDEX. For more information,
see “Defining dynamic data selection” on page 251.
To define levels:
1. In the Data Model Configuration Overview screen (see “Defining a data

model” on page 163), mark an entry, and then double-click Levels in the Dialog
Structure.
2. In the Levels Overview screen, define levels using the following parameters.
Data Hierarchy Level

Enter the hierarchy level to which a data table belongs. The following
hierarchy levels for the process ledger tables are available:
• 1 - Header table (mandatory)

• 2 - Item table (optional)
Note: Only the hierarchy levels 1 and 2 are supported by the product
standard. Higher hierarchy levels are generally possible using the
standard configuration. However, they are not provided anywhere in
the standard delivery.
Description
Enter a meaningful description for the data hierarchy level.
Table Name
Enter the name of the corresponding process ledger table to be used in the
hierarchy level.
External Field Name
Enter an external alias for the table used by external applications that send
data to the system. The external field name is required to determine the
internal SAP table name.
Note: This setting has been replaced by the level mapping
configuration. For more information, see “Maintaining level mapping”
on page 169. But the setting remains available for downward
compatibility reasons. As a consequence, no further evaluation of the
level mapping configuration takes place as long as any value is
maintained in the level definition setting.

6.2.3 Maintaining level key fields

The relationship between data hierarchy levels and the assigned process ledger
tables is established using the level key fields. Additionally these settings control
how to determine the key field values themselves.
To maintain level key fields:
1. In the Levels Overview screen (see “Defining levels” on page 164), mark an
entry, and then double-click Fields in the Dialog Structure.
2. In the Fields Overview screen, maintain the level key fields, using the following
parameters.
Field Name
Name of the key field of the process ledger table where data of the
corresponding hierarchy level is hold.
Key type
This parameter defines how the value of the key field is determined when
inserting new data entries. Select one of the possible values from the list:
Create key by number range object
The key field value is retrieved from a number range object. This only
makes sense within data hierarchy level 1 to generate the next unique
process ledger key.
Automatic indexing
The key field value is populated by sequential numbering using the
logic defined with the index parameter fields. This only makes sense for
numeric data types.
Timestamp
The key field value is determined by a timestamp. The field must be of
data type TIMESTAMP or TIMESTAMPL.
Key is self-managed by the requester
The key field value is managed by custom logic and already provided
when inserting values.
Object
Enter the name of the number range object used for the key field in case of
key type Create key by number range object.
Number range number
Enter the number range interval used for the key field in case of key type
Create key by number range object.
Important
The number range interval must be configured in the SNUM transaction
for number range object /OTX/PF02L (not delivered in BC set).
Maintain the number range 01 with the range 1 to 999999999999.

This number range object is used within the DEFAULT Data Model (also
used within solutions).
Subobject field in group table

Optional setting.
Enter the field name that contains the value of the sub-object to be used in
the number range object in case of key type Create key by number range
object.
Fieldname to-year
Optional setting.
Enter the field name that contains the value of the to-year to be used in the
number range object in case of key type Create key by number range
object.
Index start
Enter the first index value used for the key field in case of key type
Automatic indexing.
Index interval
Enter the Interval used for new key index determination for the key field in
case of key type Automatic indexing.
If a data entry already exists and the value of the highest index does not
apply to the interval definition, the next generated value is the next free one
of the interval.
Example 6-1: Index interval

Index Start = 10
Index Interval = 10
Existing entries are 10, 20, 30, and for example 37, then the next
generated index will be 40.
6.2.4 Defining external data mapping

External data mapping is used to map the attributes and values that are stored in
the /OTX/PF01_T_1EXT table or the /OTX/PF11_T_DEXT table intermediately to the
relevant business process ledger header and item table.
To define external data mapping:

model” on page 163), mark an entry, and then double-click External Data
Mapping in the Dialog Structure.
2. In the External Data Mapping Overview screen, define the external data
mapping using the following parameters:

Mapping ID
Unique technical ID which identifies the mapping scenario
Description
Enter a meaningful description for the mapping scenario.
Mapping Class
You can use this to implement custom logic in your own handler class for
the mapping. The handler class must implement the /OTX/PF20_IF_FIELD_
MAPPING interface. If no custom handler class is configured, the standard
handler class /OTX/PF02_CL_FIELD_MAPPING will be called.
Default
Select this check box for one mapping ID. To process different mapping for
different incoming channels, the mapping ID is assigned to an incoming
channel. If no assignment to a channel can be found, the default mapping is
processed. The default mapping usually maps the external fields one-to-one
to the internal ledger table fields.
Handler Class – The following methods are possible for a custom

implementation in the /OTX/PF20_IF_FIELD_MAPPING interface.
MAP_HEADER
This method maps external header fields (EXTINDEX = 1 in /OTX/PF01_T_
1EXT) to header table (Level = 1).
It is used for frame workflow processing in /OTX/PF02_CL_WORKFLOW ->
INIT_FRAMEWORKFLOW.

PI_PROJECT_ID Importing Process Foundation Profile ID
PI_PLKEY Importing Process ledger key
PI_UPDATE Importing Flag to indicate that update on database
table is done
PET_RETURN Exporting Return parameters in error case
PES_DATA Exporting Target structure with mapping result
MAP_ITEMS
This method maps external item fields (EXTINDEX = 2 to 999 in /OTX/PF01_
T_1EXT) to item table (Level = 2).
It is used for frame workflow processing in /OTX/PF02_CL_WORKFLOW ->
INIT_FRAMEWORKFLOW.

PI_PROJECT_ID Importing Process Foundation Profile ID
PI_PLKEY Importing Process ledger key


PI_INSERT Importing Flag to indicate that insert on database
table is done
PROCESS_MAPPING
This method is used for process mapping. It is called inside mapping class.

PIT_EXTDATA Importing External data values
PI_LVL Importing Data hierarchy level (see “Defining
levels” on page 164)
PI_CURRENCY Importing Currency to map currency fields
PET_INTDATA Exporting Mapping result
6.2.5 Maintaining level mapping

In this step, you define an external alias for each data level used by external
applications that send data to the system. The external field name is required to
determine the internal SAP table name behind each data level.
To maintain the level mapping:
1. In the External Data Mapping Overview screen (see “Defining external data
mapping” on page 167), mark an entry, and then double-click Level Mapping
in the Dialog Structure.
2. In the Level Mapping Overview screen, maintain the level mapping, using the
Data Hierarchy Level

Define the hierarchy level to which a data table belongs. The hierarchy level
identifies the corresponding target table (see “Defining levels” on page 164).
External Field Name

Enter the external alias for the level used by external applications that send
data to the system.
Note: You must configure the external field name for the level in the
same way as it is delivered (case-sensitive).

6.2.6 Maintaining field mapping

In this step, you map the external field names to the target ledger table fields.
To maintain the field mapping:
1. In the Level Mapping Overview screen (see “Defining external data mapping”
on page 167), mark an entry, and then double-click Field Mapping in the
Dialog Structure.
2. In the Field Mapping Overview screen, maintain the field mapping, using the
External Field Name

External alias for the field used by external applications that send data to
the system. You find the external field name in the /OTX/PF01_T_1EXT-
EXTFIELD table or the /OTX/PF11_T_DEXT-NAME table.
Note: You must configure the external field name in the same way as
it is delivered (case-sensitive).
Field Name
Enter the name of the table field in the ledger target table in the
corresponding data hierarchy level.
Currency Field
Select this check box to indicate a currency field.
Field Mapping Type

Enter the field mapping type. The mapping is processed according to the
mapping type. The following values are possible:
External Field with Conversion (SAP / Custom)

The field is mapped according the assignment of external and internal
field name. It takes the necessary conversion of the SAP field into
account. If a field conversion exit is configured, this exit is processed. If
no exit is configured, the standard SAP conversion is processed which
is assigned to the SAP field.
External Field without Conversion

The field is mapped according the assignment of external and internal
field name. It does not take the necessary conversion of the SAP field
into account.
Constant (fixed value)

A constant value is assigned to the target field. The value is configured
in the Value field (see Value on page 171).
System variable
A system variable is assigned to the target field. The value is configured
in the Value field (see Value on page 171).

Field Conversion Exit

Enter the field conversion exit. The exit is processed for field mapping type
External Field with Conversion (SAP / Custom). Use function /OTX/
PF20_UTIL_EXIT_FIELD_MAP as a template to create a custom exit.
Ignore Character
Enter characters that are deleted in an extra step before mapping continues.
This is useful, for example, if there are apostrophes in a Reference Number.
The field can contain up to 6 characters.
Condense
Select this check box to condense the value.
Value
For field mapping type constant or system variable, assign the related
value.
6.2.7 Assigning the mapping channel

In this step, you assign the mapping ID to a specific incoming document channel. If
no assignment is found, the default mapping is processed (see Default on page 168).
The following mapping IDs are delivered:
CAPTURE
Mapping for Business Center Capture application created before Business
Center Capture 16.5
CAPT_BCC
Mapping for Business Center Capture application created with Business Center
Capture 16.5 and later
CAPT_IES
Mapping for Information Extraction Service
According to your scenario, assign the corresponding mapping ID to the related

channel used in your registration scenario. For more information, see “Customizing
registration types” on page 62.
To assign the mapping channel:

model” on page 163), mark an entry, and then double-click Mapping Channel
Assignment in the Dialog Structure.
2. In the Mapping Channel Assignment Overview screen, assign the mapping ID
to the channel. using the following parameters.
Channel
Incoming channel in which the document has been processed. For more
information, see “Configuring channels” on page 55).

Mapping ID
Enter the unique technical ID which identifies the mapping scenario.
6.3 Process Foundation profile

Generating a Process Foundation profile is a mandatory technical step to assign a
configured business data model. There is a fixed one-to-one relationship between
the Process Foundation profile and the business data model.
Note: Each Process Foundation profile must be assigned to a scenario. During

generation of a Process Foundation profile, you must select the correct business
scenario that is used for this profile, for example Invoice or Sales Order. This
assignment is required for the correct license measurement.
To generate a Process Foundation profile:
2. Click Process Foundation > Generate Profiles.
Note: To run this activity, authorization for J_6NPF_ADM is needed. For

3. In the Generate Process Foundation Profiles screen, in the Generate profile

field, enter a suitable Process Foundation profile name to be generated. Make
sure the profile name does not exist yet. Click the Execute button.
Note: By default, a new profile is always generated using the template

profile PF_DEFAULT. You can control which profile is used as generation
template by the Default Profile parameter.
4. To change the the Default Profile parameter available in the basic settings of
the Process Foundation:
a. Run the /n/OTX/PF00_IMG transaction.

b. Click Process Foundation > Basic Settings. .
c. If you leave the parameter value empty, you can freely choose any existing
Process Foundation profile as a template for the generation of a new profile
To add generated profiles to a transport request:
1. Run the /n/OTX/PF00_IMG transaction
2. Click Process Foundation > Profiles.
3. Select the profile that you want to transport. Click Table View > Transport from
the menu and include all corresponding configuration settings in a transport
request.

6.4. Business data model assignment
Note: You must always manually add profile entries in the tables /OTX/
PF02_T_TBWD and /OTX/PF02_T_TBWT to a transport from the SE16
transaction.
6.4 Business data model assignment

The last step before starting to implement the detailed business scenario
requirements using the Process Configuration is to assign the configured business
data model to the generated Process Foundation profile.
To assign a business data model to a Process Foundation profile:
2. Click Process Foundation > Profiles.
3. In the Profile Configuration Overview screen, assign the configured business

data model ID to the generated Process Foundation profile, using the following
parameters:
Profile ID
ID of the Process Foundation profile
Data Model ID
Enter the name of the business data model containing the process ledger
header and item tables. This stores the business data of the corresponding
business scenario.

Chapter 7
Process Configuration
Process Configuration allows an easy and technically simplified configuration of

complex business scenario aspects. You do not have to consider any detailed SAP
Business Workflow related requirements. The following configuration aspects are
covered within Process Configuration:
• Profile configuration
• Profile assignment
7.1 Profile configuration

A profile within Process Configuration comprises the following definitions:
• which business rules must be checked for a business scenario
• which corresponding process steps should be executed

• which agent roles should execute them, using specific screen layouts and suitable
process actions
The profile configuration also offers versioning capabilities. This means, it allows
changing the defined business scenarios at any time without disrupting the already
running process instances in any way.

Chapter 7 Process Configuration
Note: Within the standard delivery, a simple dummy profile PC_DEFAULT is

delivered. This profile is independent from any business scenario data context.
It can be easily used to start and test example processes.
The following customizing steps are necessary to configure profiles:
• “Defining a profile” on page 176

• “Defining a profile version” on page 177
• “Defining actions” on page 186
• “Defining roles” on page 195
• “Configuring data enrichments” on page 197
• “Configuring the process split functionality” on page 203
• “Configuring characteristics” on page 208
• “Maintaining process steps” on page 209
7.1.1 Defining a profile

A profile is defined by a unique profile ID, a meaningful description, and a
responsible user name.
To define a profile:
2. Click Process Configuration > Profiles.
3. In the Profile Configuration Overview screen, define the profile using the
Profile ID
Define the profile with a unique ID.
Profile Description
Enter a meaningful profile description.
User
Enter the responsible person or creator for the profile.
To copy an existing profile and all its dependent settings to a different profile
name:
2. Click Process Configuration > Copy Profiles.
Note: To run this activity, authorization for J_6NPF_ADM is needed. For


7.1. Profile configuration
The copied version will always start with a first profile version again,
independent from the current version counter currently used by the copied
profile.
7.1.2 Defining a profile version

In this step, you define the main settings for a profile version and the characteristic
and Processing Screen settings. For each profile, there must be only one active
version at the same time.
To define a profile version:
3. In the Profile Configuration Overview screen, mark an entry, and then double-
click Version Definition.
4. In the Version Definition Details screen, define the version using the following
parameter.
Version
Next higher version counter
To generate a new version for an existing profile by reusing all already

available settings
Note: You can chang or enhanc the settings afterwards
2. Click Process Configuration > Create Profile Versions.
Note: To run this activity, an authorization for J_6NPF_ADM is needed. For

This will set the old version to inactive and copy all current settings to a new
active profile version automatically.
Note: To remain consistent, running processes will always continue to use

the profile version for which they have been started. This also applies if
the corresponding profile version has been set to inactive in the meantime
due to a newer active profile version. Therefore, it is not allowed to delete
profile versions from the configuration at any time.

7.1.2.1 Maintaining version settings

To maintain version settings:
• In the Version Definition Details screen (see “Defining a profile version”

on page 177), maintain the version settings, using the following parameters.
Version Description
Enter a meaningful description of the current profile version.
Active
Select this check box to set the version to active. Clear the check box to set
the version to inactive.
Creation Date
Enter the date when the version has been created.
Created by
Enter the responsible person or creator for the profile version.
Profile Class
Enter the profile class. The profile class contains the highest level profile
related processing logic that is required to execute a profile configuration
during runtime. If no class is maintained, the standard class /OTX/PF04_CL_
PROFILE is always used.
Default value: <Empty>
If the standard logic has to be changed for any reasons, the class /OTX/
PF04_CL_PROFILE must be inherited, redefined as needed, and entered as
custom profile class.
The following methods are supposed to be redefined if needed. OpenText
recommends that you do not change any other method.
AUTH_CHECK_DATA
This method implements custom authorization checks based on the
current characteristic value, process step, and process ledger data.
When executing dialog work items, the method is called for the
activities 02 - Change and 03 - Display.
If any authorization check fails, the exception /OTX/CX_PF04_
EXCEPTION has to be raised passing a suitable error message.
FINALIZE_PROCESSING
You can use this method to implement any finalization or data cleanup
activities at the end of the overall business process.
Data Class
Enter the data class. The data class is used during profile processing. It
handles read and write database accesses to the corresponding process
ledger header and item data tables. It also handles the determination of the
characteristic value. If no class is maintained, the standard class /OTX/
PF04_CL_DATA is always used.


PF04_CL_DATA must be inherited, redefined as needed, and entered as
custom data class.
The following method is supposed to be redefined if needed. OpenText
CHARACTERISTIC_EXIT
This method dynamically determines the characteristic value based on
the current process ledger data. This is necessary if the characteristic
value cannot be determined statically by a single process ledger header
table field value.
This method is used when writing data back to the process ledger
header table and during processing of a profile configuration.
The determined characteristic value is written back to the process
ledger header table field BCF_CHAR.
Analyt. Prof.
Analytics Profile. For analytic evaluations, data may need to be prepared on
the database. Enter the Analytics profile with profile type 1 - Process KPIs ,
if you want to trigger the update of Analytics database tables designed for
business processes. For details how to maintain an Analytics profile, see
“Configuring Analytics” on page 33.
7.1.2.2 Maintaining characteristic settings

To maintain characteristic settings:

on page 177), maintain the characteristic settings, using the following
parameter.
Characteristic Field (optional)

The characteristic might be represented statically by the current value of
just one single process ledger header table field during runtime. In this case,
you can maintain the table field name here. All available process ledger
header table fields can be used, except the characteristic field BCF_CHAR
itself. The BCF_CHAR field always must store the latest determined value.
Note: As soon as a static process ledger header table field is
maintained, no dynamic characteristic determination using the
method CHARACTERISTIC_EXIT of the class /OTX/PF04_CL_DATA takes
place anymore.

7.1.2.3 Maintaining Processing Screen settings

The Processing Screen is called when executing process steps in dialog. The
Processing Screen offers the corresponding business scenario related index data. It
also offers suitable process actions and further scenario or related data context
information. This is required to resolve issues represented by a dialog process step
in a fast and flexible way.
You can control the basic technical functionality of the Processing Screen and its
different screen areas by maintaining the Processing Screen settings described in this
section.
Important
To use the Processing Screen in a proper way, a minimum screen resolution of
1600 x 900 is required.
The following screen areas are available and together form the overall appearance of
the Processing Screen during runtime:
Action Pane
The action pane integrates all process actions that have been configured for an
agent role. These process actions are available for a combination of the current
characteristic value (if applicable) and the process step. Each process action is
represented by a separate action button.
A maximum of 20 process actions is allowed. They are displayed by 5 action
button rows consisting of 4 action buttons each. The arrangement of the buttons

starts in row 1 and takes place from left to right using the process action
sequence as maintained in the action assignment configuration. For more
information, see “Defining actions” on page 186. As soon as a button row
exceeds the limit of 4 action buttons, the next row is populated.
Info Pane
The info pane displays all check results of the business rules assigned to the
current agent role, characteristic value (if applicable), and process step.
The rule check status is visualized by an indicator light icon in combination with
the return messages of the check. The first check result message is displayed
directly in the info pane area overview. All further check messages can be
displayed by clicking on the message line hyperlink.
Detail Pane
In the detail pane area, additional process data context information is displayed.
The detail pane uses the processing plug-in concept. For more information, see
“Configuring plug-in integration” on page 24.
Tab Strip Area
Within the tab strip area, the index data itself is displayed. It is grouped into
several meaningful tab strip sections. Each tab strip allows calling a custom sub
screen containing the corresponding business scenario related index data fields.
Depending on the related business scenario, the index data fields can be
completely different.
You can activate a maximum of 6 different tab strip sections. Tab strips that have
not been activated will not be displayed during runtime.
To maintain Processing Screen settings:

on page 177), maintain the Processing Screen settings, using the following
parameters.
Main Class
Enter the main class. The main Processing Screen class contains all logic
required for the screen processing. If no class is maintained, the standard
class /OTX/PF40_CL_IDX_SCREEN is always used.
PF40_CL_IDX_SCREEN must be inherited, redefined as needed, and entered
as custom Processing Screen class.
Note: A redefinition of the main class is not required.
Sub Class
Enter the subclass. The Processing Screen subclass contains all logic for the
subscreen processing. Copy the general class /OTX/PF41_CL_IDX_
SUBSCREEN, enhance it with business scenario specific logic, and enter it as
Processing Screen subclass.

Note: An inheritance of the general class is not possible because the

associated types of the following class attributes must be replaced
with suitable types that are business-scenario specific:
• MS_HEAD
• MT_ITEM
• MS_ITEM
• MT_ITEM_TCTRL
• MS_ITEM_TCTRL
The attribute names themselves must remain unchanged.
Action Pane Class

Enter the action pane class. This class provides the integration and handling
of process actions into the action pane. If no class is maintained, the
standard class /OTX/PF40_CL_ACTION_PANE is always used.
If the standard logic must be changed for any reasons, the class /OTX/PF40_
CL_ACTION_PANE must be inherited, redefined as needed, and entered as
custom action pane class.
Note: In general, no redefinition of the action pane class is required.
Info Pane Class

Enter the info pane class. This class handles the integration of the business
rule check results into the info pane. If no class is maintained, the standard
class /OTX/PF40_CL_INFO_PANE is always used.
CL_INFO_PANE must be inherited, redefined as needed, and entered as
custom info pane class.
Note: In general, no redefinition of the info pane class is required.
Tab Strip Class

Enter the tab strip class. This class handles the integration of the tab strip
control into the main index data tab strip area. If no class is maintained, the
standard class /OTX/PF40_CL_TABSTRIP is always used.
CL_TABSTRIP must be inherited, redefined as needed, and entered as
custom tab strip class.
Note: In general, no redefinition of the tab strip class is required.

Field Handl. Class

Enter the field handler class. This class handles the general availability and
the input status of the business scenario related Processing Screen data
fields. If no class is maintained, the standard class /OTX/PF40_CL_FLD_
HANDLER is always used.
The maintained field settings determine whether a screen field is available
and what the field input status should be for a combination of current agent
role, characteristic value, and process step.
CL_FLD_HANDLER must be inherited, redefined as needed, and entered as
custom field handler class.
FIELD_STATUS_HEAD_SET
This method sets the screen field status of business scenario related
index header data fields.
This method has to be called in the PBO module of every business
scenario related tab strip header data sub screen.
FIELD_STATUS_ITEM_SET
This method sets the screen field status of business scenario related
index item data fields.
This method has to be called in the PBO module of every business
scenario related tab strip item data sub screen.

PCS_TAB_CONTROL Changing Table control containing the
current item field list
display
Note: The field handler class method FIELD_STATUS_HEAD_SET must

be called in the PBO module of every business scenario related tab
strip header data subscreen, regardless if it has been redefined or not.
Also the field handler class method FIELD_STATUS_ITEM_SET has to
be called in the PBO module of every business scenario related tab
strip item data subscreen regardless if it has been redefined or not. The
reason is that both methods can be used within the sub screens to
integrate the maintained field setting configuration without the need
to manually evaluate these settings in every scenario related sub
screen PBO module over and over again.
Tab Program
Enter the name of the main program where the business scenario related
subscreens are located in. Usually, this is the main program of a function
group.

Note: You can use the general function group /OTX/PF41_IDX_

DEFAULT_SCRN as a copy template. It already contains basic subscreens
for header and item data. Moreover, the function group contains the
corresponding screen logic, which is independent of the business
scenario. The function group also contains the required global data
declarations.
After copying the function group, replace all associated types of the
general data declarations in the TOP include by suitable types that are
related to the business scenario. Resolve all activation errors resulting
from the type changes within the copied function group. Additionally,
adjust the subscreen table control of the item data following the type
changes.
This approach significantly reduces development efforts when
implementing new business scenarios. It prevents developing the
same basic screen logic over and over again and therefore also lowers
maintenance efforts across different business scenarios.
Data Sync. FM
Enter the data synchronization function module. It must be created and
located in the function group where all the business scenario related
subscreens are located in. This function module allows data exchange
between the subscreens and the main Processing Screen frame screen or
program.
If you have copied the template function group /OTX/PF41_IDX_DEFAULT_
SCRN, the data synchronization function is already in place.
To create a data synchronization function completely from scratch, copy the
template function /OTX/PF40_IDX_DATA_SYNC_TEMPL into the
corresponding subscreen function group and enhance it as needed. The
objects to be synchronized by this function module are the following:
• the index header and item data

• a data changed indicator (needed to save index data if not done
already)
• the class instance of the field handler class
The following different data synchronization call modes are available. They
are initiated by the frame screen. They must be handled by the
synchronization function accordingly:
Import Mode
The import mode transfers the current screen data, the data changed
indicator, and the field handler instance to the subscreen function
group. It is called during initialization of the Processing Screen. It is
further called in the PAI section after execution of a process action and
also in the PAI after a possible change of the current characteristic
value. A characteristic value change could be caused, for example, from
changed data by a process action.

Export Mode
The export mode transfers the index data, the data changed indicator,
and the field handler instance from the subscreen function group back
to the frame screen program. It is called in the beginning of the PAI
section.
Exit Mode
When finally leaving the Processing Screen the synchronization
function is called in exit mode. It executes any final cleanup or data
reset activities. The data changed indicator has a special importance
here. It is used to ask the user if data changes should be saved before
leaving the screen.
Note: Index header data, index item data, the data changed indicator,
and the field handler class instance must be synchronized. Therefore,
suitable global data definitions must be made in the top include of the
corresponding function group.
PAI Sync. FM
Enter the PAI synchronization function module. Create it and locate it in the
function group where all the subscreens that are business scenario related
are located in. This function module allows the exchange of screen user
commands between the subscreens and the main Processing Screen frame
screen or program. If you have copied the template function group /OTX/
PF41_IDX_DEFAULT_SCRN, the PAI synchronization function is already in
place.
To create a PAI synchronization function completely from scratch, copy the
function module /OTX/PF41_IDX_PAI_SYNC_DEF into the corresponding
subscreen function group and enhance it as needed.
Tab 1-6 Subscreens , Tab 1-6 Text

Assign all business scenario specific subscreen numbers to the tabs.
Maintain the texts for the single tabs as well.
Inquire Role
Enter the inquire role. Inquiry is a special simplified process step referral
functionality. It does not need a receiving role to be chosen but only
requires the target users to be entered. To allow maintenance of suitable
process actions and field settings, you must maintain a technical role name
that is used to maintain and evaluate these settings.
Display Role
Enter the display role. It is used to read the maintained Processing Screen
field configuration if the Processing Screen is called in standalone mode
outside of any running process.
Display Process Step

Enter the display process step. It is used to read the maintained Processing
Screen field configuration if the Processing Screen is called in standalone
mode outside of any running process.

Detail Pane State

Select the detail pane state from the list. When calling the Processing Screen
for the first time, this setting is used to determine if the detail pane should
be shown or hidden. Afterwards the current state is stored user-specifically
for all further screen calls.
Possible values: Hide, Show, No Detail Pane
Detail Pane Side
Select the detail pane side from the list. When calling the Processing Screen
for the first time, this setting is used to determine on which side the detail
pane should be docked. Afterwards the current docking side is stored user-
specifically for all further screen calls.
Possible values: Left Justified, Right Justified
Detail Pane %
Enter the detail pane ratio in percent. When calling the Processing Screen
for the first time, this setting is used to determine the screen size of the
detail pane in percent. Afterwards the current size is stored user-specifically
for all further screen calls.
Note: Only ratio values between 5 and 90 % are allowed to prevent
that either the main screen or the detail pane is completely overlain.
Plug-In Type
Assign the plug-in type that shall be used in the detail pane.
Plug-In ID
Maintain the plug-in ID that should initially be displayed in the detail pane
when the screen is called for the first time. Afterwards the current plug-in
ID is stored user-specifically for all further screen calls.
7.1.3 Defining actions

In this step, you define the process actions which must be available to be assigned to
process steps in combination with the current characteristic value and agent role.
To define actions:
1. In the Version Definition Details screen (see “Defining a profile version”

on page 177), double-click Action Definition in the Dialog Structure.
2. In the Action Definition Overview screen, define actions, using the following
parameters.
Action ID
Define the action using a 15 character unique action ID.
Note: Every action ID that is relevant for processing on Fiori side also
needs to be maintained as a corresponding work object type action
using the same action ID. For more information, see “Defining and
assigning node actions” on page 314.

Action Title
Enter the action title. It will be displayed as button text for the created
process action button in the action pane area of the Processing Screen.
Action Description
Enter a description of the action. The description will be displayed as tooltip
when the pointer is moved over the process action button.
Action Type
Select the action type from the list. The action type determines how a
defined action is handled during processing. It also determines whether the
action needs to be displayed in the action pane area of the Processing Screen
or not. The following action types are available:
Background Action
All actions of this type are not displayed in the action pane area of the
Processing Screen. However, these actions can be assigned to process
steps that are executed in background.
Dialog Action
For every dialog action, which is assigned to a process step, current
characteristic value, and agent role, an executable process action button
is created in the action pane area of the Processing Screen.
History Action
A history action is some kind of “dummy” action. It is nor available
from an Processing Screen process action button or within a
background process step. It can be used from anywhere in the process
to create a history entry for any purpose.
Referral Action
This action type is a special dialog action which is used to refer process
steps to other agent roles and/or users. It is displayed as an action
button in the action pane area of the Processing Screen.
Important
The following actions are framework actions that must be available in
all profile definitions:
Action ID Action Title/ Action Action Class

Action Type
Description
FRM_HIST_ACTIV Activate Rule History /OTX/
Action PF41_CL_ACTION_
ACTIVATE
FRM_HIST_BYPASS Bypass Rule History /OTX/
BYPASS

Action ID Action Title/ Action Action Class

Action Type
Description
FRM_WP_REASSIGN Reassign Referral /OTX/
ASSIGN_EXT
FRM_WP_CLASSI Reclassify Dialog /OTX/
CLASSI_EXT
Action Class
Enter the action class. The action class contains the logic that is processed
when executing an action during runtime. If no class is maintained, the
standard class /OTX/PF04_CL_ACTION is always used.
CL_ACTION must be inherited, redefined as needed, and entered as custom
action class.
ACTION_LOGIC
This method provides logic that is executed for action of type Dialog
Action and Referral Action.
The method is called by the Processing Screen action pane when
pressing a process action button.

PIT_ACTION_REASONS Importing This parameter contains
action reasons which could
potentially be selected
during executing actions
from the Fiori Task App.
PCS_PLH Changing Process ledger header data
that can be used and
changed by the action
PCT_PLI Changing Process ledger item data
PE_SUCCESS Exporting If the action has been
processed successfully, this
parameter has to be
returned with X. This
indicates that the ledger
data can be saved and the
process can be continued.


PE_NO_DIRECT_LEDGE Exporting This parameter can be used
R_SAVE to prevent a dialog action
from directly saving data
changes to the process
ledger tables after its
successful execution.
Therefore, it leaves the
handling of the database
save up to the calling
application. This may be
useful if any changes should
explicitly be saved by the
Save button of the
Processing Screen only. On
the other hand, the changes
should also be discarded if
the Confirm Save dialog
box is denied when leaving
the Processing Screen.
PET_MESSAGES Exporting All messages returned with
this parameter are saved as
action messages for the
corresponding history entry.
PET_REFERRAL_AGENT Exporting In case of the action type
S Referral Action, all
referral agents are returned
to the process by this
parameter.
PET_COMMENT Exporting This parameter allows
returning comments, which
are written to the comment
history.
PC_FINISH_STEP Changing This parameter contains the
customizing setting if a
dialog step should be
finished after executing the
corresponding process
action. It can be overwritten
if needed in some rare cases.
PC_FINISH_PROCESS Changing This parameter contains the
customizing setting if the
whole process should be
finished after executing the


PC_RESTART_PROCESS Changing This parameter contains the
customizing setting if the
process should be restarted
after executing the
ACTION_LOGIC_PRE_CHECK
This method allows to check if executing an action is allowed or should
be stopped. The method is called for actions of type Dialog Action and
Referral Action.

PIS_ACTION_ASSIGNMENT Importing Corresponding action
assignment settings
defined in the
configuration
PIT_ACTION_REASONS Importing Corresponding action
reasons if applicable and
selected during execute
action
PIS_PLH Importing Process Ledger Header
Data
PIT_PLI Importing Process Ledger Item
Data
PET_MESSAGES Exporting If the execute action
should be prevented/
stopped, return any
messages of type E
ACTION_LOGIC_BGR
This method provides logic that is executed for action of type
Background Action. The method is called when executing background
process steps.

PCS_PLH Changing Process ledger header
data that can be used
and changed by the
action
PCT_PLI Changing Process ledger item data


processed successfully,
this parameter has to be
returned with X. This
indicates that the ledger
data can be saved and
the process can be
continued.
PE_FINISH_PROCESS Exporting You can use this
parameter to finish the
whole process after
successfully executing
the corresponding
process action.
PE_RESTART_PROCESS Exporting You can use this
parameter to restart the
process after
successfully executing
the corresponding
process action.
PET_MESSAGES Exporting All messages returned
with this parameter are
saved as action messages
for the corresponding
history entry.
ACTION_LOGIC_HIST
This method provides logic that is executed for action of type History
Action.
This method can be called whenever a dedicated history entry needs to
be created independent from the regular functionality of dialog actions
in the action pane or background actions within background steps.
Standard history entries will be created for both scenarios automatically
without the need for further history handling.

PIS_PLH Importing Process ledger header data
that can be used but not
PIT_PLI Importing Process ledger item data


PIT_ACTION_REASONS Importing This parameter contains
action reasons which could
potentially be selected
during executing actions
from the Fiori Task App.
processed successfully, this
parameter must be returned
with X. This indicates that
the history entry can be
saved to the database and
the process can be
continued.
PET_MESSAGES Exporting All messages returned with
this parameter are saved as
action messages for the
corresponding history entry.
ACTION_MESSAGE_FORMAT
This method formats action messages for screen output. This can be
required if some special formatting requirements need to be fulfilled,
for example amount formatting. It can also be required if some
language specific description texts should be displayed, for example
agent role descriptions.
This method is called when displaying action messages from the
process history plug-in.

PIS_HIST Importing History entry for which a
message line should be
formatted for screen display
PCS_MESSAGE Changing Formatted output message
ACTION_SKIP_BUTTON
This method can be used to dynamically skip the button creation for an
assigned dialog action during runtime. As soon as a button has been
skipped, it is not possible to execute the corresponding dialog action
anymore.
This method is called when creating the buttons for assigned dialog
actions in the Processing Screen action pane and the Fiori screens.


PIS_PLH Importing Process ledger
header data that can
be used but not
changed by the
action
PIT_PLI Importing Process ledger item
data that can be used
but not changed by
the action
PIS_ACTION_ASSIGNMENT Importing Configuration
settings of the action
assignment
PIS_SCREEN_SETTINGS Importing Configured screen
settings
PI_READ_ONLY_MODE Importing Indicates whether the
screen currently runs
in read only mode or
not.
PE_ACTION_SKIP_BUTTON Exporting If this parameter is
returned with value
X, no button will be
created for the dialog
action.
ACTION_SKIP_HIST_GET
This method allows to overwrite the Skip History setting of the action
configuration during runtime.
This method is used when preparing the process history entries for
screen output.

PIS_HIST Importing History entry for the
executed action in the
process history
PIT_HISM Importing History message lines for a
process history entry
PE_ACT_SKIP_HIST Exporting If this parameter is returned
with value X, the
corresponding history entry
for the action will be
skipped in the process
history screen output.
ACTION_REASONS_GET
This method allows to offer action reasons to be selected when
executing actions from the Fiori Task App.


PIS_PLH Importing Process ledger header
data that can be used but
not changed by the
action
PE_ACTION_REASON_STA Exporting This parameter controls
TE whether the selection of
action reasons is
required, optional, or
inactive.
PE_ACTION_REASON_OPT Exporting This parameter controls
whether the action
reasons are offered as a
multiple or single
selection.
PET_ACTION_REASONS Exporting Action reasons
represented by unique
IDs and suitable
descriptions. The default
action reason to be
preselected can also be
set here.
ACTION_COMMENT_INPLACE_CHECK
You can use this method to control whether action comments are
handled by one of the following:
• the action itself using a suitable inplace comment box (for example,
referral actions)
• the corresponding comment dialog box offered on framework side

PR_COMMENT_INPLACE Returning Set the parameter to X if
comments are handled
by the action itself,
otherwise return an
empty value.
Skip History
Select this check box to skip the display of history entries in the process
history. For example, adding a comment may not be relevant to be
displayed in the history as an executed action.

Action Icon
For dialog and referral actions, assign an icon symbol, which is displayed
on the created process action button in the action pane area of the
Processing Screen.
Timeline Icon
Assign an icon for visualization in the Fiori history screens.
Tip: All available icons are defined in the “SAP UI5 Icon Explorer”:
https://openui5.hana.ondemand.com/iconExplorer.html. The URL
might be object to changes.
7.1.4 Defining roles

In this step, you define the agent roles that participate in the processing of the dialog
process steps. You also define how these roles are resolved during runtime. The
roles are also used to assign process actions, possible referral, and Processing Screen
field settings to the corresponding agents. An agent role can represent a group of
users or just one single user responsible for specific process steps.
To define roles:

on page 177), double-click Role Definition in the Dialog Structure.
2. In the Role Definition Overview screen, define roles using the following
parameters:
Role ID
Define the role using a 15 character unique role ID.
Role Description
Enter a meaningful role description.
Role Type
Select the role type from the list. Based on the defined role type, the system
determines how the role has to be resolved. You can select one of the
following role types:
Organizational Object Assignment
You can assign a fixed organizational object type and ID to the role, for
example work center.
Role Resolution Logic
You can program a dynamic role resolution logic, which will be used
for the role resolution. For this role type, the assignment of a custom
role class is mandatory.
Role Class
Enter a custom role class if necessary. It contains all required logic to
resolve the assigned role users during runtime. If no class is maintained the
standard class /OTX/PF04_CL_ROLE is always used.


CL_ROLE must be inherited, redefined as needed, and entered as custom role
class.
ROLE_LOGIC
Within this method, you can define any custom role resolution logic.
This method is called by the role resolution function modules when
creating dialog process steps and when referring process steps in dialog
to propose the possible recipient list.

PET_ROLE_RESULT Exporting List of resolved users
Object Type
Enter the organizational object type, for example work center to be selected
for the role type Organizational Object Assignment.
Agent ID
Enter the agent ID or the ID of another organizational object, for example
work center, depending on the chosen object type.
Note: The IDs of organizational object assignments may be different

across the system landscape. Therefore, the /OTX/PF04_ADM_ROLE
transaction is available to adjust the values in test and production
systems, which in general do not allow any configuration changes.
The transaction is protected against a special administration
authorization. For more information, see “Authorizations”
on page 224.
EvalPath
to resolve the connected users for a role. As long as no special evaluation
path has been set up, the standard evaluation path WF_ORGUS is always
used.

7.1.5 Configuring data enrichments

In this step you configure data enrichments. Use data enrichments to determine data
at any point of time throughout the process life cycle.
Implement one or more of the following general data enrichment strategies:
• Rules based data enrichment, for example setting different Sales Order document
types.
• Document content based data enrichment, for example setting a high processing
priority if the document full text contains the “urgent” keyword .
• Master data based data enrichment, for example setting the material number
from the material master info record using the customer material number.
• Learning based data enrichment, for example setting payment terms from
learned index data in combination with provided document keywords or
descriptions.
Technically two different data enrichment configuration options are available:
1. Determine a target field value based on values learned from previous processes
with the same source field value.
2. Determine one or more target field values using logic implemented by a data
enrichment exit interface.
To configure data enrichments:

3. On the Profile Configuration Overview screen, mark a profile.
4. Double-click Version Definition in the Dialog Structure.
5. On the Version Definition Details screen, double-click Data Enrichment
Configuration in the Dialog Structure.
6. On the Data Enrichment Configuration Overview screen, configure data
enrichments.
Data Enrichment ID
Define the data enrichment using a 16 character unique ID.
Data Enrichment Description
Enrichment Type
The enrichment type reflects the two different technical data enrichment
configuration options.

The following enrichment types are available:
• Learning based data enrichment

• Logic based data enrichment
Note: If you select this enrichment type the Data Enrichment

Class parameter is not applicable anymore
• Logic based data enrichment
Note: If you select this enrichment type the field type, learning
target field, and learning source fieldparameters are not
applicable anymore.
Learning Source Field

Select the data enrichment point at which the data enrichment is executed.
The following data enrichment points are available:
• Data enrichment during process initialization. Executed within the

process framework before the business rules are processed.
• Data enrichment during indexing in dialog.
• Data enrichment during process initialization & dialog indexing
• Data enrichment at all points.
Field Type
The field type controls on which process ledger hierarchy level the data
enrichment is done. Select the field type from the list.
The following field types are available:
• Header Field
• Item Field
Learning Target Field

Define the target process ledger field which is populated by the data
enrichment.
Enrichment Source Field
Define the source process ledger field. It is used to retrieve the field value of
the target process ledger field by involving the learned data enrichment
linkages between source field values and target field values.
Data Enrichment Class
Enter a data enrichment class. Implement the /OTX/PF04_IF_DATA_
ENRICH_EX exit interface if necessary.
For a detailed description of the methods of the exit interface, see “Methods
of the data enrichment exit interface” on page 200.

Active
Select the check box to set the data enrichment to active. Clear the check box
to set the data enrichment to inactive.
7.1.5.1 Maintaining data enrichment learning keys

You use data enrichment learning keys to restrict learned data enrichment results to
special business data contexts. For example to learn and enrich payment terms
depending on the sales organization and customer number, instead of globally using
the same learning data in every case.
Note: Data enrichment learning keys are only applicable for learning based
data enrichments.
To maintain data enrichment learning keys:
1. On the Data Enrichment Configuration Overview screen, mark an entry.
2. Double-click data enrichment learning keys in the dialog structure.
3. On the Data Enrichment Learning Keys Overview screen, maintain data

enrichment learning keys.
Enrichment Key Fields

From the process ledger header table, select a data enrichment key field.
The field is used by the system to dynamically form data enrichment keys
for learning and managing learned linkages. Linked are the data enrichment
source field values and the data enrichment target field values. You can
maintain multiple field names if needed.
Sequence
Define the sequence that processes the data enrichment key fields to form
the corresponding data enrichment key.
7.1.5.2 Maintaining data enrichment logic target fields

Use the data enrichment logic target fields to tell the system which target fields are
enriched by each logic based data enrichment. This is important if a combination of
logic and learning based data enrichments is used for the same target fields. In this
context learning based data enrichments should only learn from user inputs but not
from previous results of logic based data enrichments.
Example: Material numbers should be determined in a two step approach. First from the
material master using a customer material number. If no result can be found then the material
number should be determined by learned user inputs as a fail safe option. If no data
enrichment logic target fields are maintained for the logic based data enrichment, the learning
based data enrichment can learn from the previous logic based data enrichment result instead
of user data inputs.

Note: Data enrichment logic target fields are only applicable for logic based
data enrichments.
To maintain data enrichment logic target fields:
1. On the Data Enrichment Configuration Overview screen, mark an entry.
2. Double-click data enrichment logic target fields in the dialog structure.
3. On the Data Enrichment Logic Target Fields Overview screen, maintain data
enrichment keys. Use the following parameters:
Field Type:
The field type reflects on which process ledger hierarchy level the data
enrichment is done. Select the field type from the list.
The following field types are available:
• Header Field
• Item Field
• Logic Target Field: Define the target process ledger field which is
populated by the data enrichment.
Logic Target Field

Define the target process ledger field which is populated by the data
enrichment.
7.1.5.3 Methods of the data enrichment exit interface

You must implement the /OTX/PF04_IF_DATA_ENRICH_EX exit interface, if you
define a custom logic for data enrichments.
The following methods can be implemented:
DATA_ENRICH_LOGIC
You can define any data enrichment logic within this method.
Parameter Parameter Type Description

PI_CHARACTERISTIC Importing Current characteristic value
PI_ENRICH_ID Importing Processed data enrichment
ID
PI_ENRICH_KEY Importing Currently formed data
enrichment key value
PI_ENRICH_POINT Importing Data enrichment point
PIS_DEC Importing Data enrichment
configuration


PIT_DERK Importing Data enrichment key fields
PET_RETURN Importing Return messages
PCS_HEAD Changing Enriched process ledger
header data
PCT_ITEM Changing Enriched process ledger
item data
DATA_ENRICH_CHECK
You can implement any custom logic that checks if the result of a business rule
that checks the correctness of the data enrichment result fails or succeeds.
Note: A data enrichment result check that fails, indicates a mismatch

between target field values. Check the currently indexed process ledger
target field value which differs from the enrichment value.

PI_CHARACTERISTIC Importing Current characteristic value
PI_ENRICH_ID Importing Processed data enrichment
ID
PI_ENRICH_KEY Importing Currently formed data
enrichment key value
PIS_DEC Importing Data enrichment
configuration
PIT_DERK Importing Data enrichment key fields
PET_RETURN Importing Return messages
PIS_HEAD Importing Process ledger header data
PIT_ITEM Importing Process ledger item data
PES_CHECK_RESULT Exporting Result of the data
enrichment check. Defined
by data enrichment ID, data
enrichment key value and
data enrichment target field

7.1.5.4 Assigning data enrichments

You must assign data enrichments to characteristic values to process them during
runtime.
You must additionally set the following process configurations to handle the
assigned data enrichments.
For more information, see “Maintaining process steps” on page 209 and “Assigning
process actions” on page 215.
Process Step Step Type Step Description Rule Rule Rule Class
Type
ENRICH_DAT Background Data enrichment ENRICH_D Change /OTX/PF41_CL_RULE_CHG_
AT DE_EXEC
ENRICH_MIS Dialog Data enrichment [Data Check /OTX/PF41_CL_RULE_CHK_
mismatch Enrichment DE_RSLT
ID]
Process Action Action Description Action Class

ACT_ENRICH_UPD Update learning data from mismatches /OTX/PF41_CL_ACTION_DER_UPD
ACT_ENRICH_DISP Display learned data enrichments /OTX/PF41_CL_ACTION_DER_DISP
Note: OpenText recommends to define one check rule per defined data
enrichment. This allows bypassing each failed data enrichment result check
separately.
To assign data enrichments:
3. On the Profile Configuration Overview screen, mark a profile.
4. In the Dialog Structure, double-click Version Definition .
5. On the Version Definition Details screen, in the Dialog Structure, double-click

Characteristic Configuration.
6. On the Characteristic Configuration Overview screen, mark a characteristic.
7. In the Dialog Structure, double-click Assign Data Enrichments .
8. On the Assign Data Enrichment Configuration Overview screen, assign data

enrichments.

Data Enrichment ID
Enter data enrichment IDs that are processed for the current characteristic
value.
Sequence
Maintain the sequence in which the assigned data enrichments is processed.
Enrichment Step
Enter the background process step which executes data enrichments.
Check Mismatch Step
Enter the dialog process step which executes all checks if the determined
data enrichment results are valid or not.
Check Mismatch Rule
Enter the check rule which checks if the determined data enrichment result
is valid or not.
Note: If a data enrichment is defined for execution at the Data enrichment

during process initialization point, the Check Mismatch Step and Check
Mismatch RuleEnrichment Step parameters are not applicable.
7.1.6 Configuring the process split functionality

In this step, you configure the process split functionality. You can use it to split a
business process into multiple processes depending on the defined split criteria. You
can assign a process split to characteristic values afterwards. This allows using
different logic for process splits dependent on the current characteristic value.
When splitting business processes, the following technical assumptions are made:
1. After successfully splitting a business process into several target processes, the
source process is immediately finished.
2. Each target process is linked to the source process by writing the source process
ledger key to the target header ledger data table.
3. The started target process is not linked to any inbound process anymore.
4. The archived images connected to the source process will also be linked to the
target processes without rearchiving these images.
5. If the first target process workflow start fails, the process split is stopped
immediately without taking further action.
6. If the first target process workflow has been started successfully but any other
workflow start fails, the process split writes error log entries. They can be
accessed and reprocessed using a dedicated work center at any point of time.
Automatic reprocessing of workflow start errors is also possible by scheduling
the ABAP report /OTX/PF04_P_PTEL_REPROCESS.
To configure the process split functionality:

3. On the Profile Configuration Overview screen, mark a profile, and then

double-click Version Definition in the Dialog Structure.
4. On the Version Definition Details screen, double-click Process Split

Configuration in the Dialog Structure.
5. On the Process Split Configuration Overview screen, configure the process

split, using the following parameters:
Split ID
Process Split ID. Define the process split using a 16 character unique ID.
Process Split Desc.
Process Split Description. Enter a meaningful description.
Process Split Type
Select the process split type from the list. Based on the defined process split
type, the system determines how the process split must be determined and
processed. Currently only one process split type is available:
Process split based on line item grouping
You can maintain line item grouping fields that are used as process split
criteria, as described in “Maintaining line item grouping” on page 205.
With this split type the system uses the maintained line item grouping
fields to determine the corresponding line item groups. For each of the
determined line item groups a separate new business process is started.
In the following graphic, each row of empty gray boxes represents a line
item.
Process Split Class

Enter a custom process split class if necessary. It contains all required logic
to split a business process based on the selected process split type and its
connected configuration during runtime. If no class is maintained the
standard class will always be used for the following process split type:
Process split based on line item grouping: /OTX/PF41_CL_PROC_
SPLIT_LG


If you must change the standard logic for any reasons, inherit the class /
OTX/PF04_CL_PROC_SPLIT, redefine it as needed, and enter it as custom
process split class for the corresponding process split type.
For a detailed description of the methods of the /OTX/PF04_CL_PROC_SPLIT
class, see “Methods of the process split class” on page 205.
Dialog
Select this check box to force dialog processing for all process splits.
7.1.6.1 Maintaining line item grouping

The line item grouping settings are currently only used by the Process split based
on line item grouping. You can use them as process split criteria.
To maintain line item grouping fields:
1. On the Process Split Configuration Overview screen (see “To configure the
process split functionality:“ on page 203), mark an entry, and then double-click
Line item grouping in the Dialog Structure.
2. On the Line item grouping Overview screen, maintain line item grouping fields
using the following parameter.
Field Name
From the process ledger item data table, select a line item field that is used
by the system to group line items for process splitting. You can maintain
multiple field names if needed.
7.1.6.2 Methods of the process split class

You can redefine the following methods of the /OTX/PF04_CL_PROC_SPLIT class if
needed. OpenText recommends that you do not change any other method.
PROC_SPLIT_REQUIRED_CHECK
Within this method, you can implement the logic if a process split is required or
not. It is called in the business rule class /OTX/PF41_CL_RULE_CHK_PS used for
the business rule Process split required.
Parameter Parameter Description

type
PR_PROC_SPLIT_REQUIRED Returning Process split required indicator
PROC_SPLIT_GROUPS_DETERMINE
Within this method, you can implement the logic to define into how many
different target processes a process must be splitted and which index data is

assigned to each target process. It is called in the standard process split action
classes /OTX/PF41_CL_ACTION_PS_BGR, /OTX/PF41_CL_ACTION_PS_DIA and /
OTX/PF41_CL_ACTION_PS_EXT depending on if the process split takes place in
background or dialog and based on which user interface.

type
PRT_PROC_SPLIT_GROUPS Returning Determined process split groups
including used split criteria and
assigned index data
PROC_SPLIT_RESULT_CONFIRM
This method allows you to add a dedicated SAP GUI user confirmation dialog
before processing the determined process split result. It is called in the standard
SAP GUI process split action class /OTX/PF41_CL_ACTION_PS_DIA during dialog
processing.

type
PIT_PROC_SPLIT_RESULT Importing Determined process split result
PE_CANCELLED Exporting Flag to indicate that the user did
not confirm and therefore
cancelled the process split
PROC_SPLIT_DATA_HEAD_SET
You can use this method to influence the header index data used for the target
processes. It is called during the process split result determination. By default,
the same header index data is used as in the source process.

type
PI_PROC_GROUP Importing Determined split group of the
target process
PRT_PROC_DATA_HEAD Returning Header data to be used for the
target process
Note: To map data to the target ledger data tables, the system uses the
default field mapping ID. For more information, see “Defining external
data mapping” on page 167.
PROC_SPLIT_DATA_ITEM_SET
You can use this method to influence the item index data used for the target
processes. It is called during the process split result determination. By default,

no item index data is set because this can depend strongly on the process split
logic itself.

type
target process
PRT_PROC_DATA_ITEM Returning Item data to be used for the target
process
Note: For the process split type Process split based on line item
grouping, the standard class /OTX/PF41_CL_PROC_SPLIT_LG already
provides a logic to assign the line items to the target processes that
correspond to the maintained line item grouping fields.
PROC_SPLIT_CRITERIA_OUTPUT_GET
Within this method, you can format the used process split criteria for output in
the corresponding process split result confirmation dialog.

type
PR_PROC_SPLIT_CRIT Returning External representation of the
used process split criteria
PROC_SPLIT_MSG_ERROR_ADD
This method allows adding custom error messages to the process history if any
of the target process starts fail.

type
target process
PI_PROC_SPLIT_CRIT Importing External representation of the
PI_PROC_SPLIT_VALUE Importing Process split value resulting from
the process split criteria
PRT_MSG_ERROR Returning Error messages for process history
PROC_SPLIT_MSG_SUCCESS_ADD
This method allows adding custom success messages to the process history in
case of a successfully started target process.


type
target process
PI_PROC_SPLIT_CRIT Importing External representation of the
PI_PROC_SPLIT_VALUE Importing Process split value resulting from
the process split criteria
PRT_MSG_SUCCESS Returning Success messages for process
history
7.1.7 Configuring characteristics

The characteristic value is supposed to represent any criteria that can be determined
from the current set of business data field values in order to structure the relevant
process configuration.
Example: If different business rule checks are required in a Sales Order processing scenario,
the characteristic configuration can be used to execute different rule checks based on the
current sales organization value. It also may combine different fields like the sales
organization, sales office, and distribution channel to form some kind of virtual criteria from
this multiple criteria. The virtual criteria can then be used to distinguish different process
configurations.
To configure characteristics:

on page 177), double-click Characteristic Configuration in the Dialog
Structure.
2. In the Characteristic Configuration Overview screen, configure characteristics

Characteristic Value
Enter a direct (for example sales organization) or an indirect virtual
characteristic value (for example a transcoded combination of sales
organization, sales office, and distribution channel). Values up to 10
characters are allowed.
Direct characteristic values can be represented by a single statically
assigned process ledger header field. For more information, see
“Maintaining characteristic settings” on page 179.
Indirect virtual characteristic values need to be dynamically determined by
coding logic and transcoded into a key value. For more information, see
“Maintaining version settings” on page 178.
Note: If no special characteristic configuration is required at all,

configure an empty characteristic value.

Characteristic Description
Enter a meaningful description for the defined characteristic.
Process Split ID
Enter a process split configuration which is used to split a business process
for the current characteristic value if required. If you do not assign any
process split configuration, the process split functionality is considered as
inactive.
Note: Multiple similar characteristic configurations might need to be

performed. In this case, you can use the /OTX/PF04_CHAR_COPY
transaction to copy any characteristic configuration (and all its dependent
settings) to a different characteristic value. Afterwards the different
settings can easily be adjusted without the need to completely define each
single characteristic value from scratch over and over again. The copy
transaction only allows to copy characteristic values of currently active
profile versions to prevent old versions from being changed by mistake.
7.1.8 Maintaining process steps

The process step maintenance is based on a profile version and connected to the
current characteristic configuration. It contains all processing aspects for a business
scenario including business rule checks, process action assignments, and referral
settings as well as business rule simulate/bypass, index data field, and general
Processing Screen settings.
During runtime, each process step is represented by a SAP Business Workflow

dialog or background work item depending on the corresponding step type.
The following customizing steps are necessary to maintain process steps:
• “Defining a process step” on page 210
• “Defining business rules” on page 212
• “Assigning process actions” on page 215
• “Maintaining referral settings” on page 217
• “Maintaining simulate settings” on page 219
• “Maintaining bypass rules” on page 220
• “Maintaining rules that are excluded from simulation in the Info pane and Check
messages popup” on page 220
• “Maintaining field settings” on page 221
• “Maintaining screen settings” on page 222

7.1.8.1 Defining a process step

To define a process step:
1. In the Characteristic Configuration Overview screen (see “Configuring
characteristics” on page 208), mark an entry, and then double-click Process
Steps in the Dialog Structure.
2. In the Process Steps Overview screen, configure process steps using the
Process Step ID
Define the process step using a 10 character unique ID.
Process Step Description
Enter a meaningful process step description.
Step Type
Select the process step type from the list. The process step type controls how
a process step is determined and executed. The following process step types
are available.
Background Processing Only
Use this step type to execute background actions. It can be executed
only a fixed number of times. Otherwise, it would result in an endless
processing loop if the background processing fails over and over again.
The assignment of a background action ID is mandatory here. See
Action ID on page 211.
Background Processing with Dialog (Dialog on Fail)
Use this step type as the usual choice for steps that must be processed in
background. It automatically sends the process step to dialog if the
background action fails and therefore offers more flexibility than simple
background steps. The assignment of a background action ID is
mandatory here. See Action ID on page 211.
Dialog Processing
Use this step type for all dialog processing steps. They must be defined
using this step type.
Data Preparation Only
Use this step type for simple background activities, for example data
enrichments. The step type will be executed in background. However,
unlike the step type Background Processing Only, it will be executed
within the regular business rule check sequence without creating
separate work items.
Note: The step type Data Preparation Only can be useful to
always ensure a correctly prepared data basis within the business
rule check sequence if needed. However, it is not suitable for
complex background actions like SAP document creations.
Technical errors cannot be handled in a comfortable way using the
SAP Business Workflow functionality Restart after error.

Process Node Assignment

Use this step type as an enhanced step type whose usage should not be
required in general. It allows assigning technical process nodes defined
in the Process Foundation to fulfill special requirements which cannot
be implemented using any of the above mentioned process step types.
Process Step Class

Enter the process step class. It contains all logic required to check the
following:
• if a process step should be raised

• which initial role it should be assigned to
• which logic should be executed in dialog or background depending on
the defined step type
If no class is maintained, the standard class /OTX/PF04_CL_CATEGORY is

always used.
CL_CATEGORY must be inherited, redefined as needed, and entered as
custom process step class.
CATEGORY_INITIAL_ROLE_GET
You can use this method to dynamically determine the initial role if no
fixed initial role assignment is possible.
The method is called after a process step has been determined to be the
next active process step, and no fixed initial role assignment is
available.

PE_ROLE_ID Exporting Determined initial role
Sequence
Define the processing sequence of the process steps within a characteristic
value.
Action ID
Enter the Action ID. For all process steps with type Background Processing
Only and Background Processing with Dialog (Dialog on Fail), it is
mandatory to assign an action ID that contains the logic to be executed in
background.
Note: An action ID can only be assigned to step types Background
Processing Only and Background Processing with Dialog (Dialog
on Fail).

Role ID
To define the initial role assignment statically, enter the role ID.
Note: You can set an initial role only for the step types Background
Processing with Dialog (Dialog on Fail), Dialog Processing
and Process Node Assignment.
Process Node ID
For the process step type Process Node Assignment, enter a corresponding
process node defined in the Process Foundation.
Note: This setting is mandatory for process step type Process Node
Assignment.
Time Value
Maintain the time value when processing of a dialog or background step
should be started.
Time Unit
Maintain the time unit when processing of a dialog or background step
should be started: Minutes, Hours, Days, or Working days
7.1.8.2 Defining business rules

Business rules are assigned to process steps. As soon as at least one business rule
check fails, the process step is relevant for processing. It will result in a dialog or
background work item depending on its step type. If no business rule for any of the
defined process steps fails, no work item is created and the overall process is
successfully completed.
To define business rules:
1. In the Process Steps Overview screen (see “Defining a process step”

on page 210), mark an entry, and then double-click Rules in the Dialog
Structure.
2. In the Rules Overview screen, define the business rules using the following
parameters.
Rule ID
Define the business rule using a 10 character unique rule ID.
Rule Description
Enter a meaningful business rule description.
Rule Type
Select the business rule type from the list. The business rule type controls
how a business rule is handled during runtime. The following rule types are
available.
Check Data Only
The business rule is a check-only rule. That means, it cannot change any
data but only check the given data for its validity.

Note: This rule type cannot be selected for business rules that are
assigned to the process step type Data Preparation Only.
Change Data
If this business rule type is selected, the corresponding business rule
may change the given data, for example data enrichments. It is not
possible to set this rule type to status failed.
Note: This rule type must only be selected for business rules
assigned to the process step type Data Preparation Only.
Rule Class
The business rule class contains all logic required to execute a business rule
during the business rule run in background or during business rule
simulation (if applicable).
For every business rule, a valid business rule class must be inherited from
the standard class /OTX/PF04_CL_MODULE, redefined as needed, and entered
as custom rule class.
MODULE_EXEC_CHECK
This method defines business rule check logic for the rule type Check
Data Only.
This method is called when running the business rule run in
background or during simulation in dialog.

to be used for the check but
not changeable
PIT_PLI Importing Process ledger item data to
be used for the check but
not changeable
PIS_CATEGORY_DATA Importing Customizing settings for the
process step to which the
rule has been assigned to
PE_MOD_RUN_STATUS Exporting Return the business rule
check result (see fixed
domain values of the
corresponding data type)
PET_MOD_MSG Exporting Business rule check return
messages
MODULE_EXEC_CHANGE
This method defines business rule change logic for the rule type Change
Data.

This method is called when running the business rule in background or

during simulation (if applicable) in dialog.

PI_SIMULATION_MODE Importing Indicates that a module is
currently executed in
simulation mode. No
changes to database tables
other than the process
ledger tables should be
performed at all. All
changes to the process
ledger tables are reverted
after a simulation run
automatically. However,
changes to other tables
cannot be reverted and
therefore should not be
done in simulation mode.
PIS_CATEGORY_DATA Importing Customizing settings for the
process step to which the
rule has been assigned to
PCS_PLH Changing Process ledger header data
to be changed
PCT_PLI Changing Process ledger item data to
be changed
PET_MOD_MSG Exporting Business rule change return
messages (if needed)
MODULE_MESSAGE_FORMAT
This method formats the business rule message(s) for dialog screen
output, for example amount or quantity conversions.
This method is called when displaying rule check result messages from
the business rule simulation (if applicable).

PCS_MESSAGE Changing Business rule return
message to be formatted for
dialog screen output
Note: For check rules which should always fail by default without
further check requirements, you can use the /OTX/PF41_CL_RULE_
CHK_FAILED class without the need to create similar classes for every
rule check over and over again.
Sequence
Define in which sequence the business rules are executed within a process
step.

Frequency
Define how often a business rule is executed within a process step. The
following values are available.
Always
This means that a business rule will always be executed.
Custom
For this frequency, you must define a fixed number.
Note: For business rules that are assigned to process step type
Background Processing Only, you must restrict the number of
executions to prevent endless loops.
Frequency Count
If a Custom frequency is assigned, define how often a business rule is
executed.
Dialog
Select this check box to skip processing the corresponding background
action and to directly force dialog processing. This setting is only available
for process steps of type Background Processing with Dialog (Dialog on
Fail).
Active
Select this check box to set the business rule to active. Clear the check box to
set the business rule to inactive.
7.1.8.3 Assigning process actions

The action assignment defines which process actions are available for an agent role
based on the used UI, current characteristic value, and dialog process step.
To assign process actions:

on page 210), mark an entry, and then double-click Action Assignment in the
Dialog Structure.
2. In the Action Assignment Overview screen, assign actions using the following
parameters.
UI Type
Select the UI type from the list. The following values are available.
• SAP GUI
• Web
Role ID
Enter the role ID. With this field, you can define to which role the
corresponding actions are assigned. The assigned actions will be available

in the action pane of the Processing Screen and within the Fiori screens,
depending on the chosen UI type.
Note: If not all roles should have a special action assignment, it is also
possible to leave the Role ID field empty. This simplifies the
configuration. This general setting will then be used for roles that do
not have a dedicated action assignment. However, as soon as a role
specific setting is made, the general settings will not be considered for
this special role anymore.
Action ID
Assign the action ID, which should be available for execution.
Sequence
Define the sequence. It determines the order in which the action buttons are
created in the action pane area of the Processing Screen.
Process Node ID
Enter the process node ID. This setting allows assigning a process node ID
defined in the Process Foundation. When executing an action, the assigned
process node ID will be started next. Similar to the Process Node
Assignment in the process step definition (see Process Node Assignment
on page 211), this should not be required in general. You should use it only
in very rare cases where the requirements cannot be implemented using the
regular functionality.
Time Value
Maintain the time value when processing an assigned process node ID
should be started. The setting is only used if a process node ID is assigned.
Time Unit
Maintain the time unit when processing an assigned process node ID
should be started. The setting is only used in case a process node ID is
assigned. Possible values: Minutes, Hours, Days, or Working days
Finish Step
Select this check box to determine that a process step should be finished
after executing the corresponding process action. After finishing a process
step, the defined business rules will be checked automatically to determine
the next required process step. The current value of this setting will be
passed into the method of the action class, which contains the action logic,
and can be overwritten there if needed.
Finish Process
Select this check box to determine that the whole process should be finished
after executing the corresponding process action. The current value of this
setting will be passed into the method of the action class, which contains the
action logic, and can be overwritten there if needed.
Restart Process
Select this check box to determine that the process is restarted after
performing the corresponding process action. The current value of this

setting is passed into the method of the action class, which contains the
action logic. The value can be overwritten there if needed.
A process restart runs the process initiation again and therefore
redetermines the Process Configuration profile and the corresponding
active profile version. Additionally, the current status of all related business
rules is reset, for example, whether a business rule has been bypassed or
how many times a business rule has been run already, or the business rule
results.
Comment Required
Select this check box to determine that a comment is required before
executing a process action.
Confirmation Required
Select this check box to determine that a confirmation dialog box is
displayed before executing a process action.
Active
Select this check box to set the action assignment to active. Clear the check
box to set the action assignment to inactive.
Note: The role ID which has been defined as Inquire Role (see
“Maintaining Processing Screen settings” on page 180) must only have one
“return action” (Finish Step check box selected) assigned. It must not be
allowed to send the process to further steps or roles using the inquire
functionality. The inquire step is only intended to represent a simple send/
return pattern. As soon as any “return action” is executed within the
inquire step, the process is directly returned to the sender of the inquiry.
7.1.8.4 Maintaining referral settings

The referral settings define to which roles the current role can refer a process step.
Referral is based on the used UI, current characteristic value, and dialog process
step.
To maintain referral settings:

on page 210), mark an entry, and then double-click Referral Settings in the
Dialog Structure.
2. In the Referral Settings Overview screen, maintain referral settings, using the
UI Type
• SAP GUI
• Web

Note: Referral settings for the Fiori screens are intended for future
use only. They are not evaluated so far.
Action ID
Enter the action ID. If multiple different referral actions have been defined
in a business scenario, you can use this setting to refine the referral settings
for these different referral actions.
If the referral settings should be used for all referral actions in the same
way, leave the field empty.
Role ID
Enter the role for which the referral settings should be relevant.
Note: You might want to configure that not all roles should have
special referral settings. In this case, it is possible to leave the Role ID
field empty. This simplifies the configuration. This general setting will
then be used for roles that do not have a dedicated referral setting.
However, as soon as a role specific setting is made, the general
settings will not be considered for this special role anymore.
Refer to Role
Maintain which referral roles should be available. The maintained referral
roles will be available when executing a referral option. As soon as one of
the offered referral roles is selected in the refer action dialog box, all
corresponding users will be resolved accordingly.
Sequence
Define the sequence in which the possible referral roles should be offered in
the refer action dialog box.
Comment Required
Select this check box to determine that a comment is required during
referral.
Evaluation Path
to resolve the connected users when selecting a referral role. As long as no
special evaluation path has been set up, the standard evaluation path WF_
ORGUS is always used.
BAdI /OTX/PF40_REFERRAL
The /OTX/PF40_REFERRAL BAdI implements the /OTX/PF40_IF_BADI_REFERRAL
interface. The following interface method is available:
CHANGE_REASSIGN_REFER_OPTIONS – This method allows to change the

corresponding referral options. It is called when processing a referral action from the
SAP GUI processing screen or the SAP GUI workplace.


PI_REFERRAL_MODE Importing Referral mode. Possible values:
S - Standard Referral Mode
R - Reassignment Mode
I - Inquire Mode
PIS_PLH Importing Process Ledger Header Data
PIT_PLI Importing Process Ledger Item Data
PCT_REASSIGN_REFER_OPTIONS Changing Referral Options to be changed by
the BAdI
7.1.8.5 Maintaining simulate settings

Using the simulate settings, you can define which process types can be simulated
depending on the current characteristic value, process step, and agent role.
Note: This presumes that the general simulate business rules functionality has
been assigned to the corresponding agent role using the action assignment. If
the functionality has not been assigned to an agent role, the settings described
in this section are not relevant.
To maintain simulate settings:

on page 210), mark an entry, and then double-click Simulate Settings in the
Dialog Structure.
2. In the Simulate Settings Overview screen, maintain simulate settings, using the
Role ID
Enter the role for which the simulate settings should be relevant.
Note: If not all roles should have special simulate settings, you can
leave the Role ID field empty. This simplifies the configuration. This
general setting will then be used for roles that do not have a dedicated
simulate setting. However, as soon as a role specific setting is made,
the general settings will not be considered for this special role
anymore.
Simulate Step
Enter the process step that should be considered in the business rule
simulation run.
Active
Select this check box to set the simulation setting to active. Clear the check
box to set the simulation setting to inactive.

7.1.8.6 Maintaining bypass rules

By defining bypass rules, you can control which rules of a simulated process step
can be bypassed to be skipped during further processing.
To maintain bypass rules:
1. In the Simulate Settings Overview screen (see “Maintaining simulate settings”

on page 219), mark an entry, and then double-click Bypass Rules in the Dialog
Structure.
2. In the Bypass Rules Overview screen, maintain bypass rules, using the
Rule ID
Enter the business rules of the corresponding process step that can be
bypassed if required.
Comment Required
Select this check box to determine that a comment is required before
bypassing or reactivating a business rule.
Active
Select this check box to set the bypassing of a business rule to active. Clear
the check box to set the bypassing to inactive.
7.1.8.7 Maintaining rules that are excluded from simulation in the Info
pane and Check messages popup
You can exclude one or multiple business rules from the simulation in the info pane
of the SAP GUI processing screen as well as from the Fiori task app check
messages popup.
The screen and the popup are updated regularly during data indexing.
If you frequently process business rules with complex logic, performance can be
reduced significantly. For example, by calling BAPI functions to simulate document
postings. Therefore, it can be necessary to exclude business rules in certain
constellations and notify the end user that a corresponding business rule is
excluded.
Note: Business rules that are excluded, are still available in the simulate rules
process action. The Simulate process action is executed explicitly. Therefore, it
is not having an ongoing performance impact during data indexing.
To maintain excluded rules:
1. In the Simulate Settings Overview screen mark an entry. For more information,
see “Maintaining simulate settings” on page 219.
2. In the dialog structure double-click Exclude Rule Simulation from Info Pane.

3. In the Exclude Rules Simulation from Info Pane Overview screen, maintain
excluded rules.
Use the following parameter:
Rule ID
Enter the business rules of the excluded process step.
7.1.8.8 Maintaining field settings

You can maintain the business scenario related index data field settings using the
settings described in this section. All maintained settings will be read by the field
handler class and provided to the tab strip subscreens used in the Processing Screen
tab strip area.
To maintain field settings:

on page 210), mark an entry, and then double-click Field Settings in the Dialog
Structure.
2. In the Field Settings Overview screen, maintain field settings using the
UI Type
• SAP GUI
• Web
Role ID
Enter the role for which the field settings should be relevant.
Note: If not all roles should have a special simulate settings, you can
leave the Role ID field empty. This simplifies the configuration. This
general setting will then be used for roles that do not have dedicated
field settings. However, as soon as a role specific setting is made, the
general settings will not be considered for this special role anymore.
Field Type
Select the field type from the list. Possible values: Header Field, Item
Field
Field Name
Enter the name of the header field and/or item index data field. The fields
must be available in the header and/or item process ledger table assigned to
the used business scenario.
Field Status
Select one of the following field status values from the list:
• Input

• Required
• Hide
• Display Only
Notes
• The field statuses Input, Required, and Display Only are only
evaluated if the current agent role opens the Processing Screen in
change mode.
• Field status settings for the Fiori screens are intended for future use.
They currently only support read-only fields.
Sequence
This setting is only relevant for the UI type Mobile.
Define the sequence of index data fields within the Fiori screens.
Mobile Priority
This setting is only relevant for the UI type Mobile.
Select this check box for the fields that should always be displayed in the
Fiori screens without the need to switch to the detail view.
7.1.8.9 Maintaining screen settings

By maintaining the screen settings. you can configure some general parameters for
the Processing Screen.
To maintain screen settings:

on page 210), mark an entry, and then double-click Screen Settings in the
Dialog Structure.
2. In the Screen Settings Overview screen, maintain screen settings using the
UI Type
• SAP GUI
• Web
Note: Screen settings for the Fiori screens are intended for future
use only. They are not evaluated so far.
Role ID
Enter the role for which the screen settings should be relevant.
Note: If not all roles should have special screen settings, you can leave
the Role ID field empty. This simplifies the configuration. This

7.2. Profile assignment
general setting will then be used for roles that do not have dedicated
screen settings. However, as soon as a role specific setting is made, the
general settings will not be considered for this special role anymore.
Initial Tab
Select the initial tab from the list. This defines which tab of the tab strip
containing the index data fields is the starting point when opening a process
step. You can select from of a maximum of 6 available tabs.
Allow Changes
Select this check box to determine that an agent role is allowed to change
data.
As soon as a role is not allowed to perform changes, the screen field settings
Input, Required, and Display Only are not relevant anymore.
Display Image
Select this check box to determine that the scanned image is automatically
opened and closed in a separate window when executing a process step.
This is independent form the currently chosen detail pane plug-in, which
could be Display Image at the same time as well.
7.2 Profile assignment

Within the profile assignment, a Process Configuration profile is assigned to a
Process Foundation profile.
• The Process Foundation profile covers the technical SAP Business Workflow
requirements.
• The Process Configuration profile mainly focuses on pure business scenario
related aspects.
You can make the profile assignment static by maintaining a fixed one-to-one
relationship. You can make it dynamic by maintaining a flexible one-to-n
relationship between Process Foundation profile and Process Configuration profile.
In general, no dynamic profile assignment is required. This would only make sense
if multiple Process Configuration profiles should be processed by one Process
Foundation profile due to any reasons.
To maintain the profile assignment:
2. Click Process Configuration > Profile Assignment.
3. In the Profile Assignment Overview screen, maintain the profile assignment

PF Profile
Enter the name of the corresponding Process Foundation profile, which
covers the technical SAP Business Workflow aspects.

PC Profile
In case of a fixed one-to-one assignment, enter the name of the Process
Configuration profile, which handles the business scenario requirements.
Profile Determination Class

If a dynamic Process Configuration profile determination is required, enter
a suitable profile determination class. The profile determination class
always must be inherited from the /OTX/PF04_CL_PROFILE_DETERMINE
class. The following method must be redefined as needed.
PROFILE_DETERMINE
This method allows to implement any custom logic to dynamically
determine a Process Configuration profile and version.
This method is called by the Process Foundation when initializing the
Process Configuration profile.

PIS_HEAD Importing Process ledger header data
to be used but not changed
PIT_ITEM Importing Process ledger item data to
be used but not changed
PE_PROFILE_ID Exporting Determined Process
Configuration profile ID
PE_VERSION Exporting Determined Process
Configuration profile
version (this must be the
currently active version)
7.3 Authorizations
During processing of dialog work items, the standard authorization object J_6NPF_
PRF is checked. Therefore, it must be implemented using suitable authorization roles
or profiles. The /OTX/PF04_ADM_ROLE transaction also uses the authorization object
to check if administration authorizations are available.
The authorization object J_6NPF_PRF offers the following authorization fields:
J_6NPF_PRF
Process Configuration profile ID
J_6NPF_CH
Current characteristic value
J_6NPF_CAT
Current process step

7.3. Authorizations
ACTVT
Activity (02 - Change, 03 - Display, 70 - Administer)

Chapter 8
Workplace Configuration
The Business Center Workplace is the central tool to process work objects in
Business Center.
• It allows you to switch between work centers, and to navigate in a process-

dependent tree.
• It provides access to different business objects.
• It enables you to access an inbox with personal and shared work item lists.
• It provides status information for all objects in process.
• It includes selection screens, where you can restrict entries to be displayed in a
dashboard. Each work object type has a different selection screen. Entries in the
dashboard (ALV grid) are selected when you click the node. The selection screen
is not required for this. You can use the selection screen to filter or restrict objects
at the data selection.
The entries in the ALV grid can stand for tasks, documents, business objects,
finished processes, and so on.
• It provides the detail pane where, for example, document image, process history,
and other plug-ins (depending on the work object) are shown. For more
information, see “Configuring plug-in integration” on page 24.
Areas The following screen areas are available. Together, they form the overall appearance
of the Business Center Workplace screen during runtime:

Chapter 8 Workplace Configuration
Navigation - Work Centers

A work center can include a single work object or many work objects. They
allow to access data in a structured way and according to authority.
Notes
• A maximum of nine different work centers are displayed as navigation

buttons. If a user has authority for more than nine work centers, a list
will appear.
• You can configure that the work centers are always displayed as a list. In
the user profile, set the user parameter /OTX/PF03_WP_DISPLAY to the
value LIST. If you do not set this parameter, the list will only appear if
10 or more work centers are available for the user.
• Users might be authorized for only one work center. In this case, the
work center list is not visible, but the user’s work center is selected
directly.
Navigation - Nodes
Nodes provide access to one or more different work objects and different data in
a structured way. Access is provided according to the configured selection
criteria. Nodes can be displayed statically according to the configuration. They
can also be determined dynamically during runtime.
Work Object Functions
For each work object, you can maintain functions. A function can call a
transaction, a report, or any other implemented logic, according to the work
object.

Work Object List
The work object list shows you all data for a specific work object’s node. The
data is displayed in an ALV table view. In the work object list, you can have
different actions. They can be executed for one work object type.
Selection
For each work object, you can define a selection screen to execute a selection.
Therefore, the pre-selected list of work objects according to the node will be
selected. Thereby, the additional selection parameters of the selection screen are
used.
Detail Pane
Additional work object context information is displayed in the detail pane area.
Therefore, the processing plug-in concept is used. For more information, see
“Configuring plug-in integration” on page 24.
Access To access the Business Center Workplace, run the /n/OTX/PF03_WP transaction. For
a description how to work with the Business Center Workplace as an end user, see
Section 2 “Business Center Workplace” in OpenText Vendor Invoice Management for
SAP Solutions - User Guide for Solutions Beyond Invoice (BOCP200400-UGD).
Important
To use Business Center Workplace in a proper way, a minimum screen
resolution of 1600 x 900 is required.
This section provides information how the Business Center Workplace is configured.
This happens in the Workplace Configuration branch of the /n/OTX/PF00_IMG
transaction.

8.1 Work object types

A work object type represents a processing object within the Business Center
Workplace. Thereby the work object type can represent a process object, a SAP
business object, or information from any SAP tables.
A work object is defined by the data selection, by the display of the data, and by
actions and functions.
8.1.1 Defining work object types

In this step, you define the selection, display, and processing of work objects.
To define work object types:
2. Click OpenText Business Center for SAP Solutions > Workplace

Configuration > Work object types > Work object types.
3. In the Work Object Types Overview screen, double-click a work object type.

8.1. Work object types
4. Define the work object type, using the following parameters:
Description
Enter a meaningful description of the work object type.
Authorization Exit
Enter the exit for additional authorization checks. This exit implements
interface /OTX/PF03_IF_AUTH_WOBJ_TYPE. For more information, see
“Authorization Exit” on page 233.
Handler class
Enter the class for data selection. This class is called for the selection of data
for the work object type. The class implements the /OTX/PF03_IF_WOBJ_
HANDLER interface. Class /OTX/PF03_CL_DATA_HANDLER_DYN allows a
dynamic data selection without implementation effort. For more
information, see “Handler class” on page 235.
Important
OpenText strongly advises against using the dynamic data handler for
the data access in remote systems. In case of data selection from
remote systems, you must create your own implementation of the /
OTX/PF03_IF_WOBJ_HANDLER interface.
Selection Exit
Enter the user exit to adjust the selection or the selection results before and
after the selection. Interface: /OTX/PF03_IF_CHANGE_SELECT. For more
information, see “Selection Exit” on page 237

Display class
Enter the class for the display of selected objects of the work object type, for
example in the ALV grid or in the tree. This class also displays information
in the detail pane. The class implements the /OTX/PF03_IF_UI_DATA_VIEW
interface. Class /OTX/PF03_CL_DATA_VIEWER_ALV allows a dynamic object
display without implementation effort. For more information, see “Display
class” on page 239.
Class: Change ALV

Enter the exit to change the ALV layout. This is only used if the /OTX/PF03_
CL_DATA_VIEWER_ALV class is used as display class. For more information,
see “Class: Change ALV” on page 242.
Display structure
Enter the display structure to define the fields of the work object.
Important
The display structure must have the following fields:
Field name Data Type

WOBJ_ID /OTX/PF03_E_WOBJ_ID
WOBJ_LOGSYS LOGSYS
Item structure
Define the display structure of the items.
Variant handle
Enter the identification number (Handle ID). If the same display class is
used in several work object types, this number allows to save work object
type specific variants for ALV grids.
If you use the /OTX/PF03_CL_DATA_VIEWER_ALV display class, set this
parameter. It must be unique.
Data selection structure

Enter the structure to define the selection fields. These fields can be
considered as selection conditions by the Handler class. The display
structure will include text fields that should not be used as selection fields.
Report ID screen
Enter the report that contains the selection screen. For more information, see
“Report ID screen” on page 244.
Screen number
Enter the Dynpro number that shall be called for the display of the selection
screen. Before and after displaying the selection screen, there is a certain
processing logic, dependent on the structure of the selection screens.
Selection screens are normally generated. Therefore, this logic cannot be
implemented directly in the selection screen. The selection screen is not
called directly but it is wrapped with another screen.

Variant screen
Enter the actual Dynpro number of the selection screen. This number is set
in the dialog boxes for processing variants. It saves the user from selecting
the correct screen if several selection screens are linked with the Report ID
screen program.
Display details
Select this check box to display the detail pane when initially calling the
Business Center Workplace with the related work object.
Plug-In Type
Enter the plug-in type that should be displayed in the detail pane. The plug-
in type is used by the /OTX/PF03_CL_DATA_VIEWER_ALV class. For more
information, see “Configuring plug-in integration” on page 24.
Plug-In ID
Enter the plug-in ID that is selected by default.
8.1.1.1 Field details in work object type customizing

This section provides details about the fields that are available in work object type
customizing.
8.1.1.1.1 Authorization Exit
This customizing allows you to activate a work object type specific user exit for
authorization checks. This exit is called after the check on the standard authorization
object J_6NPF_WTY. You can overwrite the result of the standard authorization check
with this user exit. This user exit implementation needs to implement interface /
OTX/PF03_IF_AUTH_WOBJ_TYPE.
Methods of interface /OTX/PF03_IF_AUTH_WOBJ_TYPE
CHECK_WOBJ_TYPE
This method checks the authorization for the current work object type. This
check is performed when the navigation tree contains nodes which are related to
a work object type. Nodes with a work object type that the user is not authorized
for are not displayed.
The following table shows the parameters that are available:

PC_AUTHORIZED Changing User is authorized or not. This parameter
contains the result of the standard
authorization check, which can be
overwritten by the user exit.
CHECK_ACTIONS
This method checks the authorization for an action of the work object type. This
check is performed at the display of work objects and before performing an

action. Actions that the user is not authorized for are not transferred to the
display class.

PI_ACTION Importing Action ID
PI_NODE_ID Importing Node in which the action will be available
(optional)
CHECK_NODE
This methods checks the authorization for a node which is related to the work
object type. This check is performed when the navigation tree contains nodes
which are related to a work object type. It is also called for nodes requested by
web services. Nodes that the user is not authorized for are not displayed.

PI_NODE_ID Importing Node ID
CHECK_FUNCTION
This method checks the authorization for work object type functions. This check
is performed when a node that is related to a work object type is selected in the
navigation tree. Only the functions that the user is authorized for are available.

PI_FUNCTION_ID Importing Function ID

8.1.1.1.2 Handler class
For the data selection, each work object type needs a handler class. The standard
handler class is /OTX/PF03_CL_DATA_HANDLER_DYN. This class selects the data as
defined in the dynamic data selection. Using the selection exit enables you to change
the result of the data selection. For more information, see “Defining dynamic data
selection” on page 251.
Alternatively, you can implement your own handler class with interface /OTX/PF03_
IF_WOBJ_HANDLER. Therefore, you must implement the following methods of this
interface:
Methods of interface /OTX/PF03_IF_WOBJ_HANDLER
GET_INSTANCE
This method returns the instance of the handler class.

PI_CLASSNAME Importing Name of the implementing class
PRH_INSTANCE Returning Handler class instance
GET_NUMBER_OF_ENTRIES
This method returns the number of entries for display in the navigation tree.

PIT_SEL Importing Selection criteria for entries
PI_COUNT_MODE Importing Indicates which entries must be
counted. Possible values:
BOTH or ALL - Return only
number of all entries
SINGLE - Check if at least one
entry exists
PE_ENTRIES Exporting Number of entries
SELECT_DATA
This method returns data objects.

PIT_SEL Importing Selection criteria
PI_MAX_HITS Importing Number of hits that should be
selected


PI_SELECT_MODE Importing Selection mode:
COUNT: Only count entries, return
no data
DATA: Only return data
BOTH: Count and return data
PIT_ORDER_BY Importing Order by criteria. This parameter
should be used for selection so that
the user gets the most important
entries if the number is restricted.
Note: This parameter might

contain the value PF07_
DEFAULT in the FIELDNAME
field. In this case, the value of
the TABNAME field is empty.
This indicates that, in the Fiori
Task App, the user changed
from a specific sort order back
to the default sort order. The
parameters of the default sort
order are also included in the
PIT_ORDER_BY parameter.
PE_ENTRIES Exporting Number of entries
PET_DATA Exporting Data
Parameter PET_DATA is a table of structure /OTX/PF03_S_DATA, which has the

following fields:
Component Description
LOGSYS Logical system ID
ATTRIBUTES Data
Expected is the “Display structure” of the work object type.
GET_OBJECTS
This method converts the selected data to instance of class /OTX/PF03_CL_WOBJ.

PIT_DATA Importing Selected data
PRT_OBJECTS Returning Work objects
Note: The most efficient way to implement your own handler class is probably
to inherit from class /OTX/PF03_CL_DATA_HANDLER_DYN. In this case, a
redefinition of the methods SELECT_DATA and GET_NUMBER_OF_ENTRIES
should be sufficient.

Additional methods of interface /OTX/PF03_IF_WOBJ_TYPE – The methods GET_

SELECTION_FMODULE and GET_LOGSYS support a simple redefinition of class /OTX/
PF03_CL_DATA_HANDLER_DYN.
GET_SELECTION_FMODULE
This method returns the name of the function module that is used for the data
selection. The standard implementation of class /OTX/PF03_CL_DATA_HANDLER_
DYN uses function module /OTX/PF03_DATA_SELECT_DYNAMIC for the data
selection. You can copy this function module and implement your own data
selection method.
Important
Do not change the parameters of the function module.
Parameter Parameter type Definition

PR_FMODULE Returning Function module name
GET_LOGSYS
This method returns the logical systems that are used for the data selection. The
standard implementation of class /OTX/PF03_CL_DATA_HANDLER_DYN returns all
logical systems defined for the VIM Foundation. For more information, see
“Configuring logical systems” on page 23. If you want to restrict the logical
systems for a specific work object type, you can redefine this method and restrict
the logical systems.
Parameter Parameter type Definition

PRT_LOGSYS Returning Logical systems
8.1.1.1.3 Selection Exit
The user exit for data selection is available in the Selection Exit field in work object
type customizing. This user exit enables you to influence the selection criteria before
the data selection and to filter or change the results after the data selection. You
must implement the /OTX/PF03_IF_CHANGE_SELECT interface for this exit.
Methods of interface /OTX/PF03_IF_CHANGE_SELECT
CHANGE_SELECTION_CRITERIA
This method allows to change the selection criteria before the data selection is
performed.

PCT_SEL Changing Selection criteria


PC_MAX_HITS Changing Maximum hits
PCT_ORDER_BY Changing Order by criteria
PI_APP_MODE Importing Set to true (“X”) when the exit has
been called from the BC Fiori Task
App.
PIS_WOBJ_TYPE Importing Work object type as customized in
current (remote) system
CHANGE_SELECTION_RESULT
This method is called after the data selection. It allows to restrict the data (for
example because of authorization checks) and to add data (for example texts).

PIT_SEL Importing Selection criteria used for the data
selection
PI_MAX_HITS Importing Maximum number of hits
PIT_ORDER_BY Importing Order by criteria
PCT_DATA Changing Selected data; table has structure of
“Display structure” of the work object
type.
PC_ENTRIES Changing Number of entries
App.
CHANGE_NUMBER_OF_ENTRIES
This method is called when the number of entries is required for a node. It
allows to change the number of entries.

PIT_SEL Importing Selection criteria for entries
App.


CHANGE_DYNAMIC_SELECTION
This method is only called if the /OTX/PF03_CL_DATA_HANDLER_DYN class is
used as data handler. It is called in function module /OTX/PF03_DATA_SELECT_
DYN_RFC, which performs the data selection for this data handler. When you
select data from a remote system, this exit allows you to perform a check of the
selected data in the remote system before the data is transferred to the system
from which the call was started.

PI_MAX_HITS Importing Maximum hits
PI_SELECT_MODE Importing Selection mode:
COUNT: Only count entries, return
no data
DATA: Only return data
BOTH: Count and return data
PIH_SEL_STATEMENT Importing Class with information for dynamic
data selection (as customized in
dynamic data selection)
PCT_DATA Changing Selected data with structure of
“Display structure” of work object
type
PCT_RETURN Changing Messages
PC_ENTRIES Changing Number of selected entries
App.
8.1.1.1.4 Display class
As display class for the data of a work object, you can either use the standard class /
OTX/PF03_CL_DATA_VIEWER_ALV, which displays the work objects in an ALV grid.
The standard class can be customized widely. But you can also implement your
custom class for displaying work objects. OpenText recommends that you use
class /OTX/PF03_CL_DATA_VIEWER_ALV.
The custom class must implement the /OTX/PF03_IF_UI_DATA_VIEW interface with

the following methods:

Methods of the /OTX/PF03_IF_UI_DATA_VIEW interface
GET_INSTANCE
This method returns an instance of the data viewer class. The workplace main
application will then use this instance.

PIH_DATA_CONTAINER Importing Container for data pane
PIH_DETAILS_CONTAINER Importing Container for detail pane
PI_DISPLAY_CLASS_NAME Importing Name of display class
PRO_INSTANCE Returning Instance of display class
SET_WOBJ_TYPE
This method sets the work object type of the currently selected node.

PIS_WOBJ_TYPE Importing Work object type
DISPLAY_DATA
This method is called by the framework when a node for this work object type
has been selected and the data for this node should be displayed. The structure
of the PIS_WOBJ_TYPE parameter contains the information about the actions that
are possible for this data. These actions should be made available by the data
viewer.

type
customizing
PIS_NODE_INFO Importing Node information
PIH_DATA_CONTAINER Importing Container for data pane
PIH_DETAILS_CONTAINER Importing Container for detail pane
PIT_DATA Importing Data
PIS_WPLACE Importing Work center
to be displayed
PIT_ORDER_BY Importing Order by criteria (data
should be displayed sorted
this way)
PI_SEL_SCREEN_PARA_APPLIED Importing Data selection restricted by
parameters of selection
screen


type
PIT_ACTION_RESTRICTIONS Importing Action restrictions on node
level
PIT_FIELD_RESTRICTIONS Importing Fields that should not be
displayed
PI_UI_CONTROLLER_CHANGED Importing UI controller has changed.
If the display class is used
for different work object
types, a refresh is probably
required.
FREE
This method destroys all objects of the data viewer and the instance.
DETAILS_AVAILABLE
The workplace main program checks with this method if the detail pane is
available. If the display class returns in the DETAILS_AVAILABLE method that the
detail pane is not available, the main program will, for example, not offer the
function Display Detail Pane. The standard implementation, for example, sets
the detail pane to not available if no plug-ins are customized for this work object
type.

PR_DETAILS_AVAILABLE Returning Flag if details are available
The /OTX/PF03_IF_UI_DATA_VIEW interface also provides the following events to

react on user inputs.
USER_COMMAND
Use this event to trigger an action for a work object.
Parameter Description
PI_ACTION Action ID
PI_WOBJ_ID Work object ID
CHANGE_NUMBER_OF_HITS
If the user requires a different number of hits, use this event to send the new
number of hits to the workplace main program. The node is then refreshed with
the new number of hits.
PI_HITS Number of hits

8.1.1.1.5 Class: Change ALV
You can use this user exit to change the layout of the ALV grid that is generated by
the /OTX/PF03_CL_DATA_VIEWER_ALV class (field Display class in work object type
customizing).
This user exit is called by the /OTX/PF03_CL_DATA_VIEWER_ALV class. It allows to

change the overall appearance of the ALV grid containing the work object types. The
class for this user exit needs to implement the /OTX/PF03_IF_CHANGE_ALV interface.
Methods of the /OTX/PF03_IF_CHANGE_ALV interface
CHANGE_EXCLUDES
Change the excluded functions.

PIS_NODE_INFO Importing Current node
PIT_DATA Importing Data that will be displayed in the
ALV grid
PIS_WORKPLACE Importing Current work center
PCT_EXCLUDES Changing Functions that will be excluded.
Functions added to this table will not
be available in the ALV grid.
CHANGE_FCAT
Change the field catalog of the ALV grid, for example remove or add fields.

ALV grid
PCT_FCAT Changing Field catalog of the ALV grid
CHANGE_VARIANT
Change settings for variant usage.



ALV grid
PCS_VARIANT Changing Variant settings
CHANGE_LAYOUT
Change layout settings.

ALV grid
PCS_LAYOUT Changing Layout settings
CHANGE_TITLE
Change the ALV grid title. The default ALV grid title is the node description.

ALV grid
PC_TITLE Changing ALV grid title
CHANGE_FIELD_VALUES
Change or add field values. All fields available in the display structure of the
work object type will be prefilled with the selection result of the work object
handler.
Note: Use this exit only for ALV grid specific fields. For adding texts and
other general data, use the Selection Exit (interface /OTX/PF03_IF_
CHANGE_SELECT).

PCS_FIELDS Changing Display structure of work object type

8.1.1.1.6 Report ID screen
This report provides solution or customer specific selection screens for work object
types.
A selection screen allows the user to restrict the objects of a node by further selection
criteria. Selection criteria of the node cannot be overwritten. This means it is only
possible to restrict the selection by further criteria but not to disable selection criteria
defined for the node.
You need a custom program and screen that contain the selection criteria and
parameters.
Tip: A dynpro with several subscreen areas enables you to show select options
and parameters in parallel. Check sample report /OTX/PF32_IDF_SEL_SCREEN
with screen 100.
In the PBO and PAI modules of this selection screen (check sample screen 100 of
the /OTX/PF32_IDF_SEL_SCREEN report), you also must handle the logic for the
following purposes:
• to transfer the selection criteria used by the workplace main program to your
selection screen
• to transfer the selection criteria entered by the user on the selection screen to the
workplace main program
For this communication, the /OTX/PF03_CL_UI_SEL_SCREEN class is used.
Methods of the /OTX/PF03_CL_UI_SEL_SCREEN class
GET_CURRENT_INSTANCE
This method returns an instance of the class. This instance contains information
about the selection criteria of the currently selected node and previously added
parameters.

PRH_INSTANCE Returning Class instance
SET_SELECTION_CRITERIA
Use this method to make the selection criteria entered in the selection screen
known to the /OTX/PF03_CL_UI_SEL_SCREEN class. The workplace main
program uses this method to set the initial selection criteria of the current node.

PIT_SEL_CRITERIA Importing Selection criteria
PI_APPLIED Importing Selection is applied

GET_SELECTION_CRITERIA
With this method, you can get the currently used selection criteria. With the first
call, this is only the selection criteria of the current node. With later calls, these
are the selection criteria of the node with additional criteria from the selection
screen.
The selection criteria can contain criteria for selection parameters available on
the screen. In this case, these values should be set in this criteria. The selection
criteria originally defined for the current node can not be overwritten. Therefore,
these selection criteria should additionally be set to not editable.

PRT_SEL_CRITERIA Returning Selection criteria
EXECUTE_USER_ACTION
This method raises an event, which is handled by the workplace main program.

PI_ACTION Importing ID of the event that should be raised.
Currently only the ID SEARCH is available.
PARAMETER_TO_SELOPT
This method converts the select option from external format (entered in the
selection screen) to the internal format, which can be used for data selection. All
selection criteria that you are transferring via the SET_SELECTION_CRITERIA
method must have the internal format.

PIS_PARAM Importing Select option/parameter
PI_ATTRIBUTE Importing Attribute name
PRS_SEL Returning Selection criteria
SELOPT_TO_PARAMETER
This method transfers a selection criteria to the format of a select option or
parameter.

PIS_SEL Importing Selection criteria
PES_PARAM Exporting Select option/parameter
GET_NODE_SEL_CRITERIA
This method returns the original selection criteria of the current node.


PRT_SEL_CRITERIA Returning Selection criteria
General logic Before the call of your selection screen, the workplace main program transfers the
currently used selection criteria to the instance of the /OTX/PF03_CL_UI_SEL_
SCREEN class. The workplace main program also sets the selection criteria of the
current node.
The workplace main program ignores any changes to the selection criteria of the
current node. This means you can only restrict the result list for the current node but
you cannot select other objects as originally customized for this node. For this
reason, make sure to prevent the change of the node selection criteria at the selection
screen. In the AT-SELECTION-SCREEN section, the select-options that are used in the
selection criteria of the current node (GET_NODE_SEL_CRITERIA method) can be read,
and these select-options can either be disabled or hidden.
In the PBO module, you must set the currently used selection criteria.
• GET_SELECTION_CRITERIA method to get them

• SELOPT_TO_PARAMETER method to transfer them to the select option format
In the PAI module, you must handle the customer actions, for example the execution
of the search. You must make the selection criteria from the selection screen known
to the /OTX/PF03_CL_UI_SEL_SCREEN class:
• PARAMETER_TO_SELOPT method to transfer the selection criteria to the correct

format
• SET_SELECTION_CRITERIA method to set the selection criteria
Then you raise the SEARCH action using the EXECUTE_USER_ACTION method.
8.1.1.2 Defining actions for a work object type

In this step, you define actions that are available for a work object type. Actions are
functions that can be performed on a work object while the work object is displayed
using the display class.
To define actions for a work object type:

3. In the Work Object Types Overview screen, mark a work object type, and then
double-click Actions in the Dialog Structure.

4. In the Actions Overview screen, define actions, using the following parameters:
Action
Enter the ID of the action.
Button type
Define the display of the action in the ALV grid. Possible values:
• Button in ALV toolbar

• Button in ALV row
Field must have type CHAR50 (character with length 50).
• Hyperlink in ALV row
Button column
Enter the column in which the action should be displayed as hyperlink or
inline button.
Type
Define the action type. Possible values:
• Standard
• Bulk
• Emphasized Bulk: most important bulk actions, with a separate button
in the ALV grid control
Action class
Enter the action class, implementing class interface /OTX/PF03_IF_ACTION.
For more information, see “Interface /OTX/PF03_IF_ACTION” on page 248.
Default
Select this check box to mark the action as default action. If the /OTX/PF03_
CL_DATA_VIEWER_ALV class is used as display class, this action will be
performed at a double-click on the ALV grid line.

Icon ID
Enter the icon for the action.
Icon text
Enter the text for the action.
Position
Define the sort order of the available actions of type Button in ALV
toolbar. The buttons are sorted in the ALV toolbar by their position value.
The display class of the work object type must provide the actions to the user.
Therefore, it depends on the implementation of the display class if and how the
actions are provided.
The /OTX/PF03_CL_DATA_VIEWER_ALV class automatically considers this
customizing.
To define message fields for bulk actions:
1. In the Actions Overview screen, mark an action, and then double-click Message
fields for bulk actions in the Dialog Structure.
2. In the Message fields for bulk actions Overview screen, enter one or more field
names (of the display structure) that are relevant for the end user in the context
of bulk action messages. The entered fields are displayed in success or error
messages that users get when performing bulk actions.
Example: You can enter the registration ID of the incoming document or the customer
name to be displayed in messages.
8.1.1.2.1 Interface /OTX/PF03_IF_ACTION
EXECUTE_ACTION method
Called at the execution of single and bulk actions.

PI_BULK Importing Action is a bulk action
PI_ACTION Importing Action of application
PE_EXECUTE_REFRESH Exporting Refresh object list
PCT_ACTIONS Changing Messages for the executed actions
Exception /OTX/CX_PF03_EXCEPTION can be raised. The message of this

exception is then displayed.
CHANGE_MESSAGE_DISPLAY method
Called before the display of the messages returned in PCT_ACTIONS (EXECUTE_
ACTION method). You can change the display options. Messages are displayed in
an ALV Grid in a dialog box. This dialog box is not displayed for a success
message for a single action.


PIT_ACTIONS Importing Executed actions with messages
PCT_FCAT Changing Field catalog for the ALV Grid
PCT_DATA Changing Displayed data
8.1.1.3 Defining functions for a work object type

In this step, you define the functions that are available for a work object type.
Functions are global actions that are not related to one specific work object type
using the display class. A function allows to access transactions, reports, or jobs that
are related to the work object type as a whole. For example for Sales Orders, call the
VKM1 transaction to display all blocked sales orders.
To define functions for a work object type:

double-click Functions in the Dialog Structure.
4. In the Functions Overview screen, define functions, using the following

parameters:
Function ID
ID of the function
Function Module
Enter a function module that implements the functionality of the function.
The interface of the function module has no parameters.
Description
Enter a description for the function.

8.1.1.4 Defining ALV grid field settings

In this step, you define the display of fields in the ALV grid, display class /OTX/
PF03_CL_DATA_VIEWER_ALV.
To define ALV grid field settings:

double-click ALV Grid Field Settings in the Dialog Structure.
4. In the ALV Grid Field Settings Overview screen, define the settings, using the
Field Name
Name of the field in the display structure
Key Field
Select this check box to mark the field as key field. The field will be
highlighted in the ALV display as key field, and the column will be fixed.
Style
Define the field style. Possible values:
• None
• Hyperlink
• Icon
• Checkbox
Status
Define the field status. Possible values:
• Display
• Hide
• Available
Column width
Enter the column width.
This parameter defines the width of the column in the ALV table control
layout for display.
Column no.
Enter the column position.
This parameter defines the default position of the column in the ALV table
control layout for display.

The display class of the work object type must provide the field settings.
The /OTX/PF03_CL_DATA_VIEWER_ALV class automatically considers this
customizing.
8.1.1.5 Defining the number of hits for the ALV grid

In this step, you define custom settings for the number of hits list. This is only used
if the standard ALV grid class /OTX/PF03_CL_DATA_VIEWER_ALV is used as the
display class of the work object type. If you do not maintain the customizing, the
standard configuration is used.
To define the number of hits for the ALV grid:

double-click ALV Grid - Number of hits in the Dialog Structure.
4. In the ALV Grid - Number of hits Overview screen, define the settings for the
number of hits using the following parameters:
ID for number of hit entry

ID for an entry in the number of hits list.
Default number of hits
Enter the default number of the entry.
Text
Enter the text that is displayed for the entry in the number of hits list.
8.1.2 Defining dynamic data selection

In this step, you define the data selection (join) for the data handler class /OTX/
PF03_CL_DATA_HANDLER_DYN.
To define dynamic data selection:

Configuration > Work object types > Dynamic data selection.

3. Basic Settings
In the Work Object Type Overview screen, mark a work object type, and then
double-click Basic Settings in the Dialog Structure.
4. In the Basic Settings Details screen, refine the dynamic data selection and
counting, using the following parameters.
Use ‘DISTINCT’
To determine that the selection will be executed with DISTINCT statement,
select this check box. This means that entries which have the same values in
all selected fields are only displayed once.
Counting field
The counting of entries will only count entries that have different values in
this field. For the counting, this provides the same logic as the DISTINCT
statement for the data selection.
Example: Process steps might be assigned to several users. If you want to show personal
tasks (process steps) for a user, you must include the table with the user assignment in
the dynamic data selection definitions. However, for nodes that are not restricted for a
user, this would mean that a process step is displayed several times (for each user
assignment). You can handle this case by activating the DISTINCT statement and using,
for example, the process step ID as counting field.
5. Tables
double-click Tables in the Dialog Structure.
6. Enter all tables that are used for data selection, using the following parameters.

Table name
Enter the name of the table.
Alias
Enter the table alias. Each table must have a unique alias, for example A, B,
or C.
7. Table joins
double-click Table joins in the Dialog Structure.
8. Define how tables are joined, using the following parameters.
Left table
Enter the table that should be joined.
Right table
Enter the table that joins.
Outer join
Select this check box to achieve that an outer join is used if possible. This
means that the fields of the right table are not used in the selection criteria.
9. Join conditions
In the Table joins Overview screen, select an entry, and then double-click Join
conditions in the Dialog Structure.
10. Define the join conditions for the table join, using the following parameters.
Left table
Table that should be joined
Right table
Table that joins
Field of left table
Field of the table that should be joined
Field of right table
Enter the field of the table that joins.
11. Table fields

double-click Table fields in the Dialog Structure.
12. Define the table fields to be selected, using the following parameters.
Table Name
Name of the table
Field Name
Name of the field

8.1.3 Defining the work object type association

In this step, you define the relationships between work object types. For example,
you can use an association to define the relationship between a header object and its
line items. In the data binding for view view.item.AdvLineItems of the Fiori Task
App, this association can then be used to display these line items. For more
information, see “Configuring advanced line items binding in the Perspective
Editor” on page 335.
To define the association of work object types:

Configuration > Work object types > Work Object Type Association.
3. On the Work Object Type Association screen, define the work object type
association, using the following parameters:
Association Name
ID of the association
Workobject type
Parent work object type
Associated work object type
Associated work object type
Card.
Cardinality of the relationship (1:1 or 1:N )
4. Association Constraints
Mark an association, and then double-click Association Constraints in the
Dialog Structure.
5. On the Association Constraints Details screen, define the field relationships of

the selection structures of the 2 work object types. These definitions are used to
select the associated work objects for a parent work object. Use the following
parameters:
Field Name
Field name of the parent work object type
Associated Field
Field name of the associated work object type
6. Additional Constraints
Double-click Additional Constraints in the Dialog Structure
7. On the Additional Constraints screen, configure additional constraints to

restrict the associated work objects, using the following parameters:

8.2. Exit for dynamic filter criteria
ID
Criteria ID. Provide a unique ID for each criteria.
Attribute
Attribute of the associated work object type. Enter the field of the Data
selection structure of this work object type.
Sign
Enter I or E for an (I)nclude or (E)xclude condition.
Option
Enter the option of the condition (EQ, BT, NE, …)
Value low
Enter the lower selection value.
Value high
Enter the higher selection value.
Exit for dynamic filter criteria

Enter a user exit that allows adjusting the filter criterion dynamically at
runtime or replacing the filter criterion by one or more filter criteria. This
enables you to consider the current user or date in the filter criteria. This
exit must implement /OTX/PF03_IF_SEL_CRITERIA. For more information,
see “Exit for dynamic filter criteria” on page 255.
8.1.4 Checking the configuration of work object types

You can check the configuration of selected work object types with the transaction /
OTX/PF63_CHECK.
Select the WorkObjectType on the selection screen.
The report checks for the selected work object types and displays the results in a list.
When executed, this report checks the J_6NPF_ADM authorization object, J_6NPF_
COM (Component) field, for the value 4 (Web UI).
8.2 Exit for dynamic filter criteria

Sometimes you must define nodes that have selection criteria that can fully be
determined at runtime; for example, a node that shows only tasks assigned to the
current user or tasks that were created within the last 30 days. For this reason, the
Exit for dynamic filter criteria is available. This exit is called before the data
selection of the node. It allows to change the selection criteria so that system
parameters like user name or current date can be considered in these criteria.
This exit implements the /OTX/PF03_IF_SEL_CRITERIA interface, which contains

the CHANGE_SEL_CRITERIA method with the following parameters.

PIS_WOBJ_TYPE Work object type customizing
PIS_NODE Configuration of current node
PI_SEL_CRITERIA_TYPE Type of selection criteria:
NORM: Normal entries
PIS_DYNAMIC_NODE Dynamic node configuration - only filled if the exit is
called in the context of a dynamic node
PCT_SEL Selection criteria of the node. Prefilled with the
customized selection criteria.
8.3 Navigation
The navigation defines the particular queues and folders in the Business Center
Workplace. Within the Business Center Workplace, the navigation defines the
specific data selection within a queue. It also defines the hierarchical levels and the
global structure of the Business Center Workplace. Nodes are also used in the Fiori
Task App.
Customizing the navigation comprises the following steps:
• “Defining nodes” on page 256

• “Defining the navigation structure” on page 261
• “Defining work centers” on page 265
8.3.1 Defining nodes

In this step, you define the nodes that can be used in a navigation structure. Further
customizing is necessary for filter criteria, order by, action restrictions, and field
restrictions, which are described in subsections.
To define nodes:

Configuration > Navigation > Nodes.

8.3. Navigation
3. Define nodes, using the following parameters.
Node ID
Unique ID of the node
Workobject type
Work object type that is processed by the node if data access is available.
Structural nodes without work object types are possible, as well.
Active
Select this check box to activate a node in order to display it in the Business
Center Workplace. Clear the check box to deactivate the node.
Node description
Enter the text that is displayed in the structure for the node.
Userexit for dynamic nodes
Enter the user exit that allows to add one or more nodes at runtime. In a
navigation structure, this node replaces the current node. This exit must
implement the /OTX/PF03_IF_DYNAMIC_NODE interface. For more
information, see “User exit for dynamic nodes” on page 260.
The detailed configuration of the nodes for restrictions, filter, and order criteria
are implemented in the delivered handler class /OTX/PF03_CL_DATA_HANDLER_
DYN and display class /OTX/PF03_CL_DATA_VIEWER_ALV. A custom data handler
or display handler must implement corresponding logic to use all additional
settings.

8.3.1.1 Defining filter criteria

In this step, you define filter criteria that define which data should be displayed for a
node.
To define filter criteria:
1. In the Nodes Overview screen, select a line, and then double-click Filter criteria
in the Dialog Structure.
2. In the Filter criteria Overview screen, define the filter criteria, using the
ID
Criteria ID. Enter the ID of the filter condition (values: 00 to 99)
Each entry is taken into account with an OR connection. For different
attributes, an AND connection is used.
Attribute
Enter the field of the Data selection structure of this work object type.
Sign
Enter I or E for an (I)nclude or (E)xclude condition.
Option
Enter the option of the condition (EQ, BT, NE, …)
Value low
Enter the lower selection value.
Value high
Enter the higher selection value.
Exit for dynamic filter criteria
Enter a user exit that allows adjusting the filter criterion dynamically at
runtime or replacing the filter criterion by one or more filter criteria. This
enables you to consider the current user or date in the filter criteria. This
exit must implement /OTX/PF03_IF_SEL_CRITERIA. For more information,
see “Exit for dynamic filter criteria” on page 255.
8.3.1.2 Defining the order

In this step, you define field and direction by which the data is ordered at data
selection and dynpro.
To define the order:
1. In the Nodes Overview screen, select a line, and then double-click Order by in
2. In the Order by Overview screen, define Order by, using the following
parameters.

8.3. Navigation
Priority
Order priority
Table Name
Name of the table from which the field is selected
Field Name
Name of the selected field
Asc./Desc.
Select the sort order: Descending or Ascending
8.3.1.3 Defining action restrictions

In this step, you define actions that are generally available for the work object type
but should not be available at this node.
To define action restrictions:
1. In the Nodes Overview screen, select a line, and then double-click Action
restrictions in the Dialog Structure.
2. In the Action restrictions Overview screen, define the actions that should not
be available, using the following parameter.
Action
ID of the action that should be excluded
8.3.1.4 Defining field restrictions

In this step, you define fields of the display structure that should not be displayed at
this node. For the /OTX/PF03_CL_DATA_VIEWER_ALV display class, this refers to
fields that are defined as visible in the ALV Grid Field Settings customizing.
To define field restrictions:
1. In the Nodes Overview screen, select a line, and then double-click Field
restrictions in the Dialog Structure.
2. Define field restrictions, using the following parameter.
Field Name
Name of the field that should be excluded

8.3.1.5 User exit for dynamic nodes

Dynamic nodes enable you to add and change nodes at runtime. You just need a
class which uses the /OTX/PF03_IF_DYNAMIC_NODE interface. In the SET_DYNAMIC_
NODES method, you must implement the logic how the node should be changed and
which nodes should be added.
The following table shows the parameters of the SET_DYNAMIC_NODES method.

PIS_TOP_NODE Importing Customizing of the top node
PIS_NODE Importing Customizing of the current node
(which has the dynamic node exit)
PRT_DYNAMIC_NODES Returning Dynamic nodes that you want to
add to the navigation tree
The import parameter PIS_TOP_NODE provides all available information about the
top node under which your dynamic nodes will be added. This enables you to
determine the positions of the nodes in the tree. With parameter PIS_NODE, you get
the customizing of your dynamic node because it is customized in the navigation
structure. You must transfer the complete customizing that should be used for the
dynamic nodes to the PRT_DYNAMIC_NODES parameter. Only the content of this
parameter defines the dynamic nodes. Nevertheless OpenText recommends that you
define the node in the customizing as detailed as possible so that you can simply
copy these parts to the dynamic nodes.
The PRT_DYNAMIC_NODES parameter is a table with the following structure.
DISPLAY_POS Position which this node should have (in relation to the
other added nodes)
WOBJ_TYPE Work object type
DISPLAY_NUMBERS Indicator if number entries are displayed next to the
folder in the tree. Possible vales:
CURR: number of entries of current node
SUB: number of entries for all sub nodes which have
option CURR
<space>: number of entries is not displayed
DESCRIPTION Text of the node
NODE_ICON Icon to be shown in front of the node
DEF_SEL_SCREEN Selection screen is displayed by default.
DISPLAY_DATA Display data for this node
DEFAULT_NODE This node is a default node. At the initial display of the
navigation tree, this will be marked and the data will be
displayed.

8.3. Navigation
DISP_NODE_WO_DAT Show node also if no data is available for this node or
any of its sub-nodes.
DOWN_CRIT Inherit selection criteria of this node to all of its sub
nodes.
SEL_CRITERIA Selection criteria for data of this node
ORDER_BY Criteria for ordering the data of this node. Data will also
be selected in this order.
FIELD_RESTRICTIONS Field restriction. Define which fields, that normally
available for this work object type, should not be
displayed at this node.
ACTION_RESTRICTIONS Define the work object type actions which are not
available for this node.
8.3.2 Defining the navigation structure

In this step, you define the order of nodes within a structure. You can optionally
map the nodes of the first and second structure level by filter options. A structure
can have a maximum depth of 5 levels.
To define the navigation structure:

Configuration > Navigation > Navigation structure.
3. In the Configuration Overview screen, define the navigation structure, using

the following parameters.
Configuration ID
ID of the structure
Configuration description
Enter description text.

Type
Select the filter type. The following options are available.
<Empty> (no value)

Default option. No filter is displayed.
Filter for work object types

This setting activates the 1st filter option for the work object types of the
top level node (nodes of level 0). The filter offers the work object types
of the nodes of level 0.
Example: If you have different work object types (for example Sales Order or
Quotation), you will get these work objects as filter criteria for your work
center.
Filter on node level

This setting activates the 1st filter option for the top level nodes (nodes
of level 0). The filter offers the nodes of level 0.
Example: If you have different nodes on top level 0 to show different

information (for example vendor or customer) you can use all nodes of level 0
as filter criteria for your work center.
2nd filter
Select this check box to activate the 2nd filter option.
• The 1st filter option is set to Filter for work object types. In this
case, the 2nd filter offers those nodes on level 1 that are assigned to the
work object type chosen in the 1st filter.
• The 1st filter option is set to Filter on node level. In this case, the 2nd
filter offers those nodes on level 2 that have the node chosen in the 1st
filter as top node.
Selecting this check box without selecting a Type has no effect.
Filter Label
Enter text for the label of filter option at node level 1.
8.3.2.1 Defining top nodes on level 0

In this step, you define the top level of the structure.
To define top nodes:
1. In the Configuration Overview screen, select a line, and then double-click Top
nodes - level 0 in the Dialog Structure.
2. Define top nodes on level 0, using the following parameters.

8.3. Navigation
Position
Position of the node on level 0. Nodes are displayed in the structure/filter
according to this position.
Node ID
Enter the ID of the node that shall be displayed.
Workobject type
Enter the work object type.
Icon ID
Enter the icon that should be displayed. The default icon is folder or file. If a
folder has sub-nodes, it will always display the folder icon.
Numbers
Specify if the number of entries is displayed next to the node text in the
structure. The following options are available:
Cumulate numbers of all subordinated nodes

The number of entries of all subordinated nodes for which the Display
only numbers of current nodes option is set is displayed.
Display only numbers of current nodes

The number of entries according to the filter criteria of the current node
is displayed.
Do not display numbers

The number of entries is not displayed.
Select scr
Select this check box to automatically display the selection screen when the
node is opened. Thereby it is possible to restrict hits. A selection screen
must be defined for the work object type of the node.
Empt. node
Select this check box to display the node even if there are no entries for the
node and all subordinated nodes.
Displ. dat
Select this check box to display the entries according to the filter criteria of
the node when the node is opened.
Down crit.
Select this check box to pass on the filter criteria of the node to subordinated
nodes.
2nd Filter Label

Enter the label for the 2nd filter option. This is only used if the first filter is
of type Filter on node level.
If the first filter is for work object type, you must configure the label; see
“Defining filter labels for work object types” on page 264.

Def. node
Select this check box to define the node as default node. It is automatically
selected at the first display of the structure.
8.3.2.2 Defining sub nodes on level 1 to 4

In this step, you define levels 1 to 4 of the structure.
To define sub nodes:
1. In the Configuration Overview screen, select a line, and then double-click Sub
nodes - level <x> in the Dialog Structure where <x> is a number from 1 to 4.
2. Define sub nodes on the chosen level, using the following parameters.
Position sub node

Position of the actual node
Node ID, Workobject type, Icon ID, Numbers, Critical, Select scr, Empt. node,
Displ. dat, Down crit., Def. node
For the description, see “Defining top nodes on level 0” on page 262.
8.3.2.3 Defining filter labels for work object types

In this step, you define labels for the second filter. This is only relevant when you
use the Filter for work object types filter type.
To define filter labels for work object types:
1. In the Configuration Overview screen, select a line, and then double-click Filter
labels for work object types in the Dialog Structure.
2. Define labels for the second filter, using the following parameters.
Workobject type
Work object type.
2nd Filter Label
Enter the label for the 2nd filter option. This is only used if the first filter is
of type Filter for work object types.

8.4. Authorization objects
8.3.3 Defining work centers

In this step, you define the work centers that can be selected in the navigation bar. A
work center can include a single work object or many work objects to access data in
a structured way and also according to authority.
To define work centers:

Configuration > Navigation > Work Center.
3. In the Work Center Overview screen, define work centers, using the following
parameters.
Work Center ID
ID of the work center
Active
Select this check box to define the work center as active.
Work Center text
Enter a description.
Priority
Enter a priority number (possible values 00 to 99). Work centers are sorted
according to this priority.
Configuration ID
Enter the ID of the navigation structure that shall be displayed in the work
center.
Icon ID
Enter the icon for the work center.
Entries
Select this check box to display the number of hits in the navigation
structure next to the work center text.
8.4 Authorization objects

The following authorization objects are available for the Business Center Workplace.
They limit access and also processing according to work object type, node, and work
center level.
J_6NPF_WTY - OpenText Business Center for SAP Solutions - Work Object Types
This authorization object provides the following fields.
• J_6NPF_WTY - Work object type

• J_6NPF_ACT - Action of application

• J_6NPF_FCT - Work center function ID

• J_6NPF_NOD - Node ID
Users need authorization for work object types, actions, functions and nodes to
see and perform them in the Business Center Workplace. The authorization for
nodes is also checked in the web application.
J_6NPF_NAV - OpenText Business Center for SAP Solutions - Work center
This authorization object provides the following field.
• J_6NPF_PLA - Work center ID
Users need this authorization to access work centers in the Business Center
Workplace.
J_6NPF_ADM - OpenText Business Center for SAP Solutions - Authorization object
for administrative tasks
• J_6NPF_COM with the following components

1. Inbound
2. Process
3. Workplace
4. Web UI
This authorization object is checked in all administrative reports, transactions,

and programs.
J_6NPF_RFC - OpenText Business Center for SAP Solutions - Authorization object
for general execution of RFC functions and reports
• ACTIVITY with the values 02 (change) and 03 (display)
This authorization object is checked in all RFC functions and executable

programs. Each user must have this authorization with the full authority.
Example 8-1: Authorizations necessary to monitor the Inbound

Configuration
Authorization object VIM Foundation component

J_6NPF_NAV Business Center Workplace
J_6NPF_PLA Work Center ID
WP_IDF
J_6NPF_WTY Work object type
J_6NPF_WTY Work object type

8.4. Authorization objects
Authorization object VIM Foundation component

PF32_MON_IDF
J_6NPF_ACT Action of application
Work object type Action
PF32_MON_IDF CHANGE_STATUS
PF32_MON_IDF DISCARD
PF32_MON_IDF DISPLAY_IDOC
PF32_MON_IDF DISPLAY_MAIL
PF32_MON_IDF DISPLAY_VALAG
PF32_MON_IDF RESET_RETRY
PF32_MON_IDF TRIGGER
PF32_MON_IDF TRIGGER
J_6NPF_FCT Work Center function ID
IDF_ARCHIVE_DOCUMENT
IDF_ARCHIVE_MON
J_6NPF_NOD Node ID
Node ID Work object type
PF32_IDF PF32_MON_IDF Inbound
Documents
PF32_IDF_END PF32_MON_IDF
Processed
PF32_IDF_ERROR PF32_MON_IDF Error
PF32_IDF_PROC PF32_MON_IDF
Processing
PF32_IDF_REJECT PF32_MON_IDF
Rejected
PF32_IDF_WAIT PF32_MON_IDF
Waiting
J_6NPF_ADM Business Center Administration
J_6NPF_COM Components
1 Inbound (only this is needed)
2 Process
3 Workplace
4 Web UI

Chapter 9
Fiori Task App
The following sections give you detailed information about the landscape,
customizing options and the interface of the Fiori Task App and the underlying
technical concept of Web Services, which are both a part of VIM Foundation.
The Fiori Task App is a light-weight web application following the Fiori design
principles. It represents 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.
You configure the complete content of the Fiori Task App by customizing and
implementing interfaces of the Web Services. Therefore no extension points for the
Fiori Task App are offered and enhancements of the Fiori Task App or the VIM
Foundation OData services are not supported.

Chapter 9 Fiori Task App
9.1 Application modes

9.1.1 Full screen with work center as entry point
This application mode uses a Tab Container layout to display all nodes assigned to a
certain work center. See “Assigning nodes to work centers” on page 321. Each tab
visualizes the data selection of a node by using a Node List Data View. Using Full
Screen List Data Binding, you define which of the available fields is displayed. For
more information, see “Configuring the data binding for a full screen list”
on page 446. Furthermore it is also possible to specify different display styles and to
choose between different navigation options. For the available options, see
“Navigation capabilities” on page 278.
If a navigation option is set, the UI renders (instead of a plain text cell) a link or icon
that the user can click in order to trigger the navigation. The navigation link
parameter must contain a perspective ID of an existing item or action dialog
perspective depending on the chosen navigation type. In case of semantic
navigation, a JSON construct as described in “Semantic object navigation with the
Fiori Task App” on page 279 is expected. Using the navigation mechanism you can
display further item details (using an item perspective) or can trigger a semantic
object navigation to another app.
Value
Parameter name Description
specification
Mandatory
appMode FS Sets the mode of the application.
workplaceId (mandatory
<value> The workplace to show.
parameter)
Optional
Alias of the backend system to which
the OData service establishes a
connection. If the parameter is not set,
system <value>
the Fiori Task App tries to connect to a
system with the SAP System Alias
LOCAL.
systemAlias <value> Alternative to parameter system
If parameter is set to false, the
complete surface of the screen is used
letterBox (only applicable
<true|false> for the app. Otherwise, there is some
in Launchpad)
free space on the left and the right.
Default value is true.
If parameter is set to false, fields
with configured semantic object
semanticNavEnabled (only
<true|false> navigation are not active. Use the
applicable in Launchpad)
parameter if target applications are not
installed. Default value is true.

9.1. Application modes
Figure 9-1: Layout and Data View Composition of main screen
Sample Item Perspective that is displayed when the user clicks on a cell
(independent of the row) in the Process Key column.
Figure 9-2: Layout and Data View Composition of a detail screen (Item
Perspective)

9.1.2 Full screen with node as entry point

This application mode generally has the same capabilities as “Full screen mode with
work-center as entry point”. The difference is that it displays only one specific node
without the option to switch between the other nodes of the specified work center.
Use it if your work center contains only one node, or access to the other nodes of the
work center is not wanted for a certain solution application.
Value
specification
Mandatory
appMode FS Sets the mode of the application.
The workplace to which the specified
workplaceId <value>
node is assigned to.
The work object type from which the
wobjType <value>
node has been created.
The node specifying a specific object
nodeId <value>
selection in the backend.
Optional
system <value>
LOCAL.
in Launchpad)
Initially applied filter that can be
filter <url_encoded_value> revoked by the user (must match
existing filter categories and values).
Works in combination
with searchValue - initially applied
searchField <value> search that can be revoked by the user
(must match existing search
categories).

Value
specification
with searchField - initially applied
searchValue <url_encoded_value> search that can be revoked by the user
categories).
with sortDirection - initially
sortOption <value> applied sorting that can be revoked by
the user (must match existing sort
options).
with sortOption - initially applied
sortDirection <asc|desc>
sorting that can be revoked by the user
(must match existing sort options).
9.1.3 Master Detail with node as entry point

This application mode uses a Master-Detail layout to display one node of a certain
work center. There is no option switch between the other nodes of the specified
work center.
The data selection of the node is shown on the left in the master area. Which data
fields are shown in each list item, is configured using the data binding of the master
list. For more information, see “Configuring the data binding for the master list”
on page 315.
Whenever a list item is clicked, the detail area loads the item perspective of the node.
For more information, see “Enabling nodes for Web Services” on page 311:
Perspective ID item. Then, the detail area fills the data views by requesting detail
data for the selected item. Therefore ensure that for each data view in the

perspective the corresponding data binding is maintained. For more information,

see “Configuring the data binding of perspectives” on page 321.
Further item navigation options are maintained under the Work Object Type. For
more information, see “Defining item related actions” on page 304. The available
options for the master detail mode are described in “Navigation capabilities”
on page 278. After an action has been defined by its type, parameter, and some
other details, you must decide where the action should occur on the detail area page.
There are two places:
• First place is in the footer toolbar. Put there every action with a transacted
behavior regarding the item.
• The other place is on top of the page in an InplaceItemAction Data View or
BcCustomObjectPageHeader control. Specify the place by filling the Perspective
view ID parameter of an action.
Note: If this parameter is not filled, the action does not occur on the screen.
Value
specification
Mandatory
workplaceId <value>
wobjType <value>
nodeId <value>
Optional
The App is called in master detail
mode. Master detail mode is also the
appMode <MD>
default mode if the appMode
parameter is not specified in the URL.
system <value>
LOCAL.
in Launchpad)

Value
specification
If this parameter is set, the Master area
is hidden initially both in portrait and
landscape. The Master area can be
opened by clicking on the top left
splitAppMode HideMode
corner button or swiping right. Swipe
is only enabled on mobile devices.
Master will keep the open state when
changing the orientation of the device.
Initially applied filter that can be
filter <url_encoded_value> revoked by the user (must match
existing filter categories and values).
with searchValue - initially applied
searchField <value> search that can be revoked by the user
categories).
with searchField - initially applied
searchValue <url_encoded_value> search that can be revoked by the user
categories).
with sortDirection - initially
sortOption <value> applied sorting that can be revoked by
the user (must match existing sort
options).
with sortOption - initially applied
sortDirection <asc|desc>
sorting that can be revoked by the user
(must match existing sort options).
The search, filter, and sort can use criteria that are defined in the node
customizing: OpenText Business Center for SAP Solutions > Web
Services > Workplace > Nodes – Search Fields, Sort Fields, Filter fields.
Alternatively, the search, filter, and sort can use criteria that is defined in the
implementation of the node exit: interface /OTX/PF62_IF_NODE, for example
method CHANGE_NODE_FILTER_FIELDS. For more information,
see “CHANGE_NODE_FILTER_FIELDS” on page 375.

9.1.4 Object with item as entry point

This application mode displays the item perspective of the specified item using the
complete screen. The user is restricted to the actions maintained for the item. A
navigation to other items within the specified node is not possible. You can specify
the item in one of the following ways:
• Using a concrete webId, typically used when coming from a semantic object
navigation.
Note: In this case all keys necessary to build the webId for the target
application must also be part of the keys specified for the source
application.
• Using an alias where the keys are explicitly maintained. For more information,
see “Defining aliases for a work object” on page 299.
Value
specification
Mandatory
appMode OBJ Sets the mode of the application.
workplaceId <value>
wobjType <value>
nodeId <value>

Value
specification
The webId or webIdAlias specifying
webId | webIdAlias <value>
the concrete item.
Optional
system <value>
LOCAL.
in Launchpad)
If parameter is set to false, fields with
semanticNavEnabled configured semantic object navigation
(only applicable in <true|false> are not active. Use the parameter if
Launchpad) target applications are not installed.

9.2 Navigation capabilities
Figure 9-5: Master detail application mode
Figure 9-6: Full screen application mode

9.2. Navigation capabilities
Figure 9-7: Object application mode
9.2.1 Semantic object navigation with the Fiori Task App

The Fiori Task App supports intent-based navigation to another Launchpad app or
Fiori Task App instance from the following data views:
Customizing
You configure the navigation using VIM Foundation customizing or by
implementing the interfaces of the Web handler (see“Web handler” on page 380) or
the Perspective class /OTX/PF62_IF_PERSPECTIVE_CLASS (see “Interface /OTX/
PF62_IF_PERSPECTIVE_CLASS” on page 415). The relevant settings are Link type
and Link parameter. For semantic object navigation, Link type must be set to
Semantic object navigation. Link parameter must be filled with JSON data
describing all necessary intent details. The concrete structure is explained in the
following.
Link type
This field defines the type of the link. Possible values:
• No link
• Semantic object navigation
Link parameter
This field contains the JSON with the link parameters. The JSON data must
match the following structure:
{
"target": {
"semanticObject": <semantic object>,
"action": <action>
},
"params": {
<optional parameters>

}
}
The following piece of code is an example. The parameters depend on the

application mode. See the parameters reference in the corresponding application
mode.
Note: The value of the filter and searchValue parameters must be URL-
encoded.
{
"target": {
"semanticObject": "Z_OTX_BC",
"action": "display"
},
"params": {
"nodeId": "PS02_ORDER_INBOX",
"wobjType": "PS02_PRC_ORDER",
"workplaceId": "WP_INBOX",
"filter": "VKORG%20EQ%201000%20AND
%20VT_WEG%20EQ%2001",
"searchField": "KUNNR",
"searchValue": "1000",
"sortOption": "WI_PRIO",
"sortDirection": "ASC"
}
}
9.2.1.1 Performing changes using the web handler interface

In the perspective class, the link parameters can be changed in the following
methods:
For the AttributeList view

In method CHANGE_DATA of interface /OTX/PF62_IF_PERSPECTIVE_CLASS in
parameter PIT_CHANGE_ATTRIBUTE_LIST, the component ATTRIBUTE_LIST
(instance of /class /OTX/PF62_CL_FC_ATTRLST_CHG) allows to change the link
type and parameter of an attribute in method SET_ATTRIBUTES.
For the AdvLineItems view

In method CHANGE_CUSTOMIZING of interface /OTX/PF62_IF_PERSPECTIVE_
CLASS in parameter PIT_TABLES_CUSTOMIZING, the component TABLE_
CUSTOMIZING (instance of class /OTX/PF62_CL_FC_LI_CST_CHNG) allows to
change the action type and parameter in method SET_CUSTOM_ACTIONS.
Method CHANGE_ACTION_PARAMETER of interface /OTX/PF62_IF_PERSPECTIVE_
CLASS allows to change the action parameter before the action is executed.
You can set or change link types and link parameters using the web handler
interface. For more information, see the links in this section:
Method “CHANGE_OBJECT_HEADER” on page 405

The PCS_OBJECT parameter has the new fields LINKTYPE and LINK_PARAMETER.

9.3. Editing perspectives and layouts
Method “CHANGE_HEADER_DETAILS” on page 398

Structure of the PCT_HEADER_DETAILS parameter has the new fields LINKTYPE
and LINK_PARAMETER.
Method “CHANGE_ITEM_STRUC” on page 396
Structure of the PCT_ITEM_STRUCTURE parameter has the new field LINKTYPE.
The new GET_ITEM_LINKS method allows defining the link parameter of single line
items. The method is called when the user clicks a link in one of the line items. For
more information, see “GET_ITEM_LINKS” on page 402.
9.3 Editing perspectives and layouts

Perspectives define which item related data is displayed in the Fiori Task App and
where. They define the content and visual appearance of items for a specific area of
the screen in the Fiori Task App. Only one perspective is shown at the same time in
the Fiori Task App.
Perspective views are delivered using the following BSP applications which reside
on the frontend server:
• PF07_BC_UI_03,
• PS30_VIM_UI_03 (and custom BSPs).
Perspective A perspective has a 1:1 relation to a perspective layout. Therefore you can modify
Layouts the layout without influencing other perspectives. You can maintain dedicated
perspective layouts separately as drafts for perspectives. You can create a
perspective from an existing perspective or perspective layout. When the
perspective is saved, it is always independent to any used draft object (either
perspective layout or another perspective).
Perspective Business Center 16.3 introduces the Perspective Editor, a maintenance tool that
Editor allows you to perform all configuration tasks on perspectives and their elements.
You can start the Perspective Editor from the Launchpad by clicking the
Perspectives Maintenance tile.
Note: To see this tile, the Perspective Editor must be configured. The tile
configuration is delivered with a transport: Administration - /OTBCWUI/PF07_
BC_ADMIN - Perspective Manager. For more information , see Section 11.4.3.1.1
“Transports” in OpenText Vendor Invoice Management for SAP Solutions -
Installation Guide (VIM200400-IGD). You only need to configure the backend
connection of this tile.
“Old” templates Perspective templates (that were used in Business Center versions earlier than 16.3)
are stored in BSPs as UI5 XMLS Views. They are available for backward
compatibility. When you modify a perspective with a template in the Perspective
Editor and save it, the template is converted into a UI5 JSON View Perspective
Layout that is stored in a backend table. You must manually convert any inline CSS
data. Also localized texts must be converted manually.

The perspective customizing for manual maintenance is deprecated with Business

Center 16 Update 2. The customizing only allows to configure perspectives
leveraging old templates. Now you can only modify the perspective layout using the
new Perspective Editor.
9.3.1 Available Fiori App views

Table 9-1: Fiori App Views
Perspective Control/ View name Description Related Related

Type Purpose Customizing Interface
methods
Item Table item. Table view “Configuring “CHANGE_
AdvLineIte the table CUSTOMIZI
ms view” NG”
on page 325 on page 416“
CHANGE_D
ATA”
on page 418“
UPDATE_RO
W_VALUES”
on page 424“
UPDATE_AF
TER_REL_AT
TR_LIST_CH
G”
on page 430“
UPDATE_NE
W_ROW”
on page 432“
CHECK_SAV
E_DATA”
on page 422
item. Table view
AdvLineIte with
msResponsi responsive
ve behavior
item. Table view,
AdvLineIte line cells are
msVertical displayed
vertical in a
single column


methods
Input Fields item. Displays “Configuring “CHANGE_
AttributeL fields in a the attribute CUSTOMIZI
ist single list view” NG”
column. A on page 322 on page 416“
field consists CHANGE_D
of a label, ATA”
input field on page 418“
and UPDATE_AT
description TRIBUTES”
on page 427“
UPDATE_AF
TER_REL_AT
TR_LIST_CH
G”
on page 430“
CHECK_SAV
E_DATA”
on page 422
Comments item. Displays Not available “CHANGE_
Comment content using DATA”
control on page 418“
sap.m.FeedLi TRANSLATE
stItem _COMMENT
S”
on page 420
Document list item. List with Not available “CHANGE_
Attachment documents. DATA”
sInplace Selected on page 418
document is
displayed in
the item.
Document/
item.Widget
view in the
same
perspective
item. List with Not available
Attachment documents.
sNewTab Selected
document is
displayed in
new tab


methods
item. List with Not available
Attachment documents.
sSplit Selected
document is
displayed in
item.Docume
nt /
item.Widget
view in same
perspective in
different
flexible
column or
split screen
Document item. Displays the Not available “CHANGE_
view Document main DATA”
document or on page 418
the document
selected in an
item.Attachm
ents views
Document item. Displays the Not available “CHANGE_
view with Widget main DATA”
data document or on page 418
validation the document
selected in
item.Attachm
ents views.
Offers
features to
move data
from a
document to
attribute list
fields and
table cells
Action Dialog Messages dialogPart Displays Not available “GET_MSG_
. messages CONTAINER
ActionMess ”
ages on page 351“
GET_MESSA
GES”
on page 352“
SET_MESSA
GE”
on page 362


methods
Display text dialogPart Text area, Not available “GET_TEXT_
. display only AREA”
Descriptiv on page 350
eText
Button dialogPart Button Not available “GET_BUTT
. ON”
DialogButt on page 357
on
File Upload dialogPart Control to Not available “EXECUTE_
. upload files ACTION”
FileUpload on page 363“
GET_FILE_U
PLOAD”
on page 361“
EXECUTE_LI
NE_ITEM_A
CTION”
on page 364“
CREATE_AC
TION”
on page 362
Drop down dialogPart Drop down Not available “GET_DROP
. list _DOWN”
MultiCombo on page 356“
Input EXECUTE_A
CTION”
on page 363“
EXECUTE_LI
NE_ITEM_A
CTION”
on page 364“
CREATE_AC
TION”
on page 362
Table dialogPart Table Not available “GET_TABLE
.Table ”
on page 358“
EXECUTE_A
CTION”
on page 363“
EXECUTE_LI
NE_ITEM_A
CTION”
on page 364“
CREATE_AC
TION”
on page 362


methods
Enter text dialogPart Text area, Not available “GET_TEXT_
. edit AREA_INPU
TextAreaIn T”
put on page 355“
EXECUTE_A
CTION”
on page 363“
EXECUTE_LI
NE_ITEM_A
CTION”
on page 364“
CREATE_AC
TION”
on page 362
Input field dialogPart Field to Not available “GET_INPUT
. display or _FIELD”
ValueHelpI maintain on page 353“
nput data. EXECUTE_A
Optional with CTION”
search help on page 363“
EXECUTE_LI
NE_ITEM_A
CTION”
on page 364“
CREATE_AC
TION”
on page 362
9.3.2 Maintaining perspectives and layouts

On the start page of the Perspective Editor, you have access to all available
perspectives and layouts.
To switch between Perspectives and Layout, click the corresponding icon on the
toolbar on the top.
The way how you work with perspectives and layouts is similar, the procedure is
therefore described only once.
In the search and filter bar below the toolbar, you can perform the following actions:
• “To search the list:“ on page 287

• “To filter the list:“ on page 287
In the list, you can perform the following actions:
• “To enable a bulk action“ on page 287

• “To open the details page:“ on page 288

• “To delete the ID:“ on page 288
• “To create a new perspective or layout:“ on page 288
• “To rename a perspective:“ on page 289
• “To transport a perspective“ on page 289
• “To activate or deactivate a perspective:“ on page 290
• “To activate or deactivate a perspective:“ on page 290
To enable a bulk action
1. Use the search or filter function to reduce the displayed perspectives to a

number that displays without switching the page.
2. In the footer, click the Multi Select button .
3. Select the items on the check-box that gets available and perform the action.
To search the list:
1. In the search box on the very left, enter a case-sensitive search term.
2. Optional To define where the term is searched, click the down icon to the right of
the search box.
Available are:
• Perspective ID
• Description
• Changed By
• Object ID
3. Press RETURN or click the search icon.
4. To clear the search term, click the cross icon in the search box.
To filter the list:
There are two ways to filter a list.
1. To filter the list, using the filters that are displayed on top of the list:
a. Click the available filter. For example, Perspective Type.

b. In the dialog box, select one or more criteria that is used for filtering.
2. To filter the list, using the Filter icon:
a. Click the Filter icon.

b. Click the Filter.

c. Select one or more criteria that is used for filtering.

3. To remove the filter and return to the original view, click the Reset icon.
To open the details page:
• Click the perspective ID (layout ID).
To delete the ID:
• In the perspective list, click More Actions > Delete for the perspective
that you want to delete.
To create a new perspective or layout:
1. Click Create Perspective on the toolbar at the bottom of the page.

2. In the Create Perspective dialog box, create a perspective in the following steps:
a. Choose a creation approach:

In this list you can choose between a creation from an existing perspective,
an existing layout, or start with an empty perspective.
b. Specify parameters.
Depending on the chosen creation approach, the mandatory parameters
vary.
Perspective Type
Choose Item, Action Dialog, or Field from the list.
Perspective ID
Mandatory. Enter a meaningful ID for the perspective.
The ending of the ID defines the device type:
• _S
Smartphone
• _M
Tablet
• _H
Hybrid
• without ending
If you do not define a device type, the systems only uses this
perspective if no other perspective is available.
If a perspectives for device types exist, the first perspective with
device type is used.
The order of the checks is:
Smartphone > tablet > hybrid > desktop.

This allows, for example, to specify one perspective which fits for
smartphone and tablet if you only define a perspective with device
type _M.
Root Work Object Type

Select a work object type from the list to which the perspective should
be bound. The root work object type determines which fields and
associations are available for property bindings and data views.
Note: You cannot change this setting later on.
Seeting a root work object type is mandatory for all perspective
types but not for ACTION_DLG perspective type.
Select Perspective
Mandatory unless you have chosen Do Not Use A Template in Step 2.a
on page 288. Click in the field to open the Select Perspective dialog box
and choose a perspective from the list.
Enter description
Enter a description for the new perspective.
3. Click Create.
To rename a perspective:
1. In the perspective list, click More Actions > Rename button for the
perspective that you want to rename.
2. In the Rename Perspective dialog box, enter the new name for the perspective,
Perspective ID
Enter the new name.
Description
Enter a description of the perspective.
3. Click Rename.
The selected perspective is copied to the new perspective ID. The old
perspective is deleted. All customizing entries related to the old perspective are
copied/changed to the new perspective ID.
To transport a perspective
Note: The action is also available as bulk action. For more information, see“To
enable a bulk action“ on page 287.
1. In the perspective list, click More Actions > Add To Transport

button, for the perspective that you want to transport.
2. In the Select Customizing Request dialog box, select a request, and then click
OK.

The content of the perspective is written to the customizing transport.
To activate or deactivate a perspective:
1. In the perspective list, click More Actions .
2. To deactivate a perspective, click the Set inactive button for an active

perspective .
You cannot use a deactivated perspective in an application anymore. It is also
not possible to maintain deactivated perspectives in the perspective editor.
3. To activate a perspective, click the Activate button for an inactive

perspective .
The Changed at and Changed by columns in the perspective list are relevant for
perspectives that are changed using one of the following actions:
• Rename
• Activate
• Deactivate
• Edit
If a perspective is changed, the user and timestamp are logged. The information is
displayed in the Changed by and Changed atcolumns.
Device specific To maintain a device specific perspective, you must append the general perspective
perspective ID with a specific suffix. During perspective retrieval, the system first tries to get a
device specific perspective. If no such perspective exists, the standard perspective is
used.
Perspective ID Device Type

<pSample> Desktop (and other device types for which no dedicated types are
maintained)
<pSample>_S Smartphone
<pSample>_M Tablet
<pSample>_C Combi devices

9.3.3 Editing perspective and layout details

The detail page of a perspective (or layout) enables you to perform all actions to
configure the perspective to your needs.
Note: When speaking of “perspectives” in this section, “layouts” are meant as

well.
Tree area The tree area on the left lists all perspective elements in a cascading structure. In
detail, a perspective comprises the following elements:
Layout root element.
Layout container. SAP UI5 control representing a specific layout, for example a
vertical layout. If the icon is green on the right side, a CSS class is assigned to
the layout container.
To see all available layouts, open the Layouts palette.
Aggregation. An aggregation is a special relation between two UI element
types. It is used to define the parent-child relationship within the tree
, structure. The parent end of the aggregation has cardinality 0..1, while the
child end may have 0..1 (empty triangle) or 0..* (filled triangle). Examples are
table rows and cells, or the content of a table cell.
Data view. A data view acts as dynamic part of a perspective. It displays data
according to the data binding defined in the customizing. A green label on the

right side of a data view indicates that a CSS class has been assigned. Each
view type can be inserted multiple times in a perspective.
Note: The History and Attachments views will always display the same
data. They cannot be configured on view instance level. So it makes sense
to include them only one time.
LayoutData. For some layouts (for example grid), you can attach specific
LayoutData to the children of the layout. LayoutData steers where and how the
child is displayed in the container if the container supports this flexibility.
Examples are column span of an element or alignment.
To edit a perspective:
1. On the start page, click the perspective or the corresponding pencil icon.
2. In the Select Customizing Request dialog box, select a request, and then click
OK.
3. Arrange the elements in the tree structure.
a. Move elements up or down or delete them using the context menu.

b. In the Palettes area on the upper right of the detail page, open the Views,
Layout Containers, and Layout Data lists. You can expand single Layout
Containers to see the respective aggregation.
Notes
• Depending on the perspective type, only suitable views are

displayed.
• You can place views and controls in aggregations where the type
matches. If the type is not suitable, the Perspective Editor does not
allow to drop the element.
c. From the Palettes area, drag elements to the tree structure to integrate them
into the perspective. You can place the elements in the tree only on valid
locations. This means, the type of aggregation must match.
4. Optional In the Description field, add a description of the perspective. It is

displayed on the start page.
5. Optional To add a scroll bar to the whole page at runtime, if necessary, select the
Scrolling of page enabled check box.
6. For elements under Layout Containers, and Layout Data in the Palettes area,
click SAP API Information from the context menu to display the corresponding
page of the SAP Help.
7. Optional To add further UI5 layout containers, click Add UI5 Control on the
context menu of Layout Containers.
To add custom data views, click Add Module Views on the context menu of
Views.

8. To edit the properties of an element, click the element in the tree structure. In
the Properties area, make the required changes.
For Layout Containers, the properties are read from the control metadata. They
rely on the UI5 toolkit version.
For properties with <string>, you can maintain a localization key:
a. Enter the text key in the field in upper case and angle brackets.
b. Click the globe icon.
c. In the Localization dialog box, enter the value corresponding to the text
key.
Note: The translation is done with regular ABAP translation

mechanisms.
9. To assign a custom CSS class to an element, maintain the CSS class in the CSS
area. In the Properties area, enter the CSS class name in the cssClass <string>
field.
The CSS area collects the CSS code for the whole perspective.
10. To perform a check of your changes, click Check on the toolbar at the bottom of
the page.
The check ensures that all IDs are unique and that referenced CSS classes are
also defined in the CSS data.
9.3.3.1 Configuring property bindings

Property bindings have the following major purposes:
• Change the perspective at runtime, for example make some areas visible or
invisible depending on computation in the backend. In such a scenario you
would bind the “visible” property of one or more layout containers.
• Arrange an arbitrary number of sap.m.ObjectAttribute and/or sap.m.
ObjectStatus in any of the available layouts to be presented somewhere on the
page, typically in the headerContent of the sap.uxap.ObjectPageLayout.
To add a binding to a certain property:
1. Click the property to open the binding action sheet.

2. To open the Work Object Type Fields dialog box, click the Add Binding action.
3. Select one of the fields.
Available fields for binding:
• Fields of the display structure of the root work object type or its associated
work object types.
• PF62_IS_LOCKED: Lock icon for a field.
• PF62_LOCKED_BY_USER: User who locks the field.

PF62_IS_LOCKED and PF62_LOCKED_BY_USER are calculated by the framework

checking the locking information of the root work object type.
Whenever a layout control has at least one binding, you can detect it in the tree
by the orange triangle on the upper left edge of the icon. See the following
screenshot.
You can change or delete an existing binding with the corresponding actions in
the binding action sheet, which is always opened when you click the property.
9.3.3.2 Support of FlexibleColumnLayout in perspectives

The Fiori Task App supports toggling and closing of the mid and end column of the
FlexibleColumnLayout control.
In the perspective editor you can assign the predefined controller methods to the
press event of the corresponding buttons of your pages used in the
FlexibleColumnLayout.
The following predefined controller methods are available for the press event:
• onToggleMidColumnFullScreen
• onCloseMidColumn
• onToggleEndColumnFullScreen
• onCloseEndColumn
The Fiori Task App:
• Automatically shows or hides the buttons at runtime according to the state of the
FlexibleColumnLayout control

• Changes the layout as defined.
To trigger the display of a page in the FlexibleColumnLayout control, you can use
the action type Change page in flexible column layout (parameter = page id)
(FLEX_PAGE) in the action customizing row of the FullScreenList or
AdvancedLineItems.
9.3.4 Maintaining perspective texts

With Business Center 16.3 and later, perspectives are maintained using the
Perspective Editor.
One exception is the maintenance and translation of perspective texts, which is still
done in the Business Center IMG.
To maintain perspective texts:
2. Click OpenText Business Center for SAP Solutions > Web Services >
Perspectives > Perspective texts.
3. In the Perspective Overview screen, maintain perspective texts, using the

Perspective ID
Unique ID of the perspective.
Pers. Type
Select the perspective type. Choose Item, Action Dialog, Node, or Field
from the list.
Description
Description of the perspective.
4. To maintain texts for a perspective, mark the perspective, and then double-click
Texts in the Dialog Structure.
5. In the Texts Overview screen, maintain texts using the following parameters:
Text Id
Unique ID of the text.
Text
Enter the text for the perspective. For translation, click Translation on the
Goto menu.

9.4 Basic settings

The basic settings allow general settings regarding the display of documents and the
definition of the keys for the work object types, displayed in the Fiori Task App.
To customize the basic Web Services settings in the IMG:
2. Click OpenText Business Center for SAP Solutions > Web Services
3. Click the setting that you want to maintain:
• Basic Settings
• Launchpad Setting Actions
9.4.1 Configuring basic settings

To configure basic settings:
2. Click OpenText Business Center for SAP Solutions > Web Services > Basic
Settings > Basic Settings.
3. In the Basic Settings Overview screen, configure basic settings using the
Device typ
Device type. You can define the settings for each device type: Tablet,
Desktop, Smart phone, Hybrid devices, All devices.
Setting
Use web viewer (if available) for desktop document view.
Value
Enter X to determine that OpenText Imaging Web Viewer (Web Viewer) or
OpenText Brava! View for SAP Solutions (Brava! View) is used to display
documents if possible.
General document viewing notes
• Web Viewer or Brava! View can only be switched off (or is not
mandatory) if the archive delivers the documents as PDFs. In that case,
the native PDF viewer of the client is launched to display the document.
On iOS devices, the native viewer is launched in a separate browser tab
when touching the first page image.
• If you use the SAP Cloud Platform deployment option, Web Viewer
must not be activated. It is not supported within this deployment
option.

9.4. Basic settings
9.4.2 Configuring the integration of standard or solution

specific Apps into the user menu
The Fiori App allows to integrate standard or solution specific Apps into the user
menu.
Whenever the Fiori App is called in the SAP Fiori Launchpad, the App checks how
the Launchpad is customized and adds the defined Apps to the user menu.
You define the object navigation to other Apps in the Launchpad Setting Actions.
Your settings are restricted by the workplace, the optional node and by an action ID.
Note: You have to authorize the users to the action ID in the J_6NPF_WTY
object.
To configure the integration of Apps into the user menu:
Settings > Launchpad Setting Actions.
4. In the New Entries: Overview of Added Entries screen, configure basic settings
Entries to define the app or node that contains additions in in the User menu
Work Center ID
Unique ID of the work center.
Node ID
Unique ID of the node. For information about defining nodes, see “Defining
nodes” on page 256.
Workobject type
Work object type which contains the Apps in the user menu.
Action ID
ID of the action.
Device type
Device type. Possible values:
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

Entries to define the standard or solution specific Apps that are shown the User
menu
Web Icon
Add the icon that is shown for the app.
Semantic Object Action
Add the action that is performed for a bundle of applications that form the
semantic object.
ShellHash
Add the routing path of the part of the app that you want to show.
Action Text
Add the text that displays for your users.
Tooltip
Add the text that displays when you mouse-over.
5. Optional If you want to deactivate an App in the User menu, select the Inactive
check-box
9.5 Work object type

Work object types maintained in the /n/OTX/PF00_IMG transaction > OpenText
Business Center for SAP Solutions > Workplace Configuration > Work object
types > Work object types (see “Defining work object types” on page 230) are
automatically available in this maintenance view.
If you create a new work object type in this view, you also need to maintain the
settings in OpenText Business Center for SAP Solutions > Workplace
Configuration > Work object types > Work object types for the new work object
type.
To enable a work object type for the Fiori Task App:

2. Click OpenText Business Center for SAP Solutions > Web Services > Work
Object Type > Work Object Type.
3. In the Work Object Type Overview screen, enable work object types for the
Fiori Task App, using the following parameters.
Work object type

Work object type to be enabled for the Fiori Task App.
Web/Mobile item handler class
Enter the exit to change or enable the displayed web content for objects of
this work object type and to define and run actions for this work object
type. Interface: /OTX/PF62_IF_ITEM_HANDLER. For more information, see
“Web handler” on page 380.

9.5. Work object type
For work object types based on a process configuration, use the default
implementation /OTX/PF31_CL_BPF_WI_WEB_HANDLE. With this class, all
settings in the process configuration related to the mobile UI are
automatically considered.
9.5.1 Defining keys for the work object type

In this step, you configure the definition of the key for a work object type based on
the fields of the display structure. Web Services select the work object with this key
using the handler class of the work object type.
To define keys for the work object type:
3. In the Work Object Type Overview screen, mark a work object type, and then
double-click Key definition in the Dialog Structure.
4. In the Key Definition Overview screen, define keys for the work object type,
Key pos.
Key position. Define the position of the field in the key. 16 position values
are available.
Field Name
Enter the name of the field.
Log. Sys.
Logical System. Select this check box to define that the content of this field
contains the logical system.
Important
The overall length of the key fields must not exceed 117 characters.
9.5.2 Defining aliases for a work object

For each work object type, you can define aliases for the web ID. You can use this
alias for the app mode OBJ for the webIdAlias parameter . Compared to the
generated webIds this alias is stable, whereas the generated webIds are temporary,
To define an alias for a work object:

double-click Alias in the Dialog Structure.
4. In the Alias Overview screen, define aliases for the work object type, using the
Alias for Web ID

Enter the alias that you want to create for the work object.
5. Mark an alias, and then double-click Alias Object - Key Values in the Dialog
Structure.
6. In the Alias Object - Key Values Overview screen, enter key values for the alias
object, using the following parameters:
Field Name
Choose the key fields and set the values of the work object. You must
maintain values for all key fields.
Value
Enter the corresponding value.
9.5.3 Defining a related business object for a work object

type
For each work object type, you can define a related business object. This business
object can be used, for example, to open a related Extended ECM for SAP Solutions
workspace.
To define a related business object for a work object type:
double-click Related business object in the Dialog Structure.
4. In the Related Business Object Details screen, configure the related business
object using the following parameters.
Work object type

Work object type that the business object relates to.
Object Type
Enter the SAP business object type.
Example: For the Sales Order solution (OTBCSL02), this can be the object
type KNA1 (customer) with the key field KUNNR (customer number).

Field List (Key)

Enter key fields of the business object in a comma-separated list. Use fields
of the display structure of the work object type.
Use the CHANGE_RELATED_BUS_OBJECT method of the web handler interface
to change the customized business object at runtime.
9.5.4 Maintaining Data Collections

In the Fiori Task App, you can use Data Collections to temporarily store data during
a certain process step for the currently used work object. This allows, for example,
an implementation of the web handler interface to access information processed in a
previous call.
Additionally the /OTX/PF62_IF_PERSPECTIVE_CLASS interface has the MH_

PERSPECTIVE_INFO attribute. This attribute is a instance of the /OTX/PF62_IF_
PERS_INFO interface . Use the GET_PERSPECTIVE_VIEWS and GET_PERSPECTIVE_INF
methods to get information about the currently used perspective. GET_ATTRIBUTE_
LISTS and GET_TABLES methods offer read access to attribute lists and tables.
To maintain Data Collections:
double-click Data Collections in the Dialog Structure.
4. In the Data Coll. Scope (Data Collections Scope) field, select the scope (process
step) for which this data collection should be used. Possible values:
Action Dialog
Data Collection starts before an action dialog box opens and is finished
when the action dialog box closes.
Perspective Life Time Token
Data Collection starts when a item perspective is loaded and ends when the
user leaves this item perspective.
5. In the Data Collection field, maintain an implementation of the interface /OTX/

PF62_IF_DATA_COLLECTION. This implementation contains the read and write
logic for the information save in the Data Collection.

9.5.4.1 Interface /OTX/PF62_IF_DATA_COLLECTION

Attributes:
Attribute /OTX/ Level Type Description

PF62_IF_PERSPEC
TIVE_CLASS.
/OTX/ Instance Attribute /OTX/ Data Collection ID
PF00_IF_DATA_COL PF00_E_DATA_COL
LECTION~M_COLL LECTION_ID
ECTION_ID
/OTX/ Instance Attribute /OTX/ Data Collection Scope
PF00_IF_DATA_COL PF00_E_DATA_COL
LECTION~M_SCOPE L_SCOPE
/OTX/ Instance Attribute /OTX/ Valid until
PF00_IF_DATA_COL PF00_E_VALID_UN
LECTION~M_VALID TIL
_UNTIL
/OTX/ Instance Attribute /OTX/ Key values
PF00_IF_DATA_COL PF00_TT_KEY_VAL
LECTION~MT_KEY_ UES
VALUES
M_LAST_CHANGE Instance Attribute /OTX/ Timestamp for last
D PF00_E_LAST_CHA change
NGED
Methods:
/OTX/PF00_IF_DATA_COLLECTION~GET_INSTANCE
This method returns the instance of the data collection class.
Parameter Type Associated Type Description

PI_COLLECTION_ID Importing /OTX/ Data Collection ID
PF00_E_DATA_COL
LECTION_ID
PIT_KEYS Importing /OTX/ Values for a key
PF00_TT_KEY_VAL
UES
PI_CLASSNAME Importing /OTX/ Data Collection class
PF00_E_DATA_COL
L_CLASS
PRH_INSTANCE Returning /OTX/ Data collection
PF00_IF_DATA_COL instance
LECTION
/OTX/PF00_IF_DATA_COLLECTION~CREATE_COLLECTION

This method is called when the data collection is started.

PIS_DATA_COLLEC Importing /OTX/ Data Collection
TION PF00_S_DATA_COL Information
L_ADMIN
Structure of PIS_DATA_COLLECTION:
Fieldname Type Description

ID /OTX/ Data Collection ID
PF00_E_DATA_COLLECTIO
N_ID
SCOPE /OTX/ Data Collection Scope
PF00_E_DATA_COLL_SCOP
E
CLASS /OTX/ Data Collection class
PF00_E_DATA_COLL_CLAS
S
VALID_UNTIL /OTX/ Valid until
PF00_E_VALID_UNTIL
/OTX/PF00_IF_DATA_COLLECTION~REMOVE_COLLECTION
This method is called when data collection is finished or deleted by an

administrative program. In this method all temporarily saved data for this data
collection should be cleaned up.
This method does not have any parameters.
SET_ADDITIONAL_INFORMATION
This method is called after call of method /OTX/PF00_IF_DATA_

COLLECTION~CREATE_COLLECTION to set additional web service specific information.

PI_LAST_CHANGE Importing /OTX/ Last changed
D PF00_E_LAST_CHA timestamp of work
NGED object

9.5.5 Defining item related actions

In this step, you define which actions are available in the Fiori Task App for a work
object type. You also define how the buttons for these actions are displayed.
You can change the settings of this customizing by implementing the

method CHANGE_ACTIONS of the web handler class. For more information, see
“CHANGE_ACTIONS” on page 381 and “HANDLE_ACTIONS_BULK”
on page 388.
To customize actions for the Fiori Task App:
3. In the Work object type Overview screen, mark a work object type Actions in
4. Double-click an action.
5. In the Actions Details screen, customize the action using the following
parameters:
Workobject type
Work object type for which actions should be made available.
Action ID
ID for the action.
Action order
Define the order of actions. The action with the lowest number is displayed
to the left.
Action type
Select the action type from the list. The following types are available:
Action type Perspectiv Action Description

e required? dialog
class
required?
Confirm dialog No No Opens the confirmation
dialog box.
Save No No Calls CHECK* and HANDLE_
UPDATE_BULK methods of
the web handler.
Check No No Calls the CHECK* methods of
the web handler.

Action type Perspectiv Action Description

e required? dialog
class
required?
Save & Confirm No No Runs a Save and afterwards
dialog calls the confirmation dialog
box.
Action dialog Yes Yes Opens the action dialog box
with customized perspective
ID calling the customized
action dialog class.
Save & Action Yes Yes Runs a Save and afterwards
dialog calls the action dialog.
Semantic object No No Performs a semantic object
navigation navigation. Enter the link in
the Link parameter field.
Further Details Yes No Calls the perspective in
Inplace inplace mode.
Further Details Yes No Calls the perspective in full
Full Screen screen mode.
Cancel No No Cancels changes done after
last Save action.
Perspective ID
Enter the perspective ID, which is used for Edit actions.
Link parameter
Enter the link for the semantic object navigation.
Action dialog class
Enter a class with logic for the Action dialog box. The class must implement
the /OTX/PF62_IF_ACTION_DIALOG interface.
Web Icon
Enter the icon that is displayed on the action button.
Tip: All available icons are defined in the “SAP UI5 Icon Explorer”:
https://openui5.hana.ondemand.com/iconExplorer.html. The URL can
be subject to changes.
UI 5 button type
Enter the SAP UI5 button type. Choose one of the following types:
• Accept type (blue button)

• Default type (no special styling)
• Emphasized type
• Reject style (red button)

• Transparent type
• Unstyled type (no styling)
Perspective view ID
Enter this parameter to set the location of the action. If no perspective view
ID is maintained, the action is not shown.
You can place actions in the footer toolbar by setting the property
itemActionsViewId of the root element in the Item perspective using the
Perspective Editor. The chosen ID must be unique and the linkage happens
by specifying the same ID as Perspective view ID in the action.
You can place actions anywhere on the page by using UI5 controls which
are designed to contain action buttons.
The Perspective view ID must then match the control ID.
Action text
Enter the text that is displayed on the button.
Tooltip
Enter the tooltip that is shown for the button.
This setting can be overwritten at runtime using the CHANGE_ACTIONS
method of interface /OTX/PF62_IF_ITEM_HANDLER. For more information,
see “CHANGE_ACTIONS” on page 381.
Bulk action
Select this check box to define the action as a bulk action.
Notes
• Bulk is only available in the Fiori Task App if there is no paging in

the inbox.
• Bulk is only available in the Confirm dialog box, not in the Action
dialog box.
Transport type
Choose one of the following options:
• No transport required (default)

• Customizing request
• Workbench request
Aggregation Name
Aggregation of the UI5 control to which the control action is assigned to.
The Aggregation of the UI5 control is specified in Perspective view ID. By
default the contentRight aggregation is used.
SAP UI5 Button Class
SAP UI5 control that is used to display the action. By default sap.m.Button
is used.

9.5.5.1 Semantic object navigation in the Fiori Task App

Define the parameters of the work object type actions which are semantic object
navigation actions (SEMANTIC action type) in the Semantic Object Navigation setting
of the work object type
To define the parameters of the work object type
2. Click Web Services > Work Object Type> Work Object Type.
3. Select a Workobject type, and then click Semantic Object Navigation
4. Open an existing entry or create a new Semantic Object entry.
In this setting you define device specific:
• the semantic object

• the object action
• Optional: an exit class. Enter a class that has implemented the /OTX/PF63_
IF_SEM_OBJ_NAV interface, which allows to change parameters at runtime.
For more information, see /OTX/PF63_IF_SEM_OBJ_NAV interface:
on page 308.
5. To define further parameters, select the Semantic Object entry, and then
double-click Parameters sub-settings.
6. To add the field values, double click a Parameter.

Parameter:
Name of the parameter. You find the parameters for the BC Fiori App via
search help.
Value:
Maintains the values for the parameter.
Work Object Type Field

Defines the fields from the display structure of the work object type. The BC
framework calculates and sets this value at runtime.
The framework provides the following fields:
• PF62_ACTION_ID
• PF62_DEVICE
• PF62_WEBID
• PF62_WOBJ_TYPE
• PF62_NODE_ID (only in FullScreenList)
• PF62_SAP_ORIGIN
Exit Class
Defines an exit class. For changing the parameter at runtime enter a class
implementing the /OTX/PF63_IF_CONV_PARAM_VALUES interface. The value
of the parameter is changed in the CHANGE_PARAMETER_VALUE . For more
information, see /OTX/PF63_IF_CONV_PARAM_VALUES interface :
on page 309.
The BC framework calculates the semantic object navigation target based on this
customizing at runtime.
/OTX/PF63_IF_SEM_OBJ_NAV interface:
GET_INSTANCE method:
Returns a class instance. Parameters:

Parameter Type Descritpion

PIH_WOBJ_TYPE Importing Work Object Type
PRH_INSTANCE Returning Instance
When the implementation class inherits the /OTX/PF63_CL_SEM_OBJ_NAV class,

then the handling for the GET_INSTANCE method is already implemented and
you only need to define the CHANGE_PARAMETER method.
CHANGE_PARAMETER method :
Allows to change customized parameters and values at runtime. Parameters:

PI_ACTION_ID Importing Action ID
PI_SEMANTIC_OBJECT Importing Semantic Object
PI_SEMANTIC_ACTION Importing Semantic Object action
PIH_WOBJ Importing Work Object
PI_WEBID Importing Web ID
PI_DEVICE Importing Device type
PCT_PARAMETER Changing Calculated Link parameter
PI_SAP_ORIGIN Importing System alias (only set in
FullScreenList and Adva
LineItems)
PI_NODE_ID Importing Node ID (only set in
FullScreenList)
/OTX/PF63_IF_CONV_PARAM_VALUES interface :
CHANGE_PARAMETER_VALUE method
Allows to change the value of a single parameter, when a this parameter is
calculated.

PI_NAME Importing Parameter name
PI_FIELDNAME Importing Field name of the work object
PIH_WOBJ Importing Work object instance
PC_VALUE Changing Parameter value

9.5.5.2 Refreshing views for work object type actions

You can maintain work object type actions that require the refresh of views in the
item perspective in the Refresh Views dialog of the work object type. A refresh is
urrently possible for the REFRESH, ACTION and SAVE_ACTN action types .
In the setting you define which views are refreshed in an item perspective when this
action is executed.
At runtime these views can be changed with implementation of method CHANGE_

VIEWS_FOR_REFRESH of interface /OTX/PF62_IF_PERSPECTIVE_CLASS. For more
information, see “CHANGE_VIEWS_FOR_REFRESH” on page 433.
9.6 Workplace
In this step, you define which nodes of the Workplace Configuration are available
for the Web Services and the relationship between nodes and work centers.
9.6.1 Defining work centers

In this step, you define work centers that are available for Web Services. These work
centers are independent from work centers defined in the Workplace Configuration.
To define work centers:
Workplace > Work Center.
3. In the Work Center for Webservice Overview screen, define work centers using

9.6. Workplace
Work Center ID
Work Center Text

Enter a meaningful description of the work center.
9.6.2 Enabling nodes for Web Services

In this step, you enable nodes, which are defined in the Workplace Configuration,
for Web Services. For more information, see “Defining nodes” on page 256. You can
also assign an item perspective to the node. For more information, see “Editing
perspectives and layouts” on page 281.
To enable nodes for Web Services:
Workplace > Nodes.
3. In the Nodes Overview screen, enable nodes for Web Services using the
Node ID
Unique ID of the node. For information about defining nodes, see “Defining
Workobject type
Work object type of the node.
Each node is connected to a work object type. When the user selects a node,
the work object type is automatically filled.
Active
Select this check box to activate the node in order to display it in the
Business Center Workplace.
Exit for node

Enter a user exit for the node. This exit requires a class with implementation
of the /OTX/PF62_IF_NODE interface. Using this exit, you can change the
node at runtime. For more information, see “Interface /OTX/
PF62_IF_NODE” on page 373.
Perspective ID item
Enter the ID of the item perspective. This perspective is used when the
items of the node are displayed with appMode MD (master detail).
Node description
Enter a meaningful description of the node. The description is displayed at
the top of the inbox in the Fiori Task App.

Page size - desktop, Page size - tablets, Page size - mobiles

Define page sizes for the node depending on the device. The default size for
all device types is 50 tasks.
The page size determines how many tasks are shown on one page in
appMode MD. If more tasks are available, you find buttons in the bottom
action bar to go to the next or the previous page.
Full Scr. List Exit
Full screen list exit. Enter a user exit for the full screen list. For more
information, see “/OTX/PF63_IF_FS_LIST interface” on page 437.
Icon ID UI5
Enter the UI5 icon that should be displayed.
Value state
Define in which status the node is displayed in the workplace view.
Possible values are the following:
• Error
• None
• Success
• Warning
None is the default value. In the workplace view (Full screen with work
center as entry point) the icon and the node text are displayed in a color
according to their status.
Bulk activ
Bulk actions active. Select this check box to indicate that at least one bulk
action for this node is available. Therefore, the Edit button at the top of the
master list in the Fiori Task App is available.
Note: Bulk is only available in the Fiori Task App if there is no paging
in the inbox.
Counter Inactive
When the app is started as Full screen with work center as entry
point, the entries for all nodes of this workplace are counted. The number
of entries for each node is displayed below the node icon. If you do not
want to have this counter for the node, select Counter Inactive.
Max. List Desktop, Max. List Tablet, Max. List Smartphone
Note: This setting is only considered in the old node list view. To use
the old view, activate Use Node List View checkbox.
Enter the maximum list sizes for this node, depending on the device.
Default values for smart phones and tablets is 100, for desktop 500.
The list size defines how many items can be displayed in the node list
maximally. When configuring this value, consider the capabilities (memory

9.6. Workplace
and CPU) of the device because all objects are loaded in the Document
Object Model (DOM) of the HTML page. If you choose the number too high,
it can happen that the application becomes very slow or unresponsive.
Export enabled
Select this check box to configure that all columns visible for the user can be
downloaded to a Microsoft Excel file, using a Download button. By hiding
columns, users can restrict the downloaded columns.
Use Node List View

Select this check box to configure that the user interface uses the old node
list view. The framework uses the same customizing and exits as in
previous version.
Perspective ID
If you want to use the Flexible Column layout for this node in the Master
Detail pattern, enter the corresponding perspective.
9.6.2.1 Adding fields for searching, sorting, and filtering to a node

In this step, you define fields that can be used for a text search, for sorting the item
list, and for additional filtering. All fields of the data selection structure of the work
object type are available. For more information, see “Defining work object types”
on page 230.
To add fields for searching, sorting, and filtering to a node:
Workplace > Nodes.
3. In the Nodes Overview, mark an entry, and then double-click one of the
following entries in the Dialog Structure:
• Search fields
• Sort fields
• Filter fields
4. In the Search fields overview, Sort fields overview, or Filter fields overview
screen, enter the respective fields that you want to use for a text search, for
sorting, or for filtering in Field Name.
In the Position field, define the order of the values, in which they are sorted and
displayed.
In Search fields, the Object ID field is always added as the last field.
In Sort fields, the Default field is always displayed as the first field.
In Filter fields, check the No multi (No multi select) check box to limit the filter
selection to one value.

You can change the fields in the following methods of the node exit interface (/OTX/
PF62_IF_NODE). For more information, see “Interface /OTX/PF62_IF_NODE”
on page 373.
• CHANGE_NODE_SEARCH_FIELDS
• CHANGE_NODE_SORT_FIELDS
• CHANGE_NODE_FILTER_FIELDS
Filter fields can be connected to domains with fixed values. In this case, the fixed
values are automatically provided. You can also define or change values in the
CHANGE_NODE_FILTER_VALUES method of the node exit interface (/OTX/PF62_IF_
NODE).
9.6.2.2 Defining and assigning node actions

In this step, you define general actions for a node and assign actions to a node.
To define general node actions:

Workplace > Nodes.
3. In the Nodes Overview, double-click Node actions in the Dialog Structure.
4. In the Node actions Details screen, define general actions for the Action ID,
• Action dialog class: Enter a class with logic for the action. The class must
implement the /OTX/PF62_IF_ACTION_DIALOG interface.
• Perspective ID
• Transport type: Choose one of the following options:
– No transport required (default)

– Customizing request
– Workbench request
To assign actions to an individual node:

Workplace > Nodes.
3. In the Nodes Overview, mark an entry, and then double-click Assign node
actions in the Dialog Structure.
4. In the Assign node actions Details screen, configure actions for the node, using

9.6. Workplace
• Action ID: Enter the ID for the action.

• UI 5 button type: Choose one of the following types:
– Accept type (blue button)

– Default type (no special styling)
– Emphasized type
– Reject style (red button)
– Transparent type
– Unstyled type (no styling)
• Web Icon: Enter the icon that is displayed on the action button.
• Action text: Enter the text that is displayed on the button.
9.6.2.3 Configuring the data binding for the master list

In this step, you configure the display of a work object in the master list. Objects in
the master list have the following layout.
Note: You can change the settings of this customizing by an implementation of

method CHANGE_OBJECT of the web handler class (see “CHANGE_OBJECT”
on page 403).
Figure 9-8: Layout of the master list
To configure the master list:

Workplace > Nodes.
3. In the Nodes Overview screen, mark a node, and then double-click Master List
- Data Binding in the Dialog Structure.
4. Configure the layout of the item list using the following parameters. For an
example, see Figure 9-8.
In all fields, you can use the field content of the display structure of the work
object by using the pattern <field name>.
Example: 2nd attribute: by <CREATOR_NAME>
• Work object type: Work object type for which this list layout is used
• Node ID
• Icon ID UI5: Define a UI5 icon that should be displayed.
• Mark as flagged: The flag icon is displayed.
• Mark favorite: The favorite icon is displayed.
• Intro text
• Item title
• Number
• Number state: The fields 1st Status and 2nd Status will be colored according
to the status value: Error - red, Warning - yellow, Success - green, None -
black ).
• Unit text
• 1st Attribute
• 2nd Attribute
• 1st Status
• 2nd Status
• Bulk actions active: If this check box is selected, all objects displayed in the
master list can be used for bulk actions. If the availability of bulks actions
needs to be calculated for each object, implement this in method CHANGE_
OBJECT of interface /OTX/PF62_IF_ITEM_HANDLER.

9.6. Workplace
9.6.2.4 Customizing a full screen list

The full screen list pattern gathers all information about processes in a table
structure on a single page.
To customize a full screen list:

Workplace > Nodes.
3. In the Nodes Overview screen, mark a node, and then double-click Full Screen
List in the Dialog Structure.
4. In the Full Screen List Overview screen, customize the full screen list’s device
specific settings, using the following parameters:
Device typ
The following settings are available:
• Tablet
• Desktop
• Smart Phone
• All Devices
• Hybrid Devices
Exp. field
If you select the option, advanced line items and full screen lists download
an Excel sheet with technical fieldnames as column headers. If it is not
selected, the label description is used as column header.Y
You can use FSList (node) and Perspective exits to redefine settings at
runtime.
Export
Select this check box to enable download of the displayed table content into
Microsoft Excel.
Paging
Select this check box to enable paging of the displayed table. The page size
of the node is only considered if paging is disabled.
Actions
Select this check box to display the Action menu for row actions.
No Setting
Select this check box to disable table settings.
5. To search, sort, or filter fields, mark a node in the Nodes Overview screen, and
then double-click Search fields, Sort fields, or Filter fields in the Dialog

Structure. For more information, see “Adding fields for searching, sorting, and
filtering to a node” on page 313.
You can change the fields in the following methods of the node exit interface (/
OTX/PF62_IF_NODE). For more information, see “Interface /OTX/
PF62_IF_NODE” on page 373.
• CHANGE_NODE_SEARCH_FIELDS
• CHANGE_NODE_SORT_FIELDS
• CHANGE_NODE_FILTER_FIELDS
• CHANGE_NODE_FILTER_VALUES
6. In the Full Screen List Overview screen, mark a device type, and then double-
click Full Screen List - Actions in the Dialog Structure.
7. In the Full Screen List - Actions Overview screen, customize actions, using the
Action Type
The following action types are available:
• Show popup
• Show inplace
• Navigate to semantic object
• Call action dialog
• No link
Description
Defines the text that is displayed in the ActionSheet.
Action ID
ID of the action to be performed in the row.
Type
Specify the Row Action Type. In this list, click one of the following action
types:
• Add
• Copy
• Delete
• Up
• Down
• Action Dialog ( Set ActionDialog class in Nav. link param. )

9.6. Workplace
• Semantic Navigation (Set Nav. link parameter ): For more

information, see “Semantic object navigation with the Fiori Task App”
on page 279
• Field Popup ( Set Perspective Id in Nav. link parameter )
• Change page in flexible column layout (parameter = page id)
Position
Specify with sequential numbering, where the action is positioned on the
screen.
Action dialog class
Enter the action dialog class.
Web Icon
Nav. link parameter
Enter the navigation link parameter. It depends on the settings in Row
Action Type.
Transport type

Not In Action Sheet

Not in Action Sheet. Select this check box to specify that the action is not
displayed in the action sheet of the row.
Action text
Enter the text that is displayed on the action button.
Tooltip
Enter the tooltip that is shown for the action button.
No Lock Required
Select this check box when the Fiori app should not set a lock for the current
object before executing the action.
8. Double-click Full Screen List - Columns in the Dialog Structure.

9. In the Full Screen List - Columns screen, customize columns, using the
Field Name
Name of the attribute field. You can use all fields available in the display
structure of the work object type. The values for these fields are
automatically set by the framework. You can define additional fields, the

values for these fields must be set in the implementation of the Full Scr. List
Exit.
Position
Define the sequence of the columns.
Width
Enter the width of the column as a valid CSS size. For more information, see
the SAP UI5 API Reference: https://sapui5.hana.ondemand.com/#/api/
sap.ui.core.CSSSize.
Column type
The following values are available: DEFAULT | MANDATORY | AVAILABLE |
HIDDEN.
Action ID
Enter the ID of the action to be performed in the column.
Display Type
The following values are available:
• Standard field (default)

• Display as checkbox
• Amount field. Define currency in field EXT_VALUE
• Display as switch
• Display as icon
• Object Identifier
Description
Enter a meaningful description of the column.
Tooltip
Enter a tooltip for the column.
Value Ext. Field
(Value in External Field): The value of this field is set in an external value
field. Currently only used for display type Amount field to set the
currency.
Default Value
The value of this field is used for display type Display as icon if no other
value has been selected for this field. This allows to define a default icon.
You can overwrite the value in the full screen list exit method /otx/pf63_
if_fs_list~change_data.

9.7. Configuring the data binding of perspectives
9.6.3 Assigning nodes to work centers

To assign nodes to work centers:
Workplace > Assignment of Nodes to Work Center.
3. In the Assignment of nodes to Work Center Overview screen, assign nodes to

work centers using the following parameters:
Work Center ID
Node ID
Unique ID of the node.
Work object type
The node is defined by the Node ID and the work object type. Therefore,
you enter the work object type of the Node ID or the work object type
assigned to the Node ID. The actual work object type has already been
defined in the node customizing. For more information, see “Defining
Node pos.
Node position. Define the sequence of the nodes.
Separator
Select the separator of the tabs in the Tab Bar of the Fiori Task App.
Agg. Count
Aggregated count. Select this check box to show the node as aggregated
count. Nodes with aggregated count are highlighted and contain all objects
that are shown in the nodes of the work center.
9.7 Configuring the data binding of perspectives

With Business Center 16.3 and later, perspectives are maintained using the
Perspective Editor. For more information, see “Editing perspectives and layouts”
on page 281.
On the top level, you can enter the perspective class. This class needs to implement
the /OTX/PF62_IF_PERSPECTIVE_CLASS interface. The actual contents of
perspectives are configured in the Business Center IMG. This includes:
• Attribute list view, table view setting and DataBinding

• Property bindings
This section describes the necessary steps.

9.7.1 Configuring the attribute list view

The attribute list view always displays the customized attributes in a vertical layout,
showing one attribute at each line. For each attribute a label, the value and a value
description can be displayed.
To configure the attribute list view:

Perspectives > Data Binding.
3. On the Perspective Overview screen, mark a perspective, and then double-click
Attribute List View in the Dialog Structure.
4. On the Attribute List View Overview screen, choose one of the available
Perspective view IDs that you want to use for the perspective.
5. To define attribute view settings, mark a perspective view ID, and then double-
click Attribute View Settings in the Dialog Structure.
6. On the Attribute View Settings Details screen, define attribute view settings,
Editable
To allow the view to be edited in general, select this check box.
Selection Listener
To configure that the data of this view can be changed at runtime, select this
check box. This refers to method /OTX/PF62_IF_PERSPECTIVE_
CLASS~CHANGE_DATA of the perspective class. If an association for this view
is maintained and the table changes the parent item, the data for this view is
automatically selected if a selection event is raised.
Association Name
Enter the association name.
An attribute list can either show the data of the root work object type or, if
the association is maintained, an associated work object type.
By setting the association, the fields of the associated work object type are
available for the customizing, and the data of the associated work object
type is selected. For more information, see “Defining the work object type
association” on page 254.
If choosing a not-associated work object type, the attributes of the root work
object type can be used.
7. Save your changes before you navigate down in the folder structure.
8. Double-click Attributes in the Dialog Structure.
9. On the Attributes Details screen, define attributes, using the following
parameters:

Field Name
Name of the attribute field.
Position
Define the sequence of the attributes.
Display Type
Configure the way the attribute is displayed. The following values are
available:

• Display as checkbox (requires boolean)
• Display a switch
• Display as icon: The value of this field is considered as icon name
Value description
Select this check box to display a description behind the value field.
The value description is not automatically set, but has to be implemented in
the /OTX/PF62_IF_PERSPECTIVE_CLAS~CHANGE_DATA method of the
perspective class.
The /OTX/PF62_IF_PERSPECTIVE_CLAS~UPDATE_ATTRIBUTES method
enables you to change the value description after the value has changed.
Update on change
Select this check box to trigger the UPDATE_ATTRIBUTES method of the /
OTX/PF62_IF_PERSPECTIVE_CLASS if the value of the field is changed. For
more information, see “UPDATE_ATTRIBUTES” on page 427.
Editable
To allow the attribute to be edited, select this check box. This setting is only
considered if the complete view is set to editable. For more information, see
“Configuring the header view” on page 441.
Required
To set the attribute as required, select this check box.
Search help ID
Unique ID of the search help that corresponds with the attribute.
Help variant
Select the type of help. The following types are available.
• F4 help only: Users can only select and enter values using a search
help.
• F4 help with suggestions: Users can directly enter values. When the
user enters a value which fits for one or several values of the search
help, these values are displayed as suggestions. The user can select
them. Alternatively, the user can select the values using a search help.

• Drop-down list: Users can select values in a drop-down list.

• Suggestions: When the user starts to enter a value suggestion, suitable
values from the search help are displayed, which the user can select.
• F4 help with input field: Users can either directly enter values for
this field or select them using a search help.
Used Help Field

Define the field in the help structure whose value should be written to the
attribute view field. You only need to specify this if the field name in the
help structure is not equal to the field name in the attribute view.
Link type
This field defines the type of the link for semantic object navigation.
Possible values:
• No link
For more information, see “Semantic object navigation with the Fiori Task
App” on page 279.
Link parameter
This field contains the JSON with the link parameters. For more
on page 279. The JSON data must match the following structure:
{
"target": {
"action": <action>
},
"params": {
}
}
Description
Enter a meaningful description of the attribute.
10. Double-click Related fields under Attribute View Settings in the Dialog
Structure.
11. On the Related fields Overview screen, define related fields for the attribute.
You can use the related fields to react on value changes in fields of other
attribute views. For this, set the Update on change check box of the related
attribute field to true and enter the field in the related fields settings of the
attribute list that wants to react on these value changes. In case of a value
change, you can update the attribute in method /OTX/PF62_IF_PERSPECTIVE_
CLAS~UPDATE_AFTER_REL_ATTR_LIST_CHG of the perspective class.

Perspective view ID
Enter the view ID.
Field Name
Enter the field name.
9.7.2 Configuring the table view

Define the contents of the tables that you want to use in a perspective.
Each view represents one table. The columns display as customized. You can give
the user the possibility to change the displayed columns. Depending on the screen
size the rows are displayed in horizontal or vertical layout.
To configure the table view:

Table View in the Dialog Structure.
4. On the Table View Overview screen, mark a perspective view ID, and then
double-click Header View in the Dialog Structure.
5. On the Header View Details screen, define the content for the header, using the
Association Name
Objects of the associated work object type are selected according to the
constraints defined in the association settings. For more information, see
“Defining the work object type association” on page 254.
Editable
To define that the table can be edited in general, select this check box.
Grouping Fieldname
Define the field for grouping. The entries of the table are grouped by their
values of the defined field.
Grouping Title Field
Field containing the text that is displayed as the grouping title.
Row Action Available
Select this check box to make the action sheet in the rows available.
Paging Is Active
Select this check box to activate paging. If this check box is cleared, all
entries are displayed at once.

Rearrange Is Active
Select this check box to allow changing the order of the table entries.
Selection Mode
Define if an entry of the table can be selected or not. The following options
are available:
• Single entry
• No selection
Selection Event
Select this check box to let the table raise an event when the user selects a
different table entry. Attribute and table views listening to the selection
event are then updated (data selection for associations and method /OTX/
PF62_IF_PERSPECTIVE_CLAS~CHANGE_DATA of perspective class).
Selection Listener
Select this check box to specify that the table listens to selection events of
other tables of this perspective.
Compare Is Available
Select this check box to define that the Compare button is available. This
button allows the user to undo actions.
Row Icon
Enter a SAP UI 5 icon that is displayed in front of the row title.
Row State
State of the row title state. Possible values:
• ERROR
• NONE
• SUCCESS
• WARNING
Is Expandable
Select this check box to set that the table can be expanded. This is only
relevant for views view.item.AdvLineItemsVertical and view.item.
AdvLineItemsResponsive.
Is Expanded
Select this check box to set that the table is initially displayed in expanded
mode. This applies only if Is Expandable is selected.
No Settings
Select this check box to set that the layout of the table is fix. No settings
button is displayed for user specific settings.

Export enabled
Select this check box to configure that all columns visible for the user can be
downloaded to a Microsoft Excel file, using a Download button. By hiding
columns, users can restrict the downloaded columns.
Export Fieldname
If you select the option, advanced line items and full screen lists download
an Excel sheet with technical fieldnames as column headers. If it is not
selected, the label description is used as column header.Y
You can use FSList (node) and Perspective exits to redefine settings at
runtime.
Table Title
Text displayed as table title.
Row Title
Define the row title that is shown in vertical tables on top of each row. You
can enter placeholders (<field name>) to use field contents of the rows.
Example: Item Number <ITEM_NR> - Material <MATNR>
Row Description
Text is displayed above row. Only displayed at AdvLineItemsVertical.
6. Double-click Columns in the Dialog Structure, and then double-click a column,

or add a new column.
7. On the Columns Details screen, configure the column, using the following
parameters:
Field Name
Field name
Filter Mode
The following options are available:
• No filter option
• Filter with selectable values
• Search with string
Position
Define the sequence of the columns.
Description
Enter a meaningful description of the column.
Editable
To allow the field to be edited, select this check box.
Required
To set the column as required, select this check box.

Action ID
Enter the ID of the action to be performed in the column.
Column type
Choose the column type to define the display behavior of the columns. The
following values are available:
Default
Column is automatically displayed, the user can hide it.
Mandatory
Columns of this type are always displayed.
Available
Column is not automatically displayed, the user can switch it on.
Hidden
Column is included in table, but is not displayed, the user cannot
switch it on.
Display Type
Configure the way the column is displayed. The following values are
available:

• Display as icon
• Object Identifier
In a column of this type, the value in field VALUE is displayed as a
heading and the value in field VALUE_EXT is displayed as a subheading.
Width
Enter the width of the column as a valid CSS size. For more information, see
the SAP UI5 API Reference: https://sapui5.hana.ondemand.com/#/api/
sap.ui.core.CSSSize.
Copy Value
Select this check box to specify that the value of the column is transferred to
a new row at copy action.
Update on change
Select this check box to trigger the UPDATE_ROW_VALUES method of the /
OTX/PF62_IF_PERSPECTIVE_CLASS if the value of the field is changed. For
more information, see “UPDATE_ROW_VALUES” on page 424.
Search help ID
Unique ID of the search help that corresponds with the column.

Used Help Field

Define the field in the help structure whose value should be written to the
attribute view field. You only need to specify this if the field name in the
help structure is not equal to the field name in the attribute view.
Help variant
help.
8. Double click Related fields under Header in the Dialog Structure.

9. On the Related fields Overview screen, define related fields for the column,
Perspective view ID
Enter the unique ID of the perspective view.
Field Name
Enter the field name of the display structure of the work object type.
10. Mark an perspective view ID, and then double-click Row Actions - Default in
11. On the Row Actions - Default Details screen, configure default row actions for
the table, using the following parameters:
Add (PF62 ADD)

Select this check box to configure an Add action to the table row.
Copy (PF62 COPY)
Select this check box to configure a Copy action to the table row.
Delete (PF62 DEL)
Select this check box to configure a Delete action to the table row.
Up (PF62 UP)
Select this check box to configure an Up action to the table row.
Up (PF62 DOWN)
Select this check box to configure a Down action to the table row.

12. Double-click Row Actions - Custom in the Dialog Structure.
13. On the Row Actions - Custom Details screen, configure custom row actions for
the table, using the following parameters:
Action ID
ID of the action to be performed in the row.
Type
Specify the Row Action Type. In this list, click one of the following action
types:
• Add
• Copy
• Delete
• Up
• Down
• Action Dialog ( Set ActionDialog class in Nav. link param. )
• Semantic Navigation (Set Nav. link parameter ): For more
on page 279
• Field Popup ( Set Perspective Id in Nav. link parameter )
• Change page in flexible column layout (parameter = page id)
Position
Specify with sequential numbering, where the action is positioned on the
screen.
Action dialog class

Enter the action dialog class.
Web Icon
Nav. link parameter

Action Type.
Transport type


Not In Action Sheet

Not in Action Sheet. Select this check box to specify that the action is not
displayed in the action sheet of the row.
Action text
Enter the text that is displayed on the action button.
Tooltip
Enter the tooltip that is shown for the action button.
No Lock Required
Select this check box when the Fiori app should not set a lock for the current
object before executing the action.
9.7.3 Configuring the data binding of AttributeList and

AdvancedLineItems views
You can maintain the attribute list view and table view in the customizing IMG.
Alternatively, you can maintain them using the Perspective Editor. For more
information, see “Editing perspectives and layouts” on page 281. This section
describes the configuration using the Perspective Editor.
To configure the data binding of views AttributeList and AdvancedLineItems:
1. Open the context menu on the tree node where you want to maintain the
binding.
2. To add a binding, click Add Binding.

a. In the Select a Work Object Type Association dialog box, select a valid
Work Object Type (Association) for the view.
The available associations depend on the view:
• For an AttributeList, you can select the Root Work Object Type or
any other 1:1 association.
• For an AdvancedLineItems view, you can select only 1:N associations.
b. When you have selected the association, confirm Save Changes.
Note: You cannot change the selected association for the binding later
on. In case of a wrong association, delete the binding and create a new
one.
3. To edit a binding, click Edit Binding:
The Binding maintenance application for the specific view is launched.
4. To remove a binding, click Remove Binding
The binding is removed.

Note: Unless all views - for which a data binding is necessary - are bound,
the perspective does not run correctly and the Perspective Editor shows a
warning.
9.7.3.1 Configuring attribute list binding in the Perspective Editor

In this step, you configure the binding of the attribute list, depending on the
perspective. In Business Center 16.3.1 and later, you can perform this configuration
using the Perspective Editor. Before, this configuration could only be performed
using the customizing IMG. For more information, see “Configuring the attribute list
view” on page 322.
To configure attribute list binding:
1. To open the Perspective Editor from the Launchpad, click the Maintain
Perspectives tile.
2. Click the Perspective ID.
3. In the Edit Perspective view, right-click a view of type view.item.

AttributeList.
4. To open the Attribute List Binding Data View Maintenance, click Edit Binding.

5. On the GENERAL SETTINGS tab, define attribute view settings, using the
Association Name
An attribute list can either show the data of the root work object type or, if
the association is maintained, an associated work object type.
By setting the association, the fields of the associated work object type are
available for the customizing, and the data of the associated work object
type is selected. For more information, see “Defining the work object type
association” on page 254.
If choosing a not-associated work object type, the attributes of the root work
object type can be used.
Editable
Listens To Selection Event
To configure that the data of this view can be changed at runtime, select this
check box. This refers to method /OTX/PF62_IF_PERSPECTIVE_
CLASS~CHANGE_DATA of the perspective class. If an association for this view
is maintained and the table changes the parent item, the data for this view is
automatically selected if a selection event is raised.
6. On the ATTRIBUTES tab, define attributes, using the following parameters:
Field Name
Name of the attribute field.

Display Type
Configure the way the attribute is displayed. The following values are
available:

Editable
considered if the complete view is set to editable.
7. On the RELATED FIELDS tabs, define related fields for the attribute.
You can use the related fields to react on value changes in fields of other
attribute views.
For this, set the Update on change check box of the related attribute field to true
and enter the field in the related fields settings of the attribute list that wants to
react on these value changes. In case of a value change, you can update the
attribute in method /OTX/PF62_IF_PERSPECTIVE_CLAS~UPDATE_AFTER_REL_
ATTR_LIST_CHG of the perspective class.
Perspective view ID
Enter the view ID.
Field Name
9.7.3.2 Configuring advanced line items binding in the Perspective

Editor
In this step, you configure the binding of advanced line items, depending on the
perspective. In Business Center 16.3.1 and later, you can perform this configuration
using the Perspective Editor. Before, this configuration could only be performed
using the customizing IMG. For more information, see “Configuring the table view”
on page 325.
To configure advanced line items binding:
1. To open the Perspective Editor from the Launchpad, click the Maintain
Perspectives tile.
2. Click the Perspective ID.

3. In the Edit Perspective view, right-click a view of type view.item.

AdvLineItems, and then click Edit Binding.
4. On the GENERAL SETTINGS tab, define advanced line items settings, using
Association Name
Objects of the associated work object type are selected according to the
constraints defined in the association settings. For more information, see
“Defining the work object type association” on page 254.
Editable
Is Expandable
Select this check box to define that the table can be expanded or collapsed
by the user.
Is Expanded
Select this check box to define that the table is initially displayed expanded
(only relevant if the Is Expandable check box is set).
Table Title
Define the overall title of the line item table.
Grouping Fieldname
Define the field name for grouping. The entries of the table are grouped by
their values.

Grouping Title Field

Define the title of the group. If you do not add a value for the Grouping
Title Field, the content of the Grouping Fieldname is used as title of the
group.
Compare Action Is Available
Select this check box to define that the Compare button is available. This
button allows the user to undo actions.
Selection Event Is Active
Select this check box to let the table raise an event when the user selects a
different table entry. Attribute and table views listening to the selection
event are then updated (data selection for associations and method /OTX/
PF62_IF_PERSPECTIVE_CLAS~CHANGE_DATA of perspective class).
Listens To Selection Event

Select this check box to specify that the table listens to selection events of
other tables of this perspective.
Settings are not displayed
Select this check box to define that the settings option is not available for the
user.
Paging Is Active
Select this check box to activate paging. If this check box is cleared, all
entries are displayed at once.
Rearrange Is Active
Select this check box to allow changing the order of the table entries.
Row title
Enter the title of the row. The title is displayed above the cell values of the
row.
Row Icon
Enter the icon that displays in front of the row title.
Row Description
Enter the description of the line, which is displayed below the row title.
Row Actions Are Available
Select this check box to make the action sheet in the rows available.
Selection Mode
Define if an entry of the table can be selected or not. The following options
are available:
• Single entry
• No selection
Row State
Define the row state. The row is highlighted in the color of the state.
Available states are:

• None (default)
• Success
• Warning
• Error
• Information
5. On the COLUMNS tab, configure advanced line item columns, using the
Field Name
Name of the column.
Column Type
Select one of the following types: Default, Mandatory, Available, Hidden.
Display Type
Configure the way the column is displayed. The following values are
available:

• Object: Object Identifier
Editable
considered if the complete view is set to editable.
6. On the RELATED FIELDS tab, define related fields for the column, using the
Perspective view ID
Enter the view ID.
Field Name
7. On the DEFAULT ROW ACTIONS tab, configure default row actions for the
table, using the following parameters:
Defaut Action Add (PF62 ADD)

Select this check box to configure an Add action to the table row.

9.8. Input helps
Defaut Action Copy (PF62 COPY)

Select this check box to configure a Copy action to the table row.
Defaut Action Delete (PF62 DEL)
Select this check box to configure a Delete action to the table row.
Defaut Action Up (PF62 UP)
Select this check box to configure an Up action to the table row.
Defaut Action Down (PF62 DOWN)
Select this check box to configure a Down action to the table row.
8. On the CUSTOM ROW ACTIONS tab, configure custom row actions for the
advanced line items, using the following parameters:
Action ID
Enter the ID of the action to be performed in the row.
Row Action Type
In this list, click one of the following action types:
• Add
• Copy
• Delete
• Up
• Down
• Action Dialog (Set ActionDialog class in Nav. link param.)
• Semantic Navigation (Set Nav. link parameter)
• Field Popup (Set Perspective Id in Nav. link parameter)
Nav. link parameter

Action Type on page 339.
9.8 Input helps

You can customize input helps for editable fields in the header data area and in the
detail area of the Fiori Task App using the Web Services customizing.
Note: Input helps can be set for item fields or header details. For item fields,
see “Configuring line item details” on page 445. For header details, see
“Configuring the item header details” on page 442. If no input help IDs are set
for editable fields in these customizing settings, then the header or item
structure is checked if an SAP help (F4 help or domain values) is assigned to
this field. The assigned help is then automatically used in the web service.

The input helps can display a maximum number of 100 domain values or results of
SAP search helps. You can also use the /OTX/PF62_BADI_INPUT_HELP user exit to
change or set the values and the structure of the input helps.
To customize input helps:
2. Click OpenText Business Center for SAP Solutions > Web Services > Input
helps > Input helps.
3. In the Input Helps Overview screen, customize input helps using the following
parameters.
Search help ID
Unique ID of the search help that corresponds with the input help.
Value type
Select the value type from the list. The following value types are available.
• Domain values: fixed values of a domain.

• Search helps: results of SAP search helps.
• Only user exit (BAdI /OTX/PF62_BADI_INPUT_HELP).
Type Name
Enter the technical name of the domain or search help.
Description
Enter a meaningful description of the input help.
4. Optional To customize related fields for the input help, mark an entry in the Input
Helps Overview screen, and then double-click Related fields in the Dialog
Structure.
Related fields are passed to the search query along with the field that you
search for. They limit the number of search results. As a prerequisite, related
fields must contain values that are shown in the header data area and in the
detail area.
5. Optional In the Related Fields Overview screen, enter a Field Name according to
the Search Help ID.
At the first call of an input help in the Fiori Task App, the framework generates
additional information for this input help. After each change to the settings of an
input help or the used search help, these data needs to be deleted. You can do this in
the /OTX/PF62_ADMIN transaction, option Clean Up Search Helps. For more
information, see OpenText Vendor Invoice Management for SAP Solutions -
The /OTX/PF62_BADI_INPUT_HELP BAdI implements the /OTX/PF62_IF_BAPI_HELP

interface. The following interface methods are available:

9.9. Action dialog box
• CHANGE_HELP_COLUMNS
• CHANGE_HELP_ROWS
• CHANGE_FILTER_OPTIONS
For more information, see “BAdI /OTX/PF62_BADI_INPUT_HELP” on page 435.
9.9 Action dialog box

Business Center 16 SP1 introduces the Action dialog box, which is a further
development of the Confirm dialog box. The Action dialog box infrastructure runs in
parallel to the existing Confirm dialog box. Unlike the Confirm dialog box, which is
suited for rather simple use cases, the Action dialog box is designed for complex use
cases, with, for example, more than 3 fields and field dependencies, where full
control over the dialog box is necessary.
Note: Starting with Business Center 16.3.2, you can also use the Action dialog
box for bulk actions.
The Action dialog box provides the following features:
• You can use various input field variants (for example MultiCombo,
ValueHelpInput, TextArea) in an arbitrary count.
• You can implement custom fields (views).

• You can model and handle dependent fields in the backend.
• You can freely define layout.
• Several messages with different type can be displayed.
• Validation can be performed on field level.
The following graphic shows an example of an Action dialog box:

Action dialog box - architecture
• The content area of the Action dialog box is filled with a new kind of perspective:
an Action dialog box perspective.
• An Action dialog box perspective generally works like an Item perspective. The
difference is that the Action dialog box perspective can include only views in the
namespace ot.approve.requests.view.dialogPart.*. The reason for this lies
in the view interface, which is specific for any type of perspective.
• You can use DialogPart views multiple times in an Action dialog box
perspective. An item view is only allowed to be used once. The following
DialogPart views are available:
DialogPart input views
– MultiComboInput
– TextAreaInput
– ValueHelpInput
– Table
– DialogButton
DialogPart read-only views
– DescriptiveText
– ActionMessages

9.9.1 Assigning a data collection to a work object type

Action dialog boxes require a data collection. Data collections are used to store and
administer data for a limited time, for example during the editing of a task or the
execution of an Action dialog box. In the context of the Fiori Task App, you can
define data collections for a work object type. For data collections, you must
implement the interface /OTX/PF62_IF_DATA_COLLECTION.
To assign a data collection to a work object type:
double-click Data Collections in the Dialog Structure.
4. Assign the data collection to the work object type using the following
parameters:
Data Coll. Scope

Data Collection Scope. Each data collection has a unique scope for which it
is used. In the list, click Action Dialog.
Data Collection
Enter the data collection for the work object type.
9.9.1.1 /OTX/PF62_IF_DATA_COLLECTION interface

The interface comprises the following methods:
/OTX/PF00_IF_DATA_COLLECTION~GET_INSTANCE
Returns data collection instance.
Parameters:

PI_COLLECTION_ID Importing Data collection ID
PIT_KEYS Importing Object key
PI_CLASSNAME Importing Data collection class
PRH_INSTANCE Returning Data collection
/OTX/PF00_IF_DATA_COLLECTION~CREATE_COLLECTION
Creates data collection. You can use this method for initially collecting the data.
Parameters:


PIS_DATA_COLLECTION Importing Data collection information
Structure of PIS_DATA_COLLECTION:
Field name Description

ID Data collection ID
SCOPE Scope
CLASS Data collection class
/OTX/PF00_IF_DATA_COLLECTION~REMOVE_COLLECTION
Implement this method to remove the collected data. This method does not have
any parameters.
/OTX/PF62_IF_DATA_COLLECTION~SET_ADDITIONAL_INFORMATION
This method provides additional information in the context of the Fiori Task
App.
Parameter:

PI_LAST_CHANGED Importing Timestamp of the last change
made to the current object.
9.9.2 Customizing action dialog boxes

To customize action dialog boxes:
3. In the Work object type Overview screen, mark a work object type, and then
double-click Actions in the Dialog Structure.
For more information, see “Defining and assigning node actions” on page 314.
4. Customize action dialog boxes using the following parameters:
• Actions of type Action dialog require a Perspective ID and an Action

dialog class implementing the /OTX/PF62_IF_ACTION_DIALOG interface.
For more information, see “Editing perspectives and layouts” on page 281.

9.9.3 Example: an Action dialog box layout

This example is based on an Action dialog box with error and warning messages, an
input field, a button, a table that displays some information, and a comment field.
See the following graphic and the description:
This action dialog box requires the following customizing:
Perspective
Perspective ID Z_EXAMPLE
Perspective type ACTION_DLG (Perspective for action dialog)
BSP Application [ot_bc_app]
BSP Module [ot_bc_app_namespace]
Template ID [ot_bc_app_namespace].templates.ActionDialogForm
Perspective name Example
Perspective views:
Error messages
• Perspective View ID: PF63_AM_ERROR

• Parent ID: vLayoutBefore
• Position in container: 0
• BSP application:
• BSP module:
• BSP view: ot.approve.requests.view.dialogPart.ActionMessages

• Description: Error messages

• Web Icon:
• CSS class: ot_actionDialogForm_displayNoBlock
• Label position
• Label Parent ID
• Description position
• Desc. Parent ID
Warning messages
• Perspective View ID: PF63_AM_WARN

• Parent ID: vLayoutBefore
• BSP application:
• BSP module:
• BSP view: ot.approve.requests.view.dialogPart.ActionMessages
• Description: Warning messages
• Web Icon:
• CSS class: ot_actionDialogForm_displayNoBlock
• Label position
• Label parent ID
• Description position
• Desc. Parent ID
Input field
• Perspective View ID: VHI_INPUT

• Parent ID: matrixLayout
• Position in container: 1,0
• BSP view: ot.approve.requests.view.dialogPart.ValueHelpInput
• Description: Input field
• Label position: 0,0
• Label parent ID: matrixLayout
Button
• Perspective View ID: B_BUTTON

• Parent ID: matrixLayout

• Position in container: 2,0

• BSP view: ot.approve.requests.view.dialogPart.DialogButton
• Description: Example button
Information table
• Perspective View ID: T_INFORMATION

• Parent ID: vLayoutAfter
• BSP view: ot.approve.requests.view.dialogPart.Table
• Description: Table with information
Comment field
• Perspective View ID: TAI_COMMENT

• Parent ID: vLayoutAfter
• BSP view: ot.approve.requests.view.dialogPart.TextAreaInput
• Description: Field for comments
• CSS class: ot_actionDialogForm_stretch_textarea
9.9.4 /OTX/PF62_IF_ACTION_DIALOG interface

The following attributes are available for the interface:
M_CLASSNAME
Name of the currently used class.
M_PLTT
Life time token of the perspective from which the action is called.
M_PERSPECTIVE
The perspective that is used in the action dialog.
M_IS_A_BULK_ACTION
Flag if the current action is executed as bulk action.
The /OTX/PF62_IF_ACTION_DIALOG interface comprises the following methods:
• “CHANGE_BULK_OBJECTS” on page 348

• “GET_ACTION_DIALOG” on page 349
• “GET_TEXT_AREA” on page 350
• “GET_MSG_CONTAINER” on page 351
• “GET_MESSAGES” on page 352

• “GET_INPUT_FIELD” on page 353

• “GET_TEXT_AREA_INPUT” on page 355
• “GET_DROP_DOWN” on page 356
• “GET_BUTTON” on page 357
• “GET_TABLE” on page 358
• “GET_FILE_UPLOAD” on page 361
• “SET_MESSAGE” on page 362
• “CREATE_ACTION” on page 362
• “EXECUTE_ACTION” on page 363
• “EXECUTE_LINE_ITEM_ACTION” on page 364
• “UPDATE_DIALOG” on page 365
9.9.4.1 CHANGE_BULK_OBJECTS
This method is called before the GET_ACTION_DIALOG method is called. The selected
objects, that could be locked, are contained in parameter PIT_BULK_OBJECTS.

PI_DEVICE Importing Device type. Possible values:
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PIH_DATA_COLLECTION Importing Data collection instance

PIT_BULK_OBJECTS Importing Set the title for each object using the
SET_TITLE method.
Use the EXCLUDE_OBJECT method to
exclude objects from this list. When
calling the method, you can set the
message that is displayed in the
overview of the selected objects.

9.9.4.2 GET_ACTION_DIALOG
This method returns main information for the Action dialog box.

PIT_KEYS Importing Object keys
PIT_ACTION_OBJECT Importing Contains instances of the selected work
objects.
Also contains the work object in case of
a single action.
Importing parameter PIT_KEYS is not
set in case of bulk actions.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PES_ACTION_DIALOG Exporting Action dialog box information
PET_RETURN Exporting Messages
PE_ERROR_TYPE Exporting Error type
Structure of the PES_ACTION_DIALOG parameter:

TITLE Dialog title.
ICON Icon.
BUTTON_TITLE Title of action button.
BUTTON_ICON Icon for action button.
BUTTON_TOOLTIP Tooltip for the action button.
EXPAND_ON_PHONE Dialog box should be expanded on smartphone.
CONTENT_WIDTH Width of dialog box.
PERSPECTIVE_ID Use to change the perspective for the dialog.
MSG_TEXT Message text. For details, see STATUS (following row)


STATUS Possible values:
DIALOG: opens the dialog box (default value).
MSG_SUCC: displays a success messsage in the
MSG_TEXT field without showing the dialog box.
MSG_ERROR: displays an error message in the
MSG_TEXT field without showing the dialog box.
MSG_EXIT_HANDLING Defines the behavior of the application after the message
has been displayed. Possible values:
REFR_COMPL: Refresh the complete app.
REFR_ITM: Refresh the current item.
REMOVE_ITM: Remove the current item from the
master list and display the details of the next item.
DIALOG_STATE You can configure a state for an action dialog. The action
dialog is colored according to the DIALOG_STATE
value.
Possible values:
ERROR
NONE
SUCCESS
WARNING
Default value is NONE.
9.9.4.3 GET_TEXT_AREA
This method returns the definition of a text area.

PI_VIEW_ID Importing Perspective View ID
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

objects.
a single action.


PES_TEXT_AREA Exporting Text area definition
Structure of the PES_TEXT_AREA parameter:

UPDATE_ON_VALUE_CHANGE Set this flag if the view should be re-read after the
UPDATE_DIALOG method has been called.
UPDATED Text has been changed and field update is required.
TEXT Displayed text.
DO_NOT_SHOW Default value is <space>, meaning the object is
displayed.
9.9.4.4 GET_MSG_CONTAINER
This method returns a container for messages.

objects.
a single action.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_VIEW_ID Importing View ID

PES_MSG_CNT Exporting Message container definition

Structure of the PES_MSG_CNT parameter:

UPDATE_ON_VALUE_CHANGE Set this flag if the view should be re-read after the
UPDATED Messages have been changed and update is required.
DESCRIPTION Description for messages.
ICON Message icon.
IS_EXPANDED Expand container for additional messages.
STATE Container state:
00 - None
01 - Error
02 - Information
03 - Success
04 - Warning
MORE Additional messages are available.
VISIBLE Container box is visible.
9.9.4.5 GET_MESSAGES
This method returns messages for a message container.

objects.
a single action.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PET_MESSAGES Exporting Messages


PET_RETURN Exporting Error messages
Structure of the PET_MESSAGES parameter:

MESSAGE_ID ID of the message
TEXT Message text
ICON UI5 icon displayed in front of the message
STATE Possible values:
None
01 Error
02 Information
03 Success
04 Warning
9.9.4.6 GET_INPUT_FIELD
This method returns the definition of an input field.

objects.
a single action.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PES_INPUT_FIELD Exporting Input field definition


Structure of the PES_INPUT_FIELD parameter:

TYPE ABAP data type.
LENGTH Length.
LABEL Label text.
VALUE Field value.
HAS_VALUE_DESC The value description is available.
VALUE_DESCRIPTION Value description.
UPDATE_ON_VALUE_CHANGE Trigger update if field value changes.
UPDATE_REQUIRED Set this flag if the view should be re-read after the
REQUIRED Mark field as required.
SHOW_VALUE_HELP Display value help.
VALUE_HELP_ID Value help ID.
VALUE_HELP_VAR Help variant:
01 - F4 help only
02 - F4 help with suggestions
04 - Suggestions
05 - F4 help with input field
VALUE_HELP_MASTER_FIELD Master field of the value help. This is the field in the
value help whose value should be transferred into
the input field.
READ_ONLY Field is read only.
CHECKBOX Display field as check box.
VALUE_STATE Value state:
• ERROR
• NONE
• SUCCESS
• WARNING
VALUE_STATE_TEXT Text for value state.

displayed.

9.9.4.7 GET_TEXT_AREA_INPUT
This method returns the definition for the text area input field.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

objects.
a single action.
PES_TEXT_AREA_INPUT Exporting Text area definition
Structure of the PES_TEXT_AREA_INPUT parameter:

LABEL Label text.
VALUE Field value.


• ERROR
• NONE
• SUCCESS
• WARNING

VALUE_PLACE_HOLDER Placeholder text. It is displayed before the user starts
to edit the field.
displayed.
9.9.4.8 GET_DROP_DOWN
This method returns the definition of the drop-down list (MultiComboInput view).

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

objects.
a single action.
PES_DROP_DOWN Exporting Drop-down definition
Structure of the PES_DROP_DOWN parameter:


LABEL Label text.
VALUE Selected value.
• ERROR
• NONE
• SUCCESS
• WARNING

MULTI_SELECT Set this flag if multiple values can be selected.
ENTRIES Available entries.
displayed.
9.9.4.9 GET_BUTTON
This method returns the definition of a button.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI



objects.
a single action.
PES_BUTTON Exporting Button definition
Structure of the PES_BUTTON parameter:

ICON Button icon.
TOOLTIP Button tooltip.
TEXT Button text.
BUTTON_TYPE Button type:
ACCEPT - Accept type (blue button)
DEFAULT - Default type (no special styling)
EMPHASIZED - Emphasized type
REJECT - Reject style (red button)
TRANSPARNT - Transparent type
UNSTYLED - Unstyled type (no styling)
ENABLED Set this flag if the button is active.
displayed.
9.9.4.10 GET_TABLE
This method returns the table definition.



• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

objects.
a single action.
PES_TABLE Exporting Table definition
Structure of the PES_TABLE parameter:

LABEL Label for table.
REQUIRED Table content must be selected or set. With this flag,
the table will be marked as required.
SELECT_MODE Select mode for table entries:
SINGLE - Single selection
MULTI - Multi selection
DELETABLE - Entry can be deleted.
NONE - No selection
READ_ONLY Set this flag if the table content is read-only and
cannot be changed.
COLUMNS Columns definition.
ITEMS Table items.
displayed.
Structure of the COLUMNS field:


COLUMN_ID Column ID.
TITLE Column title.
READ_ONLY Column is read-only.
PRIO_MOBILE Set this flag if this field should be displayed on a
smartphone with priority. It will still be displayed as
columns, other fields can be displayed as a list.
HELP_ID Value help ID.
HELP_VARIANT Value help variant:
01 - F4 help only
02 - F4 help with suggestions
04 - Suggestions
05- F4 help with input field
HELP_MASTER_FIELD Master field of the value help.
DATA_TYPE ABAP data type.
DATA_LENGTH Field length.
displayed.
Structure of the ITEMS field:

ITEM_ID Item ID.
SELECTED Item is selected.
VALUE_01 Value of column 01
displayed.

9.9.4.11 GET_FILE_UPLOAD
This method defines the layout of the upload control. Called at initial load of Action
Dialog box and after Dialog updates.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PIT_KEYS Importing Object key

objects.
a single action.
PIH_DATA_COLLECTION Importing Data collection
PES_FILE_UPLOAD Exporting File upload control information
Structure of parameter PES_FILE_UPLOAD:

DO_NOT_SHOW Control is not displayed
VALUE_STATE Value state of upload field
VALUE_STATE_TEXT Message displayed
UPDATE_ON_VALUE_CHANGE Value change of upload field triggers update of
ActionDialog.
UPDATE_REQUIRED Control needs to be refreshed by the UI.
BUTTON_ICON Icon on button
BUTTON_TITLE Button title
BUTTON_TYPE Button type


LABEL Label text
PLACE_HOLDER_TEXT Placeholder text in upload field
REQUIRED Upload is required.
MAX_FILE_SIZE Maximum file size in byte
ALLOWED_DOC_CLASSES Allowed document classes (as customized in
V_TOADD)
MULTIPLE Enables the upload of multiple files
Before uploading the file, the VIM Foundation checks if the file fits to the defined file
size and if the mime type fits to the mime type of one of the allowed document
classes. Only the content of documents matching these criteria will be saved in the
system. Error messages of these checks are transferred to the ActionDialog
implementation by calls of method SET_MESSAGE. For more information, see
“SET_MESSAGE” on page 362
9.9.4.12 SET_MESSAGE
This method transfers messages of the VIM Foundation, for example errors
occurring during the file upload, to the ActionDialog implementation. The
ActionDialog implementation has to take care that these messages are displayed.
Class /OTX/PF63_CL_ACTION_DIALOG already provides a logic for handling these
messages.

PI_MESSAGE_TYPE Importing Message type
PI_MESSAGE_TEXT Importing Message text
9.9.4.13 CREATE_ACTION
This method is called at the execution of create actions.

PIS_ACTION_EXECUTE Importing Execute Action dialog action
PET_RETURN Exporting Return parameter table
PES_RESULT Exporting Action dialog result
PCT_KEYS Changing Values for a key
The structure of parameter PIS_ACTION_EXECUTE is explained in detail in method

EXECUTE_ACTION. For more information, see “EXECUTE_ACTION” on page 363.

PCT_KEYS contain the key values as they can be defined by the VIM Foundation. The
solution implementation must take care to set the complete key for the new object.
9.9.4.14 EXECUTE_ACTION
This method is called at the execution of the action.

PIS_ACTION_EXECUTE Importing Action information
PIT_BULK_RESULTS Importing Contains the selected object instances.
For each object, the result needs to be
set using the SET_STATE method.
Possible values are:
UPDATE > Object data is updated in
master list.
REMOVE > Object is removed from
master list.
ERROR > Object processing is
considered as erroneous.
PE_ERROR_HANDLING Exporting Error handling
PES_RESULT Exporting Action result
Structure of the PIS_ACTION_EXECUTE parameter:

LOGSYS Logical system
VIEW_ID View ID
KEYS Object keys
ACTION_ID Action ID
UPDATE_INPUT_FIELDS Input fields with current values
UPDATE_TEXT_AREAS Text areas with current values
UPDATE_SELECTED_ENTRIES Selected entries in drop-down list
UPDATE_TABLE_ITEMS Current table items
UPLOAD_DOCUMENTS File Upload


UPL_DOC_JSON_STRUC Contains table content when a CSV document is
uploaded. The table content has the following
structure:
INDEX
Row index
FIELDNAME
Column name
FIELDVALUE
Cell content
Use the TABLE_DATA_UNPACK_STR method of /

OTX/PF00_CL_UTILITIES class to transfer content
into a solution specific table structure. For more
information, see “/OTX/
PF00_CL_UTILITIES=>TABLE_DATA_UNPACK”
on page 469.
Structure of the PES_RESULT parameter:

MSG Message text
STATUS Dialog status:
DLG_ERROR - Show error in dialog.
GEN_ERROR - Show general action error.
The statuses DLG_ERROR and GEN_ERROR can
also be used in a bulk scenario.
UPDATE - Update object details.
REMOVE - Remove object from master list.
9.9.4.15 EXECUTE_LINE_ITEM_ACTION
This method is called at the execution of an ActionDialog action started from an item
in the AdvLineItem table.

PIS_ACTION_EXECUTE Importing Execute Action dialog action
PIH_TABLE Importing Table information and change
operations
PIH_ITEM Importing Item information and change
operations
PES_RESULT Exporting Action result
PET_RETURN Exporting Error messages for exceptions


PE_ERROR_TYPE Exporting Exception type
Parameters PIS_ACTION_EXECUTE and PES_RESULT are explained in detail for

method EXECUTE_ACTION. For more information, see “EXECUTE_ACTION”
on page 363. Parameter PIH_TABLE provides all information about the table and its
items. With the methods ADD_ROW, DELETE_ROW and SET_ROW_POSITIONS, the table
can be changed. Parameter PIH_ITEM provides all information about the item and
allows changes to this item. Parameter PES_RESULT defines the overall result of the
action.
For information about the structure of PES_RESULT, see “EXECUTE_ACTION”

on page 363.
9.9.4.16 UPDATE_DIALOG
This method is called when a value changes in fields for which the UPDATE_ON_
VALUE_CHANGE flag is set.
The parameters are almost the same as in the EXECUTE_ACTION method, plus the
parameter in the following table. Additionally, EXECUTE_ACTION has the PIT_BULK_
RESULTS parameter. For more information, see “EXECUTE_ACTION” on page 363.

objects.
a single action.

9.9.5 Communication flow of an Action dialog box with bulk

actions

Figure 9-9: Communication flow of an Action dialog box with bulk actions

1. Request PrepareActionDialogForBulk (only for bulk actions)

When the user runs a bulk action that is linked with an Action dialog box, the
Fiori Task App sends the request PrepareActionDialogForBulk. In the
backend system, the VIM Foundation tries to lock the selected objects and start a
DataCollection for the action. It returns to the Fiori app which objects can be
processed and additional information if an object cannot be processed. The Fiori
Task App displays an overview of the objects and the additional information in a
dialog box.
Solutions can influence the locking of work objects in general with
implementations for BAdI /OTX/PF00_LOCK. You can implement bulk action
specific logics to allow/disallow the processing of single objects in method /OTX/
PF62_IF_ACTION_DIALOG~CHANGE_BULK_OBJECTS. You can also set the object
titles using this method. In full screen mode, the Fiori app is not able to calculate
these object titles automatically. Therefore they must be set by the solutions. At
the start of the DataCollection, the solutions can implement additional logics
in the methods /OTX/PF00_IF_DATA_COLLECTION~CREATE_COLLECTION and /
OTX/PF62_IF_DATA_COLLECTION~SET_ADDITIONAL_INFORMATION of the used
class.
Note: In case of a single action, the object key of the current object is
defined in all methods of interface /OTX/PF62_IF_ACTION_DIALOG by the
import parameters PIT_KEYS, PI_LOGSYS, and PI_WOBJ_TYPE. The
parameters PIT_KEYS and PI_LOGSYS cannot be set in case of bulk actions.
Therefore, the methods of interface /OTX/PF62_IF_ACTION_DIALOG have
now the additional parameter PIT_ACTION_OBJECT which contains
instances of the processed objects. In method EXECUTE_ACTION, this
parameter is replaced by parameter PIT_BULK_RESULTS.
2. Request SetLock (only for single actions)
When the user runs an action, the Fiori Task App sends a SetLock request for
the current object. In the backend system, the VIM Foundation tries to lock this
object.
Solutions can use BAdI /OTX/PF00_LOCK to influence the locking for a work
object.
3. Request StartDataCollection (only for single actions)
After a successful lock, the Fiori Task App sends the request
StartDataCollection. The VIM Foundation in the backend creates the data
collection. At creation of the DataCollection, the methods /OTX/PF00_IF_
DATA_COLLECTION~CREATE_COLLECTION and /OTX/PF62_IF_DATA_
COLLECTION~SET_ADDITIONAL_INFORMATION are called. These methods belong
to the data collection class of the current work object type. Therefore, data
necessary for the Action dialog box can be collected.
4. Requests Perspective and ActionDialog
In this step, the Fiori Task App requests the perspective for the ActionDialog
and general information for the ActionDialog window. The perspective
information is returned as it has been defined in the PerspectiveManager. If

DataBindings are used, the values for the DataBinding are read now. For the
ActionDialog information, method /OTX/PF62_IF_ACTION_DIALOG~GET_
ACTION_DIALOG is called. This method must be implemented by the solutions.
In case of a single action processing, this is the first time when the action ID is
known in the backend system. Depending on the action ID, add data to the data
collection the first time this method is called.
5. Requests for ActionDialog UI elements (ActionDlg* requests)
The Fiori Task App requests the data for all views of the perspective
customizing of the Action dialog box. These data must be set in the /OTX/PF62_
IF_ACTION_DIALOG~GET* methods. Each method gets an instance of the data
collection class as an import parameter. Therefore, the data of the data collection
can easily be accessed.
6. TransferActionDlg* and UpdateActionDialog requests
After changing an input field where the UPDATE_ON_VALUE_CHANGE flag is set,
the Fiori Task App transfers the current dialog values to the backend and
requests information how the dialog should be updated. The VIM Foundation in
the backend collects the current values of the dialog and calls method /OTX/
PF62_IF_ACTION_DIALOG~UPDATE_DIALOG. This method contains the view ID of
the field that triggered the update and contains the current data of the Action
dialog box. Therefore, the data in the data collection class can be updated and
checks can be performed.
After each update, the GET_* methods for the views that require an update
(UPDATE_REQUIRED flag) are called. Additionally, the Action dialog box is
updated.
Request flows 6 and 5 are repeated each time the user does a change that triggers
an update.
7. TransferActionDlg* and ExecuteActionDialog requests
When the user clicks the action button in the Action dialog box, the Fiori Task
App transfers the current information to the backend and requests the execution
of the action. In the backend, the VIM Foundation collects the transferred
information and calls method /OTX/PF62_IF_ACTION_DIALOG~EXECUTE_
ACTION for the execution of the action. The parameters of this method contain all
data available in the Action dialog box. The result of the execution is set in
parameter PES_RESULT, field STATUS and MSG. For details on these parameters,
see “EXECUTE_ACTION” on page 363.
For the bulk actions, the status of each object must be set in parameter PIT_
BULK_RESULTS.
In case of a single action, the Fiori Task App either displays the message and
update the object as requested or returns to the dialog. In case of a bulk action, it
will only do this for the statuses GEN_ERROR and DLG_ERROR.
8. Request FinishActionDialogForBulk (only bulk action)
When the ExecuteActionDialog did not return an error status, the Fiori Task
App sends the FinishActionDialogForBulk request to retrieve the results for
the objects from the backend. At this call, the VIM Foundation returns the results

it got in the previous call of method /OTX/PF62_IF_ACTION_DIALOG~EXECUTE_

ACTION. It also removes the DataCollections (method /OTX/PF00_IF_DATA_
COLLECTION~REMOVE_COLLECTION) and removes the locks for all objects (BAdI /
OTX/PF00_LOCK).
9. Request RemoveDataCollection (only for single actions)
When the action has been executed (successfully or with error), the Fiori Task
App sends request RemoveDataCollection to remove the DATACollection of
the ActionDialog. The VIM Foundation calls method /OTX/PF00_IF_DATA_
COLLECTION~REMOVE_COLLECTION of the data collection class. The
implementation of this method should delete all collected data.
10. Request RemoveLock (only for single actions)
Finally, the Fiori Task App requests the removal of the lock. The VIM
Foundation removes the lock in the backend system (BAdI /OTX/PF00_LOCK).
The /OTX/PF63_CL_DACO_WOBJ class is an example data collection, which handles

messages occurring during an Action dialog box. The Action dialog box logic for
these messages is implemented in the /OTX/PF63_CL_ACTION_DIALOG class. /OTX/
PF63_CL_ACTION_DIALOG handles the logic for the action messages views PF63_AM_
ERROR (error messages), PF63_AM_WARN (warning messages) and PF63_AM_INFO
(information messages).
Messages for these views can be set using the /OTX/PF63_UPDATE_MESSAGES

method. Additionally, this class allows you to check required fields and to set value
state information for input fields. Field information can be set by calling the /OTX/
PF63_SET_FIELD_INFO method.
To check the required fields, call the /OTX/PF63_CHECK_FIELDS or /OTX/PF63_

CHECK_REQ_FIELDS methods in the /OTX/PF62_IF_ACTION_DIALOG~EXECUTE_
ACTION and /OTX/PF62_IF_ACTION_DIALOG~UPDATE_DIALOG methods. If you want
to use the features of the /OTX/PF63_CL_DACO_WOBJ class, you have to inherit your
action dialog class from the /OTX/PF63_CL_ACTION_DIALOG class and the data
collection class from class /OTX/PF63_CL_DACO_WOBJ. In the perspective
customizing, maintain the views as needed.
9.10 Enabling inplace document viewing for iPhone

and iPad
By default, the Fiori Task App uses the native iOS Document Viewer. It is opened in
a new browser tab. However, this approach implies limitations regarding certain
integration scenarios.
The inplace document viewing mode allows you to overcome these limitations but it
requires the installation of Brava! View. For installation instructions, see OpenText
Brava! View for SAP Solutions - Installation and Configuration Guide (BRWEBV-IGD).
To enable the inplace document viewing:
1. After installing Brava! View, run the /n/OTX/PF00_IMG transaction.

9.11. Integrating UI5 widgets for Extended ECM or Document Access
Settings > Basic Settings.
3. Enable the Web Viewer setting for Device Types Smart phone and Tablet.
4. Open the Perspective Editor from the Launchpad by clicking the Perspectives
Maintenance tile.
5. Choose the perspective you want to change and open it in the Perspective
Editor.
6. Drag the [ot_bc_app_namespace].view.item.AttachmentsInplace view

into the same Aggregation container as the [ot_bc_app_namespace].view.
item.AttachmentsNewTab view.
7. Remember the ID of the [ot_bc_app_namespace].view.item.

AttachmentsNewTab view if it is not generic.
8. Delete the [ot_bc_app_namespace].view.item.AttachmentsNewTab view

from the perspective (Delete function in the context menu).
9. Rename the ID of the [ot_bc_app_namespace].view.item.

AttachmentsInplace view with the ID of the [ot_bc_app_namespace].view.
item.AttachmentsNewTab view.
10. Save the perspective.
9.11 Integrating UI5 widgets for Extended ECM or

Document Access
You can integrate UI5 widgets for Extended ECM for SAP Solutions (xECM) or for
Archiving and Document Access for SAP Solutions (ADA). To integrate UI5 widgets
for Extended ECM for SAP Solutions or for DocuLink, you can use the perspective
mechanism like for any other custom view. For more information, see “Editing
To integrate Extended ECM or DocuLink UI5 widgets:
1. Open the Perspective Editor from the Launchpad by clicking the Perspectives
Maintenance tile.
2. To copy the wanted perspective, use the Create function of the Perspective
Editor.
3. Add the views in the following table to the Perspective Editor. Therefore, use
the context menu of folder views.

4. Add the following views for Extended ECM.
BSP Application BSP View Web icon

/OTX/RMF_BWS4BC_02 otx.ecmlink.bws4otbcwui02. customer
view.item.BusinessWorkSpace:
This view renders the business
workspace by opening the integration
widget from OpenText™ Content Server.
/OTX/ALF_DOCS4BC_02 otx.alplus.doc4otbcwui02.view. customer-
item.BusinessDocuments: order-entry
This view renders the list of business
documents. A click on a document opens
it in an overlay over the existing web
page.
/OTX/ALF_DOCS4BC_02 otx.alplus.doc4otbcwui02.view. customer-
item.BusinessDocumentsSplit order-entry
otx.alplus.doc4otbcwui02.view.
item.DocumentDisplay
Use these views together for a split. The
view BusinessDocumentsSplit
renders the list of business documents. A
click on a document opens the document
display in the view DocumentDisplay.
5. Drag the views to the perspective that you want to change.
Workplace > Nodes.
7. Double-click the node for which you want to add the UI5 widgets. Maintain the
ID of the copied perspective in the Perspective ID for an item column.
9. Maintain the related business object. For more information, see “Defining a
related business object for a work object type” on page 300.

9.12. Interfaces and exits
9.12 Interfaces and exits

This section describes interfaces and exits that are relevant for the Web Services.
Note: The parameter naming in VIM follows the following rules:
1st Character
P fix, indicates a parameter.
2nd character
I (Importing) or C (Changing) or E (Exporting).
3rd character
<empty> (variable) or S (structure) or T (table).
9.12.1 Interface /OTX/PF62_IF_NODE

Customizing user exits for nodes in the Workplace requires a class with
implementation of the /OTX/PF62_IF_NODE interface.
This interface has the following methods:
• “CHANGE_NODE” on page 373

• “CHANGE_NODE_SEARCH_FIELDS” on page 374
• “CHANGE_NODE_SORT_FIELDS” on page 375
• “CHANGE_NODE_FILTER_FIELDS” on page 375
• “CHANGE_NODE_FILTER_VALUES” on page 376
• “CHANGE_NODE_LIST” on page 377
• “CHANGE_NODE_LIST_COLUMNS” on page 378
• “CHANGE_NODE_ACTIONS” on page 379
9.12.1.1 CHANGE_NODE
This method is called when the nodes are loaded and allows to change the state of
the node.
Tip: The implementing class of the interface /OTX/PF62_IF_NODE has to be

maintained in the field NODE_EXIT of the node customization. For more
information, see “Enabling nodes for Web Services” on page 311.



• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_WORKPLACE Importing Importing Workplace ID

PE_BUS_ERROR_HANDLING Exporting Error handling
PCS_NODE_SETTINGS Changing Node settings that can be changed. The
field VALUE_STATE allows to change the
values state of a node.
9.12.1.2 CHANGE_NODE_SEARCH_FIELDS
This method allows changing the customized field for the object search at runtime.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_SOFT_STATE Importing Soft state active?

PCT_SEARCH_NAMES Changing Fields available for search
Structure of parameter PCT_SEARCH_NAMES:

ID Field ID
TITLE Displayed title
POS Position

9.12.1.3 CHANGE_NODE_SORT_FIELDS
This method allows changing the sort fields available for this node at runtime.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PCT_SORT_NAMES Changing Fields available for sorting
Structure of parameter PCT_SORT_NAMES:

ID Field ID
POS Position
9.12.1.4 CHANGE_NODE_FILTER_FIELDS
This method allows changing the filter fields available for this node at runtime.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI



PCT_FILTER_NAMES Changing Fields available for filtering
Structure of parameter PCT_FILTER_NAMES:

ID Field ID
COUNT Number of entries found for this criteria
SEARCHABLE Values of this filter criteria are searchable
CASE_SENSITIVE Case sensitive search for values of this filter criteria
POS Position
NO_MULTI_SELECT Limits the filter selection to one value.
9.12.1.5 CHANGE_NODE_FILTER_VALUES
This method allows changing the filter values available for the current filter at
runtime.

PI_FILTER_NAME Importing Filter name
PCT_FILTER_VALUES Changing Values available as filter criteria
Structure of parameter PCT_FILTER_VALUES:

ID Filter ID
VALUE Value ID
TITLE Value title
COUNT Number of objects available for this filter value

9.12.1.6 CHANGE_NODE_LIST
This method allows changing the displayed data of a full screen list at runtime.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_SELECT_MODE Importing Required data selection mode of the

request. Possible values:
• COUNT: Only count entries,
return no data
• DATA: Only return data
PIT_NODE_LIST_COLUMNS Importing Columns of full screen list
PCT_NODE_LIST_ROW Changing Node list data
Structure of parameter PCT_NODE_LIST_ROW:

ROW_ID Row number
TASK_TITLE Title of task (displayed in detail mode)
TITLE Obsolete
Value 01-10 Value of the cell
ITEM_PERSPECTIVE_ID Perspective that is used to display the details view of the
row

9.12.1.7 CHANGE_NODE_LIST_COLUMNS
This method allows changing the columns of a full screen list at runtime.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PCT_NODE_LIST_COLUMNS Changing Columns settings
Structure of parameter PCT_NODE_LIST_COLUMNS:

COLUMN_ID Column ID
TYPE Type (ABAP data type)
DESCRIPTION Column description
DISPLAY_TYPE Display type (TEXT | ICON | CHECKBOX )
NAVIGATION_TYPE Navigation type. Possible values:
• POPUP: Show popup
• INPLACE: Show inplace
• SEMANTIC: Navigate to semantic object
• EDIT: Navigate to edit view
• ACTION_DLG: Call action dialog
• NONE: No link
ACTION_ID Action ID - only used with navigation type

ACTION_DLG
VISIBILITY_PHONE Column is visible at phone devices.
VISIBILITY_TABLET Column is visible at tablet devices.
VISIBILITY_DESKTOP Column is visible at desktops.


VISIBILITY_COMBI Column is visible at combi devices, a combination of
desktop and tablet.
For the VISIBILITY_* fields, the following values are
possible:
• DEFAULT: Display as normal column
• NONE: Do not display
• POPIN: Display as Popin
FIELDNAME Fieldname
COLUMN_WIDTH Width of column
EXPORT_ENABLED Export function
9.12.1.8 CHANGE_NODE_ACTIONS
This method allows changing general actions available for a node in full screen list
mode at runtime.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PE_ERROR_HANDLING Exporting Error handling
PCT_NODE_ACTIONS Changing Node actions
Structure of PCT_NODE_ACTIONS:

NODE_ID Node ID
ACTION_ID Action ID
DEVICE Device
PERSPECTIVE_ID Perspective ID (used for Action dialog)
TEXT Button text


BUTTON_TYPE Button style:
• ACCEPT: Accept type (blue button)
• DEFAULT: Default type (no special styling)
• EMPHASIZED: Emphasized type
• REJECT: Reject type (red button)
• TRANSPARNT: Transparent type
• UNSTYLED: Unstyled type (no styling)
ICON Icon displayed on button

TRANSPORT_REQMNT Defines the kind of transport request for the action.
Possible values:
• NONE: No transport required (default)
• CUSTOM: Customizing request
• WORKBENCH: Workbench request
9.12.2 Web handler

The web handler defines the data that is transferred by the web service for a specific
work object type. The web handler implements the /OTX/PF62_IF_ITEM_HANDLER
interface.
This interface has the following methods:
• “GET_ACTIONS” on page 381

• “CHANGE_ACTIONS” on page 381
• “GET_ACTION_REASONS” on page 383
• “GET_ACTION_VALIDAT_MSG” on page 384
• “CHANGE_ACTION_VALIDATION” on page 385
• “GET_ACTION_AGENTS” on page 387
• “EXECUTE_ACTION” on page 388
• “HANDLE_ACTIONS_BULK” on page 388
• “HANDLE_UPDATES_BULK” on page 389
• “CHECK_FIELDS” on page 390
• “CHECK_LINE_ITEM_FIELDS” on page 391
• “GET_ITEMS” on page 391
• “GET_DOCUMENTS” on page 393
• “GET_DOCUMENT_ATTRIBUTES” on page 394
• “DELETE_DOCUMENT” on page 395

• “CHANGE_ITEM_STRUC” on page 396

• “ON_VALUE_UPDATE_ITEM” on page 397
• “CHANGE_HEADER_DETAILS” on page 398
• “ON_VALUE_UPDATE_HEADER_DETAIL” on page 400
• “GET_ITEM_STRUC” on page 401
• “GET_ITEM_LINKS” on page 402
• “CHANGE_OBJECT” on page 403
• “CHANGE_OBJECT_HEADER” on page 405
• “CHANGE_OBJECT_FUNCTIONS” on page 406
• “GET_TIMELINES” on page 406
• “GET_EXCEPTIONS” on page 408
• “CHANGE_ITEM_LIST_TITLE” on page 409
• “CHANGE_RELATED_BUS_OBJECT” on page 410
• “CHANGE_NODELIST_NAV_LINK” on page 411
• “RESOLVE_URL_PARAMS” on page 412
• “GET_IMAGE_CTRL_PAGES” on page 412
• “GET_IMAGE_CTRL_FULLTEXT” on page 414
9.12.2.1 GET_ACTIONS
This method is deprecated in Business Center 10.0 SP1 and later. It is replaced by the
CHANGE_ACTIONS method. For more information, see “CHANGE_ACTIONS”
on page 381.
9.12.2.2 CHANGE_ACTIONS
This method changes the available actions for the current item. In Business Center
10.0 SP1 and later, it replaces the GET_ACTIONS method.

PIT_KEYS Importing Contains key fields of the current work
object.
PI_WOBJ_TYPE Importing Work object type.
PI_WOBJ_CHANGED_AT Importing Timestamp of the last change made to
the item.
PI_LOGSYS Importing Logical system. Is only filled if one of
the key fields is marked as logical
system field.


PI_ACTION_ID Importing Required action ID. Initial if all actions
for the item are required.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PCT_ACTIONS Changing Available actions.

PCT_RETURN Changing Error messages.
PC_ERROR_TYPE Changing Error type. Available types are:
1 - Business error
2 - Technical error
In case of an error, an exception will be
raised with the error message in
PCT_RETURN.
PC_BUS_ERROR_HANDLING Changing Allows to define the UI behavior in case
a business error occurs (pe_error_type =
1). Possible values:
1 - No update
2 - Complete refresh
3 - Item refresh
4 - Remove item
Structure of parameter PCT_ACTIONS:

ACTION_ORDER Order of actions.
ACTION_ID Action ID.
ACTION_CLASS Action class for action dialog (action type confirm).
Action class has to implement interface /OTX/
PF62_IF_ACTION_DIALOG
ICON SAP UI5 Icon. Will be displayed at the button.
TEXT Action text. Will be displayed at the button.
BUTTON_TYPE SAP UI5 button type. The following types are available:
• ACCEPT: Accept type (blue button)
• DEFAULT: Default type
• EMPHASIZED: Emphasized type
• REJECT: Reject style (red button)
• TRANSPARNT: Transparent style
• UNSTYLED: Without a style


ACTION_TYPE Action type, which defines the behavior of the action.
The following types are available:
• EDIT: Perspective defined in field PERSPECTIVE_ID
is called. Use this type to change from display to edit
mode.
• CONFIRM: The Confirm dialog box (action
validation) opens.
• SAVE: Save is triggered.
• CHECK: Check is triggered.
• SAVE_CONFM: Save with Confirmation dialog box.
• ACTION: Action dialog box.
• SAVE_ACTN: Save with Action dialog box.
• SEMANTIC: Semantic object navigation.
• DETAIL_IN: Opens new Detail screen inplace.
• DETAIL_FUL: Opens new details screen - full screen
mode.
BULK_ACTION Action can be used as a bulk action.
PERSPECTIVE_ID Perspective that is called at action type EDIT.
VIEW_ID Perspective view ID. Can be used to overwrite the
customized value at runtime.
NAV_PARAMETER Link parameter field for action type Semantic object
navigation. Can be used to overwrite the customized
value at runtime.
TRANSPORT_REQMNT Transport requirement. Possible values:
NONE - No transport required (default)
CUSTOM - Customizing request
WORKBENCH - Workbench request
9.12.2.3 GET_ACTION_REASONS
This method returns possible reasons that can be selected in the confirmation dialog
box before the execution of an action.

object.
PI_ACTION_ID Importing Action ID.
PI_LOGSYS Importing Logical system. Will only be populated
if one of the key fields is marked as
logical system field.
PI_REASON_ID Importing Reason ID.


the object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PET_ACTION_REASONS Exporting Possible reasons.

PET_RETURN Exporting Error messages.
PE_ERROR_TYPE Exporting Error type. Available types are:
1 - Business error
2 - Technical error
raised with the error message of
PET_RETURN.
PE_BUS_ERROR_HANDLING Exporting Allows you to define the UI behavior in
case a business error occurs
(pe_error_type = 1). Possible values:
1 - No update
3 - Item refresh
4 - Remove item
9.12.2.4 GET_ACTION_VALIDAT_MSG
This method returns messages that are either displayed in the validation screen or in
an extra dialog box.

object.
PI_LOGSYS Importing Logical system. Will only be filled if
one of the key fields is marked as
PIT_REASONS Importing Selected reasons.
PIT_AGENTS Importing Selected agents.
the object.


• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PET_ACTION_VALIDAT_MSG Exporting Messages.

1 - Business error
2 - Technical error
PET_RETURN.
PE_BUS_ERROR_HANDLING Exporting Allows you to define the UI behavior
in case a business error occurs
1 - No update
3 - Item refresh
4 - Remove item
9.12.2.5 CHANGE_ACTION_VALIDATION
This method defines the layout of the validation screen.

object.
PI_LOGSYS Importing Logical system. Will only be filled if one
of the key fields is marked as logical
system field.
the object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PCS_ACTION_VALIDATION Changing Layout of the validation screen.


1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Structure of PCS_ACTION_VALIDATION:

DIALOG_TYPE Type of the dialog box. Possible values:
• confirm - Confirmation dialog box is displayed.
• error - Error messages are displayed without
confirmation dialog box.
TITLE dialog box title.
TASK_DESC Description of the task in the confirmation dialog box.
COMMENT_DESC Initial text in the comment box.
COMMENT_MANDATORY Flag marking the comment as mandatory.
REASONS_ACTIVE Sets selection box for reasons active.
AGENTS_ACTIVE Sets selection box for agents active.
TITLE_REASONS Title of selection box for reasons.
AGENT_TITLE Title of selection box for agents.
REASON_OPTION Select option for reasons. Possible values:
• single - Only one reason can be selected.
• multiple - Multiple reasons can be selected.
AGENT_OPTION Select option for agents. Possible values:
• single - Only one agent can be selected.
• multiple - Multiple agents can be selected.

9.12.2.6 GET_ACTION_AGENTS
This method returns possible agents that can be selected in the confirmation dialog
box.

object.
system field.
PI_FIRST_NAME Importing First name.
PI_LAST_NAME Importing Last name.
the object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PET_ACTION_AGENTS Exporting Possible agents.

1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item

9.12.2.7 EXECUTE_ACTION
This method is deprecated in Business Center 10.0 SP1 and later. It is replaced by the
HANDLE_ACTIONS_BULK method. For more information, see
“HANDLE_ACTIONS_BULK” on page 388.
9.12.2.8 HANDLE_ACTIONS_BULK
This method executes actions for one or more items. In Business Center 10.0 SP1or
later, it replaces the EXECUTE_ACTION method.

PIT_ACTIONS_BULK Importing Actions to be executed.
1 - Business error
2 - Technical error
In case of an error, an exception will
be raised with the error message of
PET_RETURN.
PET_BULK_ACTION_RESULT Exporting Action results.
PE_BUS_ERROR_HANDLING Exporting Allows you to define the UI behavior
in case a business error occurs
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PIT_ACTIONS_BULK:

OP_NUMBER Operation number
KEYS Key fields for this item
ACTION_ID Action to be executed
COMMENT Entered comment
REASONS Selected reasons
AGENTS Selected agents
CHANGED_AT Timestamp of the last change made to the item.
TRANSPORT_REQUEST Selected transport request
Structure of parameter PET_BULK_ACTION_RESULT:


OP_NUMBER Operation number.
MSG Message text.
STATUS Action status:
• CONF_ERROR: Message is displayed as an error in the
confirmation dialog box. The user can change inputs in the
confirmation dialog box and execute the action again.
• GEN_ERROR: Message is displayed as error and confirmation
dialog box is closed.
• UPDATE: Object is updated and still selected. Message fades in.
• REMOVE: Object is removed from the master list and the next
object in the list is selected. Message fades in.
9.12.2.9 HANDLE_UPDATES_BULK
This method executes updates for header details and line items fields.

PIT_UPDATES_BULK Importing Contains update information.
1 - Business error
2 - Technical error
be raised with the error message of
PET_RETURN.
PE_RESULT Exporting Result of update:
• SUCCESS: Update successful.
• ERROR: Update error.
PE_MSG Exporting Message text.
PE_BUS_ERROR_HANDLING Exporting Allows to define the UI behavior in
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PIT_UPDATES_BULK:

OP_NUMBER Operation number.
WOBJ_TYPE Work object type.


ID Item ID.
KEYS Key fields for this item.
ITEM_ID Line item ID.
LOGSYS Logical system.
UPDATE_TYPE Update type. Possible values:
• HEAD: Header update
• ITEM: Line item update
FIELDS Field values. Table which contains field names and values.
CHANGED_AT Timestamp of the last change made to the item.
TRANSPORT_REQUEST Number of transport request used for this action
9.12.2.10 CHECK_FIELDS
This method checks values of header detail fields.

PIT_KEYS Importing Contains key fields of the current
work object.
the item.
PI_LOGSYS Importing Logical system. Is only filled if one of
the key fields is marked as a logical
system field.
PIT_FIELD_VALUES Importing Field values.
PET_MSG Returning Messages.
Structure of parameter PET_MSG:

FIELDNAME Name of the checked field
TYPE Message type:
• Error
• Warning
• Success
• None
MSG Message text.

9.12.2.11 CHECK_LINE_ITEM_FIELDS
This method checks values of line item fields.

object.
PI_WOBJ_CHANGED_AT Importing Timestamp of the last change made to the
item.
PI_LOGSYS Importing Logical system. Is only filled if one of the
key fields is marked as a logical system
field.
PI_ITEM_ID Importing ID of the line item.
PIT_FIELD_VALUES Importing Field values.
PET_MSG Returning Messages.
Structure of parameter PET_MSG:

FIELDNAME Name of the checked field
TYPE Message type:
• Error
• Warning
• Success
• None
MSG Message text
9.12.2.12 GET_ITEMS
This method returns items that should be displayed in the item list.

object.
PIT_ITEM_DETAILS Importing Customized columns with metadata
from structure.
system field.


the object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_ITEM_PERSPECTIVE_ID Importing Item perspective ID.

PET_DATA Exporting Item data.
1 - Business error
2 - Technical error
PET_RETURN.
PE_BUS_ERROR_HANDLING Exporting Allows to define the UI behavior in case
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PET_DATA:

ITEM_ID Item ID. This must be set by web handler
implementation.
VALUE_01 - VALUE_10 Values for columns 01 to 10.
EDITABLE Sets a list item as editable.
Note: The field values must be in external format. For transferring the field
values from internal to external format, you can use method /OTX/PF00_CL_
UTILITIES=>STRUCTURE_FIELD_VALUE_CONVERT. For more information, see “/
OTX/PF00_CL_UTILITIES=>STRUCTURE_FIELD_VALUE_CONVERT”
on page 469.

9.12.2.13 GET_DOCUMENTS
This method returns documents that are displayed with the function Documents.

object.
PI_USE_WEB_VIEWER Importing Web Viewer or Brava! View should be
used.
PI_DEVICE Importing Defines the device on which the Fiori
Task App is running. Possible values:
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_LOGSYS Importing Logical system. This is only populated

if one of the key fields is marked as a
the object.
PET_DOCUMENTS Exporting Document.
1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PET_DOCUMENTS:

ARCHIVE_ID Archive ID
ARCDOC_ID Document ID


MAIN_DOC Flag that marks the document as main document
OBJECTTEXT Document type
URI Document URL
DOC_CLASS Document class
LENGTH Document size in bytes
ARCHIVE_TIMESTAMP Archiving time stamp
ICON Icon
HAS_ATTRIBUTES Defines if a document has additional attributes. By
default no additional attributes are displayed.
DELETABLE Defines if a document can be deleted. By default the
Delete button is not visible.
9.12.2.14 GET_DOCUMENT_ATTRIBUTES
This method is called for one document when the user opens the panel for the
attributes.

object.
the object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PI_ARC_DOC_ID Importing Archive document ID.
PI_ARCHIVE_ID Importing Archive ID
PET_ATTRIBUTES Exporting Attributes that should be displayed.


1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PET_ATTRIBUTES:

ATTRIBUTE_NAME Unique ID of the attribute.
LABEL Label
VALUE Attribute value
VALUE_DESC Value description - displayed behind attribute value
9.12.2.15 DELETE_DOCUMENT
This method is called when the deletion of a document is triggered from view view.
item.Document. Parameters PI_ARC_DOC_ID and PI_ARCHIVE_ID define the
document that should be deleted. Deletion must be implemented in this method.

object.
PI_ARC_DOC_ID Importing Archive document ID.
1 - Business error
2 - Technical error
PET_RETURN.


1 - No update
3 - Item refresh
4 - Remove item
9.12.2.16 CHANGE_ITEM_STRUC
This method changes the item structure for the item list.

object.
the object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PCT_ITEM_STRUCTURE Changing Structure of the item list. Prefilled

according to customizing, can be
changed.
1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item

Structure of parameter PCT_ITEM_STRUCTURE:

COLUMN_ID Column ID.
FIELD_NAME Field name.
MOBILE_PRIO Marks column as priority column for mobile
devices.
TYPE Data type of column.
LENGTH Length of column.
DESCRIPTION Column label.
DECIMALS Number of decimal places.
IS_ICON Display column value as icon.
IS_UNIT Column is unit for value in previous column.
EDITABLE Column is editable.
REQUIRED Values in column must be maintained.
CHECKBOX Field is displayed as a check box.
HELP_ID ID for search help.
HELP_VARIANT Variant how search help is displayed.
REL_FIELDS Related fields for search help.
LINKTYPE Type of the link for semantic object
navigation.
UPDATE_ON_VALUE_CHANGED This field defines the following: At a change
of the value of the field, should method
ON_VALUE_UPDATE_ITEM of the item
handler be called to react on this value
change?
9.12.2.17 ON_VALUE_UPDATE_ITEM
This method is triggered if the value of a line item detail field is changed and the
Update on Change check box in the line item details is selected.

work object.


• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PI_COLUMN_ID Importing Column ID that has been changed.
PI_ITEM_ID Importing ID of the item that has been changed.
PCS_ITEM_VALUES Changing Current values displayed in the Fiori
Task App. Changed values are
displayed.
1 - Business error
2 - Technical error
be raised with the error message in
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
The parameter PCS_ITEM_VALUES contains the current field values of the item. It has
the following structure.

VALUE 01 - 10 Value displayed in column 01 - 10
9.12.2.18 CHANGE_HEADER_DETAILS
This method changes data for header details.

object.


• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_VIEW_ID Importing Perspective View ID of the Header

Details View
PIS_DISPLAY_ATTRIBUTES Importing Attributes of the work object. Uses
Display structure of work object
type.
the object.
PCT_HEADER_DETAILS Changing Header details. Prefilled with
customized fields.
1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PCT_HEADER_DETAILS:

POS Position (1 – 20).
TYPE Data type.
LENGTH Maximum length of the field value.
DESCRIPTION Label.
VALUE Field value.
FIELDNAME Technical field name.
DECIMALS Number of decimal places.


EDITABLE Column is editable.
REQUIRED Values in column must be maintained.
CHECKBOX Field is displayed as a check box.
HELP_ID ID for search help.
HELP_VARIANT Variant how search help is displayed.
REL_FIELDS Related fields for search help.
HAS_VALUE_DESC Display value description.
UPD_ON_VALUE_CHG Update is triggered when this field value changes.
VALUE_DESCRIPTION Description behind field for the current value.
LINKTYPE Type of the link for semantic object navigation.
LINK_PARAMETER JSON with the link parameters for semantic object
navigation.
9.12.2.19 ON_VALUE_UPDATE_HEADER_DETAIL
The update is triggered for fields in header details that were changed and that are
flagged for an update (field UPD_ON_VALUE_CHG).

object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PI_UPDATED_FIELD Importing Field which has been updated.
PI_VIEW_ID Importing View ID for which the update has to be
performed.
PCT_VALUES Changing The field values when the update was
made. Values and value description
changes are displayed in the UI.


1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Parameter PCT_VALUES contains the current field values. It has the following
structure.

FIELDNAME Field name.
VALUE Field value.
VALUE_DESCRIPTION Description text behind field value. The current text is
not imported, it must be changed if the field value is
changed.
UPDATE_REQUIRED Values of the fields VALUE and VALUE_DESCRIPTION
are only set in the Fiori Task App if this flag is marked.
9.12.2.20 GET_ITEM_STRUC
This method returns the structure for the item list.

object.
the object.


• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PE_ITEM_STRUCTURE Exporting Technical name of the item structure.

1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
9.12.2.21 GET_ITEM_LINKS
This method allows the definition of the link parameter of single line items in the
context of semantic object navigation. It will be called when the user clicks a link in
one of the line items.

object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_ITEM_ID Importing Item ID.

PI_COLUMN_ID Importing Column for which the link is required.


PET_ITEM_LINK Exporting Link parameter for item.
1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PET_ITEM_LINK:

COLUMN_ID Column ID
LINK_PARAMETER Link Parameter
9.12.2.22 CHANGE_OBJECT
This method offers the possibility to change the object list.

PIS_DISPLAY_ATTRIBUTES Importing Work object data. Uses the structure
Display structure as defined in the
work object type.
PIS_WOBJ_TYPE Importing Work object type customizing.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

the object.


object.
PCS_OBJECT Changing Work object.
1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PCS_OBJECT:

NODE_ID Node ID. This is populated automatically by the
framework.
INTRO Fields as described in “Configuring the data binding for
the master list” on page 315.
TASK_TITLE
TITLE
NUMBER
NUMBERSTATE
NUMBERUNIT
MARKFLAGGED
MARKFAVORITE
ATTRIBUTES0
ATTRIBUTES1
FIRSTSTATUS
SECONDSTATUS
ITEM_PERSPECTIVE_ID Item perspective ID.
HAS_A_BULK_ACTION Object has at least one bulk action.
ICON Icon.

Note: To remove the object from the object list, clear the structure PCS_OBJECT.
9.12.2.23 CHANGE_OBJECT_HEADER
This method offers the possibility to change the object header.

PIS_DISPLAY_ATTRIBUTES Importing Work object data. Uses the structure
Display structure as defined in
the work object type.
PIS_WOBJ_TYPE Importing Work object type customizing.
the object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

work object.
PCS_OBJECT Changing Object header.
1 - Business error
2 - Technical error
be raised with the error message in
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PCS_OBJECT:


ICON UI5 icon
MARKFAVORITE Show favorite flag
MARKFLAGGED Mark as flagged
TASK_TITLE Task title
TITLE Title
NUMBER Number field
NUMBERUNIT Unit of number
NUMBERSTATE State of number:
• Error
• Warning
• Success
• None
ATTRIBUTES0 Attributes
ATTRIBUTES1 Attributes
INTRO Introduction text
FIRSTSTATUS First status
SECONDSTATUS Second status
LINKTYPE Type of the link for semantic object navigation
LINK_PARAMETER JSON with the link parameters for semantic object
navigation
9.12.2.24 CHANGE_OBJECT_FUNCTIONS
This method is deprecated in Business Center 10.0 SP1 and later. The functionality is
now part of the perspectives concept. For more information, see “Editing
9.12.2.25 GET_TIMELINES
This method returns history entries and comments.

object.


the object.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_SKIP Importing Number of entries that have to be

skipped
PI_MAX_HITS Importing Maximum number of entries that
should be returned
PI_MODE Importing Selection mode:
• COUNT - Only count entries, return
no data
• DATA - Only return data
PET_TIMELINES Exporting Timeline entries
1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
PE_ENTRIES Exporting Number of entries.
If PI_MODE = COUNT, only
PE_ENTRIES needs to be set.
PET_TIMELINES can be empty.
If PI_MODE = DATA, PE_ENTRIES can
stay empty. Only PET_TIMELINES
needs to be set.
Structure of parameter PET_TIMELINES:


HIST_KEY Key of history entry.
CMNT_KEY Key of comment.
ACTIONICON Icon symbolizing the action of this entry.
USERNAME User name.
USERID User ID.
USERDETAILSAVAILABLE User details are available.
ACTIONTITLE Text for the action.
TIMESTAMP Time stamp.
COMMENT Comment text.
STEP Step description.
MSG_AVAILABLE Further messages are available.
9.12.2.26 GET_EXCEPTIONS
This method returns error messages that are displayed as detail for an object header
field.
This method is deprecated in Business Center 16.3.2 and later. Future

implementations should only implement CHECK_SAVE_DATA and return the
exceptions in the implementation of this method. For more information, see
“CHECK_SAVE_DATA” on page 422.
Existing implementations use CHECK_SAVE_DATA to check and save the data, but
return the exceptions via method GET_EXCEPTIONS. This is still working due to
downward compatibility.

object.
the item.
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI


PET_EXCEPTIONS Exporting Exceptions.
1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PET_EXCEPTIONS:

EXCEPTION_ID Exception ID
TYPE Exception type. Values:
• S - Success
• I - Information
• W - Warning
• E - Error
COUNTER Message counter

EXCEPTION_DESC Short description
MESSAGE Message text
9.12.2.27 CHANGE_ITEM_LIST_TITLE
This method changes the title of the item list.

object.
PI_LOGSYS Importing Logical system. This is only populated if
one of the key fields is marked as a
the item.


• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PC_ITEM_LIST_TITLE Changing Item list title.

1 - Business error
2 - Technical error
PET_RETURN.
1 - No update
3 - Item refresh
4 - Remove item
9.12.2.28 CHANGE_RELATED_BUS_OBJECT
This method allows you to change the customizing for the related business object at
runtime. For more information, see “Defining a related business object for a work
object type” on page 300.

object.
1 - Business error
2 - Technical error
PET_RETURN.


1 - No update
3 - Item refresh
4 - Remove item
PCS_RELATED_BUS_OBJECT Changing Related business object.
Structure of parameter PCS_RELATED_BUS_OBJECT:

OBJTYPE Object type
OBJID Object ID
9.12.2.29 CHANGE_NODELIST_NAV_LINK
This method allows to change the navigation links in the node list at runtime. The
method is called before the link is executed.

PIT_KEYS Importing Work object key values
PI_COLUMN_ID Importing Column ID
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PET_RETURN Exporting Messages for exceptions

PE_ERROR_TYPE Exporting Exception type
PC_NAV_PARAMETER Changing Navigation parameter
PC_TRANSPORT_REQMNT Changing Transport type:
• No transport required
(default)

9.12.2.30 RESOLVE_URL_PARAMS
This method is called when:
• the Fiori Task App is called with parameter resolveParamsAtBackend=true

or
• the URL contains at least one parameter that is unknown to the Fiori Task App.
The PIT_URL_PARAMETERS parameter contains all parameters of the URL.
This method is able to calculate the key values for the work object type with these
values and returns them in the PRT_KEYS parameter. All key values must be set.
When implemented, the Fiori Task App only selects this work object.

PIT_URL_PARAMETERS Importing Parameters (includes all unresolved
parameters).
PRT_KEYS Returning Key information for web ID calculation
(all key fields of work object type must
be set)
9.12.2.31 GET_IMAGE_CTRL_PAGES
This method returns the images and thumbnails for each page of the document that
should be displayed in the Image Control.

PIT_KEYS Importing Contains key fields of the
current work object.
PI_WOBJ_CHANGED_AT Importing Timestamp of the last change
made to the object.
PI_LOGSYS Importing Logical system. This is only
populated if one of the key
fields is marked as a logical
system field.


PI_DEVICE Importing Defines the device on which
the Fiori Task App is
running. Possible values:
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PI_ARC_DOC_ID Importing Document ID
PET_PAGES Exporting Pages for ImageControl.
PE_ERROR_TYPE Exporting Error type.
Available types are:
1 - Business error
2 - Technical error
In case of an error, an
exception is raised with the
error message of PET_
RETURN.
PE_BUS_ERROR_HANDLIN Exporting Allows to define the UI
G behavior in case a business
error occurs (pe_error_
type = 1).
Possible values:
• 1 - No update
• 2 - Complete refresh
• 3 - Item refresh
• 4 - Remove item
Line structure of parameter PET_PAGES:

PAGE_NUMBER Page number
PAGE_IMAGE Main image of page (byte format)
PAGE_THUMBNAIL Image of page used for thumbnail ( byte format)
CTYPE_IMAGE Content type/mime type of image


CTYPE_THUMBNAIL Content type/mime type of thumbnail
9.12.2.32 GET_IMAGE_CTRL_FULLTEXT

PIT_KEYS Importing Contains key fields of the current work object.
PI_WOBJ_CHANGED_AT Importing Timestamp of the last change made to the object.
PI_LOGSYS Importing Logical system. This is only populated if one of the key fields is m
PI_DEVICE Importing Defines the device on which the Fiori Task App is running. Possi
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PI_ARC_DOC_ID Importing Document ID
PET_FULLTEXT Exporting Pages for ImageControl
PE_ERROR_TYPE Exporting Error type.
Available types are:
1 - Business error
2 - Technical error
In case of an error, an exception will be raised with the error mes

PE_BUS_ERROR_HANDLING Exporting Allows to define the UI behavior in case a business error occurs (
Possible values:
1 - No update
3 - Item refresh
4 - Remove item
Line structure of parameter PET_PAGES:


PAGE_NUMBER Page number
PAGE_FULLTEXT Full text used by ImageControl
9.12.3 Interface /OTX/PF62_IF_PERSPECTIVE_CLASS

In general, this implementation allows the change of data in views of the perspective
at runtime. OpenText recommends that you derive the class from /OTX/PF62_CL_
PERSPECTIVE_CLASS. In this interface, the management of instances is already
implemented.
This section comprises the methods of the /OTX/PF62_CL_PERSPECTIVE_CLASS

interfaces.
Table 9-2: Attributes of /OTX/PF62_IF_PERSPECTIVE_CLASS
Attribute Description
M_PLTT Perspective life time token for the current
perspective
MH_PLTT_DATA_COLL Data collection of the perspective life time
token. For more information, see
“Maintaining Data Collections” on page 301.
MH_PERSPECTIVE_INFO Access to general information about the
perspective.
9.12.3.1 SET_ROOT_OBJECT_KEYS
This method is called at the creation of the perspective class instance and gives the
instance key information about the root object of the perspective. This method is
implemented in class /OTX/PF62_CL_PERSPECTIVE_CLASS and does not need to be
changed.

PIT_ROOT_KEYS Importing Keys of root work object
PI_ROOT_LOGSYS Importing Logical system of the root work
object
PI_ROOT_CHANGED_AT Importing Last changed time stamp of the
root work object
PIH_ROOT_WOBJ_TYPE Importing Work object type of the root work
object

9.12.3.2 GET_INSTANCE (static method)

This method returns the class instance.

PI_CLASSNAME Importing Name of perspective class
PIH_ROOT_WOBJ_TYPE Importing Work object type
PIT_ROOT_WOBJ_KEYS Importing Keys
PI_ROOT_WOBJ_LOGSYS Importing Logical system
PI_ROOT_WOBJ_CHANGED_AT Importing Last changed timestamp
PI_PLTT Importing Perspective Life Time Token
PRH_INSTANCE Returning Instance of perspective class
9.12.3.3 CHANGE_CUSTOMIZING
This method allows changing the customizing settings for the attribute list views
and table views of the current perspective at runtime.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PIT_ATTRIBUTE_LIST_CUST Importing Customizing instances for the

attribute list views
PIT_TABLES_CUSTOMIZING Importing Customizing instances for the table
views
PI_LOCKED Importing Flag to indicate that the object is
locked
PI_LOCKED_BY Importing SAP User name of the user who
locked the object
PIT_COMMENT_VIEW_CUST Importing Customizes the comment view
which is based on the standard
SAP feed list item (sap.m.
FeedListItem). The setting
defines the languages for
translation.
Line structure of PIT_ATTRIBUTE_LIST_CUST:


ROOT_WOBJ_TYPE Work object type of perspective
WOBJ_TYPE Work object type of current attribute list view
PERSPECTIVE_ID Perspective ID
VIEW_ID View ID
KEYS Keys of displayed object
CHANGED_AT Last changed timestamp of displayed object
ATTRIBUTE_LIST_CUSTOMIZING Instance of class /OTX/
PF62_CL_FC_AT_CUST_CHG. The following
methods allow changes to the customizing:
SET_SETTINGS
SET_RELATED_FIELDS
SET_ATTRIBUTES_CUST
LOCKED Marked if item is locked
LOCKED_BY User who locks the item
Line structure of PIT_TABLES_CUSTOMIZING:

WOBJ_TYPE Work object type of current table view
DEVICE Device type
ITEM_PERSPECTIVE_ID Perspective ID
VIEW_ID View ID
KEYS Keys of object for which associated items are
displayed
CHANGED_AT Last changed timestamp of root object
TABLE_CUSTOMIZING Instance of class /OTX/
PF62_CL_FC_LI_CST_CHNG. The following
methods allow changes to the customizing:
SET_HEADER_SETTING
SET_COLUMN_SETTING
SET_DEFAULT_ACTIONS
SET_CUSTOM_ACTIONS
Line structure of PIT_COMMENT_VIEW_CUST:



VIEW_ID View ID
displayed
COMMENT_SETTING_CHG Use method SET_SETTINGS to change languages
for translation
9.12.3.4 CHANGE_DATA
This method allows changing the data of the attribute list views and table views of
the current perspective at runtime.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PIT_CHANGE_ATTRIBUTE_LIST Importing Data instances for the attribute list

views
PIT_CHANGE_TABLES Importing Data instances for the table views
locked
locked the object
PIT_PROPERTY_BINDING Importing Data instances for control
properties with binding.
PIT_CHANGE_COMMENTS Importing Comment views.
Use the /OTX/PF62_IF_FC_CMT_

CHG~SET_COMMENTS method of
COMMENT_CHG (/OTX/PF62_CL_
FC_CMT_CHG) class to set the
comments that should be
displayed. For details, see “Line
structure of the PIT_COMMENTS
parameter of the /OTX/
PF62_IF_FC_CMT_CHG~SET_CO
MMENTS methods:”.
Line structure of PIT_CHANGE_ATTRIBUTE_LIST:


WOBJ Displayed object
VIEW_ID View ID
ATTRIBUTE_LIST Instance of class /OTX/
PF62_CL_FC_ATTRLST_CHG. The following
methods allow changes to the data:
SET_SETTINGS
SET_RELATED_FIELDS
SET_ATTRIBUTES
IS_LOCKED Indicator if item is locked
LOCKED_BY User who locks the item
Line structure of PIT_CHANGE_TABLES:

VIEW_ID View ID
displayed
ASSOCIATED_WOBJ_TYPE Work object type of items
TABLE Instance of class /OTX/
PF62_CL_FC_LI_CHANGE. The following
methods allow changes to the displayed items:
ADD_ROW
DELETE_ROW
SET_ROW_POSITIONS
Line structure of PIT_PROPERTY_BINDING:

CONTROL_ID ID of the control in the perspective
PROPERTY Property of the control that is bound


BINDING Instance of /OTX/PF62_CL_FC_PROP_BIND_
SET class. It has the method SET_VALUE to set a
new value. You can read the original bound
value and other information via GET methods.
Line structure of the PIT_COMMENTS parameter of the /OTX/PF62_IF_FC_CMT_

CHG~SET_COMMENTS methods:

COMMENT_ID ID of comment. The ID is used as key, and thus,
must be unique
SENDER Sender information
ICON Icon displayed in front of comment. If empty, the
initials are displayed
USERID Technical user ID. The ID us used for pop-ups
with user details
INITIALS Initials are displayed if no icon is maintained
INFO Info text. The text is displayed below comments
TIMESTAMP Timestamp. The timestamp is displayed below
comments.
TEXT Comment.
9.12.3.5 TRANSLATE_COMMENTS
This method is called when the user selects a language in the drop-down list of the
translation languages. The implementation of this methods returns the translations
of the comments.
Interface:

PIH_WOBJ_TYPE Importing Workobject type
PIT_KEYS Importing Key values
PI_PERSPECTIVE_ID Importing Current perspective
PI_VIEW_ID Importing Comment View Id
PI_TARGET_LANGUAGE Importing Requested language


PIH_TRANSLATION_CHG Importing /OTX/PF62_CL_FC_CMT_
TRANS_CHG class, contains
the displayed comments.
Translations must be set in
this class.
Methods of PIH_TRANSLATION_CHG parameter(/OTX/PF62_CL_FC_CMT_TRANS_CHG

class ):
Method Description
/OTX/PF62_IF_FC_CMT_CUST_ Get settings of comment view
GET~GET_SETTINGS
/OTX/PF62_IF_FC_CMT_GET~GET_ Get currently displayed comments
COMMENTS
/OTX/PF62_IF_FC_CMT_TRANS_ Get currently displayed translations
GET~GET_TRANSLATIONS
/OTX/PF62_IF_FC_CMT_TRANS_ Add additional translations
CHG~ADD_TRANSLATIONS
/OTX/PF62_IF_FC_CMT_TRANS_CHG~ADD_TRANSLATIONS method has the following

importing parameters:
• PI_LANGUAGE_KEY to define the language of the translations

• PIT_TRANSLATIONS for the translation texts
The structure of PIT_TRANSLATIONS has following fields:

COMMENT_ID Has to be the same as the one of the related
comment
TRANSLATED_INFO Translation of the info text
TRANSLATED_TEXT Translation of the comment text
COMMENT Comment information. Must only be set when
the translation is for a comment that has not been
displayed yet

9.12.3.6 CHECK_SAVE_DATA
This method allows setting field messages of the attribute list views and table views
of the current perspective. It is called when checking or saving the changed data is
required.

PI_CHECK_ONLY Importing Only check is required.
PI_DEVICE Importing Device type. Possible
values:
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PIT_CHECK_SAVE_ATTRIBUTE_LISTS Importing Attribute lists

PIT_CHECK_SAVE_TABLE Importing Tables
PI_TRANSPORT_REQUEST Importing Transport Request Number
PET_EXCEPTIONS Exporting Exceptions
PES_SAVE_RESULT Exporting Save result
PI_LOCKED Importing Flag to indicate that the
object is locked
PI_LOCKED_BY Importing SAP User name of the user
who locked the object
Line structure of PIT_CHECK_SAVE_ATTRIBUTE_LISTS:

VIEW_ID View ID
ATTRIBUTE_LIST Instance of class /OTX/
PF62_CL_FC_ATTRLST_CHS. The following
methods allow setting messages:
SET_FIELD_MESSAGES
ADD_FIELD_MESSAGE
ASSOCIATED_WOBJ_TYPE Associated work object type
WOBJ Instance of work object
Line structure of PIT_CHECK_SAVE_TABLE:


VIEW_ID View ID
displayed
TABLE Instance of class /OTX/
PF62_CL_FC_LI_CHANGE. You can access the
items displayed in the table using the following
methods:
• GET_ITEMS_WITH_POSITIONS
• GET_ADDED_ITEMS
• GET_CHANGED_ITEMS
• GET_DELETED_ITEMS
These items have the
methods SET_FIELD_MESSAGES and
ADD_SINGLE_FIELD_MESSAGE, which allow
the setting of messages for fields of these items.
ASSOCIATED_WOBJ_TYPE Work object type of items
Structure of parameter PET_EXCEPTIONS:

EXCEPTION_ID Exception ID
TYPE Exception type. Values:
• S - Success
• I - Information
• W - Warning
• E - Error
COUNTER Message counter

EXCEPTION_DESC Short description
MESSAGE Message text
Structure of PES_SAVE_RESULT:

MSG Message text
STATUS SUCCESS: Update successful
ERROR: Update error

9.12.3.7 CHANGE_PERSPECTIVE_VIEWS
This method changes the views of an item perspective at the initial load of the
perspective.

PIT_VIEWS Importing Views of the perspective
PIH_WOBJ_TYPE Importing Work Object Type
PIT_KEYS Importing Keys of the root object
PI_PERSPECTIVE_ID Importing Perspective Id
Structure of PIT_VIEWS:

VIEW_ID View ID
VIEW_NAME Technical view name as displayed in the
perspective editor
VIEW View object. You change the view name and
technical details of the view via /OTX/PF62_IF_
PERS_VIEW_CHG~SET_VIEW method
9.12.3.8 UPDATE_ROW_VALUES
This method allows changing data of a line item after change of a line item cell.

PI_DEVICE Importing Device type. Possible
values:
• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PIH_WOBJ_TYPE Importing Work object type

PIT_KEYS Importing Keys
PI_PERSPECTIVE_ID Importing Perspective ID


PIH_UPDATE_ITEM Importing Updated line item.
Instance of /OTX/
PF62_CL_FC_LI_LINO
BJ_UPD. Method
SET_CELL_VALUES
allows changing the
cell values.
PIH_ASSOCIATED_WOBJ_TYPE Importing Associated work object
type


PIH_GET_VIEWS Importing The parameter PIH_
GET_VIEWS is of
type /OTX/PF62_CL_
GET_VIEWS. This
class has the following
methods which return
all attribute lists /
advanced line item
tables of a perspective:
• GET_ATTRIBUTE_
LISTS
Returns all
attribute lists of a
perspective.
• GET_ATTRIBUTE_
LIST_BY_NAME
The method
returns the
attribute list (/
OTX/PF62_CL_
FC_ATTRLST_
GET) of a view.
• GET_ADV_LINE_
ITEM_TABLES
Returns all tables of
a perspective
• GET_TABLE_BY_
NAME
The method
returns the
advanced line item
table (/OTX/PF62_
CL_FC_LI_GET) of
a view
Tip: Due to
performance
reasons, use the
GET_
ATTRIBUTE_
LIST_BY_NAME
and GET_
TABLE_BY_
NAME methods
whenever
possible.
PI_LOCKED Importing Flag to indicate that
the object is locked


PI_LOCKED_BY Importing SAP User name of the
user who locked the
object
PIS_PREV_CELL_VALUE Importing Contains the values of
the cell that triggered
an update, before it
was changed by the
user
9.12.3.9 UPDATE_ATTRIBUTES
This method allows updating the attribute values after a value change of an
attribute.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PIH_ATTRIBUTE_LIST_UPD Importing Instance of /OTX/
PF62_CL_FC_ATTRLST_UPD.
Method SET_ATTRIBUTES allows
changing the attribute values.
PI_UPDATED_ATTRIBUTE Importing Name of updated attribute that
triggered the update.


PIH_GET_VIEWS Importing The parameter PIH_GET_VIEWS is
of type /OTX/PF62_CL_GET_
VIEWS. This class has the
following methods which return all
attribute lists /advanced line item
• GET_ATTRIBUTE_LISTS
Returns all attribute lists of a
perspective.
• GET_ATTRIBUTE_LIST_BY_
NAME
The method returns the
attribute list (/OTX/PF62_CL_
FC_ATTRLST_GET) of a view.
• GET_ADV_LINE_ITEM_
TABLES
Returns all tables of a
perspective
• GET_TABLE_BY_NAME
advanced line item table (/
OTX/PF62_CL_FC_LI_GET) of
a view
Tip: Due to performance

reasons, use the GET_
ATTRIBUTE_LIST_BY_
NAME and GET_TABLE_BY_
NAME methods whenever
possible.
locked
locked the object
PIS_PREV_CELL_VALUE Importing Contains the values of the cell that
triggered an update, before it was
changed by the user

9.12.3.10 CHANGE_ACTION_PARAMETER
This method allows changing the parameter of a table action before the action is
performed.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PIH_ITEM Importing Line item for which the action is
performed.
PIH_TABLE Importing Table
PC_PARAMETER Changing Parameter


perspective.
NAME
TABLES
perspective
a view

ATTRIBUTE_LIST_BY_
possible.
locked
locked the object
9.12.3.11 UPDATE_AFTER_REL_ATTR_LIST_CHG
This method is called after the change of a value in a related attribute list. The
method allows changing data in attribute lists and table views that have a relation to
the changed attribute list.


• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI
PIS_UPDATED_ATTRIBUTE_LIST Importing Updated Attribute List

PIT_UPDATE_ATTRIBUTE_LIST Importing Related attribute lists that can be
updated
PIT_UPDATE_TABLES Importing Related table that can be updated
locked
locked the object
Structure of PIS_UPDATED_ATTRIBUTE_LIST:

WOBJ Work object
VIEW_ID View ID
KEYS Keys
ATTRIBUTE_LIST Attribute list instance of class /OTX/
PF62_CL_FC_ATTRLST_GET
UPDATED_ATTRIBUTE Updated attribute
PREVIOUS_ATTRIBUTE_VALUES Contains the values of the attribute that triggered
the update, before it was changed by the user
Structure of PIT_UPDATE_ATTRIBUTE_LIST:

WOBJ Work object
VIEW_ID View ID
KEYS Keys


ATTRIBUTE_LIST Attribute list instance of class /OTX/
PF62_CL_FC_ATTRLST_UPD. Method
SET_ATTRIBUTES allows changing the attribute
list values.
Structure of PIT_UPDATE_TABLES:

VIEW_ID View ID
TABLE Table that can be updated. Instance of class /OTX/
PF62_CL_FC_LI_UPDATE. The following
methods allow changing the data of the table:
ADD_ROW
DELETE_ROW
SET_ROW_POSITIONS
ASSOCIATED_WOBJ_TYPE Associated work object type
9.12.3.12 UPDATE_NEW_ROW
This method allows to read the data of an item that has been added to an advanced
line item table by a user. With method SET_CELL_VALUES of parameter PIH_NEW_
ITEM, the values of this object can be changed.

• SMARTPHONE
• MOBILE
• DESKTOP
• COMBI

PIT_KEYS Importing Work object key values
PIH_NEW_ITEM Importing New object
PIH_ASSOCIATED_WOBJ_TYPE Importing Instance of associated work object
type


perspective.
NAME
TABLES
perspective
a view

ATTRIBUTE_LIST_BY_
possible.
locked
locked the object
9.12.3.13 CHANGE_VIEWS_FOR_REFRESH
This method defines the views that are refreshed during run time.

PI__ACTION_ID Importing Action ID
PCT_VIEWS Changing View IDs. Contains only the view
ID of the currently used item
perspective.


locked
locked the object
9.12.4 BAdI /OTX/PF62_SERVICE_HANDLER

This BAdI provides the feature to change content that does not depend on a work
object type. It implements the /OTX/PF62_IF_BAPI_SERV_HANDLER interface, which
provides the following methods:
9.12.4.1 CHANGE_USER_DETAILS
This method provides the feature to change information for users. This function is
called for the user details in the history view.

PI_USER_ID Importing User ID.
PCS_USER_DETAILS Changing User details.
PCT_RETURN Changing Error messages.
PC_ERROR_TYPE Changing Error type. Available types are:
1 - Business error
2 - Technical error
PCT_RETURN.
PE_BUS_ERROR_HANDLING Changing Allows to define the UI behavior in
1 - No update
3 - Item refresh
4 - Remove item
Structure of parameter PCS_USER_DETAILS:

USERID User ID
USERNAME User name
ATTRIBUTE1 User attributes
ATTRIBUTE2
ATTRIBUTE3
PHONE Phone number


EMAIL Email address
PICTURE_URL URL for user photo
9.12.4.2 CHANGE_PERSPECTIVES
This method is obsolete with Business Center 16.3. The interface still exists but the
method is not called any longer.
9.12.4.3 CHANGE_PERSPECTIVE_VIEWS
This method is obsolete with Business Center 16.3. The interface still exists but the
method is not called any longer.
9.12.5 BAdI /OTX/PF62_BADI_INPUT_HELP

The /OTX/PF62_BADI_INPUT_HELP BAdI implements the /OTX/PF62_IF_BAPI_HELP
interface. The following interface methods are available:
“CHANGE_HELP_COLUMNS” on page 435
“CHANGE_HELP_ROWS” on page 436
“CHANGE_FILTER_OPTIONS” on page 437
9.12.5.1 CHANGE_HELP_COLUMNS
The VIM Foundation calculates the input help structure and then calls this method.
You can change the structure of the input help or define a new structure as an input
help type Only user exit (BAdI /OTX/PF62_BADI_INPUT_HELP. You must also
consider these changes in the implementation of the CHANGE_HELP_ROWS method.

PI_HELP_ID Importing ID for search help
PI_MASTER_FIELDNAME Importing Field name for which this input help is
called
PCT_HELP_COLUMNS Changing Definition for columns of search help
PCT_RETURN Changing Return parameter table (error messages)
PC_ERROR_TYPE Changing Error type
Structure of PCT_HELP_COLUMNS:

COLUMN_ID Column ID for items.
COLUMN_TITLE Long field label.


TYPE ABAP data type.
LENGTH Field length.
FIELDNAME Contains the technical name of the search help field.
IN_SEARCH_MASK Include in the search mask.
IN_RESULT Include the column in the result list.
IS_MASTER_COLUMN Column is used as master column. The value is returned
to the field for which the F4 help is called.
IS_DESCRIPTION Column is a description field. In drop-down helps, only
the values of these fields are displayed. Internally, the
value of field IS_MASTER_COLUMN is used.
You can set the fields IS_MASTER_COLUMN and IS_DESCRIPTION to true in a

structure only once. A maximum of 10 columns is allowed.
9.12.5.2 CHANGE_HELP_ROWS
The VIM Foundation calculates the input help values and then calls this method. If
you have changed the columns in the CHANGE_HELP_COLUMNS method, you must
adapt the values of these columns accordingly.

PI_HELP_ID Importing ID for search help
PIT_FILTER_OPTIONS Importing Filter options for the search help values
PCT_HELP_ROWS Changing Search help values
PCT_RETURN Changing Return parameter table (error messages)
PC_ERROR_TYPE Changing Error type
Structure of PCT_HELP_ROWS:

ROW_ID Unique row ID
COLUMN_ID01_VALUE Value of column 01 for the current row
COLUMN_ID02_VALUE - Value of column 02 and further
COLUMN_ID10_VALUE corresponding columns for the current row

9.12.5.3 CHANGE_FILTER_OPTIONS
This method is called before calling the search help exit. It allows you to change the
filter options.

PI_HELP_ID Importing ID for search help.
object.
PI_LOGSYS Importing Logical system.
PI_OBJECT_KEY Importing Object key.
PCT_FILTER_OPTIONS Changing Filter options.
Structure of PCT_FILTER_OPTIONS:

ATTRIBUTE Attribute
SIGN I or E for an (I)nclude or (E)xclude condition
OPTION Option of the condition (EQ, BT, NE, …)
LOW Lower filter value
HIGH Higher filter value
9.12.6 /OTX/PF63_IF_FS_LIST interface

The full screen list interface /OTX/PF63_IF_FS_LIST comprises the following
methods:
9.12.6.1 CHANGE_CUSTOMIZING
Tip: Values that you enter here are not changed by the VIM Foundation later.
Use the /OTX/PF62_CL_UTILITIES method to change for example the
calculation of the correct perspective ID for the device type.


PIH_FS_LIST_CUSTOMIZING Importing Parameter PIH_FS_LIST_
CUSTOMIZING is an instance of class /
OTX/PF62_CL_FC_FSL_CUST_CHG.
PIH_FS_LIST_CUSTOMIZING has
methods to get all relevant
information of the fullScreenList.
Additionally it has methods for
changing the columns, actions and
general settings of the
FullScreenList.
9.12.6.2 CHANGE_DATA

PIH_FS_LIST_CHANGE Importing Parameter PIH_FS_LIST_CHANGE is
an instance of class /OTX/PF62_CL_
FC_FSL_CHANGE. This class offers
GET methods for all relevant
information.
Rows can be added and deleted. For

changing existing rows method /
OTX/PF62_IF_FC_FSL_
CHANGE~GET_ROWS returns for each
row an instance of class /OTX/PF62_
CL_FC_FSL_ROW_CHG. This class
allows to change the cell values,
actions and to highlight a row.
9.13 Helper classes for exit methods: /OTX/

PF62_CL_UTILITIES
Class /OTX/PF62_CL_UTILITIES provides functions for exit implementations.
9.13.1 Calculating the JSON of the link parameter

Use the auxiliary method GET_JSON_FOR_LINK_PARA of the /OTX/PF62_CL_
UTILITIES class, to calculate the JSON of the link parameter.
Table 9-3: Parameters of GET_JSON_FOR_LINK_PARA method

PI_SEMANTIC_OBJECT Importing Semantic object
PI_ACTION Importing Action of semantic object

9.13. Helper classes for exit methods: /OTX/PF62_CL_UTILITIES

PI_WORKPLACE_ID Importing Workplace ID
PI_SYSTEM Importing System Alias
PI_FILTER Importing Filter (value will be URL-encoded in
the method)
PI_SEARCH_FIELD Importing Search field
PI_SEARCH_VALUE Importing Search value (value will be URL-
encoded in the method)
PI_SORT_OPTION Importing Sort option
PI_SORT_DIRECTION Importing Sort direction
PIT_OTHER_PARAMETERS Importing Generic Parameters, can be used for
calculation links to other apps
PI_APP_MODE Importing Sets the appMode parameter of the BC
Fiori App
PI_DEACTIVATE_LETTERBOX Importing Deactivates the letter box.
If the PI_DEACTIVATE_LETTERBOX
parameter is set to X, then the
letterBox app parameter is set to
the value false.
PI_DEACTIVATE_SEM_NAV Importing Deactivates the semantic object
navigation
If the PI_DEACTIVATE_SEM_NAV
parameter is set to X, then the
semanticNavEnabled parameter is
set to false.
PI_SPLIT_APP_MODE Importing Sets the Split App Mode to active
If the PI_SPLITT_APP_MODE
parameter is set to X. then
splitAppMode app parameter is set
to true.
PI_WEBID Importing ID used in the web UI.
The value of the PI_WEBID parameter

is used for the webId app parameter.
PI_WEBID_ALIAS Importing Alias of the Web ID
The value of the PI_WEBID_ALIAS

parameter is used for the
webIdAlias app parameter.
PR_JSON Returning JSON for link parameter

To calculate the JSON for a link pointing to the Fiori Task App, set the following
parameters:
• PI_SEMANTIC_OBJECT
• PI_ACTION
• PI_NODE_ID
• PI_WOBJ_TYPE
• PI_WORKPLACE_ID
• PI_SYSTEM
If one of the parameters PI_NODE_ID, PI_WOBJ_TYPE or PI_WORKPLACE_ID is not set,

only the parameters in PIT_OTHER_PARAMETERS are considered.
To calculate the link parameters for other applications than the Fiori Task App, use
the parameters PI_SEMANTIC_OBJECT, PI_ACTION, and PIT_OTHER_PARAMETERS
only.
9.13.2 Calculating the ID for the device type

Use the GET_PERS_ID_FOR_DEVICE method of the /OTX/PF62_CL_UTILITIES class
to calculate the perspective ID for the device type that is used.
Table 9-4: Parameters of GET_PERS_ID_FOR_DEVICE method

PI_PERSPECTIVE_IDT Importing Perspective ID
PI_PERSPECTIVE_TYPE Importing Perspective type
PR_PERSPECTIVE_ID Returning Perspective ID
9.14 Configuring deprecated views

This section describes the customizing of deprecated views. These views cannot be
used in new item perspectives but they are still displayed in already existing item
perspectives. The following sections describe how you can change the configuration
for these views.

9.14. Configuring deprecated views
9.14.1 Configuring the header view

In this step, you configure the header view of a perspective.
To configure the header view:

Header View in the Dialog Structure.
4. On the Header View Details screen, enter the field descriptions, using the
• Workobject type: Work object type for which this layout is used
• Perspective ID Item
• Intro text
• Title
• Mark favorite: The favorite icon is displayed.
• Mark as flagged: The flag icon is displayed.
• Number state: The fields 1st Status and 2nd Status are colored according to
the status value: Error - red, Warning - yellow, Success - green, None -
black ).
• Number
• Unit Text
• Link type
This field defines the type of the link for semantic object navigation. Possible
values:

– No link
– Semantic object navigation
App” on page 279.
• Link parameter
This field contains the JSON with the link parameters. For more information,
see “Semantic object navigation with the Fiori Task App” on page 279. The
JSON data must match the following structure:
{
"target": {
"action": <action>
},
"params": {
}
}
• 1st Attribute
• 2nd Attribute
• 1st Status
• 2nd Status
Notes
• Business Center 16 Update 1 has added the Link type and Link parameter
fields to the item header customizing. These fields are only available in the
item header customizing and not in the master list customizing. For more
information, see “Configuring the item header details” on page 442.
• You can change the settings of this customizing by implementing the
method CHANGE_OBJECT_HEADER of the web handler class. For more
information, see “CHANGE_OBJECT_HEADER” on page 405.
9.14.2 Configuring the item header details

In this step, you define the field values displayed in the Detail view ot.approve.
requests.view.ItemDetails. You can define up to 20 attributes that should be
displayed. Each attribute must be a field of the display structure.

method CHANGE_HEADER_DETAILS of the web handler class. For more information,
see “CHANGE_HEADER_DETAILS” on page 398.
You can set item header detail fields to editable and required. You can also link
input helps to the fields. A field can be set to editable, and no input help is linked. In
this case, the Web Services automatically check if the field in the header structure is
linked to a SAP search help or a domain with values. For more information, see
“Input helps” on page 339. The Web Services use this information to generate an
input help in the Fiori Task App for this field.

To configure the item header details:
1. Run the /n/OTX/PF62_IMG_OLD transaction.

2. Click Business Center - Web Services - Deprecated Activities > Items > Item
Header Details.
3. In the Header details Overview screen, configure object header details using
Work object type

Work object type for which the item header details are configured.
Perspective ID Item
For more information, see “Enabling nodes for Web Services” on page 311.
Perspective view ID
Unique ID of the perspective view.
Position
Sequence of the item header details.
Field Name
Enter the field name of the display structure of the work object type.
Editable
To allow the field to be edited, select this check box.
Required
To set the field as required, select this check box.
Checkbox
To display the field as a check box, select this check box.
The field must be of type CHAR with length 1. Valid values are: X = true
and <blank> = false.
Search Help ID
Enter the unique ID of the search help for the field. For more information,
see “Input helps” on page 339.
Help Variant
help.
• Drop-down list: Users can select values in a drop-down list.

Value Description
Select this check box to display a description behind the value field.
The value description is not automatically set, but has to be implemented in
the CHANGE_HEADER_DETAILS method of the web handler.
The ON_VALUE_UPDATE_HEADER_DETAIL method enables you to change the
value description after the value has changed.
Update on change
Select this check box to trigger the ON_VALUE_UPDATE_HEADER_DETAIL
method of the web handler if the value of the field is changed. For more
information, see “ON_VALUE_UPDATE_HEADER_DETAIL” on page 400.
Link type
Possible values:
• No link
App” on page 279.
Link parameter
This field contains the JSON with the link parameters. For more
on page 279. The JSON data must match the following structure:
{
"target": {
"action": <action>
},
"params": {
}
}
9.14.3 Configuring the item list title

In this step, you define the title of the item list for a work object type.

method CHANGE_ITEM_LIST_TITLE of the web handler class. For more information,
see “CHANGE_ITEM_LIST_TITLE” on page 409.
To configure the item list title:

2. Click Business Center - Web Services - Deprecated Activities > Line Items >
Line Item List Title.
3. In the Titles of item list Overview screen, configure the line item list titles
Work object type

Work object type for which the item list title is configured.
Perspective ID - Item
ID of the item perspective.
Language
Language of the title.
Title
Enter the title text. You can use {n} to integrate the number of items in the
title.
9.14.4 Configuring line item details

In this step, you configure the structure of the item list. You must set the item data in
method GET_ITEMS of the web handler class.

method CHANGE_ITEM_STRUC of the web handler class (see
“CHANGE_ITEM_STRUC” on page 396).
To configure line item details:
2. Click Business Center - Web Services - Deprecated Activities > Line Items >
Line Item Details.
3. In the Line Items Overview screen, configure line item details using the
Work object type

Work object type for which the item details are configured.
Perspective ID - Item
ID of the item perspective.
Column ID
Define in which columns the field should be displayed. You can define a
maximum of 10 columns.
Field Name
Enter the field name in the item structure. This structure must be defined in
the web handler implementation. For more information, see “Web handler”
on page 380.

Search Help ID
Enter the unique ID of the search help for the field. For more information,
see “Input helps” on page 339.
Mobile
Select this check box to set the priority for mobile devices. If only a reduced
number of columns is displayed on mobile devices, these columns are
displayed with priority.
Editable
Select this check box to mark the column as editable.
Checkbox
Select this check box to display the field as a check box.
The field must be of type CHAR with length 1. Valid values are: X = true
and <blank> = false.
Is Unit
Select this check box to mark the values of the column as units of a
previously defined column.
Update
Select this check box to trigger the ON_VALUE_UPDATE_ITEM method of the
web handler if the value of the field is changed. For more information, see
“ON_VALUE_UPDATE_ITEM” on page 397.
Link type
Possible values:
• No link
App” on page 279.
9.14.5 Configuring the data binding for a full screen list

In this step, you configure the display of a work object in the full screen list. You
define the structure of the node list as a table with columns.

Example 9-1: Full screen list
To configure the data binding of a full screen list:
Workplace > Nodes.
3. In the Nodes Overview screen, mark a node, and then double-click Full Screen
List - Data Binding in the Dialog Structure.
4. In the Full Screen List - Data Binding Overview screen, double-click an entry.
5. In the Full Screen List - Data Binding Details screen, configure the data
binding using the following parameters:
• Column Id: Use this numeric field to define the order of columns.
• Field Name
• Width (CSS)
• Display style: Choose one of the following options:
– Normal text field

– Display as icon
– Display as checkbox (requires boolean)

• Navigation type: Choose one of the following options:
– Show popup
– Show inplace
– Navigate to semantic object

– Navigate to edit view

– Call action dialog

– No link
• Nav. link parameter (Navigation link parameter)
• Action ID
• Visibility on phones
• Visibility tablets
• Visibility desktops
• Vis. Combi Device (Visibility Combi Device)
Note: SAP provides the following definition of the device type

“combi”:
If this flag is set to true, the device is recognized as a combination of a
desktop system and tablet. Furthermore, a CSS class sap-combi is
added to the document root element.
For more information, see https://openui5.hana.ondemand.com/#/api/
sap.ui.Device.system/properties.
For phones, tablets, desktops, and combi device, choose one of the following
visibility options:
– Display as normal column

– Do not display
– Display as Popin
• Export enabled
Select this check box to add the content of the current column to a
spreadsheet that can be downloaded as a Microsoft® Excel® file. By hiding
columns, users can restrict the downloaded columns. If one of the node list
columns is export enabled, a Download button is available.
• Transport type: Choose one of the following options:
– No transport required (default)
– Customizing request
– Workbench request
• Medium Fld Labl (Medium field label)
• Default value
• Tooltip: Enter tooltip for the node list column.
This setting can be overwritten using the CHANGE_NODE_LIST_COLUMNS
method of interface /OTX/PF62_IF_NODE. For more information, see
“CHANGE_NODE_LIST_COLUMNS” on page 378.

Chapter 10
Fiori Task App running scenarios
You can run the Fiori Task App in several ways:
• integrated into Fiori Launchpad

• standalone
Fiori Task App running scenarios differ depending on the place of integration. This
section describes on-premises integration and integration on SAP Cloud Platform in
separate subsections.
10.1 On-premises integration

10.1.1 Integrating Fiori Task App into Fiori Launchpad
For more details and further information about the Fiori Launchpad, see http://
scn.sap.com/docs/DOC-53178.
The description in this section applies to Launchpad tiles using a Business Center
16.3 backend. If you are using the OTBCWUI 16.3 add-on in combination with a
Business Center 16 SP2 backend, see Section 9.1 “Integrating Fiori Task App into
Fiori Launchpad” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160002-CGD) (documentation Business Center 16 SP2).
To integrate Fiori Task App into Fiori Launchpad:
1. Assign catalogs to role.

You can download the launchpad catalogs from the Launchpad Content in the
patches area.
For a description how to assign tile catalogs to roles, see the SAP
documentation.
The delivered catalogs are the following:
Solution/Purpose Catalog ID
VIM Foundation (for cross /OTBCWUI/PF07_BC_FOUNDATION
solution apps)
Delivery Note /OTBCWUI/PF07_BC_SOL_DELIVERY_NOTE
Sales Order /OTBCWUI/PF07_BC_SOL_SALES_ORDER
HR Documents /OTBCWUI/PF07_BC_SOL_HR_DOCUMENT
Remittance Advice /OTBCWUI/PF07_BC_SOL_REMITTANCE_ADV

Chapter 10 Fiori Task App running scenarios
Solution/Purpose Catalog ID
Order Confirmation /OTBCWUI/PF07_BC_SOL_ORDER_CONF
Quotations /OTBCWUI/PF07_BC_SOL_QUOTATION
VIM Foundation Administration /OTBCWUI/PF07_BC_ADMIN
(for solution implementers)
2. Personalize the Launchpad.

Users can now access the Launchpad with the relative URL /sap/bc/ui5_ui5/
ui2/ushell/shells/abap/Fiorilaunchpad.html.
To add tiles to the home page, users must click the profile icon and then Edit
Home Page. From there they can search in the assigned catalogs and use the
plus icon to add the wanted solution tiles directly to the home page or organize
them in groups.

10.1. On-premises integration
10.1.2 Creating a custom solution tile

To create a custom solution tile:
1. Open the Launchpad designer using the following relative URL:

https://<host>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.
html
2. To create a new catalog, click Add on the lower left.
3. Search for the Vendor Invoice Management Administration catalog.
4. Select a target mapping from the Target Mappings tab, and then click Create
Reference. From the catalog list in the dialog box, select the previously created
catalog.
5. Go back to your newly created catalog.
6. Click the Tiles tab, and then click Create.

7. Choose between a dynamic or static tile.
8. Enter the necessary data in the dialog as shown in the following:

General
Title
Enter a title of your choice.
Subtitle
Enter a subtitle of your choice.
Dynamic Data
Service URL
Optionally you can maintain a service URL for displaying the number of
tasks in a node at the tile. This service URL has the following syntax:
/sap/opu/odata/OTX/PF05_DATA;mo;v=3/Nodes(<Node parameter>)/
Objects/$count, where <Node parameter> is described in the following list:
<Node parameter>
A node is defined by the following parameters:
SAP__Origin: System alias of backend system.
deviceType: Device type. Leave empty for $count request.
nodeId: ID of the node.
wobjType: Work object type of the node.
workplaceId: Workplace ID.
Example: /sap/opu/odata/OTX/PF05_DATA;mo;v=3/Nodes(SAP_
_Origin='OTBCWUI_BACKEND',deviceType='',nodeId='PS01_DELIVERY_
INBOX', wobjType='PS01_PRC_DELIV',workplaceId='WP_INBOX')/
Objects/$count

10.2. SAP Cloud Platform integration
Navigation
Use semantic object navigation

Select this check box.
Semantic Object
Enter OTBCWUI_PF07_BC_SEMOBJ. Starting with 16.3 SP4 enter
otbcwuipf07bc.
Action
If the used solution perspectives can only be shown properly on desktop,
enter action display or displayDesktop.
Parameters
Enter an appropriate combination of parameters with values depending on
the chosen Application Mode. For more information, see “Application
modes” on page 270.
10.1.3 Running the Fiori Task App standalone

You can run the Fiori Task App also without Fiori Launchpad. Use the following
URL:
http://<host>:<port>/sap/bc/ui5_ui5/otbcwui/pf07_bc_ui_03/index.html?
<parameters>
where you replace the <parameters> variable with an appropriate combination of

parameters with values depending on the chosen Application Mode. For more
information, see “Application modes” on page 270.
Example for the http://<host>:<port>/sap/bc/ui5_ui5/otbcwui/pf07_bc_ui_03/index.html?

Sales Order nodeId=PS02_ORDER_INBOX&system=OTBCWUI_BACKEND&wobjType=PS02_PRC_
solution
ORDER&workplaceId=WP_INBOX
10.2 SAP Cloud Platform integration

10.2.1 Integrating Fiori Task App into a SAP Cloud Platform
Portal Fiori Launchpad site
To integrate Fiori Task App into a SAP Cloud Platform Portal Fiori Launchpad
site:
1. On the Cloud Platform Cockpit, on the menu on the left, open the Services
node.

2. In the content pane on the right, click the Portal tile.
Note: For this action, the service must be enabled.
3. On the main navigation on top of the screen, click Configure Portal.

In the menu on the left, click Roles. Create roles reflecting your business needs.
As a simple sample for this description, a role with name BC_ROLE is assumed.
Assign the role to appropriate users/groups.

4. To go back to the overview, click Portal on the main navigation. Then click the
Go to service action.
Create a new Fiori Launchpad Site or choose an existing one.
5. On the menu, click Services and Tools.
Open the Transport Manager tile. Click the tab Import and select the required
content archive.
6. Assign the imported catalogs to the created roles.

7. Set the appropriate UI5 version for the Launchpad under Settings.
Note: The UI5 version must be supported by the current release. See the
Release Notes for details.
8. Finally publish the site to make it available for your users.
The content archives can be downloaded in the patches area from the Launchpad
Content folder. They comprise:
• Vendor Invoice Management - Foundation

• Vendor Invoice Management - Administration
• Vendor Invoice Management - Solution Order Confirmation
• Vendor Invoice Management - Quotation
• Vendor Invoice Management - Solution Sales Order
• Vendor Invoice Management - Solution Delivery Note
• Vendor Invoice Management - Remittance Advice
10.2.2 Creating a custom solution tile

To create a custom solution tile:
1. On the Cloud Platform Cockpit, click Apps on the menu on the left.
From the Cloud Platform Cockpit, access the Portal Service. In the Portal,
choose an existing Fiori Launchpad Site or create a new one. In the site
administration, click Applications on the left.

2. Search for the App Resource otbcwuipf07bc.
Important
If you keep the default semantic object otbcwuipf07bc, the action for your
set of parameters must be unique.
3. Enter the parameters as needed, depending on the chosen application mode. For
more information, see “Application modes” on page 270.
Note: Do not flag the parameters as mandatory.
4. Dynamic Tile Settings

When referring to the PF05_DATA service for count information, construct the
URL in the following way:
Example:
/destinations/PF05_DATA/
Nodes(SAP__Origin='OTBCWUI_BACKEND',deviceType='',nodeId='PS01_DELIVERY_INBOX',wobjTy
pe='PS01_PRC_DELIV',workplaceId='WP_INBOX')/Objects/$count
5. Assign the tile to the required catalogs and/or groups.

10.2.3 Running the Fiori Task App standalone

You can run the Fiori Task App on SAP Cloud Platform without a Fiori Launchpad
Site in the Cloud Platform Portal. The URL is constructed in the following way:
<applicationUrl>/?<parameters>
• To get the <applicationUrl>, click the application. Under section Active Version,
you find the Application URL.
• Replace the <parameters> variable with an appropriate combination of parameters
with values depending on the chosen Application Mode. For more information,
see “Application modes” on page 270.
Example for the Sales Order solution:
https://pf07bcneoui03-a9e96cfa0.dispatcher.hana.ondemand.com/?nodeId=
PS02_ORDER_INBOX&system=OTBCWUI_BACKEND&wobjType=PS02_PRC_
ORDER&workplaceId=WP_INBOX

Chapter 11
Fiori Monitoring and Analytics reports
Analytics component of Vendor Invoice Management for SAP Solutions deliver

OData enabled Core Data Services (CDS) views with UI annotations to generate
reports based on FIORI elements.
The available CDS views are optimized for the generation of a specific SAP Fiori
elements template.
• For the technical information how to generate a Fiori template based on the
annotated CDS view, see Section 8 “Sales Order Analytics” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Solutions Beyond
Invoice (BOCP200400-CCS).
• For the steps how you generate and configure reports, see “Generation and
configuration” on page 459.
• For the options how you extend these reports, see “Custom Extensions”
on page 465.
Prerequisites
• SAP Cloud Platform (SCP) is connected to the respective on-premises systems

(backend and frontend) via SAP Cloud Connector.
• Access to WebIDE is enabled for backend and frontend system.
• The backend system should have the highest possible SP of the SAP_BW
component.
• SAP Notes 2767228 must be fully implemented on the backend system.
For details, how to connect to SCP, and how to enable WebIDE, see the SAP Help.
11.1 Generation and configuration

• “Activating services on the backend system” on page 460
• “Generating reports in Web IDE” on page 460
• “Adding local annotations” on page 462
• “Deploying reports on the frontend system” on page 463
• “Setting up a launchpad tile” on page 463
• “Custom Extensions” on page 465

Chapter 11 Fiori Monitoring and Analytics reports
11.1.1 Activating services on the backend system

To activate services on the backend system
1. On the backend system, go to transaction /IWFND/MAINT_SERVICE.
2. Set up the OData service as described in the solution-specific Technical Details

table. For more information, see OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP200400-CCS).
3. For details how to activate ODATA services, see SAP Help Portal (https://
help.sap.com).
11.1.2 Generating reports in Web IDE

To generate reports in Web IDE
1. Log in to Web IDE.
2. Click File > New > Project from Template.
3. Follow the wizard and enter the requested input.

The following table shows the general input for all kind of reports. For solution-
specific details refer to Technical Details table in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Solutions Beyond Invoice
(BOCP200400-CCS).
Table 11-1: Input for Project from Template wizard
Step Input
Template Selection • SAPUI5 Version
UI version of your frontend server.
• Template:
Choose the recommended template according the table.
For example, the List Report Application template for the
Monitoring report and the Analytical List Page template
for the Analytics report.
Basic Information Fill the required fields, marked with *. If necessary, provide a
namespace on your system:
• Project Name
• Titel
• Namespace
• Description
Data Connection Select the backend system and the OData service.

11.1. Generation and configuration
Step Input
Annotation Selection Select all annotation files that display.
If you use the Add Annotation Files action with Add From
Service, select the Generic Annotation Provider checkbox, to
see all delivered annotation files.
Template Customization OData Collection

The OData collection. If the collection has parameters,
choose the one with the ending Results.
For example, xOTXxPS02xALL_DOC_QUERYResults.
OData Navigation
If available, choose OData navigation.
OData Sub Navigation
For the List Report select Template features, like Smart
Variantsor Flexible Column Layout.
For example, SAP Help Portal (https://help.sap.com/)
Qualifier (content area) - only for Analytical List Page:
Default
Table Type:
Analytical (for Analytical List Page)
4. Click Finish.
The new project is available in the Web IDE
5. Optional For OData projects without parameters, click Run for a first sandbox
test.
6. Optional For some of the available Analytics List Page, the navigation from ALP
to the object page (the arrow at the end of each line in the table) is not necessary.
To remove the navigation:
a. In your IDE project, navigate to \webapp\ , double-click manifest.json

file .
b. Open the Code Editor tab in the footer of the Editor and delete the lines for
ObjectPage:
"pages": {
"ObjectPage|ZOTX_PS02H_ALL_PROC_QUERYResults": {
"entitySet": "ZOTX_PS02H_ALL_PROC_QUERYResults",
"component": {
"name":
"sap.suite.ui.generic.template.ObjectPage"

11.1.3 Adding local annotations

You can use local annotations to enter the default values for OData with input
parameters. You can also use local annotations to optimize the output of the report..
Each report comes with a local annotation.xml as example that you can customize.
You can find the name of the annotation.xml file in the technical details table of the
solution.
To import an example annotation XML
1. In Web IDE, select your project
2. Navigate to \webapp\annotations\ and open the annotations.xml in an

editor (for example, NotePad).
3. Open the annotations.xml that is delivered for the respective report.
4. Copy the content.
5. Go to the Code Editor.
6. Replace the generated content of the annotations.xml with the delivered XML
template.
7. Click Save.
To import the example translation files
For some reports, an example i18n file (internationalization file) is delivered to

display English standard texts. You can use the file for translation into further
languages.
1. Navigate to \webapp\i18n\ .
2. Open the i18n.properties file.
3. Paste the content of the delivered i18n file, to replace the generated file.
4. Click Save.
5. Optional Click Run to check the results.

You find new facets.

11.1. Generation and configuration
11.1.4 Deploying reports on the frontend system

You can now deploy the report that you created in Web IDE. Deploye, either to the
SAP Cloud Platform or to an on-premises frontend server.
The deployment process is described in detail on the SAP Help Portal (https://
help.sap.com).
The following procedure is an example of relevant activities to deploy to an on-

premises frontend server:
To deploy to an on-premises frontend server
1. In Web IDE, click Deploy button.
2. Deploy to the SAP UI5 ABAP repository
3. Enter a name for the BSP application.
4. Select a development package for the application.
5. Select a transport.
After the deployment, the BSP application for your report is available in the
selected package.
6. If needed, go to SICF transaction and activate the service for the created
application (Service Name = Name of the BSP application).
11.1.5 Setting up a launchpad tile

To set up a launchpad designer:
1. Open the Launchpad Designer.
2. Select or create a catalog to add the report.
3. To create a target mapping, click the Target Mappings node.

Keep all fields that are not mentioned here, either empty or with their default
values.
Semantic Enter a name for the semantic object. For example ZPS08.
Object:
Action: Choose or define an action. For example display.
Application Choose SAPUI5 Fiori App.
Type
Title Enter a title.

ID Enter the ID of the app.

You find the ID in the Component.jsof the App. The string
before .Component is the ID of the App. You can look up this file in
the Web IDE or in SE80.
4. To create a tile, click the Tiles node:
a. In the General area, enter the title and subtitle.

b. In Navigationin Semantic Object field and Action field, enter the data that
was defined for the target mapping.
11.1.6 Enabling the semantic navigation

CDS views are using @SemanticObject annotation to define navigation links to
several targets.
For each report, you find the default semantic objects in the detail section. The
semantic object definition uses SAP standard objects, like SupplierInvoice and
Supplier to navigate to the respective SAP FI App.
• By Default, the report displays all navigation intents for a given semantic object.
• To reduce the number of available navigation intents, change the semantic object
that is used in the report to a custom semantic object. Change the semantic object
in the metadata extensions. For more information, see “Changing the appearance
with Metadata Extensions” on page 465.
• If you change the semantic object to a custom semantic object, also configure the
custom target mappings and the tile configurations for the SAP standard apps.
For navigation to VIM Foundation based Fiori Apps, you need to create an
additional target mapping with a semantic object that is defined in the respective
CDS view.
The values display in the detail section of the reports. You can also change the
standard semantic object by using the metadata extensions.
To enable the navigation to VIM Foundation based apps:
1. Open the Launchpad Designer.

2. Select or create a catalog.
3. In the Target Mappings tab, click Create Target mapping button.
4. Enter data in the Intent area:
Semantic Object:
For details, see detail page of the report (table entry: Semantic Navigation).
Action:
Display.

11.2. Custom Extensions
5. Enter data in the Target area:
Application Type:
SAPUI5 Fiori App
Title:
Add a title
URL:
/sap/bc/ui5_ui5/otbcwui/pf07_bc_ui_03
ID:
ot.approve.requests03
6. In Parameters area, enter the solution specific parameters.

The parameters are listed in technical details table of the solution. Check the
Semantic Navigation row. The table is available in the Analytics chapter of
each solution. For more information, seeOpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP200400-
CCS).
7. Click Save.
11.2 Custom Extensions

You can copy the provided CDS views and extend them with custom functionality.
Use the Metadata Extension (MDE) Concept for CDS views for minor UI related
changes in the appearance..
With the FIORI Elements templates you can perform modifications based on local
annotations in the WebIDE. For more information, see SAP Help (https://
help.sap.com).
11.2.1 Changing the appearance with Metadata Extensions

CDS Metadata Extensions (MDE) provide the UI annotations of the CDS views.
Here, you maintain UI related aspects, like the displayed fields, positioning or
grouping.
The MDE concepts allow to overwrite the standard annotations with custom specific
annotations without modifying the original objects.
To provide custom specific annotations:
1. Open the SAP ADT tools in Eclipse and connect to the backend system
2. Create a new Metadata Extension in the z namespace (your specific namespace)

and refer to the /OTX/-CDS view you want to enhance
3. Set the @Metadata.layer annotation to #CUSTOMER or to #PARTNER for

implementation partners.

4. Change the annotations to fulfill your requirements.

Changes are visible on the frontend immediately after you change the
annotations.
Example 11-1: MDE changed for the standard annotations of CDS view /
OTX/PS08_VC_A_INVBPF
The position of the Invoicing Party and Process ID fields is changed and the
semantic object reference for Invoicing Partyis removed.

Chapter 12
Accessing archived documents using a proxy
service
On Fiori applications, the following URLs to display archived documents are

available.
URL to the archive system

If you do not use a viewer, the Fiori applications by now use a URL that directly
points to the archive system for displaying documents. Therefore, you must put
the Archive Server (URL) into the Demilitarized Zone (DMZ) if you want to
access the image on the Fiori Task App outside the intranet domain.
URL to viewer application
As an alternative to a URL to the archive system, this kind of URL points to the
Web Viewer or to Brava! View. Therefore, it points to the archive only indirectly.
Documents are displayed using the viewer.
URL requested from the Fiori Task App
Starting with Business Center 16 SP1, an option is available to define a fix
external location that is used at the URL generation for a document if the URL is
requested from the Fiori Task App. You can use the General Settings parameter
EXTSDOKLOC (Location for Document URL generation for Fiori App). For
more information, see “Configuring general settings” on page 19.
To generate document URLs used by the Fiori Task App, SAP standard function
modules (for example SCMS_URL_GENERATE) are used. To achieve that these URLs do
not directly point to the archive but to a proxy service, you can use the Content
Server alias customizing.
The configuration of Content Server aliases is described in detail in section 5 “Cache

Server customizing in the Content Management Service (BC-SRV-KPR-CMS)” of the
SAP Scenarios with OpenText Archive Cache Server - White Paper, available on My
Support (https://knowledge.opentext.com/knowledge/cs.dll/fetch/2001/3551166/
27085941/14272488/15050695/16643454/15770872/15774847/15777136/
WhitePaper_SAP_Scenarios_with_OpenText_Archive_Cache_Server.pdf?
nodeid=58613067&vernum=-2).
For the calculation of the Location (see section 5.3.2 “Defining additional locations
for Content Server aliases” in the White Paper), VIM Foundation calls the SAP
standard modules in a way that user profile parameter LCA is used. If parameter LCA
is not maintained in the user profile, then the current IP is used. For the correct IP
calculation, installing SAP note 1833702 might be necessary.
The configuration of a proxy service in a SAP Web Dispatcher is described in the

SAP documentation.

Chapter 12 Accessing archived documents using a proxy service
Proxy for WebUI and ODATA

wdisp/system_0 = SID=D5O, NR=01, MSHOST=<Fiori server>, MSPORT=8101,
SRCSRV=*:*, SRCURL=/sap/opu/odata;/sap/bc
Proxy for Archive

wdisp/system_2 = SID=ARC, EXTSRV=<archive>:<port>, SRCSRV=*:*,
SRCURL=/archive
Note: SAP also recommends using SAP Web Dispatcher. For more
information, see, for example, section 3.1 “Deployment Options” in UI
Technology Guide for S/4HANA, on-premise edition 1511 (paragraph about
“Internet-Facing Deployment”), available in the SAP Help (https://
uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/
pdffee10356f3b43a35e10000000a44538d/1511%20000/en-US/
UITECH_OP1511.pdf)

Chapter 13
Useful methods
This chapter lists methods that can be useful in a global context.
13.1 /OTX/
PF00_CL_UTILITIES=>STRUCTURE_FIELD_VAL
UE_CONVERT
You can use this method in custom web handler implementations. The method
converts internal field values to an external output format. The reason for this is that
the standard SAP GUI conversions are not considered automatically.
13.2 /OTX/
PF00_CL_UTILITIES=>FIELD_VALUE_CONVERT
_STRUCTURE
You can use this method in custom web handler implementations. The method
converts external field values to an internal format. The reason for this is that the
standard SAP GUI conversions are not considered automatically.
13.3 /OTX/PF00_CL_UTILITIES=>TABLE_DATA_PACK
You can use this method whenever needed to transform structured internal table
data to a field value table format.
13.4 /OTX/
PF00_CL_UTILITIES=>TABLE_DATA_UNPACK
You can use this method whenever needed to transform a field value table to a
structured internal table data format. You can use the optional import parameter PI_
CONVERT_TO_INTERNAL if the data values should also be formatted to an internal
database format.

Chapter 13 Useful methods
13.5 /OTX/
PF00_CL_UTILITIES=>STRUCTURE_DATA_PAC
K
You can use this method whenever needed to transform a data structure to a field
value table format.
13.6 /OTX/
PF00_CL_UTILITIES=>STRUCTURE_DATA_UNP
ACK
You can use this method whenever needed to transform a field value table to a data
structure format. You can use the optional import parameter PI_CONVERT_TO_
INTERNAL if the data values should also be formatted to an internal database format.

Chapter 14
Document classification
This chapter describes automatic and manual document classification functions,

which are available from the VIM Foundation. Document classification determines
the correct document types and corresponding business processes for incoming
documents.
The following technical components are involved in a complete end-to-end

classification scenario as shown in Figure 14-1: “Document classification
components” on page 471:
Figure 14-1: Document classification components
Inbound Configuration - Capture
Classification
Automatic document classification by Information Extraction Service (IES): IES
usually classifies documents. You have to configure a classification profile.
Within this profile a custom field with class type is required. The
corresponding classification ID must refer to a scenario classification within the

Chapter 14 Document classification
inbound configuration where you assing document types for classification. For
more information, see “Creating scenario classifications” on page 56
Automatic document classification by Business Center Capture: For more
information, see Section 4.6 “Supported function types for custom fields in a
non-invoice application” in OpenText Business Center Capture for SAP Solutions -
Customization Guide (CPBC-CGD) and Section 4.7 “Configuring a Classification
function” in OpenText Business Center Capture for SAP Solutions - Customization
Guide (CPBC-CGD).
Classification Validation
Manual document classification within the classification validation. The
classification validation is triggered if the automatic document classification was
not possible.
To process the recognition correctly, do not skip the validation classification
within the validation assignment settings of the Inbound Configuration.
Recognition
In this step, only data extraction for the current classification takes place, no
classification functionality is involved.
Recognition Validation
In this step, only data validation takes place. If required, you can add a field
representing the current classification value. As soon as the classification field
value is changed, a new recognition step is triggered for the changed
classification. In general, you can skip the Recognition Validation by using the
validation assignment settings of the Inbound Configuration. For more
information, see “Customizing validation” on page 150.
Document Processing
Workplace
Manual reclassification in the Business Center Workplace if required. A restart
of the Capture process might result from this in special cases.
Processing Screen
Manual reclassification in the Processing Screen if required. A restart of the
Capture process might result from this in special cases.
Fiori Task App
Manual reclassification within the Fiori Task App if required. A restart of the
Capture process might result from this in special cases.
You can use a complete end-to-end classification scenario if different incoming

documents are not manually presorted before system input through scanning, email,
or other input channels. Presorting in this context means sorting incoming
documents by specific business scenarios, for example Sales or Human Resources,
and corresponding target document types, for example Employment Contract or
Employee Address Change Letter.
In general, distinguish between the following classification scenarios.

14.1. Document type handling
Classification across different business scenarios

Incoming documents are not presorted in any way. Their classification can result
in routing them to completely different business scenarios.
Classification within specific business scenarios
Incoming documents are already presorted by business scenarios. Their
classification only results in triggering different business processes for the
classified target document types in the specific business scenario.
Note: When the Classification and/or Classification Validation are finished,

you already must have set up a specific classification to continue processing.
Otherwise you must provide a special classification handling within the
business processes. If incoming documents are fully presorted already, the
Classification and Classification Validation will be skipped. In both cases,
specific classification or special classification handling, you can still perform a
reclassification in a later processing phase if required. For more information,
see “Creating scenario classifications” on page 56.
14.1 Document type handling

The document type customizing determines the classification options. For more
information, see “Assigning document types to classifications” on page 57.
All classification options are directly based on SAP ArchiveLink document types.
They are defined in the Inbound Configuration for the corresponding registration
type and channel. For more information, see “Customizing registration types”
on page 62.
Link each document type to the following SAP Business Object types. Linked
document types are available for classification in the OAC3 transaction. The Business
Object types represent the different involved components of the VIM Foundation.
/OTX/PF01
Inbound Registration Object
/OTX/PF02
Process Object
If you create or post SAP document during the business process, additional entries
for standard SAP business objects can be required. Thus, you attach the incoming
documents to the rarget SAP business objects.
You can change the classification type at any time. This also changes the SAP
ArchiveLink document type which results in adjusting the related ArchiveLink
connection entries. If the content repository must be changed to, re-archiving is
performed.
Note: Additionally offer an ArchiveLink document type for an unclassified

incoming document. This document is validated if no special classification

handling is provided within the business processes. The validation happens in

the validation assignment settings of the Inbound Configuration. The
connected Business Center Capture application of the document determines
whether a document type is considered as classified. Assign an unclassified
document type to a custom classification application. Assign all classified
document types to the corresponding scenario profiles.
14.2 Processing impacts

This section describes classification related dependencies between theVIM
Foundation components Inbound Configuration and Process Configuration. This
section also describes the special processing impacts when changing the
classification within a business process.
During inbound processing, all incoming documents are classified using specific
ArchiveLink document types as maintained in the Inbound Configuration. Each
document type is linked to a Scenario Classification profile. This profile is further
linked to a Process Foundation profile. The Process Foundation profile is
represented by a suitable business data model and one or more connected Process
Configuration profiles containing the business processes.
When you change a classification at any point within a business process, the
following logic is processed:
1. The corresponding inbound channel and its connected registration type is

determined.
2. Document types that are maintained as classification document types in the
scenario classification (see “Assigning document types to classifications”
on page 57) are determined as classification options.
For Information Extraction Service, document types are mandatory.
If you do not set document types for Business Center Capture integration, all
document types that are defined for the combination of channel and registration
type are determined as classification options.
3. ArchiveLink connection entries are adjusted, or a re-archiving is run.
4. The processing impact is determined. This means it is checked if the
classification change leads to one of the following results.
• a switch of the Scenario Classification/Process Configuration profile (business

scenario change)
• only a switch of the connected Process Configuration profile
Note: Only inbound channels based on the registration types Early Archiving,
Incoming Mail and Custom/Others are supported for classification. The reason
for this is that only these channels can provide a Business Center Capture or
Information Extraction integration.

14.2. Processing impacts
Figure 14-2: “Processing impacts” on page 475 shows the connection between the
different involved components and the processing impacts that are considered when
technically handling a classification change:
Figure 14-2: Processing impacts
Processing Impact A: Switch characteristic configuration

A classification change does not lead to a change of the business scenario and/or
the connected Process Configuration profile. You can use the characteristic
configuration to fulfill different processing requirements by maintaining
classification document types as characteristic values. For more information, see
“Configuring characteristics” on page 208.
Processing Impact B: Switch Process Configuration profile

A classification change does not lead to a change of the business scenario but
requires changing the connected Process Configuration profile. A process restart
is run. During the process restart, a redetermination of the Process
Configuration profile takes place. You can use the classification document types
as dynamic determination criteria. For more information, see “Profile
assignment” on page 223.
Processing Impact C (business scenario change): Finish process and restart

inbound processing
A classification change leads to a change of the business scenario itself. The
current process is set to obsolete and the inbound processing is restarted. During
inbound processing, the capture steps are performed again. The new scenario
classification is evaluated. The linked Process Foundation profile is used to

determine a connected Process Configuration profile. This offers a suitable

business process to fulfill the processing requirements.
14.3 Classification integration

Integrating classification into business processes uses some predefined configuration
settings and ABAP classes.
Workplace integration
Using the /OTX/PF31_CL_ACTION_CLASSI class, define a standard toolbar
button action for work object types where a classification should be available if it
is not already defined.
Processing screen integration

Assign the predefined action ACT_CLASSI to SAP GUI process steps and roles
where a classification should be available if it is not already assigned. If the
predefined action ACT_CLASSI is not available in your corresponding Process
Configuration profile, create it as a dialog action using the /OTX/PF41_CL_
ACTION_CLASSI class.
Fiori Task App integration

Assign the predefined action FRM_WP_CLASSI to web process steps and roles
where a classification should be available if it is not already assigned. If the
predefined action FRM_WP_CLASSI is not available in your corresponding Process
Configuration profile, create it as dialog action using the /OTX/PF41_CL_
ACTION_CLASSI_EXT class.
14.4 BAdI /OTX/PF40_CLASSIFICATION

The /OTX/PF40_CLASSIFICATION BAdI implements the /OTX/PF40_IF_BADI_
CLASSI interface. The following interface method is available:
CHANGE_CLASSI_OPTIONS
This method allows to change the proposed classification options. It is called when
processing the classification action from the SAP GUI processing screen, the SAP
GUI workplace, or the Fiori Task App.

PIS_CLASSI_CURRENT Importing Current Classification
PCT_CLASSI_OPTIONS Changing Classification options
Structure of PCT_CLASSI_OPTIONS:

14.4. BAdI /OTX/PF40_CLASSIFICATION

CLASSI_ID Classification option ID
CLASSI_DESC Classification description

Chapter 15
Troubleshooting
15.1 Fiori Monitoring and Analytics reports

You cannot use the delivered OData query if you create Analytical reports with SAP
S/4HANA backend with SAP_BW below SAP_BW 751 SP4. This is caused by
limitations of prior SAP S/4HANA versions. The workarounds are described here.
15.1.1 Backend SAP S/4HANA with SAP_BW below 751 SP4

You cannot use the delivered OData query if your SAP S/4HANA backend system
has a SAP_BW version below 751 SP4. The workaround is described here.
To create a custom CDS view in the Z namespace:
1. In ADT (ABAP Development Tool) in Eclipse, copy the OpenText CDS view
and its metadata extension to a package with Z namespace.
2. Activate the custom CDS view.

Custom CDS view is activated and OData is created.
SADL automatically generates a class with the prefix ZCL_ in the package to
which the custom CDS view is copied.
3. In the generated class with the prefix ZCL_, search for method DEFINE and
redefine it.
4. In the redefined method, insert the following code lines, replace the entity name
in variable iv_entity_name with the custom entity name which ends with
“Parameters”:
DATA: lo_entity_type TYPE REF TO /iwbep/if_mgw_odata_entity_typ,
lo_property TYPE REF TO /iwbep/cl_mgw_odata_property,
lo_annotation TYPE REF TO /iwbep/if_mgw_odata_annotation.
super->define( ). "Ensure you call the parent metadata
lo_entity_type = model-
>get_entity_type( iv_entity_name = 'ZOTX_PS02H_ALL_PROC_QUERYParameters').
lo_property ?= lo_entity_type-
>get_property( iv_property_name = 'P_FromDate').
CALL METHOD lo_property->/iwbep/if_mgw_odata_annotatabl~create_annotation
EXPORTING
iv_annotation_namespace = /iwbep/if_mgw_med_odata_types=>gc_sap_namespace

Chapter 15 Troubleshooting
RECEIVING ro_annotation = lo_annotation.
lo_annotation->add( iv_key = 'display-format' iv_value = 'Date' ).
lo_annotation->add( iv_key = 'label' iv_value = 'From Date' ).
5. Activate the method.

You must redo the step after each activation of the custom CDS view.
6. Activate the service on the backend system. For more information, see
“Activating services on the backend system” on page 460.
To manually change the local annotations for OData created from CDS:
In case the used OData is created for the CDS view in the Z namespace, instead of
Adding Local Annotations, do the following manual changes in the local
annotations file:
1. For OData with input parameters, for example the OData for Sales orders, keep
the default values for the parameters:
a. Navigate to /webapp/annotations.
b. Double-click the local annotations file annothations.xml.
c. In the annotation modeler, click the Select Targets button.
d. Select all entity types which contain the word parameters at the end.
e. In Properties select all parameters that do not contain the word text:
• P_ExchangeRateType,
• P_DisplayCurrency,
• P_FromDate
f. Click OK.
g. Check that the default values are set for all parameters:
In the Local Annotations of the different properties, add the expression
type and value.
Properties P_ExchangeRateType:
Common.FilterDefaultValue:
• Expression Type: String

• Value: M
Property P_DisplayCurrency:

• Value: USD

15.1. Fiori Monitoring and Analytics reports
Property P_FromDate:
• Expression Type: DateValue.

Date that is appropriate for your purpose
2. If you want to provide virtual filters in the report, do the following changes:
a. Navigate to /webapp/annotations.
b. Double-click the local annotations file annothations.xml.
c. In the annotation modeler, click the Select Targets button.
d. Select all entity types which contain the word result at the end.
e. In the Properties list, select the properties, that are used for virtual filters:
• ChannelID
• StartCanendarYear
• ProcessFinished
f. Click OK.
g. In the annotation modeler, set the default qualifier in the ValueList of each
property, that is used for virutal filters:
i. In the Local Annotations node add the Common.ValueList subnode.

ii. For the CollectionPath node enter:

• Value :: The Entity with ending Results. For example,
xOTXxPS02H_ALL_PROC_QUERYResults.
iii. In the Common.ValueList node add the

PresentationVariantQualifier subnode.
iv. For the PresentationVariantQualifier subnode enter:

• Value :: For details, see data in Virtual Filter row in the Technical
Details table of your solution - OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide for Solutions Beyond Invoice
(BOCP200400-CCS).
3. Click Save.
4. Optional Click Run to test the report.

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 Solution

Preconfigured business scenario that ensures a fast implementation phase. The
following solutions are available: Solution for Incoming Sales Orders, Solution for
Incoming Quotations, Solution for Incoming Delivery Notes, Solution for
Incoming Order Confirmations, Solution for Incoming Remittance Advices,
Solution for Incoming HR Documents, Monitor for Purchase Orders / Purchase
Requisitions.
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.

Glossary
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.
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.
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. VIM is tightly integrated with Business
Center. For example, VIM uses the Business Center Inbound Configuration
mandatorily and provides a couple of Fiori apps that are based on Business
Center.
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.

OpenText Vendor Invoice Management for SAP Solutions 20.4 - Configuration Guide for Foundation English (BOCP200400-CGD-EN-06) (1)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Vendor Invoice Management for SAP Solutions 20.4 - Configuration Guide for Foundation English (BOCP200400-CGD-EN-06) (1)

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

for SAP® Solutions

Configuration Guide for Foundation

This guide describes the general configuration of the

The components of Vendor Invoice Management include

Open Text Corporation

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

Copyright © 2021 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

2 Basic configuration ................................................................. 13

3 General settings ...................................................................... 19

4 Inbound Configuration ............................................................ 51

5 Capture Integration ................................................................. 97

6 Process Foundation .............................................................. 161

BOCP200400-CGD-EN-06 Configuration Guide for Foundation iii

6.4 Business data model assignment ................................................... 173

7 Process Configuration .......................................................... 175

8 Workplace Configuration ...................................................... 227

9 Fiori Task App ........................................................................ 269

10 Fiori Task App running scenarios ....................................... 449

11 Fiori Monitoring and Analytics reports ............................... 459

12 Accessing archived documents using a proxy service ..... 467

13 Useful methods ...................................................................... 469

iv OpenText™ Vendor Invoice Management for SAP® Solutions BOCP200400-CGD-EN-06

13.4 /OTX/PF00_CL_UTILITIES=>TABLE_DATA_UNPACK ................... 469

14 Document classification ....................................................... 471

15 Troubleshooting .................................................................... 479

GLS Glossary 483

BOCP200400-CGD-EN-06 Configuration Guide for Foundation v

About Vendor Invoice Management for SAP

VIM automates the processing of incoming documents into SAP.

Document-centric business processes like the processing of incoming invoices from

For managers VIM offers a comprehensive suite of operational and analytical

VIM includes the following solutions:

• Procure to Pay Solutions

• Order to Cash Solutions

Each solution consists of a best practice implementation for a specific document

BOCP200400-CGD-EN-06 Configuration Guide for Foundation 7

The VIM Foundation consists of the following components:

VIM requires an ArchiveLink-compliant SAP-certified content repository for the

8 OpenText™ Vendor Invoice Management for SAP® Solutions BOCP200400-CGD-EN-06

1.1 Architectural Overview

Figure 1-1: Technical system landscape

BOCP200400-CGD-EN-06 Configuration Guide for Foundation 9

1.2 About this document

To learn about the administration tasks of Vendor Invoice Management is designed,

1.2.1 Target audience

• SAP Basis Administrators

1.2.2 Further information sources

10 OpenText™ Vendor Invoice Management for SAP® Solutions BOCP200400-CGD-EN-06

For the particular solutions, guides are available on OpenText My Support.

Release Notes Release Notes describe:

• The software supported by the product

BOCP200400-CGD-EN-06 Configuration Guide for Foundation 11

2.1 Activating BC sets

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

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

BOCP200400-CGD-EN-06 Configuration Guide for Foundation 13

• /OTX/PF00_BASE_006 for the OpenText Process Base.

2.2 Configuring authorization

• Workplace Configuration: Section 8.4 “Authorization objects” in OpenText Vendor

Authority Description Usage

14 OpenText™ Vendor Invoice Management for SAP® Solutions BOCP200400-CGD-EN-06

Authority Description Usage