Kofax Export Connector for ERP 2.4.
Portions © 2004-2013 Kofax, Inc., 15211 Laguna Canyon Road, Irvine, California 92618, U.S.A. Portions © 2002-2006 Kofax Development GmbH. Portions © 1997-2006 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.
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) 2008-2013, 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.
Contents Preface .................................................................................................................................................................................... 7 User Interface Notes ....................................................................................................................................................... 7 Who Should Read This Guide ..............................................................................................................
Contents Maintaining Tasks .................................................................................................................................................... 35 Linking Tasks, Objects, Type and Class ............................................................................................................... 39 Checking the Links ..................................................................................................................................................
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.
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 www.kofax.
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 .
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 . 3 Click OK. The new document class appears on the Batch tab on the left side of the window.
Configuring the Export Connector Adding KEC-ERP to the Document Class 1 Right-click the 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.
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.
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.
Configuring the Export Connector 3 Click Save and Close. Configuring KEC-ERP 1 Right-click the 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.
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 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.
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.
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'000.50” changes to “1000,50” .
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.
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 the Export Connector 6 Link the BDCDATA table to a Kofax Capture table. 7 Link the index fields as required.
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.
Configuring the Export Connector 22 Kofax Export Connector for ERP Administrator's Guide
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.
Store with Barcode b Enter a 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.
Store with Barcode 2 Create a new workflow parameter from an existing workflow parameter. Select a 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.
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.
Store with Barcode Creating a Content Repository Link 1 In SAP, enter transaction code OAC3. 2 Select an existing and click the Copy As icon. 3 Enter the , for example S1 and click Enter 4 In the Link field, enter the (for example TOA01). Creating Objects 1 In SAP, enter transaction code OBD5. The system displays the object types.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.
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.
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.
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.
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.
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.
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.
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 80000142. ▪ Image Assign assigns the image in the background. This is task 80000141. 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.
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
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.
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.
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.
Store for Subsequent Entry 3 In the Doc.type field, enter FIIINVOICE and click Continue.
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 . 8 Select Storage system and link table. 9 In the Link field, select TOA01.
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.
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.
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.
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.
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 that matches your SAP custom installation, for example ZDMSI_FB60. c Verify the Document Class.
Store for Subsequent Entry Linking a Document Type to an SAP Object Type 1 In SAP, enter transaction code OAC3. 2 Select an existing and click the Copy As icon. 3 Edit the object type: ▪ For FB60, enter BKPF. ▪ For MIRO, enter BUS2081. 4 Click Enter. 5 In the Link field, enter the (for example TOA01). 6 If necessary, use transaction code OAD5 to correct any errors. 7 Repeat this procedure for each document type.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 BUS2081.
Store for Subsequent Entry 8 Use this graphic to complete the fields on the ABAP tab of the Change Object Type window.
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.
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.
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.
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 TS80000145 transaction. 3 Adjust the terminating events.
Generic Transactions 54 Kofax Export Connector for ERP Administrator's Guide
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. (www.xft.de). The Z_DICOM_STORE_XFT function module rearranges Kofax Capture parameters to suit XFT and calls the XFT function module.
XFT Queue Manager 2 Click Enter to clear the message. The system displays another message: The system successfully creates the repository.
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.
PDF Files 58 Kofax Export Connector for ERP Administrator's Guide
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).
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.
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.
Supported Index Fields 62 Kofax Export Connector for ERP Administrator's Guide
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.
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.
Passing Document IDs 4 Select Pick up Document Repository ID. 5 Enter the . 6 Enter the . 7 Click Save and close the window.
Passing Document IDs 66 Kofax Export Connector for ERP Administrator's Guide
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.
Disabling Image Release c Enter a text value as defined in the SAP configuration. d Click OK to close the Create a link window.
Appendix A Troubleshooting Kofax Capture includes troubleshooting tools. SAP includes additional troubleshooting tools. This appendix describes both tool sets. Kofax Troubleshooting Tools 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.
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.
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.
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 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. f Select the Certificates tab and verify that the certificates are valid.
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.
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.
Troubleshooting User Profile Test 1 Enter transaction code SU01. The user maintenance window opens. 2 Enter the User profile and click the Display icon.
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.
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.
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. Grant of Copyright License.
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.
Third-Party License Agreements 80 Kofax Export Connector for ERP Administrator's Guide
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,
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 w
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
Index 84 Kofax Export Connector for ERP Administrator's Guide
