PO Parking Process Configuration
2. Configure the Constant Value that is used to trigger a custom (sub)workflow before triggering the PO parked invoice workflow process
Default Value – None
6.4.5 Configuring Binding Function Exits
In this step, you define custom function modules that can transfer data to the OpenText delivered workflow processes for the PO parked invoice process.
To configure binding function module exits:
1. Execute the /OPT/VIM_IMG209 transaction.
Alternatively, follow LiveLink VIM - Configuration > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Technical Configuration > Advanced Process Customization > Binding Function Module Exit > Dashboard Step.
2. Configure the function module exits, using the following parameters:
Constant PRK_PSS_BIND_FM1 Usage
This function module is used to manipulate the workflow container during inward binding (task container to workflow container). This manipulation facilitates many features such as populating Analytics with custom data etc.
Default value
/PTGWFI/PRK_TMP_BIND_EXT_FM Constant PRK_PSS_BIND_FM2
Usage
This function module is used to manipulate the workflow container during outward binding (workflow container to task container). This manipulation facilitates the user to capture process information and populate with additional information.
Default value
/ORS/000007_LIX_PSS_BIND_O
Note: Do not change this value. If you need additional information to be captured for analytics or other purposes, first call the standard function /ORS/000007_LIX_PSS_BIND_Owithin your function. Otherwise,
unexpected failures in the VIM PO Parked Invoice Management process or subsequent processes may occur.
6.4.6 Configuring the Pre-dashboard Method Exit
In this step, you define custom function modules that will manage custom data before calling the dashboard.
To configure the pre-dashboard method exit:
1. Execute the /OPT/VIM_IMG215 transaction.
Alternatively, follow LiveLink VIM - Configuration > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Technical Configuration > Advanced Process Customization > Pre Dashboard Method Exit - Parking.
2. Configure the pre-dashboard method exit, using the following parameters:
Constant Value
This value is used to manage document data before calling the dashboard.
Default value – None
6.4.7 Configuring the Post-dashboard Method Exit
In this step, you define custom function modules that will manage custom data after calling the dashboard.
To configure the post-dashboard method exit:
1. Execute the /OPT/VIM_IMG214 transaction.
Alternatively, follow LiveLink VIM - Configuration > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Technical Configuration > Advanced Process Customization > Post Dashboard Method Exit (Parked Invoices).
2. Configure the post-dashboard method exit, using the following parameters:
Constant Value
This value is used to manage document data after calling the dashboard.
Default value – None
6.4.8 Configuring a Post Process (Sub)workflow
In this step, you define custom subworkflows that will execute after completing the PO Parked Invoice document process.
To configure a post process (sub)workflow:
1. Execute the /OPT/VIM_IMG217 transaction.
Alternatively, follow LiveLink VIM - Configuration > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Technical Configuration > Advanced Process Customization > Post process (sub)Workflow- Parked Invoices.
2. Configure a post process (sub)workflow, using the following parameters:
Constant Value
If you want to call a custom subworkflow after completing the PO Parked Invoice Document process, you can define a workflow template/task here.
Default value – None
6.4.9 Configuring an Autopost Exit
In this step, you define custom function modules that will post a document automatically.
To configure an autopost exit:
1. Execute the /OPT/VIM_IMG211 transaction.
Alternatively, follow LiveLink VIM - Configuration > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Technical Configuration > Autopost Global Configuration > Autopost Exit Function.
2. Configure an autopost exit, using the following parameters:
Constant Value
• Enter a function module. This function module can be used to post a document automatically using a custom function. If the function module configured here throws an exception, the system will however post the document using the standard posting logic for PO invoice documents.
• Default value: None
• For the interface of the function module, see function module /PTGWFI/PRK_M_TMP_PRE_AUTOPOST.
6.4.10 Configuring a Parked Document Posting Exit
In this step, you define custom function modules that will perform any post process transaction after the document is posted.
To configure a parked document posting exit:
1. Execute the /OPT/VIM_IMG216 transaction.
Alternatively, follow LiveLink VIM - Configuration > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Technical Configuration > Autopost Global Configuration > Parked Document Posting Exit.
2. Configure a parked document posting exit, using the following parameters:
Constant Value
• Enter a function module. This function module can be used to perform any post process transactions after the document is posted.
• Default value: None
• For the interface of the function module, see function module /PTGWFI/PIR_F_TMP_POST_EXIT_FM.
6.4.11 Configuring the Image Display Function
In this step, you define custom function modules that will display an SAP ArchiveLink image associated to the PO invoice document.
To configure the image display function:
1. Execute the /OPT/VIM_IMG216 transaction.
Alternatively, follow LiveLink VIM - Configuration > PO Based Invoice Configuration > Parked Invoice Processing Configuration > Technical Configuration > Image Display > Image Display Function.
2. Configure the image display function, using the following parameters:
Constant Value
• Enter a function module. This function module can be used to display an SAP ArchiveLink image associated to the PO invoice document.
• Default value: /PTGWFI/LIX_F_TMP_DISP_IMG
• For the interface of the function module, see function module /PTGWFI/LIX_F_TMP_DISP_IMG.
6.4.12 Configuring Automatic Image Display
VIM 5.2 SP5 introduces the following new feature: You can configure that images are automatically displayed when the PO Parked Invoice Dashboard is opened.
To configure automatic image display:
1. Execute the SM30 transaction.
2. Enter /PTGWFI/Z_CONST in Table/view and click Maintain.
3. In the WebFlow Constant Table, under Product Code LIX, double-click the Constant DASHBOARD_IMAGE_AUTO.
4. Enter Constant Value Xand save.
6.4.13 Configuring the Parking Functionality
In this step, you define custom function modules that activate the parking functionality. The previous version of VIM has enabled this by default.
To configure parking functionality:
1. Execute the SM30 transaction.
2. Enter /PTGWFI/Z_CONST in Table/view and click Maintain.
3. Look for Product Code LIX and Constant USR_EXIT_GET_DATA_FM and double-click the line.
4. Configure the parking functionality, using the following parameter:
Constant Value
Enter a function module to be used to activate the parking of PO invoice documents.
Default value:
Blank.
Baseline does not offer parking.
Optional value:
/PTGWFI/PRK_M_GET_PARK_DATA_N
This is the standard parking implementation function module.
6.4.14 Configuring Populating Screens for Re-enter Options
In exceptions workflows (parking or blocking), the following options are available to processors: Delete and re-enter as PO/NPO invoice or Cancel and re-enter as PO/NPO invoice. Currently, these options delete the existing invoice, then open a window with the invoice image and open another window with a SAP transaction, so that users are supposed to enter all information manually.
VIM 5.2 SP6 introduces new function modules for this scenario. They populate the new invoice with a subset of the header data of the deleted document:
• Company code
• Document date
• Vendor reference number
• Currency
• Vendor number
You can insert these function modules in the corresponding Z constants or you can create an own logic on basis of these function modules.
For the creation of a PO invoice, maintain the new function module
/PTGWFI/VIM_CRE_PO_INV_PREF in table /PTGWFI/Z_CONST, using the SM30 transaction.
Note: The existing function module /PTGWFI/VIM_CRE_PO_INV calls transac-tion MIRO without populating data.