OpenText VIM For SAP Reference Guide

OpenText™ Vendor Invoice Management
for SAP® Solutions
Reference Guide
The OpenText™ Vendor Invoice Management for SAP®

Solutions Reference Guide collects reference information that is
helpful when configuring and administering Vendor Invoice
Management (VIM) 7.5 SP3.
VIM070500-03-RGD-EN-1
OpenText™ Vendor Invoice Management for SAP® Solutions
Reference Guide
VIM070500-03-RGD-EN-1
Rev.: 2015-Oct-09
This documentation has been created for software version 7.5 SP3.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text SA
40 Avenue Monterey , Luxembourg, Luxembourg L-2163
Tel: 35 2 264566 1
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: http://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2015 Open Text SA or Open Text ULC (in Canada). All Rights Reserved.
Trademarks owned by Open Text SA or Open Text ULC (in Canada). All rights reserved.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
Part 1 About Vendor Invoice Management 11
1 About This Document ............................................................. 15

1.1 Target Audience ............................................................................. 15
1.2 Related Documentation ................................................................... 15
Part 2 Third Party Interface Support 17
2 Interface Remote Functions ................................................... 21

2.1 Interface Remote Function 1 ............................................................ 21
Part 3 VIM Reporting 29
3 VIM Analytics: Getting Data Reports ..................................... 31

3.1 Using the Selection Screen .............................................................. 32
3.2 Understanding Selection Screen Fields ............................................ 35
3.3 Using Report Results ...................................................................... 40
3.4 VIM Analytics and Mass Data .......................................................... 61
4 Using the VIM Analytics Current Liability Report ................. 65

4.2 Using the Report Views Screen ........................................................ 68
4.3 Viewing and Grouping Report Results .............................................. 72
5 Using the Automation Report ................................................. 79

5.2 Using the Report Screen ................................................................. 81
6 Using the Common Infrastructure of Central Reporting

Reports ..................................................................................... 87
7 Using the Summary Report .................................................... 91

8 Using the Central Audit Report .............................................. 95

9 Using the Key Process Analytics Report .............................. 99
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide iii
VIM070500-03-RGD-EN-1
Table of Contents
9.1 Using the Frame Selection Panel ................................................... 100

9.2 Using the Individual Report Panels ................................................. 101
10 Using the Exception Analysis Report .................................. 109

10.1 Using the Selection Screen ............................................................ 109
10.2 Using the Report Screen ............................................................... 111
11 Using the Productivity Report .............................................. 115

12 Using the Aging Report ........................................................ 121

Part 4 SAP NetWeaver Business Warehouse Details 127
13 InfoObjects ............................................................................. 129

13.1 Key Figures .................................................................................. 129
13.2 Characteristics .............................................................................. 133
13.3 Units ............................................................................................ 144
14 DataSources ........................................................................... 147

14.1 DataSources for Transaction Data .................................................. 147
14.2 DataSources for Master Data ......................................................... 148
15 DataStore Objects (DSOs) .................................................... 157

15.1 DSOs of the Data Propagation Layer .............................................. 157
15.2 DSOs of the Corporate Memory Layer ............................................ 161
16 MultiProviders ........................................................................ 167
Part 5 Transactions and Roles 169
17 Transaction Profiles for Various Roles ............................... 171
Part 6 Business Rules 177
18 General Information About Business Rules ....................... 179
19 Business Rules for PO Invoices .......................................... 181

19.1 Invalid PO Number (PO) ................................................................ 181
19.2 Invalid Vendor (PO) ....................................................................... 182
19.3 Invalid UOM (PO) .......................................................................... 182
19.4 Invalid Currency (PO) .................................................................... 183
19.5 Suspected Duplicate (PO) ............................................................. 183
iv OpenText Vendor Invoice Management for SAP Solutions – Reference Guide

VIM070500-03-RGD-EN-1
Table of Contents
19.6 PO Not Released or Incomplete ..................................................... 184

19.7 Unable to Match PO Lines (PO) ..................................................... 184
19.8 Manual Check Needed / Missing Data for Indexing Lines (PO) ......... 185
19.9 Unable to Determine PO Line Number (PO) .................................... 186
19.10 Manual Check Needed for Indexing Lines (PO) ............................... 188
19.11 Invalid PO Item Number (PO) ........................................................ 189
19.12 Invalid Vendor VAT Number (PO) .................................................. 190
19.13 Incomplete Credit Memo (PO) ........................................................ 191
19.14 Vendor Address Mismatch (PO) ..................................................... 192
19.15 Missing Item Quantity (PO) ............................................................ 193
19.16 Missing Item Unit Price (PO) .......................................................... 193
19.17 Missing Invoice Date (PO) ............................................................. 194
19.18 Invalid Tax Info (PO) ..................................................................... 194
19.19 Missing Date of Supply (PO) .......................................................... 196
19.20 ISR Number Mismatch (PO) .......................................................... 197
19.21 Invalid Recipient VAT Number (PO) ............................................... 198
19.22 Payment Terms Mismatch (PO) ..................................................... 199
19.23 Invalid Siret Number (PO) (French) ................................................ 199
19.24 Invalid Company Address (PO) ...................................................... 200
19.25 Vendor Invoice Reference Missing (PO) ......................................... 201
19.26 Payment Method Mismatch (PO) .................................................... 201
19.27 Missing/Invalid Tax Exempt Text (PO) ............................................ 202
19.28 Missing Import Special Text (PO) ................................................... 202
19.29 Missing Item Description (PO) ........................................................ 202
19.30 Missing Mandatory Information (PO) .............................................. 203
19.31 Missing/Invalid Triangulation Text (PO) ........................................... 204
19.32 Invalid Sales Tax for the Region (PO) ............................................. 204
19.33 Vendor Audit Required (PO) .......................................................... 206
19.34 Vendor Maintenance (PO) ............................................................. 207
19.35 Vendor Mismatch (PO) .................................................................. 207
19.36 Service Entry Required (PO) .......................................................... 207
19.37 Currency Mismatch (PO) ............................................................... 208
19.38 Unit of Measure Mismatch (PO) ..................................................... 208
19.39 Approval Required (PO) ................................................................ 209
19.40 Freight on Invoice (PO) ................................................................. 209
19.41 Tax Audit Required (PO) ............................................................... 210
19.42 Invalid Requisitioner ...................................................................... 210
19.43 PO Credit Memo Processing (PO) .................................................. 211
19.44 Company Code Mismatch (PO) ...................................................... 211
19.45 Confirmation Required from SRM (PO) ........................................... 212
19.46 Invalid Payment Reference (PO) .................................................... 212
19.47 Missing Invoice Code (PO) ............................................................ 213
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide v

VIM070500-03-RGD-EN-1
Table of Contents
19.48 Invalid Invoice Code Format (PO) .................................................. 213

19.49 Invalid Characters in Secret Code (PO) .......................................... 213
19.50 Invoice Older Than Allowed (PO) ................................................... 213
19.51 Invalid Vendor Invoice Number (PO) .............................................. 214
19.52 Invalid Common Ordinary Invoice (VAT Exists) (PO) ....................... 214
19.53 Check Hand Written (PO) .............................................................. 214
19.54 Verification Required (PO) ............................................................. 214
19.55 Validate Bank Details (PO) ............................................................ 214
19.56 Invalid/Missing Vendor ABN Number (PO) ...................................... 215
19.57 Invalid/Missing Recipient ABN Number (PO) ................................... 215
19.58 Missing Vendor Name (PO) ........................................................... 215
19.59 Missing Recipient Name (PO) ........................................................ 216
19.60 Invalid Tax Description (PO) .......................................................... 216
19.61 GR Not Done - Simple Check ........................................................ 216
19.62 Missing Vendor ECC Number (PO) ................................................ 216
19.63 Mismatch Vendor ECC Number (PO) ............................................. 216
19.64 Missing Vendor CST Number (PO) ................................................. 217
19.65 Mismatch Vendor CST Number (PO) .............................................. 217
19.66 Missing Vendor TIN/TOT Number (PO) .......................................... 217
19.67 Mismatch Vendor TIN/TOT Number (PO) ....................................... 217
19.68 Missing Vendor LST Number (PO) ................................................. 218
19.69 Mismatch Vendor LST Number (PO) .............................................. 218
19.70 Missing Vendor PAN Number (PO) ................................................ 218
19.71 Mismatch Vendor PAN Number (PO) ............................................. 218
19.72 Missing Vendor STC Number (PO) ................................................. 219
19.73 Mismatch Vendor STC Number (PO) .............................................. 219
19.74 Wait for GR - Simple Check (PO) ................................................... 219
19.75 Wait for GR - Enhanced Check (PO) .............................................. 219
19.76 Brazil - Missing NF Data (PO) ........................................................ 220
19.77 Brazil - Missing NF Customizing (PO) ............................................. 220
19.78 Brazil - NF Validation Check Failed (PO) ........................................ 220
19.79 Brazil - Wait for GR - Simple Check (PO) ........................................ 220
19.80 Brazil - Wait for GR - Enhanced Check (PO) ................................... 220
19.81 Russia - Wait for TORG-12/ACT - Simple Check (PO) ..................... 221
19.82 Russia - Wait for TORG-12/ACT - Enhanced Check (PO) ................ 221
19.83 Russia - Original Invoice Mismatch (PO) ......................................... 221
19.84 Withholding Tax Code Not Valid for Vendor (PO) ............................ 221
19.85 Withholding Tax Base Amount Bigger Than Total Net Amount (PO) . 222
19.86 Check BPF Added Data (PO) ......................................................... 222
19.87 Tolerance Exceeded (PO) ............................................................. 222
19.88 Missing VAT Date (PO) ................................................................. 222
19.89 Check Withholding Tax Data (PO) .................................................. 222
vi OpenText Vendor Invoice Management for SAP Solutions – Reference Guide

VIM070500-03-RGD-EN-1
Table of Contents
20 Business Rules for NPO Invoices ........................................ 223

20.1 Invalid Vendor (NPO) .................................................................... 223
20.2 Invalid Currency (NPO) ................................................................. 223
20.3 Invalid Requestor ID (NPO) ........................................................... 224
20.4 Suspected Duplicate (NPO) ........................................................... 224
20.5 Non-PO Credit Memo Processing .................................................. 225
20.6 Derivation Rule - Non-PO Expense Type ........................................ 225
20.7 Invalid Vendor VAT Number (NPO) ................................................ 225
20.8 Incomplete Credit Memo (NPO) ..................................................... 226
20.9 Vendor Address Mismatch (NPO) .................................................. 226
20.10 Missing Invoice Date (NPO) ........................................................... 227
20.11 Invalid Tax Info (NPO) ................................................................... 227
20.12 Invalid Recipient VAT Number (NPO) ............................................. 228
20.13 ISR Number Mismatch (NPO) ........................................................ 229
20.14 Payment Terms Mismatch (NPO) ................................................... 229
20.15 Missing Date of Supply (NPO) ....................................................... 230
20.16 Invalid Siret Number (NPO) (French) .............................................. 230
20.17 Invalid Company Address (NPO) .................................................... 230
20.18 Vendor Invoice Reference Missing (NPO) ....................................... 231
20.19 Payment Method Mismatch (NPO) ................................................. 231
20.20 Determine Expense Type .............................................................. 232
20.21 Missing/Invalid Tax Exempt Text (NPO) .......................................... 232
20.22 Missing Import Special Text (NPO) ................................................. 232
20.23 Missing Item Description (NPO) ..................................................... 233
20.24 Missing Mandatory Information (NPO) ............................................ 233
20.25 Missing/Invalid Triangulation Text (NPO) ........................................ 234
20.26 Invalid Sales Tax For The Region (NPO) ........................................ 234
20.27 Non PO Approval Required (NPO) ................................................. 235
20.28 Vendor Audit Required (NPO) ........................................................ 236
20.29 Tax Audit Required (NPO) ............................................................. 236
20.30 Validate Bank Details (NPO) .......................................................... 237
20.31 Validate Accounting Data (NPO) .................................................... 237
20.32 Invalid Payment Reference (NPO) .................................................. 238
20.33 Missing Invoice Code (NPO) .......................................................... 238
20.34 Invalid Invoice Code Format (NPO) ................................................ 238
20.35 Invalid Characters in Secret Code (NPO) ........................................ 238
20.36 Invoice Older Than Allowed (NPO) ................................................. 239
20.37 Invalid Vendor Invoice Number (NPO) ............................................ 239
20.38 Invalid Common Ordinary Invoice (VAT Exists) (NPO) ..................... 239
20.39 Check Hand Written (NPO) ............................................................ 239
20.40 Verification Required (NPO) ........................................................... 240
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide vii
VIM070500-03-RGD-EN-1
Table of Contents
20.41 Invalid/Missing Vendor ABN Number (NPO) ................................... 240

20.42 Invalid/Missing Recipient ABN Number (NPO) ................................ 240
20.43 Missing Vendor Name (NPO) ......................................................... 240
20.44 Missing Recipient Name (NPO) ...................................................... 240
20.45 Invalid Tax Description (NPO) ........................................................ 241
20.46 Missing Vendor PAN Number (NPO) .............................................. 241
20.47 Mismatch Vendor PAN Number (NPO) ........................................... 241
20.48 Missing Vendor STC Number (NPO) .............................................. 241
20.49 Mismatch Vendor STC Number (NPO) ........................................... 241
20.50 Missing Vendor CST Number (NPO) .............................................. 242
20.51 Mismatch Vendor CST Number (NPO) ........................................... 242
20.52 Missing Vendor TIN/TOT Number (NPO) ........................................ 242
20.53 Mismatch Vendor TIN/TOT Number (NPO) ..................................... 242
20.54 Missing Vendor LST Number (NPO) ............................................... 243
20.55 Mismatch Vendor LST Number (NPO) ............................................ 243
20.56 Check BPF Added Data (NPO) ...................................................... 243
20.57 Missing VAT Date (NPO) ............................................................... 243
20.58 Check Withholding Tax Data (NPO) ............................................... 244
21 General Business Rules ....................................................... 245

21.1 Check Data After Restart ............................................................... 245
21.2 Check Data After Reject from Validation ......................................... 245
21.3 Check Inbound Interface Errors ...................................................... 245
21.4 Copy Rule: Supply Date to VAT Date ............................................. 246
22 Summary Tables .................................................................... 247

22.1 Table: Business Rules for PO Invoices ........................................... 247
22.2 Table: Business Rules for NPO Invoices ......................................... 251
22.3 Table: General Business Rules ...................................................... 254
23 Customer Library ................................................................... 257

23.1 Check Country Consistency ........................................................... 257
23.2 Check Balance .............................................................................. 257
23.3 Check and Update Coding for Auto Coding ..................................... 257
Part 7 Logic Modules 259
24 General Information About Logic Modules ......................... 261
25 Global Processing Logic Modules ....................................... 263

25.1 Change Vendor Group .................................................................. 263
25.2 Determine Bank Data .................................................................... 263
25.3 Determine SAP Document Type ..................................................... 264
25.4 Determine Country ........................................................................ 264
viii OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM070500-03-RGD-EN-1
Table of Contents
25.5 Determine Invoice Category ........................................................... 264

25.6 Determine Payment Terms ............................................................ 265
25.7 Determine Payment Baseline Date ................................................. 265
25.8 Determine Posting Date ................................................................. 265
25.9 Determine Tax Code ..................................................................... 266
25.10 Determine New Credit Memo Flag .................................................. 266
25.11 Determine Vendor Address ............................................................ 266
25.12 Determine Vendor Group ............................................................... 267
25.13 Determine Vendor Name ............................................................... 267
25.14 Determine Withholding Tax ............................................................ 267
25.15 Synchronize Item Text ................................................................... 268
26 PO Related Logic Modules ................................................... 269

26.1 Determine Currency ...................................................................... 269
26.2 Determine Delivery Date ................................................................ 269
26.3 Determine PO Item Data ............................................................... 269
26.4 Determine Matching Single Line PO Data for Vendor ...................... 270
26.5 Determine Vendor ......................................................................... 270
26.6 Determine Additional Costs ............................................................ 270
26.7 Use PO Header Data to Overwrite Line Items ................................. 271
26.8 Verify PO Data .............................................................................. 271
27 NPO Related Logic Modules ................................................. 273

27.1 Determine Expense Type .............................................................. 273
27.2 Determine NPO Line ..................................................................... 273
27.3 Determine NPO Auto-Coding ......................................................... 273
28 Country Specific Logic Modules .......................................... 275

28.1 Determine Ship-to Region for Canada ............................................ 275
28.2 Determine Corrective Items for Russia ........................................... 275
28.3 Determine Service PO for Russia ................................................... 276
28.4 Determine KIDNO for Denmark ...................................................... 276
Part 8 Automated Field Enhancement 277
29 Configuring Automated Field Enhancement ...................... 279
30 Baseline of Automated Field Enhancement ........................ 281
Part 9 Z Constants 285
31 Z Constants for Product Code 002 and 009 ........................ 287
32 Z Constants for Product Code 005 ...................................... 291
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide ix

VIM070500-03-RGD-EN-1
Table of Contents
33 Z Constants for Product Code IAP ...................................... 321
34 Z Constants for Product Code IEA ...................................... 333
35 Z Constants for Product Code IEM ...................................... 335
36 Z Constants for Product Code KPI ...................................... 337
37 Z Constants for Product Code LIX ....................................... 339
38 Z Constants for Product Code PIR ...................................... 351
39 Z Constants for Product Code VAN ..................................... 357
GLS Glossary 361
x OpenText Vendor Invoice Management for SAP Solutions – Reference Guide

VIM070500-03-RGD-EN-1
Part 1
About Vendor Invoice Management
Part 1 About Vendor Invoice Management
SAP Invoice Management by OpenText (VIM) is a packaged business solution for

managing vendor invoices.
• VIM solves a business problem - paying correct amount to vendors on time and
with the lowest cost.
• VIM delivers not technology but best-practice business processes.
• VIM provides values to customers in process efficiency, visibility and
compliance.
VIM is SAP® centric.
• VIM is an add-on to your SAP ERP system, the majority of the functions and
processes run inside your SAP ERP system.
• VIM deals only with invoices that will be posted to SAP ERP.
• VIM uses SAP technology: ABAP®, Workflow, and SAP NetWeaver® Portal.
• VIM integrates with standard SAP functions: Invoice Verification, Financial
Processing, etc.
VIM consists of the following components:
Figure 1: VIM components
12 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide

VIM070500-03-RGD-EN-1
ICC (OpenText™ Invoice Capture Center for SAP® Solutions)
• Automate the capture of paper invoices by using OCR to extract invoice data.
Document Processing
• Capture invoice metadata.

• Handle suspected duplicate invoices.
• Collaborate with others.
Invoice Approval
• Receive a list of invoices to be approved.

• Code and approve the invoices.
Approval Portal
• Java based Approval Portal infrastructure running on SAP NetWeaver

Application Server Java.
• Similar to Invoice Approval but with Web interface.
Mobile Approval
• Approve invoices on a mobile device, for example a Blackberry, an iPhone,

or an iPad.
Exception Handling (Invoice Exception)
• Handle the exceptions that arise after a SAP invoice is created.
VIM Reporting / VIM Analytics
• VIM Reporting: Use various reports to analyze the status of invoices in your
system.
• VIM Analytics: Overlook the invoices in progress in a unified dashboard.
Supplier Self Service
• Provide a web interface that enables suppliers to keep track of the status of
their invoices.
SAP CRM SSF Integration
• Integrate VIM with SAP Customer Relationship Management (SAP CRM)

SAP Shared Service Framework to create Service Requests from VIM
dashboards.
• Provide VIM invoice information in Vendor Factsheet inside the Accounting
Interaction Center (AIC).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 13

VIM070500-03-RGD-EN-1
Part 1 About Vendor Invoice Management
SAP NetWeaver BW
• Integrate VIM with SAP NetWeaver® Business Warehouse (SAP NetWeaver
BW) to integrate, transform, and consolidate relevant business information
from productive SAP applications and external data sources.
Ariba® Network Integration

• Connect VIM with Ariba Network Integration for SAP Business Suite.
Suppliers create invoices in the Ariba Network. The invoices are sent to the
SAP ERP system of the buyer. The buyer processes all incoming invoices in
VIM.

VIM070500-03-RGD-EN-1
Chapter 1
About This Document
This document collects reference information that is helpful when configuring and
administering VIM.
1.1 Target Audience

This document addresses those who participate in the customization and
implementation of Vendor Invoice Management (VIM). This includes:
• SAP Basis Administrators
• SAP Workflow Administrators
• SAP Configuration and Development Support
1.2 Related Documentation

Product docu- The following documentation is available for VIM in the OpenText Knowledge
mentation Center (https://knowledge.opentext.com/knowledge/cs.dll/Open/10151494) (KC):
• OpenText Vendor Invoice Management for SAP Solutions - Installation Guide (VIM-
IGD): This guide describes the installation of all VIM components.
• OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD): This guide describes the technical aspects of configuring VIM.
• OpenText Vendor Invoice Management for SAP Solutions - Administration Guide
(VIM-AGD): This guide describes the technical and functional aspects of
administering VIM.
• OpenText Vendor Invoice Management for SAP Solutions - User Guide (VIM-UGD):
This guide describes the typical tasks for end users in VIM.
• OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide (VIM-CCS):
This guide describes functional and technical scenarios of VIM.
Release Notes The Release Notes describe the following aspects in detail:
• The software supported by the product
• Requirements
• Restrictions
• Important dependencies
• Last-minute changes regarding the documentation
• Identification codes of the current documentation

VIM070500-03-RGD-EN-1
Chapter 1 About This Document
The Release Notes are continually updated. The latest version of the VIM Release
Notes is available in the OpenText Knowledge Center (https://
knowledge.opentext.com/knowledge).

VIM070500-03-RGD-EN-1
Part 2
Third Party Interface Support
Part 2 Third Party Interface Support
A third party interface is one channel to import an invoice to VIM. Third party
vendors provide the routing of invoices from the vendor to the customer.
“Middlemen” handle the responsibility of sending the invoice from vendor to
customer. These middlemen may also communicate back to the vendor regarding
the progress of the invoice processing on customer side. Third party vendors can use
any middleware technology like EDI, and so on.
Figure 2 depicts the suggested data and process flow for a third party service
provider scenario.
Figure 2: Third party service provider scenario - overview
Process flow
1. The third party provider module receives digitally signed invoices from
vendors.
2. The third party provider module verifies the authenticity of the digital
signature using Digital Signature Application.

VIM070500-03-RGD-EN-1
3. The third party provider module calls VIM APIs.
4. An OpenText provided API (FM1) returns the archiving URL.
5. The third party provider module archives the invoice image to the OpenText™
Archive Server via HTTP Post action.
Note: HTTP Post is obsolete and may not work with recent archive server
software. Use HTTP Put instead.
6. The third party provider module calls the second API (FM2) to trigger the
invoice processing in SAP ERP.
7. While invoice processing continues in SAP ERP, the third party provider
module can query the status of the document by calling the third API (FM3).
Third party service provider responsibility
The third party service provider must provide the following:

• Ensure that the original invoice sent by the vendor is transmitted unaltered to the
customer.
• Ensure that a Digital Signature infrastructure is agreed on and implemented
according to the customer and partner needs.
• Ensure that the VIM APIs are implemented so that correct data is passed to VIM.

VIM070500-03-RGD-EN-1
Chapter 2
Interface Remote Functions
The third party service provider scenario includes 3 Interface Remote Functions.
2.1 Interface Remote Function 1

This function module allows archiving a document. This facilitates the generation of
the URL that the third party provider module uses to archive the invoice image to
the content repository. The following is the interface of the function module:
FUNCTION /OPT/ARCHIV_DOC_URL_CREATE.
*"-----------------------------------------------------------------
*"*"Local Interface:
*" IMPORTING
*" VALUE(ARCHIV_ID) TYPE /OPT/VIM_1RHEAD-ARCHIV_ID OPTIONAL
*" VALUE(SIGNATURE) TYPE CHAR1 OPTIONAL
*" VALUE(AR_OBJECT) TYPE SAEOBJART OPTIONAL
*" EXPORTING
*" VALUE(ARCHIV_DOC_ID) TYPE /OPT/VIM_1RHEAD-ARC_DOC_ID
*" VALUE(MIMETYPE) TYPE CHAR128
*" VALUE(RC) TYPE SUBRC
*" TABLES
*" URL_ROWS STRUCTURE /OPT/VIM_URL
*" RETURN STRUCTURE BAPIRET2
*"-----------------------------------------------------------------
Import parameters
The third party provider must enter the correct parameters to match the SAP
ArchiveLink® configuration.
Parameter Name Data Type Size Comments

ARCHIV_ID 2 Content Repository Identification
(constant)
SIGNATURE 1 Signature authentication is used in SAP
ArchiveLink configuration (X = yes;
Space = no)
AR_OBJECT 10 SAP Archive Document Type (constant: /
OPT/ICC, /OPT/POI6)
Export parameters

ARCHIV_DOC_ID Char 40 SAP ArchiveLink Document ID
( generated for the image)

VIM070500-03-RGD-EN-1
Chapter 2 Interface Remote Functions

MIMETYPE Char 128 Mime Type
RC Numeric 2 Value 0 means successful. Value 8 means
error.
URL_ROWS Table Type Table of URL rows to archive image /
OPT/VIM_URL
RETURN Table Type Table of messages BAPIRET2
Error handling
If the RFC raises an exception, the call has failed. The call can be resubmitted if
possible. If the RC returns value 8, a data error has occurred. This record should be
placed into a separate queue for error handling. Resubmitting without investigation
will not make much sense.

This function module facilitates receiving invoice metadata and starts the processing
in VIM. The following is the interface of the function module:
FUNCTION /OPT/VIM_START_DOC_PROCESS_EXT.
*"------------------------------------------------------------------
*" IMPORTING
*" VALUE(DOCTYPE) TYPE /OPT/DOCTYPE OPTIONAL
*" VALUE(ARCHIV_ID) TYPE /OPT/VIM_1RHEAD-ARCHIV_ID OPTIONAL
*" VALUE(ARC_DOC_ID) TYPE /OPT/VIM_1RHEAD-ARC_DOC_ID OPTIONAL
*" VALUE(AR_OBJECT) TYPE SAEOBJART OPTIONAL
*" VALUE(CHANNEL_ID) TYPE /OPT/CHANNEL_ID OPTIONAL
*" VALUE(SYSTEM) TYPE LOGSYS OPTIONAL
*" VALUE(I_DOC_HEADER) TYPE /OPT/VIM_1HEAD OPTIONAL
*" EXPORTING
*" VALUE(RC) TYPE SY-SUBRC
*" VALUE(E_WF_ID) TYPE SWWWIHEAD-WI_ID
*" VALUE(DOC_STATUS) TYPE /OPT/VIM_DP_STATUS1
*" TABLES
*" EXTDATA_HEAD STRUCTURE /OPT/VIM_1REXTDATA OPTIONAL
*" EXTDATA_ITEM STRUCTURE /OPT/VIM_1REXTDATA OPTIONAL
*" I_DOC_ITEMS STRUCTURE /OPT/VIM_1ITEM OPTIONAL
*" LOGDATA STRUCTURE /OPT/VIM_1LOG OPTIONAL
*" COMMENTS STRUCTURE /OPT/EXT_COMMENTS OPTIONAL
*" IMG_DOC_ID STRUCTURE /OPT/D_ARC_DOC_ST OPTIONAL
*" RETURN STRUCTURE BAPIRET2 OPTIONAL
*"------------------------------------------------------------------
Import parameters
When calling this function, provide the following information:
1. Archived image info:

VIM070500-03-RGD-EN-1
2.2. Interface Remote Function 2

ARCHIV_ID Char 2 Content Repository Identification
(constant)
ARC_DOC_ID Char 40 SAP ArchiveLink Document ID
(returned from Interface Remote
Function 1)
AR_OBJECT Char 10 SAP Archive Document Type
(constant: /OPT/ICC, /OPT/POI6)
2. Channel info:

CHANNEL_ID Char 10 SAP Channel ID (Constant).
Recommended to be supplied. It helps
in identifying the source of any
supplied invoice.
SYSTEM Char 10 Logical name of the SAP ERP target
system
3. Invoice info captured from External Partner:

EXTDATA_HEAD Table Type Header info, for example Vendor
number, total amount, etc. Refer to
structure /OPT/VIM_1REXTDATA.
EXTDATA_ITEM Table Type Line item info, for example PO line,
Material, Quantity, etc. Refer to
structure /OPT/VIM_1REXTDATA.
Structure/OPT/VIM_1REXTDATA:
Field Name Data Type Size Comments

EXTFIELD Char 50 Field Name from External Partner
System
EXTVALUE Char 255 External Field Value
For each invoice field passed, the External Partner must specify field name
(EXTFIELD) and value (EXTVALUE).
4. Other optional parameters:

DOCTYPE Char 10 VIM Processing Document Type
I_DOC_HEADER Structure Structure of Indexing Document
Type Header /OPT/VIM_1HEAD

VIM070500-03-RGD-EN-1

I_DOC_ITEMS Table Type Table of Indexing Document Item /
OPT/VIM_1ITEM
LOGDATA Table Type Table of Document Process Log data /
OPT/VIM_1LOG
COMMENTS Table Type Table of Comments in structure /
OPT/EXT_COMMENTS. Comments can
be assigned to an entry in LOGDATA.
Export parameters

error.
E_WF_ID Numeric 12 Work item ID of the triggered Document
Processing Workflow in VIM
DOC_STATUS Structure The Document Processing Number
Type generated in VIM and its corresponding
status is passed in this parameter. Refer to
structure /OPT/VIM_DP_STATUS1.
Error handling If the RFC raises an exception, the call has failed. The call can be resubmitted if
Basic scenarios The function supports two basic scenarios concerning the import parameters, the
mapping scenario and the data scenario. Consider these scenarios. Which one of
these basic scenarios is taken, will be decided by the content of parameter
I_DOC_HEADER. If this parameter is initial, the mapping scenario is assumed. If
this parameter is not initial, the data scenario is assumed.
Mapping scenario
In this scenario, mapping is performed according to the value of CHANNEL_ID.
Data is expected in table EXTDATA_HEAD and EXTDATA_ITEM. Data
provided in I_DOC_ITEMS will be ignored.
Parameters DOCTYPE and AR_OBJECT can be left empty. Their values are
calculated according to configuration and document type determination engine.
If one or both of these parameters are provided, the given value will override
the configuration.
Data scenario
In this scenario, data is taken from I_DOC_HEADER and I_DOC_ITEMS. Data
provided in EXTDATA_HEAD and EXTDATA_ITEMS is ignored.
Parameters DOCTYPE and AR_OBJECT can be left empty. Their values are
calculated according to configuration and document type determination engine.

VIM070500-03-RGD-EN-1
If one or both of these parameters are provided, the given value will override
the configuration.
Additional notes
The document type AR_OBJECT can be provided as import parameter for

additional images. If it is not provided, the document type for additional
images is determined by the global configuration constant 005
ADDL_DOCS_AR_OBJECT.
The document class (TIF, PDF, and so on) is determined the following way:
If document type AR_OBJECT is provided as input parameter, the document

class for the image is set to the value associated to the document type
AR_OBJECT. If AR_OBJECT is not provided, as well as for the additional
images, the document class is derived from the mime type.

This function module allows 3rd party software to query the status of a document
that was submitted. The following is the interface of the function module:
FUNCTION /OPT/VIM_DOCUMENT_STATUS.
*"----------------------------------------------------------
*" IMPORTING
*" VALUE(CHANNEL_ID) TYPE /OPT/CHANNEL_ID OPTIONAL
*" VALUE(SYSTEM) TYPE LOGSYS OPTIONAL
*" EXPORTING
*" VALUE(RC) TYPE SY-SUBRC
*" TABLES
*" DOC_QUERY STRUCTURE /OPT/DOCID_ST
*" DOC_STATUS STRUCTURE TYPE /OPT/VIM_DP_STATUS1
*" RETURN STRUCTURE BAPIRET2
*"----------------------------------------------------------
Import parameters
When calling this function, provide the following information:
1. Channel info:

CHANNEL_ID Char 10 SAP Channel ID (Constant).
Recommended to be supplied. It helps
in identifying the source of any
supplied invoice.
SYSTEM Char 10 Logical name of the SAP ERP target
system
2. Query Table parameter:

VIM070500-03-RGD-EN-1

DOC_QUERY Table Type Table parameter of Document
Processing Numbers /OPT/DOCID
Export parameters

error.
DOC_STATUS Table Type Table parameter of Document Processing
Number and its corresponding status.
Refer to structure /
OPT/VIM_DP_STATUS1
Error handling
If the RFC raises an exception, the call has failed. The call can be resubmitted if
Notes
• Error messages will be stored in the application log. The RETURN table will
not be filled.
• RC will always be 0.
The function delivers the document status of documents with the following
peculiarities on import and export parameters:
CHANNEL_ID
The function delivers documents which have the specified channel ID. If
CHANNEL_ID is empty, only documents with empty channel ID are
considered.
SYSTEM
The function delivers documents from the specified logical system. If SYSTEM is
empty, the documents are checked in all active systems of the system landscape.
DOC_QUERY
If this table parameter is empty, all documents are delivered.
DOC_QUERY-DOCID
The function delivers the document with the specified document number(s).
DOC_QUERY-LOGICAL_SYSTEM
This import parameter is ignored.

VIM070500-03-RGD-EN-1
DOC_STATUS
The resulting table is sorted by document numbers. This gives an easy overview
on the status of documents in different systems.
DOC_STATUS-LOGICAL_SYSTEM
This export parameter shows the logical system where the information of the
table entry was taken from.

VIM070500-03-RGD-EN-1
Part 3
VIM Reporting
Part 3 VIM Reporting
VIM provides the following reporting components:

• VIM Analytics
• VIM Analytics Current Liability Report
• Automation Report
• Central Reporting, comprising the following reports:
• Summary Report
• Central Audit Report
• Key Process Analytics Report
• Exception Analysis Report
• Productivity Report
• Aging Report
This part describes how to work with the mentioned reports as an end user.

VIM070500-03-RGD-EN-1
Chapter 3
VIM Analytics: Getting Data Reports
VIM Analytics provides you with a clear data report on your documents with
exceptions as well as the Invoice Exception workflows. It allows you to track the
documents routed through SAP workflows by VIM or even without any VIM
process. You can use VIM Analytics to check the current document status of a
particular invoice. You can also check the current workflow status, current agent
and exception reason of a particular invoice. VIM Analytics presents the data report
results in the SAP List Viewer (ALV). ALV is used in the result list and in the detail
pane, Processes, Line Items and History tab.
VIM Analytics has been completely reworked for VIM 7.5. Here are some of the new
features:
• The new VIM Analytics provides more detail information to selected invoices:
There are several detail views available, showing, for example, workflows, line
items, and comments. In the process view of the detail pane, the user gets
information about all running VIM processes, including parallel approval and
referral processes, which are not available in the old VIM Analytics report.
• The new VIM Analytics provides a completely reworked selection screen: The
new selection screen was designed for the following purposes:
• to avoid inconsistent combinations of selection fields and unexpected
selection results
• to be more intuitive
• to provide even more selection fields
For documentation of the “old” VIM Analytics, see the VIM 7.0 documentation.
Transactions There are different transaction codes to start VIM Analytics.
/OPT/VIM_VA2
This transaction launches VIM Analytics with the full set of more than 80
selection fields.
/OPT/VIM_VA21 (AP Basic) - using report variant /OPT/VA2_L01

This transaction launches VIM Analytics with a subset of selection fields tailored
to an accounting expert. This variant allows searches for specific invoices using
invoice data like invoice numbers, document date, total amount, and reference
number.
/OPT/VIM_VA22 (AP Advanced) - using report variant /OPT/VA2_L02

to a higher level accounting expert or special roles as duplicate checker, financial
administrator or tax expert. This variant allows searches for specific invoices

VIM070500-03-RGD-EN-1
Chapter 3 VIM Analytics: Getting Data Reports
using invoice data like invoice numbers, document date, total amount, reference
number, but also process data, accounting data and due dates.
/OPT/VIM_VA23 (Procurement) - using report variant /OPT/VA2_L03

to a purchase agent in the procurement department. This variant allows searches
for specific invoices using invoice data like invoice numbers, document date,
total amount, reference number and requisitioner, but also purchasing data.
/OPT/VIM_VA24 (Monitor) - using report variant /OPT/VA2_L04

to a person who needs to monitor invoices and their processes. This variant
allows searches for invoice data like document date, total amount and reference
number, but also accounting data, due dates, document dates and VIM
exceptions.
Tip: You can switch between the different report variants with Get Variant .
3.1 Using the Selection Screen

To start VIM Analytics:
• Run the /OPT/VIM_VA2 transaction or any of the specific transactions /

OPT/VIM_VA21 to /OPT/VIM_VA24. For more information, see “Transactions”
on page 31.
Alternatively, navigate to OpenText Vendor Invoice Management > SAP menu
> Reports > /OPT/VIM_VA2 - VIM Analytics
Note: Your screen might look different as the display of selection fields
can be customized.

VIM070500-03-RGD-EN-1
3.1. Using the Selection Screen
The selection screen controls all functions of VIM Analytics. The selection screen
comprises the application toolbar and selection field panel. The following list
summarizes the features of these panels.
Application toolbar
Using the buttons in the application toolbar, you can perform the following
actions:
Execute

VIM070500-03-RGD-EN-1
VIM Analytics creates and displays a report, using the current settings in
the selection field panel.
Get report variant.

You can save your selection criteria and use the variant button to retrieve
the previous saved one. To create a report variant, click on the selection
screen. A report variant controls the selection screen. For example, you can
do the following.
• Hide selection fields (or even complete selection blocks)
• Declare fields as required
• Save selection criteria entered
Example: You search for Document Currency = EUR and click to save the
selection criteria. Next time, you can click to retrieve the search you saved
before. This is useful if you often perform a selection with different search criteria.
Get all selections.

As soon as you select a report variant that is hiding selection fields, this
button is displayed. Click it to also show the hidden fields.
To hide the fields again, click at the same location.
Selection field panel

Selection fields explanation - For explanation on selection fields that are not
self-explanatory, see “Understanding Selection Screen Fields” on page 35.
Tips
• Where applicable, click the icon for a list of available values.
• For search criteria with two entry fields joined by a to, you can enter a
value range.
• If you do not specify search criteria in a field, the search includes all
available values.
Report Options The Report Options section enables you to edit the settings for your report:
Layout
Click to select a layout variant from the list. With baseline, a basic and an
extended layout variant are available. You can create a layout variant for the

VIM070500-03-RGD-EN-1
3.2. Understanding Selection Screen Fields
result list. Use the ALV buttons Change Layout and Save Layout on the result
list.
Reporting Currency
The amount fields in the result list like Gross invoice amount, Discount
Amount 1, and Discount Amount 2 can be displayed in document currency but
also in any user-defined reporting currency.
Select the reporting currency. You can set a default reporting currency by setting
the user parameter FWS. If no user parameter is maintained, USD is used as
default reporting currency.
Currency Translation Date

Select one of the following parameters in the first field, and enter a date in the
second field.
C
Current date
D
Document date
P
Process start date
F
Fix date
3.2 Understanding Selection Screen Fields

This section provides explanations for fields of the selection screen that are not self-
explanatory. The fields are sorted according to their appearance in the selection
screen.
Invoice Data
Transaction/Event
Categorization of invoice documents into invoices, credit memos, subsequent
debits, subsequent credits and down payments
Vendor and Purchasing Data
Reference
Reference document number from the invoice
Purchasing Document
Purchasing document number
Note: Both the actual purchasing document in line items and potential
purchasing documents from header level and purchase order list (PO list)
are taken into account.

VIM070500-03-RGD-EN-1
Purchasing Group
Purchasing group assigned to purchasing document
Note: Both the actual purchasing document in line items and potential
purchasing documents from header level and purchase order list (PO list)
are taken into account.
Plant
Plant from the invoice line items
Process Data
Invoice Document Number

SAP MM invoice number
Accounting Document Number

SAP FI invoice number
VIM Process Type

VIM supports different process types from the DP process to standalone
scenarios (parked and blocked invoices). This selection field allows to select one
of the following:
• Invoices of all Process Types. This means invoices with and without VIM
processes
• Invoices with DP Process. Technically, this means that a DP workflow was
started.
• Parked/Blocked Inv., w/o DP. This means invoices with at least one VIM
process (parking, blocking, approval) but without a DP process.
• Invoices without VIM Process. This means invoices without any VIM
process
Invoice Type
Type of invoice, indicating whether the invoice is purchase order based or not
Overall Process Status

The Overall Process Status enables you to select for invoices in a specific
processing status. You can select for predefined status scenarios and for a SAP
invoice status or a VIM processing status.
Specific Scenario
Specific Scenario provides predefined scenarios, for example All
Invoices, Open Invoices, and Completed Invoices.
An open invoice in this context is defined as an invoice that has an open
VIM process (if existing) or where the SAP invoice (if existing) is not
deleted, not cancelled, or not yet ready for payment (this means not yet
posted without any fiscal and logistic payment block).
A completed invoice in this context is defined as an invoice where both all
VIM processes (if existing) are completed and the SAP invoice is deleted, or

VIM070500-03-RGD-EN-1
cancelled, or ready for payment (this means posted without any fiscal and
logistic payment block).
You can also select for invoices in different approval scenarios supported by
VIM: approval of posted documents, or approval of parked or DP based
documents.
With the Fiscal Year Changed scenario, you can select all invoice
documents that ran through the year end program of VIM. In other words,
you can select all invoice documents whose SAP invoice documents were
deleted due to a change in the year end posting period.
Selected Status
Selected Status enables you to select for the status of the SAP invoice or for
the VIM processing status. The value help offers a big range of different
status values. SAP statuses start with the prefix SAP_. They represent
different states of the SAP invoice, for example Parked, Posted, or Blocked.
Statuses without prefix SAP_ represent DP statuses.
Note: An invoice is not in status Posted but Blocked as long as any

payment block exists. For PO based invoices, both the fiscal payment
block and the logistic payment block are taken into account.
Accounting Data
G/L Account, Cost Center, and other accounting objects

Actual accounting object of invoice line item and purchase order in case of PO
based DP document
Due Dates
Due date
Due date of invoice
Days to Due
Number of days until the invoice is due for payment
This field allows negative values, as well, to get invoices whose due date was a
number of days ago.
Note: A possible difference of time zones between payer and invoicing

party is not taken into account.
Overdue
Check box to indicate that the invoice is overdue for net payment

Days to Cash Discount Date 1

Number of days until the cash discount applied to the shortest payment period
is due

VIM070500-03-RGD-EN-1
This field allows negative values, as well, to get invoices whose cash discount 1
was a number of days ago.

Days to Cash Discount Date 2

Number of days until the cash discount applied to the second payment period is
due
This field allows negative values, as well, to get invoices whose cash discount 2
was a number of days ago.

Work Item Data
Workflow Type
Type of the VIM workflow that is or was active for processing an invoice.
Example:
• 1 – Document Process Workflow
• 2 – Parked PO Invoice Workflow
Work Item Priority

Priority of VIM workflow that is or was active for processing an invoice
Work Item Status

Current status of any VIM workflow assigned to an invoice. The following
values are available:
50 - Waiting
These are workflows with a current work item that is not yet visible in the
VIM Workplace. This can have one of the following reasons:
• The work item could be created but the condition for the step Create
Work Item is not yet fulfilled (SAP work item status: CHECKED).
• The work item cannot be executed yet and therefore cannot be seen in
the Business Workplace or the VIM Workplace yet (SAP work item
status: WAITING).
51 - In Process
These are workflows with a current work item that has one of the following
statuses:
• Available for execution (SAP work item status: READY),
• Reserved by a recipient (SAP work item status: SELECTED),
• Currently being processed (SAP work item status: STARTED)

VIM070500-03-RGD-EN-1
• Already been executed once but processing is not yet completed (SAP
work item status: COMMITED)
52 - Completed
These are workflows with the following statuses:
• Processed fully and successfully (SAP work item status: COMPLETED)
• No longer processed (SAP work item status: CANCELLED)
54 - Error in Workflow
These are workflows with a current work item that has the following status:
• Error status (SAP work item status: ERROR)
Document Dates
Start Date
Date when the invoice entered the SAP system
DP Start Date
Date when the DP workflow started
Parking Date
Date when the parked SAP invoice was created or when the SAP invoice was
parked
Update Date
Date of the last change of the invoice.
Note: Even doing an approval step is defined as a change in this context.
Unblocking Date (MM)

Date when the payment block was removed from the MM invoice document or
posting date if there was no payment block
Posting Date in the Document
Posting date in the invoice; this date is used when entering the document in
Financial Accounting or Controlling
Posting Date
Date when the posted SAP invoice was created or when the SAP invoice was
posted
End Date
Date when the last VIM process was finished
Processing Time (in Days)
Duration of VIM processes in days from the entry time (Start Date/Start Time) of
the VIM invoice in the SAP system to the end time (End Date/End Time) of the
latest VIM process
Note: In this context, a day is defined as 24 hours independent of a day

change. A duration from 18 p.m. to 4 a.m. on the next day is less than a

VIM070500-03-RGD-EN-1
complete day, this means 0 days. However, a duration from 18 p.m. to 20

p.m. on the next day is 1 day.
Payment Date
Date of the last partial or complete payment
Process Flow
Company Code of Orig. Doc.

Company Code of SAP invoice document that was deleted due to a change in
the year end posting period
Number of Original Document

Number of SAP invoice document that was deleted due to a change in the year
end posting period
Fiscal Year of Original Doc.

Fiscal year of SAP invoice document that was deleted due to a change in the
year end posting period
3.3 Using Report Results

This section describes the report results that are available when running VIM
Analytics.
The following sections explain the general layout and the various areas of the report
results.
3.3.1 General Layout

To run a report:
1. In the selection screen, enter the criteria you want to run a report for.
2. Click in the application toolbar.

VIM070500-03-RGD-EN-1
3.3. Using Report Results
The report results comprise the following sections:
1
Menu toolbar
2
Application toolbar
3
Result list
4
Detail pane
Personal layout You can change the layout of the report results screen, according to your needs:
• Show or hide the detail pane.
• Select the tab to be displayed in the detail pane: Processes, Image, Line Items,
History, or Comments. For more information, see “Detail Pane” on page 48.
• Define the ratio between result list and detail pane by dragging the borderline.
When you leave the report results screen, using the , , or button,
VIM Analytics remembers your current state, and will show it again the next time
you open the report results.
Layout variants Using the button, you can define and save layout variants in the result list, the
Processes tab, and the Line Items tab in the detail pane.

VIM070500-03-RGD-EN-1
3.3.2 Menu Toolbar

The following actions are available in the menu toolbar:
VIM Analytics > Refresh

Get the newest data for the displayed report results. Refresh is also available as a
button in the result list:
Settings > Hide Detail Pane / Show Detail Pane

Toggle between view with detail pane and view without detail pane. This
setting is also available in the application toolbar.
Settings > Reset to Default

Reset the layout settings to the default settings.
3.3.3 Application Toolbar

Hide Detail Pane / Show Detail Pane, see “Menu Toolbar” on page 42
3.3.4 Result List

ALV grid control The ALV grid control on top of the result list provides various buttons for the ALV
list viewer. The following buttons are specific for VIM Analytics:
Choose Layout
Choose, change, save, and manage layouts. Click the small arrow on the right
side of the Choose Layout button.
Choose Layout
Select a saved layout from the list.
Change Layout
Add columns to the result list by shifting columns from Column Set to
Displayed Columns, using the arrow button.
Remove columns from the result list by shifting columns from Displayed
Columns to Column Set, using the arrow button.
Change the order of displayed columns using the up and down arrows in
Displayed Columns.
Click to save your layout.
Save Layout
Save your current layout status under an existing or a new name.
To keep the layout only for you, select the User-specific check box.
To load the layout as default layout when the result list is opened, select the
Default setting check box.
Manage Layouts
Define default settings of layouts and delete layouts.

VIM070500-03-RGD-EN-1
Refresh
Get the newest data for the displayed report results.
View Service Requests

Display Service Requests for the selected document in the context of the SAP
CRM SSF Integration. For more information, see Section 10.2 “Displaying a
Service Request” in OpenText Vendor Invoice Management for SAP Solutions - User
Guide (VIM-UGD).
If no Service Requests are found for the selected document, a message is
displayed.
Dashboard
Access the OpenText unified dashboard for the selected document.
Vendor Workspace
Display the Vendor Workspace (OpenText™ Extended ECM for SAP®
Solutions) for the work item in a separate window. Extended ECM for SAP
Solutions allows you to access related OpenText™ Content Server items in the
business workspace without leaving the SAP system.
For a comprehensive description, see Section 4 “Working in SAP ERP with the
Business Content window ” in OpenText ECMLink for SAP Solutions - User Guide
(ERLK-UGD)
Result list (ALV The result list provides details on invoice header level. The most important fields of
grid) the result list are described in “Understanding Result List Fields” on page 44.
OpenText delivers one basic and one extended layout variant for the result list in the
baseline. However, you can define your own layout variant to add fields to the
result list, to remove fields from the result list, or to change the sorting of the result
list.
Note: For performance reasons, OpenText recommends that you restrict the
layout to those columns that you really need.
Underlined values, for example in the Document Number or the Exception Reason
column, serve as links to pages with detailed information.
The asterisk (*) in a cell indicates that there is more than one value in this cell. This
can be the case with, for example, Purchasing Document, Current Agent or
accounting objects. Cells showing an asterisk do not serve as links. (Exception:
Current Agent in the Processes tab of the detail pane)

VIM070500-03-RGD-EN-1
3.3.5 Understanding Result List Fields

This section provides explanations for fields of the result list that are not self-
explanatory. The fields are sorted alphabetically by name.
Accounting Document No.

Approval Status Text

In case of an active approval process, this field indicates whether the coding step
has already been finished or not. Possible values:
• Awaiting Approval – Coding is not yet finished
• Awaiting Approval – Coding is finished
Cash Disc 1 Due Date

Due date for cash discount applied to the shortest payment period
Cash Disc 2 Due Date

Due date for cash discount applied to the second payment period
Clearing Document
Clearing document of last partial or complete payment

Date that was used for the conversion of amount related fields into the reporting
currency (as entered in the selection screen)
Current Agent
Agent that is currently assigned for processing the invoice
If multiple different agents are assigned, * is displayed.
Cycle Time
Duration of VIM processes from the entry time (Start Date/Start Time) of the
VIM invoice in the SAP system to the end time (End Date/End Time) of the latest
VIM process
Days to Cash Disc.1

Days to due date for cash discount applied to the shortest payment period
Days to Cash Disc.2

Days to due date for cash discount applied to the second payment period
Days to Due
Number of days until the invoice is due for net payment.
This field is cleared for completed invoices (this means obsolete, deleted, or
cancelled invoices and confirmed duplicates) or if the invoice is already fully or
partially paid.
Discount 1 Percentage
Cash discount percentage rate applied to the shortest payment period

VIM070500-03-RGD-EN-1
Discount 2 Percentage
Cash discount percentage rate applied to the second payment period
Discount Amount 1
Amount of cash discount for the shortest payment period in document currency
Discount Amount 1 in Rep. Crcy

Amount of cash discount for the shortest payment period in reporting currency
(as entered in the selection screen)
Discount Amount 2
Amount of cash discount for the second payment period in document currency
Discount Amount 2 in Rep. Crcy

Amount of cash discount for the second payment period in reporting currency
(as entered in the selection screen)
Discount Light Icon

Icon that is indicating,
• whether cash discount 1 (shortest payment period) or cash discount 2

(second payment period) are still possible or have been missed, or
• how far it is to cash discount 1 date (shortest payment period),
depending on the configuration settings in your system.

The quick info to the discount light icon provides some more details.
Document Status
Status ID of DP document
DP ID before restart
ID of a previous DP document that was deleted and for which a new DP process
was started
Due Date
Due date of the invoice
End at
Time at which the last VIM process was finished
End on
Date when the last VIM process was finished
Enter at
Time at which the invoice entered the SAP system
Enter on
Date when the invoice entered the SAP system
Exception Reason
Current exception of the invoice, for example the current process type of a DP
document or the parking reason of a parked invoice

VIM070500-03-RGD-EN-1
Invoice Type
Type of invoice, indicating whether the invoice is purchase order based or not
Invoice Type Text

Text for invoice type, indicating whether the invoice is purchase order based or
not
MM Invoice Document No.

Obsolete Reason Code

ID of reason code that was entered when deleting an invoice
Obsolete Reason Code Text

Text of reason code that was entered when deleting an invoice
Old Company Code

Company code of SAP invoice document that was deleted due to a change in the
Old Doc Num

Number of SAP invoice document that was deleted due to a change in the year
end posting period
Old Fiscal Year

Fiscal year of SAP invoice document that was deleted due to a change in the
Paid at
Time of the last partial or complete payment
Paid on
Date of the last partial or complete payment
Parked at
Time at which the parked SAP invoice was created or at which the SAP invoice
was parked
Parked on
Date when the parked SAP invoice was created or when the SAP invoice was
parked
Plant
Plant from invoice line items
If multiple different plants are assigned, * is displayed.
Posted at
Time at which the posted SAP invoice was created or at which the SAP invoice
was posted
Posted by
User who created the posted SAP invoice or who posted the SAP invoice

VIM070500-03-RGD-EN-1
Posted on
Date when the posted SAP invoice was created or when the SAP invoice was
posted
Posting Date
Posting Date in the invoice; this date is used when entering the document in
Financial Accounting or Controlling
Predecessor Object Key

Object key of an invoice that was deleted or cancelled and re-entered by another
invoice
Priority
Document priority
Purchasing Document
Purchasing document number from invoice header, invoice items and purchase
order list.
If multiple different purchase orders are assigned, * is displayed.
Reversal Doc#
Number of reversal document
Revsed F_Year
Fiscal year of reversal document
SAP Process Status

Status ID of the SAP invoice
Note: An invoice is not in status 2 (Posted) but 5 (Blocked) as long as any

payment block exists. For PO based invoices, both the fiscal payment block
and the logistic payment block are taken into account.
SAP Process Status Text

Status of the SAP invoice
Note: An invoice is not in status 2 (Posted) but 5 (Blocked) as long as any

payment block exists. For PO based invoices, both the fiscal payment block
and the logistic payment block are taken into account.
Start at
Time at which the DP workflow started
Start on
Date when the DP workflow started
Successor Object Key

Object key of the successor invoice that was entered after deletion or
cancellation of another invoice
Total Amount in Rep. Crcy.

Gross invoice amount in reporting currency (as entered in the selection screen)

VIM070500-03-RGD-EN-1
Unblock at
Time at which the payment block was removed from the MM invoice document
or posting time if there was no payment block
Unblock on
Date when the payment block was removed from the MM invoice document or
posting date if there was no payment block
Update Date
Date of the last change of the invoice
Update Time
Time of the last change of the invoice
Vendor Name
First and last name of the vendor as entered in the invoice. If there are no values
in the invoice, the names of the vendor are taken from the vendor master data.
VIM Process Status Text

Overall process status of the invoice
3.3.6 Detail Pane

The detail pane displays additional information about the document that is selected
in the result list. You can choose the following tabs:
• Processes
• Image
• Line Items
• History
• Comments
• Vendor Workspace
Further (or less) tabs may be available depending on the configuration.
If you change the selection in the result list, the detail pane automatically switches to
the newly selected document.
Processes
This tab shows the VIM workflows of the document that is selected in the result list.
The ALV grid control of the Processes tab provides some action buttons.

VIM070500-03-RGD-EN-1
Click the small arrow on the right side of the button to choose or change the
layout. For more information, see Choose Layout on page 42.
Display Workflow Log

Select a workflow in the Processes tab and click this button to display detailed
workflow information.
The Process State column displays one of the following icons, indicating the status
of the workflow:
The workflow is currently processed in the background.
The workflow is currently waiting for a user action.
The workflow is completed.
The workflow is currently in error (technical workflow error).
The font and background color in the lines of the Processes tab indicate whether
user interaction is required.
Black
Black font indicates that user interaction is required.
Gray
Gray font and a very light gray as background color indicate completed
workflows or workflows that are currently processed in background.
Red
The background color is red if the process is on error.
In case of a parallel workflow, the Processes tab displays more than one line with
different agents.
Image
This tab displays the scanned image of the original invoice that is selected in the
result list.
Line Items
This tab displays the line items of the document that is selected in the result list.
The ALV grid control of the Line Items tab provides an action button.

VIM070500-03-RGD-EN-1
History
This tab displays the history of the document that is selected in the result list. It
displays Process History and Approval History.
The ALV grid control of the History tab provides an action button.
Comments
This tab displays the comments of the document that is selected in the result list. It
displays Process Comments and Approval Comments.
Vendor Workspace
This tab displays the Extended ECM for SAP Solutions plug-in for the work item.
Extended ECM for SAP Solutions allows you to access related OpenText Content
Server items in the business workspace without leaving the SAP system.
For a comprehensive description, see Section 4 “Working in SAP ERP with the
Business Content window ” in OpenText ECMLink for SAP Solutions - User Guide
(ERLK-UGD)
3.3.7 Understanding Process View Fields

This section provides explanations for fields in the process view that are not self-
Accounting Document No.

Note: This field is populated only for VIM processes that are related to a
SAP FI invoice, for example at the parking workflow of a SAP FI invoice.
Approval Path
Approval path in case of parallel approval processes
Block Reason
Block reason in case of a blocked workflow
Company Code
Company Code of the SAP invoice document
SAP FI invoice, for example at the parking workflow of a SAP FI invoice.
Current Agent
Agent that is currently assigned for processing the VIM process

VIM070500-03-RGD-EN-1
If multiple different agents are assigned, * is displayed.

Current Role
Role that is currently assigned for processing the VIM process
Current Task
Technical ID of the current workflow task
Current Workitem ID
Work item ID of the current workflow task
Cycle Time
Duration of the VIM process from the point in time when the workflow was
started to the point in time when the workflow was finished
Dialog Flag
Indicator whether the current task is a dialog task or not (background task)
Document ID
DP Document ID
End at
Time at which the VIM workflow was finished
End on
Date when the VIM workflow was finished
Exception Reason
Current exception of the VIM process, for example the current DP process type,
the parking reason or the block reason
Fiscal Year
Fiscal year of the SAP invoice document
SAP FI invoice or a SAP MM invoice, for example at the parking workflow
of a SAP FI invoice or of a SAP MM invoice.
Invoice Item
Item number of SAP invoice that is processed by the VIM workflow
Note: This field is populated only for the block workflow on SAP MM
invoice line items
MM Invoice Document No.

SAP MM invoice, for example at the blocking workflow of a SAP MM
invoice.
Option Id
ID of the last process option executed

VIM070500-03-RGD-EN-1
Option Text
Text of the last process option executed
Option Type
Type of the last process option executed
Park Reason
Parking reason in case of a parking workflow
Priority
Priority of the VIM workflow
Process State
For a description of this field, see “Processes” on page 48.
Process Type
DP process type
Start at
Time at which the VIM workflow was started
Start on
Date when the VIM workflow was started
Update Date
Date when the VIM workflow was processed the last time
Update Time
Time at which the VIM workflow was processed the last time
WF Type Text
Text for the VIM workflow type
Example:
• Document Process Workflow
• Parked PO Invoice Workflow
WI Status
Current status of the VIM workflow. The following values are available:
50 - Waiting
These are workflows with a current work item that is not yet visible in the
VIM Workplace. This can have one of the following reasons:
• The work item could be created but the condition for the step Create
Work Item is not yet fulfilled (SAP work item status: CHECKED).
• The work item cannot be executed yet and therefore cannot be seen in
the Business Workplace or the VIM Workplace yet (SAP work item
status: WAITING).
51 - In Process
These are workflows with a current work item that has one of the following
statuses:

VIM070500-03-RGD-EN-1
• Available for execution (SAP work item status: READY),

• Reserved by a recipient (SAP work item status: SELECTED),
• Currently being processed (SAP work item status: STARTED)
• Already been executed once but processing is not yet completed (SAP
work item status: COMMITED)
52 - Completed
These are workflows with the following statuses:
• Processed fully and successfully (SAP work item status: COMPLETED)
• No longer processed (SAP work item status: CANCELLED)
54 - Error in Workflow
These are workflows with a current work item that has the following status:
• Error status (SAP work item status: ERROR)
WI Status Text
Text for the current status of the VIM workflow
Workflow
Work item ID of the workflow instance
Workflow Definition
Technical ID of the workflow template
Workflow Type
ID of VIM workflow type
Example:
• 1 – Document Process Workflow
• 2 – Parked PO Invoice Workflow
3.3.8 Understanding Line Item Fields

This section provides explanations for fields in the line item view that are not self-
Amount
Amount in document currency
Amount in Rep. Crcy.

Amount in reporting currency (as entered in the selection screen)
Document ID
DP Document ID
Document Item ID
ID of DP document line item

VIM070500-03-RGD-EN-1
Item
Item number of purchasing document
Text
Line item text
G/L Account, Cost Center, and other accounting objects

Accounting object of invoice line item or purchase order in case of PO based DP
document
If multiple different G/L accounts, cost centers, and so on exist, * is displayed.
3.3.9 Getting Aggregated Key Figures

In the result list of the new VAN report, you can see a detailed list of all invoices
matching your selection criteria. You might be interested in getting some aggregated
key figures to this list. For example, you would like to know
• how many invoices are currently processed per role

• the average or the maximum processing time of documents per vendor
• the total invoice amount per company code, separated in PO based and NPO
based invoices
These key figures and many more can be determined by ALV grid standard features.
This section gives you an idea how this works and what is possible. For more
detailed information to the ALV grid and its features, see the SAP documentation.
3.3.9.1 Example 1: Getting the Number of Invoices Currently Processed

Per Role
To get the number of invoices currently processed per role:
1. Launch the new VAN report with selection criteria Current Role not equal to
the empty value.
To get all invoices displayed, you may have to change the value for selection
field Maximum Number of Records.
Important
If you have thousands or even millions of invoices, ensure that you add
further selective selection criteria, for example a range for the document
date, a vendor and a company code. If runtime is still slow, ask your
system administrator to check for appropriate database indexes.
2. In the list of all invoices that are currently being processed, click the small arrow
on the right side of the Choose Layout button.
3. Click Change Layout.

VIM070500-03-RGD-EN-1
4. In the Change Layout dialog box, select the Current Role column and use the
arrow buttons to set this column at the first position of the Displayed Columns
pane.
5. Select the Number of Documents column and use the arrow buttons to set this
column at the second position of the Displayed Columns pane.
6. Select the Aggregation check box for the Number of Documents column.
7. To close the Change Layout dialog box, click .
8. In the Results list, select the first column header (the Current Role column) and
press the Subtotal button to get subtotals per role.
You may want to see the lines with the subtotals as a summary without the
documents in between. In this case, continue with the following steps.
9. Click the small arrow on the right side of the Subtotal button.
10. Click Drilldown Total Level.
11. In the Determine drilldown totals level dialog box, select Level 1 Current
Role.
12. To close the dialog box, click .

The number of invoices currently processed per role is displayed.

VIM070500-03-RGD-EN-1
13. You may want to know which invoice documents there are in detail for one
role. In this case, click the icon next to the current role.
You may want to return to the view where all documents are shown with
subtotals. In this case, continue with the following steps.
16. In the Determine drilldown totals level dialog box, select Level 0 Non-total
lines.
Note: You can save your preferred layout with the Save Layout option of
the Choose Layout button.

VIM070500-03-RGD-EN-1
3.3.9.2 Example 2: Getting the Average or Maximum Processing Time of

Documents Per Vendor
To get the average or maximum processing time of documents per vendor:
1. Launch the new VAN report with appropriate selection criteria.
Important
If you have thousands or even millions of invoices, ensure that you enter
selective selection criteria. If runtime is still slow, ask your system
administrator to check for appropriate database indexes and the
configuration of the VAN report.
You get a list of all invoices matching your selection criteria.
2. Click the small arrow on the right side of the Choose Layout button.
4. In the Change Layout dialog box, select the Vendor column and use the arrow
buttons to set this column at the first position of the Displayed Columns pane.
5. Select the Processing Time (in Sec) column and use the arrow buttons to set
this column at the second position of the Displayed Columns pane.

VIM070500-03-RGD-EN-1
7. Select the second column header (the ProcTime column) in the Results list, and
click the small arrow on the right side of the Total button.
8. If you want to get the average processing time of documents per vendor, click
Mean Value.
If you want to get the maximum processing time of documents per vendor, click
Maximum.
9. In the Results list, select the first column header (the Vendor column) and click
the Subtotal button to get the subtotals per vendor.
You may want to see the lines with the subtotals as a summary without the
12. In the Determine drilldown totals level dialog box, select Level 1 Vendor.

Depending on your selection in Step 8, you get a list of the average processing
time or the maximum processing time in seconds per vendor.
You may want to know which invoice documents there are in detail for one
vendor.
14. In this case, click the icon next to the vendor.
lines.

VIM070500-03-RGD-EN-1
3.3.9.3 Example 3: Getting the Total Invoice Amount Per Company Code,
Separated in PO and Non PO Invoices
You want to see the total invoice amount per company code. For every company
code, you want to have a subtotal for PO based and for Non PO based invoices.
Getting the total invoice amount per company code, separated in PO and NPO
invoices:
1. Launch the new VAN report with appropriate selection criteria.
Important
If you have thousands or even millions of invoices, ensure that you enter
selective selection criteria. If runtime is still slow, ask your system
administrator to check for appropriate database indexes and the
configuration of the VAN report.
You get a list of all invoices matching your selection criteria.
2. Click the small arrow on the right side of the Choose Layout button.
4. In the Change Layout dialog box, select the Company Code column and use the
arrow buttons to set this column at the first position of the Displayed Columns
pane.
5. Select the Invoice Type Text column and use the arrow buttons to set this
column at the second position of the Displayed Columns pane.
6. Select the Total Amount in Rep. Crcy column and Reporting Currency, and
use the arrow buttons to set theses columns at the third and fourth position of
the Displayed Columns pane.
7. Select the Aggregation check box for the Total Amount in Rep. Crcy column.

VIM070500-03-RGD-EN-1
9. Select the first column (Company Code) and the second column (Invoice Type
Text) in the Results list and click the Subtotal button to get subtotals for the
company code and invoice type combination.
You may want to see the lines with the subtotal as a summary without the

VIM070500-03-RGD-EN-1
3.4. VIM Analytics and Mass Data

12. In the Determine drilldown totals level dialog box, select Level 1 Invoice Type
Text.

You get a list of the total invoice amounts for the company code and invoice
type combination.
14. You may want to know which invoice documents there are in detail for one
company code and invoice type combination. In this case, click the icon next
to the invoice type text.
All invoice documents of this company code and invoice type combination are
shown.
lines.
3.4 VIM Analytics and Mass Data

How fast VIM Analytics performs the data selection, depends on your database
system and some other parameters. Independent of this, some basic principles gain
increasing importance, the more VIM invoices you have in the system. When having
several hundred thousand or even millions of VIM invoices, keep the following
recommendations in mind to ensure a good runtime of VIM Analytics.
Use restrictive selection criteria

This is the most important principle. Try to limit the number of invoices to be
selected to a minimum. Therefore, use appropriate selection values on the
selection screen. Do not select a huge number of invoices and then filter and sort
in the result list.
Notes
• When working without ABAP Core Data Services views (ABAP CDS
views), the selection fields Overall Process Status and Maximum
Number of Records are not working as restrictive selection criteria. Find
more details in Selection fields for the Overall Process Status
on page 62 and Selection field Maximum Number of Records
on page 63.

VIM070500-03-RGD-EN-1
• In case you use very restrictive selection criteria but experience very
slow performance nevertheless, ask your VIM consultant or system
administrator to check if a database index might help.
Limit the number of output fields in the result list

The result list provides about 100 columns. The more records you want to be
displayed in the result list, the more important becomes the number of columns
in the result list. Adjust the existing layout variants or create a new layout
variant for the result list. So you restrict the number of output columns to those
columns you need for your daily business. For more details about layout
variants, see Section 14.3 “Layout Variants” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
VIM Analytics There are additional recommendations when VIM Analytics was configured to work
without ABAP without ABAP CDS views on your system.
CDS views
Tips
• On a SAP® HANA database system, you can easily check if VIM Analytics
was configured to work with ABAP CDS views: Have a look at the title of
VIM Analytics. If it is VIM Analytics powered by SAP HANA, VIM
Analytics works with the ABAP CDS views. If it is VIM Analytics, VIM
Analytics does not use ABAP CDS views.
• On any database system different to SAP HANA, contact your system
administrator to get the information if VIM Analytics was configured to
work with ABAP CDS views or not.
Selection fields for the Overall Process Status

The selection fields for the Overall Process Status are not working as restrictive
selection criteria in regards to runtime and memory consumption. This means,
the Overall Process Status does not limit the number of invoices to be selected
from database into memory. Entering an Overall Process Status does not speed
up the runtime of VIM Analytics very much in comparison to a selection
without any Overall Process Status.
Technical background - First, all invoices that fit to the other selection criteria
are read into the memory. After that, all these invoices are checked against the
Overall Process Status. This is owed to the fact that the Overall Process Status
is determined by using more than a dozen database tables. Finally, for this
limited number of invoices, the output fields are determined. If possible, ensure
that the selection criteria are restrictive even without the selection of an overall
process status. This will save runtime and memory space.
Example 3-1: Overall Process Status selection criteria

VIM Analytics is run with the following selection criteria:
Channel ID: ICC
Overall Process Status - Selected Status: Blocked
Let us assume that there are five million invoices on the system. One
million of these invoices have channel ICC, only 5,000 invoices are

VIM070500-03-RGD-EN-1
3.4. VIM Analytics and Mass Data
blocked. When running VIM Analytics with these selection criteria, first,
all one million invoices with channel ICC are selected and read into the
memory. Then, those 5,000 blocked invoices are filtered out. This means
that 995,000 invoices were read into the memory without need.
OpenText strongly recommends that you choose additional restrictive selection

criteria besides the Overall Process Status.
Selection field Maximum Number of Records

The selection field Maximum Number of Records is not working as restrictive
selection criteria in regards to runtime and memory consumption. This means,
selection field Maximum Number of Records does not limit the number of
invoices to be selected from database into memory. This means, entering a low
Maximum Number of Records may not necessarily speed up the runtime of
VIM Analytics very much in comparison to a selection with a high Maximum
Number of Records.
Technical background - First, all invoices that fit to the other selection criteria
are read into the memory. This means, if you are selecting with unrestrictive
criteria and a huge amount of invoice documents is found, all these invoices are
read into the memory. After that, the amount of selected invoices is reduced to
the number of invoices to be selected. Finally, for this limited number of invoices
the output fields are determined.
It is good if you can use selection field Maximum Number of Records. This will
limit the number of invoices that need to be prepared for the display of the
result list. But OpenText strongly recommends that you choose additional
restrictive selection criteria besides Maximum Number of Records.

VIM070500-03-RGD-EN-1
Chapter 4
Using the VIM Analytics Current Liability Report
The VIM Analytics Current Liability Report is part of VIM Analytics. It offers you a
clear data report on documents that are parked in the system. The purpose of the
Current Liability Report is to provide the Accounts Payable department with
accurate information about the current liabilities at any point in time.
As a primary use, the Current Liability Report helps the Accounts Payable
department to do the accruals at month or period end. The Current Liability Report
provides you with various views of the data, enabling you to analyze the liability
information from various forms. The various views address the different accrual
procedures used by various companies.
The Current Liability Report considers parked invoice documents and optionally
credit memos that are in parked status. It also considers DP documents that were
created but have not been processed as SAP documents. Both PO invoices and Non
PO invoices are supported. There are various controls within the report, allowing
you to calculate sub totals, or to download to Excel.
You can restrict the output to lines that are within a certain amount range. This is
useful if your company’s internal policy is to ignore all lines that are below a certain
money limit.

You control all functions of the Current Liability Report using a common selection
screen.
To start the Current Liability Report:
• Run the /n/OPT/VAN_LIABILITY transaction.

Alternatively, navigate to OpenText Vendor Invoice Management > SAP menu
> Reports > /OPT/VAN_LIABILITY - Current Liability Report

VIM070500-03-RGD-EN-1
Chapter 4 Using the VIM Analytics Current Liability Report

VIM070500-03-RGD-EN-1
4.1. Using the Selection Screen
Note: Your screen might look different as you can configure what
selection fields should appear in the screen, using the Edit menu in the
menu toolbar.
Application Toolbar
In the Application toolbar, the following button is available:
Execute the query. This action opens the report views screen, based on the
search criteria entered in the selection field panel.
Selection Field Panel

In the selection field panel, you enter the search criteria for the Current Liability
Report. You restrict the number of invoices that are considered for the report, by
entering appropriate criteria values.
Notes
• Your screen and the selection criteria might differ from the screenshot.
• For search criteria with two entry fields joined by a to, you can enter a value
range.
• If you run the query without entering any criteria, the report will consider all
criteria values.
• The following list only covers elements whose meaning is not obvious.
General Information
In this panel, enter general search criteria for the invoices.
Include Documents
In this panel, enter search criteria regarding which documents should be included.
Docs with no Acct Assignmt

Select this check box to include documents that have no account assignment or a
line amount of zero.
Report View Group By

Decide how you want to group the information in the report view. Select an
element from the drop-down list.
SAP Documents
Group the result based on the actual SAP documents, such as PO invoices or
Non PO invoices.
DP Documents
Group the result based on the DP documents. This setting only displays the
DP documents. No SAP documents are displayed.

VIM070500-03-RGD-EN-1
Cost Center/GL Account (example for dual elements)

Group the result based on the Cost Center and then on the GL Account.
DP In Process
Select this check box to include DP documents that are still in process in the
result, for example, a document without an SAP document number that is not
deleted.
Note: If you are searching for DP documents by selecting the DP In

Process check box, the Company Code, Vendor, and Fiscal Year search
criteria are also considered when querying for DP documents.
SAP Invoice Information: Header Information
In this panel, enter search criteria for the invoice's header item.
Document Number
Enter the accounting document number of the invoice.
Fiscal Year
Enter the fiscal year when the invoice was blocked or parked.
DP Information
In this panel, enter search criteria for the Document Processing information.
Tip: Where applicable, click the icon for a list of available values.
Doc w/o Company Code or Vendor

Select this check box to include DP documents that do not have a Company
Code or a Vendor Number. If you select this check box, you also must select the
DP In Process check box in the General Information panel.
Suspected Duplicate Items

Select this check box to include DP documents that are suspected to be a
duplicate. If you select this check box, you also must select the DP In Process
check box in the General Information panel.
4.2 Using the Report Views Screen

The following views and major grouping options are available for the report:
Views
SAP Document Header View

Displays the data based on the document (SAP documents only); see “SAP
Document Header View” on page 72.
SAP Document Lines View

Displays the data based on the line item (SAP documents only); see “SAP
Document Lines View” on page 73.

VIM070500-03-RGD-EN-1
4.2. Using the Report Views Screen
DP View
Displays the DP document only; see “DP Information View” on page 74.
Groupings
Header Groups
Allows you to group the result based on the header level; see “Document
Header Grouping” on page 74.
Line Groups
Allows you to group the result based on the line level; see “Document Lines
Grouping” on page 76.
You can select views and groupings in the Report View Group By field of the
selection screen, see “General Information” on page 67. But also in the report views
screen, you can toggle between views and groupings in the menu bar and the
application toolbar.
Executing a search in the selection screen displays the report views screen, based on
the search criteria entered in the selection field panel.
The report views screen comprises the following sections:
• “Menu Toolbar” on page 70

• “Application Toolbar” on page 70
• “Overview Section” on page 70
• “Report Results (ALV Grid)” on page 71

VIM070500-03-RGD-EN-1
4.2.1 Menu Toolbar

Views menu
Switch between the different views.
Head Groups menu

Switch between the Header groupings.
Using this grouping also includes DP documents in the report.
Line Groups menu

Switch between different Line groupings.
Switch
Toggle sections in the report views screen on and off:
Header Off/Header On
Hide and unhide the Overview section.
Total On/Total Off

Hide and unhide the display of the Total in the report views screen.
4.2.2 Application Toolbar

Header Off/Header On
See “Menu Toolbar” on page 70.
Total On/Total Off

See “Menu Toolbar” on page 70.
By Vendor/By Comp.
Group the results by Header: Vendor or Company Code
SAP Doc View/SAP Lines View/DP View

Switch between the different views of the report.
4.2.3 Overview Section

The Overview section of the report views screen provides an overview of the
current search criteria, as entered in the selection field panel.

VIM070500-03-RGD-EN-1
4.2. Using the Report Views Screen
4.2.4 Report Results (ALV Grid)

The actual report results are displayed in the ALV Grid. The different views and
groupings have different columns; for a detailed description, see “Viewing and
Grouping Report Results” on page 72. To get more details about the results,
double-click a row in the ALV Grid.
The Related List for the Chosen Items shows details of the documents that belong
to the chosen grouping. There are two different panels in the screen:
Document Header View

This panel lists the SAP documents that belong to the chosen grouping. In the
example screenshot, the panel shows all the documents that belong to Company
Code 3000 and Vendor 3000 from the ALV Grid.
DP Information
This panel lists the DP documents that belong to the chosen grouping.
Note: The DP Information panel only appears if you have selected the DP
In Process check box in the General Information panel of the selection
field panel. Moreover, the report views screen must be grouped By
Company Code or By Vendor.

VIM070500-03-RGD-EN-1
In the example screenshot, the panel shows all DP documents that belong to
Company Code 3000 and Vendor 3000 from the ALV Grid.
4.3 Viewing and Grouping Report Results

For a list of the views and grouping options, see “Using the Report Views Screen”
on page 68.
Note: You might notice that when you switch from one view to another view,
the total number of items does not equal or some of the items are missing. This
is by design; some of the items might be missing the appropriate grouping
column. For example, if you choose WBS Element grouping and the item does
not have any WBS Element, it will not be included in the Group View by WBS
Element.
4.3.1 SAP Document Header View

This view groups the report results based on the Document Number. It only
displays SAP documents even if the search returned DP documents.
To display the SAP Document Header View, click SAP Doc View in the application
toolbar.
The SAP Document Header View comprises the following columns in the ALV
Grid:
Note: The following list only covers columns whose meaning is not obvious.
Reference #
Reference number of the vendor
Total Amount
Gross amount specified in the header level
Line Amount
Line amount of the invoice
# of Lines
Total number of lines in the SAP document. In case of PO invoices, it is the
number of PO lines in the invoice. In case of Non PO invoices, it is the number
of G/L lines.
User Name
User who created the invoice

VIM070500-03-RGD-EN-1
4.3. Viewing and Grouping Report Results
4.3.2 SAP Document Lines View

This view groups the report results based on the invoice lines. It only displays SAP
documents even if the search returned DP documents.
To display the SAP Document Lines View, click SAP Lines View in the application
toolbar.
The SAP Document Lines View comprises the following columns in the ALV Grid:
Invoice Item
Line item of the invoice
Balance Sheets Account

Balance Sheets Account, if field is checked
Cost Center
Number of the Cost Center
Internal Order
Internal Order of the invoice's line item
WBS element
WBS Element of the invoice's line item
Line Amount
Amount from the invoice lines in reporting currency
Posting key
Type of transaction that is entered in a line item
Network
Network number for account assignment
Debit/Credit Ind.
Debit or Credit indicator: S = debit; H = credit
Activity
Activity of the invoice's line item
Chart of Accounts
Key that uniquely identifies a chart of accounts
Controlling Area
Highest organizational unit in Controlling
Purchasing Document
Purchase Order document ID
Item
Number that uniquely identifies an item in a purchasing document

VIM070500-03-RGD-EN-1
4.3.3 DP Information View

This view groups the report results based on the DP document number.
To display the DP Information View, click DP View in the application toolbar.
Note: If you have entered search criteria other than Fiscal Year, Company
Code and Vendor in the selection screen, those other criteria are not
considered in the DP Information View because those criteria are not relevant
in DP documents.
The DP Information View comprises the following columns in the ALV Grid:
Document ID
DP document number
Credit Memo
An X in this column indicates that the DP document is a credit memo.
Document Date
Date when this DP document was created
Reference
Reference number of the vendor
Purchasing Document
PO of the document
Total Amount in Document Currency

Total Amount in Report Currency

Total amount in the currency that is selected in the selection field panel
4.3.4 Document Header Grouping

The following groupings by document header are available:
• Company Code
• Vendor
To group the report results by Company Code or Vendor, click the appropriate
Group by button in the application toolbar. The following example screenshot
shows a grouping by Company Code.

VIM070500-03-RGD-EN-1
A section In the A section of the example screenshot, all items have a Company Code, a
Vendor # and a Vendor Name assigned. This indicates that all documents are
already processed and have a Company Code and a Vendor Number. If you have
selected the DP In Process check box in the General Information panel of the
selection field panel, the row will also include DP items. These DP items have been
indexed with both Company Code and Vendor Number.
B section In the B section of the example screenshot, all items have no Company Code and no
Vendor # assigned. The Vendor Name is DP not Indexed. This indicates that the
documents in this section are DP documents that were created but not indexed at all.
Note: This section is displayed only if you have selected the DP In Process
check box in the General Information panel of the selection field panel.
The document header grouping comprises the following columns in the ALV Grid:
# of Docs
Number of documents in the group
Total Amount
Line Amount
Amount from all invoice lines of the invoice

VIM070500-03-RGD-EN-1
4.3.5 Document Lines Grouping

The following groupings by document lines are available:
• By Cost Center/ GL account

• By Internal Order / GL account
• By WBS Element/ GL account
• By Network Activity/ GL account
• By GL / Cost Center
• By GL / Internal Order
• By GL / WBS Element
• By GL / Network Activity
• By Balance Sheet
Example: If you select the grouping By Cost Center/ GL account, the result is grouped based
on the Cost Center first and then based on the GL Account.
To group the report results by document lines, click the appropriate menu entry in
the Line Groups menu. The following example screenshot shows a grouping By
Cost Center/ GL account.
The document lines grouping comprises the following columns in the ALV Grid:

VIM070500-03-RGD-EN-1
Notes
• The following list only covers columns whose meaning is not obvious.
• Depending on the grouping, some of the columns might not be displayed.
Internal Order
Internal Order number of the invoice's line item
WBS Element
WBS Element of the invoice's line item
Network
Network ID
Activity
Activity ID
G/L Account
General Ledger Account
# of Lines Included
Number of accounting lines in the group
Line Amount
Amount from all invoice lines of the invoice

VIM070500-03-RGD-EN-1
Chapter 5
Using the Automation Report
The Automation Report is a tool that provides data about automated and manual
processing steps of VIM documents.
The data is contained in table /OPT/VT_ATM_SRC. The table is filled by the ATM
collection report, which can be scheduled in the background. For details about the
ATM collection report, see Section 26 “Automation Report” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
The VIM program “Automation Report” allows to view and export the table
contents. The current version of the Automation Report does not do any counting or
calculation.

You control all functions of the Automation Report using a common selection
screen.
To start the Automation Report:
1. Run the /n/OPT/VIM_ATM transaction.

Alternatively, in OpenText Vendor Invoice Management, navigate to SAP
menu > Reports > Automation Report.

VIM070500-03-RGD-EN-1
Chapter 5 Using the Automation Report
2. In the Automation Report selection field screen, configure parameters for the
report.
Invoice Information
Company Code, Vendor

Restrict the output according to the current value of vendor and company
code in the /OPT/VIM_1HEAD table.
Document ID, Channel ID, DP Document Type

Restrict the output according to DP document number, Channel ID, and DP
Document Type.
Vendor from ICC Extraction

Restrict the output according to the vendor after extraction. In particular,
you can select <empty> to have an overview over the documents where the
vendor could not be found by ICC.
Document Date, Scan Date, Posting Date

Restrict the output according to document creation date, scanning date, and
posting date.
Report Options
Only Finalized Documents

Select this check box to consider only documents that are posted and not
blocked. These documents are in a final status for the Automation Report
and will never be changed again. For a long-term evaluation and for a
comparison over time, you should only consider these entries.
Layout
Select one of the defined layouts if you have saved a personal layout using
the ALV grid control, before. For more information, see “Custom Layouts
for the ALV Grid” on page 85.
3. Create variants in the selection screen.

OpenText recommends creating a selection variant; for example, if you want to
use the possibility to select documents with empty vendor number after
extraction.
Save your selection criteria and click Get Variant to retrieve a previously
saved variant.

VIM070500-03-RGD-EN-1
5.2. Using the Report Screen
5.2 Using the Report Screen

When you have finished your selection in the selection screen, click to run the
report.
5.2.1 ALV Grid Control

The ALV grid control of the Automation Report displays some standard options for
the ALV grid and three additional buttons to navigate to the document image, to the
DP document, and to the SAP document.
To navigate to the change documents, double-click into column No of Changes, see

also Table 5-3: “Automation related fields” on page 83, column No of Changes.
Notes
• Change documents for object class /OPT/VIM_IDXDAT build the basis of data
for the automation report.
• Change documents are technically stored in two SAP tables: CDHDR for the
header data and CDPOS for the detailed data.

The report screen shows a number of columns, which are arranged in two parts by
default:
• Invoice data
• Automation data
Use the horizontal scroll bar to display all columns.

VIM070500-03-RGD-EN-1
Invoice Data
Note: Fields that are marked with an asterisk in the tables are not visible in the
screenshot.
Table 5-1: Key fields
Technical Field Description (column Meaning - Usage - Notes

Name name)
* LOGSYS Logical system Name of the current logical system
DOCID Document Id DP document number to identify the
document. The Document Id matches /
OPT/VIM_1HEAD.
Table 5-2: Document related fields
Technical Field Name Description (column Meaning - Usage - Notes

name)
STATUS Document Status From /OPT/VIM_1HEAD
DOCTYPE DP Document Type From /OPT/VIM_1HEAD
GROSS_AMOUNT Gross invoice amount From /OPT/VIM_1HEAD
WAERS Currency From /OPT/VIM_1HEAD
BUKRS Company Code From /OPT/VIM_1HEAD
BELNR SAP Document Number From /OPT/VIM_1HEAD
GJAHR Fiscal Year From /OPT/VIM_1HEAD

VIM070500-03-RGD-EN-1

name)
BLDAT Document Date From /OPT/VIM_1HEAD
LIFNR_SAP Vendor From /OPT/VIM_1HEAD, field LIFNR
CHANNEL_ID Channel ID From /OPT/VIM_1HEAD
SCAN_DATE Scan date From /OPT/VIM_1HEAD
BUDAT Posting Date From /OPT/VIM_1HEAD
INV_TYPE Invoice Type From /OPT/VIM_1HEAD, field
DP_DOCTYPE and /OPT/VIM_T100,
field inv_type
* SENT_TO_SYSTEM Receiving System From /OPT/VIM_1HEAD, field
TARGET_SYSTEM
Automation Data
Note: Fields that are marked with an asterisk in the table are not visible in the
screenshot.
Table 5-3: Automation related fields

name)
* LIFNR_ICC Extracted Vendor From CDPOS, Tcode EXTRACTION,
field LIFNR
* FLAG_MULTIBACK Multibackend Comparison result of LOGSYS and
SENT_TO_SYSTEM (check box)

VIM070500-03-RGD-EN-1

name)
FLAG_POSTED_BG Posted in BG From CDHDR, Tcode POSTING. Check
box is selected if username is WF-
BATCH (hardcoded).
FLAG_VAL_SKP Vali Skipped From CDHDR, Tcodes EXTRACTION
and VALIDATION. The check box is
selected if an EXTRACTION header
entry exists, but no VALIDATION
header entry.
FLAG_FIRST_PASS First Pass From /OPT/VIM_1HEAD , field
NOFIRSTPASS (inverted value)
Note: This value is taken from

the data collection for the Key
Process Analytics Report.
FLAG_BLOCKED Blocked From /OPT/VIM_1LOG and /OPT/
CT_LG_HIST (check box)
NUMBER_OF_CDHDR No of Changes From CDHDR. Number of header
entries. To view the change
documents, these fields allow
navigation to the SAP standard report
RSSCD100: Double-click in the
respective field.
NUMBER_OF_MANCHG No of Manual From CDHDR. Number of header
Changes entries with Tcode VALIDATION,
APPROVAL, or INDEXSCREEN.
NUMBER_OF_TOUCH Number of Touches From /OPT/VT_WI. This field requires
the Central Reporting infrastructure.
Note: This value is taken from

the data collection for the
Productivity Report.
VALIDAT_CHANGE ValidationChg From CDPOS, Tcode VALIDATION.
The indicator is set to V if a field from
the scope (see the end of this table) has
been changed during validation.
VIM_CHANGE VIM Changed From CDPOS, Tcode INDEXSCREEN.
The indicator is set to D if a field from
the scope (see the end of this table) has
been changed during VIM processing.
SAP_CHANGE SAPChanged From CDPOS, Tcode POSTING. The
indicator is set to P if a field from the
scope (see the end of this table) has
been changed after VIM processing.

VIM070500-03-RGD-EN-1

name)
ATM_FINAL Final Status The indicator is set to C if the
document is in a final state, that is
posted and not blocked.
STATUS_BUKRS CompCodeChg These 7 fields define the scope for the
indicators VIM changed, SAP
STATUS_LIFNR VendorNbrChg
changed, and Validation
STATUS_XBLNR ReferenceNbrChg changed.
From CDPOS, Tcodes VALIDATION,
STATUS_EBELN PONumberChanged INDEXSCREEN, and POSTING. If there
STATUS_WRBTR Amount Chg is an entry with changed values, the
respective indicator is set to the
STATUS_VAT_AMT Vat Amt Chg respective value.
STATUS_WAERS Currency Chg
Note: For Amount Chg, only
gross amount is considered.
5.2.3 Custom Layouts for the ALV Grid

OpenText recommends that you create custom layouts for the ALV grid of the
Automation Report. In the ALV grid control, you can use Choose Layout to
choose, change, save, and manage layouts.
If you do not maintain the Central Reporting infrastructure, OpenText recommends

that you remove the column Number of Touches from the layout.
If you are using a multiple backend configuration, it might be useful to have

different layouts for the central system and the satellite systems.

VIM070500-03-RGD-EN-1
Chapter 6
Using the Common Infrastructure of Central
Reporting Reports
The reports in Central Reporting mostly share a common infrastructure. This

chapter describes the infrastructure elements that are the same in all reports. For
specific elements valid only for a particular report, see the chapter of the respective
report. The following elements are identical for all reports:
Selection screen
You control all functions of the particular report using a common selection
screen.
Note: In the Key Process Analytics Report, the selection is integrated into
the main screen that also shows the individual report panels. However, the
functionality is equal to the other reports.
Report screen
The report screen comprises: Header Section, ALV Grid Control, Report Results
(ALV Grid), and Details Screen
Notes
• In the Central Audit Report, only ALV Grid Control and Report Results
(ALV Grid) are available.
• The Key Process Analytics Report does not display the results in a report
screen but in individual report panels; see “Using the Individual Report
Panels” on page 101.

To start a report, navigate to OpenText Vendor Invoice Management > SAP menu
> Reports > Central Reporting, and double-click the report.
The selection screen opens. It comprises the application toolbar and the selection
field panel.
Figure 7-1 on page 92 shows an example of the selection screen.
Application toolbar
You can perform the following action:
Execute.
The report creates and displays a report, using the current settings in the
selection field panel.

VIM070500-03-RGD-EN-1
Chapter 6 Using the Common Infrastructure of Central Reporting Reports

The following selection criteria are available in all reports. Exceptions are
indicated where appropriate.
Tips
• Where applicable, click the icon for a list of available values.
• For search criteria with two entry fields joined by a to, you can enter a
value range.
• If you do not specify search criteria in a field, the search includes all
available values.
System or Logical System

Enter the logical system name. Logical systems are the central system and
the satellite systems in a multiple backend scenario.
Channel or Channel ID
Enter the Channel ID. The channel indicates the input mode of invoices into
VIM. For example, the channel ID IDOC stands for invoices imported using
Electronic Data Interchange.
This parameter is not available in the Summary Report.
Currency or Reporting Currency

Mandatory field. Enter the currency for the report. The amounts of all
documents will be translated into this currency, using the exchange rate
valid at the Currency Translation Date.
The currency parameters are not available in the Central Audit Report, the
Productivity Report, and the Aging Report.

Select the date whose exchange rate should be used for currency translation:
C
Current date
D
Document date
P
Process start date
P is the default value.
Layout
Enter the layout for the report if you have saved a personal layout using the
ALV grid control, before.

VIM070500-03-RGD-EN-1

report.
Figure 7-2 on page 93 shows an example of the report screen.
The report screen comprises:
Header Section
The header section of the report screen displays date and time of the last update,
and of the current run of the respective report.
Tip: If you feel the data needs to be updated, contact your administrator.
For some reports, the header section also shows the selection criteria that you
have entered in the selection field panel.
ALV Grid Control

The ALV Grid control provides various standard SAP buttons for the ALV list
viewer that displays the actual report results. For example, you can change the
layout of the report, move, remove or add columns and save this new layout.
You can then select your saved layout in the selection screen when you start the
report the next time.
For individual settings, see the respective ALV Grid Control sections of the
particular reports.
Report Results (ALV Grid)

The report results differ for the particular reports. Therefore, see the respective
Report Results (ALV Grid) sections of the particular reports.
Details Screen
The details screen differs for the particular reports. The following button in the
ALV grid control of the details screen is common for all reports that have a
details screen (except the Aging Report):
Image
You can display the scanned image of the original invoice of a VIM
document in the Image Viewer that is installed and configured on your
desktop: Select a line in the table and click Image.
For individual settings of the details screens, see the respective Details Screen
sections of the particular reports.
Notes
• The Key Process Analytics Report does not display the results in a report
screen but in individual report panels; see “Using the Individual Report
Panels” on page 101.

VIM070500-03-RGD-EN-1
Chapter 6 Using the Common Infrastructure of Central Reporting Reports
• In the Central Audit Report, only ALV Grid Control and Report Results
(ALV Grid) are available.

VIM070500-03-RGD-EN-1
Chapter 7
Using the Summary Report
The Summary Report provides a summary of all documents processed through

VIM. In a multiple backend system, the Summary Report runs in the central system.
The Summary Report lists documents from all systems, central and satellite.

You control all functions of the Summary Report using a common selection screen.
To start the Summary Report:
• Run the /n/OPT/VIM_SUMM transaction.

Alternatively, in OpenText Vendor Invoice Management navigate to SAP
menu > Reports > Central Reporting > Summary Report.
The selection screen opens. It comprises the application toolbar and the
selection field panel.
For a description of the elements that are common for all reports, see “Using the
Selection Screen” on page 87.

VIM070500-03-RGD-EN-1
Chapter 7 Using the Summary Report
Figure 7-1: Summary Report selection screen

The selection fields in the Summary Report mainly repeat the most
important selection fields that are displayed in VAN. See Selection field
panel on page 34 for details.
The following selection field is specific for the Summary Report:
Include
To include invoices and credit memos in the report, select the Invoice
and Credit Memo check boxes.
At the highest level, the Summary Report distinguishes between
invoices and credit memos. They are displayed as headings in the
report screen.

VIM070500-03-RGD-EN-1

report.
Figure 7-2: Summary Report report screen
1
Header section
2
ALV grid control
3
Report results (ALV grid)
Report Screen” on page 89.

The actual report results are displayed in the ALV Grid. The ALV comprises the
Invoice and Credit Memo section, according to your settings in the selection field
panel. Your administrator can configure groups and categories of the report results.
The baseline configuration provides the following groups and categories:
In process
• Non Approval Exception
• Approval
Pre Processed
• Pre Processed (OCR)

VIM070500-03-RGD-EN-1
Chapter 7 Using the Summary Report
Processed
• Posted
Others
• Cancelled
• Deleted
• Confirmed Duplicate
• Obsolete
• Rescan Complete
7.2.2 Details Screen

The Summary Report allows you to display details about the report results. To open
the Summary Report drill down list, double-click a cell in one of the Count
columns.
Tip: The selected line in the ALV Grid must contain data. Otherwise, the
Summary Report drill down list cannot be displayed.

VIM070500-03-RGD-EN-1
Chapter 8
Using the Central Audit Report
The Central Audit Report is a slimmed VIM Analytics (VAN). The main difference
to VAN is that the Central Audit Report serves as a single point of access in a
multiple backend scenario. Therefore, you must run the Central Audit Report in the
central system. The Central Audit Report lists documents from all systems, central
and satellite. By 2 clicks in the Central Audit Report's report screen, you can directly
access VAN on the respective satellite system. You do not have to log on to the
satellite system, when using trusted RFC connections.
Note: Ask your administrator whether trusted RFC connections are used. The
administrator can configure RFC connections, using the System Landscape
Directory (SLD).
The selection screen of the Central Audit Report contains the most important
selection fields of VAN. Additionally, it provides an additional selection field for the
systems of a multiple backend scenario.
Note: The Central Audit Report considers only documents that have a DP
document number.

You control all functions of the Central Audit Report using a common selection
screen.
To start the Central Audit Report:
• Run the /n/OPT/VIM_AUDIT transaction.

menu > Reports > Central Reporting > Audit Report.

VIM070500-03-RGD-EN-1
Chapter 8 Using the Central Audit Report

The selection fields in the Central Audit Report mainly repeat the most
important selection fields that are displayed in VAN. See Selection field panel
on page 34 for details.
The following selection fields are specific for the Central Audit Report:
Only Inprocess Documents

Select this check box to consider only DP documents whose workflow status
is In Process.

VIM070500-03-RGD-EN-1

report.
The report screen comprises the following sections:

• “ALV Grid Control” on page 97
• “Report Results (ALV Grid)” on page 98

The ALV Grid control of the Central Audit Report displays the following buttons.
Workflow Log
Select a document's line in the ALV Grid and click this button to display
detailed workflow information.
Image
Select a document's line in the ALV Grid and click this button to display the
scanned image of the original invoice in the Image Viewer installed and
configured on your desktop.
Dashboard
Select a document's line in the ALV Grid and click this button to access the
OpenText unified dashboard.
Link to VAN
Select a document's line in the ALV Grid and click Link to VAN to open VAN
for the selected document, see “VIM Analytics: Getting Data Reports“
on page 31.

VIM070500-03-RGD-EN-1
Chapter 8 Using the Central Audit Report
In a multiple backend scenario, VAN is opened directly on the system where the
document resides. You do not have to log on to the system, when using trusted
RFC connections.
Note: Ask your administrator whether trusted RFC connections are used.
The administrator can configure RFC connections, using the System
Landscape Directory (SLD).

The ALV Grid of the Central Audit Report is very similar to the Result List of VAN;
see “VIM Analytics: Getting Data Reports“ on page 31. The ALV Grid of the Central
Audit Report provides the following specific columns:
Logical System
The Logical System column at the very left of the ALV Grid indicates on which
system in the multiple backend system the document resides.
MultiAgent
The column MultiAgent might be marked for a document. This indicates that
more than one agent is assigned to the document. In this case, click the link in
the Current Role column to display the IDs and names of the assigned agents.

VIM070500-03-RGD-EN-1
Chapter 9
Using the Key Process Analytics Report
The Key Process Analytics Report reports about a variety of key figures regarding
the VIM process: It shows the accumulated amounts of all documents in the DP
workflow, in parked state and in posted state.
The individual report panels of the Key Process Analytics Report highlight the
following aspects:
Total Liability
This panel provides an overview of the total liability.
Amounts that are exceeding certain thresholds are highlighted in orange or red.
Your administrator can customize these thresholds.
Processed / In Process Documents

This panel provides an overview of VIM invoices, processed and currently in
process.
If the number or percentage of processed or in process documents exceeds
certain thresholds, the respective cells are highlighted in orange or red. Your
administrator can customize these thresholds.
Channel Analysis
This panel provides an overview of VIM invoices per channel.
First Pass
This panel provides an overview of first pass VIM invoices, that means VIM
invoices that could be posted without any exceptions.
If the number or percentage of first pass VIM invoices goes below certain
thresholds, the respective cells are highlighted in orange or red. Your
administrator can customize these thresholds.
Top Exceptions by Count

This panel provides an overview of the most frequent exceptions during the
VIM process. You can select the number of exceptions to be listed.
Top Vendors by Amount

This panel provides an overview of the vendors with the highest purchase
amount, based on the gross amount of all VIM invoices. You can select the
number of vendors to be listed.
The Key Process Analytics Report supports the conversion of amount fields to
different currencies.
You can display report data as graphics, using standard SAP ALV grid functionality.
You can choose between different chart types, for example bar chart or pie chart.

VIM070500-03-RGD-EN-1
Chapter 9 Using the Key Process Analytics Report
9.1 Using the Frame Selection Panel

Unlike the other reports in Central Reporting, the Key Process Analytics Report does
not provide a separate selection screen. The Frame Selection panel is integrated into
the main screen that also shows the individual report panels.
To start the Key Process Analytics Report:
• Run the /n/OPT/VIM_KPA1 transaction.

menu > Reports > Central Reporting > Key Process Analytics Report.
The main screen comprises the application toolbar, the Frame Selection panel
and the individual report panels.
VIM070500-03-RGD-EN-1
9.2. Using the Individual Report Panels
Application toolbar
You can perform the following action:
Refresh.
Alternatively, press the RETURN key.
The Key Process Analytics Report creates and displays a report, using
the current settings in the Frame Selection panel. The report results
are displayed in the individual report panels.
Note: A new selection from the database is triggered only if you

change the selection criteria.
Frame Selection panel

The following selection field is specific for the Key Process Analytics
Report:
Date Range
Enter the date range you want to run the report for. The date refers to
the Created at date of the VIM document. This corresponds to the P
date in Currency Translation Date; see Currency Translation Date
on page 88.
Individual report panels
See “Using the Individual Report Panels” on page 101.
9.2 Using the Individual Report Panels

After you finished your selection in the Frame Selection panel, click or press
RETURN to run the report.
The individual report panels in the main screen get populated with data.
VIM070500-03-RGD-EN-1
Figure 9-1: Key Process Analytics Report results
The following sections describe the individual report panels.
All report panels are displayed using the standard SAP ALV list viewer with the
respective ALV grid control. The ALV grid control provides various standard SAP
buttons for the ALV list viewer. For example, you can change the layout of the
report, move, remove or add columns.
VIM070500-03-RGD-EN-1
9.2.1 Total Liability

For a screenshot of the report panel, see Figure 9-1.
The Total Liability panel comprises the following columns:
Category
The following states of documents are listed:
• Blocked Documents
• Parked Documents
• Pre-Process Documents (all documents that are still in process and did not
yet result in an SAP invoice)
Total Amount
Total Amount of all documents
Crcy
Reporting Currency, as selected in the Frame Selection panel
Details To show details for a specific cell in the Total Amount column, double-click the cell
in the ALV grid. The Document List opens, showing detailed information on the
VIM documents of the Category referred to in the selected cell.
Tips
• The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.
• For the columns Category and Crcy, no document lists are available.
Threshold func- In the Total Liability panel, the threshold functionality is available. Your
tionality administrator can define threshold values for an attention status and a critical status.
If the attention value is exceeded in a cell, the cell is highlighted in orange. If the
critical value is exceeded in a cell, the cell is highlighted in red.
9.2.2 Processed / In Process Documents

The Processed / In Process Documents panel provides an overview of VIM invoices,

processed and currently in process. It comprises the following columns:
Invoice Type
• PO Invoices
• NPO Invoices
• Unclassified
An unclassified invoice is not yet classified as a PO or NPO invoice.
VIM070500-03-RGD-EN-1
Total # Processed
Total number of invoices that are already processed, that means with status
Posted.
You can add the following columns using the ALV grid control:
PO Based
Indicator if the invoice is PO based or not. Possible values: Y for Yes, N for No, U
for Unclassified.
This column can be useful if you export the data, for example to Microsoft Excel.
Processed (%)
Percentage of invoices that are already processed, that means with status
Posted.
In Process (%)
Percentage of invoices that are currently in process
Details To show details for a specific cell, double-click the cell in the ALV grid. The
Document List opens, showing detailed information on the VIM documents
according to Invoice Type and Document Status referred to in the selected cell.
Tip: The selected cell in the ALV grid must contain data. Otherwise, the
The ALV grid control in the Document List contains the following button:
Image
You can display the scanned image of the original invoice of a VIM document in
the Image Viewer installed and configured on your desktop: Select a line in the
table and click Image.
Threshold func- In the Processed / In Process Documents panel, the threshold functionality is
tionality available. Your administrator can define threshold values for an attention status and
a critical status. If the attention value is exceeded in a cell, the cell is highlighted in
orange. If the critical value is exceeded in a cell, the cell is highlighted in red.
9.2.3 Channel Analysis

The Channel Analysis panel provides an overview of VIM invoices by Channel ID.
The channel indicates the input mode of invoices into VIM, for example OCR. The
Channel Analysis panel comprises the following columns:
Channel ID
Channel ID, for example IDOC for invoices imported using Electronic Data
Interchange
VIM070500-03-RGD-EN-1
Channel Text
Description of the channel
Total # Unclassified
Total number of unclassified invoices (not yet classified as PO or NPO invoices)
PO Invoices (%)
Percentage of PO invoices
NPO Invoices (%)

Percentage of NPO invoices
Unclassified (%)
Percentage of unclassified invoices
Document List opens, showing detailed information on the VIM documents,
according to Invoice Type and Channel ID referred to in the selected cell.
Tip: The selected cell in the ALV grid must contain data. Otherwise, the
9.2.4 First Pass

The First Pass panel provides an overview of first pass VIM invoices, that means
VIM invoices that could be posted without any exceptions. The following types of
exceptions can happen:
• DP process types, for example 101 - Invalid PO Number (PO)

• Parking reasons, for example 151 - Vendor Audit Required
• Blocking reasons, for example Price Discrepancy
Not every DP process type, parking reason and blocking reason is automatically
seen as an exception. Which DP process type, which parking reason and which
blocking reason is actually treated as an exception, is defined in the configuration of
exceptions for Central Reporting. For more information, see Section 27.5 “Activating
Central Reporting Baseline and Maintaining Reporting Tables” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD), especially “To
maintain exceptions for Central Reporting” and “To map exceptions for several back
end systems”.
The First Pass panel comprises the following columns:
VIM070500-03-RGD-EN-1
First Pass (%)

Percentage of First Pass documents
Total # First Pass

Total number of First Pass documents
PO Based
Indicator if the invoice is PO based or not. Possible values: Y for Yes, N for No.
This column can be useful if you export the data, for example to Microsoft Excel.
according to the Invoice Type referred to in the selected cell.
Tips
• The selected cell in the ALV grid must contain data. Otherwise, the
• There is no Document List available for the column Total # Documents.
Threshold func- In the First Pass panel, the threshold functionality is available. Your administrator
tionality can define threshold values for an attention status and a critical status. If the value in
a cell falls below the attention value, the cell is highlighted in orange. If the value in
a cell falls below the critical value, the cell is highlighted in red.
9.2.5 Top Exceptions by Count

The Top Exceptions by Count panel provides an overview of the most frequent
exceptions during the VIM process.
You can select the number of exceptions to be listed in the panel. Therefore, the ALV
grid control of the Top Exceptions by Count panel provides the Top button:
Top
Click this button to select the number of exceptions that are listed. Possible
values: 3, 5, 10, or 20
The Top Exceptions by Count panel comprises the following columns:
Exception ID
ID of the exception in the system
Exception Text
Description of the Exception
VIM070500-03-RGD-EN-1
Details To show details for a specific line, double-click the line in the ALV grid. The Work
Items with Exception List opens, showing detailed information on the work items,
according to the Exception ID referred to in the selected line.
9.2.6 Top Vendors by Amount

The Top Vendors by Amount panel provides an overview of the vendors with the
highest purchase amount, based on the gross amount of all VIM invoices.
You can select the number of vendors to be listed in the panel. Therefore, the ALV
grid control of the Top Vendors by Amount panel provides the Top button.
Top
Click this button to select the number of exceptions that are listed. Possible
values: 3, 5, 10, or 20
The Top Vendors by Amount panel comprises the following columns:
Name 1
Vendor name
Total Amount
Total amount for the vendor
Currency
Reporting Currency, as selected in the Frame Selection panel
You can add the following column using the ALV grid control:
Name 2
Only useful if this field is maintained for the vendors in the system
Details To show details for a specific line, double-click the line in the ALV grid. The
according to the Logical System and the Vendor referred to in the selected line.
VIM070500-03-RGD-EN-1
Chapter 10
Using the Exception Analysis Report
The Exception Analysis Report reports all work items with exceptions, grouped by
exception, company code or vendor. The Exception Analysis Report provides the
following features:
• Finds and tracks exceptions with the highest impact on your business.
• Monitors how often exceptions occur.
• Finds companies or vendors who cause the highest number of exceptions.
• Indicates the invoice amount that is affected by work items with exceptions.

You control all functions of the Exception Analysis Report using a common selection
screen.
To start the Exception Analysis Report:
• Run the /n/OPT/VIM_EXCP1 transaction.

menu > Reports > Central Reporting > Exception Analysis Report.
VIM070500-03-RGD-EN-1
Chapter 10 Using the Exception Analysis Report

The selection field panel comprises the following sections:
Doc Characteristics
Invoice types
Click PO Invoices, Non-PO Invoices, or All Invoices (All Invoices
includes PO, Non PO and unclassified invoices).
Note: Unclassified invoices are not yet classified as PO or NPO

invoices.
IM Document Type
Enter the DP document type, depending on the logical system.
Vendor
Enter the vendor number, depending on the logical system.
VIM070500-03-RGD-EN-1
Include In Process Items

By default, the Exception Analysis Report only considers finished
documents, with status Posted. Select this check box to include also
documents that are still in process.
Note: This setting only considers documents in the current date

range, not in the comparison period.
Include Deleted/Obsolete/Cancelled/Confirmed Duplicate/Rescan

Complete
To include finished documents of any of the mentioned states, select this
check box.
Note: This setting considers documents in the current date range

and in the comparison period.
Time Characteristics
Date Range
the Created at date of the document.
Comparison Period
Click Previous Week, Previous Month, Previous Quarter or Previous
Year. The date refers to the Created at date of the document.
Grouping
Select the parameter to group the report by. Click Exception, Vendor or
Company Code.

report.
VIM070500-03-RGD-EN-1
Chapter 10 Using the Exception Analysis Report

The following button is specific for the Exception Analysis Report:
Group By
Click this button to change the grouping of the report. This has the same effect
as the Grouping settings in the selection screen. Click Exception, Vendor or
Company Code.

The actual report results are displayed in the ALV Grid. The Grouping setting
determines the layout of the columns.
If the report is grouped by Vendor or Company Code, the logical systems are
displayed at the very left of the table, followed by the Vendor or Company Code
information. If the report is grouped by Exception, the Exception information is
displayed at the very left of the table.
Next to the right, the following columns are displayed, first for the selected period,
next for the comparison period, indicated by Previous Period or Prev. in the column
title:
Notes
• You can change the layout of the report results; for example, you can shift,
remove or add columns. So, your actual table might differ from the
following description.
• The following list only covers columns whose meaning is not obvious.
Total Amount
This value is recalculated from the original currency to the reporting currency.
Avg. Time
Average time of work on the work item
Avg. Wait Time
Average time elapsed on one VIM document before all the work items related to
this VIM document have been touched by a user for the first time.
One VIM document can comprise several work items. Every work item has a
wait time before it is touched for the first time. The report sums up these wait
times and averages them.
Note: The columns containing time data display the time in <xx>d <xx>h
<xx>m <xx>s format. You can add corresponding columns that display the
time in seconds as a numeric value. This is useful, for example, if you want
to export data to an Excel spreadsheet.
VIM070500-03-RGD-EN-1
Avg. # of Touches
Average number of how often the work item has been touched
Avg. # of Referrals
Average number of how often the work item has been referred to an agent

To show details for a specific line, double-click the line in the ALV Grid. The Work
Items with Exception List opens, showing detailed information on every work item
that appears in the # Work Items with Exceptions column in the selected line.
Tip: The selected line in the ALV Grid must contain data. Otherwise, the Work
Items with Exception List cannot be displayed.
VIM070500-03-RGD-EN-1
Chapter 11
Using the Productivity Report
The Productivity Report reports about the productivity of users/roles and the
activities of users/roles. The Productivity Report comprises the following features:
• Provides an overview of the processing times (total and average) and wait times
(average) per user/role.
• Enables the comparison of productivity of a freely selectable period to a
comparison period.
• Provides a snapshot of reserved and in process items per user/role.
• Enables the analysis of the average number of touches (per invoice) of users/
roles.
• Enables the analysis of the average number of referrals (per invoice) of users/
roles.
• Allows displaying a detailed list of:
• documents processed by a single user/role

• currently reserved items of a single user/role
• currently processed items of a single user/role
Note: The time stamps that are used for the Productivity Report are based on
the time information in the SAP work item tables and are not directly related to
the time stamps in the VIM process history.

You control all functions of the Productivity Report using a common selection
screen.
To start the Productivity Report:
• Run the /n/OPT/VIM_PROD1 transaction.

menu > Reports > Central Reporting > Productivity Report.
VIM070500-03-RGD-EN-1
Chapter 11 Using the Productivity Report

The following selection fields are specific for the Productivity Report:
Agent Info
Agent ID
Enter the IDs of the agents (users) you want to run the report for.
Role ID
Enter the IDs of the roles you want to run the report for.
Org Object
Enter the Org object you want to run the report for. The Org object
refers to the organizational objects maintained in the standard SAP
Organizational Management. Using the icon, you can restrict the
value range to Organizational unit, Position, or Organizational units
and Positions (All).
VIM070500-03-RGD-EN-1
Note: To use this selection criterion, the organizational structure

must be maintained within SAP Organizational Management on
the different logical (back end) systems.
Doc Characteristics
Click PO Invoices, Non-PO Invoices, or All Invoices (All Invoices includes
PO, Non PO and unclassified invoices).

invoices.
Time Characteristics
Date Range
the Created at date of work items related to the VIM document.
Comparison Period
Click Previous Week, Previous Month, Previous Quarter or Previous
Year. The date refers to the Created at date of work items related to the
VIM document.
Grouping
Select the parameter to group the report by. Click Agent or Role.

report.
VIM070500-03-RGD-EN-1

The following button is specific for the Productivity Report:
Group By
as the Grouping settings in the selection screen. Click Agent or Role.

determines the layout of the columns. If the report is grouped by Agent, the logical
systems are displayed at the very left of the table, followed by the Agent
information. If the report is grouped by Role, the Role information is displayed at
the very left of the table.
Note: The Validator role (ID 13) is not covered by the Productivity Report
although it is configured in the baseline. Data for this role is not shown in the
report results.
Report period Next to the right, the following columns are displayed for the report period:
results
Note: You can change the layout of the report results; for example, you can
shift, remove or add columns. So, your actual table might differ from the
Total # Processed
Number of VIM documents that have been worked on in the report period.
Work is not necessarily completed; that means, the invoice may be already
posted or not.
Reserved
Number of VIM documents that are reserved at the moment; that means, at least
one work item belonging to the VIM document is reserved. The moment of time
is determined by the last update of the data.
The value in the Reserved column is a subset of the value in the In Process
column.
In Process
Number of VIM documents that have at least one work item in the following
states at the moment:
• waiting to be worked on in an inbox of the SAP Business Workplace, not yet

touched by any user
• reserved by a user
• worked on by a user
The moment of time is determined by the last update of the data.
VIM070500-03-RGD-EN-1
Total Time Spent

Time the agent/role spent working on VIM documents
Avg. Time
Average time the agent/role spent working on one VIM document
Avg. Wait Time

Note: The columns containing time data display the time in <xx>h <xx>m
<xx>s format. You can add corresponding columns that display the time in
seconds as a numeric value. This is useful, for example, if you want to
export data to an Excel spreadsheet.
Avg. # of Touches
Average number of how often a VIM document has been touched
Avg. # of Referrals
Average number of how often a VIM document has been referred to another
agent
Comparison To the right of the report period columns, the following columns are displayed for
period results the comparison period (indicated by Prev. in the column title):
Prev. Total # Processed

Number of VIM documents that have been worked on in the comparison period
Prev. Total Time Spent

Time the agent/role spent working on VIM documents
Prev. Avg. Time

Average time the agent/role spent working on one VIM document
Prev. Avg. Wait Time

Note: The columns containing time data display the time in <xx>h <xx>m
<xx>s format. You can add corresponding columns that display the time in
seconds as a numeric value. This is useful, for example, if you want to
export data to an Excel spreadsheet.
Prev. Avg. # of Touches

Average number of how often a VIM document has been touched
VIM070500-03-RGD-EN-1
Prev. Avg. # of Ref.

Average number of how often a VIM document has been referred to another
agent

To show details for a specific cell, double-click the cell in the ALV Grid. The
Document List opens, showing detailed information on the VIM documents
referred to in the selected cell.
Tip: The selected cell in the ALV Grid must contain data. Otherwise, the
The Document List displays data for an Agent in a Logical System or a Role,
depending on the grouping of the report. Displaying the Document List for a cell is
possible in all columns, except the columns containing time data. The layout of the
Document List depends on the selected column.
VIM070500-03-RGD-EN-1
Chapter 12
Using the Aging Report
The Aging Report reports about the aging of documents and work items in the
current system. The Aging Report comprises the following features:
• Provides an overview of the processing times of documents that have not been
posted without error.
• Provides a snapshot of documents that have not been posted and are still work in
process.
• Provides a snapshot of work items that are still work in process.
• Allows displaying a detailed list of:
• documents still in process, grouped by document type.
• work items still in process, grouped by role.

You control all functions of the Aging Report using a common selection screen.
To start the Aging Report:
• Run the /n/OPT/VIM_AGING transaction.

menu > Reports > Central Reporting > Aging Report.
VIM070500-03-RGD-EN-1
Chapter 12 Using the Aging Report

The following selection fields are specific for the Aging Report:
Org Related
Channel
Enter the channel. The channel indicates the input mode of invoices into
VIM, for example OCR.
Doc Characteristics
Click PO Invoices, Non-PO Invoices, or All Invoices (All Invoices includes
PO, Non PO and unclassified invoices).

invoices.
Vendor
Enter the vendor number, depending on the logical system.
Role ID
Enter the IDs of the roles you want to run the report for.
VIM070500-03-RGD-EN-1
Grouping
Select the parameter to group the report by: Click Document Type or Role.
Report Options
Buckets (in Days)

The report results are displayed in 4 so-called buckets, each of them
representing a time range of how long documents or work items have
stayed in the system. Each bucket corresponds with a table column in
the report screen. By default, the following buckets are defined:
• 0 to 30 Days
• 31 to 60 days
• 61 to 90 days
• > 90 days
Using the Buckets (in Days) fields, you can change the limits for the
buckets. Replace the default values 30 / 60 / 90, according to your needs.
For example, the screenshot in “Using the Report Screen” on page 123
shows buckets that are defined with 50 / 75 / 100

report.
VIM070500-03-RGD-EN-1

The following button is specific for the Aging Report:
Group By
as the Grouping settings in the selection screen. Click Doc Type or Role.
VIM070500-03-RGD-EN-1

determines the layout of the columns. If the report is grouped by Doc Type, the
logical systems are displayed at the very left of the table, followed by the Doc Type
information. If the report is grouped by Role, the Role information is displayed at
the very left of the table.
With Doc Type grouping, the data cells contain information about VIM documents.
With Role grouping, the data cells contain information about work items.
Report results Next to the right, the following columns are displayed:
Note: You can change the layout of the report results; for example, you can
shift, remove or add columns. So, your actual table might differ from the
Description
Description of the document type if you have grouped by Doc Type.
Description of the role if you have grouped by Role.
0 to 30 Days
This is the default setting. You can change the setting, using the Buckets (in
Days) parameter in the selection field panel. See Buckets (in Days) on page 123.
Number of documents that are work in process and have been in the system for
0 to 30 days.
31 to 60 Days
31 to 60 days.
61 to 90 Days
61 to 90 days.
>90 Days
more than 90 days.
VIM070500-03-RGD-EN-1

To show details for a specific cell, double-click the cell in the ALV Grid.
With Doc Type grouping, the Document List opens, showing detailed information
on the VIM documents referred to in the selected cell. The Document List shows
documents with a specific Logical System and Document Type.
With Role grouping, the Work Items with Exception List opens, showing detailed
information on the work items referred to in the selected cell. The Work Items with
Exception List shows work items with a specific Role.
Tips
• The selected cell in the ALV Grid must contain data. Otherwise, the
Document List or Work Items with Exception List cannot be displayed.
• Displaying the Document List or Work Items with Exception List for a cell
is possible in all columns with numeric values, except the cells containing
the Total.
• The layout of the Document List or Work Items with Exception List
depends on the selected column.
VIM070500-03-RGD-EN-1
Part 4
SAP NetWeaver Business Warehouse
Details
Part 4 SAP NetWeaver Business Warehouse Details
This part covers details about the following objects that are part of the VIM 7.0 BW
content for SAP NetWeaver Business Warehouse (SAP NetWeaver BW):
• InfoObjects
• DataSources
• DataStore Objects (DSOs)
• MultiProviders
Note: VIM 7.0 BW content is also used for VIM 7.5.
For more information, see Section 24 “SAP NetWeaver Business Warehouse

Content” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
VIM070500-03-RGD-EN-1
Chapter 13
InfoObjects
Business evaluation objects are known in SAP NetWeaver BW as InfoObjects.

InfoObjects are the basic information providers of SAP NetWeaver BW. They
structure the information needed to create data targets.
InfoObjects are divided into the following objects:

• Key Figures
• Characteristics (including time characteristics and technical characteristics)
• Units
13.1 Key Figures

Duration in Key figure: /OPT/KDURDAY
Days
This key figure shows the number of days for processing or approving a VIM
invoice. The characteristic “Time Group” determines whether the duration stands
for the process time or the approval time.
Technical data
Available as of VIM 7.0

Release
Data element /B7999/OIKDURDAY
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No
FI Amount in Key figure: 0DEB_CRE_DC

Document
Currency This key figure shows the amount of the SAP FI document (financial accounting
document) that was created from the VIM invoice in document currency
(0DOC_CURRCY).
For technical data, see the SAP documentation.
FI Amount in Key figure: 0DEB_CRE_LC

Local Currency
The key figure shows the amount of the SAP FI document (financial accounting
document) that was created from the VIM invoice in local currency
(0LOC_CURRCY), which means the currency of the company code.
VIM070500-03-RGD-EN-1
Chapter 13 InfoObjects
Gross Invoice Key figure: /OPT/KIVGAFC

Amount in
Favorite This key figure shows the gross invoice amount of a VIM invoice in the favorite
Currency
currency. The favorite currency is taken from the KPI Dashboard customizing in the
SAP ERP system.
Technical data

Release
Data element /OPT/KIVGAFC
Exception Summation
Aggregation
Restriction No
Currency /OPT/UF_CURR
Gross Invoice Key figure: 0LIV_IVGAIC

Amount in
Invoice This key figure shows the gross invoice amount of a VIM invoice in invoice currency
Currency
(0INV_CURR). Technically, it is populated with the value of field GROSS_AMOUNT of
table /OPT/VIM_1HEAD.
Number of Key figure: /OPT/KIVCT

Invoices
This key figure shows the number of invoices.
Technical data

Release
Data element /B7999/OIKIVCT
Exception Summation
Aggregation
Restriction No
Number of Key figure: /OPT/KIVECT

Invoices per
Exception This key figure shows the number of invoices to an exception ID.
VIM070500-03-RGD-EN-1
13.1. Key Figures
Technical data

Release
Data element /B7999/OIKIVECT
Exception Summation
Aggregation
Restriction No
Number of Key figure: /OPT/KIVEXCT

Invoices per
Exception Class This key figure shows the number of invoices to an exception class. An invoice with
several exceptions in an exception class is counted only once.
Technical data

Release
Data element /B7999/OIKIVEXCT
Exception Summation
Aggregation
Restriction No
Total Approval Key figure: /OPT/KAPDURD

Time (in Days)
This key figure shows the total approval time of a VIM invoice in days. This key
figure is calculated as sum of the durations of all approval processes during the VIM
process.
Technical data

Release
Data element /B7999/OIKAPDURD
Exception Summation
Aggregation
Restriction No
VIM070500-03-RGD-EN-1
Total Approval Key figure: /OPT/KAPDURS

Time (in
Seconds) This key figure shows the total approval time of a VIM invoice in seconds. This key
figure is calculated as sum of the durations of all approval processes during the VIM
process.
Technical data

Release
Data element /B7999/OIKAPDURS
Exception Summation
Aggregation
Restriction No
Total Time (in Key figure: /OPT/KTODURD

Days)
This key figure shows the total processing time of a VIM invoice in days. The total
processing time is the time from the start of the DP process until the end of the DP
process; this means the time from the start until the end of the DP workflow.
Technical data

Release
Data element /B7999/OIKTODURD
Exception Summation
Aggregation
Restriction No
Total Time (in Key figure: /OPT/KTODURS

Seconds)
This key figure shows the total processing time of a VIM invoice in seconds. The
total processing time is the time from the start of the DP process until the end of the
DP process; this means the time from the start until the end of the DP workflow.
Technical data

Release
Data element /B7999/OIKTODURS
VIM070500-03-RGD-EN-1
13.2. Characteristics
Exception Summation
Aggregation
Restriction No
13.2 Characteristics
Accounting Characteristic: 0AC_DOC_NO
document
number This characteristic shows the document number of the SAP invoice that was created
from the VIM invoice.
Amount Class Characteristic: /OPT/CAMTCL
This characteristic classifies VIM invoices into different categories according to their
invoice amount. An example for an amount class from the VIM baseline is “Small
amounts” for invoices below 10,000 EUR. The amount classes and their ranges are
maintained in the KPI Dashboard customizing in the leading SAP ERP system.
Technical data

Release
Data element /B7999/OICAMTCL
Change Run ID Characteristic: 0CHNGID
For details, see the SAP documentation.
Channel Characteristic: /OPT/CCHANNL
This characteristic shows the input channel of the VIM invoice. The channels are
maintained in the VIM customizing of the leading SAP ERP system.
Technical data

Release
Data element /B7999/OICCHANNL
Company Code Characteristic: 0COMP_CODE
This characteristic shows the company code of the VIM invoice.
VIM070500-03-RGD-EN-1
Company Code Characteristic: /OPT/CCOCOGR

Group
This characteristic groups company codes logically. The company code groups are
maintained in the KPI Dashboard customizing of the leading SAP ERP system. The
mapping of company codes to company code groups is maintained in the local SAP
ERP system of the VIM invoice.
IMG activity: Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice
Management > Cross Component Configuration > Central Reporting > KPI
Dashboard > Company Code Groups > Company Code Groups Mapping (BW).
Technical data

Release
Data element /B7999/OICCOCOGR
Created at Characteristic: /OPT/CCREACM

(Calendar Year/
Month) This characteristic shows the calendar year and calendar month when the VIM
invoice was created in the SAP ERP system.
Technical data

Release
Data element /B7999/OICCREACM
Reference 0CALMONTH
characteristic
Created at Characteristic: /OPT/CCREADT

(Date)
This characteristic shows the date when the VIM invoice was created in the SAP ERP
system.
Technical data

Release
Data element /B7999/OICCREADT
Reference 0DATE
characteristic
Created at Characteristic: /OPT/CCREATM

(Time)
This characteristic shows the time when the VIM invoice was created in the SAP
ERP system.
VIM070500-03-RGD-EN-1
Technical data

Release
Data element /B7999/OICCREATM
Reference 0TIME
characteristic
Created at Characteristic:/OPT/CCREATE
(UTC Time
Stamp in Short This characteristic shows the time stamp in UTC time (Coordinated Universal Time)
Form
(YYYYMMDDh when the VIM invoice was created.
hmmss))
Technical data

Release
Data element /B7999/OICCREATE
Credit Memo Characteristic: /OPT/CCMIND

Indicator
This characteristic classifies the VIM invoice as invoice or as credit memo.
Technical data

Release
Data element /B7999/OICCMIND
Currency Characteristic: /OPT/CCCDTFC

Conversion
Date for This characteristic shows the date that was used for the conversion of the gross
Conversion into
Favorite invoice amount of a VIM invoice from the invoice currency into the favorite
Currency currency. The favorite currency and the conversion date are determined from the
KPI Dashboard customizing in the SAP ERP system.
Technical data

Release
Data element /B7999/OICCCDTFC
Reference 0DATE
characteristic
Document Characteristic: /OPT/CDOCID

Ledger Number
This characteristic shows the document number of the VIM invoice.
VIM070500-03-RGD-EN-1
Technical data

Release
Data element /B7999/OICDOCID
Document Characteristic: /OPT/CDOCSTA

Status
This characteristic shows the document status of the VIM invoice.
Technical data

Release
Data element /B7999/OICDOCSTA
Document Type Characteristic: /OPT/CDOCTY
This characteristic shows the VIM document type of the VIM invoice. The VIM
document types are maintained in the VIM customizing of the SAP ERP system.
Technical data

Release
Data element /B7999/OICDOCTY
Due Date Characteristic: /OPT/CDUEDT
This characteristic shows the due date of the VIM invoice.
Technical data

Release
Data element /B7999/OICDUEDT
Exception Class Characteristic: /OPT/CEXCCL
Invoice exceptions that occur during the VIM process are grouped in exception
classes. This characteristic shows the exception class of an exception. Examples for
exception classes from the VIM baseline are “Compliance issue” and “Authorization
mismatch”. The exception class is determined from the exception class mapping in
the KPI Dashboard customizing of the leading SAP ERP system.
Technical data

Release
VIM070500-03-RGD-EN-1
Data element /B7999/OICEXCCL
Exception ID Characteristic: /OPT/CEXCEPT
This characteristic shows the exception ID of an exception that occurred during the
VIM process. The exception IDs are maintained in the Central Reporting
customizing in the leading SAP ERP system. Technically, the exception IDs
represent DP process types, header blocks, line blocks or PO/NPO parking reasons
that are to be seen as exceptions.
Technical data

Release
Data element /B7999/OICEXCEPT
Finished at Characteristic: 0CALYEAR

(Calendar Year)
This characteristic shows the calendar year when the processing of the VIM invoice
was finished. Technically, this is the calendar year when the DP workflow was
finished.
Finished at Characteristic: 0CALMONTH

(Calendar Year/
Month) This characteristic shows the calendar year and calendar month when the processing
of the VIM invoice was finished. Technically, this is the month when the DP
workflow was finished.
Finished at Characteristic: 0CALQUARTER

(Calendar Year/
Quarter) This characteristic shows the calendar year and calendar quarter when the
processing of the VIM invoice was finished. Technically, this is the calendar quarter
when the DP workflow was finished.
Finished at Characteristic: /OPT/CFINIDT

(Date)
This characteristic shows the date when the processing of the VIM invoice was
finished. Technically, this is the date when the DP workflow was finished.
Technical data

Release
Data element /B7999/OICFINIDT
VIM070500-03-RGD-EN-1
Reference 0DATE
characteristic
Finished at Characteristic: /OPT/CFINITM

(Time)
This characteristic shows the time when the processing of the VIM invoice was
finished. Technically, this is the time when the DP workflow was finished.
Technical data

Release
Data element /B7999/OICFINITM
Reference 0TIME
characteristic
Finished at Characteristic /OPT/CFINISH

(UTC Time
Stamp in Short
Form
This characteristic shows the time stamp in UTC time (Coordinated Universal Time)
(YYYYMMDDh when the processing of the VIM invoice was finished. Technically, this is the point of
hmmss)) time when the DP workflow was finished.
Technical data

Release
Data element /B7999/OICFINISH
Fiscal Year Characteristic: 0FISCYEAR
This characteristic shows the fiscal year of the SAP invoice that was created from the
VIM invoice.
Fiscal Year Characteristic: 0FISCVARNT

Variant
This characteristic shows the fiscal year variant from the company code of the VIM
invoice.
Indicator if Characteristic: /OPT/CPOBAS

Invoice is PO
Based or not
This characteristic shows whether the VIM invoice refers to a purchase order or not.
VIM070500-03-RGD-EN-1
Technical data

Release
Data element /B7999/OICPOBAS
Indicator if Characteristic: /OPT/CAPPIND

Invoice was
Approved or not This characteristic indicates if the VIM invoice or its related SAP invoice was
approved at least once.
Technical data

Release
Data element /B7999/OICAPPIND
Indicator if Characteristic: /OPT/CBLKIND

invoice was
Blocked or not This characteristic indicates if a payment block occurred at least once. This
characteristic is populated for PO based invoices only.
Technical data

Release
Data element /B7999/OICBLKIND
Indicator if Characteristic: /OPT/CREFIND

Invoice was
Referred or not This characteristic indicates if the VIM invoice was referred at least once.
Technical data

Release
Data element /B7999/OICREFIND
Indicator if Characteristic: /OPT/CREJIND

Invoice was
Rejected or not This characteristic indicates if the VIM invoice was rejected at least once.
Technical data

Release
Data element /B7999/OICREJIND
VIM070500-03-RGD-EN-1
Parked at Characteristic: /OPT/CPARKCM

(Calendar Year/
invoice was parked.
Technical data

Release
Data element /B7999/OICPARKCM
Reference 0CALMONTH
characteristic
Parked at Characteristic: /OPT/CPARKDT

(Date)
This characteristic shows the date when the VIM invoice was parked.
Technical data

Release
Data element /B7999/OICPARKDT
Reference 0DATE
characteristic
Parked at Characteristic: /OPT/CPARKTM

(Time)
This characteristic shows the time when the VIM invoice was parked.
Technical data

Release
Data element /B7999/OICPARKTM
Reference 0TIME
characteristic
Parked at (UTC Characteristic: /OPT/CPARKED

Time Stamp in
Short Form This characteristic shows the time stamp in UTC time (Coordinated Universal Time)
(YYYYMMDDh
hmmss)) when the VIM invoice was parked.
Technical data

Release
Data element /B7999/OICPARKED
VIM070500-03-RGD-EN-1
Posted at Characteristic: /OPT/CPOSTCM

(Calendar Year/
invoice was posted.
Technical data

Release
Data element /B7999/OICPOSTCM
Reference 0CALMONTH
characteristic
Posted at Characteristic: /OPT/CPOSTDT

(Date)
This characteristic shows the date when the VIM invoice was posted.
Technical data

Release
Data element /B7999/OICPOSTDT
Reference 0DATE
characteristic
Posted at Characteristic: /OPT/CPOSTTM

(Time)
This characteristic shows the time when the VIM invoice was posted.
Technical data

Release
Data element /B7999/OICPOSTTM
Reference 0TIME
characteristic
Posted at (UTC Characteristic: /OPT/CPOSTED

Time Stamp in
Short Form This characteristic shows the time stamp in UTC time (Coordinated Universal Time)
(YYYYMMDDh
hmmss)) when the VIM invoice was posted.
Technical data

Release
Data element /B7999/OICPOSTED
VIM070500-03-RGD-EN-1
Purchasing Or- Characteristic: 0PURCH_ORG

ganization
This characteristic shows the purchasing organization of the purchase order that the
VIM invoice refers to. This characteristic is populated only
• for PO based invoices, and

• if there is only one purchase order assigned.
Purchasing Characteristic: 0PUR_GROUP

Group
This characteristic shows the purchasing group of the purchase order that the VIM
invoice refers to. This characteristic is populated only
• for PO based invoices, and

• if there is only one purchase order assigned.
Record Type Characteristic: 0RECORDTP
Request ID Characteristic: 0REQUID
Source System Characteristic: 0LOGSYS
This characteristic shows the name of the logical system of the OLTP source system
(SAP ERP system).
Source System Characteristic: 0SOURSYSTEM

ID
Source systems can be assigned and logically grouped to source system IDs in the
SAP NetWeaver BW system. This characteristic shows the source system ID. The
assignment of source system to source system IDs is maintained in the SAP
NetWeaver BW system (transaction code RSA1).
For more details, see the SAP documentation.
Time Group Characteristic: /OPT/CTIMEGR
This characteristic determines whether key figures with duration stand for the
process time or the approval time. The time group definitions are maintained in the
KPI Dashboard customizing in the leading SAP ERP system.
VIM070500-03-RGD-EN-1
Technical data

Release
Data element /B7999/OICTIMEGR
Time Type Characteristic: /OPT/CTIMETY
This characteristic shows the time type of a duration value. The time type classifies
durations within the VIM process. An example for a time type from the VIM
baseline is “On time” for VIM invoices that have been processed in 0 to 5 days. The
time types are maintained in the KPI Dashboard customizing in the leading SAP
ERP system. The compounded characteristic Time Group determines whether the
time type refers to the processing time or the approval time.
Technical data

Release
Data element /B7999/OICTIMETY
Compounding /OPT/CTIMEGR
Time Type of Characteristic: /OPT/CAPTITY

Approval Time
This characteristic shows the time type of the approval time of the VIM invoice. The
time types are determined from the time group ranges maintained in the KPI
Dashboard customizing in the leading SAP ERP system. Examples for time types
from the VIM baseline are “On time” and “Delayed”.
Technical data

Release
Data element /B7999/OICAPTITY
Time Type of Characteristic: /OPT/CTOTITY

Total Time
This characteristic shows the time type of the total processing time of the VIM
invoice. The time types are determined from the time group ranges maintained in
the KPI Dashboard customizing in the leading SAP ERP system. Examples for time
types from the VIM baseline are “On time” and “Delayed”.
Technical data

Release
Data element /B7999/OICTOTITY
VIM070500-03-RGD-EN-1
Updated at Characteristic: /OPT/CUPDTS

(UTC Time
Stamp in Short This characteristic shows the time stamp in UTC time (Coordinated Universal Time)
Form
(YYYYMMDDh
when the VIM invoice was selected for the SAP NetWeaver BW extraction.
hmmss)) Technically, this is the point of time when the KPI collection report selected the VIM
invoice.
Technical data

Release
Data element /B7999/OICUPDTS
Vendor Characteristic: 0VENDOR
This characteristic shows the vendor the VIM invoice was sent from.
Vendor Group Characteristic: /OPT/CVENDGR
This characteristic shows the vendor group, the VIM invoice is assigned to. The
vendor group classifies vendors into different groups regarding their total invoice
volume. An example for a vendor group from the VIM baseline is “Vendor Group A
(high volumes)”. You maintain the vendor groups in the KPI Dashboard
customizing of the leading SAP ERP system. You maintain the mapping of vendors
to vendor groups in the local SAP ERP system of the VIM invoice. If the vendor of
the VIM invoice is not assigned to a vendor group, the ABC indicator from the
purchasing organization data of the vendor master data is taken.
Technical data

Release
Data element /B7999/OICVENDGR
13.3 Units
Currency of Unit: 0INV_CURR
Invoice
This unit shows the document currency of the VIM invoice.
Document Unit: 0DOC_CURRCY

Currency
This unit shows the currency of the SAP FI document (financial accounting
document) that was created from the VIM invoice.
VIM070500-03-RGD-EN-1
13.3. Units
Favorite Unit: /OPT/UF_CURR

Currency
This unit shows the favorite currency of amount values. The favorite currency is
taken from the KPI Dashboard customizing of the SAP ERP system.
Technical data

Release
Data element /B7999/OIUF_CURR
Reference unit 0CURRENCY
Local Currency Unit: 0LOC_CURRCY
This unit shows the local currency (this means the currency of the company code) of
the SAP FI document (financial accounting document) that was created from the
VIM invoice.
VIM070500-03-RGD-EN-1
Chapter 14
DataSources
A DataSource is a set of fields that provide the data for a business unit for data
transfer into an SAP NetWeaver BW system. DataSources can be divided into:
• DataSources for transaction data
• DataSources for master data
14.1 DataSources for Transaction Data

Document DataSource Transactional Data: /OPT/VIM_DPDOC_H_TRAN
Header
This structure serves to consistently extract transaction data on VIM invoices from
VIM to a SAP NetWeaver BW system. The data is extracted on header level (/OPT/
VIM_1HEAD). Only finished invoices (= DP workflow is finished) that are not
obsolete or canceled are extracted. As a further restriction, invoices are extracted
only if they have been finished since VIM 5.2 SP8/VIM 6.0 SP3 or higher.
Technical data
Application OpenText Vendor Invoice Management > DP Documents

Component
Available as of VIM 7.0 (SAP ERP 6.0)
Release
Delta-Capable Yes
Delta Process AIE = After-Images Via Extractor
Extraction from No
Archives
Extraction by Function module /OPT/BGET_DPDOC_H
Extraction /OPT/BEXTR_DPDOC_H_TRAN_ST
Structure
Exception DataSource Transactional Data: OPT/VIM_EXC_TRAN
This structure serves to consistently extract exception data to VIM invoices from
VIM to a SAP NetWeaver BW system. Only exceptions of finished invoices (= DP
workflow is finished) that are not obsolete or canceled are extracted.
Technical data
Application OpenText Vendor Invoice Management > Exceptions

Component
VIM070500-03-RGD-EN-1
Chapter 14 DataSources

Release
Delta-Capable Yes
Delta Process AIE = After-Images Via Extractor
Extraction from No
Archives
Extraction by Function module /OPT/BGET_EXCEPTIONS
Extraction /OPT/BEXTR_EXC_TRAN_ST
Structure
14.2 DataSources for Master Data

Amount Class DataSource Master Data Attributes: /OPT/VIM_AMTCL_ATTR
(Attributes)
This structure serves to consistently extract master data on amount classes from VIM
to a SAP NetWeaver BW system. The amount class classifies VIM invoices into
different categories according to their invoice amount. An example for an amount
class from the VIM baseline is “Small amounts” for invoices below 10,000 EUR. The
amount classes are maintained in the KPI Dashboard customizing of VIM in the
leading SAP ERP system.
Technical data
Application OpenText Vendor Invoice Management > Master Data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/KAGR_C_AMNP
Extraction /OPT/ESVIM_AMTCL_ATTR0001
Structure
Amount Class DataSource Texts: /OPT/VIM_AMTCL_TEXT

(Texts)
This structure serves to consistently extract texts of amount classes from VIM to a
SAP NetWeaver BW system. The amount class classifies VIM invoices into different
categories according to their invoice amount. An example for an amount class text
from the VIM baseline is “Small amounts”. The amount classes and their texts are
maintained in the KPI Dashboard customizing of VIM in the leading SAP ERP
system.
VIM070500-03-RGD-EN-1
14.2. DataSources for Master Data
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by Function module /OPT/BGET_AMOUNTCLASS_TEXT
Extraction /OPT/BEXTR_AMTCL_TEXT_ST
Structure
Channel DataSource Master Data Attributes: /OPT/VIM_CHANNEL_ATTR

(Attributes)
This structure serves to consistently extract master data on input channels from VIM
to a SAP NetWeaver BW system. The channels are maintained in the VIM
customizing of the leading SAP ERP system.
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB View/Table /OPT/VIM_CHNL
Extraction /OPT/ESVIM_CHANNEL_AT0001
Structure
Channel (Texts) DataSource Texts: /OPT/VIM_CHANNEL_TEXT
This structure serves to consistently extract the texts of input channels from VIM to a
SAP NetWeaver BW system. The channels and their texts are maintained in the VIM
Technical data

Component
Release
Delta-Capable No
VIM070500-03-RGD-EN-1
Extraction from No
Archives
Extraction by DB view/table /OPT/VIM_CHNL_T
Extraction /OPT/ESVIM_CHANNEL_TE0001
Structure
Channel Type DataSource Texts: /OPT/VIM_CHATY_TEXT

(Texts)
This structure serves to consistently extract texts of channel types from VIM to a
SAP NetWeaver BW system. The channel types and their texts are read from the
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by Fixed values of domain /OPT/CHANNEL_TYPE
Company Code DataSource Master Data Attributes: /OPT/VIM_COCO_ATTR

(Attributes)
This structure serves to consistently extract the mapping of company codes to
company code groups from VIM to a SAP NetWeaver BW system. The mapping of
company codes to company code groups is maintained in the KPI Dashboard
customizing of VIM in the SAP ERP system(s).
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/BT_CCGP
Extraction /OPT/ESVIM_COCO_ATTR0001
Structure
Company Code DataSource Texts: /OPT/VIM_CCGROUP_TEXT

Group (Texts)
VIM070500-03-RGD-EN-1
This structure serves to consistently extract texts of company code groups from VIM
to a SAP NetWeaver BW system. The company code group groups company codes
logically. The company code groups and their texts are maintained in the KPI
Dashboard customizing of VIM in the leading SAP ERP system.
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB View/Table /OPT/KAGR_C_CCGT
Extraction /OPT/ESVIM_CCGROUP_TE0001
Structure
Document DataSource Texts: /OPT/VIM_DOCSTA_TEXT

Status (Texts)
This structure serves to consistently extract texts of document status from VIM to a
SAP NetWeaver BW system. The document status and their texts are maintained in
the VIM customizing of the leading SAP ERP system.
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/VIM_T101T
Extraction /OPT/ESVIM_DOCSTA_TEX0001
Structure
Document Type DataSource Texts: /OPT/VIM_DOCTY_TEXT

(Texts)
This structure serves to consistently extract texts of VIM document types from VIM
to a SAP NetWeaver BW system. The VIM document types and their texts are
maintained in the VIM customizing of the SAP ERP system(s).
VIM070500-03-RGD-EN-1
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/VIM_T100T
Extraction /OPT/ESVIM_DOCTY_TEXT0001
Structure
Exception DataSource Master Data Attributes: /OPT/VIM_EXCEPT_ATTR

(Attributes)
This structure serves to consistently extract the mapping of exception IDs to
exception classes from VIM to a SAP NetWeaver BW system. The mapping of
exceptions to exception classes is maintained in the KPI Dashboard customizing of
VIM in the leading SAP ERP system.
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/KAGR_C_EXCP
Extraction /OPT/ESVIM_EXCEPT_ATT0001
Structure
Exception DataSource Texts: /OPT/VIM_EXCEPT_TEXT

(Texts)
This structure serves to consistently extract the texts of exception IDs from VIM to a
SAP NetWeaver BW system. The exception IDs and their texts are maintained in the
Central Reporting customizing of VIM in the leading SAP ERP system.
Technical data

Component
Release
VIM070500-03-RGD-EN-1
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/VT_EXC_T
Extraction /OPT/ESVIM_EXCEPT_TEX0001
Structure
Exception Class DataSource Texts: /OPT/VIM_EXCCL_TEXT

(Texts)
This structure serves to consistently extract the texts of exception classes from VIM
to a SAP NetWeaver BW system. The exception class groups VIM exceptions
logically. Examples for exception classes from the VIM baseline are “Compliance
issue” and “Authorization mismatch”. The exception classes and their texts are
maintained in the KPI Dashboard customizing of VIM in the leading SAP ERP
system.
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/KAGR_C_EXCT
Extraction /OPT/ESVIM_EXCCL_TEXT0001
Structure
Time Group DataSource Texts: /OPT/VIM_TIMEGR_TEXT

(Texts)
This structure serves to consistently extract the texts of time groups from VIM to a
SAP NetWeaver BW system. Time groups from the VIM baseline are “Processing
Time” and “Approval Time”. The time groups and their texts are maintained in the
KPI Dashboard customizing of VIM in the leading SAP ERP system.
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
VIM070500-03-RGD-EN-1
Extraction by DB view/table /OPT/KAGR_C_TMGT

Extraction /OPT/ESVIM_TIMEGR_TEX0001
Structure
Time Type DataSource Master Data Attributes: /OPT/VIM_TIMETY_ATTR

(Attributes)
This structure serves to consistently extract master data on time types from VIM to a
SAP NetWeaver BW system. The time type classifies durations within the VIM
process. An example for a time type from the VIM baseline is “On time” for VIM
invoices that have been processed in 0 to 5 days. The time types are maintained in
the KPI Dashboard customizing of VIM in the leading SAP ERP system.
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/KAGR_C_TMR
Extraction /OPT/ESVIM_TIMETY_ATT0001
Structure
Time Type DataSource Texts: /OPT/VIM_TIMETY_TEXT

(Texts)
This structure serves to consistently extract texts of time types from VIM to a SAP
NetWeaver BW system. The time type classifies durations within the VIM process.
An example for a time type text regarding the processing time is “On time”. The
time type texts are maintained in the KPI Dashboard customizing of VIM in the
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by Function module /OPT/BGET_TIMETYPE_TEXT
Extraction /OPT/BEXTR_TIMETY_TEXT_ST
Structure
VIM070500-03-RGD-EN-1
Vendor DataSource Master Data Attributes: /OPT/VIM_VENDOR_ATTR

(Attributes)
This structure serves to consistently extract the mapping of vendors to vendor
groups from VIM to a SAP NetWeaver BW system. The mapping of vendors to
vendor groups is maintained in the KPI Dashboard customizing of VIM in the SAP
ERP system(s).
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/KAGR_C_VNDP
Extraction /OPT/ESVIM_VENDOR_ATT0001
Structure
Vendor Group DataSource Texts: /OPT/VIM_VENDGR_TEXT

(Texts)
This structure serves to consistently extract texts of vendor groups from VIM to a
SAP NetWeaver BW system. The vendor group classifies vendors into different
groups regarding their total invoice volume. An example for a vendor group from
the VIM baseline is “Vendor Group A (high volumes)”. The vendor groups and their
texts are maintained in the KPI Dashboard customizing of VIM in the leading SAP
ERP system.
Technical data

Component
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/KAGR_C_VNDT
Extraction /OPT/ESVIM_VENDGR_TEX0001
Structure
VIM070500-03-RGD-EN-1
Chapter 15
DataStore Objects (DSOs)
A DataStore object (DSO) serves as a storage location for consolidated and cleansed
transaction data or master data on a document (atomic) level. When being used as a
storage location for history reasons, the DSO may also store raw data.
The VIM BW content has been designed following the OpenText VIM Layered
Scalable Architecture (LSA), which groups the SAP NetWeaver BW objects into
different logical layers. The OpenText VIM LSA is based on the SAP LSA. For
details, see Section 24.1 “OpenText VIM Layered Scalable Architecture (LSA)” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD). The VIM BW content uses DSOs in the Data Propagation Layer and in the
Corporate Memory Layer.
15.1 DSOs of the Data Propagation Layer

The purpose of the Data Propagation Layer is to provide prepared, harmonized and
consistent data in an application-neutral, universally valid form.
15.1.1 DSOs of the Data Propagation Layer for Transaction

Data
DP Documents DataStore object: /OPT/DPDOC
This DSO contains VIM invoice headers from the SAP ERP system on a granular
level. The DSO is directly supplied from the DataSource /OPT/VIM_DPDOC_H_TRAN.
Data Sources/Data Targets - As a source of the DSO, the Document Header

DataSource (/OPT/VIM_DPDOC_H_TRAN) is used. This means that finished invoices (=
DP workflow is finished) that are not obsolete or canceled can be loaded into the
DSO.
Most relevant fields are updated in a 1:1 mapping into the DSO. Some fields
(amount class, company code group) are derived from the active tables of the Amount
Class DSO (/OPT/DPAMC) and the Company Group Mapping for Company Code DSO
(/OPT/DPCCG). Several time fields are derived from time stamps.
As a further source of the DSO, the DP Documents DSO (/OPT/DCDOC) from the
Corporate Memory Layer can be used for recovery purposes.
As a target of the DSO, the following are supplied:

• DSO Exception Classes with DP Documents (/OPT/DPEXCD)
• DSO Exceptions with DP Documents (/OPT/DPEXD)
• InfoCube DP Documents: Volume and Amount (/OPT/CRDOC01)
VIM070500-03-RGD-EN-1
Chapter 15 DataStore Objects (DSOs)
• InfoCube DP Documents: Times (/OPT/CRDOC02)

• MultiProvider DP Documents: Details (/OPT/MVDOC03)
Exception DataStore object: /OPT/DPEXCD

Classes with
DP Documents This DataStore object contains VIM invoices together with their exception classes,
which they have exceptions to. It also contains VIM invoices without any exception.
Data Sources/Data Targets - As a source of the DSO, the DP Documents DSO (/

OPT/DPDOC) and the Exceptions DSO (/OPT/DPEXC) are used.
Most relevant fields from the DP Documents DSO are updated in a 1:1 mapping into
the DSO. The exception class is derived from the active table of the Exception Class
Mapping for Exception DSO (/OPT/DPEID). If the DP document does not have any
exceptions, 0 is set as an initial value in the field Exception Class (/OPT/CEXCCL).
The exception specific fields from the Exceptions DSO are updated in a 1:1
mapping into the DSO. The end routine adds DP document data from the active
table of the DP documents DSO (/OPT/DPDOC). The field Number of Invoices per
Exception Class (/OPT/KIVEXCT) is set to 1, which indicates that there is one
invoice to this exception class. Even if a DP document has several exceptions to an
exception class, the invoice is counted only once.
• InfoCube Exception Classes: Occurences (/OPT/CREXC01)

• MultiProvider Exception Classes: Details (/OPT/MVEXC01)
Exceptions DataStore object: /OPT/DPEXC
This DataStore object contains exceptions to VIM invoices from the SAP ERP system.
The exception IDs are maintained in the Central Reporting customizing in the
leading SAP ERP system. Technically, the exception IDs represent DP process types,
header blocks, line blocks or PO/NPO parking reasons that are to be seen as
exceptions.
Data Sources/Data Targets - As a source of the DSO, the Exception DataSource (/

OPT/VIM_EXC_TRAN) is used. This means that exceptions of finished invoices (= DP
workflow is finished) that are not obsolete or canceled can be loaded into the DSO.
Most relevant fields are updated in a 1:1 mapping into the DSO. The exception class
is derived from the active table of the Exception Class Mapping for Exception
DSO (/OPT/DPEID). As a further source of the DSO, the Exceptions DSO (/
OPT/DPEXC) from the Corporate Memory Layer can be used for recovery purposes.
• DSO Exceptions with DP Documents (/OPT/DPEXD)

• DSO Exception Classes with DP Documents (/OPT/DPEXCD)
VIM070500-03-RGD-EN-1
15.1. DSOs of the Data Propagation Layer
Exceptions with DataStore object: /OPT/DPEXD

DP Documents
This DataStore object contains VIM invoices together with their exceptions. It also
contains VIM invoices without any exception.
Data Sources/Data Targets - As a source of the DSO, the DP Documents DSO (/

OPT/DPDOC) and the Exceptions DSO (/OPT/DPEXC) are used.
Most relevant fields from the DP Documents DSO are updated in a 1:1 mapping into
the DSO. The exception class is derived from the active table of the Exception Class
Mapping for Exception DSO (/OPT/DPEID). If the DP document does not have any
exceptions, the Exception ID field (/OPT/CEXCEPT) is kept empty and the field
Exception Class (/OPT/CEXCCL) is set to 0 as an initial value.
The exception specific fields from the Exceptions DSO are updated in a 1:1
mapping into the DSO. The end routine adds DP document data from the active
table of the DP documents DSO (/OPT/DPDOC). The field Number of Invoices per
Exception (/OPT/KIVEXT) is set to 1, which indicates that there is one invoice to this
exception.

• InfoCube Exceptions: Occurences (/OPT/CREXC02)
• MultiProvider Exceptions: Details (/OPT/MVEXC03)
15.1.2 DSOs of the Data Propagation Layer for Master Data

Amount Class DataStore object: /OPT/DPAMC
This DataStore object contains the amount classes together with their amount ranges
from the leading SAP ERP system. The amount classes and their ranges are
maintained in the KPI Dashboard customizing of the leading SAP ERP system.
Data Sources/Data Targets - As a source of the DSO, the Amount Class DataSource
(/OPT/VIM_AMTCL_ATTR) is used. As a further source of the DSO, the Amount
Classes DSO (/OPT/DCAMC) from the Corporate Memory Layer can be used for
recovery purposes. For both sources, all fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the InfoObject Amount Class (/OPT/CAMTCL) is supplied.

Additionally, the active table of the DSO is used within transformations to
determine the amount class for a DP document.
Channel DataStore object: /OPT/DPCHA
This DataStore object contains the input channels together with their channel type
from the leading SAP ERP system. The channels are maintained in the VIM
Data Sources/Data Targets - As a source of the DSO, the Channel DataSource (/

OPT/VIM_CHANNEL_ATTR) is used. As a further source of the DSO, the Channel DSO
VIM070500-03-RGD-EN-1
(/OPT/DCCHA) from the Corporate Memory Layer can be used for recovery purposes.
For both sources, all fields are updated in a 1:1 mapping into the DSO.
As a target of the DSO, the InfoObject Channel (/OPT/CCHANNL) is supplied.
Company DataStore object: /OPT/DPCCG

Group Mapping
for Company
Code
This DataStore object contains the mapping of company codes to company code
groups from all the connected SAP ERP systems. The company code groups itself
are maintained in the KPI Dashboard customizing of the leading SAP ERP system.
The mapping of company codes to company code groups is maintained in the KPI
Dashboard customizing of all SAP ERP systems that are connected to the SAP
NetWeaver BW system.
Data Sources/Data Targets - As a source of the DSO, the Company Code DataSource
(/OPT/VIM_COCO_ATTR) is used. As a further source of the DSO, the Company Code
Group Mapping for Company Code DSO (/OPT/DCCCG) from the Corporate Memory
Layer can be used for recovery purposes. For both sources, all fields are updated in a
1:1 mapping into the DSO.
There is no target of the DSO. The active table of the DSO is used within
transformations to determine the company code group to a company code.
Exception Class DataStore object: /OPT/DPEID

Mapping for
Exception
This DataStore object contains the mapping of exception IDs to exception classes
from the leading SAP ERP system. The exception class mapping is maintained in the
KPI Dashboard customizing of the leading SAP ERP system.

OPT/VIM_EXCEPT_ATTR) is used. As a further source of the DSO, the Exception
Class Mapping for Exception DSO (/OPT/DCEID) from the Corporate Memory
Layer can be used for recovery purposes. For both sources, all fields are updated in a
As a target of the DSO, the InfoObject Exception ID (/OPT/CEXCEPT) is supplied.

determine the exception class to exceptions.
Time Type DataStore object: /OPT/DPTTY
This DataStore object contains the time types to all time groups together with their
ranges. The time types and their ranges are maintained in the KPI Dashboard
Data Sources/Data Targets - As a source of the DSO, the Time Type DataSource (/
OPT/VIM_TIMETY_ATTR) is used. As a further source of the DSO, the Time Types
DSO (/OPT/DCTTY) from the Corporate Memory Layer can be used for recovery
purposes. For both sources, all fields are updated in a 1:1 mapping into the DSO.
VIM070500-03-RGD-EN-1
15.2. DSOs of the Corporate Memory Layer
As a target of the DSO, the InfoObject Time Type (/OPT/CTIMETY) is supplied.

determine the time type to the processing time/the approval time of a DP document.
Vendor Group DataStore object: /OPT/DPVEN

Mapping for
Vendor This DataStore object contains the mapping of vendors to vendor groups from all
connected SAP ERP systems. The vendor groups itself are maintained in the KPI
Dashboard customizing of the leading SAP ERP system. The mapping of vendors to
vendor groups is maintained in the KPI Dashboard customizing of all SAP ERP
systems that are connected to the SAP NetWeaver BW system.
Data Sources/Data Targets - As a source of the DSO, the Vendor DataSource (/

OPT/VIM_VENDOR_ATTR) is used. As a further source of the DSO, the Vendor Group
Mapping for Vendor DSO (/OPT/DCVEN) from the Corporate Memory Layer can be
used for recovery purposes. For both sources, all fields are updated in a 1:1 mapping
into the DSO.
There is no target of the DSO. The DSO can be used to determine the vendor group
to vendors within transformations.
15.2 DSOs of the Corporate Memory Layer

The purpose of the Corporate Memory and its DSOs is to save raw data permanently
for history reasons to help recovery in case of any eventuality.
15.2.1 DSOs of the Corporate Memory Layer for Transaction

Data
DP Documents DataStore object: /OPT/DCDOC
This DataStore object contains the VIM invoice headers as raw data as extracted by
the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Document Header

DataSource (/OPT/VIM_DPDOC_H_TRAN) is used. All relevant fields are updated in a
As a target of the DSO, the DSO DP Documents (/OPT/DPDOC) is supplied.
Exceptions DataStore object: /OPT/DCEXC
This DataStore object contains exceptions to VIM invoices as raw data as extracted
by the corresponding DataSource.

OPT/VIM_EXC_TRAN) is used. All relevant fields are updated in a 1:1 mapping into
the DSO.
As a target of the DSO, the DSO Exceptions (/OPT/DPEXC) of the Data Propagation
Layer is supplied.
VIM070500-03-RGD-EN-1
15.2.2 DSOs of the Corporate Memory Layer for Master Data

Amount DataStore object: /OPT/DCAMC
Classes
This DataStore object contains the amount classes together with their amount ranges
from the leading SAP ERP system as raw data as extracted by the corresponding
DataSource.
Data Sources/Data Targets - As a source of the DSO, the Amount Class DataSource
(/OPT/VIM_AMTCL_ATTR) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the DSO Amount Class (/OPT/DPAMC) of the Data
Propagation Layer is supplied.
Amount Class DataStore object: /OPT/DCAMCT

Texts
This DataStore object contains the texts of amount classes from the leading SAP ERP
system as raw data as extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Amount Class Text
DataSource (/OPT/VIM_AMTCL_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.
As a target of the DSO, the InfoObject Amount Class (/OPT/CAMTCL) is supplied.
Channels DataStore object: /OPT/DCCHA
This DataStore object contains the possible input channels of VIM invoices as raw
data as extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Channel DataSource (/

OPT/VIM_CHANNEL_ATTR) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the DSO Channel (/OPT/DPCHA) of the Data Propagation
Layer is supplied.
Channel Texts DataStore object: /OPT/DCCHAT
This DataStore object contains the texts of the possible input channels of VIM
invoices as raw data as extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Channel Text DataSource
(/OPT/VIM_CHANNEL_TEXT) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the InfoObject Channel (/OPT/CCHANNL) is supplied.
Channel Type DataStore object: /OPT/DCCHTT

Texts
VIM070500-03-RGD-EN-1
This DataStore object contains the texts of the possible types of input channels of
VIM invoices as raw data as extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Channel Type Text
DataSource (/OPT/VIM_CHATY_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.
As a target of the DSO, the InfoObject Channel Type (/OPT/CCHATY) is supplied.
Company Code DataStore object: /OPT/DCCCG

Group Mapping
for Company This DataStore object contains the mapping of company codes to company code
Code
groups as raw data as extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Company Code DataSource
(/OPT/VIM_COCO_ATTR) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the DSO Company Code Group Mapping for Company Code (/
OPT/DPCCG) of the Data Propagation Layer is supplied.
Company Code DataStore object: /OPT/DCCCGT

Group Texts
This DataStore object contains the texts of company code groups as raw data as
extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Company Code Group Text
DataSource (/OPT/VIM_CCGROUP_TEXT) is used. All fields are updated in a 1:1
mapping into the DSO.
As a target of the DSO, the InfoObject Company Code Group (/OPT/CCOCOGR) is

supplied.
Document DataStore object: /OPT/DCDSTT

Status Texts
This DataStore object contains the document status texts of VIM invoices as raw data
as extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Document Status Text
DataSource (/OPT/VIM_DOCSTA_TEXT) is used. All fields are updated in a 1:1
As a target of the DSO, the InfoObject Document Status (/OPT/CDOCSTA) is

supplied.
Document Type DataStore object: /OPT/DCDTYT

Texts
This DataStore object contains the texts of VIM document types as raw data as
extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Document Type Text
DataSource (/OPT/VIM_DOCTY_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.
VIM070500-03-RGD-EN-1
As a target of the DSO, the InfoObject Document Type (/OPT/CDOCTY) is supplied.
Exception Class DataStore object: /OPT/DCEID

Mapping for
Exception This DataStore object contains the mapping of exceptions to exception classes as raw
data as extracted by the corresponding DataSource.

OPT/VIM_EXCEPT_ATTR) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the DSO Exception Class Mapping for Exception (/
OPT/DPEID) of the Data Propagation Layer is supplied.
Exception Class DataStore object: /OPT/DCECLT

Texts
This DataStore object contains the texts of exception classes as raw data as extracted
by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Exception Class Text
DataSource (/OPT/VIM_EXCCL_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.
As a target of the DSO, the InfoObject Exception Class (/OPT/CEXCCL) is supplied.
Exception Texts DataStore object: /OPT/DCEIDT
This DataStore object contains the texts of exceptions as raw data as extracted by the
corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Exception Text

DataSource (/OPT/VIM_EXCEPT_TEXT) is used. All fields are updated in a 1:1
As a target of the DSO, the InfoObject Exception (/OPT/CEXCEPT) is supplied.
Time Group DataStore object: /OPT/DCTGRT

Texts
This DataStore object contains the texts of time groups as raw data as extracted by
the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Time Group Text
DataSource (/OPT/VIM_TIMEGR_TEXT) is used. All fields are updated in a 1:1
As a target of the DSO, the InfoObject Time Group (/OPT/CTIMEGR) is supplied.
Time Types DataStore object: /OPT/DCTTY
This DataStore object contains the possible time types as raw data as extracted by the
VIM070500-03-RGD-EN-1
Data Sources/Data Targets - As a source of the DSO, the Time Type DataSource (/
OPT/VIM_TIMETY_ATTR) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the DSO Time Type (/OPT/DPTTY) of the Data Propagation
Layer is supplied.
Time Type DataStore object: /OPT/DCTTYT

Texts
This DataStore object contains the texts of time types as raw data as extracted by the
Data Sources/Data Targets - As a source of the DSO, the Time Type Text DataSource
(/OPT/VIM_TIMETY_TEXT) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the InfoObject Time Type (/OPT/CTIMETY) is supplied.
Vendor Group DataStore object: /OPT/DCVEN

Mapping for
Vendor This DataStore object contains the mapping of vendors to vendor groups as raw data
as extracted by the corresponding DataSource.
Data Sources/Data Targets - As a source of the DSO, the Vendor DataSource (/

OPT/VIM_VENDOR_ATTR) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the DSO Vendor Group Mapping for Vendor (/OPT/DPVEN)
of the Data Propagation Layer is supplied.
Vendor Group DataStore object: /OPT/DCVGRT

Texts
This DataStore object contains the texts of vendor groups as extracted by the
Data Sources/Data Targets - As a source of the DSO, the Vendor Group Text
DataSource (/OPT/VIM_VENDGR_TEXT) is used. All fields are updated in a 1:1
As a target of the DSO, the InfoObject Vendor Group (/OPT/CVENDGR) is supplied.
VIM070500-03-RGD-EN-1
Chapter 16
MultiProviders
This chapter focuses on the final data targets in the Virtualization Layer: the
MultiProviders.
SAP recommends to create reports, for example BEx Queries, on MultiProviders and
not on InfoCubes directly. Therefore the VIM 7.0 BW content delivers
MultiProviders for all its InfoCubes. Technically, the MultiProviders are assigned to
the Virtualization Layer and can be found below the InfoArea with the same name
(OpenText Vendor Invoice Management > Reporting Layer > Virtualization Layer).
The VIM 7.0 BW content provides the following MultiProviders based on InfoCubes:
Note: A finished invoice in this context is an invoice that has finished the VIM
process. Cancelled and obsolete invoices are excluded (they are not loaded into
the SAP NetWeaver BW system).
MultiProvider DP Documents: Volume and Amounts (technical name: /

OPT/MVDOC01)
This MultiProvider is based on InfoCube /OPT/CRDOC01 and provides answers
to questions as:
• How many finished invoices have been processed?

• What is the total amount of finished invoices?
MultiProvider DP Document: Times (technical name: /OPT/MVDOC02)

This MultiProvider is based on InfoCube /OPT/CRDOC02 and provides answers
to questions as:
• How many finished invoices have been processed with delay/on time?
• How many finished invoices have been approved with delay/on time?
MultiProvider Exception Classes: Occurences (technical name: /

OPT/MVEXC02)
This MultiProvider is based on InfoCube /OPT/CREXC01 and provides answers
to questions as:
• How many finished invoices ran into the different exception classes?
• What is the total amount of finished invoices in the different exception
classes?
• What is the percentage of finished invoices with a certain exception class to
all finished invoices?
VIM070500-03-RGD-EN-1
Chapter 16 MultiProviders
• What is the exception free rate, which is the rate of “no real exceptions”, to
all finished invoices?
MultiProvider Exceptions: Occurences (technical name: /OPT/MVEXC04)

This MultiProvider is based on InfoCube /OPT/CREXC02 and provides answers
to questions as:
• How are the exceptions of finished invoices distributed in an exception class?

• How many finished invoices ran into the different exceptions?
• What is the total amount of finished invoices in the different exceptions?
Additional MultiProviders based on DataStore Objects are provided to allow detail

views on data using the Report-to-Report Interface in BW Reporting:
Important
For performance reasons, the following MultiProviders are not meant to be
used for extensive reporting. These MultiProviders are based on DataStore
Objects and therefore should be used for a drill down with a very restrictive
set of characteristics only.
MultiProvider DP Document: Details (technical name: /OPT/MVDOC03)

You can use this MultiProvider to get a list of DP documents to a specific,
restrictive combination of characteristics.
Example: List of all DP documents with document type NPO_75 and channel ICC to
vendor 1000
MultiProvider Exception Classes: Details (technical name: /OPT/MVEXC01)

You can use this MultiProvider do get a list of DP documents to a specific
exception class and further restrictive characteristics.
vendor 1000 that had at least one exception to exception class Auth. mismatch.
MultiProvider Exceptions: Details (technical name: /OPT/MVEXC03)

You can use this MultiProvider to get a list of DP documents to a specific
exception and further restrictive characteristics.
vendor 1000 that had the exception Missing Item Quantity (PO).
VIM070500-03-RGD-EN-1
Part 5
Transactions and Roles
Part 5 Transactions and Roles
This part provides information about the transaction codes that various roles have
access to.
VIM070500-03-RGD-EN-1
Chapter 17
Transaction Profiles for Various Roles
The following table shows domains, transactions, and the roles that have access to
the transactions.
Note: For roles ICC User and BCC User, see section 5.1.2 “ERP Users” in the
ICC and BCC Administrator’s Guide. You might have to adjust the authorizations
for ICC users after you have installed the packages for Business Center
Inbound Configuration in addition to an existing VIM package. For more
information, see Section 8 “Incoming Document Processing” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Table headings
1 Indexer
2 AP Processor
3 AP Supervisor
4 Buyer
5 Receiver
6 Requester
7 Coder
8 Approver
9 WF Admin
Transaction Description 1 2 3 4 5 6 7 8 9
VIM
Notifications
VIM /OPT/REMINDER program X X
VIM Analytics
/OPT/ Current
VIM VAN_LIABILITY Liability Report X X
VIM /OPT/VIM_WP VIM Workplace X X X X X
SAP Business
SAP SBWP Workplace X X X X X
VIM /OPT/VIM_AGING Aging Report X X
Summary
VIM /OPT/VIM_SUMM Report X X
VIM070500-03-RGD-EN-1
Chapter 17 Transaction Profiles for Various Roles
Central Audit
VIM /OPT/VIM_AUDIT Report X X
Exception
VIM /OPT/VIM_EXCP1 Analysis Report X X
Key Process
Analytics
VIM /OPT/VIM_KPA1 Report X X
Productivity
VIM /OPT/VIM_PROD1 Report X X
Automation
VIM /OPT/VIM_ATM Report X
VIM /OPT/VIM_7AX8 Admin Tool X X X
Change
VIM /OPT/VIM_1AX1 document type X X X
Display
IDocument
VIM /OPT/VIM_1AX13 (indexed) X X X X X X X X
Change process
VIM /OPT/VIM_1AX2 type X X X
VIM /OPT/VIM_1AX3 Send for rescan X X X
Display BDC
VIM /OPT/VIM_1AX4 log X X X
Approval
baseline COA
VIM /OPT/AR_COA maintenance X X
Maintain
notification
VIM /OPT/VIM_8AX50 settings for me
VIM /OPT/VIM_VA2 VIM Analytics X X X X X X X X
VIM Analytics -
VIM /OPT/VIM_VA21 AP Basic X
VIM Analytics –
VIM /OPT/VIM_VA22 AP Advanced X
VIM Analytics -
VIM /OPT/VIM_VA23 Procurement X
VIM Analytics -
VIM /OPT/VIM_VA24 Monitor X
Display special
handling
VIM /ORS/DISP_SH instructions X X X X X
VIM070500-03-RGD-EN-1
Resubmit Non-
/ORS/ PO invoice for
VIM RESUB_NPO_INV approval X X X
Resubmit PO
invoice for
VIM /ORS/RESUB_PO_INV approval X X X
Submit Non-PO
/ORS/ invoice for
VIM SUBMIT_NPO_INV approval X X X
Submit PO
/ORS/ invoice for
VIM SUBMIT_PO_INV approval X X X
Cancel PO
/PTGWFI/ invoice, re-enter
VIM CANC_INV_05 PO X X
Cancel PO
VIM CANC_INV_06 Non-PO X X
Delete Non-PO
VIM DEL_INV_01 Non-PO X X
Delete Non-PO
VIM DEL_INV_02 PO X X
Delete PO
VIM DEL_INV_03 PO X X
Delete PO
VIM DEL_INV_04 Non-PO X X
/PTGWFI/ Change vendor
VIM F_CHG_VEN (centrally) X X
/PTGWFI/ Delete park
VIM F_PINV_DEL invoice X X
Year end
program - Non-
VIM /PTGWFI/IE_YEND5 Po invoices X X
Year end
cleanup
program - Non-
VIM /PTGWFI/IE_YEND6 Po invoices X X
/PTGWFI/ Change parking
VIM LIV_CHG_PKRS reason X X X
VIM070500-03-RGD-EN-1
/PTGWFI/
VIM M_CHG_CONTR Change contract X
Change logistic
VIM /PTGWFI/M_CHGLIV invoice X X
Goods receipt
for purchase
VIM /PTGWFI/M_CR_GR order X
Display
VIM /PTGWFI/M_DIS_REQ requisition X X X
Purchasing
documents for
VIM /PTGWFI/M_LIST_PO material X X X X
Release LIV
VIM /PTGWFI/M_LIX_REL blocked invoice X X
/PTGWFI/ Short pay LIX
VIM M_LIX_SHORTP invoice X X
Reverse goods
VIM /PTGWFI/M_REV_GR receipt for PO X
/PTGWFI/ Short pay:
VIM M_SPAY_2_CM credit memo X X
Short pay:
/PTGWFI/ subsequent
VIM M_SPAY_4_SC credit X X
Short pay:
/PTGWFI/ delete invoice/
VIM M_SPAY_INV create invoice X X
/PTGWFI/ Change parking
VIM PIR_CHG_PKRS reason X X X
All VIM
VIM /OPT* transactions X
All VIM
VIM /ORS* transactions X
All VIM
VIM /PTGWFI* transactions X
Workflow
SAP SW* transactions X
Development
SAP SE* transactions X
System
SAP SM13, SM50, SM12 monitoring X
SAP ST22, ST05, Dump analysis X
VIM070500-03-RGD-EN-1
SAP SQ* SAP query X
SAP SCATT Test procedures X
SAP SHDB, SM35, SM35P BDC analysis X
OAWS, OAWD,
OAC2, OAC3, OAC0, SAP
OAA3, SOA0, OAM1, ArchiveLink
SAP OANR transactions X
Post NPO
SAP FB60 invoice X X
Display NPO
SAP FB03 invoice X X X X X X X X X
SAP MIRO Post PO invoice X X
Display PO
SAP MIR4 invoice X X X X X X X X X
SAP ME23N Create new PO X
SAP ME22N Change PO X
Change vendor
SAP XK02 master X
Create new
SAP XK01 vendor X
Create new
SAP ME51N requisition X
Change
SAP ME52N requisition X
List PO by
SAP ME2L vendor X X X X
SAP MIGO Post/reverse GR X
Unblock PO
SAP MRBR invoice X X X
Cancel PO
SAP MR8M invoice X X X
SAP ME31K Create contract X
SAP ME32k Change contract X
Update info
SAP ME12 record X
List PO by
SAP ME2M material X
Display change
SAP RSSCD100 documents X
VIM070500-03-RGD-EN-1
Authorization Objects
Class Authorization Description 1 2 3 4 5 6 7 8 9

Display
change
documents
(in
S_SCD0: TCODE=*, Automation
BC_Z ACTVT=08 Report) X
Create new
bank entry in
F_BNKA_MAN: OTV dialog
AAAB ACTVT=01 (optional) X X
VIM070500-03-RGD-EN-1
Part 6
Business Rules
Part 6 Business Rules
This part provides an overview of all business rules applied in VIM. This part also
provides some technical insight to ease the using of the business rules. If needed the
related configuration aspect is mentioned.
VIM070500-03-RGD-EN-1
Chapter 18
General Information About Business Rules
At the beginning of each business rule, a check is performed whether the business
rule is relevant for this specific document based on the customizing stored in table /
OPT/VIM_T005A (Characteristic Specific Process Types Configuration). The following
check is done:
• Invoice Characteristics
• Invoice type: A for All, N for NPO and P for PO. For example: If the coming
invoice is of type NPO but the rule is applicable for PO, the rule is not executed.
• Simplified Invoice (ignored or not): If this indicator is set, a FM is called to check
whether the invoice is a simplified one.
The check is executed based on the customizing in table /OPT/VIM_T005
(Characteristic Specific Process Types Configuration). If the fixed amount limit is
maintained, the amount of the invoice will be compared with this limit.
Otherwise if the Simplified Invoice Check FM is maintained, the FM is called.
When the invoice is determined as simplified, the rule is not applied for
simplified invoices.
• Invoice category: The invoice category maintained for the business rule (all
categories, intra-community, domestic, import, ...) is compared with the invoice
category of the indexing data. If it does not match, the rule is not executed.
Configuration Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > Document Type Configuration >
Characteristic Specific Document Type Configuration.
Double click the document type. The Characteristic Specific Attributes view opens.
In Dialog Structure, double-click Characteristic Specific Process Types.
VIM070500-03-RGD-EN-1
Chapter 19
Business Rules for PO Invoices
This chapter describes the various business rules for PO invoices. The business rules
are delivered out of the box with the product including the high level business logic
of each of these rules.
19.1 Invalid PO Number (PO)

When this business rule is applied, the purchase order number mentioned on the
invoice should be available in SAP ERP. There can be two scenarios as described in
the following:
Matching
The PO number mentioned on the supplier’s invoice matches with the PO
number in SAP ERP, and the PO number is not marked as Deleted. In this case,
no action is taken and the document proceeds to the next logical step.
Mismatch
The PO number mentioned on the supplier’s invoice does not match with the
PO number in SAP ERP, or the PO number is marked as deleted in the LOEKZ
flag. The exception Invalid PO Number (PO) is raised, and the invoice is
automatically routed to the preconfigured agent depending on the role for
further action.
Technical FM /OPT/VIM_DETERMINE_PROC_101
information
All PO numbers if given in one of the following locations are checked against table
EKKO.
• in field PO number on header level

• in field PO list (if available), which are separated by comma, on header level
• in column PO number in the line items
If only one of them is not found in table EKKO, or found with deletion flag set, the
exception Invalid PO Number (PO) is raised.
The business rule writes detailed information about the invalid PO numbers into the
message table.
VIM070500-03-RGD-EN-1
Chapter 19 Business Rules for PO Invoices
19.2 Invalid Vendor (PO)

The supplier mentioned on the invoice should be available in the SAP ERP system.
There can be two scenarios as described in the following:
Exists
The invoice supplier exists in the SAP ERP system as a vendor. In this case, no
action is taken and the document proceeds to the next logical step.
Does not exist

The invoice supplier does not exist in the SAP ERP system as a vendor. The
exception Invalid Vendor (PO) is raised. The invoice is automatically routed to
the pre-configured agent depending on the role for further action.
information
Index data from table /OPT/VIM_1HEAD is used to check the vendor. If the company
code is given in the index data, the given vendor is checked in table lfb1, otherwise
in table lfa1.
The Block Key for payment is also read from SAP table lfb1 (in case the company
code is given). If it is maintained for the vendor, the function checks the constant
GET_VEND_PAYM_BLOCK with product code 005. This constant shall contain all
allowed Block Key Payment, separated by comma, for example A,B,P.
If this constant does not exist or is not maintained -> Exception.
If this constant is maintained, but not including the Block Key Payment maintained
in the master data of the vendor -> Exception.
If the company code is not given, the Block Key for Payment is not checked.
19.3 Invalid UOM (PO)

The unit of measure (UOM) provided on the invoice should exist in the SAP ERP
system. There can be two scenarios as described in the following:
Exists
The UOM on the supplier invoice exists in SAP ERP. In this case, no action is
taken and the document proceeds to the next logical step.
Does not exist

The UOM on the supplier invoice does not exist in SAP ERP. The exception
Invalid UOM (PO) is raised and the work item is automatically routed to the
pre-configured agent depending on the role for further action.
information
The UOM is compared with the values in table field T006-MSEHI.
VIM070500-03-RGD-EN-1
19.4. Invalid Currency (PO)
19.4 Invalid Currency (PO)

The currency provided on the invoice should exist in the SAP ERP system. There can
be two scenarios as described in the following:
Exists
The currency on the supplier invoice exists in SAP ERP. In this case, no action is
Does not exist
The currency on the supplier invoice does not exist in SAP ERP. The exception
Invalid Currency (PO) is raised, and the work item is automatically routed to
Technical The value from table /OPT/_VIM_1HEAD corresponding to the field entered in the
information customizing table of this rule is checked against the table TCURC.
19.5 Suspected Duplicate (PO)

This specific business rule checks for a duplicate invoice based on specific fields
configured in the configuration. There can be two scenarios as described in the
following:
Not a duplicate
If the invoice is not a duplicate, no action is taken and the document proceeds to
the next logical step.
Duplicate
If the invoice is a duplicate, the exception Suspected Duplicate (PO) is raised
and the work item is automatically routed to the pre-configured agent
depending on the role for further action.
Technical FM /OPT/VIM_DETERMINE_PROC_DUP
information
Based on the Duplicate Check Group ID maintained for the Document Type, a
different algorithm is applied to check the duplicate.
The duplicate check can be running on the local system or on the central system
depending on the system landscape (table /OPT/VIM_SYS_LD).
In baseline configuration, there are 2 Duplicate Groups, ID1 for NPO and ID 02 for
PO. FMs (if required) are different for 2 groups.
The Duplicate Group is configured in table /OPT/VIM_T112 with Duplicate Check

Type, Duplicate Check FM for the single and external FM for the multiple backend
landscape. The central system is also maintained here if the multiple backend
landscape is configured.
Duplicate Check Type can be either Function Module (A) or Index Data Fields (B).
In case of A, the function module maintained for this Duplicate Group is called.
VIM070500-03-RGD-EN-1
In case of B, the fields maintained in table /OPT/VIM_T113 for the Duplicate Group
ID are used to compare the index data of the current document with all existing
documents in table /OPT/VIM_1HEAD. Only documents with relevant status (table /
OPT/VIM_T101) are considered in the checking process. Documents with status 06
(Rescan complete), 10 (Obsolete), and 72 - 90 (OCR specific) are not considered.
point Document Processing Configuration > General Configuration > Maintain
Duplicate Check Procedures
19.6 PO Not Released or Incomplete

This specific business rule checks whether a PO is released or incomplete. There can
Released or complete
If the PO is released or complete, no action is taken and the invoice document
proceeds to the next logical step.
Not released or incomplete
If the PO is not released or incomplete, the exception PO Not Released or
Incomplete is raised, and the work item is automatically routed to the pre-
configured agent depending on the role for further action.
information
The following check is carried out for all POs given in the indexing data, either in
field PO number or in field PO list or in the line items:
• Release group of a PO (field FRGGR) if filled will be read from table EKKO for the
given PO. If the release group is not released (indicator KZFRE in table T16FB) ->
Exception.
• If there is no Release group available, and the field Memory (the indicator that PO
is not yet complete) is set -> Exception.
19.7 Unable to Match PO Lines (PO)

This business rule matches the number of lines mentioned on the invoice against the
SAP PO lines. There can be two scenarios as described in the following:
Matches
The number of PO lines on the invoice matches with the number of SAP PO
lines. In this case, no action is taken and the document proceeds to the next
logical step.
Mismatches
The number of PO lines on the invoice exceeds the number of SAP PO lines. The
exception Unable to Match PO Lines (PO) is raised, and the work item is
automatically routed to the pre-configured agent depending on the role for
further action.
VIM070500-03-RGD-EN-1
19.8. Manual Check Needed / Missing Data for Indexing Lines (PO)
information
For every PO given in the line items, the number of line item with the same PO
number is counted. If for a certain PO there are more lines in the document than in
the PO, the exception is raised.
If the PO item is a service PO item, the number of service entries in table ESLL is
considered as a reference.
Note: This business rule can be replaced by business rule Manual Check Needed
for Indexing Lines (PO).
19.8 Manual Check Needed / Missing Data for

Indexing Lines (PO)
Since VIM 7.5, this business rule replaces “Manual Check Needed for Indexing Lines
(PO)” on page 188.
When this business rule is applied, the PO invoice is checked if all data - header and
item lines - is fully provided.
In contrast to the pre-7.5 business rule, this new version additionally checks if the
invoiced quantity on each line does not exceed the GR quantity (that has not been
invoiced yet). This can be switched off if needed, to achieve that the 7.5 business rule
performs only completeness checks. The corresponding configuration is described in
this section.
If line item data is complete, that means all mandatory fields are fully supplied, the
business rule is completed without any exception and the document proceeds to the
next logical step.
A line is considered incomplete if one or more mandatory fields are not fully
supplied.
information
In this FM, all mandatory fields of item indexing data delivered by OCR are
checked.
Mandatory fields of a Non GR-IV based PO invoice:

• PO number
• PO item
• Quantity
• Amount
• UOM
Mandatory fields of a GR-IV based PO invoice:
VIM070500-03-RGD-EN-1
• PO number
• PO item
• Delivery Note/GR Reference Document
• Quantity
• Amount
• UOM
The exception is raised if at least one line is incomplete or missing (empty). The
missing fields are then determined by the settings of the document type
configuration, PO line determination maintenance.
As mentioned above, this business rule additionally checks whether the invoice
quantity on each line item does not exceed the corresponding GR quantity that is not
invoiced yet. For service POs, SES is checked similarly. This check is made by
default in VIM 7.5, but can be switched off if needed, to make this business rule
behave similarly to the 7.0 business rule and make only completeness checks. To
switch the additional checks off, create a new entry in the table /PTGWFI/Z_CONST,
using the SM30 transaction:
• Product code: 005
• Version: empty
• Constant name: DISABLE_GR_CHECK
• Constant description: Set to X to disable additional GR checks in PO line
determination (BR 113)
• Constant value: X
19.9 Unable to Determine PO Line Number (PO)

This exception is raised when a corresponding PO line number can not be
automatically determined based on the information mentioned on the supplier’s
invoice. There can be two scenarios as described in the following:
Determined
The corresponding PO line number is determined based on the supplier’s
invoice information. In this case, no action is taken and the document proceeds
to the next logical step.
Unable to Determine
The corresponding PO line number is not determined based on the supplier’s
invoice information. The exception Unable to Determine PO Line Number (PO)
is raised, and the work item is automatically routed to the pre-configured agent
Technical FM /OPT/VIM_DETERMINE_PROC_POL
information
Item data of the PO is read from table /OPT/VIM_1ITEM.
VIM070500-03-RGD-EN-1
19.9. Unable to Determine PO Line Number (PO)
The item number is determined based on the PO Line Determination logic group ID
(POL_GROUPID). This POL Group ID is maintained for each document type in the
Document Type configuration.
The POL Group ID configuration is stored in table /OPT/VIM_TPOL.
If check FM is maintained for the POL Group ID, this FM is called. Otherwise the
Baseline FM /OPT/VIM_DETERMINE_PO_LINES is called. In this FM, fields maintained
for the POL Group ID (which are store in table /OPT/VIM_TPOL3) will be subjects to
be checked. That means the values of such fields in the invoice are used to find the
best match.
The logic of /OPT/VIM_DETERMINE_PO_LINES is the following:

• If the POL Group ID is not maintained in /OPT/VIM_TPOL3, nothing will be done.
• If the PO number is not given in the item line, this value will be read from the
header data of the invoice.
• All item lines from table EKPO are considered for the matching.
The number of fields that shall be matched is also configurable.
If field ALL_MATCH is set, all fields must be matched. Otherwise the number of
matched fields is given in field NOF_FIELDSMATCH.
If field INVOICED_LINES is checked, only item lines marked as Final Invoice (field
EREKZ is marked – meaning that the item is already invoiced and no further invoice
is expected) will be considered.
After the matching, each pair PO number and determined Item Number are checked
against table EKPO. If there is no match -> Exception.
Configuration Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > General Configuration > Automated Line
Processing > PO Line Determination > Maintain PO Line Determination
Procedures.
Notes
• The field entered in the POL configuration shall be a valid field. A field that
exists in /OPT/VIM_1ITEM can be entered in the configuration, but it will be
ignored in the POL logic if it does not exist in SAP table EKPO. Except the
following fields which are internally re-mapped from VIM fields to SAP
fields:
• BSTME -> MEINS
• WRBTR -> BRTWR
• TAX_AMOUNT -> NAVNW
• TAX_CODE1 -> MWSKZ
• LFSNR -> XBLNR
VIM070500-03-RGD-EN-1
• There is a special option for single line POs in single line invoices. The line
item matching is skipped and the line number in the DP document is set to
the number of the single PO line item unless Z constant 005
SINGLE_LINE_PO_MATCH is set to X.
19.10 Manual Check Needed for Indexing Lines (PO)

Since VIM 7.5, this business rule is replaced by “Manual Check Needed / Missing
Data for Indexing Lines (PO)” on page 185.
When this business rule is applied, the PO invoice is checked if all data – header and
item lines – is fully provided. The difference between this business rule and the
business rule Unable to Determine PO Line Number is listed in the following:
• This business rule not only checks the PO line number, it checks also other
mandatory fields of the PO.
• Not only the PO line number, but also other mandatory fields, which are not
supplied in the document, will be derived in background.
Complete
If line items data is complete, that means all mandatory fields are fully supplied,
the business rule is completed without any exception and the document
Incomplete or not supplied

If line items are incomplete or not supplied, their mandatory fields will be
derived in background based on the PO number or Delivery numbers provided
in the header. The exception Manuel Check Needed for Indexing Lines (PO) is
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action. A line is considered incomplete if one
or more mandatory fields are not fully supplied.
Technical FM /OPT/VIM_LINES_DERIVE_PO
information
In this FM, all mandatory fields of item indexing data coming from OCR are
checked. Mandatory fields of a Non GR-IV based PO invoice:
• PO number
• PO item
• Quantity
• Amount
• UOM
Mandatory fields of a GR-IV based PO invoice:

• PO number
VIM070500-03-RGD-EN-1
19.11. Invalid PO Item Number (PO)
• PO item
• Delivery Note/GR Reference Document
• Quantity
• Amount
• UOM
The completeness of mandatory fields are checked against data of the PO/DN in
tables EKBE and EKPO.
The exception is raised if at least one line is incomplete or missing (empty). The
missing fields are then determined by the settings of the document type
configuration, PO line determination maintenance.
19.11 Invalid PO Item Number (PO)

When this business rule is applied, the purchase order item number mentioned on
the invoice should be available in SAP ERP. There can be two scenarios as described
in the following:
Matching
The PO item number mentioned on the supplier’s invoice exists within the PO in
SAP ERP, and the PO item number is not marked as Deleted. In this case, no
Mismatch
The PO item number mentioned on the supplier’s invoice does not exist within
the PO in SAP ERP, or the PO item is marked as deleted with the LOEKZ flag.
The exception Invalid PO Item Number (PO) is raised, and the invoice is
automatically routed to the preconfigured agent depending on the role for
further action.
Technical FM /OPT/VIM_DETERMINE_PROC_ITEMS
information
All item lines with PO number and PO item number are checked in table EKPO.
If at least one of them is not found in table EKPO, or found with deletion flag set, the
exception Invalid PO Item Number (PO) is raised.
The business rule writes detailed information about the invalid PO item numbers
into the message table.
VIM070500-03-RGD-EN-1
19.12 Invalid Vendor VAT Number (PO)

When this business rule is applied, the supplier VAT/Tax number provided on the
invoice must match with the vendor master VAT/Tax number provided in SAP ERP.
The following scenarios are possible:
Match
The supplier VAT/Tax number provided on the invoice matches with the VAT/
Tax number mentioned in the vendor master. In this case, no action is taken and
the document proceeds to the next logical step.
Mismatch
The supplier VAT/Tax number provided on the invoice does not match with the
VAT/Tax number mentioned in the vendor master in SAP ERP. The exception
Invalid Vendor VAT Number (PO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.
information
The Vendor VAT/Tax number is read from the Vendor Master Data (table LFA1) and
compared with the VAT/Tax number given in the invoice. If no match, the Vendor
VAT/Tax number is read from the Vendor Master Data extension table LFAS. If no
match -> Exception
The following fields in the Vendor master data (table LFA1) for VAT ID are
considered in this business rule:
STCEG
VAT Registration Number
STCD1
Tax Number 1
STCD2
Tax Number 2
STCD3
Tax Number 3
STCD4
Tax Number 4
In the indexing screen, the field vendor_vat_no is strictly mapped to field STCEG.
The field vendor_tax_no is mapped to STCD1, STCD2, STCD3, or STCD4. Therefore, if
the vendor applies only STCDx (where x is 1, 2, 3, or 4) in the master data, the field
vendor_tax_no must be used instead of vendor_vat_no in the indexing screen.
The check logic is the following:
If the value in field vendor_vat_no does not match the value in STCEG in vendor
master data, it will be checked against the foreign VAT ID of the vendor, which is
VIM070500-03-RGD-EN-1
19.13. Incomplete Credit Memo (PO)
maintained in table LFAS. If the field vendor_vat_no is filled and checked

successfully, no further checking will be executed.
Otherwise, the field vendor_tax_no will be checked according to the following

logic:
If the field vendor_tax_no is not filled in the indexing screen, but one of the fields
STCDx (where x is 1, 2, 3, or 4) in vendor master data is filled with a value, the
exception is raised. If the field vendor_tax_no is filled in the indexing screen, its
value must match the value of one of the fields STCDx (where x is 1, 2, 3, or 4).
19.13 Incomplete Credit Memo (PO)

The supplier’s credit memo should have the following information:
• The supplier’s original invoice number (reference number)
• The invoice date of the supplier’s original invoice
When this business rule is applied, the credit memo should have the original
suppliers invoice number and the original invoice date. Also, the original invoice
number mentioned on the credit memo must be present in the SAP ERP system. The
following scenarios are possible:
Present and matching

The credit memo has the original invoice number and the original invoice date.
Further, there should be an invoice in the SAP ERP system (DP document or
SAP document) that has the original supplier’s invoice number as the reference
number. In this case, the exception is not raised and the document proceeds to
Not present
The credit memo does not have the original invoice number and the original
invoice date. The exception Incomplete Credit Memo (PO) is raised and the
invoice is automatically routed to the pre-configured agent depending on the
role for further action.
Mismatch
The credit memo has the original invoice number and there is no invoice in the
SAP ERP system (DP document or SAP document) that has the original
supplier’s invoice number as the reference number. The exception Incomplete
Credit Memo (PO) is raised and the invoice is automatically routed to the pre-
Technical FM: /OPT/VIM_DETERMINE_PROC_121

information
First the customizing related to the Credit Memo (CM) for the specific country is
read from table /opt/vim_t005. At least one of the two checkboxes CM Ref No Req
and CM Ref Date Req must be checked. Otherwise the check is not executed.
If CM Ref No is required for CM but the field CM REF NUMBER in the indexing is
left blank -> Exception
VIM070500-03-RGD-EN-1
If Ref Date is required for CM but the field CM REF DATE in the indexing is left
blank -> Exception
If CM Ref Data Validate is not checked -> No further check is executed.
If CM Ref Data Validate is required, the rule will search for a document with the
Posting date = CM Ref date (if CM_Ref_Date is required) and the Reference number
= CM Ref No (if CM_Ref_No is required). The searching will be carried out in the
following logic:
• First the DP documents are searched (table /OPT/VIM_1HEAD).
• If not found, the SAP parked document (table vbkpf) is searched.
• If not found, the posted documents (table rbkp for PO) are searched.
• If no matched document found at all, the exception Incomplete Credit Memo
(PO) is raised.
Customizing Run the /OPT/SPRO transaction and navigate to Document Processing

Configuration > Document Type Configuration > Characteristic Specific
Document Type Configuration.
Double-click the characteristic (country).
On the Characteristic Specific Attributes screen, there are 3 check boxes:
CM Ref No Req.
CM reference number is required.
CM Ref Date Req.
CM Reference Date is required.
CM Ref Data Validate
The correctness of the CM Ref No and Ref Date is validated against data in the
DP documents (VIM tables) or in the SAP documents (SAP tables).
This customizing is stored in table /opt/vim_t005 for the specific country.
19.14 Vendor Address Mismatch (PO)

The Remit-To-Address (supplier’s address to which the billing should happen)
should match with the SAP Vendor Master’s address as this is a required
information on the suppliers invoice. There can be two scenarios as described in the
following:
Match
The Remit-To-Address provided on the Invoice matches with the address on the
vendor master. In this case, no action is taken and the document proceeds to the
next logical step.
Mismatch
The Remit-To-Address does not match with the address on the vendor master.
The exception Vendor Address Mismatch (PO) is raised and the invoice is
VIM070500-03-RGD-EN-1
19.15. Missing Item Quantity (PO)

further action.
The following SAP vendor address fields are matched:
• House #
• Street
• Postal Code
• City
• Region
• Country
information
19.15 Missing Item Quantity (PO)

The supplier invoice should have the quantity of the goods being supplied or the
extent of the services being provided.
When this business rule is applied, the quantity on the DP index document line item
should have been filled. There can be two scenarios, as described in the following:
Entered
No action is taken and the document proceeds to the next logical step.
Not entered
The exception Missing Item Quantity (PO) is raised and the invoice is
further action.
information
Field quantity of each line item in the indexing data is checked. If not filled ->
Exception
19.16 Missing Item Unit Price (PO)

When this business rule is applied, the Unit price on all items on the DP index items
should have been filled. Otherwise the exception is raised.
Normally, if the business rule Manual Check Needed for Indexing Lines (PO) is
applied in some step before, the information like Unit Price is already derived from
PO and no exception is raised.
VIM070500-03-RGD-EN-1
19.17 Missing Invoice Date (PO)

When this business rule is applied, the invoice date on the DP index document
header should have been filled. There can be two scenarios, as described in the
following:
Entered
Not entered
The exception Missing Invoice Date (PO) is raised and the invoice is
further action.
Technical If field BLDAT of the indexing data is not filled -> Exception
information
19.18 Invalid Tax Info (PO)

The supplier’s invoice should carry the total VAT amount and (or) the VAT %
indicating the VAT payable.
When this business rule is applied, the tax information provided on the vendor
invoice is analyzed and mapped to standard SAP tax values (tax codes) and passed
onto the DP document. Depending on the VIM specific tax configuration settings
(with auto calculate tax or without auto calculate tax), the tax information is
validated and, in case of any deviations, the exception Invalid Tax Info (PO) is
raised and the invoice is routed to the pre-configured agent depending on the role
for further action. There are many scenarios that can arise depending on the
configuration. In the following, some of the possible scenarios are described:
Tax information present and matching

The tax information entered on the DP document has a corresponding valid SAP
tax information. The document proceeds to the next logical step.
Example: The VAT % mentioned on the invoice has a corresponding VAT tax code.
Tax information present and not matching

The tax information entered on the DP document does not have a corresponding
valid SAP tax information. The exception Invalid Tax Info (PO) is raised and
the document is automatically routed to the pre-configured agent depending on
the role for further action.
Example: The VAT % mentioned on the invoice does not have a corresponding VAT tax
code in SAP ERP.
Tax information not present

The tax information is not present on the invoice. The exception Invalid Tax
Info (PO) is raised and the document is automatically routed to the pre-
Example: The payable VAT % or VAT amount is not present on the vendor’s invoice.
VIM070500-03-RGD-EN-1
19.18. Invalid Tax Info (PO)
Technical FM /OPT/VIM_DETERMINE_PROC_126 (for countries like DE, US, …)

information
The following logic applies:
• Firstly, the country key (for example US, DE, JP) is determined. If PO numbers
are given in the header data, the country key is derived from the PO. If there is
no PO number in the header, the country key is derived from the very first PO in
the lines. If there are no PO numbers available in the header and in the lines, the
country will be determined based on the company code.
• FM /OPT/VIM_TAX_CODE_DETERMINE is called. This FM will determine the tax
code based on the tax rate if there is any. The logic used for the tax code
determination can be configured in /OPT/SPRO. The tax jurisdiction code is also
determined here if required.
• Specific for Canada:
• The tax code determination function module is /
OPT/VIM_CA_TAX_CODE_DETERMINE.
• FM /OPT/VIM_SHIP_TO_REG_DETERMINE is called to determine the ship to
adress.
• For Canada or for companies where the country is maintained in table /
OPT/VIM_CTRY, tax_rate is calculated as sum of all tax_rate 1 to 4,
zero_tax_rate = sum of all zero_tax_rate from 1 to 4. The same is executed to
the tax_rate and zero_tax_rate on all item lines.
After the step of tax code determination is executed, the tax rate and tax code are
checked as described in the following (for all countries).
• For PO invoice at both levels, header and line item:
• If tax rate is given and not 0.00, tax code is blank -> Exception. That means the
tax rate is not valid and no corresponding tax code can be determined.
• The combination tax rate = 0.00, tax code is blank is only allowed if the option
Allow zero tax is not checked. That means if the option Allow zero tax is
checked, there must be a valid tax code for the tax rate 0.00.
• The tax code, if given or determined by the logic mentioned above, either in the
header or in the line items, will be checked by the following logic.
• Look in table t005 for the procedure for calculating tax maintained for the
country key, for example TAXD. If the tax code is given in the invoice and the
Procedure key is found (not initial), they will be checked against table T007A.
If tax code is not given -> exception
• Tax amount if given in the invoice is checked in the following steps. If not, the
value in the total tax amount is used. The logic:
If auto_calc (Auto calculate Tax) is not checked:
• If tax_amount # 0 but tax_code in header or in all line items is not given ->
Exception
VIM070500-03-RGD-EN-1
• If tax_amount = 0, the check is successful only if the tax_rate = 0 and

allow_free_tax = X, OR both tax_rate and tax_code are initial, in header as
well as in the line items.
If auto_calc is checked:
• If tax_code in header and in all line items is initial -> Exception.
• If tax_code is given in header or in line items, it is checked in table t007a.
Customization You can customize the logic for tax code determination in /OPT/SPRO > Document
point Processing Configuration > Document Type Configuration > Maintain Document
Types. Double-click the DP Document Type.
You can also customize the options like Auto Calculate Tax, Allow Zero Tax, Allow
without Tax here.
Auto Calculate Tax

The system will calculate the tax based on the tax code supplied by the indexing
or determined by the logic mentioned above.
Allow Zero Tax

The system will determine the tax code for the tax rate 0.00. If blank or empty,
the system cannot determine the tax code.
Allow without Tax

If tax information is not given in the invoice, the exception is not raised. The
business rule is successful.
Calculate Tax on Net

If this option is selected, the tax is calculated like it is done in the SAP
transaction FV60 when the Editing Option Calculate tax on net amount is
selected.
For all Canada-specific customizing, run the /n/OPT/SPRO transaction and navigate
to Vendor Invoice Management > Document Processing Configuration >
Document Type Configuration > Specific Country Settings > Canada.
19.19 Missing Date of Supply (PO)

The invoices should have the date of supply mentioned on the invoice provided by
the suppliers. There can be two scenarios as described in the following:
Date of supply present

The date of supply on the vendor’s invoice is present. In this case, no action is
Date of supply not present

The date of supply on the vendor’s invoice is not present. In this case, the
exception Missing Date of Supply (PO) is raised, and the invoice is
further action.
VIM070500-03-RGD-EN-1
19.20. ISR Number Mismatch (PO)
Technical Field SUPPLY_DATE must be filled. If not, the exception is raised.

information
19.20 ISR Number Mismatch (PO)

This business rule is specific for Switzerland. The supplier’s invoice should have the
ISR number on the invoice as this is a required information.
When this business rule is applied, the ISR number on the DP index document
header should be present and matching with the vendor master. There are the
following scenarios:
ISR number present and matching

ISR number present and not matching

The exception ISR Number Mismatch (PO) is raised, and the invoice is
further action.
ISR number not present

If the ISR number is not mentioned on the invoice but the vendor master has it,
the exception ISR Number Mismatch (PO) is raised, and the invoice is
further action.
information
• If the Z constant ESR_CHECK_REQUIRED for product 005 is set to X, both ISR
numbers in the header data and in the vendor master must be given. Otherwise,
the exception is raised.
• If both ISR numbers on invoice and in the vendor master data are given, they are
checked irrespectively whether the Z constant is set or not. The check logic is the
following:
• The ISR number in the header data must contain the ISR number given in the
vendor master data (table lfa1). Otherwise, the exception will be thrown.
• The ISR number in the vendor master data is allowed to contain the dash
symbol, for example 01-162-8 where 01 represents the ESR code, 162 the
participant number, and 8 the check digit.
• If the Z constant ESR_CHECK_REQUIRED for product 005 is not set, the check will
be successful even if the ISR number in the invoice or the ISR number in the
vendor master data or both are not available.
VIM070500-03-RGD-EN-1
19.21 Invalid Recipient VAT Number (PO)

Every country has its typical VAT structure. This information can be found in the
Company Master Data. For some countries, the recipient’s VAT number is a
mandatory information for some kind of invoices (for example for intra-community
invoices or triangulation invoices).
When this business rule is applied, the recipient VAT number provided on the
invoice must match with the company’s VAT Number provided in the company
code in SAP ERP. The following scenarios are possible:
Match
The recipient’s VAT number provided on the invoice matches with the VAT
number mentioned in the company code information. In this case, no action is
taken, and the document proceeds to the next logical step.
Mismatch
The recipient’s VAT number provided on the invoice does not match with the
VAT number mentioned in the company code in SAP ERP. The exception
Invalid Recipient VAT Number (PO) is raised, and the invoice is automatically
Not present
If the recipient’s VAT number is not present on the invoice, the exception
Invalid Recipient VAT Number (PO) is raised, and the invoice is automatically
information
For all countries except Austria, the check is carried out in the following logic:
• If the field Recipient VAT number is blank -> Exception
• If the field Recipient VAT number is filled with a value, this value is compared
with the value in field STSEG (VAT Registration Number) in table T001 for the
Company Code on the invoice. If the VAT Registration Number is not blank and
does not match the Recipient VAT Number given in the invoice -> Exception
Note: The Company Code is either given in the invoice header or can be
derived from PO information (for PO invoice).
For Austria the check will be carried out only when the gross amount exceeds some
specific amount (for example 10,000 in the local currency).
VIM070500-03-RGD-EN-1
19.22. Payment Terms Mismatch (PO)
19.22 Payment Terms Mismatch (PO)

The payment terms mentioned on the suppliers invoice should match with the
payment terms configured in the SAP ERP system. There can be two scenarios as
described in the following:
Match
The payment terms provided on the vendor’s invoice matches with the payment
terms mentioned in the purchase order or vendor master in SAP ERP. In this
case, no action is taken and the document proceeds to the next logical step.
Mismatch
The payment terms provided on the vendor’s invoice does not match with the
payment terms maintained in the purchase order or vendor master in SAP ERP.
The exception Payment Terms Mismatch (PO) is raised and the invoice is
further action.
information
If payment terms are not given in the invoice, no check will be executed.
If payment terms are given in the invoice, they must match with the payment terms
determined for the invoice.
The payment terms of a PO invoice are determined from the PO data (table EKKO) if
given, or from the purchasing data of the vendor (table LFM1). If not found, it is
determined from the vendor company code data.
If the payment terms do not match, the exception is raised.
19.23 Invalid Siret Number (PO) (French)

The SIRET number provided on the invoice is matched against the SIRET number
maintained in the vendor master. There can be two scenarios as described in the
following:
Match
The SIRET number provided on the invoice matches with the SIRET number in
the vendor master. In this case, no action is taken and the document proceeds to
Mismatch
The SIRET number provided in the invoice does not match with the SIRET
number in the vendor master. The exception Invalid SIRET Number (PO) is
information
VIM070500-03-RGD-EN-1
The SIRET number (field siret_no) given in the invoice is compared with the tax
number stored in the master data of the vendor.
• If the tax number is maintained for the vendor and it does not match the number
given in the invoice, the exception is raised.
• If the tax number is not maintained for the vendor, no exception is raised.
Customizing There are 4 tax numbers available in the master data of the vendor (table lfa1). In
order to determine which number is applied for the SIRET, the Z constant
VENDOR_SIRET_NO_FLD for product code 005 (table /PTGWFI/Z_CONST) must be
maintained with a correct value. Possible values are STCD1, STCD3, and STCD4.
19.24 Invalid Company Address (PO)

The recipient address provided on the invoice should match with the SAP ERP
company code’s address. There can be two scenarios as described in the following:
Match
The recipient address provided on the invoice matches with the company code
address. In this case, no action is taken and the document proceeds to the next
logical step.
Mismatch
The recipient address does not match with the address of the company code.
The exception Invalid Company Address (PO) is raised, and the invoice is
further action.
information
The company code address is read from table T001 (Company Code Master Data)
and is compared with the address given in the section Ship-To-Address in the
indexing. If the address of the company code is not maintained (blank) or does not
match with the Ship-To-Address in the invoice -> Exception
Customization The address of the company code can be maintained and displayed in the SAP
Reference IMG (transaction SPRO): Financial Accounting > Company Code > Enter
Global Parameters. Click the Address button to maintain or display the company
code address.
VIM070500-03-RGD-EN-1
19.25. Vendor Invoice Reference Missing (PO)
19.25 Vendor Invoice Reference Missing (PO)

The supplier invoice should have the invoice number mentioned on the invoice.
Invoice number present

The invoice number on the vendor’s invoice is present. In this case, no action is
Invoice number not present

The invoice number on the vendor’s invoice is not present. In this case, the
exception Vendor Invoice Reference Missing (PO) is raised, and the invoice
is automatically routed to the pre-configured agent depending on the role for
further action.
Technical If field XBLNR of the indexing data is not filled with the reference number ->
information Exception
19.26 Payment Method Mismatch (PO)

The payment method mentioned on the supplier’s invoice should match with the
payment method configured in the SAP ERP system. There can be two scenarios as
Match
The payment method provided on the vendor’s invoice matches with the
payment method mentioned in the vendor master in SAP ERP. In this case, no
Mismatch
The payment method provided on the vendor’s invoice does not match with the
payment method maintained in the vendor master in SAP ERP. The exception
Payment Method Mismatch (PO) is raised, and the invoice is automatically
information
If the payment method is not given in the invoice, no check is executed.
If the payment method is given in the invoice, it must match with the payment
method maintained in the vendor master data in the current company code (table
LBF1).
If the payment method does not match, the exception is raised.
VIM070500-03-RGD-EN-1
19.27 Missing/Invalid Tax Exempt Text (PO)

information
The exception is raised in 2 cases:
• If the tax rate = 0 and the field Tax Exempt Text is blank, and there are no
different tax codes in the line items.
• If the tax rate > 0 and the field Tax Exempt Text is filled with text.
19.28 Missing Import Special Text (PO)

The supplier import invoice should have a reference/indication text indicating the
zero rated tax. There can be two scenarios as described in the following:
Special text present

The special text on the vendor’s invoice indicating tax exemption is present. In
this case, no action is taken and the document proceeds to the next logical step.
Special text not present

The special text on the vendor’s invoice indicating tax exemption is not present.
In this case, the exception Missing Import Special Text (PO) is raised and the
information
The function will check the tax rate given on the invoice. If the tax rate is zero and
there is no text entered in the field Import Text, the exception is raised.
If the tax rate is not zero but there is some text given in the field Import Text, the
exception is raised as well.
19.29 Missing Item Description (PO)

The invoices from suppliers should have the item description on the invoice for each
item supplied. There can be two scenarios as described in the following:
Item description present

The item description on the vendor’s invoice is present. In this case, no action is
Item description not present

The item description on the vendor’s invoice is not present. In this case, the
exception Missing Item Description (PO) is raised, and the invoice is
further action.
information
VIM070500-03-RGD-EN-1
19.30. Missing Mandatory Information (PO)
All line items of the invoice are checked.
If both fields SGTXT (Item Text) and MAKTX (Material Description) (in table /
OPT/VIM_1ITEM) of one of the line items are empty, the exception is raised.
19.30 Missing Mandatory Information (PO)

Selected fields on the DP document can be made mandatory as a part of the
configuration. This exception gets triggered if a value is not provided in the
mandatory field. There can be two scenarios as described in the following:
Field value entered in mandatory field

In this case, no action is taken and the document proceeds to the next logical
step.
Field value not entered in mandatory field

In this case, the exception Missing Mandatory Information (PO) is raised, and
the invoice is automatically routed to the pre-configured agent depending on the
information
Fields with status Required are read from table /opt/vim_nw_scrn. If there is one
required field that is not filled in the indexing data of the invoice, the exception is
raised.
The item fields are considered as well (table /opt/vim_i_scrn).
The header field groups SHIP_TO_ADDRESS and REMIT_TO_ADDRESS are evaluated. If

such a group is declared as mandatory, all address components except house
number and region must be filled.
Configuration Fields on the DP document can be maintained in /OPT/SPRO on the following levels:
point
On header level
Vendor Invoice Management > Document Processing Configuration >
Document Type Configuration > Maintain Document Types.
Select the DP Document Type. In Dialog Structure, double-click Index Header
Configuration.
On item level
Vendor Invoice Management > Document Processing Configuration >
Document Type Configuration > Maintain Document Types.
Select the DP Document Type. In Dialog Structure, double-click Index Item
Configuration.
VIM070500-03-RGD-EN-1
19.31 Missing/Invalid Triangulation Text (PO)

The supplier triangulation invoice should have a reference/indication text indicating
that the invoice is a triangulation invoice. There can be two scenarios as described in
the following:
Triangulation text present

The special text on the vendors invoice indicating triangulation is present. In this
case, no action is taken and the document proceeds to the next logical step.
Triangulation text not present

The special text on the vendor’s invoice indicating triangulation is not present.
In this case, the exception Missing/Invalid Triangulation Text (PO) is
information
19.32 Invalid Sales Tax for the Region (PO)

This business rule is only relevant for Canada. When this business rule is applied,
the ship-to address region, tax type and tax rate mentioned on the invoice is
matched against the allowed tax type and the tax rates for that region in SAP ERP. In
case of any deviations, the exception Invalid Sales for the Region (PO) is raised,
and the invoice is routed to the pre-configured agent depending on the role for
further action. There are many scenarios that could arise depending on the
Information matching
The ship-to region and tax types entered on the DP document matches with the
configured SAP ERP tax type for that region. The document proceeds to the next
logical step.
Example: For the region Ontario, the tax type GST is supplied, and the tax type GST is
configured in SAP ERP for that region.
Information not matching

The ship-to region and tax types entered on the DP document does not have a
corresponding valid configured SAP ERP tax type for that region. The exception
Invalid Sales Tax for the Region (PO) is raised and the document is
further action.
Example: For the region Ontario, the tax type GST is supplied, and the tax type
configured in SAP ERP is PST for that region.
Information not present

The ship-to region information is not present on the invoice. Depending on the
configuration option:
VIM070500-03-RGD-EN-1
19.32. Invalid Sales Tax for the Region (PO)
Default Region
Company code address/PO address are used as ship-to region. The business
rule proceeds with the above scenarios. You can configure this derivation of
the ship-to region on VIM side.
Blank
Keep the not present information as blank and raise exception Invalid
Sales Tax for the Region (NPO). The document is automatically routed to
Notes
• If VIM is used in combination with ICC, the ship-to region is not supplied by
ICC.
• VIM uses company code/PO (based on the configuration option chosen) to
derive the ship-to region when ICC is used as OCR. For cases where
company code/PO cannot be used to derive the ship-to region, you must
apply either a custom function or a manual entry.
• If the company code address cannot be treated as ship-to address, do not
use the company code option to derive the ship-to region. You need to
implement a custom function.
• If a PO or a combination of multiple POs has any line items with a varying
ship-to region for various PO line items (based on different Receiving
Plant at PO line item level), do not use the PO as an option to derive the
ship-to region. You need to implement a custom function.
• Without the ship-to region being determined automatically or supplied,
new business rules for validation of tax rate fields and tax code
determination will fail on VIM side; manual user input will be needed.
Technical FM /OPT/VIM_CHECK_TAX_RATE
information
First step
If tax rates (1 to 4) on line items are not given at all, they are copied from the tax
rates in the header data. The missing tax rates are determined (as much as
possible) based on the ship-to region and the configuration maintained in table /
OPT/VIM_TAX_PRO (Country Specific Tax - Province Relationship) for the region.
If the ship-to region is not given in the invoice (field SHIP_TP_REGION), it is
determined based on the options maintained in the customizing table /
OPT/VIM_STR_DET. A different logic is used for every possible option.
Possible options are the following:
Company Code
The ship-to region is determined based on the company code and read from
table T001.
Company Code -> PO
The ship-to region is determined based on the company code. If not found,
the ship-to region is determined based on the PO given in the invoice.
VIM070500-03-RGD-EN-1
PO -> Company Code

The ship-to region will firstly be determined based on the PO given in the
invoice. If not found, the ship-to region is determined based on the company
code. To determine the ship-to region based on the PO, the PO is read from
the header. If not given, the first PO in the line items is considered. Based on
the plan given in the PO, the ship-to region is read from table T001W.
Fixed Value
The region maintained in table /OPT/VIM_STR_DET is used as ship-to region.
Function Module
The FM maintained in table /OPT/VIM_STR_DET is used to determine the
ship-to region.
Second step
After all tax rates (in header as well as on line items) are determined, they will
be checked against table /OPT/VIM_TAX_PRO. If some tax rates are required
according to the customizing table, but not given in the invoice or cannot be
determined in the first step, the exception is raised.
Customization Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > Document Type Configuration > Specific
Country Settings > Canada.
19.33 Vendor Audit Required (PO)

Relevant vendors can be marked as audit required in the configuration so that the
invoices received from these vendors can be routed to the audit agent for further
processing. There can be two scenarios as described in the following:
No audit required
The vendor is not subjected to audit. In this case, no action is taken and the
document proceeds to the next logical step.
Audit required
The vendor is subjected to audit. An exception Vendor Audit Required (PO) is
information
If the vendor number is maintained in table /OPT/VIM_BL_VAUD with flag Audit
Required set, the exception Vendor Audit Required (PO) is raised for all invoices
of this vendor. The wildcard * in column Vendor Number means “All Vendors”.
Customization point
• Run the /OPT/VIM_BL_VAUD transaction or
• run the /n/OPT/VIM transaction and navigate to OpenText Vendor Invoice
Management > SAP menu > Customization > Vendor Audit List Configuration.
VIM070500-03-RGD-EN-1
19.34. Vendor Maintenance (PO)
19.34 Vendor Maintenance (PO)

This business rule is not in use yet.
19.35 Vendor Mismatch (PO)

The vendor number of the invoice should match with the purchase order vendor
number in the SAP ERP system. There can be two scenarios as described in the
following:
Match
The vendor number provided matches with the vendor number of the purchase
order in SAP ERP. In this case, no action is taken and the document proceeds to
Mismatch
The vendor number provided does not match with the vendor number of the
purchase order in SAP ERP. The exception Vendor Mismatch (PO) is raised and
information
The check is executed for every PO given in the invoice: in the header, in the PO list,
or in the line items. The vendor for each PO is read from table EKKO and is checked
against the vendor given in the invoice header.
• If matched, no further processing is required.
• If not matched, the partner functions maintained in the Z constant
EXIT_VEND_PARTN_FUNC for product 005 (table /PTGWFI/Z_CONST) is used to
fetch the partner vendor from table EKPA for a certain PO . If the partner vendor
does not match the vendor given in the document, the exception is raised.
• If the Z constant EXIT_VEND_PARTN_FUNC does not exist in the Z table or is blank,
the exception is raised as well.
19.36 Service Entry Required (PO)

When this business rule is applied, the service based invoice received by the
recipient is checked for the service entry sheet in the SAP ERP system. There can be
two scenarios as described in the following:
Exists
The service entry sheet exists. In this case, no action is taken and the document
Does not exist
The service entry sheet does not exist. In this case, the exception Service Entry
Required (PO) is raised, and the invoice is automatically routed to the pre-
VIM070500-03-RGD-EN-1
information
The PO number given in the invoice is checked in the following logic:
• Check whether some line item of the PO is set as Serv-based Invoice Verification
(the indicator LEBRE in table EKPO). If the indicator LEBRE is set, and no Service
Entry Sheet for this line exists (table EKBE) -> exception
• With VIM 7.0 SP3 and higher, the two Z constants SERVICE_ENTRY_BSTYP and
SERVICE_ENTRY_BSART (product code 005) are not used any more.
19.37 Currency Mismatch (PO)

This business rule exception gets triggered when the currency provided on the
invoice does not match with the purchase order currency. There can be two
scenarios as described in the following:
Match
The currency provided on the vendor’s invoice matches with the purchase order
currency in SAP ERP. In this case, no action is taken, and the document proceeds
to the next logical step.
Mismatch
The currency provided on the vendor’s invoice does not match with the
purchase order currency in SAP ERP. The exception Currency Mismatch (PO) is
information
The currency given in the header data of the invoice is compared with the currency
of all POs given in the invoice. All POs that are entered in the header and in the line
items are considered.
The POs given in the new field PO List is not considered yet.
19.38 Unit of Measure Mismatch (PO)

This business rule exception gets triggered when the unit of measure (UOM)
provided on the invoice does not match with the purchase order unit of measure.
There an be two scenarios as described in the following:
Match
The UOM provided on the vendor’s invoice matches with the purchase order
UOM in SAP ERP. In this case, no action is taken, and the document proceeds to
Mismatch
The UOM provided on the vendor’s invoice does not match with the purchase
order UOM in SAP ERP. The exception Unit of Measure Mismatch (PO) is
VIM070500-03-RGD-EN-1
19.39. Approval Required (PO)
information
For service POs, the MIRO proposal is calculated and the UOM is compared to the
MIRO proposal.
For normal POs, if all UOMs in the tables (EKPO, EKBE, MSEG) are the same, the UOM
is compared directly to the UOM in the line item. If the UOMs in the tables are
different, the MIRO proposal is calculated and the UOM is compared to the MIRO
proposal.
Additional change in VIM 7.0 and higher: Line items with qualifiers (additional
costs) are not considered for UOM matching because they are line items that
transport costs only.
19.39 Approval Required (PO)

This business rule exception gets triggered when one of the PO numbers, which are
given in the invoice header or in the line items, is maintained in the table of
Approval-required POs (table /OPT/VIM_BL_POAP). This business rule does not
consider the POs given in the PO list.
information
Customization Run the /n/OPT/VIM transaction and navigate to OpenText Vendor Invoice
point Management > SAP menu > Customization > PO Invoice Approval Configuration.
Note: If the exception is triggered, a work item is created and forwarded to the
requisitioner of the PO if this requisitioner is maintained in COA (Chart of
Authority). If not, no agent can be found for the current work item.
19.40 Freight on Invoice (PO)

This exception is triggered when the unplanned freight on the invoice is greater than
the freight amount maintained in the global configuration. There can be two
Does not exceed

The unplanned freight amount on the vendor’s invoice does not exceed the
freight amount maintained in the global configuration. In this case, no action is
Exceeds
The unplanned freight amount on the vendor’s invoice exceeds the freight
amount maintained in the global configuration. The exception Freight on
Invoice (PO) is raised, and the invoice is automatically routed to the pre-
information
The freight amount given on the invoice header is compared with the maximal
freight amount maintained in the Z constant 005 / FREIGHT_AMOUNT. If the freight
VIM070500-03-RGD-EN-1
amount on the invoice exceeds the amount maintained in the Z constant, the
exception is raised. If no value is maintained for this Z constant, no check is
executed.
19.41 Tax Audit Required (PO)

Relevant vendors can be marked as tax audit required in the configuration so that
the invoices received from these vendors can be routed to the tax audit agent for
further processing. There can be two scenarios as described in the following:
No tax audit required

The vendor is not subjected to tax audit. In this case, no action is taken and the
Tax audit required
The vendor is subjected to tax audit. An exception Tax Audit Required (PO) is
information
The configuration maintained in table /OPT/VIM_BL_TAX is checked. If company
code, material group, and vendor number on the invoice are maintained with the
flag set in table /OPT/VIM_BL_TAX, the exception Tax Audit Required (PO) is
raised.
The wildcard in all columns means “All”.
Customization point
• Transaction /OPT/VIM_BL_PTX, or
Management > SAP menu > Customization > Tax Audit Configuration for PO
Invoices.
19.42 Invalid Requisitioner

This exception is raised when the requisitioner mentioned on the supplier invoice
does not match with the SAP purchase order requisitioner. There can be two
Match
The supplier invoice requisitioner matches with the SAP purchase order
requisitioner. In this case, no action is taken and the document proceeds to the
next logical step.
Mismatch
The supplier invoice requisitioner does not match with the SAP purchase order
requisitioner. The exception Invalid Requisitioner is raised and the invoice is
further action.
VIM070500-03-RGD-EN-1
19.43. PO Credit Memo Processing (PO)
information
If the PO number is given in the PO document, it is checked whether it is SRM-
related or not. For an SRM-related PO, no further check is done. For a non-SRM-
related PO, the requisitioner of the PO is read from table EKPO. If this requisitioner is
not maintained in table /ORS/USERMAP (COA), the exception is raised.
To determine whether a PO is SRM-related or not, the status of the PO is compared

with the status maintained in the Z table under the Z constant SRM_PO_STATUS. If it
matches, the PO is considered as SRM-related.
19.43 PO Credit Memo Processing (PO)

If this business rule is maintained as active for the given Document Type, the PO
invoice is checked whether it is a Credit Memo or not. There can be two scenarios as
Not a Credit Memo

If the invoice is not a Credit Memo, no action is taken and the document
Credit Memo
If the invoice is a Credit Memo, the exception PO Credit Memo Processing (PO)
is raised, and the invoice is automatically routed to the pre-configured agent
Technical The field CREDIT_MEMO is checked. If it is selected, the invoice is handled as a

information Credit Memo and the exception is raised.
19.44 Company Code Mismatch (PO)

The company code of all POs entered in the invoice should match with the company
code in the header if the Company Code field of the header is filled. There can be
Match
The company code of all POs entered in the header and in the line items matches
the company code of the invoice. In this case, no action will be taken and the
document proceeds to the next logical step. If the company code is not given in
the header, no matching is executed.
Mismatch
The company code of at least one PO that is entered in the header and in the line
items does not match the company code of the invoice. The exception Company
Code Mismatch (PO) is raised and the invoice is automatically routed to the pre-
information
If the Company Code field in the header is not filled, no matching is executed. No
exception is raised.
VIM070500-03-RGD-EN-1
The company codes of all POs entered in the header and in the line items of the
invoice is read from table EKKO. The company codes of each PO are compared with
the company code of the invoice. If there is at least one mismatch, the exception is
raised.
When the exception occurs, the first “mismatching” PO number is returned in the
header structure if the constant FAIL_PO_HEADER_SET for product code 005 is set.
The business rule writes detailed information about the mismatches found into the
message table.
19.45 Confirmation Required from SRM (PO)

If this business rule is maintained as active for the given Document Type, all POs on
the invoice are checked whether there is a SRM-related PO. If there are some SRM-
related POs, some items of these POs are flagged as GRIV but there is no GR posted
for those items. The exception is raised, and the invoice is automatically routed to
information
• All POs on the invoice are checked whether they are SRM-related or not. If there
is a FM maintained in the constant LIX / SRM_PO_CHECK, this FM is called for the
checking. If there is no FM maintained, the status of the PO is compared with all
statuses maintained in the Z constant LIX / SRM_PO_STATUS. If the status matches,
the PO is considered as SRM-related.
• If the PO is SRM-related, a line item has a GRIV flag, and no GR or multiple GRs
exist for this item -> exception
19.46 Invalid Payment Reference (PO)

The business rule checks the payment reference using the SAP ERP function module
FI_PAYREF_CHECK. Payment reference check is used in Norway, Sweden and
Finland.
If the check fails, the exception Invalid Payment Reference (PO) is raised, and the
invoice is automatically routed to the pre-configured agent depending on the role
for further action.
information
VIM070500-03-RGD-EN-1
19.47. Missing Invoice Code (PO)
19.47 Missing Invoice Code (PO)

If the Invoice Code (INVOICE_CODE) field is empty, the exception Missing
invoice code (PO) is raised, and the invoice is automatically routed to the pre-
Technical To use this business rule, the INVOICE_CODE field must be configured as required
information field.
19.48 Invalid Invoice Code Format (PO)

If the Invoice Code (INVOICE_CODE) field length is not equal to 10 or 12, the
exception Invalid Invoice Code Format (PO) is raised.
If the invoice code length is equal to 10, then the 7th digit should be either 6 - or
greater than 0 and less than 5. Otherwise, the exception Invalid Invoice Code
Format (PO) is raised and the invoice is automatically routed to the pre-configured
agent depending on the role for further action.

information
19.49 Invalid Characters in Secret Code (PO)

In the Secret Code (SECRET_CODE1, SECRET_CODE2, SECRET_CODE3,
SECRET_CODE4) field, all digits from 0 to 9 are allowed. Apart from that, if the
Secret Code field value has characters other than +, /, <, >, -, *, then the exception
Invalid Characters in Secret Code (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

information
19.50 Invoice Older Than Allowed (PO)

If the difference of system date and invoice date is greater than the number of days
mentioned in the Z constant 005 / INVOICE_DAYS_OLD, the exception Invoice Older
than Allowed (PO) is raised, and the invoice is automatically routed to the pre-

information
VIM070500-03-RGD-EN-1
19.51 Invalid Vendor Invoice Number (PO)

The vendor reference value (XBLNR) length must be 8. Otherwise, the exception
Invalid Vendor Invoice Number (PO) is raised, and the invoice is automatically

information
19.52 Invalid Common Ordinary Invoice (VAT Exists)

(PO)
If the invoice category is Non VAT (N) and a VAT amount (VAT_AMOUNT) exists,
the exception Invalid Common Ordinary Invoice (PO) is raised, and the invoice is
action.

information
19.53 Check Hand Written (PO)

If the gross amount is greater than 100000 and the Not hand written
(NOT_HAND_WRITTEN) check box is not selected, the exception Check Hand
Written (PO) is raised, and the invoice is automatically routed to the pre-

information
19.54 Verification Required (PO)

If the AFTCS_VALIDATION field is empty, the exception Verification Required
(PO) is raised, and the invoice is automatically routed to the pre-configured agent

information
19.55 Validate Bank Details (PO)

If invalid bank data is received, the exception Validate Bank Details (PO) is

information
The business rule consists of the following checks:
• Check if bank entry exists in database in case of one-time-vendor
• Check if bank data is provided in case of one-time-vendor
• Check if bank data and vendor fit together
VIM070500-03-RGD-EN-1
19.56. Invalid/Missing Vendor ABN Number (PO)
• Check if IBAN number has valid syntax and does not contradict the other bank
details
• Check if SWIFT code has valid syntax and does not contradict the other bank
details
• Check for IBAN, if SWIFT code is given (SEPA check according SAP note
1400525)
• Check SWIFT code in bank data table BNKA, if SWIFT code is given (SEPA check
according SAP note 1400525)
The business rule writes detailed information about the error reason into the
message table.
19.56 Invalid/Missing Vendor ABN Number (PO)

If the vendor VAT number (VENDOR_VAT_NO) field is empty, or if the vendor VAT
number (VENDOR_VAT_NO) is not matching with the vendor master data, the
exception Invalid/Missing Vendor ABN Number (PO) is raised, and the invoice is
action.

information
19.57 Invalid/Missing Recipient ABN Number (PO)

If the recipient VAT number (RECIPIENT_VAT_NO) field is empty, or if the recipient
VAT number (RECIPIENT_VAT_NO) is not matching with company code master
data, the exception Invalid/Missing Recipient ABN Number (PO) is raised and the
for further action.

information
19.58 Missing Vendor Name (PO)

If the Vendor Name (VEND_NAME) field is empty, the exception Missing Vendor Name
Technical To use this business rule, the VEND_NAME field must be configured as required field.
information
VIM070500-03-RGD-EN-1
19.59 Missing Recipient Name (PO)

If the Recipient Name (RECIPIENT_NAME) field is empty, the exception Missing
Recipient Name (PO) is raised, and the invoice is automatically routed to the pre-
Technical To use this business rule, the RECIPIENT_NAME field must be configured as required
information field.
19.60 Invalid Tax Description (PO)

This business rule is specific to India. If the vendor belongs to India and the Tax
Description (TAX_DESC) field is empty, the exception Invalid Tax Description

information
19.61 GR Not Done - Simple Check

If a PO is GR-IV based and the Good Receipt is not done, the exception GR Not Done
- Simple Check is raised, and the invoice is automatically routed to the pre-

information
19.62 Missing Vendor ECC Number (PO)

This business rule is specific to India. If the vendor belongs to India and the ECC
Number (ECC_NO) field value is empty, the exception Missing Vendor ECC Number

information
19.63 Mismatch Vendor ECC Number (PO)

This business rule is specific to India. The following conditions can apply:
• The vendor belongs to India.

• The material in the DP document is excisable material.
• The ECC Number (ECC_NO) field value does not match with the vendor master
data.
If these conditions apply, the exception Mismatch Vendor ECC Number (PO) is
VIM070500-03-RGD-EN-1
19.64. Missing Vendor CST Number (PO)

information
19.64 Missing Vendor CST Number (PO)

This business rule is specific to India. If the vendor belongs to India and the CST
Number (CST_NO) field value is empty, the exception Missing Vendor CST Number

information
19.65 Mismatch Vendor CST Number (PO)

This business rule is specific to India. If the vendor belongs to India, and the CST
Number (CST_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor CST Number (PO) is raised and the invoice is
action.

information
19.66 Missing Vendor TIN/TOT Number (PO)

This business rule is specific to India. If the vendor belongs to India and the TIN/
TOT Number (TIN_TOT) field value is empty, the exception Missing Vendor
TIN/TOT Number (PO) is raised, and the invoice is automatically routed to the pre-

information
19.67 Mismatch Vendor TIN/TOT Number (PO)

This business rule is specific to India. If the vendor belongs to India, and the TIN/
TOT Number (TIN_TOT) field value does not match with the vendor master data, the
exception Mismatch Vendor TIN/TOT Number (PO) is raised, and the invoice is
action.

information
VIM070500-03-RGD-EN-1
19.68 Missing Vendor LST Number (PO)

This business rule is specific to India. If the vendor belongs to India and the LST
Number (LST_NO) field value is empty, the exception Missing Vendor LST Number

information
19.69 Mismatch Vendor LST Number (PO)

Number (LST_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor LST Number (PO) is raised, and the invoice is
action.

information
19.70 Missing Vendor PAN Number (PO)

This business rule is specific to India. If the vendor belongs to India and the PAN
Number (PAN_NO) field value is empty, the exception Missing Vendor PAN Number

information
19.71 Mismatch Vendor PAN Number (PO)

Number (PAN_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor PAN Number (PO) is raised and the invoice is
action.

information
VIM070500-03-RGD-EN-1
19.72. Missing Vendor STC Number (PO)
19.72 Missing Vendor STC Number (PO)

This business rule is specific to India. If the vendor belongs to India and the STC
Number (STC_NO) field value is empty, the exception Missing Vendor STC Number

information
19.73 Mismatch Vendor STC Number (PO)

Number (STC_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor STC Number (PO) is raised, and the invoice is
action.

information
19.74 Wait for GR - Simple Check (PO)

If a PO is GR-IV based and the Good Receipt is not done, this exception is raised.
This rule is optimized to be maintained for a waiting process type.
• For any PO number within indexing data (header/item), the PO lines are checked
if any line has the GR-IV based flag set.
• For these lines, it is checked that at least one open invoicing line exists.

information
19.75 Wait for GR - Enhanced Check (PO)

• For any PO item within indexing data (header/item), the delivered PO lines are
checked if any line has the GR-IV based flag set.
• For these lines, it is checked that all lines are open for invoicing with the correct
amount.

information
VIM070500-03-RGD-EN-1
19.76 Brazil - Missing NF Data (PO)

If the Nota Fiscal Data within the invoice is not filled, this exception is raised.

information
19.77 Brazil - Missing NF Customizing (PO)

If the Nota Fiscal Data is not customized on the system, this exception is raised.

information
19.78 Brazil - NF Validation Check Failed (PO)

For future use.

information
19.79 Brazil - Wait for GR - Simple Check (PO)


information
19.80 Brazil - Wait for GR - Enhanced Check (PO)

amount.

information
VIM070500-03-RGD-EN-1
19.81. Russia - Wait for TORG-12/ACT - Simple Check (PO)
19.81 Russia - Wait for TORG-12/ACT - Simple Check

(PO)
If a PO is GR-IV based and the Good Receipt (Bill of lading = TORG-12 form) is not
done, this exception is raised. This rule is optimized to be maintained for a waiting
process type.

information
19.82 Russia - Wait for TORG-12/ACT - Enhanced

Check (PO)
If a PO is GR-IV based and the Good Receipt (Bill of lading = TORG-12 form) is not
done, this exception is raised. This rule is optimized to be maintained for a waiting
process type.
amount.

information
19.83 Russia - Original Invoice Mismatch (PO)

A corrective invoice contains the original invoice number and date. If the reference
number of the original invoice cannot be found in VIM, this exception is raised.

information
19.84 Withholding Tax Code Not Valid for Vendor (PO)

This business rule is valid for documents that are subject to withholding tax. If the
withholding tax code is not valid for the invoice vendor, the exception is raised.

information
VIM070500-03-RGD-EN-1
19.85 Withholding Tax Base Amount Bigger Than Total

Net Amount (PO)
withholding tax base amount is bigger than the total net amount, the exception is
raised.

information
19.86 Check BPF Added Data (PO)

When this business rule is applied, a check is performed whether data of a DP PO
document was enhanced within the logic module processing.
Technical FM: /OPT/VIM_DETERMINE_BPF_VALID

information
19.87 Tolerance Exceeded (PO)

When this business rule is applied, the PO invoice amount is checked whether it
does not exceed the PO amount and tolerances like in MIRO.

information
19.88 Missing VAT Date (PO)

This business rule checks if the VAT date is provided in the DP document. If not, the
DP processing stops with an exception. Users are required to enter the VAT date in
the DP document. To enable the check, add the respective process type for DP
document or characteristic, with the function /OPT/VIM_DETERMINE_PROC_407.
The baseline configuration of this business rule contains predefined process options.
You can adjust the process options list to suit your scenarios.

information
19.89 Check Withholding Tax Data (PO)

withholding tax checked flag is not filled, the exception is raised.

information
VIM070500-03-RGD-EN-1
Chapter 20
Business Rules for NPO Invoices
This chapter describes the various business rules for NPO invoices. The business
rules are delivered out of the box with the product including the high level business
logic of each of these rules.
20.1 Invalid Vendor (NPO)

The supplier mentioned on the invoice should be available in the SAP ERP system.
Exists
The invoice supplier exists in the SAP ERP system as a vendor. In this case, no
action is taken, and the document proceeds to the next logical step.
Does not exist

The invoice supplier does not exist in the SAP ERP system as a vendor. The
exception Invalid Vendor (NPO) is raised, and the invoice is automatically

information
For more information, see “Invalid Vendor (PO)” on page 182.
20.2 Invalid Currency (NPO)

The currency provided on the invoice should exist in the SAP ERP system. There can
Exists
The currency on the supplier invoice exists in SAP ERP. In this case, no action is
Does not exist

The currency on the supplier invoice does not exist in SAP ERP. The exception
Invalid Currency (NPO) is raised and the work item is automatically routed to
Technical Field WAERS is checked against SAP table TCURC.

information
VIM070500-03-RGD-EN-1
Chapter 20 Business Rules for NPO Invoices
20.3 Invalid Requestor ID (NPO)

This exception is raised when the requestor mentioned on the supplier invoice does
not exist in SAP ERP. There can be two scenarios as described in the following:
Exists
The requestor mentioned on the supplier invoice exists in the recipient’s SAP
ERP system. In this case, no action is taken, and the document proceeds to the
next logical step.
Does not exist

The requestor mentioned on the supplier invoice does not exist in the recipient’s
SAP ERP system. The exception Invalid Requestor ID (NPO) is raised, and the

information
If the Email ID is available in the index data, it is searched in table /ORS/USERMAP
(maintained in COA). If no such email address exists, or it exists but is marked as
Deleted -> Exception
20.4 Suspected Duplicate (NPO)

This specific business rule checks for a duplicate invoice based on specific fields
configured in the configuration. There can be two scenarios as described in the
following:
Not a duplicate
If the invoice is not a duplicate, no action is taken, and the document proceeds to
Duplicate
If the invoice is a duplicate, the exception Suspected Duplicate (NPO) is
raised, and the work item is automatically routed to the pre-configured agent
Technical FM: /OPT/VIM_DETERMINE_PROC_DUP

information
For more information, see “Suspected Duplicate (PO)” on page 183.
VIM070500-03-RGD-EN-1
20.5. Non-PO Credit Memo Processing
20.5 Non-PO Credit Memo Processing

If this Business Rule is applied, an exception is always raised for an invoice where
the indicator Credit Memo is checked. Its purpose is to indicate that the incoming
invoice is a credit memo. Such invoices will be sent to a pre-defined agent for further
processing.
Technical Field CREDIT_MEMO will be checked. If this field of a NPO invoice is checked, the
information invoice is considered as a Credit Memo.
20.6 Derivation Rule - Non-PO Expense Type

This is not a rule that will check and throw an exception if the check is not
successful. The Derivation Rule is used in OCR case only. This rule should be
executed only once.

information
Invoices of vendors who are maintained in the table /OPT/VIM_BL_UTLV (Utility
Vendors) with flag UTLITY_VEND_FLAG set to X shall always have the Expense Type
UT - Utility.
All invoices of other vendors shall have the Expense Type ST - Standard.
20.7 Invalid Vendor VAT Number (NPO)

When this business rule is applied, the supplier VAT/Tax number provided on the
invoice must match with the vendor master VAT/Tax number provided in SAP ERP.
The following scenarios are possible:
Match
The supplier VAT/Tax number provided on the invoice matches with the VAT/
Tax number mentioned in the vendor master. In this case, no action is taken, and
the document proceeds to the next logical step.
Mismatch
The supplier VAT/Tax number provided on the invoice does not match with the
VAT/Tax number mentioned in the vendor master in SAP ERP. The exception
Invalid Vendor VAT Number (NPO) is raised, and the invoice is automatically

information
For more information, see “Invalid Vendor VAT Number (PO)” on page 190.
VIM070500-03-RGD-EN-1
20.8 Incomplete Credit Memo (NPO)

When this business rule is applied, the credit memo should have the original
suppliers invoice number. Also, the original invoice number mentioned on the credit
memo must be present in the SAP ERP system. There can be three scenarios as
Present and matching

The credit memo has the original invoice number. Further, there should be an
invoice in the SAP ERP system (DP document or SAP document) that has the
original suppliers invoice number as the reference number. In this case, the
exception is not raised, and the document proceeds to the next logical step.
Not present
The credit memo does not have the original invoice number. The exception
Incomplete Credit Memo (NPO) is raised, and the invoice is automatically
Mismatch
The credit memo has the original invoice number, and there is no invoice
existing in the SAP ERP system (DP document or SAP document) that has the
original suppliers invoice number as the reference number. The exception
Incomplete Credit Memo (NPO) is raised, and the invoice is automatically

information
For more information, see “Incomplete Credit Memo (PO)” on page 191.
20.9 Vendor Address Mismatch (NPO)

The Remit-To-Address (suppliers address to which the billing should happen)
should match with the SAP ERP Vendor Master’s address as this is a required
information on the suppliers invoice. There can be two scenarios as described in the
following:
Match
The Remit-To-Address provided on the invoice matches with the address on the
vendor master. In this case, no action is taken, and the document proceeds to the
next logical step.
Mismatch
The Remit-To-Address does not match with the address on the vendor master.
The exception Vendor Address Mismatch (NPO) is raised, and the invoice is
further action.
The following SAP ERP vendor address fields are matched:
• House #
VIM070500-03-RGD-EN-1
20.10. Missing Invoice Date (NPO)
• Street
• Postal Code
• City
• Region
• Country

information
20.10 Missing Invoice Date (NPO)

When this business rule is applied, the invoice date on the DP index document
header should have been entered. There can be two scenarios as described in the
following:
Entered
The invoice date is entered on the DP index document header. In this case, no
Not entered
The invoice date is not entered on the DP index document header. The exception
Missing Invoice Date (NPO) is raised, and the invoice is automatically routed
to the pre-configured agent depending on the role for further action.
Technical If field BLDAT of the indexing data is not filled -> Exception
information
20.11 Invalid Tax Info (NPO)

The supplier’s invoice should carry the total VAT amount and (or) the VAT %
indicating the VAT payable.
When this business rule is applied, the tax information provided on the vendor
invoice is analyzed and mapped to standard SAP tax values (tax codes) and passed
onto the DP document. Depending on the VIM specific tax configuration settings
(with auto calculate tax or without auto calculate tax), the tax information is
validated. In case of any deviations, the exception Invalid Tax Info (NPO) is
raised, and the invoice is routed to the pre-configured agent depending on the role
for further action. There are many scenarios that can arise depending on the
Tax information present and matching

The tax information entered on the DP document has a corresponding valid SAP
tax information. The document proceeds to the next logical step.
Example: The VAT % mentioned on the invoice has a corresponding VAT tax code.
Tax information present and not matching

The tax information entered on the DP document does not have corresponding
valid SAP tax information. The exception Invalid Tax Info (NPO) is raised,
VIM070500-03-RGD-EN-1
and the document is automatically routed to the pre-configured agent

Example: The VAT % mentioned on the invoice does not have a corresponding VAT tax
code in SAP ERP.
Tax information not present

The tax information is not present on the invoice. The exception Invalid Tax
Info (NPO) is raised, and the document is automatically routed to the pre-
Example: The payable VAT % or VAT amount is not present on the vendor’s invoice.

information
For more information, see “Invalid Tax Info (PO)” on page 194.
20.12 Invalid Recipient VAT Number (NPO)

Every country has its typical VAT structure. You find this information in the
Company Master Data. For some countries, the recipient’s VAT number is a
mandatory information for some kind of invoices (for example for intra-community
invoices or triangulation invoices).
When this business rule is applied, the recipient VAT number provided on the
invoice must match with the company’s VAT number provided in the company
code in SAP ERP. The following scenarios can apply:
Match
The recipient’s VAT number provided on the invoice matches with the VAT
number mentioned in the company code information. In this case, no action is
Mismatch
The recipient’s VAT number provided on the invoice does not match with the
VAT number mentioned in the company code in SAP ERP. The exception
Invalid Recipient VAT Number is raised, and the invoice is automatically
Not present
If the recipient’s VAT number is not present on the invoice, the exception
Invalid Recipient VAT Number is raised, and the invoice is automatically

information
For more information, see “Invalid Recipient VAT Number (PO)” on page 198.
VIM070500-03-RGD-EN-1
20.13. ISR Number Mismatch (NPO)
20.13 ISR Number Mismatch (NPO)

This business rule is specific for Switzerland. The supplier’s invoice should have the
ISR number on the invoice as this is a required information.
When this business rule is applied, the ISR number on the DP index document
header should be present and matching with the vendor master. The following
scenarios are possible:
ISR number present and matching

No action is taken, and the document proceeds to the next logical step.
ISR number present and not matching

The exception ISR Number Mismatch (NPO) is raised, and the invoice is
further action.
ISR number not present

If the ISR number is not mentioned on the invoice but the vendor master has it,
the exception ISR Number Mismatch (NPO) is raised, and the invoice is
further action.

information
For more information, see “ISR Number Mismatch (PO)” on page 197.
20.14 Payment Terms Mismatch (NPO)

The payment terms mentioned on the supplier’s invoice should match with the
payment terms configured in the SAP ERP system. There can be two scenarios as
Match
The payment terms provided on the vendor’s invoice matches with the payment
terms mentioned in the vendor master in SAP ERP. In this case, no action is
Mismatch
The payment terms provided on the vendor’s invoice does not match with the
payment terms maintained in the vendor master in SAP ERP. The exception
Payment Terms Mismatch (NPO) is raised, and the invoice is automatically

information
For more information, see “Payment Terms Mismatch (PO)” on page 199.
VIM070500-03-RGD-EN-1
20.15 Missing Date of Supply (NPO)

The invoices should have the date of supply mentioned on the invoice provided by
the suppliers. There can be two scenarios as described in the following:
Date of supply present

The date of supply on the vendor’s invoice is present. In this case, no action is
Date of supply not present
The date of supply on the vendor’s invoice is not present. In this case, the
exception Missing Date of Supply (NPO) is raised, and the invoice is
further action.
Technical The field SUPPLY_DATE must be filled. If it is not, the exception is raised.
information
20.16 Invalid Siret Number (NPO) (French)

This business rule is, for example, applied for France. The SIRET number provided
on the invoice is matched against the SIRET number maintained in the vendor
master. There can be two scenarios as described in the following:
Match
The SIRET number provided on the invoice matches with the SIRET number in
the vendor master. In this case, no action is taken, and the document proceeds to
Mismatch
The SIRET number provided in the invoice does not match with the SIRET
number in the vendor master. The exception Invalid SIRET Number (NPO) is

information
For more information, see “Invalid Siret Number (PO) (French)” on page 199
20.17 Invalid Company Address (NPO)

The recipient address provided on the invoice should match with the SAP ERP
company code’s address. There can be two scenarios as described in the following:
Match
The recipient address provided on the invoice matches with the company code
address. In this case, no action is taken, and the document proceeds to the next
logical step.
Mismatch
The recipient address does not match with the address of the company code.
The exception Invalid Company Address (NPO) is raised, and the invoice is
VIM070500-03-RGD-EN-1
20.18. Vendor Invoice Reference Missing (NPO)

further action.

information
For more information, see “Invalid Company Address (PO)” on page 200.
20.18 Vendor Invoice Reference Missing (NPO)

The supplier invoice should have its invoice number mentioned on the invoice.
Invoice number present

The invoice number on the vendor’s invoice is present. In this case, no action is
Invoice number not present

The invoice number on the vendor’s invoice is not present. In this case, the
exception Vendor Invoice Reference Number Missing (NPO) is raised, and the
Technical In the baseline, field XBLNR is set as Required field. That means the value of this field
information in the indexing data is checked. If it is empty -> exception
20.19 Payment Method Mismatch (NPO)

The payment method mentioned on the supplier’s invoice should match with the
payment method configured in the SAP ERP system. There can be two scenarios as
Match
The payment method provided on the vendor’s invoice matches with the
payment method mentioned in the vendor master in SAP ERP. In this case, no
Mismatch
The payment method provided on the vendor’s invoice does not match with the
payment method maintained in the vendor master in SAP ERP. The exception
Payment Method Mismatch (NPO) is raised, and the invoice is automatically

information
For more information, see “Payment Method Mismatch (PO)” on page 201.
VIM070500-03-RGD-EN-1
20.20 Determine Expense Type

This Business Rule is used to derive the Expense Type if this field is not delivered.
There are 3 types of Expense Types:
PA
Pre-approved. This Expense Type is delivered from OCR.
UT
Utility invoices from vendors that match the predefined Utility Vendors.
ST
Standard for other invoices.
The FM checks the vendor in the invoice against the vendors maintained in table /
OPT/VIM_BL_UTLV. If the vendor is maintained as Utility Vendor, the Expense Type
is set to UT. Otherwise the Expense Type is set to ST.

information
Customization Run the /n/OPT/VIM transaction and navigate to SAP menu > Customization >
point Utility Vendors.
20.21 Missing/Invalid Tax Exempt Text (NPO)

The exception is raised in the following cases:
• If the tax rate = 0 and the Tax Exempt Text field is blank, and there are no
different tax codes in the line items.
• If the tax rate > 0 and the Tax Exempt Text field is filled with text.

information
20.22 Missing Import Special Text (NPO)

The supplier import invoice should have a reference/indication text indicating the
zero rated tax. There can be two scenarios as described in the following:
Special text present

The special text on the vendors invoice indicating tax exemption is present. In
this case, no action is taken, and the document proceeds to the next logical step.
Special text not present

The special text on the vendor’s invoice indicating tax exemption is not present.
In this case, the exception Missing Import Special Text (NPO) is raised, and

information
VIM070500-03-RGD-EN-1
20.23. Missing Item Description (NPO)
For more information, see “Missing Import Special Text (PO)” on page 202.
20.23 Missing Item Description (NPO)

The invoices received (for example by Switzerland companies) from suppliers
should have the item description on the invoice for each item supplied. There can be
Item description present

The item description on the vendor’s invoice is present. In this case, no action is
Item description not present

The item description on the vendor’s invoice is not present. In this case, the
exception Missing Item Description (NPO) is raised, and the invoice is
further action.

information
For more information, see “Missing Item Description (PO)” on page 202.
20.24 Missing Mandatory Information (NPO)

Selected fields on the DP document can be made mandatory as a part of the
configuration. This exception gets triggered when a value is not provided in the
mandatory field. There can be two scenarios as described in the following:
Field value entered in mandatory field

In this case, no action is taken, and the document proceeds to the next logical
step.
Field value not entered in mandatory field

In this case, the exception Missing Mandatory Information (NPO) is raised,
and the invoice is automatically routed to the pre-configured agent depending
on the role for further action.

information
For more information, see “Missing Mandatory Information (PO)” on page 203.
VIM070500-03-RGD-EN-1
20.25 Missing/Invalid Triangulation Text (NPO)

The supplier triangulation invoice should have a reference/indication text indicating
that the invoice is a triangulation invoice. There can be two scenarios as described in
the following:
Triangulation text present

The special text on the vendors invoice indicating triangulation is present. In this
case, no action is taken, and the document proceeds to the next logical step.
Triangulation text not present

The special text on the vendor’s invoice indicating triangulation is not present.
In this case, the exception Missing/Invalid Triangulation Text (NPO) is

information
For more information, see “Missing/Invalid Triangulation Text (PO)” on page 204.
20.26 Invalid Sales Tax For The Region (NPO)

When this business rule is applied, the ship-to address region, tax type, and tax rate
mentioned on the invoice are matched against the allowed tax type and the tax rates
for that region in VIM. In case of any deviations, the exception Invalid Sales for
the Region (NPO) is raised, and the invoice is routed to the pre-configured agent
depending on the role for further action. There are many scenarios that can arise
depending on the configuration. Some of the possible scenarios are described in the
following:
Information matching
The ship-to region, tax types entered on the DP document matches with the
configured SAP ERP tax type for that region. The document proceeds to the next
logical step.
Example: For region Ontario, the tax type GST is supplied, and the tax type GST is
configured in SAP ERP for that region.
Information not matching

The ship-to region and tax types entered on the DP document do not have a
corresponding valid configured SAP ERP tax type for that region. The exception
Invalid Sales Tax for the Region (NPO) is raised, and the document is
further action.
Example: For region Ontario, the tax type GST is supplied, and the tax type configured
in SAP ERP is PST for that region.
Information not present

The ship-to region information is not present on the invoice. Depending on the
configuration option:
VIM070500-03-RGD-EN-1
20.27. Non PO Approval Required (NPO)
Default Region
Set company code address as ship-to region and proceed with the above
scenarios. You can configure this derivation of the ship-to region on VIM
side.
Blank
Keep the not present information as blank and raise exception Invalid
Sales Tax for the Region (NPO). The document is automatically routed to
Notes
• If VIM is used in combination with ICC, the ship-to region is not supplied by
ICC.
• VIM uses company code/PO (based on the configuration option chosen) to
derive the ship-to region when ICC is used as OCR. For cases where
company code cannot be used to derive the ship-to region, you must apply
either a custom function or a manual entry.
• If the company code address cannot be treated as ship-to address, do not

use the company code option to derive the ship-to region. You need to
implement a custom function.
• Without the ship-to region being determined automatically or supplied,
new business rules for validation of tax rate fields and tax code
determination will fail on VIM side; manual user input will be needed.
Technical FM: /OPT/VIM_CHECK_TAX_RATE

information
For more information, see “Invalid Sales Tax for the Region (PO)” on page 204.
Customization Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > Document Type Configuration > Specific
Country Settings > Canada.
20.27 Non PO Approval Required (NPO)

This Business Rule is used to determine whether the Approval process must be
invoked for the invoice.

information
The Expense Type given in the invoice is checked against table /ORS/EXPENSE_TYP
to determine whether Approval is required for this expense type. If Approval is
required, the exception is raised. A work item is created and forwarded to the
requester given in the invoice.
Customization Run transaction /n/OPT/SPRO and navigate to Vendor Invoice Management >
point Invoice Approval Configuration > Approval Workflow > Setup Approval Chain >
Maintain Expense Types.
VIM070500-03-RGD-EN-1
In the Expense Type Definition Maintenance (View), you can maintain whether
Approval is required for a specific Expense Type.
20.28 Vendor Audit Required (NPO)

Relevant vendors can be marked as audit required in the configuration so that the
invoices received from these vendors can be routed to the audit agent for further
processing. There can be two scenarios as described in the following:
No audit required
The vendor is not subjected to audit. In this case, no action is taken and the
Audit required
The vendor is subjected to audit. An exception Vendor Audit Required (NPO) is

information
Customization point
• Run the /OPT/VIM_BL_VAUD transaction or
Management > SAP menu > Customization > Vendor Audit List Configuration.
For more information, see “Vendor Audit Required (PO)” on page 206.
20.29 Tax Audit Required (NPO)

Relevant vendors can be marked as tax audit required in the configuration so that
the invoices received from these vendors can be routed to the tax audit agent for
further processing. There can be two scenarios as described in the following:
No tax audit required

The vendor is not subjected to tax audit. In this case, no action is taken, and the
Tax audit required
The vendor is subjected to tax audit. An exception Tax Audit Required (NPO) is

information
The configuration maintained in table /OPT/VIM_BL_NPTX is checked. If the
company code, the G/L account number, and the vendor number on the invoice are
maintained in the table with the Active flag set, the exception Tax Audit Required
(NPO) is raised.
The wildcard in all columns means “All”.
VIM070500-03-RGD-EN-1
20.30. Validate Bank Details (NPO)
Customization Run the /OPT/VIM_BL_NPTX transaction. Alternatively, run the /n/OPT/VIM

point transaction and navigate to OpenText Vendor Invoice Management > SAP menu >
Customization > Tax Audit Configuration for PO Invoices.
20.30 Validate Bank Details (NPO)

If invalid bank data is received, the exception Validate Bank Details (NPO) is

information
For more information, see “Validate Bank Details (PO)” on page 214.
20.31 Validate Accounting Data (NPO)

When the business rule is applied, header and accounting data are validated. The
validation done here is the same as the validation done in the approval screen when
an invoice is approved. If an error occurs, error messages are added to the log table,
and the exception Validate Accounting Data (NPO) is raised. A work item is
created and routed to the pre-configured agent for further action.
To use this business rule, you must maintain and activate the new process type 271
in the document type configuration, navigating to /OPT/SPRO > Vendor Invoice
Management > Document Processing Configuration > Document Type
Configuration > Maintain Document Types. For background information, see
Section 9.1.2 “Defining Process Types” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide (VIM-CGD).
In the Baseline configuration, the process type is not characteristic specific (the
Characteristic Check check box is not set). Therefore, you do not have to maintain
the process type for characteristic.
In the document type configuration, Sequence Steps, use the function module /
OPT/VIM_DETERMINE_PROC_LIB004 as Check Function for DP Document Type
NPO_75, Step ID 418. For background information, see Section 9.1.3.1 “Defining
Sequence Steps” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
In the Baseline configuration, the business rule is added to the document type
NPO_75 but it is not activated.
Technical FM: /OPT/VIM_DETERMINE_PROC_LIB004

information
VIM070500-03-RGD-EN-1
20.32 Invalid Payment Reference (NPO)

Payment reference check is used in Norway, Sweden and Finland. The business rule
checks the payment reference using the SAP ERP function module
FI_PAYREF_CHECK.
If the check fails, the exception Invalid Payment Reference (NPO) is raised, and

information
20.33 Missing Invoice Code (NPO)

If the Invoice Code (INVOICE_CODE) field is empty, the exception Missing
invoice code (NPO) is raised, and the invoice is automatically routed to the pre-
Technical To use this business rule, the INVOICE_CODE field must be configured as required
information field.
20.34 Invalid Invoice Code Format (NPO)

If the Invoice Code (INVOICE_CODE) field length is not equal to 10 or 12, the
exception Invalid Invoice Code Format (NPO) is raised.
If the invoice code length is equal to 10, then the 7th digit should be one of the
following digits: 1, 2, 3, 4, or 6. If this is not the case, the exception Invalid Invoice
Code Format (NPO) is raised and the invoice is automatically routed to the pre-

information
20.35 Invalid Characters in Secret Code (NPO)

The Secret Code (SECRET_CODE1, SECRET_CODE2, SECRET_CODE3,
SECRET_CODE4) field value may contain only the following characters:
• Digits from 0 to 9
• Characters like +, /, <, >, -, and *
Otherwise, the exception Invalid Characters in Secret Code (NPO) is raised, and

information
VIM070500-03-RGD-EN-1
20.36. Invoice Older Than Allowed (NPO)
20.36 Invoice Older Than Allowed (NPO)

If the difference of system date and invoice date is greater than the number of days
mentioned in the Z constant 005 / INVOICE_DAYS_OLD, the exception Invoice Older
than Allowed (NPO) is raised, and the invoice is automatically routed to the pre-

information
20.37 Invalid Vendor Invoice Number (NPO)

The vendor reference value (XBLNR) length must be 8. If this is not the case, the
exception Invalid Vendor Invoice Number (NPO) is raised, and the invoice is
action.

information
20.38 Invalid Common Ordinary Invoice (VAT Exists)

(NPO)
If the invoice category is Non VAT (N) and a VAT amount (VAT_AMOUNT) exists,
the exception Invalid Common Ordinary Invoice (NPO) is raised, and the invoice is
action.

information
20.39 Check Hand Written (NPO)

If the gross amount is greater than 100000 and the Not hand written
(NOT_HAND_WRITTEN) check box is not selected, the exception Check Hand
Written (NPO) is raised, and the invoice is automatically routed to the pre-

information
VIM070500-03-RGD-EN-1
20.40 Verification Required (NPO)

If the AFTCS_VALIDATION field is empty, the exception Verification Required
(NPO) is raised, and the invoice is automatically routed to the pre-configured agent

information
20.41 Invalid/Missing Vendor ABN Number (NPO)

If the vendor VAT number (VENDOR_VAT_NO) field is empty, or if the vendor VAT
number (VENDOR_VAT_NO) is not matching with the vendor master data, the
exception Invalid/Missing Vendor ABN Number (NPO) is raised, and the invoice is
action.

information
20.42 Invalid/Missing Recipient ABN Number (NPO)

If the recipient VAT number (RECIPIENT_VAT_NO) field is empty, or if the recipient
VAT number (RECIPIENT_VAT_NO) is not matching with company code master data,
the exception Invalid/Missing Recipient ABN Number (NPO) is raised, and the
for further action.

information
20.43 Missing Vendor Name (NPO)

If the Vendor Name (VEND_NAME) field is empty, the exception Missing Vendor Name
Technical To use this business rule, the VEND_NAME field must be configured as required field.
information
20.44 Missing Recipient Name (NPO)

If the Recipient Name (RECIPIENT_NAME) field is empty, the exception Missing
Recipient Name (NPO) is raised, and the invoice is automatically routed to the pre-
Technical To use this business rule, the RECIPIENT_NAME field must be configured as required
information field.
VIM070500-03-RGD-EN-1
20.45. Invalid Tax Description (NPO)
20.45 Invalid Tax Description (NPO)

This business rule is specific to India. If the vendor belongs to India and the Tax
Description (TAX_DESC) field is empty, the exception Invalid Tax Description

information
20.46 Missing Vendor PAN Number (NPO)

Number (PAN_NO) field value is empty, the exception Missing Vendor PAN Number

information
20.47 Mismatch Vendor PAN Number (NPO)

Number (PAN_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor PAN Number (NPO) is raised and the invoice is
action.

information
20.48 Missing Vendor STC Number (NPO)

Number (STC_NO) field value is empty, the exception Missing Vendor STC Number

information
20.49 Mismatch Vendor STC Number (NPO)

Number (STC_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor STC Number (NPO) is raised, and the invoice is
action.

information
VIM070500-03-RGD-EN-1
20.50 Missing Vendor CST Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the CST
Number (CST_NO) field value is empty, the exception Missing Vendor CST Number

information
20.51 Mismatch Vendor CST Number (NPO)

This business rule is specific to India. If the vendor belongs to India, and the CST
Number (CST_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor CST Number (NPO) is raised and the invoice is
action.

information
20.52 Missing Vendor TIN/TOT Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the TIN/
TOT Number (TIN_TOT) field value is empty, the exception Missing Vendor
TIN/TOT Number (NPO) is raised, and the invoice is automatically routed to the pre-

information
20.53 Mismatch Vendor TIN/TOT Number (NPO)

This business rule is specific to India. If the vendor belongs to India, and the TIN/
TOT Number (TIN_TOT) field value does not match with the vendor master data, the
exception Mismatch Vendor TIN/TOT Number (NPO) is raised, and the invoice is
action.

information
VIM070500-03-RGD-EN-1
20.54. Missing Vendor LST Number (NPO)
20.54 Missing Vendor LST Number (NPO)

Number (LST_NO) field value is empty, the exception Missing Vendor LST Number

information
20.55 Mismatch Vendor LST Number (NPO)

Number (LST_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor LST Number (NPO) is raised, and the invoice is
action.

information
20.56 Check BPF Added Data (NPO)

When this business rule is applied, a check is performed whether data of a DP NPO
document was enhanced within the logic module processing.

information
20.57 Missing VAT Date (NPO)

This business rule checks if the VAT date is provided in the DP document. If not, the
DP processing stops with an exception. Users are required to enter the VAT date in
the DP document. To enable the check, add the respective process type for DP
document or characteristic, with the function /OPT/VIM_DETERMINE_PROC_407.
The baseline configuration of this business rule contains predefined process options.
You can adjust the process options list to suit your scenarios.

information
VIM070500-03-RGD-EN-1
20.58 Check Withholding Tax Data (NPO)

withholding tax checked flag is not filled, the exception is raised.

information
VIM070500-03-RGD-EN-1
Chapter 21
General Business Rules
This section describes general business rules that are independent from NPO or PO.
21.1 Check Data After Restart

If the DP process was started using the process option Delete and Restart, the DP
process will run into this exception. The user can verify or add the index data of the
new DP process and can continue the DP process.
21.2 Check Data After Reject from Validation

If the DP process was started with forwarding a document from status 90 Reject
from Validation, the DP process will run into this exception. This exception can be
treated manually, but you can also configure that the document is set to obsolete or
that it is sent to rescan.
To leave the exception, you must choose one of the following options:
• Activate bypass
• Send to rescan
• Obsolete document
You cannot leave the exception by changing data, by clicking Apply Business Rules,
or by referring the document to another user.
Technical FM: /OPT/VIM_DETERMINE_PROC_RJ

information
21.3 Check Inbound Interface Errors

This exception is triggered if there were recoverable errors detected in the IDH
interface for the given document. The processor is supposed to review the errors, by
clicking the Display Errors button in the DP dashboard. For the DP process to
continue, the errors must be confirmed by clicking the option button configured for
the process option 2025 (Confirm Errors).
Note: As of VIM 7.0 SP3, only the Ariba inbound interface triggers this.
Technical FM: /OPT/VIM_DETERMINE_PROC_IDHERR

information
VIM070500-03-RGD-EN-1
Chapter 21 General Business Rules
21.4 Copy Rule: Supply Date to VAT Date

You can enter the VAT Date field during indexing in the DP indexing screen. In
many cases, the value of the supply date, which already exists in VIM, can be
assigned to the VAT date.
This business rule copies the supply date value into the VAT date. This is not a
dialog process type: it does not trigger an exception. The same process type has to be
used for both PO and NPO invoices. You can enable it for individual document
types or using characteristics.

information
VIM070500-03-RGD-EN-1
Chapter 22
Summary Tables
22.1 Table: Business Rules for PO Invoices

Index Business rule Function Module Version[a]
100 Process PO Invoice (PO) No FM required 5.2
/OPT/
101 Invalid PO Number (PO) 5.2
VIM_DETERMINE_PROC_101
/OPT/
102 Invalid Vendor (PO) 5.2
/OPT/
103 Invalid UOM (PO) 5.2
Field WAERS will be checked
104 Invalid Currency (PO) 5.2
against SAP table TCURC
/OPT/
105 Suspected Duplicate (PO) 5.2
VIM_DETERMINE_PROC_DUP
/OPT/
106 PO Is Not Released (PO) 5.2
/OPT/
107 Unable to Match PO Lines (PO) 5.2
108 Process PO Invoice (PO) OCR No FM required 5.2
Unable to Determine PO Line /OPT/
109 5.2
Number (PO) VIM_DETERMINE_PROC_POL
Manual Check Needed for
110 /OPT/VIM_LINES_DERIVE_PO 5.2
Indexing Lines (PO)
/OPT/
111 Missing invoice code (PO) 6.0
/OPT/
112 Invalid invoice code format (PO) 6.0
Manual Check Needed / Missing /OPT/
113 7.5
Data for Indexing Lines (PO) VIM_DETERMINE_PROC_108
Invalid characters in Secret code /OPT/
114 6.0
(PO) VIM_DETERMINE_PROC_114
Invalid PO item number (PO) /OPT/
115 VIM_DETERMINE_PROC_ITEM 7.0 SP3
S
/OPT/
116 Invoice older than allowed (PO) 6.0
VIM070500-03-RGD-EN-1
Chapter 22 Summary Tables

Invalid vendor invoice number /OPT/
117 6.0
Invalid common ordinary invoice /OPT/
118 6.0
(VAT Exists) (PO) VIM_DETERMINE_PROC_118
/OPT/
119 Check hand written invoice (PO) 6.0
Invalid Vendor VAT Number /OPT/
120 5.2
/OPT/
121 Incomplete Credit Memo (PO) 5.2
/OPT/
122 Vendor Address Mismatch (PO) 5.2
/OPT/
123 Missing Item Quantity (PO) 5.2
125 Missing Invoice Date (PO) Field BLDAT must be filled 5.2
/OPT/
126 Invalid Tax Info (PO) 5.2
Field SUPPLY_DATE must be
127 Missing Date of Supply (PO) 5.2
filled
Invalid Recipient VAT Number /OPT/
128 5.2
/OPT/
129 ISR Number Mismatch (PO) 5.2
/OPT/
130 Payment Terms Mismatch (PO) 5.2
/OPT/
131 Invalid Siret Number (PO) 5.2
/OPT/
132 Invalid Company Address (PO) 5.2
Vendor Invoice Reference
133 Field XBLNR must be filled. 5.2
Missing (PO)
/OPT/
134 Payment Method Mismatch (PO) 5.2
Missing/Invalid Tax exempt Text /OPT/
135 5.2
/OPT/
136 Missing Import Special Text (PO) 5.2
/OPT/
137 Missing Item Description (PO) 5.2
VIM070500-03-RGD-EN-1
22.1. Table: Business Rules for PO Invoices

Missing Mandatory Information /OPT/
138 5.2
Missing/Invalid Triangulation /OPT/
139 5.2
Text (PO) VIM_DETERMINE_PROC_139
Invalid Sales Tax for the Region
140 OPT/VIM_CHECK_TAX_RATE 6.0
(PO)
/OPT/
141 Verification required (PO) 6.0
142 Check Data After Restart No FM required 5.2
/OPT/
145 Invalid Tax Description (PO) 6.0
Not necessary – triggered via
149 Posted Approval Required (PO) 5.2
PAS
/OPT/
150 Approval Required (PO) 5.2
/OPT/
151 Vendor Audit Required (PO) 5.2
/OPT/
153 Vendor Mismatch (PO) 5.2
/OPT/
154 Service Entry Required (PO) 5.2
/OPT/
155 Currency Mismatch (PO) 5.2
/OPT/
156 Unit of Measure Mismatch (PO) 5.2
/OPT/
157 Freight on Invoice (PO) 5.2
/OPT/
158 Tax Audit Required (PO) 5.2
/OPT/
159 Invalid Requisitioner (PO) 5.2
Field CREDIT_MEMO will be
160 PO Credit Memo Processing (PO) 5.2
checked.
/OPT/
161 Company Code Mismatch (PO) 5.2
Confirmation required from SRM /OPT/
162 5.2
/OPT/
163 GR Not Done - Simple Check 6.0
VIM070500-03-RGD-EN-1

/OPT/
164 Wait for GR - Simple Check (PO) 7.0
Wait for GR - Enhanced Check /OPT/
165 7.0
/OPT/
170 Validate Bank Details (PO) 7.0
Invalid/Missing Vendor ABN /OPT/
172 6.0
Number (PO) VIM_DETERMINE_PROC_172
Invalid/Missing Recipients ABN /OPT/
173 6.0
Number(PO) VIM_DETERMINE_PROC_173
174 Missing Vendor Name(PO) Configuration 6.0
175 Missing Recipients Name(PO) Configuration 6.0
/OPT/
176 Invalid Payment Reference (PO) 5.2
Missing Vendor ECC /OPT/
177 6.0
Mismatch Vendor ECC /OPT/
178 6.0
Missing Vendor CST /OPT/
179 6.0
Mismatch Vendor CST /OPT/
180 6.0
Missing Vendor TIN/TOT /OPT/
181 6.0
Mismatch Vendor TIN/TOT /OPT/
182 6.0
Missing Vendor LST /OPT/
183 6.0
Mismatch Vendor LST /OPT/
184 6.0
Missing Vendor PAN /OPT/
185 6.0
Mismatch Vendor PAN /OPT/
186 6.0
Missing Vendor STC /OPT/
187 6.0
Mismatch Vendor STC /OPT/
188 6.0
/OPT/
191 Missing NF Data (PO) 7.0
VIM070500-03-RGD-EN-1
22.2. Table: Business Rules for NPO Invoices

/OPT/
192 Missing NF Customizing (PO) 7.0
/OPT/
193 NF validation check failed (PO) 7.0
Brazil – Wait for GR – Simple /OPT/
194 7.0
Check (PO) VIM_DETERMINE_PROC_194
Brazil – Wait for GR – Enhanced /OPT/
195 7.0
Check (PO) VIM_DETERMINE_PROC_195
Russia – Wait for TORG-12/ACT /OPT/
196 7.0
– Simple Check (PO) VIM_DETERMINE_PROC_196
Russia – Wait for TORG-12/ACT /OPT/
197 7.0
– Enhanced Check (PO) VIM_DETERMINE_PROC_197
Russia – Original Invoice /OPT/
198 7.0
Mismatch (PO) VIM_DETERMINE_PROC_198
/OPT/
401 Withholding Tax Code not Valid 7.0
Withholding Tax Amount Bigger /OPT/
402 7.0
than Total Net Amount VIM_DETERMINE_PROC_402
/OPT/
405 Check BPF Added Data (PO) 7.5
VIM_DETERMINE_BPF_VALID
/OPT/
406 Tolerance Exceeded (PO) 7.5
/OPT/
408 Missing VAT Date (PO) 7.0 SP4
Check Withholding Tax Data /OPT/
415 7.0 SP6
[a] VIM version that introduced the business rule.
22.2 Table: Business Rules for NPO Invoices

200 Process Non-PO Invoice (NPO) Not necessary 5.2
/OPT/
201 Invalid Vendor (NPO) 5.2
Field WAERS will be checked
202 Invalid Currency (NPO) 5.2
against SAP table TCURC
/OPT/
203 Invalid Requester ID (NPO) 5.2
/OPT/
204 Suspected Duplicate (NPO) 5.2
VIM_DETERMINE_PROC_DUP
VIM070500-03-RGD-EN-1

206 Non-PO Credit Memo Processing Check field CREDIT_MEMO 5.2
Process Non-PO Invoice (NPO)
207 Not necessary 5.2
OCR
Derivation Rule – Non PO – /OPT/
209 5.2
Expense Type VIM_DETERMINE_PROC_209
/OPT/
211 Missing invoice code (NPO) 6.0
Invalid invoice code format /OPT/
212 6.0
(NPO) VIM_DETERMINE_PROC_112
Missing Secret Code (NPO) / /OPT/
213 6.0
Obsolete since VIM 7.0 VIM_DETERMINE_PROC_113
Invalid characters in Secret code /OPT/
214 6.0
Invoice older than allowed /OPT/
216 6.0
Invalid vendor invoice number /OPT/
217 6.0
Invalid common ordinary invoice /OPT/
218 6.0
(VAT Exists) (NPO) VIM_DETERMINE_PROC_118
Check hand written invoice /OPT/
219 6.0
Invalid Vendor VAT Number /OPT/
220 5.2
/OPT/
221 Incomplete Credit Memo (NPO) 5.2
Vendor Address Mismatch /OPT/
222 5.2
223 Missing Invoice Date (NPO) Field BLDAT must be filled 5.2
/OPT/
224 Invalid Tax Info (NPO) 5.2
Invalid Recipient VAT Number /OPT/
225 5.2
Field SUPPLY_DATE must be
228 Missing Date of Supply (NPO) 5.2
filled
/OPT/
229 Invalid Siret Number (NPO) 5.2
/OPT/
232 Invalid Company Address (NPO) 5.2
Vendor Invoice Reference Field XBLNR is required to be
233 5.2
Missing (NPO) filled
VIM070500-03-RGD-EN-1
22.2. Table: Business Rules for NPO Invoices

Payment Method Mismatch /OPT/
234 5.2
Missing/Invalid Tax exempt Text /OPT/
235 5.2
Missing Import Special Text /OPT/
236 5.2
/OPT/
237 Missing Item description (NPO) 5.2
Missing Mandatory Information /OPT/
238 5.2
Missing/Invalid Triangulation /OPT/
239 5.2
Text (NPO) VIM_DETERMINE_PROC_139
Invalid Sales Tax For the Region
240 /OPT/VIM_CHECK_TAX_RATE 5.2
(NPO)
/OPT/
241 Verification required (NPO) 6.0
/OPT/
242 Check Data After Restart 5.2
/OPT/
245 Invalid Tax Description (NPO) 6.0
Posted Approval Required Not necessary – triggered via
249 5.2
(NPO) PAS
Non PO Approval Required /OPT/
250 5.2
/OPT/
253 Vendor Audit Required (NPO) 5.2
/OPT/
254 Tax Audit Required (NPO) 5.2
Invalid/Missing Vendor ABN /OPT/
255 6.0
Number (NPO) VIM_DETERMINE_PROC_172
Invalid/Missing Recipients ABN /OPT/
256 6.0
Number(NPO) VIM_DETERMINE_PROC_173
257 Missing Vendor Name(NPO) Configuration 6.0
258 Missing Recipients Name(NPO) Configuration 6.0
/OPT/
270 Validate Bank Details (NPO) 7.0
/OPT/
271 Validate Accounting Data (NPO) VIM_DETERMINE_PROC_LIB00 7.0 SP3
4
VIM070500-03-RGD-EN-1

Invalid Payment Reference /OPT/
276 5.2
Missing Vendor PAN /OPT/
277 6.0
Mismatch Vendor PAN /OPT/
278 6.0
Missing Vendor STC /OPT/
279 6.0
Mismatch Vendor STC /OPT/
280 6.0
Missing Vendor CST /OPT/
281 6.0
Mismatch Vendor CST /OPT/
282 6.0
Missing Vendor TIN/TOT /OPT/
283 6.0
Mismatch Vendor TIN/TOT /OPT/
284 6.0
Missing Vendor LST /OPT/
285 6.0
Mismatch Vendor LST /OPT/
286 6.0
Check Withholding Tax Data /OPT/
289 7.0 SP6
/OPT/
407 Missing VAT Date (NPO) 7.0 SP4
22.3 Table: General Business Rules

140 Check data after restart /OPT/ 5.2
243 Check data after reject from /OPT/ 7.0 SP7
validation VIM_DETERMINE_PROC_RJ
403 Check inbound interface errors /OPT/ 7.0 SP3
VIM_DETERMINE_PROC_IDHE
RR
VIM070500-03-RGD-EN-1
22.3. Table: General Business Rules

409 Copy rule: Supply Date to VAT /OPT/ 7.0 SP4
Date VIM_DETERMINE_PROC_409
VIM070500-03-RGD-EN-1
Chapter 23
Customer Library
Besides the business rules delivered along with VIM Baseline, you can create custom
business rules as well as implement custom function modules for your business
rules to meet your needs. OpenText delivers some function module templates that
you can configure or implement. The functions are example functions.
23.1 Check Country Consistency

This function checks whether the country assigned to the VIM document type is equ
al to the corresponding country resulting from the entered index data.

information
23.2 Check Balance

This function executes a balance check. You find details in the function module.

information
23.3 Check and Update Coding for Auto Coding

This function updates the coding data within the invoice item data according to the
auto coding configuration for NPO.

information
VIM070500-03-RGD-EN-1
Part 7
Logic Modules
Part 7 Logic Modules
The task of logic modules is to check whether data is missing for a document and to
add the data where possible. This data enrichment is mostly scheduled before the
business rules run. It can be useful to also trigger some logic modules at a later point
of time, for example if the user has entered data on the indexing screen and presses
Rerun Business Rules.
Business rule Check BPF Added Data (process types 404 and 405) has been added. It
“informs” the user that a logic module has added data to the document. Business
rules are intended to check document data whereas logic modules are intended to
also change document data.
VIM070500-03-RGD-EN-1
Chapter 24
General Information About Logic Modules
The following categories of logic modules exist:
• Simple mapping (single fields)

• Mapping
• Changing data
• Deleting data
You can group logic modules into process IDs and schedule them to run at the
following points in time:
• at process start
• at rerun business rules
• at both (process start and rerun business rules)
The mapping modules are intended to run before the DP workflow is started. They
replace enhanced mapping functions.
Changing and deleting modules check data and modify if certain conditions are
fulfilled. Some of them are intended to run at process start, others during rerun
business rules.
For reasons of clarity, the modules are classified as:
• Global processing
• PO processing
• NPO processing
• Country specific
The VIM baseline customizing contains preconfigured process IDs that you must
map to PO and NPO document types. Some global processing is active for all
document types.
point Document Processing Configuration > Document Type Configuration > Logic
Module Processing.
For details, see Section 9.3 “Processing Logic Modules” in OpenText Vendor Invoice
VIM070500-03-RGD-EN-1
Chapter 25
Global Processing Logic Modules
25.1 Change Vendor Group

This logic module changes the vendor group. If the vendor is changed in
background (for example, due to the partner role), the vendor group must be
changed, too.
Precondition
Vendor number and company code are filled.
Data affected
Vendor group
Class interface
/OPT/CL_D_LM_CHG_V_GRP
25.2 Determine Bank Data

This logic module fills missing bank data.
Category
Mapping
Precondition
Partner bank type is empty.
Data affected
All bank data is filled if available in vendor master.
• Partner bank type

• Bank number
• Name of bank
• Bank country key
• IBAN
• SWIFT
• Vendor permitted as payee
• Reference specification for bank details
Class interface
/OPT/CL_D_LM_DETERM_BANKDATA
VIM070500-03-RGD-EN-1
Chapter 25 Global Processing Logic Modules
25.3 Determine SAP Document Type

This logic module fills the missing SAP document type from VIM document type
customizing.
Category
Simple mapping
Precondition
SAP document type is empty.
Data affected
SAP document type is filled.
Class interface
/OPT/CL_D_LM_DETERM_BLART
25.4 Determine Country

This logic module fills country specific data (invoice category).
Category
Simple mapping
Precondition
Company code or document type is filled.
Data affected
Invoice category, tax invoice flag is filled.
Class interface
/OPT/CL_D_LM_DETERM_COUNTRY
25.5 Determine Invoice Category

This logic module maps the ICC-specific invoice category to the VIM invoice
category.
Category
Simple mapping
Precondition
Invoice category is filled from ICC.
Data affected
Invoice category contains a VIM specific value.
Class interface
/OPT/CL_D_LM_DETERM_INV_CAT
VIM070500-03-RGD-EN-1
25.6. Determine Payment Terms
25.6 Determine Payment Terms

This logic module fills missing payment terms from the vendor (non PO) or from the
PO (vendor, company code). In VIM baseline, this logic module is configured to run
at process start.
Category
Mapping
Precondition
Document type, vendor number and company code are filled.
Data affected
Payment terms are filled.
Class interface
/OPT/CL_D_LM_DETERM_PAY_TERM
25.7 Determine Payment Baseline Date

This logic module fills missing payment baseline date from VIM document type
customizing. In VIM baseline, this logic module is configured to run at process start.
Category
Mapping
Precondition
Payment baseline date is empty.
Data affected
Payment baseline date is filled.
Class interface
/OPT/CL_D_LM_DETERM_PBL_DATE
25.8 Determine Posting Date

This logic module fills the posting date from VIM country specific customizing.
Category
Simple mapping
Precondition
Posting date or posting date determination is empty.
Data affected
Posting date is filled.
Class interface
/OPT/CL_D_LM_DETERM_POST_DATE
VIM070500-03-RGD-EN-1
25.9 Determine Tax Code

This logic module fills the tax code using VIM document type customizing.
Category
Simple mapping
Precondition
Tax code is empty.
Data affected
Tax code is filled.
Class interface
/OPT/CL_D_LM_DETERM_TAX_CODE
25.10 Determine New Credit Memo Flag

This logic module fills the document “transaction” field (VORGANG) depending on the
older Credit memo flag.
Category
Simple mapping
Precondition
Document “transaction” field is initial and old credit memo flag is filled.
Data affected
New credit memo flag is filled.
Class interface
/OPT/CL_D_LM_DETERM_VORGANG
25.11 Determine Vendor Address

This logic module fills the vendor address data from the vendor master.
Category
Simple mapping
Precondition
Vendor number is filled.
Data affected
Vendor address is filled.
Class interface
/OPT/CL_D_LM_DETERM_V_ADR
VIM070500-03-RGD-EN-1
25.12. Determine Vendor Group
25.12 Determine Vendor Group

This logic module fills the vendor group from VIM Business Rule Framework
Customizing.
Category
Simple mapping
Precondition
Vendor number and company code are filled.
Data affected
Vendor group is filled.
Class interface
/OPT/CL_D_LM_DETERM_V_GRP
25.13 Determine Vendor Name

This logic module fills the vendor name from the vendor master.
Category
Simple mapping
Precondition
Vendor name is empty and vendor number is filled.
Data affected
Vendor name is filled.
Class interface
/OPT/CL_D_LM_DETERM_V_NAME
25.14 Determine Withholding Tax

This logic module fills the withholding tax data. Classic withholding data are read
only on the indexing screen. Extended withholding tax data can be changed
manually.
Category
Mapping
Precondition
Vendor number and company code are filled and subject to withholding tax.
The following data is required to retrieve withholding tax.
For PO documents
• Company code
• Vendor
• Total gross amount
VIM070500-03-RGD-EN-1
• PO number
• Tax code for net or tax based withholding tax type
For Non PO documents

• Company code
• Vendor
• Total gross amount
• Currency
• Posting date
• At least one line item
Data affected
Withholding tax data is filled.
Class interface
/OPT/CL_D_LM_FILL_WHT
25.15 Synchronize Item Text

This logic module synchronizes the item text and item material text fields. If one is
initial and the other is not, the content is copied.
Category
Simple mapping
Precondition
Not applicable
Data affected
Item text fields SGTXT and MAKTX contain the same text.
Class interface
/OPT/CL_D_LM_SYNC_ITEM_TXT
VIM070500-03-RGD-EN-1
Chapter 26
PO Related Logic Modules
26.1 Determine Currency

This logic module fills missing currency from an existing PO.
Category
Simple mapping
Precondition
Currency is empty and PO number is filled.
Data affected
Currency is filled.
Class interface
/OPT/CL_D_LM_DETERM_CURR
26.2 Determine Delivery Date

This logic module fills the missing delivery date from an existing PO.
Category
Simple mapping
Precondition
Delivery date is empty and PO number is filled.
Data affected
Delivery date is filled.
Class interface
/OPT/CL_D_LM_DETERM_DEL_DATE
26.3 Determine PO Item Data

This logic module fills the PO data according to the VIM document type specific PO
Line Automation customizing.
Category
Mapping at process start
Precondition
PO number is filled.
Data affected
PO item data is retrieved.
VIM070500-03-RGD-EN-1
Chapter 26 PO Related Logic Modules
Class interface
/OPT/CL_D_LM_DETERM_PO_MAP
26.4 Determine Matching Single Line PO Data for

Vendor
This logic module checks whether open single item POs for the vendor match
invoice data.
Category
Precondition
Single line item invoice; PO number is empty and vendor is filled.
Data affected
PO data is retrieved.
Class interface
/OPT/CL_D_LM_DETERM_PO_SGL1
26.5 Determine Vendor

This logic module fills the missing vendor from the PO.
Category
Simple mapping
Precondition
Vendor number is empty and PO number is filled.
Data affected
Vendor number is filled
Class interface
/OPT/CL_D_LM_DETERM_LIFNR
26.6 Determine Additional Costs

This logic module looks for planned costs in the PO and matches them with
additional cost lines delivered by ICC. Unmatched lines are treated according to
VIM unplanned costs handling determination.
Category
Mapping
Precondition
PO number(s) provided, and ICC delivers valid additional cost lines.
Data affected
Depending on the VIM additional cost customizing
VIM070500-03-RGD-EN-1
26.7. Use PO Header Data to Overwrite Line Items
Class interface
/OPT/CL_D_LM_MAP_ADD_COSTS
26.7 Use PO Header Data to Overwrite Line Items

This logic module discards the existing lines items and overwrites them with the
current MIRO proposal (GR) list.
Category
Mapping
Precondition
PO number and invoice header amount are filled. The PO amount is identical to
the GR amount and the invoice amount.
Data affected
Line items are overwritten.
Class interface
/OPT/CL_D_LM_MAP_HEADER_PO
26.8 Verify PO Data

This logic module checks whether the PO number belongs to company code and
vendor. Non-matching data is deleted. If no PO is left, the document type is
redetermined.
Category
Changing data
Precondition
Company code, PO number and vendor number are filled.
Data affected
PO number, PO line item data, document type
Class interface
/OPT/CL_D_LM_VERIFY_DATA
VIM070500-03-RGD-EN-1
Chapter 27
NPO Related Logic Modules
27.1 Determine Expense Type

This logic module fills a missing expense type from VIM vendor customizing.
Category
Simple mapping
Precondition
Expense type is empty and vendor is filled.
Data affected
Expense type is filled.
Class interface
/OPT/CL_D_LM_DETERM_EXP
27.2 Determine NPO Line

This logic module fills a missing line item from header data.
Category
Precondition
NPO document type and no line item.
Data affected
One line item is created from header data.
Class interface
/OPT/CL_D_LM_DETERM_NPO_LINE
27.3 Determine NPO Auto-Coding

This logic module fills coding data from the VIM NPO line auto-coding
configuration.
Category
Precondition
No purchase order numbers or delivery notes are used on the invoice.
Data affected
Line item coding data is filled.
VIM070500-03-RGD-EN-1
Chapter 27 NPO Related Logic Modules
Class interface
/OPT/CL_D_LM_DETERM_NPO_COD
VIM070500-03-RGD-EN-1
Chapter 28
Country Specific Logic Modules
28.1 Determine Ship-to Region for Canada

This logic module fills the ship-to region for Canada.
Category
Simple mapping
Precondition
Country is Canada and ship-to region is empty.
Data affected
Ship-to region is filled.
Class interface
/OPT/CL_D_LM_DETERM_SHP_REGN
28.2 Determine Corrective Items for Russia

This logic module reacts to ICC delivered corrective invoice categories for Russia
and condenses line items for VIM.
Category
Mapping
Precondition
Country is Russia and invoice category contains either a V or a W.
Data affected
Four corrective line items are condensed to one line.
Class interface
/OPT/CL_D_LM_MAP_R_CORR_ITEMS
VIM070500-03-RGD-EN-1
Chapter 28 Country Specific Logic Modules
28.3 Determine Service PO for Russia

This logic module reacts to ICC delivered service invoice categories for Russia and
maps a single service PO.
Category
Mapping
Precondition
Country is Russia, the PO number is empty and the invoice category contains M.
A PO with corresponding net price and quantity exists for the vendor.
Data affected
Service PO is filled.
Class interface
/OPT/CL_D_LM_MAP_R_SERV_PO
28.4 Determine KIDNO for Denmark

This logic module checks and, if needed, corrects the payment reference field
(KIDNO) for Denmark.
Category
Mapping
Precondition
Country is Denmark. Company code is filled and payment reference is
provided.
Data affected
KIDNO is filled.
Class interface
/OPT/CL_D_LM_VERIFY_KIDNO
VIM070500-03-RGD-EN-1
Part 8
Automated Field Enhancement
Part 8 Automated Field Enhancement
VIM provides a feature that allows you to add mapping activities after the field
mapping is done. In this Automated Field Enhancement (also called enhanced
mapping), you can refer to the values of different fields.
VIM070500-03-RGD-EN-1
Chapter 29
Configuring Automated Field Enhancement
You control Automated Field Enhancement in table /OPT/VIM_T107, and you

maintain it in the same maintenance view as the normal field mapping. For more
information, see Section 8.2 “Maintaining the VIM Field Mapping” in OpenText
In the Automated Field Enhancement configuration, you enter a sequence of

entries, which will be processed in the order of their counter value. In each entry,
you specify a target field and the action (normally a function module), which will be
called to modify the value of the target field.
In the field mapping, the relation between source field and target field is a 1:1
relation. This is visible in the mapping table. With Automated Field Enhancement,
this is not the case. “Baseline of Automated Field Enhancement“ on page 281 shows
the relation between source fields and target fields.
VIM070500-03-RGD-EN-1
Chapter 30
Baseline of Automated Field Enhancement
The following tables provide an overview of Automated Field Enhancement, which

is delivered in the baseline. The overview shows only the involved values and
tables.
Mapping ID Type Sources Target field Function module

GENERAL Header LIFNR, LFA1 VEND_NAME /OPT/
VIM_EXIT_MAP_E
NH_01
GENERAL Item MAKTX SGTXT /OPT/
VIM_EXIT_MAP_E
NH_01
GENERAL Item SGTXT MAKTX /OPT/
VIM_EXIT_MAP_E
NH_01
GENERAL Header CREDIT_MEMO VORGANG /OPT/
VIM_EXIT_MAP_E
NH_03
GENERAL Header EBELN, T169F BLART /OPT/
VIM_EXIT_MAP_E
NH_03

ICC Header LIFNR, LFA1 VEND_NAME /OPT/
VIM_EXIT_MAP_E
NH_01
ICC Item SGTXT SGTXT /OPT/
VIM_EXIT_MAP_E
NH_01
ICC Item MAKTX MAKTX /OPT/
VIM_EXIT_MAP_E
NH_01
ICC Header CREDIT_MEMO VORGANG /OPT/
VIM_EXIT_MAP_E
NH_03
ICC Header EBELN, T169F BLART /OPT/
VIM_EXIT_MAP_E
NH_03
VIM070500-03-RGD-EN-1
Chapter 30 Baseline of Automated Field Enhancement

ICC Header INV_CAT CLASSIFIER /OPT/
VIM_EXIT_MAP_E
NH_05
ICC Header XBLNR, INV_CAT NFNUM /OPT/
VIM_EXIT_MAP_E
NH_04
ICC Header INV_CAT FLAG_SNFE /OPT/
VIM_EXIT_MAP_E
NH_04
ICC Header INV_CAT MODEL /OPT/
VIM_EXIT_MAP_E
NH_04
ICC Header INV_CAT NF_TYPE /OPT/
VIM_EXIT_MAP_E
NH_04
ICC Header BLDAT SUPPLY_DATE /OPT/
VIM_EXIT_MAP_E
NH_04
ICC Header INV_CAT, XBLNR XBLNR /OPT/
VIM_EXIT_MAP_E
NH_04
ICC Header CLASSIFIER INV_CAT /OPT/
VIM_EXIT_MAP_E
NH_05
ICC Header CONTRACT, BSTYP /OPT/
INV_CAT, EKKO VIM_EXIT_MAP_E
NH_06
ICC Header ORG_NUM, BKTXT /OPT/
ORG_DATE, VIM_EXIT_MAP_E
INV_CAT NH_06
ICC Header TAX_DESC TAX_INVOICE /OPT/
VIM_EXIT_MAP_E
NH_07
ICC Header PAN_NO, LIFNR, VENDOR_VAT_N /OPT/
LFA1 O VIM_EXIT_MAP_E
NH_07
ICC Header STC_NO, LIFNR, VENDOR_TAX_N /OPT/
LFA1 O VIM_EXIT_MAP_E
NH_07
ICC Header VENDOR_TAX_N SIRET_NO /OPT/
O VIM_EXIT_MAP_E
NH_07
VIM070500-03-RGD-EN-1
ICC Header LIFNR, LFA1, REMIT_STREET /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_HSNM1 /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_PSTLZ /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_LAND1 /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_AD_CITY1 /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_REGIO /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header BNKA SWIFT /OPT/
VIM_EXIT_MAP_E
NH_08
ICC Header IBAN, SWIFT, BANKS /OPT/
BNKA VIM_EXIT_MAP_E
NH_08

XML_ENFE Header BLDAT DOCDAT /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header DOCDAT BLDAT /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header RMWWR GROSS_AMOUNT /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header GROSS RMWWR /OPT/
_AMOUNT. VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header LIFNR LIFNR /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header PARID PARID /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
VIM070500-03-RGD-EN-1
Chapter 30 Baseline of Automated Field Enhancement

XML_ENFE Header STCD1 VEND_NAME /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_STREET REMIT_STREET /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_PSTLZ REMIT_PSTLZ /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_AD_CITY1 REMIT_AD_CITY1 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_LAND1 REMIT_LAND1 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_REGIO REMIT_REGIO /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header BUKRS, CDC, BUKRS /OPT/
T001Z VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM XBLNR /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM9 NFNUM9 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM NFNUM /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header J_1BAA NF_TYPE /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Fix: BRL WAERS
XML_ENFE Header Fix: X AUTO_CALC
XML_ENFE Header Fix: X FLAG_ENFE
VIM070500-03-RGD-EN-1
Part 9
Z Constants
Part 9 Z Constants
This part provides a list of the Z constants that are used in VIM. There are individual
chapters for each product code.
The following product codes are available:
002, 009
Cross component product codes
005
Document Processing (DP) based product codes
IAP
Invoice Approval product codes
IEA
Product codes for Unified Dashboard and archiving supports
IEM
Invoice Exception Monitor product codes
KPI
KPI Dashboard product codes
LIX
LIV based product codes (both for PO parking and PO blocking workflows)
PIR
Product codes for Non-PO parking workflows
VAN
VIM Analytics product codes
VIM070500-03-RGD-EN-1
Chapter 31
Z Constants for Product Code 002 and 009
Product Constant Description Default Value

Code
Fail_Safe
002 FAILSAFE_TCODE transaction code /OPT/CP_9CX10
LIV Parking
reasons that
require PO number
during document
002 LIV_PO_REQ_REASONS parking 7
Suppress -
“Continue with out
workflow” Button
002 SUP_CONT_WO_WF_BUTT on parking screen
Suppress “Return
to invoice” Button
002 SUP_RETN_TO_INV_BUTT on parking screen X
FM to determine
the Approver for /PTGWFI/
002 APPROVER_GET_FM Parked Document 0000000002_APP001
Function module to
check input on /PTGWFI/
002 CHK_REQUESTER_RCODE requester code 0000000002_TMP006
Function Module
to calculate Due
date for Delay FM /PTGWFI/
002 DUE_DATE_FM logic 0000000002_TMP010
Function Module
to calculate Due
date for Delay FM /PTGWFI/
002 DUE_DATE_FM_PRICE logic ( Price Block) 0000000002_TMP010
FM Exit for
collective
validitation of
initial approvers
from all approval /PTGWFI/
002 EXIT_MULTI_APPROVERS paths 0000000002_TMP004
FM Exit for
validitating initial
approver in an /PTGWFI/
002 EXIT_SINGLE_APPROVER approval path 0000000002_TMP003
VIM070500-03-RGD-EN-1
Chapter 31 Z Constants for Product Code 002 and 009

Code
Superior's approval
is independednt of
Subordinate's
approval in
002 FAST_TRACK_APPROVAL another chain
Get Current
Approver and the
Next Approver to
GET_CURRENT_APPROVE the current
002 R Approver /PTGWFI/0000000002_M002
Get Intial
Approvers for the /PTGWFI/
002 GET_INITIAL_APPROVER invoice document 0000000002_TMP007
Flag to Hide
additional
Approvers Button
HIDE_ADD_APPR_BUTTO on the Send for
002 N Approval Screen
Flag to Hide
Requester Selection
from Employee
002 HIDE_REQUESTER_EMPID Master X
Flag to Hide
Requester Selection
from Customized
002 HIDE_REQUESTER_RCODE Receiver Codes
Flag to Hide
Requester Selection
002 HIDE_REQUESTER_SAPID from SAP User X
Maximum Allowed
wait days for the FM:/PTGWFI/
002 MAX_WAIT_DAYS wait workflow 0000000002_TMP005
FM to validate
parking
002 PARK_VALIDATION_FM1 information
Tolerenace % limit
002 PAYASISTOLERANCE for Pay-As-Is 100
Max val Tolerance
for Pay-As-Is
( giveCurr by
placing a “;” - Eg.
002 PAYASIS_MAX_VAL_TOLE 100;USD) 1000000;USD
Search help for
002 SHLP_ON_APPROVER Initial Approver /PTGWFI/SH_APB
VIM070500-03-RGD-EN-1
Code
Function module to
be called to build
short pay
SHORTPAY_BDC_CAN_IN transactions
002 V Cancel/Create Inv
Function module to
be called to build
short pay
transactions for SC/
002 SHORTPAY_BDC_SC_DM DM
Supress -
“Continue with out
workflow” Button
002 SUP_CONT_WO_WF_BUTT on parking screen
Supress “Return to
invoice” Button on
002 SUP_RETN_TO_INV_BUTT parking screen
Wait data Display /PTGWFI/
002 WAIT_DATA_DISP_FM Function Module 0000000002_TMP002
Function module to /PTGWFI/
002 WAIT_DATA_GET_FM get the wait data 0000000002_TMP001
Set to X to activate
all authorization
009 AUTH_CHECK_ACTIVE checks in VIM
For more information, see Section 7.2.3 “Enabling VIM Authorization Checks
Globally” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD) and Section 17.5 “Defining Action Authority Groups for the
VIM Workplace” in OpenText Vendor Invoice Management for SAP Solutions -
EXTEND_RECIPIENT_SEL Set to X to enable <blank>
the new extended
recipient selection
dialog for DP and
invoice exceptions
009 dashboards.
For more information, see the Release Notes of VIM 5.2 SP9.
LIX_PIR_WITEXT_FM Txt maintenance /OPT/
for BIR Workflow BL_IF_DET_REASON_WI_T
009 EXT
VIM070500-03-RGD-EN-1
Chapter 32
Z Constants for Product Code 005

Code
005 5.1.6_WF_TEMPLATE WS00275255
If PO number not
on OCR lines set
easy match=X
(compare with
005 ADD_COST_EASYMATCH plan. del. cost)
ADD_COST_FM Customer specific
function module
for mapping of
005 additional cost
For more information, see Section 9.16.8 “Maintaining a Function Module for
Customer Specific Cost Handling” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM-CGD).
ADD_UNPL_COST_FM Customer specific
function module
for mapping of
005 unplanned cost
For more information, see Section 9.16.9 “Maintaining a Function Module for
Customer Specific Unplanned Cost Matching” in OpenText Vendor Invoice
Process Type for
005 AFTCS_PROCESS_TYPES AFTCS File 141,241
For more information, see Section 15.4 “Z Constants” in OpenText Vendor Invoice
To Allow
calculation for
deriving Amount/
Quantity based on
005 ALLOW_NETPR_CAL Net Price X
This constant is called in form CALCULATION1 or CALCULATION in the FM /
OPT/VIM_LINES_DERIVE_PO to calculate the line item. The FM is used in the
business rule Manual Check Needed for Indexing Lines (PO). To support
tax calculation on net amount, set the constant to X .
Option Id for
Approval
005 APPROVAL_OPTION Workflow 2015
VIM070500-03-RGD-EN-1
Chapter 32 Z Constants for Product Code 005

Code
For more information, see Section 13.5.8.1 “Defining Resubmit for Approval
Action Codes” in OpenText Vendor Invoice Management for SAP Solutions -
URL to show
Configuration
Documentation for
Document
Processing
005 APP_DOCU_URL Application http://www.opentext.com
For more information, see Section 9.14 “Configuring Global Parameters” in
CGD).
If set to 'X', AR
object in
VIM_1HEAD will
be derived from
005 AR_OBJECT_FROM_DP DP doctype
For more information, see Section 9.1.7 “Mapping ArchiveLink Document Types”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
Function module
for customer logic
to determine
005 AR_OBJECT_DETRM_FM archive doc type
Template for this function module is /OPT/VIM_GET_AR_OBJECT_TEMPLT.
(VIM-CGD).
Function module
for customer logic
to trigger
redetermination of
005 AR_OBJECT_TRIG_FM archive doc type
Template for this function module is /OPT/VIM_AR_OBJECT_TRIG_TEMPLT.
(VIM-CGD).
Use Business
Center for SAP
Solutions Inbound
Configuration (X-
005 BC_INBOUND Yes, space -No)
VIM070500-03-RGD-EN-1
Code
Use OpenText™ Business Center for SAP® Solutions Inbound Configuration to
register and pre-process documents.
X = Use Business Center Inbound Configuration.
Values: X = active, <space> = not active
For more information, see Section 16 “ICC Integration” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD) and Section 23.1.1
“Configuring Inbound Processing (InvoiceDetailRequest)” in OpenText Vendor
BDC Id to be called
by Function /OPT/
VIM_PREPOPULA
005 BDC_PARKING_ONLINE TE_MIR7 16
This constant is used in the FM /OPT/VIM_PREPOPULATE_MIR7. The FM is
used in BDC 201 to support PO invoice parking online in a special case with
multiple POs existing in the invoice. The BDC maintained in this constant is used
for the online parking option maintained with BDC 201.
BDC Id to be called
by the function /
OPT/
VIM_PREPOPULA
005 BDC_PARK_ONLINE TE_MIR7 16
This constant is not used.
BDC Id to be called
by Function /OPT/
VIM_PREPOPULA
005 BDC_POSTING_ONLINE TE_MIRO 1
For more information, see Section 9.12.3 “Enhancing MIRO for Pre-population of
Data During Online Invoice Creation” in OpenText Vendor Invoice Management for
Set to ‘X’ to use
VIM data instead
of delivery note
number for Brazil
(in reference
document building
005 BR_NO_GR_REF enhancement).
For more information, see Section 9.12.3 “Enhancing MIRO for Pre-population of
SAP Solutions - Configuration Guide (VIM-CGD). This section describes the steps
that are necessary to keep line item data during online posting.
Usually the PO line data of the DP document is used. For Brazilian invoices, the
reference number is used to retrieve delivery note data and to fill the line items
accordingly. If this Z constant is set to X, the enhancement ignores the Brazilian
specialty and uses the PO line data.
VIM070500-03-RGD-EN-1

Code
Start VIM process
in Central System
always (X=via RFC,
C=direct call,
005 CENTRAL_VIM_PROCESS empty=no)
This constant is related to starting a new DP process in VIM. It indicates whether
the new DP process should always be started in the central system or not. There
are two variants to start the DP workflow in the central system:
X: start via RFC
C: start by direct function call
• Report /OPT/VIM_DP_TRIGGER to trigger a DP process from DP trigger
program.
• Report /OPT/VIM_ICC_ADMIN_TOOL to start a DP process from IDH (ICC)
Admin tool
• Report /OPT/RESTART_DP_FROM_CENTRAL to restart a DP process by
process option
• FM /OPT/C_IDH_VIM_REGISTRATION to trigger a DP process from IDH
trigger program
• FM /OPT/VIM_START_DOC_PROCESS_EXT to start a DP process from an
external process
• FM /OPT/START_DP_WF_FROM_IDOC to start a DP document from IDOC
• For testing purpose (OCR_TEST tool), it is also called in screen 0002 and
0003 in report /OPT/VIM_BL_M1_SUBSCREENS
Check Rules
005 CHECKRULES_OPTION Option 2737
This constant is obsolete.
Checks if Update
Tasks are running
005 CHK_UPD_TSK_IS_ALIVE (when set to 'X') X
VIM070500-03-RGD-EN-1
Code
Description - When running a process option based on a call transaction (posting
or parking), the system checks if the update tasks are running. If not, a message
Update delayed. Please wait. is shown to the user.
Case 1: User is waiting for time out.
Case 2: User aborts the transaction.
--> Result in case 1 and 2: The workflow stays in the current state and can be
continued later.
Case 3: Update task continued or restarted after some time.
--> Result in case 3: The process is continuing, posting or parking is possible.
Logging - If you activate the check, an application log entry (SLG1) is written:
Object: VIM, Subobject: DP, LogPoint 94 (Update Delayed), if any update delay
that is longer than 10 seconds was discovered.
Scope - Activate this function if the system often experiences issues with update
tasks or inconsistencies between posted documents and VIM data. The additional
check improves the stability when posting invoices in dialog in these
environments. However, the check can slightly slow down processing.
Flag (x = manual
change of BRF-
Bypass allowed in
COMPL_ALLOW_M_BYPA Simulation/Bypass
005 SS Popup) X
If set to X, a manual change of activate/bypass is allowed in the DP simulation
screen. For more information, see Section 9.4.3 “Additional Configuration” in
CGD).
Flag (x = no check
type in Simulate
COMPL_HIDE_CHECKTYP Business Rule
005 E Popup)
If set to X, check type information is hidden in the DP simulation screen. For more
information, see Section 9.4.3 “Additional Configuration” in OpenText Vendor
If random number
(0-100) is bigger
than minimum
value run rule
005 COMPL_RANDOM_MIN check 50
VIM070500-03-RGD-EN-1

Code
This central value is used as a lower limit for the Business Rule Framework. If
check type RANDOM is active for a business rule (process type), the SAP random
number generator is called. It returns a value between 0 and 100. If you want
business rules to run very rarely, you have to enter a high value (for example 90).
If you want them to run more often you have to enter a low value (for example
10). For more information, see Section 9.4.3 “Additional Configuration” in
CGD).
Convert Time
Duration into Days
Hours Min Secs
005 CONVERT_DURATION Format X
This constant has been created for VIM 5.1.6 but it is not used.
Customer specific
function module
for Russian
corrective invoice
005 CORR_ITEMS_FM item handling
Logical system for
the CRM system
for SSF integration
005 CRM_LOGICAL_SYSTEM with VIM
Name of the logical system for the SAP CRM system used in the SAP Shared
Service Framework integration scenario. You must maintain this constant to
display the View Service Requests button and the Create Service Request
button in the VIM dashboards and in VIM Analytics.
For more information, see Section 30.2 “Maintaining a Logical System for the
CRM System in VIM” in OpenText Vendor Invoice Management for SAP Solutions -
Installation Guide (VIM-IGD).
User Exit for
CUSTOM_FM_COMPLIAN customer specific
005 CE compliance
User Exit for customer specific Business Rule Framework matching. The template
for this function module is /OPT/VIM_DCMP_EX_MATCH. For more information,
see Section 9.4.3 “Additional Configuration” in OpenText Vendor Invoice
User Exit to
manipulate data
005 CUSTOM_FM_PLUGIN for BAPI Input
For more information, see Section 9.7.2 “Changing BAPI Configuration” in
CGD).
VIM070500-03-RGD-EN-1
Code
User Exit for
customer specific
005 CUSTOM_FM_WHHIDE wht hiding
User Exit for customer specific hiding of withholding tax from indexing screen in
combination with constant WHTAX_FROM_SAP. The template for this function
module is /OPT/VIM_WT_LIMIT_HIDE. For more information, see Section 20
“Extended Withholding Tax” in OpenText Vendor Invoice Management for SAP
User exit for
customer RFC
function to sort
documents for
005 CUSTOM_ICC_EX_SORT extraction
Obsolete, use CUSTOM_ICC_EX_SORT_N
User exit for
customer RFC
function to sort
documents for
005 CUSTOM_ICC_EX_SORT_N extraction
For more information, see Section 16.3.2 “Defining Frequently Used Default
Values” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
User exit for
customer RFC
function for PO
CUSTOM_ICC_PO_DOWNL download from
005 D ICC
Guide (VIM-CGD).
User exit for
customer RFC
function to sort
documents for
005 CUSTOM_ICC_VA_SORT validation
Obsolete, use CUSTOM_ICC_VA_SORT_N
User exit for
customer RFC
function to sort
documents for
005 CUSTOM_ICC_VA_SORT_N validation
Guide (VIM-CGD).
VIM070500-03-RGD-EN-1

Code
Change the MIRO -
proposal data as
per the customer
005 CUSTOM_MIRO_CHANGE requirement
This constant is part of the function module /
OPT/VIM_CHANGE_PROPOSAL_MIRO. During proposal, VIM provides some
baseline information. If you want to add specific data, you can add it in this
function module. See also Section 9.12.3 “Enhancing MIRO for Pre-population of
Display invoice
image on display
of dash board
DASHBOARD_IMAGE_AU screen(X- Yes,
005 TO space -No)
For more information, see Section 9.1.9 “Configuring Automatic Image Display”
(VIM-CGD).
Display no Logo
005 DASHBOARD_NO_LOGO (Dashboard)
For more information, see Section 17.3.2.2 “Enhanced Application” in OpenText
Exit FM to
influence the
dashboard buttons
005 DB_OPTION_SEQ (old index screen)
You can set a custom function to change the sequence of process options in the
dashboard. For the interface of the function, check the Release Notes of VIM 7.0
SP3 or VIM 6.0 SP8.
As this Z constant refers to the old index screen, it is only valid for VIM versions
7.0 and earlier.
Default Archive
005 DEFAULT_AR_OBJECT Document Type /OPT/ICC
If the function module /OPT/VIM_WF_START_EXTERNAL is used to start the
VIM process externally and no valid ArchiveLink document type is handed over,
the document type maintained in this constant is used to create the image link
entry.
Populate default
tax code exit (Ex
FM:/OPT/
VIM_DEFAULT_T
005 DEFAULT_TAXCODE_NPO AXCODE_NPO)
VIM070500-03-RGD-EN-1
Code
This constant is used in FM /OPT/VIM_TAX_CODE_DETERMINE. In this constant,
you can maintain a custom exit function to determine the tax code if this value is
not determined in the tax code determination step. The template delivered in the
baseline is /OPT/VIM_DEFAULT_TAXCODE_NPO.
Populate default
tax code exit (Ex
FM:/OPT/
VIM_DEFAULT_T
005 DEFAULT_TAXCODE_PO AXCODE_PO)
This constant is used in FM /OPT/VIM_TAX_CODE_DETERMINE. In this constant,
you can maintain a custom exit function to determine the tax code if this value is
not determined in the tax code determination step. The template delivered in the
baseline is /OPT/VIM_DEFAULT_TAXCODE_PO.
Delay Document
Confirmation
(number entered is
multplied by 5
005 DELAY_DOC_CONF seconds)
This constant can be used to delay the execution of the “Document confirmation”
task in the DP workflow, to let other parallel processes finish. This reduces the
probability of resource conflicts leading to data inconsistencies. The constant
value will be multiplied by 5 to get the delay duration in seconds.
Delay trigger
Approval
Workflow (number
entered is
multiplied by 5
005 DELAY_IAP_EVENT_CREA seconds) 3
This constant has been introduced to avoid the synchronous update issue when
the approval workflow starts. The constant is called in method Initprocess of
object type /ORS/INVAP. The approval process is delayed by the maintained
amount of time.
Synchronous update issue

There are some VIM tables that must be updated in the process/workflow.
Sometimes they are updated synchronously by several workflows/
processes, which leads to a deadlock.
Delay workflow
following FI event
(number entered is
DELAY_NPO_EVENT_CRE multiplied by 5
005 A seconds) 12
VIM070500-03-RGD-EN-1

Code
This constant is called in FM /OPT/BL_NPO_PRK_RECEIVER to delay starting
workflow WS00275254 for parked NPO invoices. This delay will help to solve
the synchronous update issue, which might lead to short dump or missing data
while updating VIM tables. For more information, see Synchronous update issue
on page 299.
Delay WF
following BUS2081
event (number
entered is
DELAY_PO_EVENT_CREA multplied by 5
005 T seconds) 12
This constant is called in FM /OPT/BL_PO_BLK_RECEIVER to delay starting
workflow WS00275264 for blocked PO invoices. The constant is also called in
FM /OPT/BL_PO_PRK_RECEIVER to delay starting workflow WS00275260 for
parked PO invoices. This delay will help to solve the synchronous update issue,
which might lead to short dump or missing data while updating VIM tables. For
more information, see Synchronous update issue on page 299.
Delay in seconds to
the confirmation
coming from SAP
005 DELAY_SAP_CONFIRM ERP 2
This constant is called in FM /OPT/VIM_CONFIRMATION_BINDING to delay
updating VIM tables. This helps to avoid missing data like status.
Customer specific
function module to
determine partner
005 DET_PARTBANKTYPE_FM bank type
Custom function
module to /OPT/
determine invoice VIM_TEMPLATE_DET_INV
005 DETERMINE_INV_CAT category _CAT
For more information, see Section 15.4 “Z Constants” in OpenText Vendor Invoice
Set to X to disable
additional GR
checks in PO line
determination (BR
005 DISABLE_GR_CHECK 113) X
VIM070500-03-RGD-EN-1
Code
Set this constant value to X if you want to switch off additional GR checks in the
business rule 113, Manual Check Needed / Missing Data for Indexing Lines. This
affects only the new 7.5 business rule, the older business rule with the 7.0 process
type 110 is not affected. In the standard configuration, the business rule checks
whether the invoice quantity on each line item does not exceed the corresponding
GR quantity that is not invoiced yet. For service POs, SES is checked similarly.
Setting the constant value to X disables those checks. The business rule will then
check only if the line items are complete.
This constant has been introduced with VIM 7.5 SP2.
Minimum length of
a delivery note
005 DN_MIN_LEN number 5
This constant is used to exclude dummy delivery note numbers. Some customers
are using dummy delivery note numbers (for example 1) for a lot of invoices.
Such a delivery number cannot be used for line item
determination and performance optimizing, because this number is extremely
ambiguous. If all your delivery numbers, even very short ones, are significant,
you can set this value to 1.
DP Doc type for
Down Payments
005 DOCTYPE_DWN w/o DP workflow DWN_75
Maintain the VIM document type that should be set if a Down Payment is posted
directly from the SAP transaction without going through the regular VIM DP
workflow. This is required because no VIM document type determination takes
place in this case.
DP Doc type for
NON PO when
direct Parking w/o
DP workflow is
005 DOCTYPE_NPO used NPO_75
Maintain the VIM document type that should be set if a Non-PO invoice or credit
memo is posted directly from the SAP transaction without going through the
regular VIM DP workflow. This is required because no VIM document type
determination takes place in this case.
DP Doc type for
PO when direct
Parking/Blocking
w/o DP workflow
005 DOCTYPE_PO is used PO_75
Maintain the VIM document type that should be set if a PO invoice or credit
memo is posted directly from the SAP transaction without going through the
regular VIM DP workflow. This is required because no VIM document type
determination takes place in this case.
Default DP Doc
005 DP_DOC_TYPE type NPO_75
VIM070500-03-RGD-EN-1

Code
Guide (VIM-CGD) and Section 16.5 “Document Type Determination Rules
Engine” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
If set to 'X', DP Doc
type will be
redetermined
DP_DOC_TYPE_REDETRM (before starting DP
005 N workflow) X
For more information, see Section 16.5 “Document Type Determination Rules
Engine” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
OCR Extraction/
Validation is
005 DP_EX_VA_CANCEL Cancel Cancel
Guide (VIM-CGD).
OCR Extraction/
005 DP_EX_VA_ERROR Validation is Error Error
Guide (VIM-CGD).
OCR Extraction/
005 DP_EX_VA_REJECT Validation is Reject Reject
Guide (VIM-CGD).
OCR Extraction/
Validation is
005 DP_EX_VA_SUCCESS Success Ok
Guide (VIM-CGD).
Exit FM to add/
change data in
BAPI structures
(EX:/OPT/
DNONPO_INVOI
005 DP_NPO_POSTING_EXIT CE_BAPI_EXIT)
CGD).
VIM070500-03-RGD-EN-1
Code
Set to X to prevent
from simulating all
rules at DP WF
005 DP_START_NO_ALLRULES start
All business rules are run at the beginning of the DP process to collect the
information for the logging infrastructure. If this is causing performance
problems, to switch off the simulation of all business rules, set this constant value
to X.
Process Code to
control parallel DP
005 DP_SYNC_PROC trigger process X
Guide (VIM-CGD).
Refresh DP Sync
005 DP_SYNC_REFRESH_TAB table X
Guide (VIM-CGD).
005 EDI_CHANNEL_ID EDI Channel ID IDOC
Maintain the channel ID that is used during processing of an incoming IDOC.
EDI visualization/
image archiving
exit (Template: /
OPT/
EDI_IMAGES_EXI
005 EDI_IMAGES_FM T_TEMP)
For more information, see Section 8.7.6.1 “EDI Image Exit Function Module” in
CGD).
Extended IIC:
Function module to
determine object
005 EIIC_DET_OBJ_KEY key
This constant is obsolete since VIM 7.5 because Integrated Invoice Cockpit is
discontinued.
Extended IIC:
Function module to
update customer
005 EIIC_UPD_CUSTFIELDS fields
This constant is obsolete since VIM 7.5 because Integrated Invoice Cockpit is
discontinued.
VIM070500-03-RGD-EN-1

Code
Activate Buttons to
Call PO Line
005 ENABLE_MATCHING_SCR Proposal Screen X
As this Z constant refers to the old indexing screen, it is only valid for VIM
versions 7.0 and earlier.
To Enable Original
005 ENABLE_ORIGINAL_LINE Lines
Activate ESR
005 ESR_CHECK_REQUIRED Number Check
For more information, see “ISR Number Mismatch (PO)” on page 197.
FM Exit to
populate container
in custom rule for
Org Unit based /PTGWFI/
005 EXIT_RULE_RESOLUTION template COA_W_CONT_ELEMENT
You might want to use a custom rule, created in transaction PFAC, and integrate
this rule into VIM. A custom rule is always associated with the custom rule
container. To support the integration of the custom rule, you must implement a
custom function module that populates the value of the custom rule container to
VIM parameters. You must maintain this function module in the Z constant 005 /
EXIT_RULE_RESOLUTION. You can use the function module template /
PTGWFI/COA_W_CONT_ELEMENT for this purpose.
Partner Roles for
PO Vendor. Use
the values from
table view
V_TPAUM which
are not language
005 EXIT_VEND_PARTN_FUNC specific RS,WL
For more information, see “Vendor Mismatch (PO)” on page 207.
Mapping of line
items for custom FM interface: /OPT/
005 EXT_MAP_LINE_ITEM fields VIM_EXT_LINE_MAPPING
You can use this constant to map custom invoice fields or change line item data
before passing it to the tax calculation functions. The constant value must contain
a function module name. The function module interface must be the same as that
of /OPT/VIM_EXT_LINE_MAPPING.
Move PO number
from list / item to
header in case of
005 FAIL_PO_HEADER_SET exception for PO
VIM070500-03-RGD-EN-1
Code
This constant is called in function module /OPT/VIM_DETERMINE_PROC_161,
which is used in the business rule Company code mismatch (PO). When this
constant is set to X and when the exception occurs, the first PO with the
mismatching company code will be returned in the PO number field in the
header structure.
Function module to /OPT/
get the Image file C_GET_ARCHIVED_FILE_E
005 FM_GET_IMG_FILE_EXT extention XT
You can use the function module /OPT/CSEND_EMAIL_NOTIFICATION to send
an email with an attachment to an SRM user. The attachment is an archived
invoice with a certain extension. The function module maintained in Z constant
FM_GET_IMG_FILE_EXT is used to get the file extension of the archived file. The
default function module is /OPT/C_GET_ARCHIVED_FILE_EXT.
Freight Amount
005 FREIGHT_AMOUNT tolerance 4
For more information, see
“Freight on Invoice (PO)”
on page 209.
Vendor Payment
005 GET_VEND_PAYM_BLOCK Block Indicators A,B,P
For more information, see “Invalid Vendor (PO)” on page 182.
FM Exit to verify /OPT/
005 GR_CHECK_EXIT GR is done or not VIM_BL_CHECK_GR_EXIT
CGD).
GR posting -
Movement
type( actual value
or FM to
determine(ex-
005 GR_MOVEMENT_TYPE FM:xxxxxxxx) ) 101
CGD).
Exit in GR post
BDC FM (Ex FM:/
OPT/
DPPO_GR_BAPI_P
005 GR_POST_BAPI_EXIT OST_EXIT)
CGD).
VIM070500-03-RGD-EN-1

Code
GR BDC id & PO
invoice BDC ID
005 GR_PO_POST_BDC_ID (EX: 00037:00006) 00037:00006
The value maintained in this Z constant provides the ID number of the BDC for
creating the GR and the BDC for posting PO invoices in the form
GR_BDC_ID:POST_PO_BDC_ID. The Z constant is called in function module /
OPT/DPPO_GR_INVOICE_BAPI_POST. The corresponding GR BDC is called to
post the GR in background. After the GR is posted successfully, the Post BDC is
called to post the PO invoice in background.
Default value is 00037:00006, that means BDC 37 is used for posting the GR
and BDC 6 is used for posting the PO invoice.
Delay before
sending document
to extraction,
format HHMMSS,
005 ICC_AR_DELAY 000500 = 5 min 0
Guide (VIM-CGD).
005 ICC_CHANNEL_ID ICC Channel ID ICC
For more information, see Section 16.3.3 “Maintaining Channel IDs” in OpenText
Customer specific
function module
for adding
metadata for ICC
005 ICC_METADATA_ADD extraction
For more information, see Section 9.1 “Overview” in OpenText Vendor Invoice
Management for SAP Solutions - Scenario Guide (VIM-CCS).
If set, display limit
value instead of
real length of
queue for
005 ICC_VA_COUNT_LIMIT validation
Guide (VIM-CGD).
Start date to
forward docs with
OCR validation
rejected
005 ICC_VA_RJ_FWD (YYYYMMDD) 20150930
VIM070500-03-RGD-EN-1
Code
For more information, see Section 16.8.2 “Maintaining the Treatment of Existing
Documents” in OpenText Vendor Invoice Management for SAP Solutions -
Archive
DocumentType
Substring to be
watched - for
breakpoints and
005 ICC_WATCHTYPE logs
Specify a string with maximum 10 characters to be found among the first 4
document types of a query. If the string is found, the logs will be written with log
point 96 instead of 95.
Process Code to
control parallel
IDH trigger
005 IDH_SYNC_PROC process X
Do not change this value. Only X is a reasonable setting.
URL to show
Configuration
Documentation for
005 IMG_DOCU_URL IMG http://www.opentext.com
CGD).
Vendor Invoice not
allowed for more
than X number of
005 INVOICE_DAYS_OLD days old 250
For more information, see “Invoice Older Than Allowed (PO)” on page 213 and
“Invoice Older Than Allowed (NPO)” on page 239.
KPA Report:
Thresholds for
“First Pass” - Total
005 KPA_TS_1STPASS_NO #
For more information, see Section 27.11.1 “Constant KPA_TS_1STPASS_NO” in
CGD).
KPA Report:
Thresholds for
“First Pass” -
005 KPA_TS_1STPASS_PERC Percentages
For more information, see Section 27.11.2 “Constant KPA_TS_1STPASS_PERC” in
CGD).
VIM070500-03-RGD-EN-1

Code
KPA Report:
Thresholds for
“Total Liability” -
Amounts for
Blocked
005 KPA_TS_LIAB_AMOUNT1 Documents
For more information, see Section 27.11.3 “Constant KPA_TS_LIAB_AMOUNT1”
(VIM-CGD).
KPA Report:
Thresholds for
Amounts for
005 KPA_TS_LIAB_AMOUNT2 Parked Documents
(VIM-CGD).
KPA Report:
Thresholds for
Amounts for Pre-
005 KPA_TS_LIAB_AMOUNT3 Process Documents
(VIM-CGD).
KPA Report:
Thresholds for
“Processed/In
Process
Documents” - Total
005 KPA_TS_PROCDOCS_NO #
For more information, see Section 27.11.6 “Constant KPA_TS_PROCDOCS_NO”
(VIM-CGD).
KPA Report:
Thresholds for
“Processed/In
Process
Documents” -
005 KPA_TS_PROCDOCS_PERC Percentages
For more information, see Section 27.11.7 “Constant
KPA_TS_PROCDOCS_PERC” in OpenText Vendor Invoice Management for SAP
VIM070500-03-RGD-EN-1
Code
User Exit for KPI
Collection to fill
Customer Specific
005 KPI_COLLECT_CUST_EVT Events
The function module maintained in this Z constant is called in form
get_tsp_and_flags of KPI report /OPT/VR_KPI_COLLECTION. Based on a
customer logic, you can implement a custom mapping of all possible events to
corresponding flags and timestamps.
Functional module
to perform custom
validations on the
line item indexing
005 LINE_FIELD_CHECK_FM screen /OPT/DP_ITEM_EXTN2
You can use the function module maintained in this Z constant to deliver
additional custom logic for validation of line item data of DP invoices in the
indexing screen.
The function module is called in form validate_fields_lines_1200 of the
include file /OPT/LVIM_IDX_UIF01.
The template for the function module is /OPT/DP_ITEM_EXTN2.
Function module to
change the field
display in the item
005 LINE_FIELD_CONFIG_FM indexing screen /OPT/DP_ITEM_EXTN1
Line item data of PO and NPO invoices can be processed before being displayed
in the indexing screen. Here, you can implement additional custom logic in an
exit to manipulate data. This Z constant is provided to support this purpose.
If the exit function module is maintained, it is called in method

MODIFY_ITEM_BY_EXIT of class /OPT/CL_C_IDX_UI_SCREEN.
Main Workflow
Template for
Document
005 MAIN_WF_TEMPLATE Processing WS00275269
CGD) and Section 16.4.1 “Maintaining the Default Workflow Template” in
CGD).
Continue After
005 MAP_ERROR_CONTINUE mapping Error
Set to X to prevent
defaulting the tax
code if it's not
present in the line
005 NO_DEF_LINE_TAXCODE (PO)
VIM070500-03-RGD-EN-1

Code
During the posting of a PO invoice, if there is no tax code present in the line, the
default value of the tax code, coming from the header or the PO, is used. Set this
constant to X to turn off this behavior.
Restrict allowed
number of line
items in
NR_ALLOWED_LINEITEM background
005 S posting. 1000
This constant is introduced with VIM 7.5 SP3 (VIM 7.0 SP7) to restrict the number
of line items for background posting. This constant can avoid that workflows get
stuck due to background posting time outs. If the number of line items exceeds
the customized value, the workflow is sent to the processor and can be posted
manually.
Custom Number
Range Object for
Document
005 NUMBER_RANGE_OBJECT Processing
CGD).
Web Viewer
005 PLUG_IN_OBJECTDISP Customization
This constant provides flexibility in defining which viewer should be used to
show the scanned invoice in the image plugin of the Details pane, for example in
the DP indexing screen. Available values:
<SPACE> (default) or ON
Web Viewer is launched, based on the ArchiveLink standard viewer
configuration, if the ArchiveLink exit for viewers (TOAEX) is active.
Read TOAEX with EXIT_ID = OA_OBJECTDISPLAY_01 AND ACTIVE = X
and use the function module found there (default: /
IXOS/OA_X_OA_OBJECTDISPLAY_01).
OFF
HTML/Native viewer is launched, whether or not the ArchiveLink exit for
viewers (TOAEX) is active.
<Customer function module name>
You can have a custom implementation for the viewer to be launched for the
detail pane. The constant value is considered as the name of a function
module. It is called dynamically. In this case, only check if the function
module exists and do not check TOAEX. The template FM is /
OPT/TMP_WEB_DISP_IMG or /IXOS/OA_X_OA_OBJECTDISPLAY_01.
Note: This is an advanced setting for special requirements.
Package Size for

Purchase Order
005 PO_REC Download 50000
VIM070500-03-RGD-EN-1
Code
Guide (VIM-CGD).
Document Data
Preprocess Exit
005 PREPROCESS_EXIT_FM Function Module
CGD) and Section 16.4.2 “Maintaining the Preprocess Exit” in OpenText Vendor
Set to X to filter
proposal using the
vendor from DP
005 PROPOSAL_ONE_VENDOR document
You may want to restrict the proposal search to only those POs that were created
for the vendor specified in the header data of the DP document. Therefore, set
this constant to X. This may help to improve the performance and prevent
problems caused by limited authorizations (for example empty proposal).
Flag - Comment
necessary for
005 REFER_COM_REQ Referral
This flag controls whether comments are required when referring workitems.
/OPT/
User exit for VIM_NOTIF_USER_EXIT_T
005 REMINDER_USER_EXIT reminder report EMP
CGD).
Reminder mail
005 REM_MAIL_DOCTYPE document type RAW
The format maintained in this constant is used globally for all kind of email
notification, like reminder email notification, approval email notification, and
SRM email notification.
The notification emails can be sent in HTML format with readable formatting and
invoice data presented in the form of HTML tables. To enable this functionality,
you must set this constant to HTM. In the /OPT/VIM_8CX50 transaction, you
must configure the Email Type to be Internet Email.
Reminder mail
formatting exit
005 REM_MAIL_FORMAT_FM function
For more information, see Section 33.4 “Maintaining a Notification Email
Formatting Function Module” in OpenText Vendor Invoice Management for SAP
VIM070500-03-RGD-EN-1

Code
The Process Type
number for which
the required fields
are shown on the
005 REQUIRED_PROC_TYPE screen 138;238
Maintain process types for which mandatory index data header and item fields
should be handled as required input fields during the index screen processing.
Note: This is a table parameter. You can define several lines by specifying
different version numbers ZVER, if one line is not long enough to store all
the values you need.
Option ID to Start
005 RESTART_DP DP Workflow 2014
Maintain the process option that triggers a restart of the VIM document
processing workflow.
Process Type used
in case of RFC
failures when
calling Central
005 RFC_PTYPE_NPO System(NPO) 270
Process Type used
in case of RFC
failures when
calling Central
005 RFC_PTYPE_PO System(PO) 170
Return to Vendor:
Document Type for
Archiving the
005 RTV_AR_OBJECT Vendor mail /OPT/HTM
For more information, see Section 21.7 “Maintaining Email Archiving” in
CGD).
User exit / function
to retrieve Email
for Return to
005 RTV_GET_EMAIL Vendor
For more information, see Section 21.5 “Maintaining the Email Determination
User Exit” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
Return to Vendor:
Standard Text
(SO10) for the mail /OPT/
005 RTV_SIGNATURE_NAME signature VIM_SIGNATURE_RTV
VIM070500-03-RGD-EN-1
Code
For more information, see Section 21.6 “Maintaining the Email Signature” in
CGD).
Prefix for standard
texts used for
005 RTV_TEMPLATE_PREFIX Return to Vendor /OPT/VIM_RTV
For more information, see Section 21.4 “Maintaining Email Templates” in
CGD)
Option Id for
Sending Back to
005 SENDBACK_OPTION Central System 2013
Service Entry
005 SERVICE_ENTRY_BSART Document Type
This constant is obsolete since VIM 7.0 SP3.
Purchase
Document
Category for
005 SERVICE_ENTRY_BSTYP service entry
This constant is obsolete since VIM 7.0 SP3.
not set (Z constant entry is
not delivered in baseline
005 SET_TAX_CALC_FLAG configuration.)
You may need to have the Calculate Tax flag (SAP field BKPF-XMWST) set for
NPO invoices posted in background through baseline BDC 34. Normally this is
not advised but maybe required by your process, for example, for custom reports.
In this case, set this constant to X.
Note: Setting this flag may affect the value calculated for the field Discount
base amount in the posted document. It also may have other side effects.
This constant is introduced with VIM 7.0 SP7 / VIM 7.5 SP3.
If set to 'X', single
line PO will be
matched according
005 SINGLE_LINE_PO_MATCH to setting in BR 109
For more information, see “Unable to Determine PO Line Number (PO)”
on page 186.
If set to 'X', BAPI
posting of OTV
will be possible
without SEPA
005 SKIP_BAPICHECK_SEPA enhancement X
VIM070500-03-RGD-EN-1

Code
This constant is called when an invoice for an One time vendor (OTV) is to be
posted or parked in background.
Set to X to skip the
check of line-based
tax and the error /
005 SKIP_LINETAX_CHECK OPT/VIM_701 108
Starting recent SAP EHPs (or if corresponding OSS notes are implemented), it is
not possible to post NPO invoices in background anymore using BDC ID 34, if
line by line tax determination is used, because VIM does not support assignment
of tax line numbers. The following error is shown: “Line by line tax determination
not supported for background posting”. In case you would like to skip this check
when you are using a user exit to extend the data passed to SAP BAPI and set tax
line numbers yourself, set this constant to X.
Set to X to allow
posting if
VATDATE is used
but cannot be
passed into
005 SKIP_VATDATE_CHECK document
This constant allows to bypass checks relevant for VAT Date in posting functions.
For more information, see Section 9.17.3 “Maintaining Z Constant 005 /
SKIP_VATDATE_CHECK” in OpenText Vendor Invoice Management for SAP
If set to 'N', invoice
items will not be
sync'ed with BSEG
SYNC_ITEM_PARKED_NP after parking
005 O (NPO)
In standard configuration, parked SAP document line item data is written back
into the original DP document. If you want to avoid this data synchronization, set
this constant value to N. In case of any other value, or if the constant is missing in
the constants table, the synchronization will be performed.
items will not be
synced with RSEG
005 SYNC_ITEM_PARKED_PO after parking (PO)
In standard configuration, parked SAP document line item data is written back
items will not be
sync'ed with BSEG
after posting
005 SYNC_ITEM_POSTED_NPO (NPO)
VIM070500-03-RGD-EN-1
Code
In standard configuration, posted SAP document line item data is written back
items will not be
synced with RSEG
005 SYNC_ITEM_POSTED_PO after posting (PO)
In standard configuration, posted SAP document line item data is written back
Process Type to
handle System in
which DP
workflow should
005 SYSTEM_HANDLE_PTYPE be triggered 171
Function module to
read the Image/
005 URL_READ_FM Document URL SCMS_DOC_URL_READ
Guide (VIM-CGD).
Set to X if line item
data has to be sent
into SAP tax
005 USE_ITEMDATA_FOR_TAX calculation <blank>
This constant enables the passing of item data into tax calculation functions. This
may be needed for US company codes for which an external tax system is used.
Set tax item links
according to OSS
005 USE_ITEM_COUNTER Note 1692637
Setting this constant to X enables the use of tax item counters for line-by-line tax
calculation according to SAP OSS Note 1692637.
Validate DP
Document if there
is any mapping
005 VALIDATE_ON_MAP_ERR errors NO
For more information, see Section 16.3.4 “Validating DP Documents with
Mapping Error” in OpenText Vendor Invoice Management for SAP Solutions -
005 VALIDATOR_ROLE Validator Role VALIDATOR
VIM070500-03-RGD-EN-1

Code
For more information, see Section 16.3.5 “Assigning Validation Agents” in
CGD).
Package Size for
005 VEND_REC Vendor Download 50000
Guide (VIM-CGD).
Set to ‘X’ to
transfer indexing
screen wht amount
value to posting. If
empty the wht
amount is
calculated from
WHTAX_AMT_TR wht base amount.
For more information, see Section 20 “Extended Withholding Tax” in OpenText
Set to ‘X’ to hide
extended
withholding tax
data in indexing
screen and to use
SAP values during
005 WHTAX_FROM_SAP posting.
Calculate
withholding tax net
base from gross
amount/tax code (X
= calculate, ' ' = use
005 WHT_CALC_NET header net amount) X
Exit FM for wht
005 WHT_EXIT_BAPI data BAPI transfer
User Exit for customer specific determination whether withholding tax data is
transferred to background posting from VIM or from SAP. The template for this
function module is /OPT/VIM_WT_BAPI_TRANS. For more information, see
Section 20 “Extended Withholding Tax” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide (VIM-CGD).
VIM070500-03-RGD-EN-1
Code
Set to X to post
zero WHT amount
if WHT code is not
005 WHT_POST_ZERO entered X
This constant must be set to X to enable posting some lines of withholding tax
with zero values, even if the value calculated according to customizing is not
zero. To post zero withholding tax amount for a specific withholding tax line, you
need to remove the corresponding withholding tax code in the DP indexing
screen. In this case, the line will still be posted by VIM with withholding tax code,
found using the withholding tax type entry in the respective vendor master
record. However, the tax amount value will be set to zero and the zero flag in
SAP PO BAPI will be set according to the OSS note 1803535. For more
information, see Section 20 “Extended Withholding Tax” in OpenText Vendor
This constant has been introduced with VIM 7.0 SP6.
FM for Dashboard
Workitem Text: /
OPT/ /OPT/
BL_IF_DETERMIN BL_IF_DETERMINE_WI_TE
005 WI_TEXT_FM E_WI_TEXT XT
CGD).
If set to 'X', archive
document id for
XML will be
assigned via RFC
005 XML_AR_ASSIGN_LATE from ICC X
Guide (VIM-CGD).
Content Repository
005 XML_AR_CONTREP for XML Document
Guide (VIM-CGD).
If set to 'X', XML
document in
archive will be
deleted as soon as
005 XML_AR_DELETE_EARLY possible <Empty>
Guide (VIM-CGD).
VIM070500-03-RGD-EN-1

Code
Archive Object for
005 ADDL_DOCS_AR_OBJECT Other attachments /OPT/OTHER
For more information, see “Interface Remote Function 2” on page 22.
Screen for selecting
the DP NPO
DPNPO_APROVER_SELEC Requester/
005 T Approver /ORS/SAPL000007_DP:8000
Screen for selecting
the DP PO
Requester/
005 DPPO_APPROVER_SELECT Approver /ORS/SAPL000007_DP:8000
FM for
manipulating the
item text in the
header - DPPO /OPT/
005 DPPO_BAPI_ITEM_TEXT (BSEG-SGTXT) VIM_BAPI_UE_ITEMTEXT
Standard task for
DP dashboard
005 DP_DASHBOARD_TASKID TS95780003 TS00275257
CGD).
Task number of the
DP_DASHBOARD_TASK_I DP document
005 D dashboard TS00275278
Delimiter for
005 DUP_CHECK_DELIMIT duplicate check /-
CGD).
Function Module
for ESRNR
Number
005 ESR_CHECK_FUNCTION Determination
Starting Position
for finding POR
subscriber number
in ESR Reference
005 ESR_NO_BEGIN_POS Number
Ending Position for
finding POR
subscriber number
in ESR Reference
005 ESR_NO_END_POS Number
VIM070500-03-RGD-EN-1
Code
Function Module
for custom
attachment
IDH_MAIL_ATT_HANDLE handling of
005 R incoming emails
For more information, see Section 8.4.1 “Customizing the Workflow Using the
Email Channel” in OpenText Vendor Invoice Management for SAP Solutions -
Invoice statuses
that need workflow
to be started -
005 LIST_WF_STATUSES VIM5 A
CGD).
DP Non PO
posting - Default
005 NPO_DOCTYPE_DEFAULT document type KR
Default FI document type to use for posting, if not maintained in the DP
document type definition. For more information, see Section 9.1.1 “Creating a
New DP Document Type” in OpenText Vendor Invoice Management for SAP
OCR Currency
005 OCR_CURRENCY_FIELD Field InvoiceCurrency
This constant sets the ICC field name where the currency code is read from. This
must correspond to the ICC application logic.
Siret Number field
on the Vendor
005 VENDOR_SIRET_NO_FLD Master STCD1
For more information, see “Invalid Siret Number (PO) (French)” on page 199.
Field for Tax Code
005 VENDOR_TAX_CD_FIELD in Vendor Master STCD1
This constant is used if the DP document type is set to use the tax code from
vendor master. The field name corresponds to one of the Tax Number N fields in
the Control screen of transaction XK02.
Doc Types to start
the workflow -
005 WFDOCTYPE VIM5 KR,RE,KG
This constant is obsolete, it is no longer used.
VIM070500-03-RGD-EN-1

Code
The plants for
which workflows
will be triggered; *
means all plants. -
005 WFTRGPLANT VIM5 *
CGD).
VIM070500-03-RGD-EN-1
Chapter 33
Z Constants for Product Code IAP

Code
Function Module
for accounting field
IAP ACCT_CHECK_FM status group check
The custom function module maintained in this Z constant can be called in
method VALIDATEACCTDATA of class /ORS/NON_PO_INVOICE_NEW to provide
more validation checks to the accounting data.
This additional check takes place in the approval process.
Bear in mind that the additional check implemented in that way will not be
executed while posting with /OPT/DNONPO_INVOICE_BAPI_POST.
Example: Function Module /ORS/000007_VALIDATE_FSG
The constant has been introduced in VIM 6.0 SP8 / VIM 7.0 SP3.
Flag: Allow passive
substitute to
IAP ALLOW_PAS_SUB approve invoices
If this constant is set to X, the passive substitute is allowed to process the
approval items. The adopting user must be maintained in the COA.
Flag for copying
user to COA-table
with no approval
IAP APPR_USR_COA_COPY limit X
This constant is obsolete with VIM 7.5 and higher because the old COA is no
longer supported.
If this constant is set to X, a manager M can be added to a user A without
maintaining details for the user A in the COA Details tab, which was necessary
when configuring the COA with the logic before VIM 5.2 SP5. Data for the user A
with limit = 1 is automatically created in the COA Details tab.
Set to X for asterisk
in COA to match
IAP AST_ALLOWS_SPACE space <empty>
With this constant, you can choose whether the asterisk will match an empty
invoice field or not.
Without the constant enabled, for lines with empty cost elements, VIM will
propose any existing coding agent to allow the coding process to continue.
With the constant enabled, users that have COA records with asterisks are
excluded from the search. This means, the line is not empty for them anymore
because the asterisk fills the space.
For more details, see Section 5.5.3 “COA Details View” in OpenText Vendor Invoice
VIM070500-03-RGD-EN-1
Chapter 33 Z Constants for Product Code IAP

Code
BDC Function to /ORS/
Be Called to Write 000007_NPO_SAVE_CODIN
IAP BDC_FUNCTION to Database G
For more information, see Section 8.6.4 “Changing BDC IDs” in OpenText Vendor
Invoice Management for SAP Solutions - Scenario Guide (VIM-CCS).
BDC function to be
called to write to /ORS/
IAP BDC_FUNCTION_PO database 000007_PO_SAVE_CODING
This constant sets the function module that will be used to save parked PO
invoice accounting information.
Bulk approval/
reject invoice
validation (Ex
FM: /ORS/
AINV_BULK_VAL
IAP BULK_VALIDATE_EXIT IDATE_INV)
For more information, see Section 13.12.5 “Configuring the Bulk Approval
Validation Exit” in OpenText Vendor Invoice Management for SAP Solutions -
Calculate tax on
net amount option
for DP approval
IAP CALC_TAX_ON_NET ('X' or ' ' or 'D')
For more information, see Section 13.5.8.4 “Configuring Tax Calculation on Net
Amount” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
Standard Text
Object to appear as
Approval Certify
Message on Web
IAP CERTIFY_MESSAGE screen ZCERTIFY
For more information, see Section 13.5.11 “Configuring the Certify Message” in
CGD).
Check SAP user
validity in COA
IAP CHECK_SAP_USER maintenance
If this constant is not set to X in table /PTGWFI/Z_CONST (or if it does not exist in
the table), the SAP user validity in COA is not checked. To enable the checks, set
the constant value to X.
Check if the
^TXJDC is to be
validated against
IAP CHECK_TXJCD the Cost Object X
VIM070500-03-RGD-EN-1
Code
Set this constant to X if you want VIM to compare the tax jurisdiction code
entered manually in the line item with the code retrieved from the account
assignment object. If they are not the same, the standard message F5 532 will be
displayed as a warning.
Extended COA line
check for next
approver
determination ('' =
IAP COA_LINE_CHECK_EXT off, 'X' = on)
This constant is obsolete with VIM 7.5 and higher because the old COA is no
longer supported.
If this constant is set to X, all approval lines are checked against the COA.
Otherwise only the first approval line is checked against the COA.
Display invoice
image on display
of dashboard
DASHBOARD_IMAGE_AU screen (X- Yes,
IAP TO space -No) X
If this constant is set to X, the archived image of the invoice is automatically
displayed in a separate screen when the Approval Dashboard is called in the SAP
GUI. Make sure that there is an SAP instance available to display the image,
otherwise an error message is displayed in the status bar.
A user parameter /OPT/DISP_IMAGE_AUTO is introduced. It allows each user to

switch off the auto image displaying functionality individually. If the parameter
is set to N for the user in consideration, the image displaying functionality will be
deactivated globally, not only for the Approval Dashboard, but also for other
dashboards like Indexing, Parked, or Blocked dashboard.
IAP DASHBOARD_NO_LOGO Display no Logo
If this constant is set to X, the logo is hidden in the Approval dashboard.
UserExit: Display
IAP DISP_INV_IMAGE Invoice Image
This constant can be maintained with a custom FM to display the invoice image
when a user clicks the View Invoice Image button in the Approval Dashboard. If
not maintained, the baseline FM /ORS/000007_DISPLAY_FILES is called to
display the image.
DP Invoice
approval - Is
validation required
DP_APPROVAL_VALIDAT or not, when data
IAP E is saved?(X- No) X
Set this constant to X to skip the validation in the Approval Dashboard while
performing actions like Save, Forward, Reject, or Return to Inbox. If this constant
is not set, the validation will always be carried out for all actions taken in the
Approval Dashboard.
VIM070500-03-RGD-EN-1

Code
FM Exit for
calculating all.
Called in FM /ORS/
000007_CALCULA
IAP EXIT_CALCULATE_ALL TE_ALL
When maintained, the custom FM will be called in FM /
ORS/000007_CALCULATE_ALL to handle some values like balance, returned
messages according to the customer needs.
The template of the exit FM is /ORS/EXIT_CALCULATE_ALL.
FM Exit for
filtering BAPI
messages - used in
FM /ORS/
000007_FILTER_B
IAP EXIT_FILTER_APPR_MSG API_MSG
When maintained, the custom FM will be called in FM /
ORS/000007_FILTER_BAPI_MSG to filter out messages as required by
customer.
The template for this user exit is FM /ORS/C_EXIT_FILTER_BAPI_MSG.
Search help user /ORS/
exit with Pre-filled SEARCH_HELP_FIELDS_PR
IAP EXIT_SEARCH_HELP_FLT values EFIL
For more information, see Section 12.2 “Configuring Search Helps with Pre-filled
Values” in OpenText Vendor Invoice Management for SAP Solutions - Administration
Guide (VIM-AGD).
Extension for
IAP EXT_DATA_CLASS Ext_data_class /ORS/EXT_DATA
Get TXJCD from
Company Code
IAP GET_TXJCD_BUKRS Table: T001 X
If this constant is set to X or does not exist in the customizing table, VIM will
retrieve the tax jurisdiction code from the company code data and use it for line
item. Set the constant to blank if you do not want the tax jurisdiction code to be
overwritten with the one from company code.
Get TXJCD from
Vendor Master
IAP GET_TXJCD_LFA1 Table: LFA1 X
If this constant is set to X or does not exist in the customizing table, VIM will
retrieve the tax jurisdiction code from the vendor master data and use it for line
item. Set the constant to blank if you do not want the tax jurisdiction code to be
overwritten with the one from vendor master.
Override Coding
IAP GL_ACC_SCR_EXIT Fileds attributes
VIM070500-03-RGD-EN-1
Code
Evaluation Path
IAP HR_EVALUATION_PATH Maintenance
In the function module /PTGWFI/GET_USERS_OF_ORG_UNIT, the evaluation
path SAP_TAGT is passed by default into the FM
HRWPC_STRUC_GET_MULTIPLE_ROOTS. So you cannot pass your own
evaluation path.
Using this constant, you can define your own evaluation path and pass it into the
FM. You can create the user-defined function module using the template /
OPT/HR_EVALUATION_PATH.
Set to X to enable
multiple account
assignment
IAP MULTI_ACCT_ASSIGN elements in COA
Setting this constant to X enables the use of multiple cost elements for a COA line
and makes the authority checks logic similar to VIM 5.2 and 6.0. For more
information, see Section 5.5 “Maintaining Chart of Authority” in OpenText Vendor
Data validation
required during
coding for parked
PARK_CODE_VALIDATIO doc(X-yes,space -
IAP N No) X
When this Z constant is set, the data validation is executed before the data of a
parked invoice is saved or approved. This constant is checked in the function
modules /ORS/000007_NPO_SAVE_CODING and /
ORS/000007_NPO_SAVE_CODING2.
PO park approval -
Accounting data
editable or not (X-
Editable, Space -
IAP POPARK_APPR_ACCTEDIT no) X
When this Z constant is set, the accounting data of PO parked invoices is editable
in the approval screen. Otherwise it is not editable.
Indicator, if set ->
Maintaining
PORTAL_NOTMAINT_SUB Substitute in Portal
IAP S is not allowed
The Substitute maintenance on OpenText Approval Portal can be disabled from
ABAP side. Therefore, you must maintain the Z constant
PORTAL_NOTMAINT_SUBS and set the constant value to X.
Enable PO Lines
IAP PO_ACC_SCR_EXIT for coding
VIM070500-03-RGD-EN-1

Code
This constant enables coding for PO lines in the OpenText Approval Portal and in
the Invoice Approval in SAP GUI. You can implement your own logic. Enter the
name of your custom function module in the constant value.
Number of days to
wait for the Referee
to provide
IAP REFERRAL_WAIT_TIME information 10
For more information, see Section 13.5.8.3 “Configuring the Referral Wait Time”
(VIM-CGD).
Enable the display
of DP comments in
appr.log: D=detail
only, I=detail and
IAP SHOW_DP_COMMENTS inbox <blank>
To enable the display of the DP comments together with the approval comments
(in the Approval Portal only), set the new constant value to D or I.
If it is sufficient to display the DP comments of the approval history in the invoice

detail page only, set the constant value to D. OpenText recommends this value.
If it is necessary to display the DP comments also in the invoice list page

(“Inbox”), set the constant value to I.
Note: Setting the constant value to I may result in longer load times of the
invoice list.
If set to 'X',
accounting data
will not be
validated in
Coding / Approval
by simulating the
IAP SKIP_BAPICHECK posting with BAPI. X
For more information, see Section 13.9.4.1 “Activating and Deactivating Approval
Validation” in OpenText Vendor Invoice Management for SAP Solutions -
Subscreen Number
for Usermap
Maintenance
IAP UMUTIL_SUBDYNP Utility 100
The subscreen maintained in this Z constant is used as the initial screen when
calling the Reassignment Utility (transaction /ORS/UMREASSIGNED). See Z
constant UMUTIL_SUBPROG.
VIM070500-03-RGD-EN-1
Code
Subscreen Program
for Usermap
Maintenance /ORS/
IAP UMUTIL_SUBPROG Utility 0000007_UMUTIL_DYNP
The program maintained in this Z constant in conjunction with Z constant
UMUTIL_SUBDYNP determines which initial screen is triggered when calling
the Reassignment Utility (transaction /ORS/UMREASSIGNED).
Approval
Workflow Task
IAP APPROVAL_TASK Number TS00275253
For this constant value, maintain the name of the dialog task in the approval
workflow. Used, for example, in the reminder program to search for open
approval tasks.
Approval
Workflow
IAP APPROVAL_WORKFLOW Template Number WS00275252
For this constant value, maintain the name of the approval workflow template.
Whenever an approval workflow instance needs to be created, VIM will use the
provided template name. The workflow container values are populated according
to the needs of standard template WS00275252.
APPROVAL_WORKFLOW_ Approval
PA Workflow
Template Number
(SubWF LBA
integration)
IAP WS00275253 WS00275253
This is an internal parameter, which is used in the approval workflow. Do not
change this parameter.
Approver Class /OPT/
IAP APPROVER_CLASS Extension CL_IAP_APPROVER_BL
This constant is obsolete because simple approval is no longer supported with
VIM 7.5 and higher.
Function module to
determine if
comments are
required after
IAP APPR_COMMENT_NEED Approval/Rejection
Name of the function module to be called to decide if comments are required on
approval. See the function /ORS/COMMENT_REQUIRED for interface and logic
example.
IAP CODER_DEFAULT Coder default XXX X
This constant is not used anymore.
VIM070500-03-RGD-EN-1

Code
R=by requester ID;
C=by company
code; B=by both R
and C; S=use
IAP CODER_DETERMING requester R
VIM 7.5 and higher.
Doc types for
Credit Memos
CREDIT_MEMO_DOC_TYP (Separated by
IAP E comma) KG
List of SAP FI document types that correspond to credit memos. This is used in
invoice data reading modules to decide on further processing logic.
Set in user
preference table. REF_DOC_NO,RECEIPT_D
Default fields to be ATE,VENDOR_NAME,ORT
shown on the 01,DUE_DATE,INVOICE_A
IAP DEFAULT_INV_LIST invoice list. MT,CURRENCY
Configure the
message to be
display when no
coding is entered
IAP EMPTY_CODING_MSG (Validateacctdata) CHECK_SP:ERROR
For more information, see Section 13.9.3 “Optional Coding” in OpenText Vendor
Exit function for
IAP EXIT_INVOICE_ACTION Invoice Action /OPT/OAP_EXIT_ACTION
For more information, see Section 13.5.12.3 “Configuring Exits” in OpenText
Exit function for
IAP EXIT_INVOICE_DETAIL Invoice Detail /OPT/OAP_EXIT_DETAIL
Exit function for
IAP EXIT_INVOICE_LIST Invoice List /OPT/OAP_EXIT_LIST
Extended Ext_data
Class /ors/ext_data
IAP EXT_DATA_CLASS when not extension /ORS/EXT_DATA
VIM070500-03-RGD-EN-1
Code
Ext IE RPT -
Loading data in
Class /ORS/
APPR_LOG_OBJE 000007_5_IE_RPT_APPR_LO
IAP EXT_IE_RPT_APPR_LOG CT G
Function module that is called during approval steps to update VIM Analytics
data tables with the information about performed actions. This constant is for
internal use. It was created for VIM versions when VIM Analytics was an
optional component. Normally, do not change it from its standard value.
Ext IE RPT -
Loading data in
Business Object /ORS/
IAP EXT_IE_RPT_INVAP Type INVAP 000007_5_IE_RPT_INVAP
Function module that is called for each approval step to update VIM Analytics
data tables with the current approver information. This constant is for internal
use. It was created for VIM versions when VIM Analytics was an optional
component. Normally, do not change it from its standard value.
Ext IE RPT -
Loading data in /ORS/
Prog. 000007_5_IE_RPT_LIX_BIND
IAP EXT_IE_RPT_LIX_BIND LIX_PSS_BIND_O 1
Function module that is called at the end of the PO approval workflow to update
VIM Analytics data tables. This constant is for internal use. It was created for VIM
versions when VIM Analytics was an optional component. Normally, do not
change it from its standard value.
Ext IE RPT -
Loading data in /ORS/
Prog. 000007_5_IE_RPT_PIR_BIND
IAP EXT_IE_RPT_PIR_BIND PIR_PSS_BIND_O 1
Function module that is called at the end of the Non-PO approval workflow to
update VIM Analytics data tables. This constant is for internal use. It was created
for VIM versions when VIM Analytics was an optional component. Normally, do
not change it from its standard value.
/ORS/
Image Delete URL 000007_TMP_IMAGE_DEL_
IAP IMAGE_DEL_URL_FM FM URL
/ORS/
Image Display 000007_TMP_IMAGE_DISP_
IAP IMAGE_DIS_JPG_FM JPEG generate FM JPG
For more information, see Section 13.12.1 “Configuring Image Display” in
CGD).
VIM070500-03-RGD-EN-1

Code
/ORS/
Image Display 000007_TMP_IMAGE_DISP_
IAP IMAGE_DIS_URL_FM URL generate FM URL
For more information, see Section 13.12.1 “Configuring Image Display” in
CGD).
Network
implementation
system: NET=.Net;
IAP IMPLEMENTATION_SYS EP6=EP6 EP6
This constant value must remain EP6 at all times. The value NET was used in
older VIM versions.
Supported
IAP LANGUAGE language E,D,F,S,P,N,J,I
For more information, see Section 13.5.8.2 “Defining Supported Currency and
Language” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD) and Section 12.3.2 “Configuring Additional
Languages” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD).
Seconds that
invoice lock will be
valid (Called from
object /ors/
IAP LOCK_DURATION invoice_lock) 1800
Set the life time of the invoice lock, to prevent processing of the same invoice by
multiple users. Standard value is 1800 seconds. Values less than 300 seconds are
ignored, a minimum of 300 is forced in such cases.
Extended Non PO
Invoice Class
(Called in
Approval =>
GET_NPO_INV_C /ORS/
IAP NPO_INV_CLASS LASS) NON_PO_INVOICE_NEW
VIM 7.5 and higher.
E=email ID;
S=sequence #;
N=.NET ID and
IAP OPTUSERID_DETERMING Domain; P=EP6 ID E
VIM070500-03-RGD-EN-1
Code
When you add a new user in the User Details tab in the COA, the OpenText User
ID is determined. This constant specifies how the OpenText User ID is
determined. Possible values:
E: by Email
S: by Sequence where the sequence number should be generated from the defined
number range (/ORS/USRMP)
N: by .Net ID and Domain
P: by EP6 ID
Popup window to
display company
code selection for /ORS/
cross company 000007_POPUP_COMPANY
IAP POPUP_COMPANY_CODE invoice approve _CODE
For more information, see Section 13.5.9 “Cross Company Coding” in OpenText
Extended PO
Invoice Class
(Called in
Approval =>
GET_PO_INV_CL
IAP PO_INV_CLASS ASS) /ORS/PO_INVOICE_NEW
VIM 7.5 and higher.
/ORS/
Class: Processed By INVOICE_PROCESSED_BY
IAP PRC_BYME_CLASS ME ME
Class: Non PO
Invoice Proc for /ORS/
IAP PRC_BYME_CLASS_NPO Processed By ME NON_PO_INVOICE_PROC
Class: PO Invoice
Proc for Processed
IAP PRC_BYME_CLASS_PO By ME /ORS/PO_INVOICE_PROC
2 fields: rejection
rsn ; comments( 1 =
mandatory and 0 =
IAP REJECTION_REASON optional) 0;1
For more information, see Section 13.5.7 “Defining Rejection Reasons” in
CGD).
IAP SAP_PROXY_ID SAP proxy ID WF-BATCH
This constant sets the SAP user ID to which the dialog approval task is sent if the
next approver does not have an SAP user ID.
VIM070500-03-RGD-EN-1

Code
Actions for Submit
for Approval (used
in TCode binding 8701,8601,8602,8603,8604;202
IAP SUBMIT_ACTION_CODE function exit) 7;2028;
For more information, see Section 13.5.8.1 “Defining Resubmit for Approval
Action Codes” in OpenText Vendor Invoice Management for SAP Solutions -
Transaction can be
called from the
Substitution
Maintenance APB Maintenance:/ORS/
IAP TRANSCODE_ON_SUBST Transaction 7_2_APB
/OPT/
IAP USERMAP_CLASS CL_IAP_USERMAP_BL
VIM 7.5 and higher.
Determine how
user map table to
be maintained by
IAP USERMAP_DATA_SOURCE Data Source 1
Determine how
user map table
should be
IAP USERMAP_MODIFY maintained 3
Determine how
user map table to
be maintained by
IAP USERMAP_WEB_ID Web ID 3
VIM070500-03-RGD-EN-1
Chapter 34
Z Constants for Product Code IEA

Code
PAI exit in Log
IEA PAI_EXIT_9204_CIV Screen (9204) LIV /ORS/IEA_9204_PAI_EXIT
It is possible to display all log entries of the pre-processes in the SAP GUI
approval/coding screen of NPO invoices. Use the exit function modules
maintained in PAI_EXIT_9204_CIV and PBO_EXIT_9204_CIV.
PAI exit in Log
IEA PAI_EXIT_9204_LIV Screen (9204) LIV /ORS/IEA_9204_PAI_EXIT
approval/coding screen of PO invoices. Use the exit function modules maintained
in PBO_EXIT_9204_LIV and PAI_EXIT_9204_LIV.
PBO exit in Log
IEA PBO_EXIT_9204_CIV Screen (9204) CIV /ORS/IEA_TEMP_LOG
approval/coding screen of NPO invoices. Use the exit function modules
maintained in PAI_EXIT_9204_CIV and PBO_EXIT_9204_CIV.
PBO exit in Log
IEA PBO_EXIT_9204_LIV Screen (9204) LIV /ORS/IEA_TEMP_LOG
approval/coding screen of PO invoices. Use the exit function modules maintained
in PBO_EXIT_9204_LIV and PAI_EXIT_9204_LIV.
Unified Dashboard
(CIV) subscreen
program for /PTGWFI/
IEA UDB_SUBSCRN_PROG_CIV invoice info. IEA_SUBSCREEN_PROG
Program used for displaying the unified dashboard for CIV (NPO parked or
posted) invoice
Unified Dashboard
(DP) subscreen
IEA UDB_SUBSCRN_PROG_DP invoice info IEA_SUBSCREEN_PROG
Program used for displaying the unified dashboard for DP (NPO or PO) invoice
Unified Dashboard
(LIV) subscreen
IEA UDB_SUBSCRN_PROG_LIV invoice info. IEA_SUBSCREEN_PROG
VIM070500-03-RGD-EN-1
Chapter 34 Z Constants for Product Code IEA

Code
Program used for displaying the unified dashboard for LIV (PO parked or
posted) invoice
Unified Dashboard
(CIV) subscreen
number for invoice
IEA UDB_SUBSCRN_SCRN_CIV info. 9002
Screen used for displaying the unified dashboard for CIV (NPO parked or
posted) invoice
Unified Dashboard
(DP) subscreen
number for invoice
IEA UDB_SUBSCRN_SCRN_DP info. 9003
Screen used for displaying the unified dashboard for DP (NPO or PO) invoice
Unified Dashboard
(LIV) subscreen
number for invoice
IEA UDB_SUBSCRN_SCRN_LIV info. 9001
Screen used for displaying the unified dashboard for LIV (PO parked or posted)
invoice
VIM070500-03-RGD-EN-1
Chapter 35
Z Constants for Product Code IEM

Code
PO document field
for Parked Invoice
in table /PTGWFI/
IEM EBELN M_PRKMTR EBELN
UserExit for /
PTGWFI/
IE_MONITOR_NE
IEM PAI W /ORS/IEM_RPT_EXIT_PAI
This constant is obsolete with VIM 7.5 SP1 and higher because the old VIM
Analytics is no longer supported.
UserExit for /
PTGWFI/
IE_MONITOR_NE
IEM PBO W /ORS/IEM_RPT_EXIT_PBO
Constant for
determining due
IEM CALCULATE_DUEDATE date FM
This constant is not used.
FM for currency
IEM CURRENCY_CONVERSION conversion
data f mode: space
= joint selection X =
using function
IEM DATA_FETCH_MODE modules
IEM DISPLAY_LOGO Logo image name /PTGWFI/DCHENLOGO
/PTGWFI/
FM for Reading SWW_WI_LIST_ARCH_REA
IEM FETCH_ARCHIVE_FM Archive DATA D
FM for Reading
CIV PARK - /PTGWFI/
POSTED PARK IEM_DATA_CIV_PARK_JOI
IEM FETCH_DATA_CIVP_FM DATA N
Not in use
VIM070500-03-RGD-EN-1
Chapter 35 Z Constants for Product Code IEM

Code
/PTGWFI/
FM for Reading IEM_DATA_LIV_BLOC_JOI
IEM FETCH_DATA_LIVB_FM LIV BLOCK DATA N
Not in use
/PTGWFI/
FM for Reading IEM_DATA_LIV_PARK_IN
IEM FETCH_DATA_LIVP_FM LIV PARK DATA TL
Not in use
FM for Reading
WF DATA - CIV /PTGWFI/
IEM FETCH_DATA_WF_CIVP Park IEM_DATA_WF_CIVP
Not in use
FM for Reading
WF DATA - LIV /PTGWFI/
IEM FETCH_DATA_WF_LIVB Block IEM_DATA_WF_LIVB
Not in use
FM for Reading
WF DATA - LIV /PTGWFI/
IEM FETCH_DATA_WF_LIVP Park IEM_DATA_WF_LIVP
Not in use
Tran code used to
display blocked
CIV invoice during
drilldown
IEM INVOICE_DISPLAY_BIR reporting MR03
Tran code used to
display all LIV
invoices during
drilldown
IEM INVOICE_DISPLAY_LIV reporting MIR4
Tran code used to
display parked CIV
invoice during
drilldown
IEM INVOICE_DISPLAY_PIR reporting FBV3
range break
IEM RANGE_ENDURANCE endurance 750
FM to be used to
update /PTGWFI/
IEM_DCVW and / /PTGWFI/
PTGWFI/ IEM_008_UPDATE_RESOLV
IEM REPORT_TABLE_UPDATE IEM_WFVW tables E
VIM070500-03-RGD-EN-1
Chapter 36
Z Constants for Product Code KPI

Code
KPI CURR_CONVERSION_DAT Time for Currency F
E Conversion (T =
Today, P = Posting
Date, F = Fix day)
For more information, see Section 25.4.10.1 “Currency Conversion Date” in
CGD).
KPI CURR_CONVERSION_DAY Only used if 101
CURR_CONVERSI
ON_DATE = F, Fix
Day for
Curr.Convers.
(MMDD)
For more information, see Section 25.4.10.2 “Currency Conversion Day” in
CGD).
KPI DASHBOARD_HELP_URL Help URL for the
KPI Dashboard
For more information, see Section 25.4.10.3 “KPI Dashboard Help URL” in
CGD).
KPI DASHBOARD_START_URL Maintain URL up http://<server>:<port>/sap/
to 80 characters. If bc/webdynpro/opt/
> 80 characters, vim_kpi_main
then Value as
(FM:Custom FM)
For more information, see Section 25.4.10.5 “KPI Dashboard Start URL” in
CGD).
KPI DO_NOT_CHECK_BUKRS If set to 'X' the
company code is
not checked for
authorization.
Otherwise yes.
For more information, see Section 25.4.10.6 “Company Code Authority Check” in
CGD).
KPI FAVORITE_CURRENCY Favorite Currency EUR
VIM070500-03-RGD-EN-1
Chapter 36 Z Constants for Product Code KPI

Code
For more information, see Section 25.4.6.2 “Maintaining Amount Classes” in
CGD) and Section 25.4.10.7 “Favorite Currency” in OpenText Vendor Invoice
KPI FILTER_START_PERIOD Define the Start 201202
Period of the Filter
Options on the
Web Dashboard
For more information, see Section 25.4.10.8 “Filter Start Period” in OpenText
KPI KPI_VENDOR_CLASS Use KPI specific
vendor
classification (X = /
OPT/
KAGR_C_VNDP /
empty = LFM1)
For more information, see Section 25.4.5.2 “Mapping Vendor Groups” in
CGD) and Section 25.4.10.9 “Vendor Class” in OpenText Vendor Invoice
KPI MULTI_LANGU_HELP_UR if set to 'X' the Help
L URL supports
multi language by
adding parameter
sy-langu.
For more information, see Section 25.4.10.4 “KPI Dashboard Help URL with
Multi-language Support” in OpenText Vendor Invoice Management for SAP Solutions
- Configuration Guide (VIM-CGD).
VIM070500-03-RGD-EN-1
Chapter 37
Z Constants for Product Code LIX

Code
If set to X, only
items with same
blk.reason can be
ended on hdr level
LIX AUTH_SAME_BLKREASON decision.
Area: VIM Blocked PO invoice workflows (line item level)
You may want to apply the same “Authorize”-type action to all line level
workflows of a blocked invoice. You also may want the action to apply only to
the other workflows with the same payment block as that of the current work
item. (Previously, up to and including VIM 5.2 SP10, all other workflows would
be cancelled and the header workflow started if you confirmed the corresponding
dialog question.)
If you need the workflows with other payment blocks to remain active, set the
constant value to X. The default configuration delivered with VIM will have the
old logic of cancelling all line level workflows of the invoice (the constant value is
blank).
Display invoice
image on display
of dash board
LIX TO space -No)
For more information, see Section 10.3.12 “Configuring Automatic Image
Display” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
LIX DASHBOARD_NO_LOGO Display no Logo
If this constant is set to X, the logo is hidden in the parking and blocking
dashboard for PO invoices.
Exit FM to
influence the
LIX DB_OPTION_SEQ dashboard buttons
SP3 or VIM 6.0 SP8.
Use old Delete and
Re-enter sequence
(duplicate error): 1.
LIX DELETE_ENTER_OLD Delete, 2. Re-enter
VIM070500-03-RGD-EN-1
Chapter 37 Z Constants for Product Code LIX

Code
FM to select
distributed account
assignment data
LIX PO_MULTIK_FM for item
LIX SRM_PO_CHECK SRM PO Check
For more information, see “Confirmation Required from SRM (PO)” on page 212
and Section 29.2 “Determining Purchase Order Types” in OpenText Vendor Invoice
SRM- Mail
configuration ID
LIX SRM_QTY_BLK_MAIL_CID for Qunatity Block 2
For more information, see Section 29.3.2 “Quantity Discrepancy Scenario” in
CGD).
WF relevant
LIX WFDOCTYPE document types *
This constant is used in the receiver function modules, for example the block
receiver (/OPT/VIM_RPT_PO_INV_RECEIVER), the post receiver, or the park
receiver.
According to the configured SAP document type, it is checked against the
document type of RBKP (for example, in case of PO, in /
OPT/VIM_RPT_PO_INV_RECEIVER) if the routine to update data in VAN
should be executed.
In very old VIM versions (before SAP reselling), VAN was an extra component
that customers had to pay for. Hence there was an option to configure when VAN
should be updated or used according to the SAP document type.
Possible values are SAP document types, for example KR, RE, or KG. VIM baseline
always sets this value to * because there are other options to decide how VIM
should be triggered and used.
Active plants (WF
LIX WFTRGPLANT relevant) *
Workitem Text
crreation FM (Refer
FM: /OPT/
BL_IF_SET_WI_TE
LIX WI_TEXT_FM XT)
FM to determine /PTGWFI/
the Approver for PRK_M_TMP_GET_APPRO
LIX APPROVER_GET_FM Parked Document VER
BDC function
module for PO /ORS/
LIX BDC_FUNCTION invoice saving. 000007_PO_SAVE_CODING
VIM070500-03-RGD-EN-1
Code
Function module
exit for processing
block reasons in
invoice verification /PTGWFI/
LIX BLK_REASON_EXIT_FM subwf LIX_F_UPD_BLK_REASONS
Function module
exit or fixed rule
for moving cash
LIX CHECK_CASH_DISC_RULE discount date
Option for
changing Parking
LIX CHG_PARK_RSN_OPTION reason 2025
FM to create
invoice in case of
Delete/Cancel and /PTGWFI/
LIX CREATE_PO_BDC_FM Re-enter option VIM_CRE_PO_INV
For more information, see Section 10.3.14 “Configuring Populating Screens for
Re-enter Options” in OpenText Vendor Invoice Management for SAP Solutions -
FM exit in the
Binding FM for the
DB step - at the
time of Inward
LIX DB_BIND_EXIT_FM1 binding
For more information, see Section 11.3.5 “Configuring Header Level Dashboard
Binding Exits” in OpenText Vendor Invoice Management for SAP Solutions -
FM exit in the
Binding FM for the
Dashboard step - at
the time of
LIX DB_BIND_EXIT_FM2 outward bindin
For more information, see Section 11.3.5 “Configuring Header Level Dashboard
Binding Exits” in OpenText Vendor Invoice Management for SAP Solutions -
FM exit in the LIX
DB step int he BD
method when
Sendback is done
LIX DB_SNDBACK_EXIT successfully
For more information, see Section 11.3.6 “Configuring the Send Back
Functionality Exit” in OpenText Vendor Invoice Management for SAP Solutions -
VIM070500-03-RGD-EN-1

Code
Execute
Transaction Code
in LIX Header
Level Worklfow
LIX HD_EXECTCODE_TASKID Task ID TS98600021
Header Level
HEADERLEVELWORKFLO Workflow ID
LIX W WS99680014 WS00275266
LIX IMAGE_DISP_FM display Image LIX_F_TMP_DISP_IMG
For more information, see Section 10.3.11 “Configuring the Image Display
Function” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
Inventory
INVENTORY_ACCT_ASSG Assignment
LIX M Category
Invoice Verification
LIX INVVERIFYSUBWF Sub Workflow WS98600120
Line Item Level
Workflow
LINEITEMLEVLWORKFLO IDWS98600023 /
LIX W WS99680013 WS00275264
Invoice statuses
that need workflow
LIX LIST_WF_STATUSES to be started 5;
FI Doctypes that
are the follow-up
docs for Logistic
Invoices (separated
LIX LIV_FI_DOC_TYPES by '; ) RE
LIV Line Item
Workflow Task ID
WS98600023/
LIX LIV_LINE_WF WS99680013 WS00275264
LIX Header Level
Dash Board Task
LIX LIXDASHBOARD_TASKID ID TS00275267
Subscreen program /PTGWFI/
LIX LIXDBPROG for LIV Dashboard M_LIXDB_SUBSCREEN02
For more information, see Section 11.3.1.2 “Header Level” in OpenText Vendor
Subscreen for LIV
LIX LIXDBSCREEN Dashboard 9902
VIM070500-03-RGD-EN-1
Code
For more information, see Section 11.3.1.2 “Header Level” in OpenText Vendor
Subscreen program
for Logistic Invoice /PTGWFI/
LIX LIXPROG Resolution M_LIX_SUBSCREEN02
For more information, see Section 11.3.1.1 “Line Level” in OpenText Vendor Invoice
Subscreen for
Logistic Invoice
LIX LIXSCREEN Resolution 9902
Currency
conversion(I=Invoi
ce, P=PO , L=Local,
N=None)
(1=button, 0=no
LIX LIXSCREEN_CURR_CONV button) N0
Returns subscreen
screen number for
PSS ( FM:) for FM FM:/ORS/
or can be direct LIX_T_GET_EXIT_SUBSCR
LIX LIX_B_PSS_EXIT_S_NO value N
Returns subscreen
program name and
screen number in FM:/ORS/
PSS ( FM: indicates LIX_T_GET_EXIT_SUBSCR
LIX LIX_B_PSS_EXIT_S_PRG FM) N
Returns subscreen
screen number for
or can be direct LIX_T_GET_EXIT_SUBSCR
LIX LIX_P_PSS_EXIT_S_NO value N
Returns subscreen
program name and
screen number in FM:/ORS/
PSS ( FM: indicates LIX_T_GET_EXIT_SUBSCR
LIX LIX_P_PSS_EXIT_S_PRG FM) N
Line Item Execute
Transaction Task
LIX LN_EXECTCODE_TASKID ID TS98600016
VIM070500-03-RGD-EN-1

Code
Function module to
determine the
options to be
displayed in
LIX OPTION_DET_FM Process Selection /PTGWFI/0000000002_F002
FM exit for F4 help
from override
LIX OVERRIDE_F4_EXIT screen 9207
Parked Invoice
LIX PARKREASON Blocking Reason 9
LIV Parked Invoice
Main Workflow
Template ID
WS98600062/
LIX PARKWORKFLOW WS99680012 WS00275260
Post LIV blk pss /PTGWFI/
LIX POST_PSS_METHOD_EXIT screen user ext LIX_BK_TMP_PST_PSS_EXT
For more information, see Section 11.3.4 “Configuring the Post Dashboard
Method Exit” in OpenText Vendor Invoice Management for SAP Solutions -
Post PSS screen
LIX POST_PSS_PK_MTD_EXT method exit (park)
For more information, see Section 10.3.7 “Configuring the Post-dashboard
Method Exit” in OpenText Vendor Invoice Management for SAP Solutions -
PO Invoice Archive
LIX PO_INV_ARCHIVE_OBJ Object
Pre PSS screen
LIX PRE_PSS_METHOD_EXIT method exit
Pre PSS screen
LIX PRE_PSS_PK_MTD_EXT method exit (park)
For more information, see Section 10.3.6 “Configuring the Pre-dashboard Method
Exit” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
Name of the
Function module
which does the /PTGWFI/
LIX PRICE_BLOCK_FM price check LIX_F_CHECK_P_BLK
This function module is used whenever it is required to check if the price block
for an invoice item is still valid. For example, the function module is used in VIM
workflows to decide on the further processing steps.
VIM070500-03-RGD-EN-1
Code
Subscreen program
for Parked Invoice /PTGWFI/
LIX PRKPROG Resolution PRK_SUBSCREEN01
For more information, see Section 10.3.2 “Configuring Screen Exits” in OpenText
Subscreen for
Parked Invoice
LIX PRKSCREEN Resolution 9901
For more information, see Section 10.3.2 “Configuring Screen Exits” in OpenText
Function Module
Exit to be executed
before the start of
LIX PRK_AUTOPOST_EXIT Auto-Posting (LIV)
For more information, see Section 10.3.9 “Configuring an Autopost Exit” in
CGD).
Function Module
Exit to be executed
at the end of
Parked Document
LIX PRK_POSTING_EXIT_FM Posting Step
For more information, see Section 10.3.10 “Configuring a Parked Document
Posting Exit” in OpenText Vendor Invoice Management for SAP Solutions -
Post Process Sub
Workflow for
Parked Document
LIX PRK_POST_PROCESS_WF WF
For more information, see Section 10.3.8 “Configuring a Post Process
(Sub)workflow” in OpenText Vendor Invoice Management for SAP Solutions -
Pre Process Sub
Workflow for
Parked Document
LIX PRK_PRE_PROCESS_WF Workflow
For more information, see Section 10.3.4 “Defining a Preprocess (Sub)workflow”
(VIM-CGD).
FM exit in the
Binding FM for the
PSS step - at the
time of Inward /PTGWFI/
LIX PRK_PSS_BIND_FM1 Binding PRK_TMP_BIND_EXT_FM
VIM070500-03-RGD-EN-1

Code
For more information, see Section 10.3.5 “Configuring Binding Function Exits” in
CGD).
FM exit in the
Binding FM for the
PSS step - at the
time of Outward /ORS/
LIX PRK_PSS_BIND_FM2 Binding 000007_LIX_PSS_BIND_O
For more information, see Section 10.3.5 “Configuring Binding Function Exits” in
CGD).
Parallel Exit
workflow for PSS
Step in LIV Parked
LIX PRK_PSS_EXIT_WF Doc workflow
LIV Parked
Document Process
Selection Screen
LIX PRK_PSS_TASK_ID Task ID TS00275262
Function module to
be executed before
the TCode
Execution step is /PTGWFI/
LIX PRK_TCODE_BIND_FM1 created PRK_TMP_BIND_EXT_FM
Function module to
be executed at the /ORS/
end of the Tcode 000007_LIX_TCODE_BIND_
LIX PRK_TCODE_BIND_FM2 Execution step O
LIV Parked
Document Execute
Transaction Code
LIX PRK_TCODE_TASK_ID Task ID TS78600019
Process Selection
Screen - Task ID
LIX PROC_SELECT_TASKID TS99691001 TS00275265
FM exit in the
Binding FM for the
PSS step - at the
time of Inward
LIX PSS_BIND_EXIT_FM1 Binding
For more information, see Section 11.3.3 “Configuring Binding Function Exits
(Dashboard)” in OpenText Vendor Invoice Management for SAP Solutions -
VIM070500-03-RGD-EN-1
Code
FM exit in the
Binding FM for the
PSS step - at the
time of Outward
LIX PSS_BIND_EXIT_FM2 Binding
For more information, see Section 11.3.3 “Configuring Binding Function Exits
(Dashboard)” in OpenText Vendor Invoice Management for SAP Solutions -
User exit at the
PBO of PSS Log /PTGWFI/
LIX PSS_LOG_SCREEN_EXIT Subscreen PIR_TMP_PSS_LOG_EXIT
PSS screen: Option
type display
sequence ( A=
Action T=
Authorize
LIX PSS_OPTYP_DIS_SEQ R=Referral) 10ATR
For more information, see Section 10.3.3 “Configuring the Option Order” in
CGD).
Option key for the
LIX RESUBMIT_OPTION re-submit Option R9998
Parking Reasons
with Single Level
LIX SINGL_APPRVL_PRKRSN Approval 03;
SRM Block process
LIX SRM_BLK_PROCTYPE type 162
LIX SRM_PO_STATUS SRM PO Status K;
For more information, see “Invalid Requisitioner” on page 210, “Confirmation
Required from SRM (PO)” on page 212, and Section 29.2 “Determining Purchase
Order Types” in OpenText Vendor Invoice Management for SAP Solutions -
SRM- Mail
configuration ID
LIX SRM_PRC_BLK_MAIL_CID for Price Block 3
For more information, see Section 29.3.3 “Price Discrepancy Scenario” in
CGD).
Proxy Role for
LIX SRM_PRC_BLK_PXY_ROLE Price Block AP_PROCESSOR
CGD).
VIM070500-03-RGD-EN-1

Code
Delay in minutes
for SRM Price
LIX SRM_P_BLK_DELAY Block 1
CGD).
SRM- Recipient /OPT/
Email ID FM for S_GET_SRM_USER_EMAIL_
LIX SRM_P_BLK_RCV_EML_FM price block ID
CGD).
SRM Quantity
Block process type
(obsolate, replaced
by
SRM_BLK_PROCT
LIX SRM_QTY_BLK_PROCTYPE YPE) 162
CGD).
Proxy Role for
LIX SRM_QTY_BLK_PXY_ROLE Quantity Block AP_PROCESSOR
CGD).
LIX SRM_SCENARIO_TYPE SRM Scenario Type EXTENDED_CLASSIC
For more information, see Section 29.3.4 “SRM Scenario Type” in OpenText Vendor
Function module to
be executed before
the TCode
Execution step is
LIX TCODE_BIND_EXIT_FM1 created
Function module to
end of the Tcode 000007_LIX_TCODE_BIND_
LIX TCODE_BIND_EXIT_FM2 Execution step O
TCODE_CHANGE_LIV_IN Transaction code to
LIX V change LIV invoice MIR4
Transaction code to
LIX TCODE_DISP_LIV_INV display LIV invoice MIR4
VIM070500-03-RGD-EN-1
Code
FM to be called in
the User Exit to /PTGWFI/
collect data during PRK_M_GET_PARK_DATA
LIX USR_EXIT_GET_DATA_FM Document Parking _N
For more information, see Section 10.3.13 “Configuring the Parking
Functionality” in OpenText Vendor Invoice Management for SAP Solutions -
FM to be called in
collect data after PRK_M_GET_PARK_DATA
LIX USR_EXIT_GET_DATA_S Document Parking _S
VIM070500-03-RGD-EN-1
Chapter 38
Z Constants for Product Code PIR

Code
Display invoice
image on display
of dash board
PIR TO space -No)
For more information, see Section 12.2.11 “Configuring Automatic Image
Display” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
PIR DASHBOARD_NO_LOGO Display no Logo
If this constant is set to X, the logo is hidden in the parking dashboard for NPO
invoices.
Exit FM to
influence the
PIR DB_OPTION_SEQ dashboard buttons
SP3 or VIM 6.0 SP8.
WF relevant Doc
PIR WFDOCTYPE types *
This constant is used in the receiver function modules, for example the block
receiver (/OPT/VIM_RPT_PO_INV_RECEIVER), the post receiver, or the park
receiver.
According to the configured SAP document type, it is checked against the
document type of RBKP (for example, in case of PO, in /
OPT/VIM_RPT_PO_INV_RECEIVER) if the routine to update data in VAN
should be executed.
In very old VIM versions (before SAP reselling), VAN was an extra component
that customers had to pay for. Hence there was an option to configure when VAN
should be updated or used according to the SAP document type.
Possible values are SAP document types, for example KR, RE, or KG. VIM baseline
always sets this value to * because there are other options to decide how VIM
should be triggered and used.
PIR WFTRGPLANT Trigerring Plants *
Workitem Text
crreation FM (Refer
FM: /OPT/
BL_IF_SET_WI_TE
PIR WI_TEXT_FM XT)
VIM070500-03-RGD-EN-1
Chapter 38 Z Constants for Product Code PIR

Code
FM to determine
the Approver for /PTGWFI/
PIR APPROVER_GET_FM Parked Document 0000000002_APP001
Function Module
Exit to be executed
before the start of
PIR AUTOPOST_EXIT Auto-Posting (CIV)
For more information, see Section 12.2.8 “Configuring an Autopost Exit” in
CGD).
Exit for Running /OPT/
PIR AUTOPOST_RULES_EXIT Auto Post rules BL_AUTO_TEMPLATE
Option for
changing Parking
PIR CHG_PARK_RSN_OPTION reason 2023
Non PO Invoice /PTGWFI/
PIR CREATE_BDC_FM create FM VIM_CRE_NPO_INV
For more information, see Section 12.2.14 “Configuring Populating Screens for
Re-enter Options” in OpenText Vendor Invoice Management for SAP Solutions -
be executed before PIR_F_TMP_PRE_SND_MAI
PIR EXIT_PRE_SENDMAIL sending mail L
FM to delete Doc
Line Items before /ORS/
recreating via / RUN_BDC_CREATE_SCRIP
PIR GL_ACC_CREATE_BDC ORS/MAIN T
FM to delete Doc
Line Items before /ORS/
recreating via / RUN_BDC_DELETE_SCRIP
PIR GL_ACC_DELETE_BDC ORS/MAIN T
User Exit to
preload Invoice /ORS/
PIR GL_ACC_PRELOAD_EXIT Lines - FV60 GL_ACC_PRELOAD_EXIT
User Exit to
override or change
PIR GL_ACC_SCR_EXIT Table control fields /ORS/GL_ACC_SCR_EXIT
Subcsreen Program
for G/L Account
PIR GL_ACC_SUBSCR_PROG Entry /ORS/PRK_ENTRY_HDR
Subcsreen Screen
for G/L Account
PIR GL_ACC_SUBSCR_SCR Entry 9001
VIM070500-03-RGD-EN-1
Code
Function Module /PTGWFI/
PIR IMAGE_DISP_FM to Display Image BIR_F_TMP_DISP_IMG
For more information, see Section 12.2.10 “Configuring the Image Display
Function” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
Transactions to
create Non-PO FV60;FB60;/PTGWFI/
based Parked LIV_CHG_PKRS;
PIR NONPO_INV_TCODE Invoices /PTGWFI/PIR_CHG_PKRS;
For more information, see Section 12.2.1 “Configuring Transactions to Create
Parked Invoices” in OpenText Vendor Invoice Management for SAP Solutions -
NPO Invoice
PIR NPO_INV_ARCHIVE_OBJ Archive Object
Function module to
determine the
options to be
PIR OPTION_DET_FM displayed in Proc /PTGWFI/0000000002_F001
Parked Invoice
PIR PARKREASON Blocking Reason V
Subscreen program
for Parked Invoice /PTGWFI/
PIR PIRPROG Resolution PIR_SUBSCREEN01
For more information, see Section 12.2.2 “Configuring Dashboard Screen Exits” in
CGD).
Subscreen for
Parked Invoice
PIR PIRSCREEN Resolution 9901
For more information, see Section 12.2.2 “Configuring Dashboard Screen Exits” in
CGD).
Returns subscreen
program name and
also screen number FM:/ORS/
for PSS ( FM:) for BIR_T_GET_EXIT_SUBSCR
PIR PIR_PSS_EXIT_SUBSCRN FM N
Returns subscreen
screen number for
or can be direct BIR_T_GET_EXIT_SUBSCR
PIR PIR_PSS_EXIT_SUBS_NO value N
VIM070500-03-RGD-EN-1

Code
PIR Process
Selection Screen
Task ID
PIR PIR_PSS_TASK_ID TS98691004 TS00275260
PIR Execute
Transaction Code
PIR PIR_TCODE_TASK_ID Task ID TS78600019
Function Module
Exit to be executed
at the end of
Parked Document
PIR POSTING_STEP_EXIT_FM Posting Step
For more information, see Section 12.2.9 “Configuring a Parked Document
Posting Exit” in OpenText Vendor Invoice Management for SAP Solutions -
Post Process Sub
Workflow for
Parked Document
PIR POST_PROCESS_WF WF
For more information, see Section 12.2.7 “Configuring a Post Process
(Sub)workflow” in OpenText Vendor Invoice Management for SAP Solutions -
Post PSS screen
method
PIR POST_PSS_METHOD_EXIT exit(parked)
For more information, see Section 12.2.6 “Configuring the Post PSS Method Exit”
(VIM-CGD).
Transactions to
create PO based MR01;MIR7;/PTGWFI/
PIR PO_BASED_INV_TCODE Parked Invoices LIV_CHG_PKRS;
For more information, see Section 10.3.1 “Configuring Transactions to Create
Parked PO Invoices” in OpenText Vendor Invoice Management for SAP Solutions -
Pre Process Sub
Workflow for
Parked Document
PIR PRE_PROCESS_WF Workflow
For more information, see Section 12.2.3 “Defining a Preprocess (Sub)workflow”
(VIM-CGD).
Pre PSS screen
PIR PRE_PSS_METHOD_EXIT method exit(parke
VIM070500-03-RGD-EN-1
Code
For more information, see Section 12.2.5 “Configuring the Pre PSS Method Exit”
(VIM-CGD).
FM exit in the
Binding FM for the
PSS step - at the
time of Inward
PIR PSS_BIND_EXIT_FM1 Binding
For more information, see Section 12.2.4 “Configuring Binding Function Module
Exits” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
FM exit in the
Binding FM for the
PSS step - at the
time of Outward /ORS/
PIR PSS_BIND_EXIT_FM2 Binding 000007_PIR_PSS_BIND_O
For more information, see Section 12.2.4 “Configuring Binding Function Module
Exits” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
User exit at the
PBO of PSS Log /PTGWFI/
PIR PSS_LOG_SCREEN_EXIT Subscreen PIR_TMP_PSS_LOG_EXIT
Parallel Exit
workflow for PSS
Step in PIR
PIR PSS_STEP_EXIT_WF workflow-
For more information, see Section 12.2.12 “Configuring a Parallel Workflow Exit”
(VIM-CGD).
Option key for the
PIR RESUBMIT_OPTION re-submit Option R9998
FM for sending /PTGWFI/
PIR SEND_MAIL Document PIR_F_TMP_SEND_MAIL
Parking Reasons
with Single Level
PIR SINGL_APPRVL_PRKRSN Approval 03;
Function module to
be executed before
the TCode
Execution step is
PIR TCODE_BIND_EXIT_FM1 created
VIM070500-03-RGD-EN-1

Code
Function module to
end of the Tcode 000007_PIR_TCODE_BIND_
PIR TCODE_BIND_EXIT_FM2 Execution step O
FM to be called in
collect data during PIR_F_GET_PARK_DATA_
PIR USR_EXIT_GET_DATA_FM Document Parking N
For more information, see Section 12.2.13 “Configuring the Parking
Functionality” in OpenText Vendor Invoice Management for SAP Solutions -
FM to be called in
the User Exit to
collect data after /PTGWFI/
PIR USR_EXIT_GET_DATA_S Document Parking PIR_F_GET_PARK_DATA_S
Main Workflow
Template ID
WS98600055/
PIR WORKFLOWTEMPLATE WS99680011 WS00275254
VIM070500-03-RGD-EN-1
Chapter 39
Z Constants for Product Code VAN

Code
Calculate the
DueDate for table / /OPT/
VAN CALC_DUEDATE_FOR_DP OPT/VIM_HD_DP VIM_DP_CALC_DUEDATE
VAN DASHBOARD_NO_LOGO Display no Logo
If this constant is set to X, the logo is hidden in VIM Analytics.
Display result of
SYNC run in SYNC
VAN SYNCH_DIAG_INFO INFO button X
FM to be called in
the User Exit to
handle hotspots in
VAN USR_EXIT_HOTSPOT VIM Analytics
This constant can be used to facilitate an additional user exit in VIM Analytics.
You can maintain it with a custom function module, which determines the
behavior of hot spots in VIM Analytics.
If maintained, the custom function module is called in method COL_HOTSPOT of
class CL_EVENT_RECEIVER in the report /OPT/VIM_ANALYTICS.
You can use the function module /OPT/VIM_RPT_HOTSPOT_EXIT as a template
for the custom function module.
Constant to
maintain if VAN
Report Summary
VAN VIM_ANALYTICS_HEAD Section is required
This constant is obsolete. Since VIM 5.2 SP4, The VAN Report Summary Section
has been replaced by the Summary Report (/OPT/VIM_SUMM).
Approval flag:
'XX'=both, 'X '=PO
only, ' X'=NPO
APPROVAL_PO_NPO_FLA only, ' '=both not
VAN G include XX
VIM070500-03-RGD-EN-1
Chapter 39 Z Constants for Product Code VAN

Code
/ORS/
000007_5_VIM_M
ONITOR_PLUG
/ORS/
000007_5_VIM_M
ONITOR_PLUG /ORS/
Class to process 000007_5_VIM_MONITOR_
VAN APPROVAL_PROCESS_CL ORS PLUG
Usermap for NPO
Approval (space
means no NPO /ORS/
Approval data 000007_5_VIM_PLUG_SEL_S
VAN APPROVAL_SEL_SCR_PG plug in) CR; 8800
Constant for
determining due
VAN CALCULATE_DUEDATE date FM
FM for currency
VAN CURRENCY_CONVERSION conversion
This function module is used to convert the total amount/the line amount of DP
documents from the document currency to the local currency throughout the VIM
Analytics report.
If there is no function module provided, the function module

CONVERT_TO_LOCAL_CURRENCY is used as a fallback.
Detailed workitem
logging active ( X =
Active; Space =
VAN DETAILED_LOG_ACTIVE inactive) X
VAN DISPLAY_LOGO logo image name /OPT/VIM_OTLOGO
Use document date
when convert
VAN DOC_DATE_IN_CONVERT currency X
DOCUMENT
TYPE FOR CREDIT
VAN DOC_TYPE_CREDITMEMO MEMO KG;RA
DP PROCESS
VAN DP_PROCESS INCLUDED FLAG X
FREQ_GRAPH_MAX_LINE Max graphic item
VAN S for frequency 29
VIM070500-03-RGD-EN-1
Code
Tran code used to
display all LIV
invoices during
drilldown
VAN INVOICE_DISPLAY_LIV reporting MIR4
In some VIM reports (for example VIM Analytics), it is possible to use a link to go
from the SAP invoice number (BELNR) to the display of the corresponding SAP
invoice. This is the transaction code that is used for displaying PO invoices.
Tran code used to
display parked CIV
invoice during
drilldown
VAN INVOICE_DISPLAY_PIR reporting FBV3
In some VIM reports (for example VIM Analytics), it is possible to use a link to go
from the SAP invoice number (BELNR) to the display of the corresponding SAP
invoice. This is the transaction code that is used for displaying Non-PO invoices.
INVOICE
DOCUMENT
TYPE FOR NON-
VAN INV_DOC_TYPES_NPO PO INVOICE KR;KG
INVOICE
DOCUMENT
TYPE FOR PO
VAN INV_DOC_TYPES_PO INVOICE RE;RG
User exit for Non
PO workitems -
VAN NON_PO_WIH_EXIT Function module
Function module to
process ORS
VAN NPO_APPROVAL_FM approve plug in
Class name for
VIM Monitor user
VAN OBJ_LOGIC_EXTENSION extension
Object class for
VIM Monitor main
VAN OBJ_PROCESS process /OPT/VIM_RPT_PROCESS
User exit for PO
workitems -
VAN PO_WIH_EXIT Function module
VIM070500-03-RGD-EN-1
Chapter 39 Z Constants for Product Code VAN

Code
Default language
REMNDER_DEFAULT_LA for sending
VAN NG Reminders EN
Default selection
VAN SEL_SCR_DEF_VARIANT screen variant /OPT/VIM_DEF
This constant allows to maintain a global (not user specific) default screen layout
for the VIM Analytics selection screen.
Specify the max
number of records
VAN SYNCH_MAX_NUM which can be synch 800
User defined
extension selection
VAN USER_SEL_SCR_PROG screens PRO
VIM070500-03-RGD-EN-1
Glossary
AAK
See SAP Add-On Assembly Kit (AAK).
After Image
Technical option to realize an delta upload from the source systems into the SAP
NetWeaver BW system. A data record loaded as After Image provides the status
of the record after it has been changed, or after data has been added.
Aging Report
Part of the Central Reporting infrastructure. The Aging Report reports about the
aging of documents and work items in the current system.
AP processor
Accounts Payable personnel
Application Component Hierarchy
Hierarchy of folders to structure DataSources in SAP NetWeaver BW.
Approval chart of authority (COA)
The Approval chart of authority (COA) determines first approver and next
approver for an invoice by combinations of Company Code (specific or range),
Expense Type (marketing expense, utility), Cost Objects (G/L account, Cost
Center), and HR objects (Position, Job code).
Approval Portal
VIM web interface for approving invoices.
Archive system
Computer system that enables storage, management and retrieval of archived

data and documents
ArchiveLink document types
Document types that need to be customized for ArchiveLink
ArchiveLink
Service integrated in the SAP NetWeaver Application Server ABAP for linking
archived documents and the application documents entered in the SAP ERP
system
VIM070500-03-RGD-EN-1
Glossary
Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can perform in the SAP ERP system. These authorizations are
stored in Authorization profiles.
Automation Report
Tool that provides data about automated and manual processing steps of VIM
documents
BAdI
See Business Add-Ins (BAdI).
BAPI®
SAP programming interface: Business Application Programming Interface
Baseline
Set of functionality with pre-defined configuration and the starting point to

implement VIM
BasisCube
See InfoCube.
BDC ID
Business Data Communication ID. The BDC ID is used by the system to process
an SAP transaction to create an SAP Document in user context.
Block
Situation where an invoice has a price or quantity variance that prevents invoice
from posting
BTE
See Business Transaction Event (BTE).
Business Add-Ins (BAdI)
Business Add-Ins (BAdI) is an SAP enhancement technique based on ABAP

objects. BAdI can be inserted into the SAP ERP system to accommodate user
requirements too specific to be included in the standard delivery.
Business rules
Rules that describe the operations, definitions and constraints that apply to an
organization
Business Transaction Event (BTE)
Event used for extending a Non PO invoice functionality to call a custom program
VIM070500-03-RGD-EN-1
Glossary
Buyer
Person who is in charge of the PO. This role should have authorization to create
and change the purchase order. This role is also responsible for negotiating and
communicating with vendors.
Central Audit Report
Part of the Central Reporting infrastructure. The Central Audit Report is a

slimmed VIM Analytics (VAN). The main difference to VAN is that the Central
Audit Report serves as a single point of access in a multiple backend scenario.
Central Reporting
Reporting infrastructure that provides several reports that enable you to measure
certain properties of VIM documents and their work items, in order to optimize
working with VIM. Central Reporting comprises the following individual reports:
Aging Report, Central Audit Report, Exception Analysis Report, Key Process Analytics
Report, Productivity Report, and Summary Report.
Characteristic
Type of InfoObject in SAP NetWeaver BW that represents descriptions of fields,

such as Vendor ID, Invoice Number, Unit of Measure, and Posting Date.
COA
See Approval chart of authority (COA).
Coding
Coding allocates an invoice to G/L account and cost object if required.
Contract agent
Person who can create and modify SAP contracts.
Dashboard
User interface that organizes and presents information in a way that is easy to
read. Users can also perform actions from the dashboard.
Data Transfer Process (DTP)
Object in SAP NetWeaver BW to transfer data from source objects to target objects
DataSource
Set of fields in SAP NetWeaver BW that provide the data for a business unit for
data transfer to the SAP NetWeaver BW system; technically, it contains an extract
structure and an extraction function module.
VIM070500-03-RGD-EN-1
Glossary
DataStore Object (DSO)
Storage location for consolidated and cleansed data in SAP NetWeaver BW
DocuLink
OpenText™ DocuLink for SAP Solutions enables the archiving, management and
retrieval of SAP CRM or SAP ERP documents from within the SAP infrastructure.
Document Processing (DP)
VIM component that captures invoice metadata including line items for PO and
performs preconfigured business rules
Document type
Type of document such as PO, Non PO, OCR, Non OCR
DP
See Document Processing (DP).
DSO
See DataStore Object (DSO).
DTP
See Data Transfer Process (DTP).
Duplicate analyzer
Person who is responsible to identify duplicate invoices
EDI
See Electronic Data Interchange (EDI).
Electronic Data Interchange (EDI)
Method for transferring data between different application systems in the form of
messages. SAP applications support EDI with messages sent in an SAP
Intermediate Document (IDoc) format. VIM supports the creation of vendor
invoices through the EDI/IDoc interface.
Event Type Linkage
Error handling method. Event Type Linkage determines what the application
should do in case an error could not be handled.
Exception Analysis Report
Part of the Central Reporting infrastructure. The Exception Analysis Report

reports all work items with exceptions, grouped by exception, company code or
vendor.
VIM070500-03-RGD-EN-1
Glossary
Exception
Action that is not part of normal operations or standards
FI
See Financial Accounting (FI).
Financial Accounting (FI)
SAP module for the Finance and Accounting department
IAP
See Invoice Approval (IAP).
ICC
See Invoice Capture Center (ICC).
IDoc
See Intermediate Document (IDoc).
IE
See Invoice Exception (IE).
Indexer
Person responsible for entering index data
Indexing
Process of entering or storing data into the system
InfoArea
Folder in SAP NetWeaver BW to organize InfoCubes, DataStore Objects, InfoObjects,

and InfoObject Catalogs
InfoCube
Self-contained dataset in SAP NetWeaver BW, for example, of a business-oriented

area; an InfoCube is a quantity of relational tables arranged according to the
enhanced star schema: A large fact table in the middle surrounded by several
dimension tables
InfoObject Catalog
Folder structure in SAP NetWeaver BW to organize InfoObjects
InfoObject
Smallest information unit in SAP NetWeaver BW. Key figures and Characteristics
are collectively called InfoObjects.
VIM070500-03-RGD-EN-1
Glossary
InfoPackages
Object in SAP NetWeaver BW that specifies when and how to load data from a
given source system to the SAP NetWeaver BW system
InfoProvider
Object in SAP NetWeaver BW for which queries can be created or executed.

InfoProviders are the objects or views that are relevant for reporting.
Information provider
Receiving role for option Refer for Information
Intermediate Document (IDoc)
Standard SAP message document format for the EDI interface.
Invoice Approval (IAP)
VIM component that enables users to perform coding, approving and rejecting
invoices
Invoice approver
Person who approves invoices
Invoice Capture Center (ICC)
Optional VIM OCR component
Invoice characteristic
A value specific to each invoice (for example country) that allows flexible
processing in VIM. An invoice characteristic is determined during runtime and
depends on the corresponding index data of the document.
Invoice coder
Person who enters the accounting info on invoices to allocate the cost
Invoice Exception (IE)
VIM component that handles the exceptions that arise after an SAP invoice is
created
Invoice requester
Person who requested goods and services for Non PO invoices
Key Figure
Type of InfoObject in SAP NetWeaver BW that represents numeric values or

quantities, such as Number of Invoices and Gross Invoice Amount.
VIM070500-03-RGD-EN-1
Glossary
Key Process Analytics Report
Part of the Central Reporting infrastructure. The Key Process Analytics Report
reports about a variety of key figures regarding the VIM process: It shows the
accumulated amounts of all documents in the DP workflow, in parked state and
in posted state.
KPI Dashboard
Tool for managers showing VIM related process data at a glance in graphical
charts.
LIV
See Logistic invoice (LIV).
Logistic invoice (LIV)
purchase order invoice
Materials Management (MM)
Materials management module of the SAP ERP software package. Materials

management is used for procurement and inventory management.
MM
See Materials Management (MM).
Mobile Approval Portal
VIM component for approving invoices on mobile devices.
MultiProvider
Object in SAP NetWeaver BW that is based on InfoCube(s), DataStore Object(s),

and/or InfoObject(s). A MultiProvider is used as a layer for the creation of end user
queries; the MultiProvider itself does not contain any data; rather, data resides in
the BasisCubes.
Namespace
Name range reserved by SAP for customer objects and SAP objects to make sure
that objects are not overwritten by SAP objects during the import of corrections or
an upgrade
Non purchase order (Non PO)
Order that is not based on a PO
Non purchase order (Non PO) invoice (PIR)
Invoice based on a Non purchase order (Non PO)
VIM070500-03-RGD-EN-1
Glossary
Number range
Array of numbers that can be used for an object in the SAP ERP system
OCR
See Optical character recognition (OCR).
Optical character recognition (OCR)
Mechanical or electronic translation of images of handwritten, typewritten or

printed text (usually captured by a scanner) into machine-editable text
Park
Situation where an invoice is not posted and is waiting for further processing
Parked invoice document
Temporary document that the AP processor can change and post. SAP assigned
document number becomes real number when posted.
Persistent Staging Area (PSA)
Data staging area in SAP NetWeaver BW. It allows to check data in an

intermediate location before the data is sent to its destinations in SAP NetWeaver
BW.
PIR
See Non purchase order (Non PO) invoice (PIR).
PO
See Purchase order (PO).
Posted invoice document
Invoice that has already been posted in SAP ERP. Only free-form text fields can
be changed. Related documents such as POs or good receipts may be created or
changed to effect the invoice. If the document is not needed, it must be cancelled
( PO invoice) or reversed ( non-PO invoice).
Price variance
Situation where the price on the invoice is different from the price in the purchase
order
Process Chain
Sequence of processes in SAP NetWeaver BW that are scheduled to wait in the

background for an event; used to automate, visualize and monitor the processes.
VIM070500-03-RGD-EN-1
Glossary
Process options
Processing options for the user in the dashboard, such as Referral, Authorization,
and Actions
Process type
Process type for a document. The process type determines the initial actor and
various collaboration options available to the various actors during the process
flow.
Productivity Report
Part of the Central Reporting infrastructure. The Productivity Report reports

about the productivity of users/roles and the activities of users/roles.
PSA
See Persistent Staging Area (PSA).
Purchase order (PO) invoice
Invoice based on a Purchase order (PO)
Purchase order (PO)
SAP module. PO indicates a document sent from a buyer to a seller. The purpose
of the document is to order the delivery of goods or services.
Quantity variance
Situation where the quantity on the invoice is different from the quantity in the
purchase order
Receiver
Person who can create and reverse the goods receipt in SAP ERP
Requisitioner
Person who requested goods and services
Roles
Set of predefined roles for the SAP user
SAP Add-On Assembly Kit (AAK)
Standardized delivery procedure for software
SAP Customer Relationship Management (SAP CRM)
SAP application that provides software for ticket systems, for example in the
Accounts Payable department.
VIM070500-03-RGD-EN-1
Glossary
SAP NetWeaver Business Warehouse (SAP NetWeaver BW)
SAP application that allows to integrate, transform, and consolidate relevant

business information from productive SAP applications and external data
sources.
SAP Shared Service Framework
SAP software that contains a rich set of tools to improve and automate Shared
Service Center operations.
SAP Supplier Relationship Management (SAP SRM)
SAP application that automates, simplifies, and accelerates procure-to-pay

processes for goods and services.
Scan operator
Person who scans the invoices into images (may not have a SAP ID)
Service approver
Person who approves a service entry
Service requisitioner
Person who enters a service entry
Summary Report
Part of the Central Reporting infrastructure. The Summary Report provides a

summary of all documents processed through VIM.
Swimlane
Diagram representing a specific VIM process. A swimlane comprises the process

description, roles, user interface and options of the process.
Tax expert
Person who advises on invoices that need tax audit. Normally tax department
personnel.
Transformation (TRF)
Object in SAP NetWeaver BW to connect source objects to data targets; it allows

to consolidate, cleanse and integrate data
TRF
See Transformation (TRF).
VAN
See VIM Analytics (VAN).
VIM070500-03-RGD-EN-1
Glossary
Vendor Invoice Management (VIM)
Packaged business solution that solves a business problem – paying correct

amount to vendors on-time and with the lowest cost. VIM delivers not technology
but best-practice business processes. VIM provides values to customers in process
efficiency, visibility and compliance.
Vendor maintenance
Person who is responsible for creating and maintaining the vendor master
records
VIM Analytics (VAN)
VIM component that gives users a clear data report on their invoices in progress.
VIM Analytics allows to track the documents routed through SAP workflows via
VIM.
VIM Workplace
Tool for VIM super users, which allows users to display lists of their work items
that meet a selection they have entered before. Users also can display work items
of other users and of their team as a whole.
Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP ERP system.
VIM070500-03-RGD-EN-1

OpenText VIM For SAP Reference Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText VIM For SAP Reference Guide

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

for SAP® Solutions

The OpenText™ Vendor Invoice Management for SAP®

40 Avenue Monterey , Luxembourg, Luxembourg L-2163

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

No Warranties and Limitation of Liability

1 About This Document ............................................................. 15

Part 2 Third Party Interface Support 17

2 Interface Remote Functions ................................................... 21

Part 3 VIM Reporting 29

3 VIM Analytics: Getting Data Reports ..................................... 31

4 Using the VIM Analytics Current Liability Report ................. 65

5 Using the Automation Report ................................................. 79

6 Using the Common Infrastructure of Central Reporting

7 Using the Summary Report .................................................... 91

8 Using the Central Audit Report .............................................. 95

9 Using the Key Process Analytics Report .............................. 99

9.1 Using the Frame Selection Panel ................................................... 100

10 Using the Exception Analysis Report .................................. 109

11 Using the Productivity Report .............................................. 115

12 Using the Aging Report ........................................................ 121

Part 4 SAP NetWeaver Business Warehouse Details 127

13 InfoObjects ............................................................................. 129

14 DataSources ........................................................................... 147

15 DataStore Objects (DSOs) .................................................... 157

16 MultiProviders ........................................................................ 167

Part 5 Transactions and Roles 169

17 Transaction Profiles for Various Roles ............................... 171

Part 6 Business Rules 177

18 General Information About Business Rules ....................... 179

19 Business Rules for PO Invoices .......................................... 181

iv OpenText Vendor Invoice Management for SAP Solutions – Reference Guide

19.6 PO Not Released or Incomplete ..................................................... 184

OpenText Vendor Invoice Management for SAP Solutions – Reference Guide v

19.48 Invalid Invoice Code Format (PO) .................................................. 213

vi OpenText Vendor Invoice Management for SAP Solutions – Reference Guide

20 Business Rules for NPO Invoices ........................................ 223

20.41 Invalid/Missing Vendor ABN Number (NPO) ................................... 240

21 General Business Rules ....................................................... 245

22 Summary Tables .................................................................... 247

23 Customer Library ................................................................... 257

Part 7 Logic Modules 259

24 General Information About Logic Modules ......................... 261

25 Global Processing Logic Modules ....................................... 263

25.5 Determine Invoice Category ........................................................... 264

26 PO Related Logic Modules ................................................... 269

27 NPO Related Logic Modules ................................................. 273

28 Country Specific Logic Modules .......................................... 275

Part 8 Automated Field Enhancement 277

29 Configuring Automated Field Enhancement ...................... 279

30 Baseline of Automated Field Enhancement ........................ 281

Part 9 Z Constants 285

31 Z Constants for Product Code 002 and 009 ........................ 287

32 Z Constants for Product Code 005 ...................................... 291

OpenText Vendor Invoice Management for SAP Solutions – Reference Guide ix

33 Z Constants for Product Code IAP ...................................... 321

34 Z Constants for Product Code IEA ...................................... 333

35 Z Constants for Product Code IEM ...................................... 335

36 Z Constants for Product Code KPI ...................................... 337

37 Z Constants for Product Code LIX ....................................... 339

38 Z Constants for Product Code PIR ...................................... 351

39 Z Constants for Product Code VAN ..................................... 357