1/9/2018 OpenText VIM: Rollout Criteria and Event Linkages | SAP Blogs

Products
Products Industries
Industries Support
Support Training
Training Community
Community Developer
Developer Partner
Partner

About
About

 
Home / Community / Blogs + Actions

OpenText VIM: Rollout Criteria and Event

Linkages
April 24, 2016 | 500 Views |

Pankaj Pareek
more by this author

FIN (Finance)
event linkages | opentext vendor invoice management | rollout criteria

share
0 share
0 tweet share
0

Follow

In this document, we are going to discuss Rollout Criteria that will trigger parking
(for PO and Non-PO) and blocking (for PO) of documents and setting up of Event

https://blogs.sap.com/2016/04/24/opentext-vim-rollout-criteria-and-event-linkages/ 1/8
1/9/2018 OpenText VIM: Rollout Criteria and Event Linkages | SAP Blogs

Linkages for them.

Rollout Criteria : In VIM one might want to have a parking process (Blocking
process only for PO) defined on the basis of a specific combination of Company
Code, Document Type and Plant (NOTE: In the case of Non-PO plant will not be
the criteria). Rollout Criteria helps us to define these. We can also say that they
are the workflow start conditions. When rollout criteria are defined then following
tables are impacted:

Company Codes: /OPT/VIM_CCODE_A

Document Types: /OPT/VIM_DTYPE_A

Plants: /OPT/VIM_PLANT_A

Event Linkages: In the Rollout Criteria we have defined the parameters against
which Parking or Blocking process will be triggered but event linkages are where
we set up the FMs and only after activating it we are able to trigger the process.

PO Parking Process

Define Rollout Criteria: In order to define the rollout criteria go to the path: Vendor
Invoice Management > PO Based Invoice Configuration > Parked Invoice
Processing Configuration > Rollout Criteria > Allowed Company Codes, Plants,
Document Types.

1. Allowed company codes: Company codes can be allowed for both PO and Non-
PO document types. Click on “New Entry” button in order to add a new company
code

2. Allowed Plants and Document Types: Select the company code and then
double click on “Allowed Plants” and/or “Allowed Document Type” folder on the
navigation panel on the left. Maintain the entry as required.

https://blogs.sap.com/2016/04/24/opentext-vim-rollout-criteria-and-event-linkages/ 2/8
1/9/2018 OpenText VIM: Rollout Criteria and Event Linkages | SAP Blogs

Receiver function module (in event linkages) triggers the workflow is triggered
based on the data maintained in this setting.

Define Event Linkages:

1. Go to T-Code /n/OPT/VIM_IMG241 (Path: Vendor Invoice Management > PO

Based Invoice Configuration > Parked Invoice Processing Configuration > Rollout
Criteria > Event Linkages (PO Parked Invoices)). Maintain the FM

2. Check the “Linkage Activated” checkbox to ensure that event linkage triggers
the PO parking Process.

https://blogs.sap.com/2016/04/24/opentext-vim-rollout-criteria-and-event-linkages/ 3/8
1/9/2018 OpenText VIM: Rollout Criteria and Event Linkages | SAP Blogs

PO Blocking Process

Define Rollout Criteria: Just like PO parking we can set up criteria for PO blocking.
Go to the following path: Vendor Invoice Management > PO Based Invoice
Configuration > Blocked Process Configuration > Rollout Criteria > Allowed
Company Codes, Plants, Document Types.

1. Allowed company codes: Click on “New Entry” button in order to add a new
company code

2. Allowed Plants and Document Types: Select the company code and then
double click on “Allowed Plants” and/or “Allowed Document Type” folder on the
navigation panel on the left. Maintain the entry as required.

https://blogs.sap.com/2016/04/24/opentext-vim-rollout-criteria-and-event-linkages/ 4/8
1/9/2018 OpenText VIM: Rollout Criteria and Event Linkages | SAP Blogs

Receiver function module (in event linkages) triggers the workflow is triggered
based on the data maintained in this setting.

Define Event Linkages:

1. Go to T-Code /n/OPT/VIM_IMG311 (Path: Vendor Invoice Management > PO

Based Invoice Configuration > Blocked Process Configuration > Rollout Criteria >
Event Linkages for Process (PO Blocked Invoices)). Maintain the FM

2. Check the “Linkage Activated” checkbox to ensure that event linkage triggers
the PO parking Process

https://blogs.sap.com/2016/04/24/opentext-vim-rollout-criteria-and-event-linkages/ 5/8
1/9/2018 OpenText VIM: Rollout Criteria and Event Linkages | SAP Blogs

Non-PO Parking Process

Define Rollout Criteria: Just like PO we can define the criteria for Non-PO parking
process. NOTE: In Non-PO process we will not have plants as the criteria. Go to
the following path: Vendor Invoice Management > Non-PO Based Invoice
Configuration > Parked Invoice Processing Configuration > Rollout Criteria >
Allowed Company Codes, Plants, Document Types.

1. Allowed Company Codes: Company codes can be allowed for both PO and
Non-PO document types. Click on “New Entry” button in order to add a new
company code

2. Allowed Document Types: Select the company code and then double click on
“Allowed Document Type” folder on the navigation panel on the left. Maintain the
entry as required. NOTE: Plants cannot be maintained for Non-PO document type.

https://blogs.sap.com/2016/04/24/opentext-vim-rollout-criteria-and-event-linkages/ 6/8
1/9/2018 OpenText VIM: Rollout Criteria and Event Linkages | SAP Blogs

Receiver function module (in event linkages) triggers the workflow is triggered
based on the data maintained in this setting.

Define Event Linkages:

1. Go to T-Code /n/OPT/VIM_IMG239 (Path: Vendor Invoice Management > Non-

PO Based Invoice Configuration > Parked Invoice Processing Configuration >
Rollout Criteria > Event Linkage for Processes (Non-PO). Maintain the FM

2. Check the “Linkage Activated” checkbox to ensure that event linkage triggers
the PO parking Proces

I hope this was useful and gave an insight into Rollout Criteria and Event Linkages

https://blogs.sap.com/2016/04/24/opentext-vim-rollout-criteria-and-event-linkages/ 7/8
1/9/2018 OpenText VIM: Rollout Criteria and Event Linkages | SAP Blogs

Alert Moderator

1 Comment
You must be Logged on to comment or reply to a post.

ashok bevara

March 16, 2017 at 5:37 am

hi Pankaj,

I am commenting because I don’t know where to ask you a question.

I have blocked one invoice due to quantity discrepancy.it is with non-prd po.But when I
generate invoice exception it went to some other user who was not in purchase group
and not po creator. why this is happened? what should I do now?

Share & Follow

Privacy Terms of Use Legal Disclosure Copyright Trademark Sitemap Newsletter

https://blogs.sap.com/2016/04/24/opentext-vim-rollout-criteria-and-event-linkages/ 8/8