ReadSoft PROCESS DIRECTOR

Import and Upgrade Guide

Version: 7.7

Date: 2018-11-20
Legal Notice

© 2018 Kofax. All rights reserved.

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.

2
Table of Contents
Legal Notice...................................................................................................................................................2
Overview........................................................................................................................................................ 5
About ReadSoft PROCESS DIRECTOR transports.......................................................................... 5
Transports for different SAP versions..................................................................................... 5
Contents................................................................................................................................... 5
Location....................................................................................................................................6
Licensing............................................................................................................................................. 6
Web Application..................................................................................................................................7
Upgrading............................................................................................................................................7
Upgrading ReadSoft PROCESS DIRECTOR Accounts Payable............................................7
Upgrading ReadSoft PROCESS DIRECTOR..........................................................................7
Upgrading SAP........................................................................................................................ 9
Import procedure......................................................................................................................................... 10
Implementing prerequisite SAP Notes............................................................................................. 10
Required SAP notes.............................................................................................................. 10
Recommended SAP notes.................................................................................................... 16
Importing the transports................................................................................................................... 19
Service Packs........................................................................................................................ 20
ReadSoft PROCESS DIRECTOR......................................................................................... 21
Languages..............................................................................................................................22
Reading the import log.....................................................................................................................22
Checking the namespaces............................................................................................................... 22
After importing the transports...........................................................................................................22
Executing the load generator................................................................................................ 22
Installing licenses..............................................................................................................................23
Importing and activating indexes for PD AP performance optimization......................................................24
Index types....................................................................................................................................... 24
Type 1.................................................................................................................................... 24
Type 2.................................................................................................................................... 25
Type 3.................................................................................................................................... 25
Prerequisite....................................................................................................................................... 26
Importing indexes into the development system..............................................................................26
Activating indexes.............................................................................................................................26
Space calculation..............................................................................................................................30

3
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Troubleshooting........................................................................................................................................... 32
ReadSoft PROCESS DIRECTOR Accounts Payable...................................................................... 32
Import errors.......................................................................................................................... 32
Other problems...................................................................................................................... 32
ReadSoft PROCESS DIRECTOR.................................................................................................... 32
Import errors.......................................................................................................................... 32
Short dumps...........................................................................................................................32
Other problems...................................................................................................................... 33
Setting the buffer size...................................................................................................................... 34

4
Overview

This document explains how to import the Kofax ReadSoft PROCESS DIRECTOR™ transports into your
SAP system.
• ReadSoft PROCESS DIRECTOR transports. Which ones to use and the download location.
• Tasks to perform when before upgrading from a previous version of ReadSoft PROCESS DIRECTOR.
• Tasks to perform before and after upgrading your SAP system.
• Implementing prerequisite SAP Notes.
• Importing the transport(s).
• Checking the necessary namespace(s).
• Required tasks after importing.
• Troubleshooting information.

About ReadSoft PROCESS DIRECTOR transports

There are two ReadSoft PROCESS DIRECTOR transports:
Product Transport Description
ReadSoft PROCESS PD AP Transport Contains the /COCKPIT/ namespace objects
DIRECTOR Accounts Required for Accounts Payable
Payable™
ReadSoft PROCESS PD Transport Contains the /EBY/ namespace objects
DIRECTOR Required for all the process types
For Accounts Payable, this transport is required in
addition to the PD AP Transport.

Transports for different SAP versions

Kofax delivers SAP release version-independent transports.

Note From ReadSoft PROCESS DIRECTOR 7.4, only versions from SAP ECC6 and higher are
supported, including SAP S/4HANA on-premise releases.

Contents
This table lists the processes and supplementary products that the transports contain.

5
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Transport Contents
PD AP Transport ReadSoft PROCESS DIRECTOR Accounts Payable
ReadSoft PROCESS DIRECTOR WORK CYCLE (SAP parts)
ReadSoft EDI COCKPIT™
ReadSoft Email-based Approval™ (formerly MOBILE APPROVAL) (SAP
parts)
ReadSoft INFO MAIL™ (SAP parts)
ReadSoft REPORTER™ EXTRACTOR
PD Transport Requisitions
Order Confirmations
Goods Receipts
Payment Approvals
Accounts Receivable (formerly Payment Advices)
• Includes Electronic Bank Statements
Customer Orders
Financial Postings
Master Data:
• Customer
• Vendor
• Cost Center
• Profit Center
• GL Account
• Asset
Asset Management:
• Acquisition
• Transfer
• Retirement
Generic Archiving

Location
ReadSoft PROCESS DIRECTOR transports are available for partners and customers on the Kofax E-
Delivery web service.

Licensing
You must order a license from Kofax to activate ReadSoft PROCESS DIRECTOR. Each process type and
supplementary product can only be used if a valid license is activated. For details on installing licenses,
see the following guides in the Product Documentation website at:

https://docshield.kofax.com/Portal/Products/en_US/RSPD/RS_Process_Director.htm
• PROCESS DIRECTOR License Installation Guide

6
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

• PROCESS DIRECTOR Configuration Guide

https://docshield.kofax.com/Portal/Products/en_US/RSPDAP/RS_Process_Director_AP.htm
• PROCESS DIRECTOR Accounts Payable Configuration Guide

Web Application
When installing a new version of ReadSoft PROCESS DIRECTOR or a service pack, we strongly
recommend that you also deploy the latest version of the Web Application with the latest patch.

In general, since ReadSoft PROCESS DIRECTOR 7.4, the Web Application is independent of the SAP
version.

Upgrading
This section lists the tasks that you need to perform when upgrading to ReadSoft PROCESS DIRECTOR
from previous versions.

Note ReadSoft PROCESS DIRECTOR and ReadSoft PROCESS DIRECTOR Accounts Payable can be
upgraded independently of one another, for only all the currently supported versions. Thus, it is possible,
for example, to remain with ReadSoft PROCESS DIRECTOR Accounts Payable 7.5, but upgrade other
processes to 7.7, and vice versa.

Upgrading ReadSoft PROCESS DIRECTOR Accounts Payable

This section lists required tasks when upgrading from old versions. For information on prerequisite tasks
for upgrading from unsupported versions, contact Tech Support.

Note If you are using the EOL solution, ReadSoft ANALYZER, do not upgrade to the 7.6 version as this
will remove the existing ANALYZER package.

Perform this task immediately after importing the transports:

• If you upgrade from ReadSoft PROCESS DIRECTOR 7.5 to a higher version, check the new tax code
determination configuration.

Upgrading ReadSoft PROCESS DIRECTOR

This section lists the required tasks when upgrading from a previous version of ReadSoft PROCESS
DIRECTOR.

Perform these tasks immediately after importing the transports:

• The /EBY/PDBO_CHECK_CUST_PROCESS program lists all the obsolete customizing entries. To identify
the changes required to be made to the configuration, you should always run this custom check for all
the active process types. For example:
• The customization of processes changed slightly in ReadSoft PROCESS DIRECTOR 7.2, with the
result that some customizations are obsolete and must be removed. If you use a version of ReadSoft

7
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

PROCESS DIRECTOR prior to 7.2 and have customized processes, checks, or determinations, you
should run the /EBY/PDBO_CHECK_CUST_PROCESS consistency check program. This program lists
all the obsolete customizing entries that must be removed.

Remove the entries in the appropriate IMG configuration activity. For example, to remove obsolete
determination entries, go to Initial settings > Rules > Determinations and delete the entries
for the corresponding Actions. Similarly, do it for Initial settings > Rules > Checks .

• The workflow start action was modified to allow bulk workflow start with manual assignment.
If custom checks or actions have been configured for workflow start, these must be redefined
after upgrading. In most cases, this involves replacing the WCSTRT10CHECK_DOC action with
WCSTART10CHECK_DOC_, and the WCSTART0CHECK_OWNER action with WCSTART0CHECK_OWNER_.
You can run the /EBY/PDBO_CHECK_CUST_PROCESS consistency check program to list the
customizing entries that must be changed. Refer to RSPDN3026 for more information and detailed
instructions.
• From ReadSoft PROCESS DIRECTOR 7.7, the /EBY/PDVI_TRANSLATE_OLD_MENU program is
available to transition the existing custom menu and toolbar function code settings to the current design
tables.
The /EBY/PDVI_TRANSLATE_OLD_XY_MEN program is also available to transition the standard
configuration containing the customer document types that are based on the XY template. This report
transfers the menu configuration from the old to the new format, which makes it visible in the new
configuration transaction available in the IMG tree.

Note After the transition, the report asks for the transport number a couple of times. Workbench
transports handle the standard settings, like the menu configuration; whereas the customizing
one transfers the information that the menu has been modified. The destination system needs this
information to decide about menu regeneration.

If you are upgrading from a lower version, refer to the corresponding Import Guide and perform the
upgrade in two steps; first from the lower version to the supported one, and then to the latest version.

8
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Upgrading SAP

Before upgrading SAP

For ReadSoft PROCESS DIRECTOR 7.7 and ReadSoft PROCESS DIRECTOR Accounts Payable
7.7, there are no prerequisite tasks that need to be performed in relation to an SAP system upgrade or
Enhancement Pack (EhP) installation.

If you upgrade an SAP S/4HANA version, it is recommended to upgrade to the latest PROCESS
DIRECTOR Service Pack.

After upgrading SAP

After upgrading an SAP installation, perform these tasks in order to ensure the continued smooth running
of ReadSoft PROCESS DIRECTOR.
• Upgrade ReadSoft PROCESS DIRECTOR.
Kofax strongly recommends upgrading to the latest version of ReadSoft PROCESS DIRECTOR before
upgrading an SAP installation. Upgrading ReadSoft PROCESS DIRECTOR will ensure that all the
functionality works properly in the new SAP environment. In particular, when you upgrade from a non-
Unicode to a Unicode system, you must upgrade ReadSoft PROCESS DIRECTOR; otherwise, the
customizing views will not be displayed.
• Check the license validity.
If the SAP installation number and system ID remain the same after the upgrade, the ReadSoft
PROCESS DIRECTOR licenses will work as before and no further action is required.
You need new licenses if:
• The SAP installation number and/or system ID changes.
• Review customer-specific customizations.
All User Exits and BAdIs must be reviewed and tested to confirm that they work correctly with the new
version of SAP. Their compatibility with Unicode and (potentially) SAP S/4HANA must also be checked.
If you are also upgrading to a new version of ReadSoft PROCESS DIRECTOR (recommended), this
review should form a part of the migration plan.
• For information on implementing the relevant SAP notes and hotfixes, see the following links.
• Implementing prerequisite SAP Notes contains details of the relevant SAP notes.
• Troubleshooting contains fixes for various issues that may arise when installing ReadSoft PROCESS
DIRECTOR.

9
Import procedure

Important Before importing the ReadSoft PROCESS DIRECTOR transport requests, ensure that the
prerequisite SAP notes are implemented in your system. Also, check the Upgrading chapter for tasks
that you may need to perform before importing.

Note Most of the referenced SAP Notes are for very old SAP releases and not applicable.

Implementing prerequisite SAP Notes

• Required notes must be applied if the corresponding process type is used; otherwise, the system may
not run.
• Recommended notes are not necessary for the system to run, but fix certain minor bugs or enable
feature enhancements.

Required SAP notes

Required notes for all process types

Required notes for Accounts Payable

Required notes for Customer Orders

Required notes for Financial Postings

Required notes for Master Data Maintenance

Required notes for Requisitions

All processes: Required notes

This list contains the SAP required notes that can be found at https://support.sap.com/home.html.
SAP Note # Issue addressed Comments Affected SAP releases
930742 The ReadSoft PROCESS DIRECTOR ECC 6, no EhP SAP_BASIS 620-640
Worklist configuration transaction uses Fixed with
the new ABAP editor control element SAPKB62060
(AB4 control). SAPKB64018
1078450 When using the HTML viewer, any CR/ ECC 6, no EhP Only SAP_BASIS 620
LF characters coming from a <textarea> Fixed with SAPKB62063
are converted to simple hash signs.

10
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

SAP Note # Issue addressed Comments Affected SAP releases

1243840 In the dynamic selection screen of Only required if the SAP_BASIS 620-640
the ReadSoft PROCESS DIRECTOR selection screen is 700-702 and 710-711
Worklist, selection screen fields with configured. Fixed with
conversion exit (for example, /EBY/
PDBO_THDR-NUMBR with NUMC1) SAPKB62066
result in an error message regarding SAPKB64023
lower value greater if single value is SAPKB70018
used.
SAPKB70103
SAPKB70204
SAPKB71007
SAPKB71101
1539662 The FM Required in ECC 6.0 Systems
ARCHIV_CONNECTION_INSERT Fixed with
terminates with a program error. SAPKB70026
Without this note, the RFC transfer SAPKB70110
function module is likely to terminate SAPKB70209
during execution.
SAPKB71013
SAPKB71108
SAPKB72006
SAPKB73004
SAPKB73102
869218 Import error " Program /EBY/ Required for customers SAP_BASIS
CL_ICIV_DAO==============CP, with a low BASIS SP 610 SAPKB61046
Include /EBY/ level. 620 SAPKB62058
CL_USER_MANAGER==========CU:
Syntax error in line 000150 640 SAPKB64016
The type 'XUPWDSTATE' is unknown." 700 SAPKB70006

Accounts Payable: Required notes

SAP Note # Issue addressed Comments Affected SAP releases
1647756 FB60 - Tax on "Basic data" tab page Obsolete since EhP 7 SAP_APPL 600-606
without specifying tax code. Fixed with
In transaction FB60, if the manual SAPKH60021
tax amount is specified on the "Basic
SAPKH60211
data" tab page without a tax code
being entered, the system does not SAPKH60310
display the amount when you branch SAPKH60411
to the tax tab page. SAPKH60507
This causes balance problems SAPKH60602
(balance is not equal to zero) and the
document cannot be posted.

11
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

SAP Note # Issue addressed Comments Affected SAP releases

1666591 FB60/MIRO – Setting tax on the Obsolete since EhP 7 SAP_APPL 600-606
“Basic data” tab page to not 0. Fixed with
If you do not specify a posting SAPKH60022
amount for the vendor on the "Basic
SAPKH60211
data" tab page, a tax amount that
was entered (or, for example, the SAPKH60310
tax from the entry from the "Tax" tab SAPKH60411
page) is set to zero if there is only SAPKH60508
one tax code.
However, the balance is not adjusted. SAPKH60602
The error does not occur for several
tax codes in the expense items
because the tax amount is hidden on
the "Basic data" tab page.
1881279 MM item proposal returns the Only required if SAP SAP_APPL 600-616
wrong quantity if the purchase order Note 1821383 “MIRO/ 600 SAPKH60024
numbers are not MIGO: wrong values 602 SAPKH60214
sorted in ascending order. proposed for amount
and quantity” has been 603 SAPKH60313
implemented. 604 SAPKH60414
605 SAPKH60511
617 SAPKH61702
606 SAPKH60609
616 SAPKH61604
1605537 No BI data for SAPLKACB 0002 Only required if SAP SAP_APPL 600-606
You have activated General Ledger Note 1137272 has been 600 SAPKH60020
Accounting (new) and, in the current implemented. 602 SAPKH60210
company code, Obsolete since EhP 7
603 SAPKH60309
document splitting. In this case, Note
604 SAPKH60410
1137272 provides a coding block on
the tax 605 SAPKH60506
screen SAPMF05A 0312 to enable 606 SAPKH60601
you to enter split-relevant fields. A
batch input
session for transaction FB01, in
which these fields are not filled,
hangs with message
00 344 "No batch input data for
screen SAPLKACB 0002".
1327973 FB01/Argentina: BSEG-BUPLA not For Argentina only. SAP_APPL 600-604
ready for input. Required for the 600 SAPKH60016
Business Place field. 602 SAPKH 60206
Obsolete since EhP 5 603 SAPKH 60305
604 SAPKH 60404

12
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

SAP Note # Issue addressed Comments Affected SAP releases

591415 Error messages when processing Obsolete since EhP 5 SAP_APPL 600-604
605780 invoices for purchase orders with 600 SAPKH60017
freight conditions. 602 SAPKH60207
1148218
603 SAPKH60306
604 SAPKH60406

Customer Orders: Required notes

SAP Note # Issue addressed Comments Affected SAP releases
1761277 Missing profitability segments since EPH5 Only required if SAP_APPL 605-616
or SAP Note 12877794. these short dumps Fixed with
During sales order creation check several are generated. SAPKH60510
short dumps are generated at the same
SAPKH60512
time:
SAPKH60607
CALL_FUNCTION_NOT_REMOTE
SAPLKED1_WRITE_CE4_IDEA SAPKH60611
MESSAGE_TYPE_X SAPMSSY0 SAPKH61602
MESSAGE_TYPE_X RK2AIDEA_POST SAPKH61606
Caution: You have to perform this post- SAP_FIN 617-700
implementation step manually and
separately in each system after you have Fixed with
imported the Note to implement. SAPK-61704INSAPFIN
Immediately after you implement the SAPK-70001INSAPFIN
source code corrections, execute the
function module RKE_GENERATE_UPD
for the operating concern that you use.

Financial Postings: Required notes

SAP Note # Issue addressed Comments Affected SAP releases
1605537 No BI data for SAPLKACB 0002 Only required if SAP SAP_APPL 600-606
You have activated General Ledger Note 1137272 has been 600 SAPKH60020
Accounting (new) and, in the current implemented. 602 SAPKH60210
company code, Obsolete since EhP 7
603 SAPKH60309
document splitting. In this case, Note
604 SAPKH60410
1137272 provides a coding block on
the tax 605 SAPKH60506
screen SAPMF05A 0312 to enable 606 SAPKH60601
you to enter split-relevant fields. A
batch input
session for transaction FB01, in
which these fields are not filled,
hangs with message
00 344 "No batch input data for
screen SAPLKACB 0002".

13
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Master data maintenance: Required notes

SAP Note # Issue addressed Comments Affected SAP releases
1537561 When asset master data is deleted in ReadSoft Obsolete since SAP_APPL 604-605
PROCESS DIRECTOR, the asset is not deleted, EhP 6 And Note 1455659
but no error message is displayed. Fixed with
SAPKH60409
SAPKH60504
1706458 Error message AA592 “Depreciation key has SAP_APPL 600-616
fewer depreciation types than previously valid And Note 1491266
key” during post/check. Fixed with
SAPKH60024
SAPKH60214
SAPKH60312
SAPKH60413
SAPKH60510
SAPKH60607
SAPKH61602
1578624 In ECC 6.00, during profit center deletion there is Obsolete since SAP_APPL 600-605
1574641 an error message "Profit centers are used in new EhP 6 Fixed with
General Ledger Accounting" SAPKH60020
(FAGL_LEDGER_CUST155).
SAPKH60210
SAPKH60309
SAPKH60410
SAPKH60505
1770717 After implementing OSS note 1754448 (Incorrect Only required SAP_APPL 600-616
bank data can be copied), bank data with partner if SAP Note Fixed with
type (BVTYP) is not correctly updated and there 1754448 SAPKH60023
is no error message. has been
implemented. SAPKH60213
SAPKH60312
SAPKH60413
SAPKH60510
SAPKH60606
SAPKH61601

14
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

SAP Note # Issue addressed Comments Affected SAP releases

2706149 When you create a customer or vendor SAP_APPL 600-618
using CMD_EI_API or VMD_EI_API, the S4CORE 100-103
corresponding business partner is not created. Fixed with
SAPK-10008INS4CORE
SAPK-10106INS4CORE
SAPK-10204INS4CORE
SAPK-10301INS4CORE
SAPKH60031
SAPKH60221
SAPKH60320
SAPKH60421
SAPKH60518
SAPKH60623
SAPKH61613
SAPKH61718
SAPK-61812INSAPAPPL

Requisitions: Required notes

SAP Note # Issue addressed Comments Affected SAP releases
1160754 Update termination with Obsolete since EhP 5 SAP_APPL 600-604
K_OPEN_ITEM_POST when BAPI Fixed with
is called in simulation mode several SAPKH60016
times.
SAPKH60206
Short dump K_OPEN_ITEM_POST.
SAPKH60305
SAPKH60404
305785 Recheck an already checked 'OK' Only required if All versions
document in display mode. SAP Note 100409 has
Error: Update termination module been implemented.
K_OPEN_ITEM_POST.
Short dump RAISE_EXCEPTION
--> Exception condition
"TEMP_REFBN_COOI" raised.
891356 Change mode: A change to an Only required for SAP_APPL 600
already checked OK document unpatched ECC6 systems Fixed with
(for example, remove doc (without EhP). SAPKH60003
type) leads to a short dump
RAISE_EXCEPTION -> Exception
condition "FAILURE" raised in
CL_HANDLE_MANAGER_MM
METHOD get.

15
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

SAP Note # Issue addressed Comments Affected SAP releases

394058 BAPI_REQUISITION and Commit Only required if All versions
Work. requisitions will be
According to the general design created in SAP. Not
guidelines, a Commit Work must required if only purchase
not be triggered in the BAPI itself. orders will be created in
However, this is not the case for SAP.
BAPI_REQUISITION_DELETE,
BAPI_REQUISITION_CREATE,
BAPI_REQUISITION_CHANGE and
other purchase requisition BAPIs.
For upward compatibility reasons,
this design error cannot be corrected.
Therefore, we provide a consulting
note containing a correction that you
can use in specific cases.
856741 OCI catalog popup support in SAP Only required if using OCI SAP_BASIS 620-700
GUI. catalogs. Fixed with
Link in HTML Viewer displays 'HTTP SAPKB62055
500 Internal Server Error'.
SAPKB64014
SAPKB70004

Recommended SAP notes

Recommended notes for all process types

Recommended notes for Delivery Notes

Recommended notes for Accounts Payable

Recommended notes for Asset Management

Recommended notes for Customer Orders

Recommended notes for Financial Postings

Recommended notes for Requisitions

Recommended notes for Master Data Maintenance

16
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

All processes: Recommended notes

SAP Note # Issue addressed Comments Affected SAP releases
1451769 Required to enable file descriptions Both notes must be SAP_BASIS 700-731
1560955 for attachments (only available from implemented and in Fixed with
ECC600). transaction OAG1 the SAPKB70028
Save File Attribute flag SAPKB70113
must be set.
SAPKB70213
SAPKB73009
SAPKB73106
SAP_BASIS 700-702
Fixed with
SAPKB70024
SAPKB70109
SAPKB70208
2596759 When there is foreign currency with All versions
anything other than two decimal
points in the purchase order, using
BAPI_PO_GETDETAIL1 to get the PO
data leads to incorrect POHISTORY
data.

Delivery Notes: Recommended notes

SAP Note # Issue addressed Comments Affected SAP releases
1050944 Goods Receipt for inbound delivery Obsolete since EhP 7 SAP_APPL 600-606
using inventory management, as of Fixed with
ECC 6.00. SAPKH60015
SAPKH60205
SAPKH60304
SAPKH60402
1974552 Canceling a Goods Receipt in the Required only if Fixed with
feeder system by using the VL09 SAP Note 1928615 has SAPK-90720INSLLPI
transaction leads to the runtime error, been implemented. SAPK-90820INSLLPI
GETWA_NOT_ASSIGNED.
SAPK-90920INSLLPI
SAPK-90A20INSLLPI

Accounts Payable: Recommended note

SAP Note # Issue addressed Comments Affected SAP releases
1650443 Use of Perform or Post function Check Kernel version according
creates short dump with error to the list in SAP note
CALL_TRANSACTION_USING_NESTED

17
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Asset Management: Recommended note

SAP Note # Issue addressed Comments Affected SAP releases
1569937 Error message no. B1537 during Obsolete since EhP 6 SAP_APPL 600-605
posting/checking: Fixed with
BAPIACAM1X_MAX_DE-WAERS SAPKGPFD20
initial v., currency amount & in & was
SAPK-60309INEAFINSRV
transferred without
SAPK-60410INEAFINSRV
a currency.
SAPK-60505INEAFINSRV

Customer Orders: Recommended note

SAP Note # Issue addressed Comments Affected SAP releases
699533 No message from BAPI Only required if EA- EA-RETAIL 110 and 200
SALESDOCUMENT_CREATE if the RETAIL is used Fixed with
credit limit is exhausted SAPKGPRA17
SAPKGPRB06

Financial Postings: Recommended note

SAP Note # Issue addressed Comments Affected SAP releases
1486149 Short dump during FI/FIC reversal Prerequisite is Note SAP_APPL 500-606
due to missing function module 1608790 600 SAPKH60019
"GM_DOCUMENT_REVERSE". Obsolete since EhP 7 602 SAPKH60208
603 SAPKH60307
604 SAPKH60408
605 SAPKH60502

Requisitions: Recommended notes

SAP Note # Issue addressed Comments Affected SAP releases
1008717 OCI catalog: Checkout in SAPGUI Only required if using an SAP_BASIS 620-700
Only partial data is transferred back OCI catalog. Fixed with
to ReadSoft PROCESS DIRECTOR SAPKB62062
from the OCI catalog.
SAPKB64020
SAPKB70011
1355577 BAPI_PO_CREATE1: Runtime Valid only for EhP 4 SAP_APPL 604
problems when calling RTTS Fixed with SAPKH60404
Performance problems occur when
you call BAPI_PO_CREATE1 and/or
BAPI_PO_CHANGE.
ECC 600 Ehp4

18
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

SAP Note # Issue addressed Comments Affected SAP releases

1108045 Performance improvement for Obsolete since EhP 4 SAP_APPL 600-603
archiving object MM_EBAN Fixed with
SAPKH60012
SAPKH60202
SAPKH60301

Master Data Maintenance: Recommended note

SAP Note # Issue addressed Comments Affected SAP releases
639754 For vendor or customer master, Release independent
this note enables the use of the API
posting process, instead of the IDOC
posting process.
You can simulate the posting process
only with API, but if the number
buffering for internal number ranges
has been deactivated, the system
uses at least one customer number.
If the number buffering has been
activated, the system uses all the
buffered numbers.

Importing the transports

Note Before importing, make sure you have checked the prerequisite SAP Notes and the Upgrading
chapter for tasks that you may need to perform before importing.

Warning: Import the transports one at a time for the main version transports. If a return code greater
than 4 is returned after importing a transport, do not import any further transport requests! Contact Tech
Support for assistance and provide details of the return code.

For importing service packages, the SP transports can be imported in one queue.

The import can be done into any client.

Note In systems with Enhancement Pack 5 and later, you may get the error message “n of n requests
do not match the component version of the target system” when trying to import the ReadSoft
PROCESS DIRECTOR transports, and the import cannot be carried out. It is recommended to activate
the Ignore Invalid Component Version import option in the Import Transport Request dialog box.
See SAP Note 1742547 for more information.

19
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

To import the transports, complete the following steps.

1. Extract the ZIP file in the SAP transport folder (...\TRANS\).
2. The transport files are already in the correct COFILES and DATA subfolders.
If it is not possible to extract the transport files directly into the SAP transport folders (for example,
because there is no direct access to the file system on the SAP application server), you have to use
a binary method to transfer the files (for example, FTP). See OSS note 2050.
3. Start SAP transaction STMS (or use the command line using the TP program).
4. Open the import queue of the SAP system.
5. Go to Extras > Other requests > Add.
6. Add the required transport requests one by one to the import queue in the order listed below.
Warning: Import the transports one at a time. If a return code greater than 4 is returned after
importing a transport, do not import any further transport requests! Contact Tech Support for
assistance and provide details of the return code.
If you get other import errors, see the Reading the import log and Troubleshooting sections.

Service Packs
When importing service packs, you need to import only the most recent service pack. Later service packs
always include previous service packs. Therefore, for example, if you want to upgrade to Service Pack 3,
you do not need to import Service Packs 1 and 2 first, as these are included in Service Pack 3.

20
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Service packs do not, however, include the main transport. You must always import the main transport
before importing a service pack.

ReadSoft PROCESS DIRECTOR

New installation
Warning: Import the transports one at a time. If a return code greater than 4 is returned after importing a
transport, do not import any further transport requests. Contact Tech Support for assistance and provide
details of the return code.
Import order Transport
1 ReadSoft_PROCESS_DIRECTOR_AP_7_7*.zip
This is the main transport for Accounts Payable.
2 READSOFT_INVOICE_COCKPIT_Create_Indexes_*.zip
This transport creates the indexes required for ReadSoft PROCESS DIRECTOR
Accounts Payable. Indexes must be activated after import. See Importing and
activating indexes for instructions.
This transport is not required when a HANA database is in use.
3 Kofax_ReadSoft_Namespaces_FQAK901961.zip
This transport creates the /EBY/, /COCKPIT/, and /RSE/ namespaces. Make sure
that the namespaces are activated after importing.
4 READSOFT_PROCESS DIRECTOR 7.7* .zip
This transport provides components for the integration of Accounts Payable in
ReadSoft PROCESS DIRECTOR and use of the ReadSoft PROCESS DIRECTOR
Web Application, as well as other process types.
Optional READSOFT_WEB_CYCLE_PDF_Form_*.zip
This transport is required only if you use the old style SAPSCRIPT form to archive
notes in the HTML format in the /COCKPIT/WI8 transaction. You have to import the
transport into client 000.
This is not required for new installations.

Note If additional components are used (for example, Business Solution Package, Data Import), these
should be imported after all the other transports.

Upgrade
See Upgrading first for tasks that you may need to perform before or after importing.

Warning: Import the transports one at a time. If a return code greater than 4 is returned after importing a
transport, do not import any further transport requests. Contact Tech Support for assistance and provide
details of the return code.
Import order Transport
1 ReadSoft_PROCESS_DIRECTOR_AP_7_7*.zip
This is the main transport for Accounts Payable.

21
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Import order Transport

2 READSOFT_PROCESS DIRECTOR 7.7 * .zip
This transport provides components for the integration of Accounts
Payable in ReadSoft PROCESS DIRECTOR and use of the ReadSoft
PROCESS DIRECTOR Web Application, as well as other process types.

Languages
The languages listed in the PROCESS DIRECTOR Product availability and GUI Languages document are
delivered with ReadSoft PROCESS DIRECTOR 7.7.

If a required language is not available in the standard delivery, contact your Kofax representative or Tech
Support for assistance.

Reading the import log

Any warnings issued (return code 4) during the import can be ignored.

Important: If you get a return code greater than 4, do not import any further transport requests! Contact
Tech Support for assistance and provide details of the first log with return code > 4.

Note Even if errors or aborts occur during the import, this has no adverse effect on your SAP system!

See the Troubleshooting section for other information on other import errors.

Checking the namespaces

The namespaces should have already been created and activated, but we recommend that you check
these settings.

To check the namespace settings, complete the following steps.

1. Start the SE03 SAP transaction.
2. In the Administration folder, double-click Display/Change Namespaces and then the Execute
button.

After importing the transports

After importing the transports, execute the SAP load generator (transaction SGEN).

Executing the load generator

To execute the load generator, complete the following steps.
1. Go to SGEN.

22
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

2. Select Generate the objects of a transport request and click Continue.

3. Select the ReadSoft PROCESS DIRECTOR transport request.
4. Click the Execute button.

Installing licenses
To install the licenses you have been provided, which are text files, execute one of the following
transactions.
• For Accounts Payable and its supplementary products in transaction /COCKPIT/C46.
• For other ReadSoft PROCESS DIRECTOR processes in transaction /EBY/PD_LICENSES.

See the PROCESS DIRECTOR License Installation Guide for detailed information.

23
Importing and activating indexes for PD AP
performance optimization

This section describes how to import and activate indexes to optimize the performance of new ReadSoft
PROCESS DIRECTOR Accounts Payable. It is not required if a HANA database is in use.

ReadSoft PROCESS DIRECTOR Accounts Payable contains indexes to support the current selection
screen, scheduled reports and other developments. Activation of indexes is project specific. This saves
database space because indexes are activated only when they will be used in a ReadSoft PROCESS
DIRECTOR Accounts Payable installation.

Installation and activation of indexes requires the following steps. Make sure that the prerequisites are
fulfilled, and then complete the following steps.
1. Import the new indexes into the development system.
2. Activate the indexes that should be used in the development system. The indexes must be explicitly
activated so that they take effect.

Note Importing and activating indexes has to be done only once. There is no need to perform this task
again after an upgrade.

Index types
There are three types of indexes available for performance optimization.

Type 1
Indexes for optimizing performance with the /COCKPIT/1, /COCKPIT/2, /COCKPIT/WL1, /COCKPIT/
WL2, and /COCKPIT/WL3 transactions.
Name Short description Status Mandatory/optional
S01 Company code (COMP_CODE) Inactive Optional.
Can be activated if the project uses more
than one company code in ReadSoft
PROCESS DIRECTOR Accounts Payable.
S02 Currency (CURRENCY) Inactive Optional.
Can be activated if the project uses more
than one currency code in ReadSoft
PROCESS DIRECTOR Accounts Payable.
S03 Vendor (VENDOR_NO) Inactive Mandatory. Must be activated.
S04 Document date (DOC_DATE) Inactive Mandatory. Must be activated.

24
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Name Short description Status Mandatory/optional

S05 Purchasing Document Number Inactive Mandatory. Must be activated.
(PO_NUMBER)
S06 Document number of an invoice Inactive Mandatory. Must be activated.
document (SAP_DOC_NO)
S07 Reference document number Inactive Mandatory. Must be activated.
(REF_DOC_NO)
S08 Agent (CR_USER) Inactive Optional/mandatory.
Optional: Can be activated if the
project uses Agent to assign ReadSoft
PROCESS DIRECTOR Accounts Payable
documents to special uses.
Mandatory: If a project uses the
COCKPIT/WL1, /COCKPIT/WL2, and /
COCKPIT/WL3 transactions, this index
must be activated.
S09 Transfer date (CR_TIMESTAMP) Inactive Mandatory. Must be activated.
S10 Cockpit document number (DOCNO) Inactive Mandatory. Must be activated.
S11 Cockpit document type Inactive Optional.
(CP_DOC_TYPE) Can be activated if the project uses
more than one ReadSoft PROCESS
DIRECTOR Accounts Payable document
type.

Type 2
Indexes for optimizing performance with the /COCKPIT/PAYMENT_CONTROL report.
Name Short description Status Mandatory/optional
P01 Only PAYMENT_CONTROL Inactive Mandatory for payment control report.
(AUGBL) Must be activated if the project uses the
COCKPIT/PAYMENT_CONTROL scheduled
report to update the payment information in
ReadSoft PROCESS DIRECTOR Accounts
Payable.

Type 3
Indexes for optimizing performance with project-specific requirements. These indexes will be locally
created as a part of the normal project activity.
Name Short description Status
Z** Xxx Inactive
Y** Xxx Inactive

25
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Prerequisite
• The namespaces must be modifiable as described in Checking the namespaces.
This step must be performed by the responsible database administrator. When migrating to new
indexes, some steps can create a huge amount of database load, which can slow down the system.
Those steps should be done during a period that does not have a normal production load.

Importing indexes into the development system

The transport requests in the table below contain a set of necessary indexes for the /COCKPIT/THDR
table. Import the appropriate transport request for your SAP version into the development system.
Request User Short description
DR6K901390 READSOFT INVOICE COCKPIT Create Indexes ERP 6.0

Activating indexes
Index activation must be done in the development system, imported into a test/QA system, and then into a
production system. The activation of indexes is a repair, so this will create a local transport request. Local
transport requests need to be released after all the indexes have been activated. You need to create a
Transport of Copies and include the local transport requests to import the indexes into successor systems.

If you migrate from old indexes to new indexes, this step can create a huge amount of database load.
The installed ReadSoft PROCESS DIRECTOR Accounts Payable already contains data, so the database
not only has to create the new indexes, but also calculate the index entries for the existing entries in the
COCKPIT/THDR table. All the steps in this chapter need to be performed by the responsible Database
Administrator.

To activate an index in the /COCKPIT/THDR table, complete the following steps.

1. Open the SE11 transaction.
2. Set the Database table to /COCKPIT/THDR.
3. Click Display .
4. Click Indexes .

26
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

5. Double-click an index to activate it.

27
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

6. Click the Display/Change button, and then click the Continue (Enter) button for each of the
Information pop-up messages.

28
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

7. Under Non-unique index, select Index on all database systems.

8. Save the changes and create/choose a Workbench request.

9. The Workbench request cannot have an entry set in the Target field.

29
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

10. Save the changes. If there are already a lot of documents in ReadSoft PROCESS DIRECTOR
Accounts Payable, this step can take several minutes or even hours.
The index will be active after Step 10 has been completed and changes have been saved.

Space calculation
The table below contains the length of each delivered index.
Name Short description Length
P01 Only PAYMENT_CONTROL (AUGBL) 53
S01 Company code (COMP_CODE) 68
S02 Currency (CURRENCY) 69
S03 Vendor (VENDOR_NO) 53
S04 Document date (DOC_DATE) 51
S05 Purchasing Document Number (PO_NUMBER) 53
S06 Document number of an invoice document (SAP_DOC_NO) 53
S07 Reference document number (REF_DOC_NO) 59
S08 Agent (CR_USER) 80
S09 Transfer date (CR_TIMESTAMP) 64

30
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Name Short description Length

S10 Cockpit document number (DOCNO) 57
S11 Cockpit document type (CP_DOC_TYPE) 66

(i1 + i2 + .. + in) * (row count of table, /COCKPIT/THDR) = required space to store indexes

The DDIC size of the /COCKPIT/THDR table is less than 1K. Most fields are from type, VARCHAR2,
and some fields are normally empty. The real size of a /COCKPIT/THDR entry on the database is ~527.
Mandatory indexes total to 390.

These figures are only a clue to calculate the required space of indexes. The calculation must be
balanced with the transaction, DB02 > Detailed analysis and real measurement of the used space on the
database.

Example: Table /COCKPIT/THDR has 10,000 entries.

Table size on database: ~ 10000 * 527 = 5270000

Index size on database: ~ 10000 * 390 = 3900000

Total size on database: ~ 5270000 + 3900000 = 9170000

31
Troubleshooting

ReadSoft PROCESS DIRECTOR Accounts Payable

Import errors
During the import you may get an import error. Use the following instructions to assist in solving import
errors you may encounter. For additional assistance, content Tech Support.

If a specific structure cannot be activated during the import, please check the structure in the SE11
transaction. It could be that a field from a Customer Include is now a part of the standard structure. In
such a case, remove that field from the Customer Include and test if you can activate the structure.

Other problems
• If you encounter the following problems:
Images cannot be opened in docking mode in the SAP GUI
Images cannot be opened in the Web Application
Change the settings in the /COCKPIT/C21 transaction to Y- first archive (image data), then Web server
(URL).
These problems may arise because this configuration table is now different from the version of PD AP
you are upgrading from.
• If you get a license error (license not valid) after upgrading to ReadSoft PROCESS DIRECTOR
Accounts Payable, delete the entries in /COCKPIT/C46 and re-enter them.

ReadSoft PROCESS DIRECTOR

Import errors
If the log display shows errors about objects that cannot be activated, the PD AP transport was not
imported.

Solution: Import the PD AP transport.

Short dumps
LOAD_PROGRAM_LOSS short dump occurs during document transfer, check, post, or other action.

Solution: Increase the abap/buffersize parameter in transaction RZ11, Recommended value: 400000 or
higher.

32
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Short dump object modified during runtime.

Call the SGEN transaction and generate all objects of the PD main transport.

DYNPRO_READ_FAILED short dump (terminations) occurs when you load or generate certain screens.

Solution: Adjust the ztta/dynpro_area profile parameter.

Other problems
Poor performance in ReadSoft PROCESS DIRECTOR.

Solution: Check the Tune Summary in transaction ST02 with the SAP System Administrator.

33
ReadSoft PROCESS DIRECTOR Import and Upgrade Guide

Setting the buffer size

To set the buffer size, complete the following steps.
1. Go to RZ11.
2. Enter the parameter abap/buffersize and click Display.
3. We recommend a value of 400000 or higher. Ask the SAP system administrator to increase the
value, if necessary. This requires a restart of the SAP system.

34