0% found this document useful (0 votes)

1K views308 pages

OpenText VIM 7.0.0 - ReferenceGuide

Uploaded by

ramana623

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

1K views308 pages

OpenText VIM 7.0.0 - ReferenceGuide

Uploaded by

ramana623

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

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.0.

VIM070000-RGD-EN-4
OpenText Vendor Invoice Management for SAP Solutions
Reference Guide
VIM070000-RGD-EN-4
Rev.: 2014-Jan-29
This documentation has been created for software version 7.0.
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
Email: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com

Copyright © 2014 by Open Text Corporation

OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not
exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names
mentioned herein are property of Open Text SA or other respective owners.

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
1 About Vendor Invoice Management ........................................ 9
1.1 About This Document ...................................................................... 12

2 Third Party Interface Support ................................................. 13

2.1 Interface Remote Functions ............................................................. 14

Part 1 VIM Reporting 21

3 VIM Analytics: Getting Data Reports ..................................... 23

3.1 Using the Selection Screen .............................................................. 23
3.2 Using Report Views ......................................................................... 28

4 Using the VIM Analytics Current Liability Report ................. 33

4.1 Using the Selection Screen .............................................................. 33
4.2 Using the Report Views Screen ........................................................ 36
4.3 Viewing and Grouping Report Results .............................................. 40

5 Using the Automation Report ................................................. 47

5.1 Using the Selection Screen .............................................................. 47
5.2 Using the Report Screen ................................................................. 48

6 Using the Common Infrastructure of Central Reporting

Reports ..................................................................................... 55
6.1 Using the Selection Screen .............................................................. 55
6.2 Using the Report Screen ................................................................. 57

7 Using the Summary Report .................................................... 59

7.1 Using the Selection Screen .............................................................. 59
7.2 Using the Report Screen ................................................................. 61

8 Using the Central Audit Report .............................................. 63

8.1 Using the Selection Screen .............................................................. 63
8.2 Using the Report Screen ................................................................. 65

9 Using the Key Process Analytics Report .............................. 67

9.1 Using the Frame Selection Panel ..................................................... 68
9.2 Using the Individual Report Panels ................................................... 69

10 Using the Exception Analysis Report .................................... 77

10.1 Using the Selection Screen .............................................................. 77
10.2 Using the Report Screen ................................................................. 79

11 Using the Productivity Report ................................................ 83

11.1 Using the Selection Screen .............................................................. 83

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions iii

Table of Contents

11.2 Using the Report Screen ................................................................. 85

12 Using the Aging Report .......................................................... 89

12.1 Using the Selection Screen .............................................................. 89
12.2 Using the Report Screen ................................................................. 91

13 Using the License Report ....................................................... 95

Part 2 SAP NetWeaver Business Warehouse Details 97

14 InfoObjects ............................................................................... 99
14.1 Key Figures .................................................................................... 99
14.2 Characteristics .............................................................................. 103
14.3 Units ............................................................................................ 114

15 DataSources ........................................................................... 117

15.1 DataSources for Transaction Data .................................................. 117
15.2 DataSources for Master Data ......................................................... 118

16 DataStore Objects (DSOs) .................................................... 127

16.1 DSOs of the Data Propagation Layer .............................................. 127
16.2 DSOs of the Corporate Memory Layer ............................................ 131

17 MultiProviders ........................................................................ 137

Part 3 Transactions and Roles 139

18 Transaction Profiles for Various Roles ............................... 141

23 Summary Tables .................................................................... 215

23.1 Table: Business Rules for PO Invoices ........................................... 215
23.2 Table: Business Rules for NPO Invoices ......................................... 219
23.3 Table: General Business Rules ...................................................... 222

24 Customer Library ................................................................... 223

24.1 Check Country Consistency ........................................................... 223
24.2 Check Balance .............................................................................. 223
24.3 Check and Update Coding for Auto Coding ..................................... 223

Part 5 Automated Field Enhancement 225

25 Configuring Automated Field Enhancement ...................... 227

26 Baseline of Automated Field Enhancement ........................ 229

Part 6 Z Constants 233

27 Z Constants for Product Code 002 and 009 ........................ 235

28 Z Constants for Product Code 005 ...................................... 239

29 Z Constants for Product Code IAP ...................................... 259

30 Z Constants for Product Code IEA ...................................... 271

31 Z Constants for Product Code IEM ...................................... 273

32 Z Constants for Product Code KPI ...................................... 275

33 Z Constants for Product Code LIX ....................................... 277

34 Z Constants for Product Code PIR ...................................... 289

35 Z Constants for Product Code VAN ..................................... 295

GLS Glossary 299

viii OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 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:

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 9

Chapter 1 About Vendor Invoice Management

Figure 1-1: VIM components

ICC (Invoice Capture Center)

• 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.

10 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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).

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.

VIM070000-RGD-EN-4 Reference Guide 11

Chapter 1 About Vendor Invoice Management

1.1 About This Document

This document collects reference information that is helpful when configuring and
administering VIM.

1.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.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

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).

12 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 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-1 depicts the suggested data and process flow for a third party service
provider scenario.

Figure 2-1: Third party service provider scenario - overview

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 13

Chapter 2 Third Party Interface Support

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.

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 Archive
Server via HTTP Post action.

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.

2.1 Interface Remote Functions

The third party service provider scenario includes 3 Interface Remote Functions.

2.1.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

14 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

2.1. Interface Remote Functions

*" 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

Parameter Name Data Type Size Comments

ARCHIV_DOC_ID Char 40 SAP ArchiveLink Document ID
( generated for the image)
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.

VIM070000-RGD-EN-4 Reference Guide 15

Chapter 2 Third Party Interface Support

2.1.2 Interface Remote Function 2

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.
*"------------------------------------------------------------------
*"*"Local Interface:
*" 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
*" 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:

Parameter Name Data Type Size Comments

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:

Parameter Name Data Type Size Comments

CHANNEL_ID Char 10 SAP Channel ID (Constant).
Recommended to be supplied. It helps
in identifying the source of any
supplied invoice.

16 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

2.1. Interface Remote Functions

Parameter Name Data Type Size Comments

SYSTEM Char 10 Logical name of the SAP ERP target
system

3. Invoice info captured from External Partner:

Parameter Name Data Type Size Comments

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:

Parameter Name Data Type Size Comments

DOCTYPE Char 10 VIM Processing Document Type
I_DOC_HEADER Structure Structure of Indexing Document
Type Header /OPT/VIM_1HEAD
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

Export parameters

Parameter Name Data Type Size Comments

RC Numeric 2 Value 0 means successful. Value 8 means
error.
RETURN Table Type Table of messages BAPIRET2
E_WF_ID Numeric 12 Work item ID of the triggered Document
Processing Workflow in VIM

VIM070000-RGD-EN-4 Reference Guide 17

Chapter 2 Third Party Interface Support

Parameter Name Data Type Size Comments

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
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.

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.
If one or both of these parameters are provided, the given value will override
the configuration.

Additional notes

The document type AR_OBJECT cannot be provided as import parameter for

additional images. 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.

18 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

2.1. Interface Remote Functions

2.1.3 Interface Remote Function 3

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.
*"----------------------------------------------------------
*"*"Local Interface:
*" 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:

Parameter Name Data Type Size Comments

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:

Parameter Name Data Type Size Comments

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

Export parameters

Parameter Name Data Type Size Comments

RC Numeric 2 Value 0 means successful. Value 8 means
error.
RETURN Table Type Table of messages BAPIRET2
DOC_STATUS Table Type Table parameter of Document Processing
Number and its corresponding status.
Refer to structure /
OPT/VIM_DP_STATUS1

VIM070000-RGD-EN-4 Reference Guide 19

Chapter 2 Third Party Interface Support

Error handling

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.

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.

20 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Part 1
VIM Reporting
Part 1 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
• License Report

This part describes how to work with the mentioned reports as an end user.

22 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 3
VIM Analytics: Getting Data Reports

VIM Analytics provides you with clear data reports 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. VIM Analytics presents the data
report results in the SAP List Viewer (ALV).

You can use VIM Analytics to check the current document status and exception
reason of a particular invoice in the Document View. You can also check the current
workflow status, current agent and exception reason of a particular invoice in the
Workflow view.

3.1 Using the Selection Screen

To start VIM Analytics:

• Run the /OPT/VIM_ANALYTICS transaction.

Alternatively, navigate to OpenText Vendor Invoice Management > SAP menu
> Reports > /OPT/VIM_ANALYTICS - VIM Analytics

Note: Your screen might look different as the display of selection fields
can be customized.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 23

Chapter 3 VIM Analytics: Getting Data Reports

24 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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
VIM Analytics creates and displays a report, using the current settings in
the Selection field panel.
Get variant.
You can save your selection criteria and use the variant button to retrieve
the previous saved one.
Example: You search for Document Status = Posted 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.

Open additional selection criteria dialog box.

The selection screen that is shipped contains various selection fields that
show up. Some selection fields are not displayed by default as there are too
many. Click to open a screen where you can select more fields to be
displayed in the selection screen.
Selection field panel
Selection fields explanation - The following list provides some explanation on
selection fields that are not self-explanatory. The list refers to selection fields that
are always visible but also to those in the additional selection criteria dialog box.

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.

Line Item
Line item number from the SAP invoice document
Reference
Reference document number from the invoice
Purchase Order Line
Line item number from the purchase order
Exception Date
Date on which the VIM invoice exception was raised; for example: approval
required, vendor maintenance required.

VIM070000-RGD-EN-4 Reference Guide 25

Chapter 3 VIM Analytics: Getting Data Reports

Due Date
Date on which the invoice is due for payment

Enter on
Date on which the parked invoice work item was created

Enter at
Time at which the parked invoice work item was created

Start on
Date on which the parked invoice work item was started

Start at
Time at which the parked invoice work item was started

End on
Date on which the parked invoice work item was completed

End at
Time at which the parked invoice work item was completed

Update Date
Date on which the parked invoice was updated

Update Time
Time at which the parked invoice was updated

Days to Due
Number of days until the invoice is due for payment

Overdue
Check box to indicate that the invoice is overdue for payment

Old Doc Num

SAP invoice document number that was deleted due to a change in the year
end posting period

Old Fiscal Year

SAP invoice document fiscal year that was deleted due to a change in the
year end posting period

Old Company Code

SAP invoice document company code that was deleted due to a change in
the year end posting period

Status
Status of the work item; for example: ready, completed

Task
VIM workflow task number

First Name
First name of the work item's current agent

26 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

3.1. Using the Selection Screen

Last Name
Last name of the work item's current agent
Creation Date
Date on which the work item was generated in status ready or waiting for
the first time
Creation Time
Time at which the work item was generated in status ready or waiting for
the first time
End on
Date on which the work item was completed
End at
Time at which the work item was completed
Process Type
DP document exception type; for example: Invalid vendor number,
Invalid UOM

Character Length 1
DP Items check box in the Report Options panel. If selected, DP documents
are included in the selection of data for the report.

Report Options The Report Options section enables you to edit the settings for your report:

View Type

Document View, Workflow View

Use the radio button to toggle between document view and workflow view. See
“Using Report Views” on page 28 for details.

Include Activate the check boxes for the types of invoices you want to include in your report:

Note: The PO and NPO check boxes depend on Invoice Exception. That means
that the documents were parked or blocked. The following kinds of invoices
will not appear with that search criteria:
• any directly posted invoices from DP (without parking or blocking)

VIM070000-RGD-EN-4 Reference Guide 27

Chapter 3 VIM Analytics: Getting Data Reports

• DP NPO and DP PO invoices

These work items do not have a SAP document yet and still are in the DP
workflow.

DP Items Activate the DP Items check box if you want to include DP items in your report,
generally.

Note: For DP Credit Memos (including status Posted with no Invoice

Exception), you can add the selection field CREDITMEMO (see Application
toolbar on page 25) and enter X. With this selection, DP Credit Memos will be
shown correctly.

3.2 Using Report Views

This section describes the various views of the report results that are available when
running VIM Analytics. You can run the report in the following views:
• Document view
• Workflow view

The following sections explain the general layout and each of the views. During the
output display, you can toggle between the views.

3.2.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.

The report views comprise the following sections:

1
Menu toolbar

28 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

3.2. Using Report Views

2
Application toolbar

3
ALV Grid Control

4
ALV Grid (Document View or Workflow View)

3.2.2 Menu Toolbar

The following action is available in the menu toolbar under Actions

Update Selected Records

In the ALV Grid, select the row that you want to update and click this menu
item to get the newest data.

3.2.3 Application Toolbar

The application toolbar contains the following buttons:

Workflow View/Document View

Toggle between workflow view and document view.

Group Freq. & Stat.

Start the Document Frequency Report.

To use the Document Frequency Report:

1. Click Group Freq. & Stat.

2. In the Choose Group dialog box, select one selection criterion, for example
VENDOR, and click Choose.

The Document Frequency Report provides columns indicating the average

time that a work item has spent in the system:

Avg. All Cycle Time

Average time between start date and time, and end date and time for all
invoices

VIM070000-RGD-EN-4 Reference Guide 29

Chapter 3 VIM Analytics: Getting Data Reports

Avg. Open Cycle Time

Average time between start date and time, and end date and time for all
open invoices
Avg. Resl Cycle Time
Average time between start date and time, and end date and time for all
resolved invoices
To change the criterion for grouping, click Group Freq. & Stat. again.
To show the results in SAP Business Graphics, click Stat. Graphic in the
application toolbar.
To open a list with related items for a document, select the document in the
ALV Grid and click Detail in the application toolbar.

Sync
Update the records selected in the VAN report output by program /
OPT/VAN_SYNC_JOB. The update bases on SAP standard tables and the /
OPT/VIM_1HEAD table.

Sync Info.
Display the Sync Information dialog box. It contains information when data has
been updated lately.

3.2.4 ALV Grid Control

The ALV Grid control provides various SAP-specific buttons for the ALV list viewer.
The following buttons are specific for VIM Analytics:

Workflow Log (only available in Workflow View)

Display the workflow log with technical details for the selected document.
Image
Display the scanned image of the original invoice of the selected document in
the Image Viewer installed and configured on your desktop.
Dashboard
Access the OpenText unified dashboard for the selected document.

3.2.5 Document View

The Document View (ALV Grid) presents the report results in a document
perspective. That means, the Document View counts the document once,

30 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

3.2. Using Report Views

irrespective of the number of workflows and exceptions that the document might
have passed through. The Document View shows the Document Status, the
Exception Reason and various other document related information.

Underlined values, for example in the Document Number or the Vendor column,
serve as links to pages with detailed information.

Tip: You can toggle between the Document View and the Workflow View, by
clicking Document View or Workflow View in the application toolbar.

3.2.6 Workflow View

The Workflow View (ALV Grid) presents the report results in a workflow
perspective. That means, the Workflow View shows one record for each of the
workflows that have been started for a particular document. You can use the
Workflow View to determine the Current Agent for a particular workflow, in case
the workflow is still in process. The Workflow View also shows process times, like
the Cycle Time and various other workflow related information.

Tip: You can toggle between the Document View and the Workflow View, by
clicking Document View or Workflow View in the application toolbar.

VIM070000-RGD-EN-4 Reference Guide 31

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.

4.1 Using the Selection Screen

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

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 33

Chapter 4 Using the VIM Analytics Current Liability Report

34 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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.

VIM070000-RGD-EN-4 Reference Guide 35

Chapter 4 Using the VIM Analytics Current Liability Report

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 40.

SAP Document Lines View

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

36 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

4.2. Using the Report Views Screen

DP View
Displays the DP document only; see “DP Information View” on page 42.

Groupings

Header Groups
Allows you to group the result based on the header level; see “Document
Header Grouping” on page 42.

Line Groups
Allows you to group the result based on the line level; see “Document Lines
Grouping” on page 44.

You can select views and groupings in the Report View Group By field of the
selection screen, see “General Information” on page 35. 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 38

• “Application Toolbar” on page 38
• “Overview Section” on page 38
• “Report Results (ALV Grid)” on page 39

VIM070000-RGD-EN-4 Reference Guide 37

Chapter 4 Using the VIM Analytics Current Liability Report

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 38.

Total On/Total Off

See “Menu Toolbar” on page 38.

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.

38 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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 40. 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.

VIM070000-RGD-EN-4 Reference Guide 39

Chapter 4 Using the VIM Analytics Current Liability Report

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 36.

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

40 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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:

Note: The following list only covers columns whose meaning is not obvious.

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

VIM070000-RGD-EN-4 Reference Guide 41

Chapter 4 Using the VIM Analytics Current Liability Report

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:

Note: The following list only covers columns whose meaning is not obvious.

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

Gross amount specified in the header level

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.

42 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

4.3. Viewing and Grouping Report Results

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:

Note: The following list only covers columns whose meaning is not obvious.

# of Docs
Number of documents in the group

Total Amount
Gross amount specified in the header level

Line Amount
Amount from all invoice lines of the invoice

VIM070000-RGD-EN-4 Reference Guide 43

Chapter 4 Using the VIM Analytics Current Liability Report

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:

44 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

4.3. Viewing and Grouping Report Results

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

VIM070000-RGD-EN-4 Reference Guide 45

Chapter 5
Using the Automation Report

The Automation Report, introduced with VIM 7.0 SP2, 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 25 “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.

5.1 Using the Selection Screen

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.

2. In the Automation Report selection field screen, configure parameters for the
report.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 47

Chapter 5 Using the Automation 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.

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 53.

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.

5.2 Using the Report Screen

When you have finished your selection in the selection screen, click to run the
report.

48 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

5.2. Using the Report Screen

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 51, 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.

5.2.2 Report Results (ALV Grid)

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.

Invoice Data

Note: Fields that are marked with an asterisk in the tables are not visible in the
screenshot.

VIM070000-RGD-EN-4 Reference Guide 49

Chapter 5 Using the Automation Report

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
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

50 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

5.2. Using the Report Screen

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

Technical Field Name Description (column Meaning - Usage - Notes

name)
* LIFNR_ICC Extracted Vendor From CDPOS, Tcode EXTRACTION,
field LIFNR
* FLAG_MULTIBACK Multibackend Comparison result of LOGSYS and
SENT_TO_SYSTEM (check box)
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)
FLAG_BLOCKED Blocked From /OPT/VIM_1LOG and /OPT/
CT_LG_HIST (check box)

VIM070000-RGD-EN-4 Reference Guide 51

Chapter 5 Using the Automation Report

Technical Field Name Description (column Meaning - Usage - Notes

name)
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.
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.
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.

52 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

5.2. Using the Report Screen

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.

VIM070000-RGD-EN-4 Reference Guide 53

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 69.

6.1 Using the Selection Screen

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 60 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.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 55

Chapter 6 Using the Common Infrastructure of Central Reporting Reports

Selection field panel

The following selection criteria are available in all reports. Exceptions are
indicated where appropriate.

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.

Currency Translation Date

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.

56 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

6.2. Using the Report Screen

6.2 Using the Report Screen

When you have finished your selection in the selection screen, click to run the
report.

Figure 7-2 on page 61 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 69.

VIM070000-RGD-EN-4 Reference Guide 57

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.

58 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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.

7.1 Using the Selection Screen

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 55.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 59

Chapter 7 Using the Summary Report

Figure 7-1: Summary Report selection screen

Selection field panel

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 25 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.

60 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

7.2. Using the Report Screen

7.2 Using the Report Screen

When you have finished your selection in the selection screen, click to run the
report.

Figure 7-2: Summary Report report screen

1
Header section
2
ALV grid control
3
Report results (ALV grid)

For a description of the elements that are common for all reports, see “Using the
Report Screen” on page 57.

7.2.1 Report Results (ALV Grid)

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)

VIM070000-RGD-EN-4 Reference Guide 61

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.

62 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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.

8.1 Using the Selection Screen

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.

Alternatively, in OpenText Vendor Invoice Management, navigate to SAP
menu > Reports > Central Reporting > Audit Report.
For a description of the elements that are common for all reports, see “Using the
Selection Screen” on page 55.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 63

Chapter 8 Using the Central Audit Report

Selection field panel

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 25 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.

64 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

8.2. Using the Report Screen

8.2 Using the Report Screen

When you have finished your selection in the selection screen, click to run the
report.

The report screen comprises the following sections:

• “ALV Grid Control” on page 65

• “Report Results (ALV Grid)” on page 66

8.2.1 ALV Grid Control

The ALV Grid control of the Central Audit Report displays the same buttons that are
available in VAN; see “ALV Grid Control” on page 30. Additionally, the following
button is displayed:

Link to VAN
Select a document's line in the ALV Grid and click Link to VAN to open the
VAN Workflow View (see “Workflow View” on page 31) for the selected
document.
In a multiple backend scenario, the VAN Workflow View 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).

VIM070000-RGD-EN-4 Reference Guide 65

Chapter 8 Using the Central Audit Report

8.2.2 Report Results (ALV Grid)

The ALV Grid of the Central Audit Report is very similar to the Document View of
VAN; see “Document View” on page 30. 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.

66 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 67

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.

Alternatively, in OpenText Vendor Invoice Management, navigate to SAP
menu > Reports > Central Reporting > Key Process Analytics Report.

The main screen comprises the application toolbar, the Frame Selection panel
and the individual report panels.
For a description of the elements that are common for all reports, see “Using the
Selection Screen” on page 55.

68 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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 56.
Individual report panels
See “Using the Individual Report Panels” on page 69.

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.

VIM070000-RGD-EN-4 Reference Guide 69

Chapter 9 Using the Key Process Analytics Report

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.

70 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

9.2. Using the Individual Report Panels

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

For a screenshot of the report panel, see Figure 9-1.

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.

VIM070000-RGD-EN-4 Reference Guide 71

Chapter 9 Using the Key Process Analytics Report

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
Document List cannot be displayed.

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

For a screenshot of the report panel, see Figure 9-1.

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:

Note: The following list only covers columns whose meaning is not obvious.

Channel ID
Channel ID, for example IDOC for invoices imported using Electronic Data
Interchange

72 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

9.2. Using the Individual Report Panels

Channel Text
Description of the channel

Total # Unclassified
Total number of unclassified invoices (not yet classified as PO or NPO invoices)

You can add the following columns using the ALV grid control:

PO Invoices (%)
Percentage of PO invoices

NPO Invoices (%)

Percentage of NPO invoices

Unclassified (%)
Percentage of unclassified invoices

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 Channel ID referred to in the selected cell.

Tip: The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.

9.2.4 First Pass

For a screenshot of the report panel, see Figure 9-1.

The First Pass panel provides an overview of first pass VIM invoices, that means
VIM invoices that could be posted without any exceptions. The First Pass panel
comprises the following columns:

Note: The following list only covers columns whose meaning is not obvious.

First Pass (%)

Percentage of First Pass documents

Total # First Pass

Total number of First Pass documents

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.
This column can be useful if you export the data, for example to Microsoft Excel.

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 the Invoice Type referred to in the selected cell.

VIM070000-RGD-EN-4 Reference Guide 73

Chapter 9 Using the Key Process Analytics Report

Tips
• The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.
• 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

For a screenshot of the report panel, see Figure 9-1.

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:

Note: The following list only covers columns whose meaning is not obvious.

Exception ID
ID of the exception in the system

Exception Text
Description of the Exception

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.

74 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

9.2. Using the Individual Report Panels

9.2.6 Top Vendors by Amount

For a screenshot of the report panel, see Figure 9-1.

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:

Note: The following list only covers columns whose meaning is not obvious.

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
Document List opens, showing detailed information on the VIM documents,
according to the Logical System and the Vendor referred to in the selected line.

VIM070000-RGD-EN-4 Reference Guide 75

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.

10.1 Using the Selection Screen

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.

Alternatively, in OpenText Vendor Invoice Management, navigate to SAP
menu > Reports > Central Reporting > Exception Analysis Report.
For a description of the elements that are common for all reports, see “Using the
Selection Screen” on page 55.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 77

Chapter 10 Using the Exception Analysis Report

Selection field panel

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.

78 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

10.2. Using the Report Screen

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
Enter the date range you want to run the report for. The date refers to
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.

10.2 Using the Report Screen

When you have finished your selection in the selection screen, click to run the
report.

VIM070000-RGD-EN-4 Reference Guide 79

Chapter 10 Using the Exception Analysis Report

For a description of the elements that are common for all reports, see “Using the
Report Screen” on page 57.

10.2.1 ALV Grid Control

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.

10.2.2 Report Results (ALV Grid)

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.

80 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

10.2. Using the Report Screen

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

10.2.3 Details Screen

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.

VIM070000-RGD-EN-4 Reference Guide 81

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

11.1 Using the Selection Screen

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.

Alternatively, in OpenText Vendor Invoice Management, navigate to SAP
menu > Reports > Central Reporting > Productivity Report.
For a description of the elements that are common for all reports, see “Using the
Selection Screen” on page 55.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 83

Chapter 11 Using the Productivity Report

Selection field panel

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).

84 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

11.2. Using the Report Screen

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).

Note: Unclassified invoices are not yet classified as PO or NPO

invoices.

Time Characteristics

Date Range
Enter the date range you want to run the report for. The date refers to
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.

11.2 Using the Report Screen

When you have finished your selection in the selection screen, click to run the
report.

For a description of the elements that are common for all reports, see “Using the
Report Screen” on page 57.

VIM070000-RGD-EN-4 Reference Guide 85

Chapter 11 Using the Productivity Report

11.2.1 ALV Grid Control

The following button is specific for the Productivity 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 Agent or Role.

11.2.2 Report Results (ALV Grid)

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 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.

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
following description.

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.

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

86 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

11.2. Using the Report Screen

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>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

Prev. Avg. # of Touches

Average number of how often a VIM document has been touched

Prev. Avg. # of Ref.

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

VIM070000-RGD-EN-4 Reference Guide 87

Chapter 11 Using the Productivity Report

11.2.3 Details Screen

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
Document List cannot be displayed.

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.

88 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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.

12.1 Using the Selection Screen

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.

Alternatively, in OpenText Vendor Invoice Management, navigate to SAP
menu > Reports > Central Reporting > Aging Report.
For a description of the elements that are common for all reports, see “Using the
Selection Screen” on page 55.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 89

Chapter 12 Using the Aging Report

Selection field panel

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).

Note: Unclassified invoices are not yet classified as PO or NPO

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.

90 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

12.2. Using the Report Screen

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 91
shows buckets that are defined with 50 / 75 / 100

12.2 Using the Report Screen

When you have finished your selection in the selection screen, click to run the
report.

VIM070000-RGD-EN-4 Reference Guide 91

Chapter 12 Using the Aging Report

For a description of the elements that are common for all reports, see “Using the
Report Screen” on page 57.

12.2.1 ALV Grid Control

The following button is specific for the Aging 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 Doc Type or Role.

92 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

12.2. Using the Report Screen

12.2.2 Report Results (ALV Grid)

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 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
following description.

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 91.
Number of documents that are work in process and have been in the system for
0 to 30 days.

31 to 60 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 91.
Number of documents that are work in process and have been in the system for
31 to 60 days.

61 to 90 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 91.
Number of documents that are work in process and have been in the system for
61 to 90 days.

>90 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 91.
Number of documents that are work in process and have been in the system for
more than 90 days.

VIM070000-RGD-EN-4 Reference Guide 93

Chapter 12 Using the Aging Report

12.2.3 Details Screen

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.

94 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 13

Using the License Report

The License Report allows you to print a report of the number of invoices processed
through VIM in all channels in a given time period. You can send the report to
OpenText or SAP.

To start the License Report:

1. Run the /n/OPT/VIM_LICENSE transaction.

Alternatively, in OpenText Vendor Invoice Management, navigate to SAP
menu > Reports > Central Reporting > License Report.

2. In the selection screen, enter the report parameters:

Date

Created
The creation date. Mandatory field. Both “From” and “To” fields are
required.
By default, the “From” field is populated with the date 2 years ago from the
current date. The “To” field is populated with the current date.

Org Related

Channel ID
Optional field. Enter the channel through which invoices are processed.

DP Document Type
Optional field. Enter the DP document type.

3. To display the License Report, click in the application toolbar.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 95

Chapter 13 Using the License Report

The invoice count is displayed for each channel per month in a year. It is
summed for each year in a channel, and for all years in a channel. At the end,
the total number of invoices in all channels is displayed.
You can print the report and send it to OpenText or SAP.

96 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Part 2
SAP NetWeaver Business Warehouse
Details
Part 2 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

For more information, see Section 23 “SAP NetWeaver Business Warehouse

Content” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).

98 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 14
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

14.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.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 99

Chapter 14 InfoObjects

For technical data, see the SAP documentation.

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

Available as of VIM 7.0

Release
Data element /OPT/KIVGAFC
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
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.

For technical data, see the SAP documentation.

Number of Key figure: /OPT/KIVCT

Invoices
This key figure shows the number of invoices.

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

Available as of VIM 7.0

Release
Data element /B7999/OICCHANNL

Company Code Characteristic: 0COMP_CODE

This characteristic shows the company code of the VIM invoice.

For technical data, see the SAP documentation.

VIM070000-RGD-EN-4 Reference Guide 103

Chapter 14 InfoObjects

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.

(Time)
This characteristic shows the time when the VIM invoice was created in the SAP
ERP system.

104 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

14.2. Characteristics

Release
Data element /B7999/OICCCDTFC
Reference 0DATE
characteristic

Document Characteristic: /OPT/CDOCID

Ledger Number
This characteristic shows the document number of the VIM invoice.

VIM070000-RGD-EN-4 Reference Guide 105

14.2. Characteristics

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

Available as of VIM 7.0

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.

For technical data, see the SAP documentation.

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.

For technical data, see the SAP documentation.

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.

For technical data, see the SAP documentation.

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

Available as of VIM 7.0

Release
Data element /B7999/OICFINIDT

VIM070000-RGD-EN-4 Reference Guide 107

Chapter 14 InfoObjects

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

Available as of VIM 7.0

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

Available as of VIM 7.0

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.

For technical data, see the SAP documentation.

Fiscal Year Characteristic: 0FISCVARNT

Variant
This characteristic shows the fiscal year variant from the company code of the VIM
invoice.

For technical data, see the SAP documentation.

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.

108 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 14 InfoObjects

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.

For technical data, see the SAP documentation.

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.

For technical data, see the SAP documentation.

Record Type Characteristic: 0RECORDTP

For details, see the SAP documentation.

Request ID Characteristic: 0REQUID

For details, see the SAP documentation.

Source System Characteristic: 0LOGSYS

This characteristic shows the name of the logical system of the OLTP source system
(SAP ERP system).

For technical data, see the SAP documentation.

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.

112 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

14.2. Characteristics

Technical data

Available as of VIM 7.0

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

Available as of VIM 7.0

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

Available as of VIM 7.0

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

Available as of VIM 7.0

Release
Data element /B7999/OICTOTITY

VIM070000-RGD-EN-4 Reference Guide 113

Chapter 14 InfoObjects

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

Available as of VIM 7.0

Release
Data element /B7999/OICUPDTS

Vendor Characteristic: 0VENDOR

This characteristic shows the vendor the VIM invoice was sent from.

For technical data, see the SAP documentation.

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

Available as of VIM 7.0

Release
Data element /B7999/OICVENDGR

14.3 Units
Currency of Unit: 0INV_CURR
Invoice
This unit shows the document currency of the VIM invoice.

For technical data, see the SAP documentation.

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.

For technical data, see the SAP documentation.

114 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

14.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

Available as of VIM 7.0

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.

For technical data, see the SAP documentation.

VIM070000-RGD-EN-4 Reference Guide 115

Chapter 15
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

15.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

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 117

Chapter 15 DataSources

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_EXCEPTIONS
Extraction /OPT/BEXTR_EXC_TRAN_ST
Structure

15.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
Available as of VIM 7.0 (SAP ERP 6.0)
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.

118 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

15.2. DataSources for Master Data

Technical data

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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
customizing of the leading SAP ERP system.

Technical data

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
Release
Delta-Capable No

VIM070000-RGD-EN-4 Reference Guide 119

Chapter 15 DataSources

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
leading SAP ERP system.

Technical data

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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)

120 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

15.2. DataSources for Master Data

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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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).

VIM070000-RGD-EN-4 Reference Guide 121

Chapter 15 DataSources

Technical data

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
Release

122 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

15.2. DataSources for Master Data

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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
Release
Delta-Capable No
Extraction from No
Archives

VIM070000-RGD-EN-4 Reference Guide 123

Chapter 15 DataSources

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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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
leading SAP ERP system.

Technical data

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
Release
Delta-Capable No
Extraction from No
Archives
Extraction by Function module /OPT/BGET_TIMETYPE_TEXT
Extraction /OPT/BEXTR_TIMETY_TEXT_ST
Structure

124 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

15.2. DataSources for Master Data

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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
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

Application OpenText Vendor Invoice Management > Master Data

Component
Available as of VIM 7.0 (SAP ERP 6.0)
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/KAGR_C_VNDT
Extraction /OPT/ESVIM_VENDGR_TEX0001
Structure

VIM070000-RGD-EN-4 Reference Guide 125

Chapter 16
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 23.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.

16.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.

16.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)

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 127

Chapter 16 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.

As a target of the DSO, the following are supplied:

• 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.

As a target of the DSO, the following are supplied:

• DSO Exceptions with DP Documents (/OPT/DPEXD)

• DSO Exception Classes with DP Documents (/OPT/DPEXCD)

128 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

16.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.

As a target of the DSO, the following are supplied:

• InfoCube Exceptions: Occurences (/OPT/CREXC02)
• MultiProvider Exceptions: Details (/OPT/MVEXC03)

16.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
customizing of the leading SAP ERP system.

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

VIM070000-RGD-EN-4 Reference Guide 129

Chapter 16 DataStore Objects (DSOs)

(/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.

Data Sources/Data Targets - As a source of the DSO, the Exception DataSource (/

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
1:1 mapping into the DSO.

As a target of the DSO, the InfoObject Exception ID (/OPT/CEXCEPT) is supplied.

Additionally, the active table of the DSO is used within transformations to
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
customizing of the leading SAP ERP system.

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.

130 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

16.2. DSOs of the Corporate Memory Layer

As a target of the DSO, the InfoObject Time Type (/OPT/CTIMETY) is supplied.

Additionally, the active table of the DSO is used within transformations to
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.

16.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.

16.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
1:1 mapping into the DSO.

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.

Data Sources/Data Targets - As a source of the DSO, the Exception 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.

VIM070000-RGD-EN-4 Reference Guide 131

Chapter 16 DataStore Objects (DSOs)

16.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

132 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

16.2. DSOs of the Corporate Memory Layer

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
mapping into the DSO.

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.

VIM070000-RGD-EN-4 Reference Guide 133

Chapter 16 DataStore Objects (DSOs)

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.

Data Sources/Data Targets - As a source of the DSO, the Exception 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
mapping into the DSO.

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
mapping into the DSO.

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
corresponding DataSource.

134 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

16.2. DSOs of the Corporate Memory Layer

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
corresponding DataSource.

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
corresponding DataSource.

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
mapping into the DSO.

As a target of the DSO, the InfoObject Vendor Group (/OPT/CVENDGR) is supplied.

VIM070000-RGD-EN-4 Reference Guide 135

Chapter 17
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?

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 137

Chapter 17 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_GLOBAL 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.

Example: List of all DP documents with document type NPO_GLOBAL and channel ICC
to 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.

Example: List of all DP documents with document type NPO_GLOBAL and channel ICC
to vendor 1000 that had the exception Missing Item Quantity (PO).

138 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Part 3
Transactions and Roles
Part 3 Transactions and Roles

This part provides information about the transaction codes that various roles have
access to.

140 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 18

Transaction Profiles for Various Roles

The following table shows domains, transactions, and the roles that have access to
the transactions.

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
Integrated
VIM /OPT/VIM_IIC Invoice Cockpit X X X 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
Central Audit
VIM /OPT/VIM_AUDIT Report X X
Exception
VIM /OPT/VIM_EXCP1 Analysis Report X X

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 141

Chapter 18 Transaction Profiles for Various Roles

Transaction Description 1 2 3 4 5 6 7 8 9
Key Process
Analytics
VIM /OPT/VIM_KPA1 Report X X
VIM /OPT/VIM_LICENSE License Report X X
Productivity
VIM /OPT/VIM_PROD1 Report X 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
/OPT/VIM_7CX1 baseline COA
VIM /OPT/AR_COA maintenance X X
Maintain
notification
VIM /OPT/VIM_8AX50 settings for me
/OPT/
VIM VIM_ANALYTICS VIM Analytics X X X X X X X X
Display special
handling
VIM /ORS/DISP_SH instructions X X X X X
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

142 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Transaction Description 1 2 3 4 5 6 7 8 9
Cancel PO
/PTGWFI/ invoice, re-enter
VIM CANC_INV_05 PO X X
Cancel PO
/PTGWFI/ invoice, re-enter
VIM CANC_INV_06 Non-PO X X
Delete Non-PO
/PTGWFI/ invoice, re-enter
VIM DEL_INV_01 Non-PO X X
Delete Non-PO
/PTGWFI/ invoice, re-enter
VIM DEL_INV_02 PO X X
Delete PO
/PTGWFI/ invoice, re-enter
VIM DEL_INV_03 PO X X
Delete PO
/PTGWFI/ invoice, re-enter
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
/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

VIM070000-RGD-EN-4 Reference Guide 143

Chapter 18 Transaction Profiles for Various Roles

Transaction Description 1 2 3 4 5 6 7 8 9
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
SAP SQ* SAP query X
SAP SCATT Test procedures X
SAP SHDB, SM35, SM35P BDC analysis X
OAWS, OAWD,
OAC2, OAC3, OAC0,
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

144 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Transaction Description 1 2 3 4 5 6 7 8 9
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

VIM070000-RGD-EN-4 Reference Guide 145

Part 4
Business Rules
Part 4 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.

148 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 19
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.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 149

Chapter 20
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.

20.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.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 151

Chapter 20 Business Rules for PO Invoices

20.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.

Technical FM /OPT/VIM_DETERMINE_PROC_201
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.

20.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.

Technical FM /OPT/VIM_DETERMINE_PROC_103
information
The UOM is compared with the values in table field T006-MSEHI.

152 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.4. Invalid Currency (PO)

20.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
taken and the document proceeds to the next logical step.
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
the pre-configured agent depending on the role for further action.

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.

20.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.

VIM070000-RGD-EN-4 Reference Guide 153

Chapter 20 Business Rules for PO Invoices

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.

Configuration Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > General Configuration > Maintain
Duplicate Check Procedures

20.6 PO Not Released or Incomplete

This specific business rule checks whether a PO is released or incomplete. There can
be two scenarios as described in the following:

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.

Technical FM /OPT/VIM_DETERMINE_PROC_106
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.

20.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.

154 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.8. Unable to Determine PO Line Number (PO)

Technical FM /OPT/VIM_DETERMINE_PROC_107
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).

20.8 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
depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_POL
information
Item data of the PO is read from table /OPT/VIM_1ITEM.

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.

VIM070000-RGD-EN-4 Reference Guide 155

Chapter 20 Business Rules for PO Invoices

• 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
• 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.

156 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.9. Manual Check Needed for Indexing Lines (PO)

20.9 Manual Check Needed for Indexing Lines (PO)

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.

There can be two scenarios as described in the following:

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
proceeds to the next logical step.

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
• PO item
• Delivery Note/GR Reference Document
• Quantity
• Amount
• UOM

VIM070000-RGD-EN-4 Reference Guide 157

Chapter 20 Business Rules for PO Invoices

• Net price

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.

Customizing To deploy this business rule, import and activate the BC set /
point OTEXVIM/VIM52PO_LINE_MATCHING.

20.10 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
action is taken and the document proceeds to the next logical step.

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.

158 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.11. Invalid Vendor VAT Number (PO)

20.11 Invalid Vendor VAT Number (PO)

When this business rule is applied, the supplier VAT number provided on the
invoice must match with the vendor master VAT Number provided in SAP ERP.
The following scenarios are possible:

Match
The supplier VAT number provided on the invoice matches with the VAT
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 number provided on the invoice does not match with the
VAT 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.
Not present
If the supplier’s VAT number is not present on the invoice, 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.

Technical FM /OPT/VIM_DETERMINE_PROC_120
information
The Vendor VAT number is read from the Vendor Master Data (table LFA1) and
compared with the VAT number given in the invoice. If no match, the Vendor VAT
number is read from the Vendor Master Data extension table LFAS. If no match ->
Exception

20.12 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
the next logical step.
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

VIM070000-RGD-EN-4 Reference Guide 159

Chapter 20 Business Rules for PO Invoices

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-
configured agent depending on the role for further action.

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

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.

160 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.13. Vendor Address Mismatch (PO)

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.

20.13 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
automatically routed to the pre-configured agent depending on the role for
further action.

The following SAP vendor address fields are matched:

• House #
• Street
• Postal Code
• City
• Region
• Country

Technical FM /OPT/VIM_DETERMINE_PROC_122
information

20.14 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.

VIM070000-RGD-EN-4 Reference Guide 161

Chapter 20 Business Rules for PO Invoices

Not entered
The exception Missing Item Quantity (PO) is raised and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_123
information
Field quantity of each line item in the indexing data is checked. If not filled ->
Exception

20.15 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.

20.16 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
No action is taken and the document proceeds to the next logical step.

Not entered
The exception Missing Invoice Date (PO) 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.17 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:

162 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.17. Invalid Tax Info (PO)

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-
configured agent depending on the role for further action.

Example: The payable VAT % or VAT amount is not present on the vendor’s invoice.

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:

VIM070000-RGD-EN-4 Reference Guide 163

Chapter 20 Business Rules for PO Invoices

• 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
• 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.

164 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.18. Missing Date of Supply (PO)

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.

20.18 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
taken and the document proceeds to the next logical step.

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
automatically routed to the pre-configured agent depending on the role for
further action.

Technical Field SUPPLY_DATE must be filled. If not, the exception is raised.

information

20.19 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

No action is taken and the document proceeds to the next logical step.

ISR number present and not matching

The exception ISR Number Mismatch (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
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
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_129
information

VIM070000-RGD-EN-4 Reference Guide 165

Chapter 20 Business Rules for PO Invoices

• 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.
• Since VIM 5.2 SP6, 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.

20.20 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
routed to the pre-configured agent depending on the role for further action.

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
routed to the pre-configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_128
information
For all countries except Austria, the check is carried out in the following logic:

• If the field Recipient VAT number is blank -> Exception

166 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.21. Payment Terms Mismatch (PO)

• 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).

20.21 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
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_130
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.

VIM070000-RGD-EN-4 Reference Guide 167

Chapter 20 Business Rules for PO Invoices

20.22 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
the next logical step.
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
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_229
information
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.

20.23 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
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_132
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

168 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.24. Vendor Invoice Reference Missing (PO)

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.

20.24 Vendor Invoice Reference Missing (PO)

The supplier invoice should have the invoice number mentioned on the invoice.
There can be two scenarios as described in the following:

Invoice number present

The invoice number on the vendor’s invoice is present. In this case, no action is
taken and the document proceeds to the next logical step.

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

20.25 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
described in the following:

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
action is taken and the document proceeds to the next logical step.

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
routed to the pre-configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_134
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).

VIM070000-RGD-EN-4 Reference Guide 169

Chapter 20 Business Rules for PO Invoices

If the payment method does not match, the exception is raised.

20.26 Missing/Invalid Tax Exempt Text (PO)

Technical FM /OPT/VIM_DETERMINE_PROC_135
information
The exception is raised in 2 cases:

• If the tax rate = 0 and the field Tax Exempt Text is blank.
• If the tax rate > 0 and the field Tax Exempt Text is filled with text.

20.27 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
invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_136
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.

20.28 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
taken and the document proceeds to the next logical step.

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
automatically routed to the pre-configured agent depending on the role for
further action.

170 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.29. Missing Mandatory Information (PO)

Technical FM /OPT/VIM_DETERMINE_PROC_137
information
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.

20.29 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
role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_138
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.

VIM070000-RGD-EN-4 Reference Guide 171

Chapter 20 Business Rules for PO Invoices

20.30 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
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_139
information

20.31 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
configuration. In the following, some of the possible scenarios are described:

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
automatically routed to the pre-configured agent depending on the role for
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:

172 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.31. 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
the pre-configured agent depending on the role for further action.

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.

VIM070000-RGD-EN-4 Reference Guide 173

Chapter 20 Business Rules for PO Invoices

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.

20.32 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
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_151
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.

174 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.33. Vendor Maintenance (PO)

20.33 Vendor Maintenance (PO)

This business rule is not in use yet.

20.34 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
the next logical step.
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
the invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_153
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.

20.35 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
proceeds to the next logical step.
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-
configured agent depending on the role for further action.

VIM070000-RGD-EN-4 Reference Guide 175

Chapter 20 Business Rules for PO Invoices

Technical FM /OPT/VIM_DETERMINE_PROC_154
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, the two Z constants SERVICE_ENTRY_BSTYP and
SERVICE_ENTRY_BSART (product code 005) are not used any more.

20.36 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
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_155
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.

20.37 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
the next logical step.
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
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

176 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.38. Approval Required (PO)

Technical FM /OPT/VIM_DETERMINE_PROC_156
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: Line items with qualifiers (additional costs) are not
considered for UOM matching because they are line items that transport costs only.

20.38 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.

Technical FM /OPT/VIM_DETERMINE_PROC_150
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.

20.39 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
scenarios as described in the following:

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
taken and the document proceeds to the next logical step.

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-
configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_157
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

VIM070000-RGD-EN-4 Reference Guide 177

Chapter 20 Business Rules for PO Invoices

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.

20.40 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
document proceeds to the next logical step.
Tax audit required
The vendor is subjected to tax audit. An exception Tax Audit Required (PO) is
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_158
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
• run the /n/OPT/VIM transaction and navigate to OpenText Vendor Invoice
Management > SAP menu > Customization > Tax Audit Configuration for PO
Invoices.

20.41 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
scenarios as described in the following:

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
automatically routed to the pre-configured agent depending on the role for
further action.

178 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.42. PO Credit Memo Processing (PO)

Technical FM /OPT/VIM_DETERMINE_PROC_303
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.

20.42 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
described in the following:

Not a Credit Memo

If the invoice is not a Credit Memo, no action is taken and the document
proceeds to the next logical step.
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
depending on the role for further action.

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.

20.43 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
two scenarios as described in the following:

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-
configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_161
information
If the Company Code field in the header is not filled, no matching is executed. No
exception is raised.

VIM070000-RGD-EN-4 Reference Guide 179

Chapter 20 Business Rules for PO Invoices

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.

20.44 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
the pre-configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_162
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

20.45 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.

Technical FM /OPT/VIM_DETERMINE_PROC_176
information

180 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20.46. Missing Invoice Code (PO)

20.46 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-
configured agent depending on the role for further action.

Technical To use this business rule, the INVOICE_CODE field must be configured as required
information field.

20.47 Invalid Invoice Code Format (PO)

Technical FM: /OPT/VIM_DETERMINE_PROC_173

information

20.57 Missing Vendor Name (PO)

If the Vendor Name (VEND_NAME) field is empty, the exception Missing Vendor Name
(PO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical To use this business rule, the VEND_NAME field must be configured as required field.
information

20.58 Missing Recipient Name (PO)

Technical FM: /OPT/VIM_DETERMINE_PROC_194

information

Net Amount (PO)
This business rule is valid for documents that are subject to withholding tax. If the
withholding tax base amount is bigger than the total net amount, the exception is
raised.

Technical FM: /OPT/VIM_DETERMINE_PROC_402

information

190 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 21
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.

21.1 Invalid Vendor (NPO)

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 (NPO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_201

information
For more information, see “Invalid Vendor (PO)” on page 152.

21.2 Invalid Currency (NPO)

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
taken, and the document proceeds to the next logical step.

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
the pre-configured agent depending on the role for further action.

Technical Field WAERS is checked against SAP table TCURC.

information

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 191

Chapter 21 Business Rules for NPO Invoices

21.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
invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_203

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

21.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
the next logical step.

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
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_DUP

information
For more information, see “Suspected Duplicate (PO)” on page 153.

192 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

21.5. Non-PO Credit Memo Processing

21.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.

21.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.

Technical FM: /OPT/VIM_DETERMINE_PROC_209

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.

21.7 Invalid Vendor VAT Number (NPO)

When this business rule is applied, the supplier VAT number provided on the
invoice must match with the vendor master VAT Number provided in SAP ERP.
The following scenarios are possible:

Match
The supplier VAT number provided on the invoice matches with the VAT
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 number provided on the invoice does not match with the
VAT number mentioned in the vendor master in SAP ERP. The exception
Invalid Vendor VAT Number (NPO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.

Not present
If the supplier VAT number is not present on the invoice, the exception Invalid
Vendor VAT Number (NPO) is raised, and the invoice is automatically routed to
the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_120

information
For more information, see “Invalid Vendor VAT Number (PO)” on page 159.

VIM070000-RGD-EN-4 Reference Guide 193

Chapter 21 Business Rules for NPO Invoices

21.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
described in the following:

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
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
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
routed to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_121

information
For more information, see “Incomplete Credit Memo (PO)” on page 159.

21.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
automatically routed to the pre-configured agent depending on the role for
further action.

The following SAP ERP vendor address fields are matched:

• House #

194 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

21.10. Missing Invoice Date (NPO)

• Street
• Postal Code
• City
• Region
• Country

Technical FM: /OPT/VIM_DETERMINE_PROC_122

information

21.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
action is taken, and the document proceeds to the next logical step.

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

21.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
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 corresponding
valid SAP tax information. The exception Invalid Tax Info (NPO) is raised,

VIM070000-RGD-EN-4 Reference Guide 195

Chapter 21 Business Rules for NPO Invoices

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 (NPO) is raised, and the document is automatically routed to the pre-
configured agent depending on the role for further action.

Example: The payable VAT % or VAT amount is not present on the vendor’s invoice.

Technical FM: /OPT/VIM_DETERMINE_PROC_126

information
For more information, see “Invalid Tax Info (PO)” on page 162.

21.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:

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
routed to the pre-configured agent depending on the role for further action.

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
routed to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_128

information
For more information, see “Invalid Recipient VAT Number (PO)” on page 166.

196 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

21.13. ISR Number Mismatch (NPO)

21.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
automatically routed to the pre-configured agent depending on the role for
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
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_129

information
For more information, see “ISR Number Mismatch (PO)” on page 165.

21.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
described in the following:

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
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 vendor master in SAP ERP. The exception
Payment Terms Mismatch (NPO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_130

information
For more information, see “Payment Terms Mismatch (PO)” on page 167.

VIM070000-RGD-EN-4 Reference Guide 197

Chapter 21 Business Rules for NPO Invoices

21.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
taken, and the document proceeds to the next logical step.
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
automatically routed to the pre-configured agent depending on the role for
further action.

Technical The field SUPPLY_DATE must be filled. If it is not, the exception is raised.
information

21.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
the next logical step.
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
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_229

information
For more information, see “Invalid Siret Number (PO) (French)” on page 168

21.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

198 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

21.18. Vendor Invoice Reference Missing (NPO)

automatically routed to the pre-configured agent depending on the role for

further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_132

information
For more information, see “Invalid Company Address (PO)” on page 168.

21.18 Vendor Invoice Reference Missing (NPO)

The supplier invoice should have its invoice number mentioned on the invoice.
There can be two scenarios as described in the following:

Invoice number present

The invoice number on the vendor’s invoice is present. In this case, no action is
taken, and the document proceeds to the next logical step.

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
invoice is automatically routed to the pre-configured agent depending on the
role for further action.

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

21.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
described in the following:

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
action is taken, and the document proceeds to the next logical step.

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
routed to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_134

information
For more information, see “Payment Method Mismatch (PO)” on page 169.

VIM070000-RGD-EN-4 Reference Guide 199

Chapter 21 Business Rules for NPO Invoices

21.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.

Technical FM: /OPT/VIM_DETERMINE_PROC_209

information
Customization Run the /n/OPT/VIM transaction and navigate to SAP menu > Customization >
point Utility Vendors.

21.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.
• If the tax rate > 0 and the Tax Exempt Text field is filled with text.

Technical FM: /OPT/VIM_DETERMINE_PROC_135

information

21.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
the invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_136

information
For more information, see “Missing Import Special Text (PO)” on page 170.

200 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

21.23. Missing Item Description (NPO)

21.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
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
taken, and the document proceeds to the next logical step.

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
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_137

information
For more information, see “Missing Item Description (PO)” on page 170.

21.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.

Technical FM: /OPT/VIM_DETERMINE_PROC_138

information
For more information, see “Missing Mandatory Information (PO)” on page 171.

VIM070000-RGD-EN-4 Reference Guide 201

Chapter 21 Business Rules for NPO Invoices

21.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
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_139

information
For more information, see “Missing/Invalid Triangulation Text (PO)” on page 172.

21.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
automatically routed to the pre-configured agent depending on the role for
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:

202 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

21.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
the pre-configured agent depending on the role for further action.

• 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 172.

Customization Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > Document Type Configuration > Specific
Country Settings > Canada.

21.27 Non PO Approval Required (NPO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_250

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.

VIM070000-RGD-EN-4 Reference Guide 203

Chapter 21 Business Rules for NPO Invoices

In the Expense Type Definition Maintenance (View), you can maintain whether
Approval is required for a specific Expense Type.

21.28 Vendor Audit Required (NPO)

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 (NPO) is
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_151

information
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.

For more information, see “Vendor Audit Required (PO)” on page 174.

21.29 Tax Audit Required (NPO)

No tax audit required

The vendor is not subjected to tax audit. In this case, no action is taken, and the
document proceeds to the next logical step.
Tax audit required
The vendor is subjected to tax audit. An exception Tax Audit Required (NPO) is
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_258

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”.

204 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

21.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.

21.30 Validate Bank Details (NPO)

If invalid bank data is received, the exception Validate Bank Details (NPO) is
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_270

information

21.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_GLOBAL, 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_GLOBAL but it is not activated.

Technical FM: /OPT/VIM_DETERMINE_PROC_LIB004

information

VIM070000-RGD-EN-4 Reference Guide 205

Chapter 21 Business Rules for NPO Invoices

21.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
the invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_176

information

21.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-
configured agent depending on the role for further action.

Technical To use this business rule, the INVOICE_CODE field must be configured as required
information field.

21.34 Invalid Invoice Code Format (NPO)

21.43 Missing Vendor Name (NPO)

If the Vendor Name (VEND_NAME) field is empty, the exception Missing Vendor Name
(NPO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical To use this business rule, the VEND_NAME field must be configured as required field.
information

21.44 Missing Recipient Name (NPO)

This section describes general business rules that are independent from NPO or PO.

22.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.

22.2 Check Inbound Interface Errors

222 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 24
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.

24.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.

Technical FM: /OPT/VIM_DETERMINE_PROC_LIB001

information

24.2 Check Balance

This function executes a balance check. You find details in the function module.

Technical FM: /OPT/VIM_DETERMINE_PROC_LIB002

information

24.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.

Technical FM: /OPT/VIM_DETERMINE_PROC_LIB003

information

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 223

Part 5
Automated Field Enhancement
Part 5 Automated Field Enhancement

VIM 7.0 introduces a new 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.

226 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 25
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
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).

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 229 shows
the relation between source fields and target fields.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 227

Chapter 26

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

Mapping ID Type Sources Target field Function module

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

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 229

Chapter 26 Baseline of Automated Field Enhancement

Mapping ID Type Sources Target field Function module

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

230 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Mapping ID Type Sources Target field Function module
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

Mapping ID Type Sources Target field Function module

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
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

VIM070000-RGD-EN-4 Reference Guide 231

Chapter 26 Baseline of Automated Field Enhancement

Mapping ID Type Sources Target field Function module

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

232 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Part 6
Z Constants
Part 6 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

234 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 27
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

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 235

Chapter 27 Z Constants for Product Code 002 and 009

Product Constant Description Default Value

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

236 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
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 18.4 “Defining Action Authority Groups for the
VIM Workplace” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
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

VIM070000-RGD-EN-4 Reference Guide 237

Chapter 28
Z Constants for Product Code 005

Product Constant Description Default Value

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.13.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.13.9 “Maintaining a Function Module for
Customer Specific Unplanned Cost Matching” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
Process Type for
005 AFTCS_PROCESS_TYPES AFTCS File 141,241
For more information, see Section 15.4 “Z Constants” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
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

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 239

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
For more information, see Section 13.6.8.1 “Defining Resubmit for Approval
Action Codes” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
URL to show
Configuration
Documentation for
Document
Processing
005 APP_DOCU_URL Application http://www.opentext.com
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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.
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 trigger
redetermination of
005 AR_OBJECT_TRIG_FM archive doc type
Template for this function module is /OPT/VIM_AR_OBJECT_TRIG_TEMPLT.
For more information, see Section 9.1.7 “Mapping ArchiveLink Document Types”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
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.

240 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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.9.3 “Enhancing MIRO for Pre-population of
Data During Online Invoice Creation” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide (VIM-CGD).
Start VIM process
in Central System
005 CENTRAL_VIM_PROCESS always
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. The
constant is called in the following code pieces:
• Report /OPT/VIM_DP_TRIGGER to trigger a DP process from IDH (ICC)
Admin tool.
• 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.
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

VIM070000-RGD-EN-4 Reference Guide 241

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
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 24.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 to
manipulate data
005 CUSTOM_FM_PLUGIN for BAPI Input
For more information, see Section 9.9.4 “Changing BAPI Configuration” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
User exit for
customer RFC
function to sort
documents for
005 CUSTOM_ICC_EX_SORT 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
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 to sort
documents for
005 CUSTOM_ICC_VA_SORT validation
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).
Display invoice
image on display
of dash board
DASHBOARD_IMAGE_AU screen(X- Yes,
005 TO space -No)

242 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
For more information, see Section 9.1.8 “Configuring Automatic Image Display”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
Display no Logo
005 DASHBOARD_NO_LOGO (Dashboard / IIC)
For more information, see Section 18.2.2.2 “Enhanced Application” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
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.
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)
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. The constant has been
introduced in VIM 6.0 SP3.
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. The constant has been
introduced in VIM 6.0 SP3.

VIM070000-RGD-EN-4 Reference Guide 243

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
Delay trigger
Approval
Workflow (number
entered is
multiplied by 5
005 DELAY_IAP_EVENT_CREA seconds) 3
This constant has been introduced in VIM 7.0 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
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 244.
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 244.
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.

244 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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
Management for SAP Solutions - Configuration Guide (VIM-CGD).
DP Doc type for
Down Payments
005 DOCTYPE_DWN w/o DP workflow DWN_GLOBAL
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_GLOBAL
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_GLOBAL
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_GLOBAL
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) 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

VIM070000-RGD-EN-4 Reference Guide 245

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
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
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).
OCR Extraction/
005 DP_EX_VA_ERROR Validation is Error Error
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).
OCR Extraction/
005 DP_EX_VA_REJECT Validation is Reject Reject
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).
OCR Extraction/
Validation is
005 DP_EX_VA_SUCCESS Success Ok
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).
Exit FM to add/
change data in
BAPI structures
(EX:/OPT/
DNONPO_INVOI
005 DP_NPO_POSTING_EXIT CE_BAPI_EXIT)
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Set to X to prevent
from simulating all
rules at DP WF
005 DP_START_NO_ALLRULES start
Starting with VIM 5.2 SP8 / VIM 6.0 SP3, all business rules are run at the
beginning of the DP process to collect the information for the new logging
infrastructure. If this is causing performance problems, to switch off the
simulation of all business rules, set this constant value to X.

246 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
Process Code to
control parallel DP
005 DP_SYNC_PROC trigger process X
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).
Refresh DP Sync
005 DP_SYNC_REFRESH_TAB table X
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).
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
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Extended IIC:
Function module to
determine object
005 EIIC_DET_OBJ_KEY key
For more information, see Section 17.5.2 “Determining Key Fields of the Work
Items” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
Extended IIC:
Function module to
update customer
005 EIIC_UPD_CUSTFIELDS fields
For more information, see Section 17.6.2 “Updating Values of Customer-specific
Fields” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD).
Activate Buttons to
Call PO Line
005 ENABLE_MATCHING_SCR Proposal Screen X
For more information, see Section 9.9.2 “Enhancing the DP Dashboard” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).

VIM070000-RGD-EN-4 Reference Guide 247

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
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 165.
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.
The constant has been introduced in VIM 5.2 SP8/VIM 6.0 SP3.
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 175.
Move PO number
from list / item to
header in case of
005 FAIL_PO_HEADER_SET exception for PO
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.
This constant is introduced in VIM 7.0.
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.

248 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
Freight Amount
005 FREIGHT_AMOUNT tolerance 4
For more information, see
“Freight on Invoice (PO)”
on page 177.
Vendor Payment
005 GET_VEND_PAYM_BLOCK Block Indicators A,B,P
For more information, see “Invalid Vendor (PO)” on page 152.
FM Exit to verify /OPT/
005 GR_CHECK_EXIT GR is done or not VIM_BL_CHECK_GR_EXIT
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
GR posting -
Movement
type( actual value
or FM to
determine(ex-
005 GR_MOVEMENT_TYPE FM:xxxxxxxx) ) 101
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Exit in GR post
BDC FM (Ex FM:/
OPT/
DPPO_GR_BAPI_P
005 GR_POST_BAPI_EXIT OST_EXIT)
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
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.

VIM070000-RGD-EN-4 Reference Guide 249

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
Delay before
sending document
to extraction,
format HHMMSS,
005 ICC_AR_DELAY 000500 = 5 min 0
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).
005 ICC_CHANNEL_ID ICC Channel ID ICC
For more information, see Section 16.3.3 “Maintaining Channel IDs” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
URL to show
Configuration
Documentation for
005 IMG_DOCU_URL IMG http://www.opentext.com
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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 181 and
“Invoice Older Than Allowed (NPO)” on page 207.
KPA Report:
Thresholds for
“First Pass” - Total
005 KPA_TS_1STPASS_NO #
For more information, see Section 26.11.1 “Constant KPA_TS_1STPASS_NO” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
KPA Report:
Thresholds for
“First Pass” -
005 KPA_TS_1STPASS_PERC Percentages
For more information, see Section 26.11.2 “Constant KPA_TS_1STPASS_PERC” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
KPA Report:
Thresholds for
“Total Liability” -
Amounts for
Blocked
005 KPA_TS_LIAB_AMOUNT1 Documents

250 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
For more information, see Section 26.11.3 “Constant KPA_TS_LIAB_AMOUNT1”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
KPA Report:
Thresholds for
“Total Liability” -
Amounts for
005 KPA_TS_LIAB_AMOUNT2 Parked Documents
For more information, see Section 26.11.4 “Constant KPA_TS_LIAB_AMOUNT2”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
KPA Report:
Thresholds for
“Total Liability” -
Amounts for Pre-
005 KPA_TS_LIAB_AMOUNT3 Process Documents
For more information, see Section 26.11.5 “Constant KPA_TS_LIAB_AMOUNT3”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
KPA Report:
Thresholds for
“Processed/In
Process
Documents” - Total
005 KPA_TS_PROCDOCS_NO #
For more information, see Section 26.11.6 “Constant KPA_TS_PROCDOCS_NO”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
KPA Report:
Thresholds for
“Processed/In
Process
Documents” -
005 KPA_TS_PROCDOCS_PERC Percentages
For more information, see Section 26.11.7 “Constant
KPA_TS_PROCDOCS_PERC” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM-CGD).
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.

VIM070000-RGD-EN-4 Reference Guide 251

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
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
Processing
005 MAIN_WF_TEMPLATE WS99680010 WS00275269
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD) and Section 16.4.1 “Maintaining the Default Workflow Template” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Continue After
005 MAP_ERROR_CONTINUE mapping Error
Custom Number
Range Object for
Document
005 NUMBER_RANGE_OBJECT Processing
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Package Size for
Purchase Order
005 PO_REC Download 50000

252 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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).
Document Data
Preprocess Exit
005 PREPROCESS_EXIT_FM Function Module
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD) and Section 16.4.2 “Maintaining the Preprocess Exit” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
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
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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.
Reminder mail
formatting exit
005 REM_MAIL_FORMAT_FM function
For more information, see Section 31.4 “Maintaining a Notification Email
Formatting Function Module” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM-CGD).

VIM070000-RGD-EN-4 Reference Guide 253

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

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.
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
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.
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 155.
If set to 'N', invoice
items will not be
synced with RSEG
005 SYNC_ITEM_PARKED_PO after parking (PO) N

254 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
Setting N can be used if you want to keep the items unchanged in the DP
document after parking.
If set to 'N', invoice
items will not be
synced with RSEG
005 SYNC_ITEM_POSTED_PO after posting (PO) N
Setting N can be used if you want to keep the items unchanged in the DP
document after posting.
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
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).
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.
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 -
Configuration Guide (VIM-CGD).
005 VALIDATOR_ROLE Validator Role VALIDATOR
For more information, see Section 16.3.5 “Assigning Validation Agents” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Package Size for
005 VEND_REC Vendor Download 50000
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).

VIM070000-RGD-EN-4 Reference Guide 255

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
FM for Dashboard
Workitem Text: /
OPT/ /OPT/
BL_IF_DETERMIN BL_IF_DETERMINE_WI_TE
005 WI_TEXT_FM E_WI_TEXT XT
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
If set to 'X', archive
document id for
XML will be
assigned via RFC
005 XML_AR_ASSIGN_LATE from ICC X
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).
Content Repository
for XML Document
(if not defined in
005 XML_AR_CONTREP OAC3)
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).
If set to 'X', XML
document in
archive will be
deleted as soon as
005 XML_AR_DELETE_EARLY possible X
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).
Archive Object for
005 ADDL_DOCS_AR_OBJECT Other attachments /OPT/OTHER
For more information, see “Interface Remote Function 2” on page 16.
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

256 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Task number of the
DP_DASHBOARD_TASK_I DP document
005 D dashboard TS00275278
Delimiter for
005 DUP_CHECK_DELIMIT duplicate check /-
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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
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 -
Configuration Guide (VIM-CGD).

VIM070000-RGD-EN-4 Reference Guide 257

Chapter 28 Z Constants for Product Code 005

Product Constant Description Default Value

Code
Invoice statuses
that need workflow
to be started -
005 LIST_WF_STATUSES VIM5 A
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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
Solutions - Configuration Guide (VIM-CGD).
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 168.
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
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
The plants for
which workflows
will be triggered; *
means all plants. -
005 WFTRGPLANT VIM5 *
For more information, see Section 9.11 “Configuring Global Parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).

258 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 29
Z Constants for Product Code IAP

Product Constant Description Default Value

Code
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. The constant
is introduced in VIM 5.2 SP7.
Flag for copying
user to COA-table
with no approval
IAP APPR_USR_COA_COPY limit X
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.
BDC Function to /ORS/
Be Called to Write 000007_NPO_SAVE_CODIN
IAP BDC_FUNCTION to Database G
For more information, see Section 5.7.3 “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.13.5 “Configuring the Bulk Approval
Validation Exit” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
Calculate tax on
net amount option
for DP approval
IAP CALC_TAX_ON_NET ('X' or ' ' or 'D')

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 259

Chapter 29 Z Constants for Product Code IAP

Product Constant Description Default Value

Code
For more information, see Section 13.6.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.6.11 “Configuring the Certify Message” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Extended COA line
check for next
approver
determination ('' =
IAP COA_LINE_CHECK_EXT off, 'X' = on)
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. The constant
has been introduced in VIM 5.2 SP10.
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.

The constant is introduced in VIM 7.0 SP2.

IAP DASHBOARD_NO_LOGO Display no Logo
If this constant is set to X, the logo is hidden in the Approval dashboard. The
constant is introduced in VIM 5.2 SP10.
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.

260 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
DP Invoice
approval - Is
validation required
DP_APPROVAL_VALIDAT or not, when data
IAP E is saved?(X- No)) X
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.
This constant has been introduced in VIM 7.0 SP2.
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.
This constant has been introduced in VIM 7.0 SP2.
Search help user /ORS/
exit with Pre-filled SEARCH_HELP_FIELDS_PR
IAP EXIT_SEARCH_HELP_FLT values EFIL
For more information, see Section 10.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
EXT_IE_RPT_LIX_
IAP EXT_IE_RPT_LIX_BIND BIND
Override Coding
IAP GL_ACC_SCR_EXIT Fileds attributes
Evaluation Path
IAP HR_EVALUATION_PATH Maintenance

VIM070000-RGD-EN-4 Reference Guide 261

Chapter 29 Z Constants for Product Code IAP

Product Constant Description Default Value

Code
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
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD). The
constant is introduced in VIM 7.0 SP2.
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.
Number of days to
wait for the Referee
to provide
IAP REFERRAL_WAIT_TIME information 10

262 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
For more information, see Section 13.6.8.3 “Configuring the Referral Wait Time”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
2 fields: rejection
rsn ; comments( 1 =
mandatory and 0 =
IAP REJECTION_REASON optional) 1;1
For more information, see Section 13.6.7 “Defining Rejection Reasons” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (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.
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.
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

VIM070000-RGD-EN-4 Reference Guide 263

Chapter 29 Z Constants for Product Code IAP

Product Constant Description Default Value

Code
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
For more information, see Section 13.13.2 “Defining the Custom Approver Class”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).

Note: This constant is used only for the “old” simple approval workflow,
known from versions of VIM before 7.0. However, it is also used in VIM 7.0
if no approval flow settings are found for the DP document type.
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.
R=by requester ID;
C=by company
code; B=by both R
and C; S=use
IAP CODER_DETERMING requester R

264 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
For more information, see Section 13.7.1 “Configuring the Coder Role” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
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.10.3 “Optional Coding” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Exit function for
IAP EXIT_INVOICE_ACTION Invoice Action /OPT/OAP_EXIT_ACTION
For more information, see Section 13.6.12.3 “Configuring Exits” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Exit function for
IAP EXIT_INVOICE_DETAIL Invoice Detail /OPT/OAP_EXIT_DETAIL
For more information, see Section 13.6.12.3 “Configuring Exits” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Exit function for
IAP EXIT_INVOICE_LIST Invoice List /OPT/OAP_EXIT_LIST
For more information, see Section 13.6.12.3 “Configuring Exits” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Extended Ext_data
Class /ors/ext_data
IAP EXT_DATA_CLASS when not extension /ORS/EXT_DATA
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

VIM070000-RGD-EN-4 Reference Guide 265

Chapter 29 Z Constants for Product Code IAP

Product Constant Description Default Value

Code
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.13.1 “Configuring Image Display” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
/ORS/
Image Display 000007_TMP_IMAGE_DISP_
IAP IMAGE_DIS_URL_FM URL generate FM URL
For more information, see Section 13.13.1 “Configuring Image Display” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).

266 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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.6.8.2 “Defining Supported Currency and
Language” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD) and Section 10.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
For more information, see Section 13.10.1 “BAdI Validation for Parked Non PO
Invoices” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM-CGD) and Section 13.13.3 “Defining the Custom Invoice Class” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).

Note: This constant is used only for the “old” simple approval workflow,
known from versions of VIM before 7.0. However, it is also used in VIM 7.0
if no approval flow settings are found for the DP document type.
E=eamil ID;
S=sequence #;
N=.NET ID and
IAP OPTUSERID_DETERMING Domain; P=EP6 ID E
Popup window to
display company
code selection for /ORS/
cross company 000007_POPUP_COMPANY
IAP POPUP_COMPANY_CODE invoice approve _CODE

VIM070000-RGD-EN-4 Reference Guide 267

Chapter 29 Z Constants for Product Code IAP

Product Constant Description Default Value

Code
For more information, see Section 13.6.9 “Cross Company Coding” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Extended PO
Invoice Class
(Called in
Approval =>
GET_PO_INV_CL
IAP PO_INV_CLASS ASS) /ORS/PO_INVOICE_NEW
For more information, see Section 13.13.3 “Defining the Custom Invoice Class” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).

Note: This constant is used only for the “old” simple approval workflow,
known from versions of VIM before 7.0. However, it is also used in VIM 7.0
if no approval flow settings are found for the DP document type.
/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.6.7 “Defining Rejection Reasons” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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.
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.6.8.1 “Defining Resubmit for Approval
Action Codes” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).

268 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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
This constant sets the class that is used to map internal VIM users to SAP and
portal users, and to perform user search and other functions.

For more information, see Section 13.13.4 “Defining a Custom Usermap Class” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).

Note: This constant is used only for the “old” simple approval workflow,
known from versions of VIM before 7.0. However, it is also used in VIM 7.0
if no approval flow settings are found for the DP document type.
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

VIM070000-RGD-EN-4 Reference Guide 269

Chapter 30
Z Constants for Product Code IEA

Product Constant Description Default Value

Code
PAI exit in Log
IEA PAI_EXIT_9204_CIV Screen (9204) LIV /ORS/IEA_9204_PAI_EXIT
Since VIM 5.2 SP7, 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
Since VIM 5.2 SP7, it is possible to display all log entries of the pre-processes in
the SAP GUI 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
Since VIM 5.2 SP7, 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.
PBO exit in Log
IEA PBO_EXIT_9204_LIV Screen (9204) LIV /ORS/IEA_TEMP_LOG
Since VIM 5.2 SP7, it is possible to display all log entries of the pre-processes in
the SAP GUI 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
program for /PTGWFI/
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
program for /PTGWFI/
IEA UDB_SUBSCRN_PROG_LIV invoice info. IEA_SUBSCREEN_PROG

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 271

Chapter 30 Z Constants for Product Code IEA

Product Constant Description Default Value

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

272 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 31

Z Constants for Product Code IEM

Product Constant Description Default Value

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
UserExit for /
PTGWFI/
IE_MONITOR_NE
IEM PBO W /ORS/IEM_RPT_EXIT_PBO
Constant for
determining due
IEM CALCULATE_DUEDATE date FM
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
/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

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 273

Chapter 31 Z Constants for Product Code IEM

Product Constant Description Default Value

Code
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

274 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 32
Z Constants for Product Code KPI

Product Constant Description Default Value

Code
KPI CURR_CONVERSION_DAT Time for Currency F
E Conversion (T =
Today, P = Posting
Date, F = Fix day)
For more information, see Section 24.4.10.1 “Currency Conversion Date” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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 24.4.10.2 “Currency Conversion Day” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
KPI DASHBOARD_HELP_URL Help URL for the
KPI Dashboard
For more information, see Section 24.4.10.3 “KPI Dashboard Help URL” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
KPI DASHBOARD_START_URL URL to the KPI http://<server>:<port>/sap/
Dashboard bc/webdynpro/opt/
vim_kpi_main
For more information, see Section 24.4.10.5 “KPI Dashboard Start URL” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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 24.4.10.6 “Company Code Authority Check” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
KPI FAVORITE_CURRENCY Favorite Currency EUR

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 275

Chapter 32 Z Constants for Product Code KPI

Product Constant Description Default Value

Code
For more information, see Section 24.4.6.2 “Maintaining Amount Classes” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD) and Section 24.4.10.7 “Favorite Currency” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
KPI FILTER_START_PERIOD Define the Start 201202
Period of the Filter
Options on the
Web Dashboard
For more information, see Section 24.4.10.8 “Filter Start Period” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
KPI KPI_VENDOR_CLASS Use KPI specific
vendor
classification (X = /
OPT/
KAGR_C_VNDP /
empty = LFM1)
For more information, see Section 24.4.5.2 “Mapping Vendor Groups” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD) and Section 24.4.10.9 “Vendor Class” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
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 24.4.10.4 “KPI Dashboard Help URL with
Multi-language Support” in OpenText Vendor Invoice Management for SAP Solutions
- Configuration Guide (VIM-CGD).

276 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 33
Z Constants for Product Code LIX

Product Constant Description Default Value

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
DASHBOARD_IMAGE_AU screen(X- Yes,
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
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.
Use old Delete and
Re-enter sequence
(duplicate error): 1.
LIX DELETE_ENTER_OLD Delete, 2. Re-enter

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 277

Chapter 33 Z Constants for Product Code LIX

Product Constant Description Default Value

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 180
and Section 28.2 “Determining Purchase Order Types” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
SRM- Mail
configuration ID
LIX SRM_QTY_BLK_MAIL_CID for Qunatity Block 2
For more information, see Section 28.3.2 “Quantity Discrepancy Scenario” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
WF relevant
LIX WFDOCTYPE document types *
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
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

278 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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 -
Configuration Guide (VIM-CGD).
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 -
Configuration Guide (VIM-CGD).
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 -
Configuration Guide (VIM-CGD).
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 -
Configuration Guide (VIM-CGD).
Execute
Transaction Code
in LIX Header
Level Worklfow
LIX HD_EXECTCODE_TASKID Task ID TS98600021
Header Level
HEADERLEVELWORKFLO Workflow ID
LIX W WS99680014 WS00275266
Function module to /PTGWFI/
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).

VIM070000-RGD-EN-4 Reference Guide 279

Chapter 33 Z Constants for Product Code LIX

Product Constant Description Default Value

Code
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
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Subscreen for LIV
LIX LIXDBSCREEN Dashboard 9902
For more information, see Section 11.3.1.2 “Header Level” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
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
Management for SAP Solutions - Configuration Guide (VIM-CGD).
Subscreen for
Logistic Invoice
LIX LIXSCREEN Resolution 9902
For more information, see Section 11.3.1.1 “Line Level” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).

280 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
Currency
conversion(I=Invoi
ce, P=PO , L=Local,
N=None)
(1=button, 0=no
LIX LIXSCREEN_CURR_CONV button) N0
For more information, see Section 11.3.1.1 “Line Level” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
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
PSS ( FM:) for FM FM:/ORS/
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
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

VIM070000-RGD-EN-4 Reference Guide 281

Chapter 33 Z Constants for Product Code LIX

Product Constant Description Default Value

Code
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 -
Configuration Guide (VIM-CGD).
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 -
Configuration Guide (VIM-CGD).
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 the
Integrated Invoice Cockpit.
Subscreen program
for Parked Invoice /PTGWFI/
LIX PRKPROG Resolution PRK_SUBSCREEN01
For more information, see Section 10.3.2 “Configuring Screen Exits” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Subscreen for
Parked Invoice
LIX PRKSCREEN Resolution 9901
For more information, see Section 10.3.2 “Configuring Screen Exits” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).

282 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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 -
Configuration Guide (VIM-CGD).
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 -
Configuration Guide (VIM-CGD).
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”
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 Inward /PTGWFI/
LIX PRK_PSS_BIND_FM1 Binding PRK_TMP_BIND_EXT_FM
For more information, see Section 10.3.5 “Configuring Binding Function 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/
LIX PRK_PSS_BIND_FM2 Binding 000007_LIX_PSS_BIND_O

VIM070000-RGD-EN-4 Reference Guide 283

Chapter 33 Z Constants for Product Code LIX

Product Constant Description Default Value

Code
For more information, see Section 10.3.5 “Configuring Binding Function Exits” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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 -
Configuration Guide (VIM-CGD).
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 -
Configuration Guide (VIM-CGD).

284 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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 178, “Confirmation
Required from SRM (PO)” on page 180, and Section 28.2 “Determining Purchase
Order Types” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
SRM- Mail
configuration ID
LIX SRM_PRC_BLK_MAIL_CID for Price Block 3
For more information, see Section 28.3.3 “Price Discrepancy Scenario” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Proxy Role for
LIX SRM_PRC_BLK_PXY_ROLE Price Block AP_PROCESSOR
For more information, see Section 28.3.3 “Price Discrepancy Scenario” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Delay in minutes
for SRM Price
LIX SRM_P_BLK_DELAY Block 1
For more information, see Section 28.3.3 “Price Discrepancy Scenario” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).

VIM070000-RGD-EN-4 Reference Guide 285

Chapter 33 Z Constants for Product Code LIX

Product Constant Description Default Value

Code
SRM- Recipient /OPT/
Email ID FM for S_GET_SRM_USER_EMAIL_
LIX SRM_P_BLK_RCV_EML_FM price block ID
For more information, see Section 28.3.3 “Price Discrepancy Scenario” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
SRM Quantity
Block process type
(obsolate, replaced
by
SRM_BLK_PROCT
LIX SRM_QTY_BLK_PROCTYPE YPE) 162
For more information, see Section 28.3.2 “Quantity Discrepancy Scenario” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Proxy Role for
LIX SRM_QTY_BLK_PXY_ROLE Quantity Block AP_PROCESSOR
For more information, see Section 28.3.2 “Quantity Discrepancy Scenario” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
LIX SRM_SCENARIO_TYPE SRM Scenario Type EXTENDED_CLASSIC
For more information, see Section 28.3.4 “SRM Scenario Type” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
Function module to
be executed before
the TCode
Execution step is
LIX TCODE_BIND_EXIT_FM1 created
Function module to
be executed at the /ORS/
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
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 -
Configuration Guide (VIM-CGD).

286 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
FM to be called in
the User Exit to /PTGWFI/
collect data after PRK_M_GET_PARK_DATA
LIX USR_EXIT_GET_DATA_S Document Parking _S

VIM070000-RGD-EN-4 Reference Guide 287

Chapter 34

Z Constants for Product Code PIR

Product Constant Description Default Value

Code
Display invoice
image on display
of dash board
DASHBOARD_IMAGE_AU screen(X- Yes,
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
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.
WF relevant Doc
PIR WFDOCTYPE types *
PIR WFTRGPLANT Trigerring Plants *
Workitem Text
crreation FM (Refer
FM: /OPT/
BL_IF_SET_WI_TE
PIR WI_TEXT_FM XT)
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
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Exit for Running /OPT/
PIR AUTOPOST_RULES_EXIT Auto Post rules BL_AUTO_TEMPLATE

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 289

Chapter 34 Z Constants for Product Code PIR

Product Constant Description Default Value

Code
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 -
Configuration Guide (VIM-CGD).
Function module to /PTGWFI/
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
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;/PTGWFI/
PIR NONPO_INV_TCODE Invoices 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 -
Configuration Guide (VIM-CGD).

290 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
CGD).
Subscreen for
Parked Invoice
PIR PIRSCREEN Resolution 9901
For more information, see Section 12.2.2 “Configuring Dashboard Screen Exits” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-
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
PSS ( FM:) for FM FM:/ORS/
or can be direct BIR_T_GET_EXIT_SUBSCR
PIR PIR_PSS_EXIT_SUBS_NO value N
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

VIM070000-RGD-EN-4 Reference Guide 291

Chapter 34 Z Constants for Product Code PIR

Product Constant Description Default Value

Code
For more information, see Section 12.2.9 “Configuring a Parked Document
Posting Exit” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM-CGD).
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 -
Configuration Guide (VIM-CGD).
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”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(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 -
Configuration Guide (VIM-CGD).
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”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
Pre PSS screen
PIR PRE_PSS_METHOD_EXIT method exit(parke
For more information, see Section 12.2.5 “Configuring the Pre PSS Method Exit”
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 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).

292 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
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”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(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
Function module to
be executed at the /ORS/
end of the Tcode 000007_PIR_TCODE_BIND_
PIR TCODE_BIND_EXIT_FM2 Execution step O
FM to be called in
the User Exit to /PTGWFI/
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 -
Configuration Guide (VIM-CGD).

VIM070000-RGD-EN-4 Reference Guide 293

Chapter 34 Z Constants for Product Code PIR

Product Constant Description Default Value

Code
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

294 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Chapter 35
Z Constants for Product Code VAN

Product Constant Description Default Value

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 has been created in VIM 7.0 SP3 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
Approval flag:
'XX'=both, 'X '=PO
only, ' X'=NPO
APPROVAL_PO_NPO_FLA only, ' '=both not
VAN G include XX
/ORS/
000007_5_VIM_M
ONITOR_PLUG/
ORS/
000007_5_VIM_M /ORS/
ONITOR_PLUGCl 000007_5_VIM_MONITOR_
VAN APPROVAL_PROCESS_CL ass to process ORS PLUG

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 295

Chapter 35 Z Constants for Product Code VAN

Product Constant Description Default Value

Code
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
Calculate the
DueDate for table / /OPT/
VAN CALC_DUEDATE_FOR_DP opt/vim_hd_dp VIM_DP_CALC_DUEDATE
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
Tran code used to
display all LIV
invoices during
drilldown
VAN INVOICE_DISPLAY_LIV reporting MIR4
In some VIM reports (for example VIM Analytics and Integrated Invoice
Cockpit), 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.

296 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Product Constant Description Default Value
Code
Tran code used to
display parked CIV
invoice during
drilldown
VAN INVOICE_DISPLAY_PIR reporting FBV3
In some VIM reports (for example VIM Analytics and Integrated Invoice
Cockpit), 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
For more information, see Section 14.3.4 “Updating Table /PTGWFI/Z_CONST”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).
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
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.

VIM070000-RGD-EN-4 Reference Guide 297

Chapter 35 Z Constants for Product Code VAN

Product Constant Description Default Value

Code
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
For more information, see Section 14.1.3 “Updating Table /PTGWFI/Z_CONST”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM-CGD).

298 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

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.

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

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.

VIM070000-RGD-EN-4 OpenText Vendor Invoice Management for SAP Solutions 299

Glossary

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

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.

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.

300 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Glossary

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.

DataStore Object (DSO)

Storage location for consolidated and cleansed data in SAP NetWeaver BW

DocuLink

OpenText DocuLink enables the archiving, management and retrieval of CRM or

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).

VIM070000-RGD-EN-4 Reference Guide 301

Glossary

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

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

302 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Glossary

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.

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

Integrated Invoice Cockpit

VIM component that gathers and displays all VIM exceptions in one place. Users
can start the respective dashboard by processing a work item directly from the
Integrated Invoice Cockpit.

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

VIM070000-RGD-EN-4 Reference Guide 303

Glossary

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.

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.

304 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Glossary

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)

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).

VIM070000-RGD-EN-4 Reference Guide 305

Glossary

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.

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.

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

306 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

Glossary

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.

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

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.

VIM070000-RGD-EN-4 Reference Guide 307

Glossary

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).

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.

308 OpenText Vendor Invoice Management for SAP Solutions VIM070000-RGD-EN-4

20 Carding Videos + 55 Methods Cash
79% (28)
20 Carding Videos + 55 Methods Cash
3 pages
2025 - Carding BTC
88% (17)
2025 - Carding BTC
16 pages
Hella Methods Here
87% (30)
Hella Methods Here
17 pages
7839+ Awesome Deep Web Onion Links List (Uncensored Content) PDF
76% (38)
7839+ Awesome Deep Web Onion Links List (Uncensored Content) PDF
391 pages
WESTERN UNION METHOD - 3000 - Per Day 100 - Working @SpamLord00
86% (43)
WESTERN UNION METHOD - 3000 - Per Day 100 - Working @SpamLord00
5 pages
Tools List
83% (29)
Tools List
2 pages
Card in 1 Lesson 2024
83% (23)
Card in 1 Lesson 2024
27 pages
30 Best Tor Sites For Any and Everything You'll Ever Need! - Your Hacker
88% (42)
30 Best Tor Sites For Any and Everything You'll Ever Need! - Your Hacker
8 pages
How To Apply For CC With Fullz and Cashout
90% (21)
How To Apply For CC With Fullz and Cashout
7 pages
2024 Latest Cashapp Method 1-2
83% (35)
2024 Latest Cashapp Method 1-2
7 pages
Virtual Carding Techniques Explained
93% (28)
Virtual Carding Techniques Explained
33 pages
Cash App Money Hack & Generator 2021
54% (28)
Cash App Money Hack & Generator 2021
6 pages
Open CC and Get 10K Instantly Approved
89% (38)
Open CC and Get 10K Instantly Approved
6 pages
Corce
68% (50)
Corce
206 pages
Bank Logs and Linkeable Card 2024
29% (7)
Bank Logs and Linkeable Card 2024
1 page
Non VBV Bins
64% (22)
Non VBV Bins
2 pages
Fraud Tactics for Beginners
77% (48)
Fraud Tactics for Beginners
6 pages
Sugar Daddy
100% (15)
Sugar Daddy
18 pages
Carding Forum: CC to BTC Methods
91% (11)
Carding Forum: CC to BTC Methods
19 pages
How To Order Free Phones On Verizon
90% (42)
How To Order Free Phones On Verizon
17 pages
Test Card Credit
100% (8)
Test Card Credit
32 pages
How To Check Client or Fullz Credit Score@Baddestupdate
91% (22)
How To Check Client or Fullz Credit Score@Baddestupdate
7 pages
Spamming Checks Sauce
93% (40)
Spamming Checks Sauce
14 pages
How To Apply For CC With Fullz and Cashout PDF Credit Card Social Security Number
80% (5)
How To Apply For CC With Fullz and Cashout PDF Credit Card Social Security Number
1 page
Full Tutorial
84% (25)
Full Tutorial
45 pages
Black Book of Crime
75% (20)
Black Book of Crime
39 pages
Illegal Loan Fraud Techniques Guide
100% (15)
Illegal Loan Fraud Techniques Guide
13 pages
Apple Pay - No Otp Needed
92% (13)
Apple Pay - No Otp Needed
22 pages
SBA 2024: Get $10K+ Loans Guide
75% (8)
SBA 2024: Get $10K+ Loans Guide
5 pages