Chapter 5

Process Foundation

This chapter provides details about the Business Center Foundation part 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.

OpenText Business Center for SAP Solutions – Configuration Guide 95

BOCP160301-CGD-EN-01
Chapter 5 Process Foundation

Important
The Process Foundation is reserved for internal use only. Any custom
configurations beside the activities described in this document are not
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
As a prerequisite, the SAP Business Workflow engine must be configured to
run processes based on Process Foundation. Additionally, the following
tasks must be maintained as general tasks in the PFTC transaction:

• Workflow Template 00297300

• Workflow Template 00297330
• Standard Task 00297316
• Standard Task 00297303

The Process Foundation allows controlling running workflow instances from

external applications using some special event type linkages, which must be
maintained in the SWETYPV transaction:

Object Business Object Type

Category
Object Type /OTX/PF04E
Event FINISH_PROCESS
Receiver Type /OTX/PF04
Receiver Call Function Module

96 OpenText Business Center for SAP Solutions – Configuration Guide

BOCP160301-CGD-EN-01
 5.1. Basic Settings

Receiver /OTX/PF02_EVENT_RECEIVER
Function
Module

Object Business Object Type

Category
Object Type /OTX/PF04E
Event RUN_ASSIGNMENT
Receiver Type /OTX/PF04
Receiver Call Function Module
Receiver /OTX/PF02_EVENT_RECEIVER
Function
Module

5.1 Basic Settings

In this step, you configure basic settings for the Process Foundation.

To configure basic settings:

1. Run the /n/OTX/PF00_IMG transaction and navigate to Process Foundation >

Basic Settings.

2. In the Basic Settings Overview screen, configure basic settings, using the
following parameters.

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
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 106.

OpenText Business Center for SAP Solutions – Configuration Guide 97

BOCP160301-CGD-EN-01
Chapter 5 Process Foundation

5.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.

5.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:

1. Run the /n/OTX/PF00_IMG transaction and navigate to Process Foundation >

Data Model.

2. In the Data Model Configuration Overview screen, define the data model
using the following parameters:

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.

98 OpenText Business Center for SAP Solutions – Configuration Guide

BOCP160301-CGD-EN-01
 5.2. Data model configuration

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.

5.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 5-1: Mandatory key fields for the header table

Fieldname Data Element

MANDT MANDT
PROJECT_ID /OTX/PF02_E_PROJECT_ID
PLKEY /OTX/PF02_E_PLKEY

Mandatory include structures for the header table

• /OTX/PF02_S_PLH_DATA
• /OTX/PF04_S_BCF_DATA

Table 5-2: Mandatory key fields for the item table

Fieldname Data Element

MANDT MANDT
PROJECT_ID /OTX/PF02_E_PROJECT_ID
PLKEY /OTX/PF02_E_PLKEY
ITEM_NR /OTX/PF02_E_ITEM_NR

Table 5-3: Mandatory non-key fields for the item table

Fieldname Data Element

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 170.

OpenText Business Center for SAP Solutions – Configuration Guide 99

BOCP160301-CGD-EN-01
Chapter 5 Process Foundation

To define levels:

1. In the Data Model Configuration Overview screen (see “Defining a data

model” on page 98), mark an entry and 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.

5.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 99), mark an entry
and 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.

100 OpenText Business Center for SAP Solutions – Configuration Guide

BOCP160301-CGD-EN-01
 5.2. Data model configuration

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 Solution Accelerators).

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.

OpenText Business Center for SAP Solutions – Configuration Guide 101

BOCP160301-CGD-EN-01
Chapter 5 Process Foundation

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 5-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.

5.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 intermediately to the relevant business process ledger
header and item table.

1. In the Data Model Configuration Overview screen (see “Defining a data

model” on page 98), mark an entry and 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

102 OpenText Business Center for SAP Solutions – Configuration Guide

BOCP160301-CGD-EN-01
 5.2. Data model configuration

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.

Parameter Parameter type Description

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.

Parameter Parameter type Description

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
PET_RETURN Exporting Return parameters in error case

PROCESS_MAPPING
This method is used for process mapping. It is called inside mapping class.

Parameter Parameter type Description

PIT_EXTDATA Importing External data values
PI_LVL Importing Data hierarchy level (see “Defining
levels” on page 99)
PI_CURRENCY Importing Currency to map currency fields
PET_RETURN Exporting Return parameters in error case

OpenText Business Center for SAP Solutions – Configuration Guide 103

BOCP160301-CGD-EN-01
Chapter 5 Process Foundation

Parameter Parameter type Description

PET_INTDATA Exporting Mapping result

5.2.5 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 External Data Mapping Overview screen (see “Defining external data
mapping” on page 102), mark an entry and double-click Field Mapping in the
Dialog Structure.
2. In the Field Mapping Overview screen, maintain the field mapping, using the
following parameters.

Data Hierarchy Level

Definition of the hierarchy level to which a data table belongs. The
hierarchy level identifies the corresponding target table (see “Defining
levels” on page 99).
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.

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.

104 OpenText Business Center for SAP Solutions – Configuration Guide

BOCP160301-CGD-EN-01
 5.2. Data model configuration

Constant (fixed value)

A constant value is assigned to the target field. The value is configured
in the Value field (see Value on page 105).

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

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.

5.2.6 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 102).

To assign the mapping channel:

1. In the Data Model Configuration Overview screen (see “Defining a data

model” on page 98), mark an entry and 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 50).

Mapping ID
Enter the unique technical ID which identifies the mapping scenario.

OpenText Business Center for SAP Solutions – Configuration Guide 105

BOCP160301-CGD-EN-01
Chapter 5 Process Foundation

5.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.

To generate a Process Foundation profile:

1. Run the /n/OTX/PF00_IMG transaction and navigate to Process Foundation >

Generate Profiles.

Note: To run this activity, authorization for J_6NPF_ADM is needed. For

more information, see “Authorization objects” on page 184.

2. 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 available in the basic settings
of the Process Foundation. To change this parameter, run the /n/OTX/
PF00_IMG transaction and navigate to Process Foundation > Basic
Settings. When leaving 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 and navigate to Process Foundation >

Profiles.

2. 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.

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.

106 OpenText Business Center for SAP Solutions – Configuration Guide

BOCP160301-CGD-EN-01
 5.4. Business data model assignment

5.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:

1. Run the /n/OTX/PF00_IMG transaction and navigate to Process Foundation >

Profiles.

2. 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.

OpenText Business Center for SAP Solutions – Configuration Guide 107

BOCP160301-CGD-EN-01