Non PO Parking Process Configuration
4. Double-click Allowed Document Types in the navigation panel to switch to the Allowed Document Types screen and define the rollout criteria for document
types, as described for company codes.
The respective receiver function module triggers the workflow based on the data in the tables. The workflow is triggered when there is no data maintained in the table(s) or the data meets all the conditions such as company code and document type.
8.1.1 Event Linkages
In this step, you define the standard event linkage delivered by OpenText as active.
Caution
If you change the configuration in this section, the Non PO parking process might not trigger at all.
To define the standard event linkage as active:
1. To access the Event Type Linkages screen, execute the /OPT/VIM_IMG239 transaction.
Alternatively, follow LiveLink VIM - Configuration > Non PO Processing >
Non PO Parking Process Configuration > Rollout Criteria > Event Linkage for Processes (Non PO).
2. Make sure the Linkage Activated check box is selected.
8.2 Configuring Parking Reasons
Figure 8-1 shows the parking reason selection screen. You can configure the dropdown selections based on the instruction in this section.
Figure 8-1: Non PO Parking reason selection screen
In this step, you define the valid parking reasons in the VIM Non PO parking process.
Configuring a parking reason comprises the following actions:
• Define the parking reason.
• Define the roles that are responsible for receiving the first work item in the process, for posting the Non PO invoice, and the initial approver.
• Define if the process triggering needs to be delayed.
• Delimit the available options for the parking reason.
To configure a parking reason:
1. Execute the /OPT/SPRO transaction and follow LiveLink VIM - Configuration >
Non PO Processing > Non PO Parking Process Configuration > Park Reason Maintenance > Parking Reason Maintenance
2. Select a parking reason and click in the application bar.
3. Define the parking reason, using the following parameters:
Description
Enter a description for the parking reason.
Active Indicator
Select this check box to achieve that the user can select the parking reason during parking of a Non PO invoice.
Subscreen Program/Screen Number
Select a sub screen that can be configured to capture additional information from the user when the user chooses a particular parking reason.
• You can extend the structure /PTGWFI/F_PIRMTR to capture additional data during parking a Non PO invoice.
Example: If a Non PO invoice needs to be parked for “Approval Required”, the system needs to know who is the Requisitioner. This additional information can be programmed in a custom sub screen for the parking reason “Approval Required”.
• Copy the OpenText delivered subscreen program and screen number to ensure that the common part include /PTGWFI/PIR_COMMON_PART is defined and data is exchanged properly.
Approval Required
Select this check box to achieve that the parking reason is flagged for approval and that the Invoice Approval process is triggered.
Autopost
Select this check box to achieve that the system automatically posts the invoice after Invoice Approval is completed.
Initial Actor
Define the role who receives the first work item once this document is parked for the current parking reason.
Example: If a Non PO invoice is parked for “Approval Required”, the initial role that needs to look at the invoice is the APPROVER. If the Approval Required check box is selected, the initial role will be CODER.
Initial Actor FM
You can define a custom function module to determine the initial actor.
For the interface of the function module, see function module /OPT/BL_Q_INIT_ACT_FM.
Delay Function
• Define the custom function module that can be used to restrict the immediate triggering of the Non PO parking process even if the user selected the current parking reason when the invoice is parked.
•
Example: The Non PO invoice is parked for “Approval Required” and you want to delay the approval for 2 days. You might then want to send the work item to the AP's inbox not before two days. For this purpose, you can define a custom function to restrict the triggering of the work
• For the interface of the delay function module, see function module /OPT/BL_P_DELAYFM_SRM.
Initial Approver
Define the role of the initial approver if the invoice document is sent for approval.
Posting Actor
Define the role responsible for posting the invoice and also responsible for handling errors if the posting in background fails.
Available Options
Define the options that are available for the role on the dashboard during Non PO parking process for the current parking reason. Separate the options by semicolon. The option format is AXXXX where Ais the option type and XXXX is the 4 digit value representing the option ID.
The system uses these values in conjunction with the user process options defined in “Configuring User Process Options” on page 181 to determine which options show up for the role’s dashboard.
8.2.1 Configuring User Process Options
In this step, you define all the process options available for roles when a Non PO invoice document is parked.
Configuring the process options comprises the following steps:
• Define user process options for all the roles in the process.
• Delimit available options for each parking reason in individual parking reason definition.
Tip: The standard SAP authorizations for transactions are checked for the underlying transactions in a user process option.
To configure user process options for Non PO parked documents:
1. Execute the /OPT/SPRO transaction and follow LiveLink VIM - Configuration >
Non PO Processing > Non PO Parking Process Configuration > Technical Configuration > Advanced Process Option Configuration > PSS User Process Options - OST
2. Click New Entries in the application toolbar.
3. Configure the user process options, using the following parameters:
BlockReason
Select block reason. Vis the system defined block reason for Non PO parked invoices.
From Actor
Select the role that sent the work item.
To Actor
Select the role who receives the work item after successfully processing the option.
Option Type
Select the type of process option (Action, Referral, BDC Action, Approve, Reject, etc., see “Configuring Process Options” on page 128)
Option ID
Select the ID of the process option.
Condition FM
• Define a condition function module to restrict availability of an option to a role even if the availability is defined here.
•
Example: If you want to show the option “Change Tax Information” only if the Non PO invoice has taxable line items, you can define a custom function to verify the existence of taxable line items and raise an error if there are no taxable line items.
• If an error is raised in the function module, the option will not be available to the user.
• For the interface of the condition function module, see function module /OPT/BL_CONDFM_INFOPROVIDER.
8.3 Configuring Global Parameters
This section describes the various global customization parameters that are
available. Global parameters control various aspects of the processing logic for Non PO parking process flows.
Important
Take care when you change the global configuration parameters. Changes can affect the functionality of the process.
Configuring global parameters comprises the following actions:
• “Configuring Transactions to Create Parked Invoices” on page 183
• “Configuring Dashboard Screen Exits” on page 184
• “Defining a Preprocess (Sub)workflow” on page 186
• “Configuring Binding Function Module Exits” on page 187
• “Configuring the Pre PSS Method Exit” on page 188
• “Configuring the Post PSS Method Exit” on page 189
• “Configuring a Post Process (Sub)workflow” on page 189
• “Configuring an Autopost Exit” on page 190
• “Configuring a Parked Document Posting Exit” on page 191
• “Configuring the Image Display Function” on page 192
• “Configuring Automatic Image Display” on page 192
• “Configuring a Parallel Workflow Exit” on page 193
• “Configuring the Parking Functionality” on page 193
• “Configuring Populating Screens for Re-enter Options” on page 194
8.3.1 Configuring Transactions to Create Parked Invoices
In this step, you configure the transactions that create parked Non PO invoices.
To configure transactions to create parked invoices:
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 PIR, double-click the Constant NONPO_INV_TCODE.
4. Enter the Constant Value: FBV0;FB01;FBV1;FV60;F-43;F-64;FB60;/PTGWFI/PIR_CHG_PKRS;FB65;FV65;
8.3.2 Configuring Dashboard Screen Exits
In this step, you configure the custom program/sub screen that displays the header data on the user dashboard.
Example:
After you have selected a particular parking reason, you want a particular sub screen to appear as shown in the screenshot below.
To configure dashboard screen exits:
1. Copy the OpenText delivered header program and subscreen.
Note: We strongly recommend that you copy the program and subscreen because the common part /PTGWFI/WLIX_COMMON_PART is required to communicate to the main program.
2. To access the configuration for PIRPROG and PIRSCREEN, execute the /OPT/VIM_IMG224 transaction.
Alternatively, follow LiveLink VIM - Configuration > Non PO Processing >
Non PO Parking Process Configuration > Technical Configuration >
Dashboard Screen Customization > Dashboard Screen Exits.
3. Configure PIRPROG and PIRSCREEN, using the following parameters:
Constant: PIRPROG Usage
Subscreen program for Non PO parked invoice dashboard header subscreen. To provide additional data on the invoice dashboard, you can define your custom screen here.
Default Value
/PTGWFI/PIR_SUBSCREEN01 Constant: PIRSCREEN
Usage
Subscreen number for Non PO parked invoice dashboard header
subscreen. To provide additional data on the invoice dashboard, you can define your custom screen here.
Default Value 9901
8.3.3 Defining a Preprocess (Sub)workflow
In this step, you define a custom (sub)workflow that needs to be triggered before the Non PO parking workflow process is triggered.
To define a preprocess (sub)workflow:
1. Execute the /OPT/VIM_IMG222 transaction.
Alternatively, follow LiveLink VIM - Configuration > Non PO Processing >
Non PO Parking Process Configuration > Technical Configuration >
Advanced Process Customization > Pre-Process (sub)Workflow.
2. Configure the Constant Value that is used to trigger a custom (sub)workflow