Kofax Export Connector for ERP

Transcription

1 Kofax Export Connector for ERP Administrator's Guide

2 Portions Kofax, Inc., Laguna Canyon Road, Irvine, California 92618, U.S.A. Portions Kofax Development GmbH. Portions Kofax Development UK Ltd. All Rights Reserved. Use is subject to license terms. This product is protected by U.S. Patent Nos. 5,159,667 and 7,478,332. Third-party software is copyrighted and licensed from Kofax's suppliers. THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF KOFAX, INC. USE, DISCLOSURE OR REPRODUCTION IS PROHIBITED WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF KOFAX, INC. Kofax, the Kofax logo, and MarkView are trademarks or registered trademarks of Kofax, Inc. in the U.S. and other countries. All other products names are the trademarks or registered trademarks of their respective owners. U.S. Government Rights Commercial software. Government users are subject to the Kofax, Inc. standard license agreement and applicable provisions of the FAR and its supplements. You agree that you do not intend to and will not, directly or indirectly, export or transmit the Software or related documentation and technical data to any country to which such export or transmission is restricted by any applicable U.S. regulation or statute, without the prior written consent, if required, of the Bureau of Export Administration of the U.S. Department of Commerce, or such other governmental entity as may have jurisdiction over such export or transmission. You represent and warrant that you are not located in, under the control of, or a national or resident of any such country. DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. This product includes itext Library - Copyright (c) by Bruno Lowagie and Paulo Soares. The contents of itext Library are subject to the Mozilla Public License Version 1.1 (the License ); you may not use this file except in compliance with the License. You may obtain a copy of the License at Software distributed under the License is distributed on an AS IS basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. This product includes software developed by: Apache Software Foundation ( Licensed under the Apache License, Versions 1.1 and 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at or Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Jean-Loup Gailly and Mark Adler - Copyright (c) The JDOM Project ( Jaxen Project ( Copyright 2001 werken digital. All Rights Reserved. Copyright (c) The Legion Of The Bouncy Castle (

3 All other third-party products or brands mentioned in this documentation are or may be trademarks or registered trademarks and are the property of their respective owners. LibTiff.Net Copyright (c) , Bit Miracle All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the Bit Miracle nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BIT MIRACLE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

4

5 Contents Preface... 7 User Interface Notes... 7 Who Should Read This Guide... 7 Related Documentation...7 Getting Help for Kofax Products... 8 Configuring the Export Connector... 9 Creating and Configuring a Batch Class - Initial Steps... 9 Creating a Batch Class...9 Adding a Document Class to the Batch Class...10 Adding KEC-ERP to the Document Class Making Initial Configuration Settings Adding Index Fields (Optional)...13 Configuring a Store Using Barcode with No Index Fields...13 Creating a Barcode Field Type Configuring KEC-ERP Configuring a Store for Subsequent Entry Configuring KEC-ERP Customizing Table Data (Optional) Dynamic Transactions Configuring a Store with Customer-Defined Transactions...19 Configuring KEC-ERP Configuring a Store using XFT Queue Manager Configuring KEC-ERP Store with Barcode...23 Creating Global Document Types...23 Creating Workflow Document Types...24 Creating Workflow Parameters Creating Barcode Types Creating Barcode Entry...26 Creating a Content Repository Link...27 Creating Objects Store for Subsequent Entry Configuring SAP for Release with Image...29 Creating Global Document Classes...30 Creating Business Objects Adding a Transaction Code Kofax Export Connector for ERP Administrator's Guide 5

6 Contents Maintaining Tasks Linking Tasks, Objects, Type and Class...39 Checking the Links Creating Workflow Document Types...44 Creating Workflow Parameters...45 Creating Global Document Types Linking a Document Type to an SAP Object Type Configuring SAP for Release without Images Creating Business Objects Maintaining Tasks Generic Transactions Configuring SAP for Customer-Defined Transactions with Images...51 Configuring SAP for Customer-Defined Transactions without Images...52 Configuring SAP for Customer-Defined Non-BKPF Transactions XFT Queue Manager Customizing SAP Content Repository with More than Two Characters...55 PDF Files...57 Adding the PDF Generator as a Module to the Batch Class...57 Configuring KEC-ERP Supported Index Fields...59 Index Field Prefixes and Names...60 MIRO Fields Passing Document IDs Releasing the Document ID to Another Export Connector...63 Passing the Document ID to a Function Parameter Disabling Image Release...67 Troubleshooting...69 Kofax Troubleshooting Tools Log Files...69 SAP Troubleshooting Tools...71 Archive System Availability...71 Workflow Test...74 User Profile Test Workitem Technical Location Test...76 Third-Party License Agreements...77 Index Kofax Export Connector for ERP Administrator's Guide

7 Preface This guide provides step-by-step instructions for configuring Kofax Export Connector for ERP (KEC-ERP). To use this guide, verify that Kofax Capture is installed on your workstation, and that you have a working knowledge of your computer hardware and operating system. User Interface Notes The user interface and access paths in this guide may differ from those in your environment. The terms Export Connector and Release Script appear interchangeably. What appears depends on the version of Kofax Capture that you have installed. However, the configuration steps are identical. Who Should Read This Guide To use this guide, you should have a thorough understanding of: Windows standards, applications, and interfaces Kofax Capture SAP and its functioning with external DMS Use this guide if you are a system administrator or developer who is configuring Kofax Export Connector for ERP (KEC-ERP). Related Documentation For more information, see: Kofax Export Connector for ERP Features Guide This guide introduces the release scenarios available with KEC-ERP and describes basic concepts about the relationship between Kofax Capture, KEC-ERP, and SAP. Kofax Export Connector for ERP Installation Guide This guide contains instructions and information about installing KEC-ERP. Kofax Export Connector for ERP Release Notes This document describes the latest release of KEC-ERP, identifies outstanding defects and work-around solutions (where applicable), and lists the defects the release fixes. Kofax Export Connector for ERP Administrator's Guide 7

8 Preface Getting Help for Kofax Products Kofax regularly updates the Kofax Support site with the latest information about Kofax products. To access some resources, you must have a valid Support Agreement with an authorized Kofax Reseller/Partner or with Kofax directly. Use the tools that Kofax provides for researching and identifying issues. For example, use the Kofax Support site to search for answers about messages, keywords, and product issues. To access the Kofax Support page, go to The Kofax Support page provides: Product information and release news Click a product family, select a product, and select a version number. Downloadable product documentation Click a product family, select a product, and click Documentation. Access to product knowledge bases Click Knowledge Base. Access to the Kofax Customer Portal (for eligible customers) Click Account Management and log in. To optimize your use of the portal, go to the Kofax Customer Portal login page and click the link to open the Guide to the Kofax Support Portal. This guide describes how to access the support site, what to do before contacting the support team, how to open a new case or view an open case, and what information to collect before opening a case. Access to support tools Click Tools and select the tool to use. Information about the support commitment for Kofax products Click Support Details and select Kofax Support Commitment. Use these tools to find answers to questions that you have, to learn about new functionality, and to research possible solutions to current issues. 8 Kofax Export Connector for ERP Administrator's Guide

9 Chapter 1 Configuring the Export Connector Create and initially configure the batch class. Then, continue at the section that matches your scenario. The following scenarios require customized configurations: Store for Barcode with no Index Fields Store for Subsequent Entry Store with Customer-Defined Transactions Store using XFT Queue Manager Creating and Configuring a Batch Class - Initial Steps Creating a Batch Class 1 From the Kofax Capture Administration menu, click the New Batch Class icon. 2 On the General tab, enter a <batch class name>. 3 Select the Queues tab to see the queues for this batch class. Kofax Export Connector for ERP Administrator's Guide 9

10 Configuring the Export Connector 4 Use the Add and Remove arrows to select the queues for the batch class. 5 Click OK to close the window. Adding a Document Class to the Batch Class 1 On the Batch tab on the left side of the window, right-click the new batch class (for example, Barcode) and select New Document Class. The Create Document Class window opens. 2 On thegeneral tab, enter a <document class name>. 3 Click OK. The new document class appears on the Batch tab on the left side of the window. 10 Kofax Export Connector for ERP Administrator's Guide

11 Configuring the Export Connector Adding KEC-ERP to the Document Class 1 Right-click the <new document class> and select Export Connectors. 2 Select Kofax Export Connector - ERP and click the Add arrow to move Kofax Export Connector - ERP to the list of Assigned Release Scripts. The Kofax Export Connector - ERP configuration window opens. Making Initial Configuration Settings 1 Enter the following data on the General Settings tab in the Kofax Export Connector - ERP configuration window: User Name: the name of a system user who already exists in your SAP system. Password: the password associated with the user. Connection String: This consists of four parts: CLIENT: a 3-digit number that represents the SAP client SYSNR: a 2-digit number that represents the SAP system for connection ASHOST: the IP address or DNS name of the SAP R/3 server LANG: the SAP logon language For example: CLIENT=800 SYSNR=00 ASHOST=r4sap60 LANG=en Kofax Export Connector for ERP Administrator's Guide 11

12 Configuring the Export Connector 2 On the Image tab, in the RFC Settings section, specify the following values: Release Mode Select Save Image in Content Server for typical image release to SAP. Select Pick up Document ID if the document is already released. Select Disable Image Release to disable releasing images to SAP. Image File Type: Select either TIFF or Kofax PDF Files. Working Directory: Specify the directory for temporary storage of images. The system deletes all files in this directory after image processing is completed. Content Repository ID: The Content Repository ID Must match the same of the SAP Content Repository. Click the ellipsis to the right of the Value field and select Text Constant. Set Text Constant to K1. 12 Kofax Export Connector for ERP Administrator's Guide

13 Configuring the Export Connector Doc Type : Specify how SAP stores and displays images. Click the ellipsis to select Index Fields, Batch Fields, Ascent Capture Values, or Text Constant. If you select Text Constant, enter a text value in the Doc Type field. SaveRepDocID in AC, Verify image in content server after upload: If you select these checkboxes, the content server verifies that a physical image is stored. 3 Click OK to close the Kofax Export Connector - ERP configuration window. 4 Continue as follows: To add an index field, go to Adding Index Fields (Optional). If you are not adding an index field, continue at the section that matches your scenario: Configuring a Store Using Barcode with No Index Fields Configuring a Store for Subsequent Entry Configuring a Store with Customer-Defined Transactions Configuring a Store using XFT Queue Manager Adding Index Fields (Optional) The Store for Subsequent Entry and Store Using XFT Queue Manager scenarios require at least the CONF_AR_OBJECT index field. 1 Right-click the new document class and select Properties. 2 Click New Index Field. 3 Enter the Index Field Name. 4 Use the drop-down list to select the Field Type. 5 Click OK to save the new index field and close the window. 6 Continue at the section that matches your store scenario: Configuring a Store Using Barcode with No Index Fields Configuring a Store for Subsequent Entry Configuring a Store with Customer-Defined Transactions Configuring a Store using XFT Queue Manager Configuring a Store Using Barcode with No Index Fields Creating a Barcode Field Type 1 From the Kofax Capture Administration menu, click the New Field Type icon:. The Create Field Type window opens. 2 Select the General tab and enter the following information: Name: Enter a meaningful name for this field type. Description (Optional): Enter a description. Number of characters: Select the number of characters in the barcode. Kofax Export Connector for ERP Administrator's Guide 13

14 Configuring the Export Connector 3 Click Save and Close. Configuring KEC-ERP 1 Right-click the <new document class> and select Export Connectors. 2 In the Export Connectors window, double-click Kofax Export Connector - ERP. The Kofax Export Connector - ERP window opens. 3 On the General tab, in the RFC Settings section, specify the following values: Function Group: Select Z_DICOM_BARCODE. After you select the Function Group, the system populates the Function Name list. Function Name: Select Z_DICOM_STORE_USING_BARCODE. Description (Optional): Enter a description. 4 Select the Parameters tab. 5 Link the index field that contains the barcode to the barcode value as follows. a Double-click the <index field that contains the barcode>. b In the Create a link window, click the ellipsis to the right of the Value field and select Index Fields > Barcode. c Click OK to close the Create a link window. d Click OK to close the Parameters tab. 6 Close the Export Connectors window. 14 Kofax Export Connector for ERP Administrator's Guide

15 Configuring the Export Connector Configuring a Store for Subsequent Entry Before you begin, verify that you created the CONF_AR_OBJECT index field. Configuring KEC-ERP 1 Right-click the <new document class> and select Export Connectors. 2 In the Export Connectors window, double-click Kofax Export Connector - ERP. 3 On the General tab, in the RFC Settings section, specify the following values: Function Group: Select Z_DICOM. After you select the Function Group, the system populates the Function Name list. Function Name: Select any of the available functions. Description (Optional): Enter a description. Kofax Export Connector for ERP Administrator's Guide 15

16 Configuring the Export Connector 4 Select the Parameters tab. 5 Specify which information is passed to the selected function module. The system lists valid parameters and information about each (description, type, length). a Double-click CONF_AR_OBJECT. b In the Create a link window, click the ellipsis to the right of the Value field and select Text Constant. 16 Kofax Export Connector for ERP Administrator's Guide

17 Configuring the Export Connector c Configure the Text Constant as defined in your SAP configuration. d Click OK to close the window. 6 (Optional) On the Scripts tab, specify the acceptable data formats for releasing index fields. Amount fields: The standard formatter converts amounts by replacing the input characters with the corresponding output characters. In the following example, the value 1' changes to 1000,50. Date fields: The standard formatter converts dates by assuming that they are provided in the input format. In the following example, the date "23/11/2004" changes to " ". To customize the behavior of the data formatter, double-click DateConversion or AmountConversion. 7 Repeat this procedure for each document class. Customizing Table Data (Optional) Specify how and if KEC-ERP extracts position table data from XML files. 1 Select the Parameters tab and double-click ITEM_DATA. The Table Links window opens. Kofax Export Connector for ERP Administrator's Guide 17

18 Configuring the Export Connector 2 Select a Data Source: No Table: Creates a single row in the SAP table with links to index fields. 1 Double-click ITEM_ACCOUNT. 2 In the Create a link window, click the ellipsis to the right of the Value field and select Text Constant. Set this field as defined in the SAP configuration. 3 Click OK to close the window. 4 Double-click ITEM_AMOUNT. 5 In the Create a link window, click the ellipsis to the right of the Value field and select Index Fields > Amount. 6 Click OK to close the window. Ascent Table: Uses values from Kofax Capture files in the fist record or an SAP table. XML File: Enables defining the XPath query that retrieves the XML nodes that represent the rows of the table. Analyze the XML format that your recognition engine uses and create the XPath accordingly. XPath queries are case-sensitive. 1 Enter the <XPath expression for table rows>: Kofax for Invoices without Validation: Enter //dokustar/result/index/ table[name="table"]/row[state="tablerow"] Kofax for Invoices with Validation: Enter //DOKuStarValidation/Tables/ Table[@Name="Table"]/Rows/Row Where Table is your table name. 2 Enter the <XML file extension>. 3 Enter the <Text XML path >. 4 Double-click ITEM_AMOUNT, and continue as follows: For Kofax for Invoices without Validation, enter./cell[name = "Amount"]/ value. You may need to change the word "Amount" based on your recognition engine settings. Leave the attribute empty. For Kofax for Invoices with Validation, enter./cells/cell[@name = "Amount"]. You may need to change the word "Amount" based on your recognition engine settings. Set the attribute to Value. 3 Select the <link name> and click New. 4 Close all open windows and repeat this procedure for each document class. Dynamic Transactions Dynamic transactions provide the ability to release two types of documents within one batch. The following function modules are available for dynamic transactions: Z_DICOM_STORE_USING_FB60_MIRO Can release FB60 and MIRO documents. Z_DICOM_STORE_USING_FV60_MIR7 Can release FV60 and MIR7 documents. 18 Kofax Export Connector for ERP Administrator's Guide

19 Configuring the Export Connector Z_DICOM_STORE_USING_FB60_FV60 Can release FB60 and FV60 documents. KEC-ERP selects FB60 and FV60 transactions when the function module cannot find a PO number for the document. If SAP locates a PO number, SAP calls the MIRO and MIR7 transactions for the document. Because dynamic transactions handle two different function modules, they use two sets of configuration parameters for the task, active object, and posting type. Configuring a Store with Customer-Defined Transactions This process uses BDC, including metadata, to create a workitem for a transaction. Configuring KEC-ERP 1 On the General tab, in the RFC Settings section, specify the following values: Function Group: Select Z_DICOM_GENERIC. After you select the Function Group, the system populates the Function Name list. Function Name: Select Z_DICOM_CREATE_WORKITEM_EX. Description (Optional): Enter a description. 2 Select the BDC tab. 3 Select the <text file> created when SAP recorded the transaction. 4 Select the Parameters tab. 5 Verify the values for CONF_AR_OBJECT and CONF_TASKID. Kofax Export Connector for ERP Administrator's Guide 19

20 Configuring the Export Connector 6 Link the BDCDATA table to a Kofax Capture table. 7 Link the index fields as required. 20 Kofax Export Connector for ERP Administrator's Guide

21 Configuring the Export Connector Configuring a Store using XFT Queue Manager Before you begin, verify that you created the CONF_AR_OBJECT index field. Configuring KEC-ERP 1 On the General tab, in the RFC Settings section, specify the following values: Function Group: Select Z_DICOM_XFT. After you select the Function Group, the system populates the Function Name list. Function Name: Select Z_DICOM_STORE_XFT. Description (Optional): Enter a description. 2 Select the Parameters tab. 3 Specify the <Process Type>. The Process Type is a mandatory parameter of the function module, which you can enter using the standard Kofax Capture index link menu. 4 (Optional) Specify the header data: a Double-click the parameter Z_KEYVALUE. b Click Add and enter the <name> and <value> in the index link. 5 (Optional) Specify ProgID of a data formatter class. The data formatter prepares the amount and date fields for the release if necessary. 6 Link the index fields as required. The Store using XFT Queue Manager scenario requires at least the CONF_AR_OBJECT index field. Kofax Export Connector for ERP Administrator's Guide 21

22 Configuring the Export Connector 22 Kofax Export Connector for ERP Administrator's Guide

23 Chapter 2 Store with Barcode This chapter describes how to configure SAP to use the Store with Barcode scenario with no index fields. To configure SAP: Create Global Document Types for the FAX and PDF documents Create Workflow Document Types for these same documents Create Workflow Parameter for these same documents Create the Barcode Type Create the Barcode Entry Create the Content Repository Link Create Object Types Creating Global Document Types 1 Enter transaction code OAC2. The system displays the global document types. 2 Copy and rename an existing global document type. a Select FIINVOICE (for FB60) or select MMIINVOICE (for MIRO) and click the Open icon. Kofax Export Connector for ERP Administrator's Guide 23

24 Store with Barcode b Enter a <new document type name> that matches your SAP custom installation, for example ZDMSI_FB60. c Verify the Document Class. Valid values include FAX, PDF, and TIFF. d Click the green check mark to save the new document type. 3 Repeat this procedure for every global document type. Creating Workflow Document Types 1 In SAP, enter transaction code SOA0. The system displays the workflow document types. 2 Copy and rename an existing workflow document type. a Select FIINVOICE (for FB60) or select MMIINVOICE (for MIRO) and click the Open icon. b Enter a <new document type name> that matches your SAP custom installation, for example ZDMSI_FB60. c Verify the Document Class. Valid values include FAX, PDF, and TIFF. d Click the green check mark to save the new document type. 3 As necessary, use transaction code OAD5 to correct any errors. 4 Repeat this procedure for every workflow document type. Creating Workflow Parameters 1 In SAP, enter transaction code OACA. The system displays the workflow parameters. 24 Kofax Export Connector for ERP Administrator's Guide

25 Store with Barcode 2 Create a new workflow parameter from an existing workflow parameter. Select a <workflow parameter> and click the Open icon. 3 In the Name field, enter Transactioncode. 4 In the Contents field, enter FB60 or another transaction code. Creating Barcode Types 1 In SAP, enter transaction code OAD4. The system displays the barcode types. Kofax Export Connector for ERP Administrator's Guide 25

26 Store with Barcode 2 Define the barcode type required and assign it to a barcode function. For example, assign Code_2_5_1 to the function module ARCHIV_BARCODECHECK_CODE_2_5_1. Creating Barcode Entry 1 In SAP, enter transaction code OAC5. The system displays the settings for barcode entry. 2 Create a new barcode entry with the following information: 26 Kofax Export Connector for ERP Administrator's Guide

27 Store with Barcode Creating a Content Repository Link 1 In SAP, enter transaction code OAC3. 2 Select an existing <content repository> and click the Copy As icon. 3 Enter the <new content repository name>, for example S1 and click Enter 4 In the Link field, enter the <table name> (for example TOA01). Creating Objects 1 In SAP, enter transaction code OBD5. The system displays the object types. Kofax Export Connector for ERP Administrator's Guide 27

28 Store with Barcode 2 Link the document type (for example, ZFIINVOICE) to the Company Code (for example, 1000) and the Document Type (for example, KR for Creditors). 3 Confirm that the system is configured correctly. Use transaction code SE16 and TOAOM to check the object type, document type, content repository. The values should be similar to the values in the following image: 28 Kofax Export Connector for ERP Administrator's Guide

29 Chapter 3 Store for Subsequent Entry This chapter describes how to configure SAP to use the Store for Subsequent Entry feature. Kofax Export Connector for ERP (KEC-ERP) lets you release documents with or without images and index data. This can occur when the images were stored in KEC-ERP or a previous release process. The process for creating business objects is the same for releases with and without images. The following table includes information about the linking. Both release types use a customized business object (Method ZCreateWD). The following are sample KEC-ERP business objects: ZDCM_BKPF (FB60,65...) ZDCM_B2081 (MIRO...) ZWI_BKPF (Generic) Release Required Tasks Transaction with image SWO1 Opening the task PFTC Linking the Image OAD5 (Background) without image Opening the task SWO1 PFTC Configuring SAP for Release with Image When SAP releases an image, KEC-ERP uses the standard SAP ArchiveLink procedure to link the image to the invoice record. The following procedure provides the minimal SAP configuration. You might need additional configuration depending on the customization of your SAP system. To configure SAP to release workitems with images: Create Global Document Classes for FAX, TIFF and PDF (if they do not already exist) Create Business Objects for Transactions Add Transaction Code to business objects Maintain Tasks Link tasks, objects, types and classes Kofax Export Connector for ERP Administrator's Guide 29

30 Store for Subsequent Entry Check the links. Create Workflow Document Types for FAX and PDF documents Create Workflow Parameters Link the document types and object types Create Global Document Types Link document types to original object types Creating Global Document Classes 1 In SAP, enter transaction code OAD2. The system displays the global document classes. 2 Verify that document classes FAX, TIFF, and PDF exist. 3 If the document classes do not exist, click New Entries to create the document classes. Creating Business Objects To release index data, first create the required business objects: ZDCM_BKPF BKPF object plus ZCreateWD (for TA FB60, FB65, FV60, FV65) ZDCM_B2081 BUS2081 object plus ZCreateWD (for TA MIRO, MIR7) 1 In SAP, enter transaction code SWO1. The system displays the business objects. 2 Click Create. The Create Object Type window opens. 3 Enter the Supertype. For Fxxx transactions, enter BKPF. For MIRx transactions, enter BUS Click the green check mark to save the object. 5 Add a new method to the object type. 30 Kofax Export Connector for ERP Administrator's Guide

31 Store for Subsequent Entry 6 When the system prompts you to create with function module as template, click No. 7 Complete the following fields on the General tab in the Change Object Type window. Kofax Export Connector for ERP Administrator's Guide 31

32 Store for Subsequent Entry 8 Use this graphic to complete the fields on the ABAP tab of the Change Object Type window. 9 Enter the following code to call the function: 'Z_DICOM_SHOW_WORKITEM_BASIC' BEGIN_METHOD ZCREATEWD CHANGING CONTAINER. *** Local Variables DATA: TCODE LIKE T020-TCODE. *** Get transaction code from workflow. SWC_GET_ELEMENT CONTAINER 'TransactionCode' TCODE. *** Call wrapper function to display workitem details CALL FUNCTION 'Z_DICOM_SHOW_WORKITEM_BASIC' EXPORTING TCODE = TCODE BUS_OBJECT_NAME = 'ZDCM_BKPF'. *** Check for errors IF SY-SUBRC <> 0. MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. ENDIF. 10 Continue at Adding a Transaction Code. Adding a Transaction Code 1 Click Edit to switch to edit mode. The system displays the business objects. 2 Select the method name you created in Adding a Transaction Code and click Parameters. 32 Kofax Export Connector for ERP Administrator's Guide

33 Store for Subsequent Entry The Display Object Type window opens. 3 Click the New icon. 4 When the system prompts you to create with ABAP Dictionary field proposals, click No. Kofax Export Connector for ERP Administrator's Guide 33

34 Store for Subsequent Entry 5 Use this graphic to complete the fields on the General tab of the Change Object Type window. 6 Click the green arrow to save the transaction code. 7 Change the Method Status to Released: a Select the new method name. b Select Edit > Change Release Status > Object Type Component > implemented. c Select the next status. d Select Edit > Change Release Status > Object Type Component > released. The system displays a success message: 8 Change the Object Status to Released. a Select the first status. b Select Edit > Change Release Status > Object Type > implemented. c Select the next status. d Select Edit > Change Release Status > Object Type > released. 34 Kofax Export Connector for ERP Administrator's Guide

35 Store for Subsequent Entry Maintaining Tasks Two tasks control how SAP links images to records in SAP workitems: TA Entry opens the transaction for data entry. This is task Image Assign assigns the image in the background. This is task Various business objects call the first task, depending on the transaction. For example, FI transactions call the BKPF task and MM transactions call the BUS2081 task. Create your own tasks as follows: 1 In SAP, enter transaction code PFTC and create a new standard task with the following settings. Store with Barcode scenario Business Object = IMAGE Method = IMAGEAssignLate Store with Subsequent Entry scenario Business Object = IMAGE Method = IMAGEAssignEarly 2 Click the green Enter button. 3 Click Yes to transfer missing elements from the object method. 4 Add the structure DCM_DOCDATA to store the index data: a On the Container tab, click Create Element. b Use this graphic to set the values on the D. Type tab: Kofax Export Connector for ERP Administrator's Guide 35

36 Store for Subsequent Entry c Use this graphic to set the values on the Properties tab: 36 Kofax Export Connector for ERP Administrator's Guide

37 Store for Subsequent Entry 5 Select the Terminating Events tab and enter the field values as follows: 6 To define when the workitem will be removed from the user's inbox, click the Call Binding Editor icon with the two green boxes. 7 Save the task. 8 To define which users receive the workitem in their inboxes, select Additional Data > Agent Assignment > Maintain. Kofax Export Connector for ERP Administrator's Guide 37

38 Store for Subsequent Entry 9 Select Attributes > General Task > Transfer. The Standard task: Maintain Agent Assignment window opens. 10 Set the Task value: General Tasks are available to every user. General forwarding allowed tasks are available to every user and can be forwarded. General forwarding not allowed tasks are available to every user but cannot be forwarded. Forwarding not allowed tasks are only available to specific users. 11 Click the Generate Index icon. 38 Kofax Export Connector for ERP Administrator's Guide

39 Store for Subsequent Entry 12 Verify that the footer includes the success message Index was Generated. 13 Save and exit. 14 Repeat this procedure for the second task. 15 Continue at Linking Tasks, Objects, Type and Class. Linking Tasks, Objects, Type and Class SAP transaction code OAD5 allows you to configure all scenarios according to the following table. DocTypes ZDMSI_FB60 ZDMSI_FV60 ZDMSI_FB65 ZDMSI_FV65 ZDMSI FB60 P ZDMSI FV60 P ZDMSI FB65 P ZDMSI FV65 P ZDMSI_MIRO ZDMSI_MIR7 ZDMSI MIRO P ZDMSI MIR7 P ZDMSI_FB10 Business Object Method Class Template ZDCM_BKPF ZCreateWD FAX FIINVOICE ZDCM_BKPF ZCreateWD PDF FIINVOICE ZDCM_B2081 ZCreateWD FAX MMIINVOICE ZDCM_B2081 ZCreateWD PDF MMIINVOICE ZWI_BKPF ZCreateWD FAX FIIINVOICE Image Assign is task TA Entry is task In SAP, enter transaction code OAD5. 2 If the document types do not yet exist, enter the <new document type name>. Kofax Export Connector for ERP Administrator's Guide 39

40 Store for Subsequent Entry 3 In the Doc.type field, enter FIIINVOICE and click Continue. 40 Kofax Export Connector for ERP Administrator's Guide

41 Store for Subsequent Entry 4 If this is a new document type, select Document class and set the value. Valid values are FAX, PDF, or TIFF. 5 Select Object, method and tasks and use this graphic to set the values. 6 Select Workflow parameter. 7 Enter the appropriate <transaction code>. 8 Select Storage system and link table. 9 In the Link field, select TOA01. Kofax Export Connector for ERP Administrator's Guide 41

42 Store for Subsequent Entry 10 Click Complete to save the settings. 11 To verify that the configuration tool wrote the document class properly to the table TOAOM, go to Checking the Links. Checking the Links 1 In SAP, enter transaction code SE16. The Data Browser: Initial Screen opens. 2 In the Table Name field, enter TOAOM and click Enter. The Data Browser: Table TOAOM: Selection Screen opens. 42 Kofax Export Connector for ERP Administrator's Guide

43 Store for Subsequent Entry 3 Click the Execute icon. The Select Entries window opens. 4 Verify that all configuration settings are correct, including the document type. Correct any errors: If you have the proper permissions, correct errors directly in the table. Otherwise, use the correct transaction code to correct the errors. Kofax Export Connector for ERP Administrator's Guide 43

44 Store for Subsequent Entry Creating Workflow Document Types 1 In SAP, enter transaction SOA0. 2 Select a Document Type and click the Open icon. 3 Add new criteria as displayed in the following graphic. Enter the document types as defined by your custom SAP installation. 4 Click Choose to confirm the selection. The list should look similar to the following: 44 Kofax Export Connector for ERP Administrator's Guide

45 Store for Subsequent Entry 5 Double-click a Doc. Type to view the contents. For example, the following shows the ZDMSIFB60P configuration. 6 As necessary, use transaction code OAD5 to correct any errors. 7 Repeat this procedure for every document type. Creating Workflow Parameters Use workflow parameters to configure transaction codes for every work item. The transaction code triggers the corresponding transaction for the relevant posting data (FB60 / MIRO). 1 Select a Document Type and click Append. 2 Add new criteria as displayed in the following graphic. Enter the document types as defined by your custom SAP installation. 3 Click Choose to confirm the selection. The list should look similar to the following: Kofax Export Connector for ERP Administrator's Guide 45

46 Store for Subsequent Entry 4 As necessary, use transaction code OAD5 to correct any errors. Creating Global Document Types 1 Enter transaction code OAC2. The system displays the global document types. 2 Copy and rename an existing global document type. a Select FIINVOICE (for FB60) or select MMIINVOICE (for MIRO) and click the Open icon. b Enter a <new document type name> that matches your SAP custom installation, for example ZDMSI_FB60. c Verify the Document Class. Valid values include FAX, PDF, and TIFF. d Click the green check mark to save the new document type. 3 Repeat this procedure for every global document type. 46 Kofax Export Connector for ERP Administrator's Guide

47 Store for Subsequent Entry Linking a Document Type to an SAP Object Type 1 In SAP, enter transaction code OAC3. 2 Select an existing <content repository> and click the Copy As icon. 3 Edit the object type: For FB60, enter BKPF. For MIRO, enter BUS Click Enter. 5 In the Link field, enter the <table name> (for example TOA01). 6 If necessary, use transaction code OAD5 to correct any errors. 7 Repeat this procedure for each document type. Configuring SAP for Release without Images To configure SAP to release workitems without images: Create Business Objects for Transactions Maintain Tasks Kofax Export Connector for ERP Administrator's Guide 47

48 Store for Subsequent Entry Creating Business Objects To release index data, first create the required business objects: ZDCM_BKPF BKPF object plus ZCreateWD (for TA FB60, FB65, FV60, FV65) ZDCM_B2081 BUS2081 object plus ZCreateWD (for TA MIRO, MIR7) 1 In SAP, enter transaction code SWO1. The system displays the business objects. 2 Click Create. The Create Object Type window opens. 3 Enter the Supertype. For Fxxx transactions, enter BKPF. For MIRx transactions, enter BUS Click the green check mark to save the object. 5 Add a new method to the object type. 6 When the system prompts you to create with function module as template, click No. 7 Complete the following fields on the General tab in the Change Object Type window. 48 Kofax Export Connector for ERP Administrator's Guide

49 Store for Subsequent Entry 8 Use this graphic to complete the fields on the ABAP tab of the Change Object Type window. 9 Enter the following code to call the function: 'Z_DICOM_SHOW_WORKITEM_BASIC' Kofax Export Connector for ERP Administrator's Guide 49

50 Store for Subsequent Entry BEGIN_METHOD ZCREATEWD CHANGING CONTAINER. *** Local Variables DATA: TCODE LIKE T020-TCODE. *** Get transaction code from workflow. SWC_GET_ELEMENT CONTAINER 'TransactionCode' TCODE. *** Call wrapper function to display workitem details CALL FUNCTION 'Z_DICOM_SHOW_WORKITEM_BASIC' EXPORTING TCODE = TCODE BUS_OBJECT_NAME = 'ZDCM_BKPF'. *** Check for errors IF SY-SUBRC <> 0. MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. ENDIF. Maintaining Tasks Because Kofax does not deliver tasks with the business objects in our transports, you must create tasks. The business object of the task must be in line with the transaction to be called. To make sure captured index data are properly filled into the transaction fields, use the customized business object and the ZCreateWD open method. As there are no ArchiveLink components involved, you can call the Z_DICOM_STORE_USING_XX modules by passing the taskid. No image-related information (Archiv, ArchivObject and DocType) is required. 50 Kofax Export Connector for ERP Administrator's Guide

51 Chapter 4 Generic Transactions This chapter describes how to configure SAP to use the Generic Transactions feature. The Generic Transactions feature creates a large variety of transactions and is implemented with a generic export connector. The generic export connector enables you record a transaction in SAP. Kofax Export Connector for ERP (KEC-ERP) includes samples for the BKPF business object, however you can also configure transactions for other objects. Configuring SAP for Customer-Defined Transactions with Images The following procedure creates a generic release for the FB10 transaction. Use the same process to create generic releases for other transactions. 1 Create a recording of transaction FB10. a From SAP enter transaction code SHDB. b Select transaction code FB10 and click Start Recording. c Make the recording. Include place holder values in every field that you want Kofax Capture to fill. d Click the green check mark to save the recording. e Click the yellow Exit button to stop the recording. f If the system displays a message that data will be lost, click Yes. The recording should look similar to the following: Kofax Export Connector for ERP Administrator's Guide 51

52 Generic Transactions 2 Select Recording > Export and save the recording to a text file. 3 Create a new doc type and link it to the corresponding tasks. Document Type: ZDMSI_FB10 Name: Leave this field empty. Document Type Template: Leave this field empty. Workflow Document Type: Select this checkbox. Object, Method and Tasks: Workflow Parameter: FB10 The settings for preselection are relevant. Note There is a different Object Type available for the generic release, however, the tasks and methods are the same as for the standard Fxxx and MIRX scenarios. 4 Enter transaction code SE16. 5 In the Table Name field, enter TOAOM and click Enter. The system displays the table data. 6 Verify that all configuration settings are correct, including the document type. Correct any errors: If you have the proper permissions, correct errors directly in the table. Otherwise, use the correct transaction code to correct the errors. 7 Repeat this procedure to create generic releases for other transactions. Configuring SAP for Customer-Defined Transactions without Images When releasing without images, you can ignore all ArchiveLink settings and call one task. The task configuration required is similar to the 'no image' tasks for the Fxxx and MIRX transactions, but you may need business object ZWI_BKPF. 52 Kofax Export Connector for ERP Administrator's Guide

53 Generic Transactions Configuring SAP for Customer-Defined Non-BKPF Transactions 1 Create a new business object from an existing business object. For example, copy the ZCreateWD method from the ZWI_BKPF business object. 2 Select the business object you created in step 1 in the OAD5 linking process (if releasing with an image) or when creating a new task (if releasing without images). If you are creating a new task, use object settings similar to the TS transaction. 3 Adjust the terminating events. If you do not adjust the terminating events, the system does not delete the workitem from an inbox after the transaction is saved. Kofax Export Connector for ERP Administrator's Guide 53

54 Generic Transactions 54 Kofax Export Connector for ERP Administrator's Guide

55 Chapter 5 XFT Queue Manager Use function module Z_DICOM_STORE_XFT to configure Kofax Export Connector for ERP (KEC-ERP) to work with the XFT Queue Manager. ( The Z_DICOM_STORE_XFT function module rearranges Kofax Capture parameters to suit XFT and calls the XFT function module. Before you configure SAP, follow the steps in these sections: Creating and Configuring a Batch Class - Initial Steps on page 9 Customizing SAP Configuring a Store using XFT Queue Manager KEC-ERP uses the remote function module Z_DICOM_STORE_XFT to write data into an XFT queue. Each document in the XFT queue has one entry. This entry releases all of the index values in a key/value table. As displayed in the following diagram, Kofax Capture calls an intermediate function, Z_DICOM_STORE_XFT, that interacts with the original XFT function to create a queue entry. No additional SAP configuration is required. Content Repository with More than Two Characters SAP ArchiveLink content repository names have a maximum length of two characters. However, because no ArchiveLink functions are used to communicate with XFT, the content repository name can be up to 30 characters. Content repository names are case sensitive. 1 Save the content repository with a new name. If you use a name that is longer than two characters, the system displays the following warning message. Kofax Export Connector for ERP Administrator's Guide 55

56 XFT Queue Manager 2 Click Enter to clear the message. The system displays another message: The system successfully creates the repository. 56 Kofax Export Connector for ERP Administrator's Guide

57 Chapter 6 PDF Files To enable the release of Kofax PDF files: Add the PDF Generator as a module to the batch class. Configure KEC-ERP. Adding the PDF Generator as a Module to the Batch Class 1 From the Kofax Capture Administration menu, right-click the Batch Class and select Properties. The Create Batch Class window opens. 2 On the Queues tab in the list of Available Queues, select PDF Generator and click Add. 3 Save and close the Create Batch Class window. Configuring KEC-ERP 1 From the Kofax Capture Administration menu, right-click the Batch Class and select Properties. The Batch Class Properties window opens. 2 Select the Image tab. 3 In the Image File Type field, select Multipage - Kofax PDF Files. 4 In the Doc Type field, select PDF. 5 Select the Parameters tab. 6 Add the workflow program name for PDF files (according to your SAP ArchiveLink configuration). 7 Save and close the Document Class Properties window. Kofax Export Connector for ERP Administrator's Guide 57

58 PDF Files 58 Kofax Export Connector for ERP Administrator's Guide

59 Chapter 7 Supported Index Fields This chapter describes which SAP transaction index fields Kofax Capture supports and how to match the SAP transaction index fields with the Kofax Kofax Capture. The parameters list displays the valid parameters for the selected SAP function module and information about each parameter (description, type, length). Kofax Export Connector for ERP Administrator's Guide 59

60 Supported Index Fields Index Field Prefixes and Names Index fields include a prefix and a name. Prefix The prefix matches the tab names in SAP. For example, for transaction code FB60, the prefix values include: BSC: basic data PYT: Payment DTL: Details TAX: Tax NTS: Notes CONF: Configuration Details Name The name is an abbreviation based on the parameter description. For example, for transaction code FB60, the parameter field names include: BSC_INVOICE_DATE: Invoice Date BSC_POSTING_DATE: Posting date BSC_POSTING_TYPE: Posting type PYT_AMOUNT: Payment Amount PYT_BASELINE_DATE: Baseline date for due date calculation DTL_ASSIGN_NO: Assignment number as additional information reference field in the line item DTL_BUS_AREA: Business area TAX_AMOUNT: Tax amount in document currency TAX_CODE: Tax code 60 Kofax Export Connector for ERP Administrator's Guide

61 Supported Index Fields MIRO Fields For MIRO releases, three line item values are released to SAP. The other line item values are retrieved from SAP. The released line item values are: Item_Quantity Item_Measure_Unit Item_Amount To enable SAP to update these values, pass the article number to SAP so that the line items can be correctly matched. If the line items do not match, or if the invoice item number cannot be found in SAP, SAP displays a "General error" message. This limited release of line item values does not occur for FB60 which releases all values to SAP. Kofax Export Connector for ERP Administrator's Guide 61

62 Supported Index Fields 62 Kofax Export Connector for ERP Administrator's Guide

63 Chapter 8 Passing Document IDs The Kofax Capture framework from which KEC-ERP can save the document ID for use by another export connector. KofaxKofax Capture calls this ID the Repository Document ID. In the Administration module you can link the Repository Document ID to any parameter of the selected function module. This chapter describes how to configure passing the document ID of a released document to another export connector. Releasing the Document ID to Another Export Connector The Repository Document ID from one export connector can be linked to a parameter in another export connector. KEC-ERP replaces the parameter value in another export connector with the Repository Document ID. The export connector will not verify whether the Repository Document ID is valid. If the Repository Document ID does not exist, the parameter will be empty. The function module ensures that the parameter is correctly processed. Because the standard function modules do not evaluate the Repository Document ID they do not report any Repository Document ID errors. It is possible to pass the Archive Object ID of a newly created document to another export connector. This feature allows you to write an export connector that locates the document in the archive system in order to add index information to this document. Kofax Capture allows only one export connector to update the Repository Document ID of a document class. KEC-ERP only updates the Repository Document ID with the archive document ID if the following are true: Direct Image Upload is selected Save RepDocID in AC is selected Repository Document ID is empty 1 In the Release Script window, select the Image tab. 2 Select Save RepDocID in AC. 3 Save and close the Release Script configuration window. Kofax Export Connector for ERP Administrator's Guide 63

64 Passing Document IDs 4 Add a second export connector to the batch class. a Select the second export connector and click Setup. b Add an index field to be released. Set the Index Value to Repository Document ID. c Save and close the Release Script configuration window. Passing the Document ID to a Function Parameter KEC-ERP can extract the archived document ID from the RepositoryDocID field of a previous release script or export connector. 1 Right-click the <document class> and select Release Scripts or Export Connectors. The configuration window opens. 2 In the Assigned column, double-click Kofax Export Connector - ERP. 3 Select the Image tab. 64 Kofax Export Connector for ERP Administrator's Guide

65 Passing Document IDs 4 Select Pick up Document Repository ID. 5 Enter the <Content Repository ID>. 6 Enter the <Doc Type>. 7 Click Save and close the window. Kofax Export Connector for ERP Administrator's Guide 65

66 Passing Document IDs 66 Kofax Export Connector for ERP Administrator's Guide

67 Chapter 9 Disabling Image Release The standard function modules in Kofax Export Connector for ERP (KEC-ERP) support the release of index field data without images. If the image release is disabled, KEC-ERP does not connect to any content repository, nor is the image transferred to SAP or any server. By default, image release is enabled and existing batch classes can be used without changes. If you disable image release, set CONF_TASKID. You do not need to set the following parameters when you disable image release: CONF_ARCHIV_I CONF_DOC_TYPE CONF_AR_OBJECT 1 Right-click the <document class> and select Release Scripts or Export Connectors. The configuration window opens. 2 In the Assigned column, double-click Kofax Export Connector - ERP. 3 Select the Image tab. 4 Select Disable Image Release. 5 Select the Parameters tab. 6 Set the value for the CONF_TASKID parameter. If you disable the image release, the task ID is mandatory and must match the task ID you created when you customized SAP for your scenario: a Double-click CONF_TASKID. The Create a link window opens. b Click the ellipsis to the right of the Value field and select Text Constant. The value of this field varies based on the Function module. Kofax Export Connector for ERP Administrator's Guide 67

68 Disabling Image Release c Enter a text value as defined in the SAP configuration. d Click OK to close the Create a link window. 68 Kofax Export Connector for ERP Administrator's Guide

69 Appendix A Troubleshooting Kofax Capture includes troubleshooting tools. SAP includes additional troubleshooting tools. This appendix describes both tool sets. Kofax Troubleshooting Tools Log Files If you cannot immediately determine why a release fails, turn on debug mode in the batch release: 1 Turn on Debug Mode. In KEC-ERP, select the Tracing tab and click Activate. 2 Process a batch. If there is an error, the system sends the batch to the Kofax Quality Control module and may also display an error message in the bottom frame of the Kofax Quality Control module. 3 Review the detailed log files. KEC-ERP generates three log files. kcec-erp-trace-release-yyyymmdd.txt - This log includes information about images KEC- ERP sends to SAP. kcec-erp-trace-admin-yyyymmdd.txt - This log includes information about configuring KEC-ERP. dev_rfc.trc - The system creates this file in the Kofax Capture application folder. This file includes all the SAP error messages. The following is a sample kcec-erp-trace-release-yyyymmdd.txt log file. Logging started at :34:20 on 'NBROR' for 'release.exe'. Version of DicomPS.ERP.ReleaseScript.dll: OpenScript enter Lock license. Opening RFC connection with user 'kofax' Connection string: CLIENT=800 SYSNR=00 ASHOST=sap47 LANG=de Opening RFC connection with user 'kofax' Connection string: CLIENT=800 SYSNR=00 ASHOST=sap47 LANG=de OpenScript exit ReleaseDoc :34:22 Step 1: Upload image. performfilerelease enter Uploading image to content server. TIFF release enabled. transferimage enter Defining import parameter 'FUNCNAME' with value 'Z_DICOM_DOC_URL_CREATE'. Defining table 'PARAMS' with 0 rows. Kofax Export Connector for ERP Administrator's Guide 69

70 Troubleshooting Defining table 'TABLE_PARAMS' with 0 rows. Calling function module 'Z_DICOM_LISTPARAMS' RFC Return Code = RFC_OK ExecuteFunction enter Defining import parameter 'CONF_ARCHIV_ID' with value 'S1'. Defining import parameter 'CONF_DOCTYPE' with value 'FAX'. Defining export parameter 'ARCHIV_DOC_ID'. Defining export parameter 'MIMETYPE'. Defining table 'ZURL_ROWS' with 0 rows. Calling function module 'Z_DICOM_DOC_URL_CREATE' RFC Return Code = RFC_OK Read export parameter 'ARCHIV_DOC_ID' with value '31219DC638BFD BDBB4E63C26'. Read export parameter 'MIMETYPE' with value 'image/tiff'. Read table 'ZURL_ROWS' with 5 rows. ExecuteFunction exit - upload url (truncated): contentserver.dll - mime type: image/tiff - document id: 31219DC638BFD BDBB4E63C26 httpupload enter Opening source file. Creating HTTP request. Starting to read blocks and write them to the HTTP stream. httpupload exit transferimage exit Image uploaded successfully. Image verification is disabled. Delete temporary file. XXXperformFileRelease exit Step 2: Call function module. callfunctionmodule enter Defining import parameter 'FUNCNAME' with value 'Z_DICOM_STORE_USING_FB60'. Defining table 'PARAMS' with 0 rows. Defining table 'TABLE_PARAMS' with 0 rows. Calling function module 'Z_DICOM_LISTPARAMS' RFC Return Code = RFC_OK ExecuteFunction enter Defining import parameter 'ARCHIV_DOC_ID' with value '31219DC638BFD BDBB4E63C26'. Defining import parameter 'BSC_INVOICE_NO' with value '07326'. Defining import parameter 'CONF_ARCHIV_ID' with value 'S1'. Defining import parameter 'CONF_AR_OBJECT' with value 'ZDMSI_FB60'. Defining import parameter 'CONF_DOC_AVAILABLE' with value 'X'. Defining import parameter 'CONF_DOC_TYPE' with value 'FAX'. Defining table 'ITEM_DATA' with 0 rows. Calling function module 'Z_DICOM_STORE_USING_FB60' RFC Return Code = RFC_OK Read table 'ITEM_DATA' with 1 rows. ExecuteFunction exit callfunctionmodule exit ReleaseDoc :34:24 CloseScript enter Closing RFC connection. Release license. CloseScript exit Note If a batch goes to the Kofax Quality Control Module, entries appear in both thekec- ERP log and the Kofax Capture Quality Control log. The KEC-ERP log files include the entire error message. Kofax Capture Quality Control Module log files generally do not include the entire error message. 70 Kofax Export Connector for ERP Administrator's Guide

71 Troubleshooting SAP Troubleshooting Tools Use these tools to diagnose possible errors in SAP customization. Archive System Availability The following example uses the SAP HTTP Content Server. If you use another SAP ArchiveLink-certified archive system, verify that the configuration selects correct content repository and that the repository is available. 1 Test the SAP HTTP Content Server connection: a Enter transaction code OAC0. b Double-click your content repository, for example, S1. c Click the Test Connection icon. SAP displays the test result. For example, a successful test returns this message: 2 Test the SAP HTTP Content Server function: a Enter transaction code OAC0. b Double-click your content repository, for example, S1. Kofax Export Connector for ERP Administrator's Guide 71

72 Troubleshooting c Click CS Admin. d Select the Overview tab and verify that the HTTP Content Server is running. If the HTTP Content Server is running, a green light appears in the Cust. column. e f Select the Details tab and verify that the HTTP Content Server is running. If the HTTP Content Server is running, a green light appears in the Cust. column. Select the Certificates tab and verify that the certificates are valid. 72 Kofax Export Connector for ERP Administrator's Guide

73 Troubleshooting g Select the Settings tab and verify that the fields are populated similar to the following graphic. h Press F8 to execute the test. i Enter the repository data and the front and back end paths. j Click the Execute icon. Green lights indicate that the tests were successful. 3 Test the archive system function. For DMS to be ArchiveLink-certified, this test must run successfully. a Enter transaction code SE38. b Enter the program rscmst. c Select Source Code. d Press F8 to execute the test. e Enter the repository data and the front and back end paths. Kofax Export Connector for ERP Administrator's Guide 73

74 Troubleshooting f Click the Execute icon. Green lights indicate that the tests were successful. 4 Correct the settings and rerun these tests as needed. Workflow Test 1 Enter transaction code OAWD. 2 Click the icon to the left of Incoming invoice w/o verification DICOM. 3 Enter the file name. 4 Enter transaction code SBWP. SAP creates a workitem for subsequent entry > no data. 5 Check the test results. If this test fails, check the ArchiveLink customization. 74 Kofax Export Connector for ERP Administrator's Guide

75 Troubleshooting User Profile Test 1 Enter transaction code SU01. The user maintenance window opens. 2 Enter the User profile and click the Display icon. 3 Use the following graphic to verify the settings on the Logon data tab: Kofax Export Connector for ERP Administrator's Guide 75

76 Troubleshooting Workitem Technical Location Test If the workitem contents contains any errors, view the workitem contents in SAP. 1 Click Display Workflow Log. 2 Press F9 to list with technical details. 3 Click the Show Container icon. 76 Kofax Export Connector for ERP Administrator's Guide

77 Third-Party License Agreements BEA Public License Version 2.1 TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1 Definitions. License shall mean the terms and conditions of this agreement. Licensor shall mean BEA Systems, Inc. Legal Entity shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, control means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. You (or Your ) shall mean an individual or Legal Entity exercising permissions granted by this License, including but not limited to each Contributor other than Licensor in such Contributor s role as a licensee for the Software. Source Format shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. Object Format shall mean any form resulting from mechanical transformation or translation of a Source Format, including but not limited to compiled object code, generated documentation, and conversions to other media types. Software shall mean the original version of the software accompanying this agreement as released by BEA, including in Source or Object Format, and also any documentation provided therewith. Derivative Works shall mean any work, whether in Source or Object Format, that is based on (or derived from) the Software and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Software and derivative works thereof. Contribution shall mean any work of authorship, including the original version of the Software and any modifications or additions to that Software or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Software by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, submitted means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Software, but Kofax Export Connector for ERP Administrator's Guide 77

78 Third-Party License Agreements excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as Not a Contribution. Contributor shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Software. 2 Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Software and such Derivative Works in Source or Object Format. Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the foregoing copyright license. 3 Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Software, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Software to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Software or a Contribution incorporated within the Software constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Software shall terminate as of the date such litigation is filed. 4 Redistribution. You may reproduce and distribute copies of the Software or Derivative Works thereof in any medium, with or without modifications, and in Source or Object Format, provided that You meet the following conditions: You must give any other recipients of the Software or Derivative Works a copy of this License; and You must cause any modified files to carry prominent notices stating that You changed the files; and You must retain, in the Source Format of any Derivative Works that You distribute, BEA s copyright notice, [Date] BEA Systems, Inc. All rights Reserved., and all other copyright, patent, trademark, and attribution notices from the Source Format of the Software, excluding those notices that do not pertain to any part of the Derivative Works; and You must affix to the Software or any Derivative Works in a prominent manner BEA s copyright notice, ( [Date] BEA Systems, Inc. All rights Reserved. whenever You distribute the Software or such Derivative Works in Object Format. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Software otherwise complies with the conditions stated in this License. 5 Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Software by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 78 Kofax Export Connector for ERP Administrator's Guide

79 Third-Party License Agreements 6 Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Software and reproducing the content of the NOTICE file. 7 Disclaimer of Warranty. EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE SOFTWARE IS PROVIDED ON AN AS IS BASIS, WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using and distributing the Software and assume all risks associated with Your exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations. Further, You understand that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that its Contribution does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to You for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, You hereby assume sole responsibility to secure any other intellectual property rights needed, if any. 8 Limitation of Liability. EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NO CONTRIBUTOR SHALL HAVE ANY LIABILITY TO YOU FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE SOFTWARE OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 9 Accepting Warranty or Additional Liability. Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Software, if You include the Software in a commercial product offering, You may do so only in a manner which does not create potential liability for any Contributor. Therefore, if You include the Software in a commercial product offering, You shall and hereby do agree to defend and indemnify each and every Contributor against any losses, damages and costs (collectively Losses ) arising from claims, lawsuits and other legal actions brought by a third party against such Contributor(s) to the extent caused by Your acts or omissions in connection with Your distribution of the Software in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify to receive indemnification from You, a Contributor must: a b promptly notify You in writing of such claim, and allow the You to control, and cooperate with the You in, the defense and any related settlement negotiations. The Contributor indemnified by You may participate in any such claim at its own expense. Kofax Export Connector for ERP Administrator's Guide 79

80 Third-Party License Agreements 80 Kofax Export Connector for ERP Administrator's Guide

81 Index A active objects, 18 admin log file, 69 amount formats, 15 article number, 61 Ascent tables, subsequent entry, 17 ASHOST, 11 B barcode with no index, barcode entries, 26 barcode types, 25 business objects, 27 configuring KEC-ERP, 13 configuring SAP, 23 content repository links, 27 workflow document types, 24 workflow parameters, 24 barcode, length, 15 batch classes, creating, 9 document classes, 10 index fields, 13 initial configuration, 11 PDF generator, 57 BDC, 19 BKPF, subsequent entry with image, 30 subsequent entry without image, 48 BUS2081, subsequent entry with image, 30 subsequent entry without image, 48 business objects, barcode with no index, 27 customer-defined non-bkpf transactions, 53 customer-defined transactions without images, 52 subsequent entry, 29 subsequent entry with image, 30 subsequent entry without image, 48 C CLIENT, 11 CMS_DOCUMENTS table, 55 CONF parameters, disabling image release, 67 CONF_AR_OBJECT, 67 batch classes, 13 subsequent entry, 15 XFT Queue Manager, 21 CONF_ARCHIV_I, 67 CONF_DOC_TYPE, 67 CONF_TASKID, 67 connection string, 11 content repository links, barcode with no index, 27 subsequent entry with image, 47 content repository names for XFT, 55 D data formats, 15 data formatter, XFT Queue Manager, 21 date formats, 15 debug mode, 69 dev_rfc.trc log file, 69 DIO_DIC_INPUT_CREATE, 55 Direct Image Upload, 63 document classes, 10 KEC-ERP, 11 document IDs, releasing to export connector, 63 releasing to function parameter, 64 document types, subsequent entry with image, 47 dynamic transactions, 18 E error logs, 69 export connector/release script, 7 F FIINVOICE, 39 function modules, 18 G global document classes, 30 global document types, 23, 46 H help for Kofax products, 8 I image assign, 39 image release disabling, 67 index fields, 59 batch classes, 13 Kofax Export Connector for ERP Administrator's Guide 81

82 Index prefixes and names, 60 ITEM tables, subsequent entry, 17 Item_Amount, 61 Item_Measure_Unit, 61 Item_Quantity, 61 K kcec-erp-trace-admin log, 69 kcec-erp-trace-release log, 69 KERPR, 55 KEYVALUE table, 55 L LANG, 11 license agreements, 77 log files, 69 M Method ZCreateWD, 29 MMIINVOICE, 39 N number formats, 15 P PDF generator, adding to batch class, 57 configuring KEC-ERP, 57 posting type, 18 PROPERTIES table, 55 Q queues, 9 R recording transactions, customer-defined non-bkpf transactions, 53 with images, 51 without images, 52 release log file, 69 release mode, 11 release script, 7 RepDocID, 63 Repository Document ID, 63 ROWKEYVALUE table, 55 S Store for Subsequent Entry, index field, 13 Store Using XFT Queue Manager, index field, 13 subsequent entry, configuring KEC-ERP, 15 configuring SAP, 29 subsequent entry with image, business objects, 30 content repository links, 47 global document classes, 30 linking document types, 47 links, 39 tasks, 35 transaction codes, 32 validating, 42 workflow document types, 44 workflow parameters, 45 subsequent entry without image, business objects, 48 tasks, 50 support site, 8 SYSNR, 11 T TA entry, 39 tables, 55 BDCDATA, 19 tables, subsequent entry, 17 tasks, subsequent entry with image, 35 subsequent entry without image, 50 templates, 39 terminating events, 53 testing SAP, 71 trace-admin log, 69 trace-release log, 69 tracing, 69 transaction codes, subsequent entry with image, 32 transactions, recording, 51 V validating subsequent entry with image, 42 W workflow document types, barcode with no index, 24 subsequent entry with image, 44 workflow parameters, barcode with no index, 24 subsequent entry with image, 45 SAP, testing, 71 Save RepDocID in AC, Kofax Export Connector for ERP Administrator's Guide

83 Index X XFT Queue Manager, 21, 55 XML nodes, subsequent entry, 17 Z Z_DICOM, subsequent entry, 15 Z_DICOM_BARCODE, barcode no index, 13 Z_DICOM_STORE_USING_BARCODE, barcode no index, 13 Z_DICOM_STORE_XFT, 55, 55 ZCreateWD, 29 subsequent entry with image, 30 subsequent entry without image, 48 ZDCM_B2081, 29 ZDCM_BKPF, 29 subsequent entry with image, 30 subsequent entry without image, 48 ZWI_BKPF, 29 customer-defined transactions without images, 52 Kofax Export Connector for ERP Administrator's Guide 83

84 Index 84 Kofax Export Connector for ERP Administrator's Guide