ICC 70 AdministratorsGuide en PDF
ICC 70 AdministratorsGuide en PDF
ICC 70 AdministratorsGuide en PDF
Administrator's Guide
Invoice Capture Center
Administrator's Guide
Rev.: V7.0 (2012-12-11)
Open Text Document Technologies GmbH
Max-Stromeyer-Straße 116
D-78467 Konstanz – Germany
Phone: +49 7531 87 0
Support:
Phone: +49 89 4629 2121
E-Mail: [email protected]
Internet: http://www.opentext.com/2/global/services-home/services-support-contact.htm
Introduction 3
Functional Overview ................................................................................................................. 3
Components of Invoice Capture Center ..................................................................................... 5
Customizing ............................................................................................................................... 6
Hot Spots ................................................................................................................................... 7
Achieving Optimum Recognition Results ................................................................................. 8
Installation 9
Planning the Installation ............................................................................................................ 9
System Requirements .................................................................................................. 9
Image Formats ........................................................................................................... 11
Configurations ........................................................................................................... 11
Preparing Installation ............................................................................................................... 14
Configuring Vendor Invoice Management ................................................................ 14
Creating a Domain User for Windows Services ........................................................ 14
Preparing SAP ERP User Accounts .......................................................................... 14
Preparing SAP ERP Login Data ................................................................................ 14
Installing Microsoft .NET Framework ...................................................................... 14
Installing SAP Connector for Microsoft .NET .......................................................... 15
Installing Microsoft Visual C++ Redistributables ..................................................... 15
Switching Off User Account Control ........................................................................ 15
Installing the Microsoft SQL Server ......................................................................... 15
Installation Process .................................................................................................................. 16
Stand-alone Installation ............................................................................................. 16
Installation of the Server ........................................................................................... 17
Installing a Validation Client ..................................................................................... 17
Installation of a Recognition Node ............................................................................ 18
Creating Installation Log Files .................................................................................. 18
Follow-up Activities ................................................................................................................ 19
Configuring the Cluster ............................................................................................. 19
Configuring the Archive Server ................................................................................ 19
Creating and Configuring Applications ..................................................................... 19
Configuring the Windows Firewall for Validation Clients ........................................ 19
Configuring SAP GUI ............................................................................................... 19
Upgrading Existing Applications .............................................................................. 20
Moving the Caches to a Different Location .............................................................. 20
Installing Patches and Service Packs ....................................................................................... 21
Security 65
User Management and Authorization Concept ........................................................................ 65
Windows Users.......................................................................................................... 65
ERP Users.................................................................................................................. 66
Creating a New Role with RFC Authorizations in SAP ERP for Recognition .......... 68
Creating a New Role with RFC Authorizations in SAP ERP for Validation ............ 73
Creating a New Role with RFC Authorizations in SAP ERP for Customizing ......... 74
Delivered Users ....................................................................................................................... 75
Emergency User Concept ........................................................................................................ 75
Logging of Security Relevant Events ...................................................................................... 75
Logging of Application Configuration Data Changes ............................................................. 76
Encryption of Communication Channels ................................................................................. 76
Files and Databases ................................................................................................... 76
SAP ERP ................................................................................................................... 76
Secure configuration ................................................................................................................ 77
Responsibilities ........................................................................................................................ 78
Glossary of Terms 79
Index 85
Audience
The Invoice Capture Center Administrator’s Guide is designed to help both new and experienced administrators to
install, configure, monitor, and administer ICC production systems using the tools and facilities of the ICC Customizing
Client.
Conventions
Example Description
FlowService.dcf This format is used for file names, paths, URLs, and
commands in the command line. It is also used for
example data, text to be entered in text boxes, and other
literals.
System page This format is used for elements of the graphical user
interface (GUI), such as buttons, names of icons, menu
items, names of dialog boxes, and fields. It is also used to
introduce new terms, emphasize particular terms,
concepts.
CTRL+V Key names appear in ALL CAPS.
http://www.opentext.com This format is used for hyperlinks to the Internet and for
internal cross references. Click the link to move to the
respective target page.
<TraceRoot> The brackets < > are used to denote a variable or
placeholder. Enter the correct value for your situation.
Functional Overview
As an option for Vendor Invoice Management for SAP Solutions, Invoice Capture Center extends VIM’s capabilities to
automate the capture of machine-printed paper invoices.
For electronic processing invoices are scanned on entry to the financial accounting department. The digital images of the
invoices are stored in an archive. Invoice Capture Center Recognition is indirectly triggered by the early archiving
mechanism of SAP ERP.
Invoice Capture Center Recognition extracts the essential invoice data (date, amount, order number etc.) from the
scanned invoices in the archive. ICC Recognition uses a knowledge base that has been trained on samples of thousands
of invoices from multiple countries around the world. In addition, it uses fuzzy database matching: ICC Recognition
maps the read data – such as names, addresses, vendor numbers, purchase order numbers etc. – to SAP ERP vendor
master data and SAP ERP purchase order data during analysis.
The extracted information is passed on to Vendor Invoice Management.
Besides the facility to save an invoice application in SAP ERP (export), the Customizing Client also provides the facility
to load an invoice application from SAP ERP to the Recognition Server (import). Using the SAP ERP export and import
facilities the Customizing Client user can copy an invoice application from a development system to a test system or
from a test system to a production system.
Note: While for development and testing, a workstation operating system such as Windows 7 may be used, it is strongly
recommended to use a server operating system such as Windows 2008 Server R2 for Recognition Server and
Recognition Nodes of a production system.
Network
The protocol TCP/IP must be supported. Windows File Sharing is needed for the Recognition Server and the
Recognition Nodes.
Take notice that the HTTPS protocol is not supported for connection to archive systems.
Configurations
Invoice Capture Center allows different configurations ranging from a stand-alone system on a single computer to a
production system for high throughput with a Recognition Server, several Recognition Nodes for automatic recognition,
and several Validation Clients for document correction.
ICC needs a database in a Microsoft SQL Server instance that is used for download data and learning data of all
applications. You can either install an instance with a database on the ICC Server or use suitable instance on a different
computer. During installation of the Invoice Capture Center a dialog box will ask for instance and database name.
The Server manages the connections to the SAP ERP system that provide the applications with recognition tasks and
required download data.
The Server includes the Customizing Client that is used for application development and for configuration of the Invoice
Capture Center and its applications. On a production system, the server also performs load balancing, distributing
recognition tasks to the different Recognition Nodes.
The Recognition Nodes process recognition tasks assigned to them by the Server. They use the applications and
downloaded data that are stored on the Server.
The Validation Clients log on to the SAP ERP system and fetch documents available for correction. They work
independently from the Server and its Recognition nodes.
It is recommended to install Invoice Capture Center on a separate server, i.e. don't install other application software, e.g.
an archive server, on the ICC Server.
Standalone System
Invoice Capture Center can be installed on a single computer for testing purposes. In this case, all features will be
installed on a single computer that is used as recognition server, as validation client, and for customizing.
Note: For unattended installation of Validation Clients, command script examples are available. Comments in the
example files describe how you can adapt the scripts to your configuration.
Structure
In the Customizing Client you can switch between several monitoring views to monitor a special aspect of your Invoice
Capture Center system and you can open several tools for the technical configuration of your system.
The views and the tools are accessible in the ribbon of the Customizing Client: There are buttons to open views and
buttons to start configuration tools.
When you click on a configuration tool button, the tool is opened in a new window. When you click on a view button,
the view is opened within the Customizing Client window; the according view button in the ribbon stays pressed to
indicate which view is currently open in the Customizing Client.
The view buttons and tool buttons are provided on different tabs of the ribbon. View buttons and tool buttons that belong
together in a way are presented on the same tab. A tab of the ribbon corresponds to a scope of the ICC system.
Selecting a different tab in the ribbon will automatically change the view.
During application development you will work mainly with the Application view.
The General tab provides monitoring facilities to the Customizing Client user. On the General tab you can switch
between several technical monitoring views: HotSpot view, Jobs view, and Cluster view. In addition, the
General tab provides the tools Trace Viewer and Load Manager Configuration tool that are described in detail in this
Guide.
The views and tools of the General tab are needed for the technical configuration and for monitoring of an Invoice
Capture Center production system.
All tools of the Application tab work on the currently opened application whereas the General tab permits to show
global data of the Recognition Server – independently of the opened application.
The tools and views of the Application tab are not discussed in detail in this guide. For detailed information about
application development please refer to the Customizing Guide; for detailed information about validation refer to the
User`s Guide. This guide concentrates on monitoring and technical configuration.
Standalone System
Usually, a standalone system is used for developing, for testing, and for demo systems. All Windows components of the
Invoice Capture Center system are installed on one PC:
Standalone PC
o Recognition Server with Customizing Client and databases
o Validation Client
Monitoring
To monitor an Invoice Capture Center system, use the ICC Admin Tool of the Vendor Invoice Management product
in SAP ERP. For further information refer to the Vendor Invoice Management Administration Guide, chapter “Working
with the ICC Admin Tool”.
The Customizing Client (installed on the Recognition Server) provides views to monitor the Recognition Cluster of an
Invoice Capture Center system.
The State column indicates which Hot Spots are active. In a production system, all Hot Spots of all applications should
be in state Scheduled most of the time.
The Last run column shows when the Hot Spot was running last time and the amount of data that were processed
during this run.
Symbol State
Start state of the operation.
Job waits for processing.
Job is being processed.
Job has been completed successfully.
Job has terminated with error(s).
Job is about to be removed from the list.
Column Description
Cluster Node Name of the cluster node that currently processes this
operation.
Profile Profile used by the operation.
Client Client ID started by the operation.
Started at Time when the Operation started.
The first column shows the state of each job. If several processing nodes are available in your configuration, several jobs
may be in state Processing at the same time. Additional jobs that have already been downloaded from SAP ERP but
are still waiting for a free processing node will be in state Pending.
The second column indicates the cluster node a job that is currently being processed has been assigned to. As long as a
job is waiting for processing, this field is empty.
Symbol State
Cluster node has not yet been started (after start or restart of the cluster node).
Cluster node is ready for operation.
Cluster node is executing an operation.
Cluster node is suspended. No operations will be assigned to this node.
Network disturbance. Cluster node is not available.
Cluster node is in a state of error and will be reset
Cluster node is blocked due to a reset or a configuration change.
Cluster node is about to be removed from the list.
Column Description
Name Cluster node name composed of computer name, service type, and
instance number.
Profile Currently loaded profile.
Client Client ID that started the currently active operation.
Total Time Total active time of the cluster node since start of the Load Manager.
Operations Number of processed operations since start of the cluster node.
Command Description
Suspend Cluster Node Excludes the cluster node from load balancing. A currently active
operation will be completed before suspension takes effect.
Release Cluster Node Releases a suspended cluster node to rejoin the load balancing.
Lookup Cluster Node Updates the cluster node state (normally the Load Manager updates it once
per minute).
Reset Cluster Node Terminates the current instance of the cluster node and starts a new one.
Overview of Tracing
Invoice Capture Center permits to generate trace data that can be used to analyze and fix problems at runtime. The
tracing component has the following features:
Output to multiple tracing targets
Hierarchical tracing architecture
Easy configuration on-the-fly through XML configuration files or software
Trace Viewer to view trace files, filter and search trace data and observe applications on several hosts
Tracers
A tracer represents the source of a trace message. Tracers are named entities with a hierarchical structure. Hierarchy
levels are separated by dots. This corresponds to the naming of .NET classes including namespaces. Therefore usually
the class name, e.g. DOKuStar.Runtime.Server, is used as name of the respective tracer.
The tracer name is used to configure the properties of the tracer such as the trace level. You may use the full name of the
trace or only a part of the name. If a particular trace has not been configured explicitly, it will inherit its configuration
from its parent tracer.
E.g. DOKuStar.Runtime is a parent of DOKuStar.Runtime.Server, DOKuStar is a parent of
DOKuStar.Runtime.
A special tracer, called the RootTracer, is the parent of all tracers; it has no name.
Trace Listeners
Trace listeners represent the destination of trace messages. The tracing system ships with a collection of trace listeners:
Trace Configuration
Several trace configuration files in the trace folder specify what trace messages a distinct Invoice Capture Center
component will write to the trace folder. For example, a trace configuration file defines the trace level for the trace
messages. Only trace messages with this specified trace level or higher will be written to the trace folder.
You may configure traces by editing the appropriate trace configuration file directly or selecting a predefined trace
configuration in the Trace Viewer (see Trace Viewer). Notice that selecting a predefined trace configuration in the Trace
Viewer will change the trace configuration files automatically.
The trace configuration file has three types of elements:
listener
This element configures a trace listener by specifying:
name any describing name,
type the full qualified name of the class which implements the listener,
threshold trace level (optional, default is Finest)
and other trace listener specific parameters.
<root>
<listener-ref ref="file" />
<listener-ref ref="remote" />
<level value="fine" />
</root>
category
This element configures certain tracers by specifying:
name name of the tracer or part of its hierarchical name
level trace level
<category name="DOKuStar.Cluster.Operation">
<level value="fine" />
</category>
There are two types of configuration files: merge (default) and overwrite.
A file of type merge configures only a few items and merges them with a configuration that may have been initialized
by software and already has specified its root tracer and trace listeners so that you only want to change trace levels of
certain categories.
Example:
<?xml version="1.0" encoding="utf-8" ?>
<trace>
<category name="DOKuStar.Cluster.Operation">
<level value="fine" />
</category>
<category name="DOKuStar.Cluster.ClusterNode">
<level value="fine" />
</category>
<category name="DOKuStar.Cluster.Extraction">
<level value="fine" />
</category>
</trace>
A file of type overwrite configures all features and will completely reset an initial configuration made through
software. You must specify the root tracer and its listeners.
Example:
<root>
<listener-ref ref="file" />
<listener-ref ref="remote" />
<level value="fine" />
</root>
<category name="DOKuStar.Cluster.Operation">
<level value="fine" />
</category>
<category name="DOKuStar.Cluster.ClusterNode">
<level value="fine" />
</category>
<category name="DOKuStar.Cluster.Extraction">
<level value="fine" />
</category>
</trace>
Examples for trace configuration files you will find in the folder TraceConfig in the Invoice Capture Center
installation folder.
Format of Traces
Traces written to trace files have the following format:
<DateTime> <Level>:<Computer> <Application> <PID> <Category> <ThreadId> [[<Message>]]
DateTime: Time when the trace message was written, sortable format yyyy.MM.ddTHH:mm:ss
Level: Trace level Fatal, Error, Warning, Info, Fine, Finer or Finest
Computer: Name of the host where the trace message was written
Application: Name of the application that wrote the trace message
PID: ID of the process that wrote the trace message
Category: Trace category (hierarchically to reflect classes and modules)
ThreadId: ID of the thread that created the trace message
Message: Trace message enwrapped with 2 squared brackets at begin and end. Note: A trace message is multi-
line; it may contain carriage return and line feed.
Example:
2011.03.04T10:17:45 Error: SYS2186 DOKuStarLoadManager 2264 DOKuStar.Cluster.Configuration 1 [[this is the
error message]]
Trace Viewer
Trace Viewer Window
The Trace Viewer can be started from the Customizing Client by clicking Trace viewer in the Tools group of the
General tab. You can also start it directly from the Invoice Capture Center program group of the Windows start menu.
It is used to show trace messages created by the Invoice Capture Center components and permits to
- view trace files,
- search text using regular expression,
- filter trace messages,
- record trace information on-the-fly even on multiple computers simultaneously,
- drop files into the viewer.
When you start the Trace Viewer, it will show a list of all trace files found on the local machine on the left side. The list
is grouped by the different components:
The header shows the path of the trace folder as a link. If you click on the link, the folder is opened in a Windows
Explorer.
Note: The dialog box can’t indicate the current trace configuration, because you could modify the trace configuration
files using a text editor at any time, creating a custom configuration differing from all three default configurations
described above.
Options
Opens the Options dialog box where you can change the language of the Trace Viewer user interfaces.
Help Menu
About Trace Viewer
Shows a dialog box with version information.
The toolbar buttons above the messages list view permit to control which messages will be displayed in the list view, see
below.
By double-clicking on a message in the list view you can open a Trace Message dialog box showing the complete
message and its details:
Trace Configuration
Opens the Trace Configuration dialog box where you can select one of three trace configurations:
Debugging production system: This configuration can be used to search for errors. Here all trace
levels are set to the level finest. This mode will produce a large amount of trace data.
Development: This configuration can be used to search for errors in your own code. Here the trace level
for all namespaces starting with DOKuStar is set to info, while all other levels are set to finest. So you
will get the maximum amount of trace data for project modules and plug-ins if you use a separate namespace.
Production: This configuration is intended for production systems. It will trace all errors, warnings, and
info traces, but won’t produce too much trace data.
This configuration affects the local computer. If you want to search an error on a processing cluster, you may
need to modify the trace configurations on all computers of the cluster.
Display Level
Permits to specify one of seven different trace levels. In the most restrictive level only fatal error messages are
shown. In the most talkative trace level, messages of all message types are shown.
The toolbar text indicates the currently selected trace level. In the above example, trace level Debug Fine is
just being used.
Display filter
A dialog box permits to set different kinds of filters that control which log messages are shown.
Find
The Find dialog box opens. It permits to search messages containing a string, word, or a regular expression.
When the command has already been used, the F3 function key can be used to jump to the next occurrence.
Auto scroll
If this button is pressed, the view will show the last lines, when trace messages are added.
Open…
Opens a log file. The contents of the file is loaded and shown in the messages list view.
Take notice that specified filters only affect the messages view of the Trace Viewer. They don’t modify the contents of
the trace files and they don’t control which messages will be written to trace files.
To open the Filter dialog box, use the Filter command in the context menu of the messages list view or the
corresponding toolbar button.
Different kinds of filters can be specified:
Level
This filter permits to switch all trace messages off or to specify a trace level. If the trace level is set to Error,
only error messages will be shown. The other values will add messages of other types successively. If the
trace level is set to Finest, messages of all types will be shown.
The trace level can also be set using the toolbar of the messages list view. This toolbar is not shown by
default. It can be switched on or off with the Tool Bar command in the context menu of the messages list
view.
Computer
Here all computers of the cluster used by the project are listed. By default, messages from all computers are
shown. If you work with a cluster you can exclude some computers or restrict output to the messages of a
single computer.
Application
Here all applications of the current project are listed. By default, all applications are enabled.
PID
Here the process IDs of all processes of the current project are listed. By default, all processes are enabled.
To open the dialog box, use the Find command in the context menu of the messages list view or the respective button in
the toolbar of the view.
If you just enter a string into the text box, this string will be searched. If you select the Match case check box, the
string will be searched in exactly the same spelling with regard to upper and lower case letters. If you select the Match
whole word check box, the search string will not be matched to a part of a word or stretching over two or more words
but only to a single word. If you select the Use regular expression check box, the search string is interpreted as a
regular expression.
If you click Find Previous or Find Next, the previous or next matching trace message is selected in the messages
list view.
Customizing Client
The Customizing Client runs on the Recognition Server and keeps configuration data in the folder
%ALLUSERSPROFILE%\Application Data\Open Text\DOKuStar Dispatch\data\config\RdaProject as
described in the section Application Configuration Data (Customizing Data) on the next page.
Runtime Files
Temporary Files of DOKuStar Professional and DOKuStar Extraction
On the Recognition Cluster Nodes the actual extraction is done by a component named DOKuStar Extraction.
Superordinate tasks, like splitting of pages or export of results are done by a component named DOKuStar Professional.
Both components write temporary files into the Windows temp directory.
If the Load Manager Service of a Recognition Cluster Node is running using the LocalSystem account, the
temporary files are written in the temp directory defined in the system temp variable.
If the Load Manager Service is running using a domain account, the temporary files are written into the temp directory
defined in the user temp variable.
Trace folder
Each participant of an Invoice Capture Center system writes trace files to its local trace folder
%ALLUSERSPROFILE%\Application Data\Open Text\Trace.
The location of the Trace folder can be changed by creating a registry entry. See Logging and Tracing for further
information.
Registry Entries
During installation Invoice Capture Center adds some entries to the Windows registry, e.g. installation paths and version
information.
ICC Database
Vendor master data and purchase order data are periodically downloaded from SAP ERP and stored into the ICC
database. In addition, this database includes recipient data that have been imported during customizing.
Several tables in the ICC database contain the learning data for Adaptive Recognition (ART) and Adaptive Classification
(ACT). For each Invoice Capture Center application there is a single table with learning data for all adaptive recognition
fields of the respective application. For each adaptive classification field that has been added to an Invoice Capture
Center application there is a single table with learning data.
The ICC database is used for all Invoice Capture Center applications running on the Recognition Server, but each
application uses its own set of tables.
Services
Invoice Capture Center is based on Open Text Capture Center. The runtime environment of Open Text Capture Center
consists of several programs and Windows services. In the standard configuration the following Capture Center
Windows services run on the Recognition Server (Master), on the Recognition Nodes (Slaves) and on the Validation
Clients:
Recognition Server
o Load Manager Service (DOKuStar Load Manager 3.0)
o Hot Spot Service (DOKuStar HotSpot 3.0)
o Tracing Service (DOKuStar Tracing)
Recognition Node
o Load Manager Service (DOKuStar Load Manager 3.0)
o Tracing Service (DOKuStar Tracing)
Validation Client
o Tracing Service (DOKuStar Tracing)
The Load Manager Service on the Recognition Server distributes the workload on the Recognition Nodes by
communicating with the Load Manager Services on the Nodes.
The connection of the Recognition Server to the SAP VIM system is provided by the Hot Spot Service. The Hot Spot
Service polls for recognition jobs provided by the VIM Dispatcher Infrastructure. It also polls for vendor master data and
purchase order data that will be imported into the database of the Recognition Server.
A Cluster Node hosts a service of a specified type called the Service Type. For DOKuStar Professional there are services
for DOKuStar Extraction and DOKuStar Professional Runtime.
In order to process a job request, a Cluster Node usually must be initialized: for example a DOKuStar Professional
Runtime Cluster Node is initialized with the name of a DOKuStar Professional project file. There may be more complex
initializations on other service types. Such initialization data are stored within Profiles, which are also configured at the
master. A job refers only to this profile name instead of specifying all initialization data to carry out the task.
DOKuStar Professional automatically creates and configures the appropriate profiles at the Load Manager; you do not
need to configure them manually.
The Load Manager processes a job request by creating an Operation. The Load Manager keeps a list of waiting and
active operations and manages them until their execution has been completed.
The Jobs view and the Cluster view of the Customizing Client on the Recognition Server permit to monitor the Load
Manager. For information about monitoring refer to Monitoring.
The Cluster configuration is managed centrally at the Recognition Server. The Load Manager Configuration tool
(provided by the Customizing Client) permits to configure the Recognition Cluster.
In the explorer view on the left side yon can use the context menus of the different nodes, to add or delete computers or
to add or remove cluster nodes. If you select a node, its properties are shown in the right part of the dialog box.
During installation, a Runtime Node for the computer acting as server will be configured automatically. At runtime
additional Runtime Nodes for each processor on that computer will be added automatically. Therefore you need to
modify configuration only if you have installed Invoice Capture Center on additional Recognition Nodes.
Enter the computer name and confirm with OK. A new computer node appears for the respective computer.
Note: The context menu of the computer nodes permit to add Extraction as well as Runtime nodes. Whether
Extraction nodes are needed, depends on the DOKuStar Professional project. Within Invoice Capture Center,
Extraction nodes are not needed!
At each additional Recognition node add one Runtime node for each processor. In the context menu you can specify
the number of needed Runtime Nodes:
For a computer with two processors, the configuration should look as follows:
Property Description
Name Cannot be edited; comprised from the computer name, service type and instance number.
AgentUrl Specifies the URL of the agent service for this cluster node within the cluster. To edit the
computer name, select the parameter line and then click the ellipsis button at the end of the
line.
Description Only for logging purposes.
Exclusive Profiles Permits to restrict a cluster node to specified profiles.
Priority Specifies the priority of the cluster node. The Load Manager will prefer cluster nodes with
higher priority.
Within Invoice Capture Center you don’t need to modify any properties.
Property Description
LookupInterval Specifies the time interval after which the Load Manager will check whether the cluster
node is still alive.
Profiles This property can be used to view the profiles. Select the property and click the ellipsis
button that appears at the end of the line to open the Profile dialog box.
Reset Cycle After the specified number of operations the cluster node will be reset automatically. This
can also be used to ensure that the project will be reloaded. This may be needed to activate
new versions of database files for an Extraction project-
Reset on failure If this property has the value True, the Load Manager will try to reset the cluster node in
case of failure.
Startup Time Specifies the maximum time the cluster node should need for start-up.
Note: If the Extraction Link Hot Spot is not running, the Recognition Server won’t ask for recognition jobs and won’t
deliver recognition data for Vendor Invoice Management!
Tag Information
DataShare Path of the data share, i.e. \\<servername>\DOKuStarDispatchData
User User account used for the DOKuStar Load Manager 3.0 service
Cluster List of ClusterNode tags containing the names of all configured cluster nodes.
The first part of the name indicates the computer the cluster is running on.
Trace Path of the trace folder
SqlServer Contains:
Server tag with the computer name,
Instance tag with the instance name,
Database tag with the name of the database file,
User tag with the user name in case of SQL Server Authentication,
IntegratedSecurity tag has value true in case of Windows
Authentication, false in case of SQL Server Authentication.
Product Product name (Invoice Capture Center)
Version Version number (7.0)
Build Build number
ServicePack Installed service pack
OwnerName Name of the product owner (Open Text)
Error Scenario ICC Error Code SAP ERP Error Message Administrator Action
87 Recognition Errors
Recognition service broken 001 Recognition service broken Check Recognition Server, restart
Recognition Services, retry
Empty image 002 Empty image Check image, delete job, and rescan
document
Unknown image format 003 Unknown image format Check image, delete job, and rescan
(Extraction) document
License error 004 License error (Extraction) Check license file, install license file,
order new license file, retry
Archive not accessible 005 Archive not accessible Check archive connection, set job back
(Recognition gets no image (Extraction) to retry
data)
Other 006 Other error (Extraction) Check error details for more information
89 Validation Errors
Unknown image format 003 Unknown image format Delete document
(Validation)
Archive not accessible 005 Archive not accessible Cancel and retry to get document data
(Validation gets no image (Validation)
and result files)
Other 006 Other error (Validation) Check error details for more information
Port Usage
The following table lists ports used by Invoice Capture Center:
To determine the instance-specific port number used by the SQL Server, start the SQL Server Configuration Manager.
Under SQL Server Network Configuration click Protocols for <instance>, click the protocol TCP/IP
with the right mouse button and then click Properties on the context menu. On the appearing TCP/IP Properties
dialog box click the IP Addresses tab. By default, a dynamic port number is used. Switch to static port number as
described in the online help of the Configuration Manager, and then use the specified static port number for
configuration of the Firewall.
Deleting an Application
To delete an application, click the Invoice Capture Center button in the top left corner of the Customizing Client
window. Then click Delete Application, and select the appropriate application in the sub-menu.
To delete the current application, first close the application.
Note: The application will be deleted locally on the Recognition Server. It won’t be deleted in SAP ERP. Refer to the
Vendor Invoice Management Administration Guide, chapter “Deleting an ICC application from SAP tables” for
information about deleting an application in SAP ERP.
Validation Client
The version information is shown in the About dialog box. In the Validation Client on the Invoice Capture
Center menu, click About to open the About dialog box.
File System
You find the version information in the Invoice Capture Center installation folder ( C:\Program Files\Open
Text\Invoice Capture Center 7.0) in the file Invoice Capture Center Version.xml.
Registry
You find the version information in the registry key
HKEY LOCAL MACHINE/Software/Open Text/Invoice Capture Center/7.0 on Windows
x86 systems
or
HKEY LOCAL MACHINE/Software/ Wow6432Node/Open Text/Invoice Capture
Center/7.0 on Windows x64 systems.
SLD Registration
All Windows components of an Invoice Capture Center system register in the SAP System Landscape Directory. The
SLD registration is provided by a Windows service named Invoice Capture Center SLD Data Supplier that is running on
each component. The registration takes place automatically when the SLD Data Supplier Service starts and periodically
twice a day.
The Data Supplier has to be configured once after installation. To open the configuration dialog box, select Tools –
SLD Data Supplier in the Invoice Capture Center program group of the Windows start menu. Enter the NetWeaver
settings SLD host, port, user, and password. To test the configuration click Test collect and send SLD data.
Windows Users
For further information about using the Windows user management refer e.g. to Best Practice Guide for Securing Active
Directory Installations or to the Windows Server 2003 Security guide (downloadable at
http://www.microsoft.com/downloads).
If you want to store images as training module SAP ERP user, you need two additional authorizations:
S_TCODE:TCD=OAWD
S_WFAR_OBJ:OAARCHIV=*,OAOBJEKTE=/OPT/V1001,OADOKUMENT=*,ACTVT01
Now click the Authorizations tab. You will be asked to save the role. Save the role and proceed.
Click Do not select templates. On the Change role: Authorizations screen, click Manually to add the
needed RFC authorizations.
Edit the fields Activity, Name of RFC to be protected, and Type of RFC object to be protected under
Authorization Check for RFC Access.
Click the pencil next to Name of RFC to be protected. In the pop-up enter the values as shown below and click
Save.
For current versions, add lines with values RFC1, RFC_METADATA, SDIFRUNTIME and SYSU.
When all field values have been entered, click Save in the Change role screen.
For current versions, add lines with values RFC1, RFC_METADATA, SDIFRUNTIME and SYSU.
For current versions, add lines with values RFC1, RFC_METADATA, SDIFRUNTIME and SYSU.
In SAP ERP versions newer then release 7.10 (EHP 4 and later), you can choose a finer granularity for your
authorizations (see SAP Note 460089). Instead of the authorizations for RFC function groups, you can use authorizations
for each single function module.
The following authorizations can be replaced:
1. S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SYST
replace by:
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFCPING
2. S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SRFC
replace by:
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFC_PING
3. S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=RFC1
replace by:
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFC_FUNCTION_SEARCH
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFC_GET_FUNCTION_INTERFACE
4. S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SDIFRUNTIME
replace by:
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=DDIF_FIELDINFO_GET
Replacing the other function group authorizations by the function module authorizations is possible, but it does not make
much sense, because nearly each function module within the groups is used.
SAP ERP
All participants of an Invoice Capture Center system communicate with the ICC Dispatcher Infrastructure in SAP ERP
by making RFC calls using the SAP .NET connector. You can use Secure Network Communication (SNC) to secure
RFC connections (see Encryption for RFC for further information).
SAP archives are accessed using HTTP or HTTPs – depending on the configuration of the archive.
ACT
Abbreviation of Adaptive Classification Technology
Adaptive Classification
An adaptive classification field does some sort of classification of a document. Normally the field value is one of a set of
terms. The term itself is not contained in the text of the document but can be determined by examining the entire contents
of the document. When configuring an adaptive classification field you will enter the set of valid terms for the field. At
runtime the adaptive classification field will be presented to the user with a combo box containing the list of terms. The
Recognition Server and the Recognition Nodes have to learn how to select the correct term for an adaptive classification
field from the set of terms. They need a sample for each kind of invoice and the correct term for each sample. These
samples and the according term have to be provided by training. During training, the term is selected manually by the
user. The document and the term are then stored in a learning database. If a similar document is processed later on,
adaptive classification will then find a matching sample in the learning database, and will then use the learned term.
Adaptive Recognition
The Recognition Server and the Recognition Nodes have to learn how to extract data for an adaptive recognition field.
They need a sample for each kind of invoice, e.g. for each vendor, and the position where the field can be extracted on
this kind of invoice. These samples (=templates) and the according position information have to be provided by training.
During training, the field is captured manually using the mouse. The layout of the document and the positions of the
respective field are then stored in a learning database. If a similar document is processed later on, adaptive recognition
will then find a matching sample in the learning database, and will then extract the field at the learned position.
Application
An invoice application bundles all settings that are needed to process invoices of a certain kind, e.g. the country in which
the recipients of the invoices reside, or which fields have to be extracted by which extraction method, or which fields
should be visible in the Validation Client.
ART
Abbreviation of Adaptive Recognition Technology
Cluster
See Recognition Cluster
Cluster Node
A Cluster Node is a component of a Recognition Cluster performing job processing. The Recognition Cluster contains
one Cluster Node for each processor of the Recognition Cluster. The DOKuStar Load Manager performs load balancing
and distributes recognition jobs among all Cluster Nodes of the Recognition Cluster. If there is only a Recognition
Server and no Recognition Nodes, there will be as many Cluster Nodes as processors in the Recognition Server machine.
Content-Based Classification
See Adaptive Classification
Customizing
Invoice Capture Center provides various settings to adapt the system to customer needs. These customizing settings are
bundled in invoice applications. To customize Invoice Capture Center for customer needs you have to create invoice
applications.
Customizing Client
The Customizing Client is a Windows program that is used on the development system to customize Invoice Capture
Center, i.e. to create and configure applications. It is also used to test applications, to export them to a SAP ERP system,
and to import them on a test or production System. In addition, it is used to monitor and administer an Invoice Capture
Center system.
DOKuStar Professional
In an Invoice Capture Center system the actual data extraction from an invoice image and super-ordinate tasks, like
splitting of pages or export of results, are performed by a component named DOKuStar Professional.
Hot Spot
The Recognition Server uses Hot Spots to fetch recognition jobs, download data, and learning data from its SAP ERP
system. A Hot Spot becomes active regularly after expiring of a specified interval or at a specified time on specified days
and then tries to fetch new data. Each application uses Hot Spots of two different types. A SAP Extraction Link is used
to fetch new recognition jobs from SAP ERP. A SAP Download Link is used to fetch new data, such as vendor master
data and purchase order data.
Invoice Application
See Application
Learning
While special, optimized methods are used to extract the standard fields, for adaptive recognition fields and adaptive
classification fields Invoice Capture Center has to learn how to fill the field values. The learning data have to be
provided by training. The Recognition Server keeps the learning data in its local database.
Link
Links are used to download recognition jobs and download data from SAP ERP. Links are implemented as so-called Hot
Spots. The Hot Spots used for the Links connect to SAP ERP regularly at specified times and fetch available jobs or
data.
Load Manager
See DOKuStar Load Manager
Master
On a Recognition Cluster, the DOKuStar Load Manager performs load balancing over all processors of the Server and
the Recognition Nodes. The Load Manager on the Server acts as Master. It transfers recognition jobs that are fetched
from SAP ERP regularly to free Cluster Nodes for processing.
Recipient Data
Invoice Capture Center can derive the company code and target SAP ERP system automatically using recipient address
data found on the invoice. During application configuration, a database containing recipient data together with the
corresponding company codes and SAP ERP system names has to be supplied if automatic company code detection shall
be used.
Recognition
Recognition comprises the extraction of essential invoice data, such as date, amount, order number etc., from the scanned
invoices and the intelligent verification of these data. Recognition is performed by the Recognition Cluster.
Recognition Job
Scanned documents are first stored in an archive (early archiving). Then a workflow is started that creates entries for the
documents in the ICC Dispatcher Infrastructure. The Recognition Server fetches available entries from Vendor Invoice
Management regularly, creates Recognition jobs, and transfers them to the input queue of the Load Manager. The Load
Manager assigns the first waiting recognition job to the next Cluster Node that becomes available. The Cluster Node
fetches the document from the archive, processes it, and transfers the result data to SAP ERP. The document is then
made available for Validation.
Recognition Node
For huge systems the Recognition Server can be supported by additional machines, installed as Recognition Nodes. The
DOKuStar Load Manager on the Recognition Server fetches jobs from SAP ERP using a SAP Extraction Link and
distributes the jobs among all processors of the Server and the different Recognition Nodes. By adding Recognition
Nodes, the processing power of the whole Recognition Cluster can be adapted to the required throughput.
Recognition Server
Document processing is performed on a Recognition Cluster consisting of a Recognition Server and possibly additional
Recognition Nodes. The Recognition Server comprises the Customizing Client that is used to customize, configure, and
monitor the Invoice Capture Center system. It also comprises the databases containing vendor master data, purchase
order data, and learning data. It also hosts the Hot Spots that are used to fetch jobs and download data from the SAP ERP
system regularly. The DOKuStar Load Manager of the Recognition Server is the master of the recognition cluster. It
contains the cluster configuration and distributes recognition jobs on the processors of the Server and additional
Recognition Nodes.
Slave
On a Recognition Cluster, the DOKuStar Load Manager performs load balancing over all processors of the Server and
the Recognition Nodes. The Load Manager acts as a Slave on each Recognition Node. When a Runtime Node terminates
a job, it waits until the Load Manager on the Server that acts as Master supplies it with a new job.
Server
See Recognition Server
Standalone System
For development and testing of applications, all components of Invoice Capture Center can be installed on a standalone
system, i.e. on a single computer.
Training
To be able to extract adaptive recognition fields or adaptive classification fields automatically, some training has to be
performed first. Training can be performed manually by the user on the Customizing Client.
Validation
The extracted invoice data can be checked and eventually corrected or completed by a user. The validation facilities of
Invoice Capture Center are provided by the Validation Client program and also by the Customizing Client program.
Validation on the Customizing Client is only performed for developing and testing purposes.
Validation Client
The Validation Client is a Windows program that is used by a clerk to check and correct data that have been extracted
automatically and to capture additional fields that could not be read automatically. The corrected and completed data are
then passed on to Vendor Invoice Management.
VIM
Abbreviation of Vendor Invoice Management
Index P
Port Usage 61
R
A
Recognition Node 5, 25, 27
Application Adding Recognition Nodes 56
Configuration Data 47, 76 Configuring 51, 52, 53
Deleting 62 Installation 18
Upgrading 20 Port Usage 61
Archive Server 19 Requirements 9
Hardware 9
C Software 10
Cache 9
Configuration Data 46 S
Databases 48 SAP ERP
Location 46 Configuration Data 47
Configuring SAP GUI 19
H Preparing SAP ERP Login Data 14
RFC Authorizations 65
Hardware Requirements 9
SAP Solution Manager 60
High Availability 57, 58
SLD Registration 63
Hot Spots 7
Tracing 44
Files 46
User Management and Authorization 65
Monitoring 28
Secure Configuration 77
Starting and Stopping 58
Security 65
Trace Files 36
Encryption 76
Logging 75, 76
I Responsibilities 78
Secure Configuration 77
Installing 9
User Management and Authorization Concept 65
Planning 9
Services 48
Preparing 14
DOKuStar Load Manager 47, 51, 65
Recognition Node 18
Port Usage 61
Server 17
SLD Data Supplier 63
Stand-alone System 25
Starting and Stopping 58
Two Recognition Servers 58
Single Sign-On 66
Upgrading Applications 20
Software Requirements 10
Validation Client 17
SQL Server
Installing 15
L Port Usage 61
Load Manager 51 Starting and Stopping 58
Clients 59
Configuration 19, 52
Hot Spots 58
Configuration Files 46
Services 59
Location of Temporary Files 47
Logging 31, 76
T
M Trace Viewer 37
Filter Dialog 43
Monitoring 28
V
Validation Client 25, 27
Configuring the Windows Firewall 19
Installing 17
RFC Authorizations 68, 73, 74
Single Sign-On 66
Starting and Stopping 59
Testing 12, 16
Trace Files 36
Wiindows User 65
Version Information 63
W
Windows Firewall 19