Kofax Process Director 7.9 Configuration Guide

PROCESS DIRECTOR

Configuration Guide

Version: 7.5

Date: 2018-11-16

Kofax is a trademark of Kofax, Inc., registered in the U.S. and/or other countries. All other trademarks are the property of

their respective owners. No part of this publication may be reproduced, stored, or transmitted in any form without the

prior written permission of Kofax.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

3

Table of Contents

Document-driven process types ................................................................................................................ 5

Request-driven process types ................................................................................................................... 5

Get your system up and running ............................................................................................................... 7

Create an RFC user for the Web Application ............................................................................................ 7

Open the IMG ............................................................................................................................................ 7

Connect to an archive ................................................................................................................................ 8

Manage licenses ...................................................................................................................................... 12

Configure the Worklist ............................................................................................................................. 21

Manage users and authorizations ........................................................................................................... 31

Configure rules ........................................................................................................................................ 39

Configure workflows ................................................................................................................................ 50

Map external data .................................................................................................................................... 65

Archiving .................................................................................................................................................. 68

Additional configuration tasks ................................................................................................................ 73

Customize fields and layout..................................................................................................................... 73

Customize message texts ....................................................................................................................... 89

Configure attachments ............................................................................................................................ 90

Enable upload from external files ............................................................................................................ 98

Define configuration criteria ................................................................................................................... 103

Configure rejection reasons................................................................................................................... 103

Configure system messages ................................................................................................................. 105

Configure posting .................................................................................................................................. 106

Configure document splitting ................................................................................................................. 107

Customize actions ................................................................................................................................. 110

Process type-specific configuration tasks ........................................................................................... 111

Accounts Receivable ............................................................................................................................. 111

Customer Orders ................................................................................................................................... 111

Electronic Bank Statements .................................................................................................................. 112

Financial Postings ................................................................................................................................. 112

Generic Archiving .................................................................................................................................. 115

Goods Receipts ..................................................................................................................................... 116

Payment Approvals ............................................................................................................................... 116

Requisitions ........................................................................................................................................... 118

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

4

IMG reference .......................................................................................................................................... 119

Settings .................................................................................................................................................. 119

Payment transaction filters .................................................................................................................... 122

Initial settings ......................................................................................................................................... 123

Additional settings ................................................................................................................................. 163

Change system settings ........................................................................................................................ 168

User exits / BAdIs .................................................................................................................................. 209

Catalog settings ..................................................................................................................................... 236

Financial Posting specific settings ......................................................................................................... 237

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

5

About PROCESS DIRECTOR

PROCESS DIRECTOR is a software solution that runs inside SAP and in a web browser. It can create,

receive and process different types of business documents, improving your ability to optimize document

or request driven processes in SAP.

PROCESS DIRECTOR includes:

 The generic PROCESS DIRECTOR core services (workflows, user management, process logging,

archiving, data versioning and database persistence)

 A number of built-in process types, that is, business document types and all of the process-specific

business logic for handling them

By consolidating the handling all of these documents and requests onto a unified platform, PROCESS

DIRECTOR provides an easy user experience for what is often a difficult process in SAP standard.

The easy to use web browser interface is tightly integrated with the SAP based application and provides a

single point of entry and full transparency for all parties involved in a process.

PROCESS DIRECTOR’s single document ledger and flexible workflow capability offer better control and

visibility while seamlessly integrating with the familiar SAP interface.

Document-driven process types

Document-driven processes are initiated by the need to process existing documents, usually from

external sources. Examples of such documents are delivery notes, sales orders, payment advices, etc.

PROCESS DIRECTOR offers these document-driven process types:

 Accounts Payable

 Customer Orders

 Electronic Bank Statements

 Generic Archiving

 Goods Receipts (can also be implemented as a request-driven process)

 Order Confirmations

 Payment Advices

Request-driven process types

Request-driven processes arise from the need to process requests for action, usually from internal

sources. Examples of such requests are purchase requisitions, changes to master data, and corrections

to FI postings.

PROCESS DIRECTOR provides the following standard request-driven process types.

 Financial Postings

 Fixed Asset Postings:

 Asset Acquisition

 Asset Retirement

 Asset Transfer

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

6

 Goods Receipts. You can also implement Goods Receipts as a document-driven process.

 Invoice Block and Cancelation

 Master Data Maintenance:

 Assets

 Cost centers

 Customers

 G/L accounts

 Profit centers

 Vendors

 Payment Approvals

 Requisitions

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

7

Get your system up and running

Create an RFC user for the Web Application

All communication between SAP and the PROCESS DIRECTOR Web Application takes place via an

RFC user. You must create this RFC user in SAP and assign to this user authorizations for all activities

that the Web Application may need to perform. In particular, the RFC user must have authorization to

perform RFC calls for function group ARFC.

You only need to perform these steps if you are installing the PROCESS DIRECTOR Web Application.

To create an RFC user for the Web Application, complete the following steps.

1. In transaction SU01, create an RFC user (naming suggestion: PDWA_USER ) with Logon data >

User Type System.

If you are configuring the RFC user in a development or test system, it is recommended to set Logon

data > User Type to Dialog, otherwise RFC cannot be debugged.

2. Set up the appropriate authorizations for the RFC user. For example, if you are using Requisitions,

set up the authorizations required to create an SAP purchase order.

3. Set Defaults > Spool Control > OutputDevice to a properly configured output device. Which device

to use depends on the customer system and requirements.

Open the IMG

Each process type in PROCESS DIRECTOR has its own IMG. Most process types have a "standard"

IMG, which is a simplified version of the IMG that provides access to the most common configuration

activities. All process types have an "expert" IMG that provides advanced functionality. In general, only

expert users will use the expert IMG.

Note: You perform most of the configuration for Accounts Payable in the /COCKPIT/CI transaction. See

the PROCESS DIRECTOR Accounts Payable Configuration Guide for more information.

To open the IMG for a process type, complete the following steps.

1. Go to transaction /EBY/PDBOC.

Note: When entering PROCESS DIRECTOR transactions, you must add /N as a prefix to the

transaction, even from the SAP Easy Access menu. For example, enter /N/EBY/PDBOC.

2. Select the process type.

3. Optional. Clear the Expert configuration check box if you want to use the standard IMG (if

available).

4. Click the Execute button. A license check is performed.

Note: If the process type you selected does not have a valid license, a warning message is displayed

before the customizing tree is opened.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

8

You can directly access the IMG for the following process types with these transaction codes.

Process type

Standard IMG

Expert IMG

Requisitions

/EBY/PDPOC

/EBY/PDPOCE

Customer Orders

/EBY/PDSOC

/EBY/PDSOCE

Goods Receipts

/EBY/PDDNC

/EBY/PDDNCE

Financial Postings

/EBY/PDFIC

/EBY/PDFICE

Accounts Receivable

/EBY/PDPAC

/EBY/PDPACE

Payment Approvals

/EBY/PDPRC

/EBY/PDPRCE

Order Confirmations

/EBY/PDORC

/EBY/PDORCE

Connect to an archive

Define a content repository

Customer implementations usually require that PROCESS DIRECTOR business objects are archived, so

you must define a content repository for the archived objects. You can also use an existing content

repository.

To define a content repository, complete the following steps.

1. Go to transaction OAC0.

2. In change mode, click the Create button.

3. Define a new content repository as per customer specification.

4. Click Save.

Add archiving document types

Add the archiving documents types that you will use with PROCESS DIRECTOR.

To add archiving document types, complete the following steps.

1. Go to transaction OAC2.

2. In change mode, add a new entry.

3. Add your document types.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

9

4. Click Save.

Example

Doc. type

Long name

Doc. class

ZEPD_DOC

PROCESS DIRECTOR MS Word document

DOC

ZEPD_HTML

PROCESS DIRECTOR HTML document

HTM

ZEPD_JPG

PROCESS DIRECTOR JPG document

JPG

ZEPD_NOTES

PROCESS DIRECTOR notes & workflow

PDF

ZEPD_PDF

PROCESS DIRECTOR PDF document

PDF

ZEPD_TIF

PROCESS DIRECTOR scanned document

TIF

ZEPD_TXT

PROCESS DIRECTOR TXT document

TXT

ZEPD_XLS

PROCESS DIRECTOR MS Excel document

XLS

Note: The italicized Doc. type entries are only naming suggestions. The actual names to use may

depend on customer requirements.

Add archiving links

Create links between your archiving document types and the PROCESS DIRECTOR business objects.

To add archiving links, complete the following steps.

1. Go to transaction OAC3.

2. In change mode, add a new entry.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

10

3. Add these new entries for each process type you want to use, then save your changes.

ObjectType

Doc. Type

S

Cont. Rep.

ID

Relationship

Retent.

Period

Process type's SAP

object type (for

example /EBY/PDPO

for PO Requisition)

ZEPD_DOC

X

customer-

specific

TOA01

customer-

specific

Process type's SAP

object type (for

example /EBY/PDPO

for PO Requisition)

ZEPD_HTML

X

customer-

specific

TOA01

customer-

specific

Process type's SAP

object type (for

example /EBY/PDPO

for PO Requisition)

ZEPD_JPG

X

customer-

specific

TOA01

customer-

specific

Process type's SAP

object type (for

example /EBY/PDPO

for PO Requisition)

ZEPD_PDF

X

customer-

specific

TOA01

customer-

specific

Process type's SAP

object type (for

example /EBY/PDPO

for PO Requisition)

ZEPD_XLS

X

customer-

specific

TOA01

customer-

specific

Note: Make sure that the same content repository ID is assigned to the PROCESS DIRECTOR object

type and its corresponding SAP business object type. For example, /EBY/PDPO should have the same

content repository ID as BUS2012 (Purchase order) and BUS2105 (Purchase requisition). This ensures

that the attachments of the PROCESS DIRECTOR document can be viewed in the SAP document.

Note: The italicized Doc. type entries are only naming suggestions — the actual names to use may

depend on customer requirements.

Note: If using the Web Application, only the Doc. types configured here will be allowed for attachment

upload for a given process type. The allowable document types can be further restricted in the Web

Application configuration file mimetypes.properties.

Note: In order to add and view attachments, users must have the authorization object S_WFAR_OBJ with

activities 01 Create and 03 Display.

Set up the archive device

PROCESS DIRECTOR uses a Smart Form to create the workflow log. To archive Smart Form output in

SAP, you must define an archive device in spool administration (transaction SPAD) and define a device

type for this archive device. See the SAP ArchiveLink documentation for detailed information.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

11

In the standard R/3 System, the archive device ARCH of type ARCHIXOS is the default for storing with

SAP ArchiveLink. If you use this standard archive device, you should not need to make any changes.

If the standard archive device is not configured, or if you use an archive device with a different name, you

need to ensure that the device and the system profile parameters are correctly set up. As with all

installation tasks, this is usually done by the SAP Basis Team, who have the required permissions.

To create the archive device, complete the following steps,

1. Go to transaction SPAD.

2. Click the Output devices Display button.

3. In change mode, click the Create button.

4. Enter the following settings and save your changes.

Field

Description

Output

device

Enter a name for the device.

Short name

Enter a short name for the device. If you use the default short name ARCH, you do not

have to configure the system profile parameters.

Device Attributes tab

Device Type

Select the appropriate device type for archiving, for example, ARCHLINK , ARCHIXOS

or ARCHUTF8.

Spool Server

Select a spool server.

Device class

Select Archiving program.

Location

Enter text to identify the device, for example, Virtual printer for archiving.

Access Method tab

Host Spool

Access

Method

Select Archiving device.

To set the system profile parameters, complete the following steps.

1. Go to transaction RZ10.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

12

2. In the Profile field, select the appropriate system profile.

3. Select Extended maintenance and click the Change button.

4. Click the Create parameter button.

5. In the Parameter name field, enter rspo/default_archiver.

6. In the Parameter val. field, enter the short name of your archive device.

7. Click Save.

Manage licenses

About licenses

Licenses are available for production and non-production clients and may have an expiry date (the

license is only valid until a specified date) or a volume limit (the license is only valid for a specified

number of documents).

You can activate licenses per system or per client. If you do not specify a client, the license is valid for all

clients in the system.

License types

The following types of license are available. Volume limits are annual limits, which are reset every year on

1 January (only for licenses with no expiry date).

License type

Client type

Expiry date

Volume limit

1. Demo

Non-production only

No

2. Test

Non-production only

Yes

No

3a. Normal/Full

Production

No

Yes

3b. Normal/Full

Production

Yes

Process type licenses

You can obtain licenses for the following standard PROCESS DIRECTOR process types. You need a

license for each standard PROCESS DIRECTOR process type that you want to use.

Process type

ID

Notes

Accounts Payable

IV

For the Accounts Payable process type, you need a

PROCESS DIRECTOR Accounts Payable (formerly INVOICE

COCKPIT Suite) license. A separate license exists for

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

13

PROCESS DIRECTOR Accounts Payable and its associated

products.

 WORK CYCLE

 EDI COCKPIT

 Email-based Approval (formerly MOBILE APPROVAL)

 INFO MAIL

 WEB BOARD

 Ariba integration for PROCESS DIRECTOR Accounts Payable

(Activation license only)

Customer Orders

SO

Electronic Bank

Statements

ES

Financial Postings

FI

This license includes G/L Account Postings (FI) and FI

Customer Postings (FIC).

Fixed Asset

Postings

ASSET

This license includes the following types of fixed asset

postings.

 Asset Acquisition (AA)

 Asset Retirement (AR)

 Asset Transfer (AT)

Generic archiving

ARCH_BUS

Goods Receipts

DN

Invoice Block and

Cancelation

IB

Master Data

Maintenance

MD

This license includes the following types of master data.

 Cost Center Maintenance (MD_COSTCTR)

 Profit Center Maintenance (MD_PRCTR)

 Vendor Master Maintenance (MD_VENDOMA)

 Customer Master Maintenance (MD_CUSTMA)

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

14

 G/L Account Maintenance (MD_GLACC)

 Asset Master Maintenance (MD_ASSET)

Order

Confirmations

OR

Payment Advices

PA

This license works for Electronic Bank Statements too. A

separate ES license is not required.

Payment

Approvals

PR

Requisitions

PO

Umbrella Solution

UM

Activation license only. The Synchronizer program checks this

license.

Workflows not

assigned to a

specific process

WC

See Workflow licenses.

Customer-defined

process types

YZ

Customer-defined process types require only a single license

for all customer-defined process types handled on a single

PROCESS DIRECTOR installation.

ZUGFeRD

ZUGFERD

Activation license only.

Workflow licenses

You can activate workflow licenses per process type or as a separate global license independent of the

process types you use. An exception is Accounts Payable. Using workflows with Accounts Payable

requires a license for the WORK CYCLE.

 In the case of a workflow license for a specific process type, the volume limit for workflows is usually

equal to the document volume limit for the process type. However, you can specify a different volume

limit for the workflow than for the process type. For example, for requisitions (PO), you can specify a

document volume limit of 10,000, but a workflow volume limit of only 8,000. In this case, you can

create 10,000 requisitions, but you can only send 8,000 to a workflow.

 In the case of a global workflow license (WC), the volume limit for the workflow license applies to all

process types you use.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

15

 You can combine a global workflow license with process-specific licenses. In this case, the global

workflow volume limit applies only to those process types for which you have not activated a process-

specific workflow license.

License counters

License counters count the number of documents that are processed in PROCESS DIRECTOR, but they

are only incremented on production clients.

PROCESS DIRECTOR

For PROCESS DIRECTOR, counters are incremented in the following cases:

 A new document is created in PROCESS DIRECTOR, either via manual entry in the SAP GUI or the

Web Application or via transfer from external sources.

 A document is sent to a workflow for the first time. If the same document is sent to other workflows, or

is sent to the same workflow a second time, the counter is not incremented.

PROCESS DIRECTOR Accounts Payable

The following table describes how counters are implemented in the PROCESS DIRECTOR Accounts

Payable applications:

Application

Counter

Counters checked

Counter type

PROCESS

DIRECTOR

Accounts

Payable

Yes

PROCESS

DIRECTOR Accounts

Payable

Every document, except IDocs,

transported into PROCESS DIRECTOR

Accounts Payable is counted.

PROCESS

DIRECTOR

Accounts

Payable

Umbrella System

No

Total count of

PROCESS

DIRECTOR Accounts

Payable and EDI

COCKPIT

Activation license only.

EDI COCKPIT

Yes

EDI COCKPIT

Every IDoc transferred from EDI

COCKPIT to PROCESS DIRECTOR

Accounts Payable.

The PROCESS DIRECTOR Accounts

Payable counter will not increment.

PROCESS

DIRECTOR

Accounts

Payable & EDI

COCKPIT

Yes

PROCESS

DIRECTOR Accounts

Payable and EDI

COCKPIT

Every document transferred to

PROCESS DIRECTOR Accounts

Payable, including IDocs.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

16

WORK CYCLE

Yes

WORK CYCLE

The WORK CYCLE counter increments

the first time a document is sent from

PROCESS DIRECTOR Accounts

Payable to a WORK CYCLE workflow. If

you send the same document to a

second workflow, the counter does not

increment.

Invoices created in WORK CYCLE are

incremented in the PROCESS

DIRECTOR Accounts Payable counter.

Email-based

Approval

(formerly

MOBILE

APPROVAL)

No

Total count of

PROCESS

DIRECTOR Accounts

Payable and EDI

COCKPIT

Activation license only.

WEB BOARD

No

Total count of

PROCESS

DIRECTOR Accounts

Payable and EDI

COCKPIT

Activation license only.

Invoices created in WEB BOARD are

counted as PROCESS DIRECTOR

Accounts Payable documents.

INFO MAIL

No

Total count of

PROCESS

DIRECTOR Accounts

Payable and EDI

COCKPIT

Activation license only.

ANALYZER

No

Total count of

PROCESS

DIRECTOR Accounts

Payable and EDI

COCKPIT

Activation license only.

REPORTER

No

Total count of

PROCESS

DIRECTOR Accounts

Payable and EDI

COCKPIT

Activation license only.

PERFORMANCE

ANALYTICS

No

None. The system only

checks if a valid

license exists for

PROCESS

DIRECTOR Accounts

Payable.

Activation license only.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

17

Note: In the case of licenses with no expiry date, the license counters are reset every year on 1st January

to the number of purchased documents. You can view the counters for previous years by clicking the

Display counters for all years button in /EBY/PD_LICENSES.

License validity

When a license for a process type has expired or the volume limit is exceeded, users cannot create new

documents of this type in the SAP GUI and the Web Application. Transfer of documents from external

sources is not interrupted, but a separate counter is incremented for these documents. When you renew

the process type license, this separate counter is added to the license counter. For example, after the

Customer Orders license has expired, 100 Customer Order documents are transferred to PROCESS

DIRECTOR. You then renew the Customer Order license and 50 new Customer Orders are transferred.

The total license count for Customer Orders is now 150.

When a workflow license volume limit is exceeded, no new workflows can be started. However, workflow

processing is still possible for all documents that have already been sent to a workflow. For example, if a

document is recalled from a workflow and then the workflow volume license is exceeded, it is still possible

to send this document to a workflow again.

Note: In the case of licenses with no expiry date, the volume limits are annual limits, which are reset

every year on 1 January.

You can only have one active license installed per process type on one system. The license validity

mechanism behaves differently depending on whether a production or non-production client is used.

 Production client

You can only activate normal licenses on a production client. Demo or test clients running on the

same system use the normal license, because only one license can be valid on an SAP system.

PROCESS DIRECTOR does not increment license counters in these clients.

The license expires when it exceeds the production client volume limit or passes the expiry date. If

the production client license expires, PROCESS DIRECTOR will not also not function on the demo

and test clients.

 Non-production clients

You can activate normal, demo and test licenses on non-production clients.

If a normal license is installed, the volume processed on the production client is taken into account. If

a test license is installed, the expiration date on the production client is taken into account. If a demo

license is installed, no validity and expiration date are used.

License threshold warnings

Fifteen days before the license expiration date, or when the license counter reaches 90%, 95% and 99%

of the volume limit, threshold warning messages are displayed when PROCESS DIRECTOR is started.

Threshold warning messages are not displayed in the Web Application.

To suppress the display of these messages in SAP, click No at the bottom of the dialog. The messages

will not be displayed again until the next threshold is reached.

Note: The current license counter value is always displayed at logon. For this reason, values not equal to

90%, 95% or 99% may be displayed if further documents have been processed between the threshold

being reached and the user logging on.

Threshold warning messages for WORK CYCLE and for applications that do not have a direct view in the

SAP GUI (EDI COCKPIT, WEB BOARD and INFO MAIL) are displayed in PROCESS

DIRECTOR Accounts Payable. Threshold warnings are not displayed in the Web Application or WORK

CYCLE.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

18

Once the license counter reaches 100%, PROCESS DIRECTOR will stop working (cannot be started)

and new workflows cannot be started. However, workflow processors can continue to process their

current documents.

Define license threshold warning recipients

You can define license threshold warnings only to those users who are responsible for ordering the

licenses, rather than to each user who starts PROCESS DIRECTOR in the SAP GUI.

To define threshold warning recipients, complete the following steps.

1. In the IMG, select Initial settings > Licenses > Manage license keys and activate process types

(/EBY/PD_LICENSES).

2. Click the License threshold warning recipients button.

3. In change mode, add a new entry.

4. Enter the ID of each processor to whom license threshold warnings should be displayed. The

Complete name field is filled when you press ENTER or save.

5. Click Save.

Obtain and install licenses

Obtain a license

To order a license, you must provide your SAP installation number and SAP System ID. You can find this

information by selecting the menu item System > Status in your SAP system.

You need the following information.

 SAP System data > Installation number

 Database data > Name

 Usage data > Client (only required if the license should be restricted to this client)

When you have placed your order, you will receive a license file in .TXT format. Your license file contains

the following information.

Field

Description

License key

The license key provided by Lexmark. This encrypted number

validates the license.

SAP Installation Number

The SAP installation number of your system (that you provided to

Lexmark when you ordered the license).

SAP System ID

The SAP system ID of your system (that you provided to Lexmark

when you ordered the license).

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

19

Process type

(not Accounts Payable)

The process type for which the license is valid.

Component ID

(Accounts Payable only)

The PROCESS DIRECTOR Accounts Payable component for which

license is valid:

 C – PROCESS DIRECTOR Accounts Payable

 U – PROCESS DIRECTOR Accounts Payable Umbrella System

 E – EDI COCKPIT

 D – PROCESS DIRECTOR Accounts Payable & EDI COCKPIT

 A – ANALYZER

 W – WORK CYCLE

 I – INFO MAIL

 B – WEB BOARD

 M – Email-based Approval (formerly MOBILE APPROVAL)

 T – TRAVEL EXPENSES

 R – REPORTER

License type

The type of license: Demo, Test or Normal.

Client

The client ID, if the license applies only to a specific client.

Expiration date

The date on which the license expires.

Licensed volume/

Licensed number

The volume limit, that is, the number of documents for which the

license is valid.

Workflow active

(not Accounts Payable)

X indicates that the license includes the use of workflows. If this line

is blank, workflows are not included.

Workflow volume

(not Accounts Payable)

The volume limit for workflows, that is, the number of documents that

can be sent to a workflow.

Notes

 Component ID E: It is possible to run EDI COCKPIT together with PROCESS DIRECTOR Accounts

Payable, with only a license for EDI COCKPIT. Requirements: 1. A valid EDI COCKPIT license. 2.

ReadSoft PROCESS DIRECTOR 7.5 Configuration Guide

20

The sum of the document counters for EDI COCKPIT and PROCESS DIRECTOR Accounts Payable

must not exceed the license volume for EDI COCKPIT.

 Component ID D: The volume is equal to the total documents processed by PROCESS DIRECTOR

Accounts Payable and EDI COCKPIT. Adding this license removes any existing PROCESS

DIRECTOR Accounts Payable and/or EDI COCKPIT licenses.

Install a license

To install a license, PROCESS DIRECTOR must already be installed. There are two ways to install

licenses:

 Enter license information in PROCESS DIRECTOR.

 Transport an existing license from one system to another

Enter license information in PROCESS DIRECTOR

To enter license information in PROCESS DIRECTOR, complete the following steps.

1. Go to /EBY/PD_LICENSES.

For Accounts Payable and its associated products, go to /COCKPIT/C46.

2. In change mode, add a new entry.

3. Enter the license settings. You can find the required information in the license file supplied to you by

ReadSoft.

4. Click Save.

Transport an existing license from one system to another

It is possible for a product component to have more than one license installed on the same machine.

However, only one can be valid at any one time, because only one will match the SAP system (the SAP

Installation Number and SAP System ID [Database Data Name]) it is installed on.

When working on an instance of PROCESS DIRECTOR that you wish to migrate, or transport, from one

system to another, the licenses are included. This means that you can install a normal/full PROCESS

DIRECTOR license in a demo/development system and transport it to the test/QA system, and later to the

normal/production system. The normal license will only be used/valid when it matches the SAP

Installation Number and SAP System ID (Database Data Name) used within the (production) system.

View license information

You can only view license information in the SAP GUI.

To view information about your PROCESS DIRECTOR licenses, complete the following step.

 Go to transaction /EBY/PD_LIC_INFO.

To view information about your PROCESS DIRECTOR Accounts Payable or WORK CYCLE license,

as well as other associated products, complete the following step.

 In PROCESS DIRECTOR or WORK CYCLE, on the Extras menu, select Info, then click the

Licenses tab.

Page is loading ...

Kofax Process Director 7.9 Configuration Guide

Kofax Process Director 7.9 Configuration Guide

Related papers

Other documents