In the Document Type Definition Overview screen, double-click a document type

3. Define the document type, using the following parameters.

Document Type Definition group Description

Enter the document type description.

Document Index Type

Select the type of indexing to determine how the system determines the origin of data. The following values are available:

Indexing using OCR

Use this option if the document is scanned and the OCR interface passes the data to SAP for creating an OpenText document.

Online Indexing

Use this option if archiving a document using the SAP ArchiveLink Early Archiving process. Indexing is manual and the person responsible maintains the data and submits for further processing.

No Indexing

Use this option if there is no indexing required and the document is directly processed. Use this option if there is no scanned image and the process is triggered using an API provided by OpenText.

Indexing using Idoc

This is not supported at the moment.

Invoice Type

Decide whether the document generates a Non PO Invoice or a PO Invoice.

Number Range

Enter the number range for the number range object. If a custom number range object is not defined in global configuration, you can maintain the number range for object /OPT/DOCID in the Maintain Number Ranges step, see “Configuring Global Parameters” on page 115.

SAP FI DocType

To determine the SAP document type in the background, enter a fixed document type or a custom function module.

If you use a function module, enter FM:<FunctionModuleName>. As the interface for the function module, use the template

/OPT/BL_IF_DETERMINE_SAP_DTYPE.

From VIM 5.2 SP4 onwards, you can configure separate FI document types for invoices and credit memos at the DP document type level. Fill the SAP FI DocType field with two separate FI document types, separated by comma.

Example: If the value in the field is AA,BB, the system will set the FI document type AA for invoice and BB for credit memos.

You can still configure a custom function module to determine the FI document type.

Archive Doc. Type

Select the archive doc type defined in the SAP ArchiveLink process, see

“Creating SAP ArchiveLink Document Types” on page 45. We strongly recommend that each OpenText document type has a unique archive doc type.

Lines item data

Select the check box if line item data is used that needs to be managed for the document (for example PO lines).

Header Program/Header Subscreen

OpenText provides subscreens for managing index data both at header level and item level. If the layout or information on the subscreen is inadequate to

the business process, you can define your own header program and custom subscreen.

Note: The sections Header Fields and Item Fields in this transaction are not supported in this VIM version.

Item Program/Item Subscreen

OpenText provides subscreens for managing index data both at header level and item level. If the layout or information on the subscreen is inadequate to the business process, you can define your own item program and custom subscreen.

Note: The sections Header Fields and Item Fields in this transaction are not supported in this VIM version.

Duplicate Check Data group Duplicate Check Grp

Select the duplicate check group defined.

Duplicate Check Role

Select the role that gets the work item if the duplicate check fails and system identifies the document as a potential duplicate.

Document Posting Configuration group Default Process Type

Select the process type the system uses if the initial business rule check fails to result in a valid process type.

Usage – This process type is used if no other process type is determined.

Example: If a document has no errors and should directly be created in SAP, you select a default process type for creating the document.

Dialog Posting Step Options group Posting Role

Select the role that is responsible for posting the document finally. If the posting of the document fails in background, this role gets the work item to post the document in dialog.

Note: A valid role must be already defined, see “Defining Roles” on page 29.

Display Index Data

Select this check box to display the index document in a separate session while document posting so the user is able to reference back the index data.

Note: At least one session must be available for display.

Skip Dashboard

Select this check box to skip the dashboard step. The system creates the SAP document directly during the document posting process for the posting user.

Example: If the document is all okay, the user might want to post it directly, without displaying the document data.

Display Image

Select this check box to display the archived image linked to the document in a separate session when the user processes the work item.

Note: Archiving must be active in the system.

Rescan Data group Rescan Role

Select the role that receives the work item if the document data is not legible or if the user decides to send the document for rescanning.

Note: A valid role must be already defined, see “Defining Roles” on page 29.

For a description of further fields in the Document Type Definition Details screen, see “Tax calculation Group” on page 62,“Maintaining Tax Code Determination” on page 60, and “Maintaining the PO Line Determination” on page 56.

5.1.3 Defining Process Types

In this step, you define the valid process types for document types and the BDC Id for each process type.

1. Execute the /OPT/VIM_1CX1 transaction.

Alternatively, follow LiveLink VIM - Configuration > Document Processing >

Document Type Configuration > Maintain Document Types.

2. In the Document Type Definition Overview screen, select a document type