Document Processing Process Configuration
/OPT/VIM_BL_1RIDX_DATA
2. Configure the fields in the Field Stat column, using the following parameters:
Input
Users can enter values on the indexing screen.
Required
Users must enter values. The field is marked as mandatory.
Hide
The field does not appear on the indexing screen.
Note: If you want to import and store data from an external system but you do not want to show them in the indexing screen, you can use this setting.
Display Only
The field appears on the indexing screen, but the user cannot enter values.
5.7 Configuring the Process Type
A process type in the VIM DP process is used by the system to determine if the process type is an exception, and to define the initial role that gets the work item.
The user process options for each role define the options on the dashboard for each role.
5.7.1 Defining the Process Type
To define the process type:
1. Execute the /n/OPT/VIM_8CX1 transaction.
Alternatively, follow LiveLink VIM - Configuration > Document Processing >
Process Configuration > Maintain Process Types.
2. Define the process types using the following parameters:
Process Type Number
5 digit unique number identifying the process type.
Process Type
Description of the process type.
Initial Actor
Select the initial role that gets the work item.
Initial Actor Function
Select a custom function module to determine the initial role. The system first checks if there is an initial actor. If there is no initial actor, the system tries to get the initial actor from the function module.
Is Exception
Select this check box to mark the process type as exception. If this check box is selected, the process type is not relevant for automatic background document posting.
Auto Start
Relevant for DP based approval workflow. If the process type corresponding to the approval workflow is determined, the system checks whether the Auto Start check box is enabled. If yes, the system starts the approval workflow if it is enabled. If Auto Start is not enabled, processing continues with the initial actor assigned to the current process type. The initial actor will manually start the approval workflow.
Create SR
Relevant for the SSF integration. This column is only available if VIM is integrated with CRM SSF. See “SSF Integration” on page 437.
Select this check box to configure that an automatic Service Request is created in background when this process type is triggered.
Country Check
Relevant for country specific configuration, for the following kinds of process types:
• Process types that are specific to a single country or multiple countries
• Process types that need to be checked for specific invoice categories in specific countries only
• Custom process types that need to be executed only for certain invoice categories of a country
Select this check box for these process types.
This check box tells the VIM system to check the country configurations also before the check defined in the process types is executed on the invoice.
Baseline configuration provides the check box as selected for the baseline process types that need additional checks to be performed for the country configuration.
See “Process Types” on page 361 Workflow Type
Select Opentext Approval Workflow from the drop down list to start the DP based approval workflow. With Opentext Approval Workflow selected, it is possible to select or clear the Auto Start check box, as the case may be.
Select External Workflow from the drop down list to run any external workflow (based on SAP technology) outside SAP IM workflows as a part of any business rule. With External Workflow selected, the Auto Start option is always enabled.
Select SRM System Integration from the drop down list for SRM scenarios or any other external systems where an email will be sent and the workflow will be in wait status. See “Supplier Relationship Management (SRM) Integration” on page 535.
Task ID
Enter the workflow template to be triggered. The workflow template container can be of any interface as the binding is controlled by a custom binding function module.
Binding Function
Enter the Workflow Binding function module.
It must be implemented in the system where the SAP IM workflow is running, to pass appropriate data to the external workflow. The function module should have an interface as /OPT/VIM_DASHBOARD_BINDING. Inside the custom function, in this case, implement Dataflow = E(Inward Binding).
You can access the complete container elements of the DP workflow from the table parameter CALLING_CONTAINER. Regarding how actual to implement the binding function, you can refer /OPT/VIM_DASHBOARD_BINDING.
As a simple implementation, element INDEXDOCUMENT can be accessed from the container CALLING_CONTAINER. DP (Document Processing number) can be retrieved and other indexing information can be extracted and passed to the elements of the CALLED_CONTAINER container, which is the container of the external workflow. The external workflow must also raise the event /OPT/V1001.PSS_COMPLETED at the end in the system where the SAP IM workflow runs so that the SAP IM workflow proceeds further.
Example 5-2: Sample code for the Workflow Binding function module FUNCTION Z_SHV_BINDING.
*"---
*"*"Local interface:
*" IMPORTING
*" VALUE(DATAFLOW) LIKE SWABINDEF-DATAFLOW
*" TABLES
*" CALLED_CONTAINER STRUCTURE SWCONT
*" CALLING_CONTAINER STRUCTURE SWCONT
*"--- include <cntn01>.
DATA : lcl_indexer TYPE REF TO /opt/cl_vim_doc_processor, l_curr_role type SWCONT-VALUE.
data : l_head type /opt/vim_1head,
l_objkey TYPE swotobjid-objkey, l_docid TYPE /opt/docid,
l_bus2012 TYPE swc_object.
IF DATAFLOW = 'E'. " Task Container <== Workflow Container
" Called_Container -- Calling_container
**************************************************************
**
* The binding is as follows
* External Workflow Container <=== VIM Workflow Container
* ===================== <=== =======================
**************************************************************
**
* Convert the Calling Container to Persistent SWC_CONTAINER_TO_RUNTIME CALLING_CONTAINER.
swc_get_element calling_container:
'IndexDocument' lo_v1001 .
swc_get_object_key lo_v1001 l_objkey.
l_docid = l_objkey.
select single * into l_head from /opt/vim_1head where docid = l_docid.
swc_set_element called_container: 'HEAD' l_head.
swc_create_object l_bus2012 'BUS2012' l_head-ebeln.
swc_set_element called_container: 'PurchaseOrder' l_bus2012.
SWC_CONTAINER_TO_RUNTIME called_container.
SWC_CONTAINER_TO_PERSISTENT called_container.
*
ELSEIF DATAFLOW = 'I'. " Task Container ==> Workflow Container
" Called_Container -- Calling_container
**************************************************************
**
* The binding is as follows
* External Workflow Container ===> VIM Workflow Container
* ===================== =======================
**************************************************************
**
* Convert the Called Container to Persistent SWC_CONTAINER_TO_RUNTIME CALLED_CONTAINER.
SWC_CONTAINER_TO_RUNTIME CALLING_CONTAINER.
ENDIF.
ENDFUNCTION.
Max Retry Counter Retry Time (Minutes) Mail Config ID
Function Module for Rcvr Email Function Module to send email
These columns are only relevant for the SRM integration. See “Missing Goods Receipt Scenario” on page 540.
Logical System
Enter the name of the system where the external workflow is supposed to run. The external workflow should be based on SAP technology.
5.7.2 Defining User Process Options
In this step, you define process options for each role. Process options are associated with the process type.
To define user process options:
1. In the Process Type Definition Overview screen, select a process type and