OpenText VIM 7.5 SP3 - Config Guide

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

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

1.1 Target Audience ............................................................................. 13
1.2 Further Information Sources ............................................................ 14
2 Understanding Vendor Invoice Management ....................... 15

2.1 Delivery Model ................................................................................ 15
2.2 Workflow Scheme ........................................................................... 17
2.3 Process Swimlanes ......................................................................... 18
3 Preparing the Configuration ................................................... 21
Part 2 Mandatory Configuration 23
4 Configuring ArchiveLink ......................................................... 25

4.1 Early Archiving Scenario .................................................................. 25
4.2 PDF History Log Scenario ............................................................... 39
5 Roles ......................................................................................... 43
5.1 Defining Roles ................................................................................ 44
5.2 Defining Role Templates ................................................................. 45
5.3 Assigning Templates to Roles .......................................................... 49
5.4 Maintaining Role Determination Settings .......................................... 51
5.5 Maintaining Chart of Authority .......................................................... 54
6 Defining Rollout Criteria for Parking and Blocking

Processes ................................................................................. 77
6.1 Defining Rollout Criteria for the PO Parking Process ......................... 77
6.2 Defining Rollout Criteria for the PO Blocking Process ........................ 80
6.3 Defining Rollout Criteria for the Non PO Parking Process .................. 82
Part 3 Advanced Configuration 85
7 Authorization Checks .............................................................. 87

7.1 Available Authorization Checks ........................................................ 87
7.2 Configuring the Authorization Checks ............................................... 93
7.3 Authorization Group for VIM Tables .................................................. 95
8 Incoming Document Processing ............................................ 97

8.1 Maintaining Channels ...................................................................... 98
8.2 Maintaining the VIM Field Mapping ................................................. 101
8.3 Maintaining Service Modules ......................................................... 104
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide iii
VIM070500-03-CGD-EN-1
Table of Contents
8.4 Customizing the Email Channel ..................................................... 105

8.5 Connecting Using the Document Pipeline ....................................... 112
8.6 Maintaining Processes .................................................................. 113
8.7 EDI Configuration .......................................................................... 115
9 Document Processing Process Configuration ................... 131

9.1 Configuring DP Document Types ................................................... 134
9.2 Configuring Automatic Posting ....................................................... 175
9.3 Processing Logic Modules ............................................................. 180
9.4 Business Rule Framework ............................................................. 189
9.5 Customizing Profiles for the Indexing Screen .................................. 201
9.6 Roles in Document Processing ...................................................... 204
9.7 Configuring DP Process Options .................................................... 204
9.8 Invoice Processing Plug-ins ........................................................... 218
9.9 Extending Document Data ............................................................. 222
9.10 Mapping External System Data (OCR/IDoc) .................................... 223
9.11 Configuring the Process Type ........................................................ 225
9.12 Configuring Indexing Line Matching ................................................ 231
9.13 Additional Process Configurations .................................................. 241
9.14 Configuring Global Parameters ...................................................... 246
9.15 Excluding Company Codes from Process Types ............................. 251
9.16 Maintaining Additional Cost Handling ............................................. 252
9.17 Maintaining the VAT Date .............................................................. 262
10 PO Parking Process Configuration ...................................... 265

10.1 Configuring Process Options .......................................................... 267
10.2 Configuring Parking Reasons ......................................................... 272
11 PO Blocking Process Configuration .................................... 291

11.1 Configuring PO Blocking Process Options ...................................... 294
11.2 Configuring Blocking Reasons ....................................................... 295
12 Non PO Parking Process Configuration .............................. 313

12.1 Configuring Parking Reasons (Non PO Parking Process) ................ 315
13 Invoice Approval .................................................................... 335

13.1 Overview ...................................................................................... 335
13.2 Configuring the Process Type ........................................................ 338
13.3 Configuring the Parking Reason ..................................................... 338
13.4 Configuring Posted Approval .......................................................... 341
13.5 Implementing Invoice Approval ...................................................... 350
iv OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide

VIM070500-03-CGD-EN-1
Table of Contents
13.6 Roles in the IAP Process ............................................................... 390

13.7 Configuring Header Based Approval ............................................... 396
13.8 Configuring Level Based Approval Features ................................... 397
13.9 Coding Validation .......................................................................... 400
13.10 Configuring the Profitability Segment Feature ................................. 409
13.11 Logging and Monitoring in Invoice Approval .................................... 414
13.12 Enhancing Invoice Approval Using Extensions ................................ 416
13.13 Configuring the Fiori Invoice Approval Application ........................... 421
14 VIM Analytics (New) .............................................................. 427

14.1 Report for One-time Data Upload and for Consistency Check of
Documents ................................................................................... 428
14.2 Customizing Profiles for the New VAN ............................................ 433
14.3 Layout Variants ............................................................................. 444
14.4 Additional Configuration Options for the New VAN .......................... 445
14.5 VIM Analytics on Mass Data .......................................................... 458
15 Characteristic Specific Configuration ................................. 461

15.1 Introduction ................................................................................... 461
15.2 Invoice Categories, Category Groups, and Mapping ........................ 468
15.3 Characteristic Specific Settings for Document Types ....................... 472
15.4 Z Constants .................................................................................. 479
15.5 Configuration for Canada ............................................................... 480
16 ICC Integration ....................................................................... 489

16.1 ICC Dispatcher ............................................................................. 490
16.2 Maximum Allowed Time for Extraction and Validation ...................... 492
16.3 Validation Framework .................................................................... 494
16.4 Maintaining the Workflow Template for DP ...................................... 504
16.5 Document Type Determination Rules Engine .................................. 505
16.6 Periodic Jobs for ICC Dispatcher .................................................... 508
16.7 Download of Recipient Data for ICC Usage ..................................... 508
16.8 Customizing Options for the Reject from Validation Function ............ 510
17 Configuring the VIM Workplace ........................................... 513

17.1 Migration Report for the VIM Workplace ......................................... 513
17.2 Configuring the System Landscape Directory (SLD) for the VIM
Workplace .................................................................................... 517
17.3 Customizing Profiles for the VIM Workplace .................................... 517
17.4 Defining Action Buttons for the VIM Workplace ............................... 526
17.5 Defining Action Authority Groups for the VIM Workplace .................. 528
17.6 Configuring Scanning in VIM Workplace ......................................... 529
17.7 Defining Smart Selections .............................................................. 531
17.8 Maintaining General Teams for the VIM Workplace ......................... 534
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide v

VIM070500-03-CGD-EN-1
Table of Contents
17.9 Specifying Discount Light Settings .................................................. 535
18 Customizing Plug-in Controls for End-user Screens ......... 537

18.1 Defining the Plug-in Type ............................................................... 537
18.2 Defining the Plug-in ID ................................................................... 538
18.3 Assigning the Plug-in IDs to Plug-in Types ...................................... 539
18.4 Customizing the Integration of Extended ECM for SAP Solutions ..... 539
19 Configuring VIM Dashboards for Plug-ins .......................... 547

19.1 Maintaining Customizing Profiles for Dashboards ............................ 547
19.2 Assigning Default Profiles to Product Code ..................................... 549
Part 4 Optional Configuration 551
20 Extended Withholding Tax ................................................... 553
21 Return to Vendor ................................................................... 557

21.1 Configuring SAPConnect and SMTP .............................................. 558
21.2 Maintaining Process Options .......................................................... 558
21.3 Maintaining Return Reasons .......................................................... 558
21.4 Maintaining Email Templates ......................................................... 558
21.5 Maintaining the Email Determination User Exit ................................ 559
21.6 Maintaining the Email Signature ..................................................... 559
21.7 Maintaining Email Archiving ........................................................... 561
21.8 Maintaining Project Enhancements ................................................ 561
22 Supplier Self Service ............................................................. 563

22.1 Customizing the OData Channel on the SAP NetWeaver Gateway
System ......................................................................................... 564
22.2 Customizing the HANA Cloud Server (Option) ................................. 575
22.3 Customizing Supplier Self Service .................................................. 583
22.4 Configuring the Status ................................................................... 585
22.5 Configuring the Layout .................................................................. 587
22.6 Configuring Company Code Settings .............................................. 589
22.7 Configuring the Supplier Settings ................................................... 590
22.8 Configuring Gateway Host and Application Parameters ................... 592
23 Integration with the Ariba Network ...................................... 595

23.1 Integrating Ariba SAP Business Suite Adapter ................................ 596
23.2 Integrating the Ariba SAP NetWeaver Process Integration Adapter .. 605
24 SAP NetWeaver Business Warehouse Content .................. 613

24.1 OpenText VIM Layered Scalable Architecture (LSA) ........................ 614
24.2 Installing VIM BW Content ............................................................. 618
vi OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide

VIM070500-03-CGD-EN-1
Table of Contents
25 KPI Dashboard ....................................................................... 627

25.1 KPI Dashboard Definitions ............................................................. 627
25.2 Periodic Jobs - Collection and Aggregation ..................................... 629
25.3 Authorizations ............................................................................... 637
25.4 Customizing Settings ..................................................................... 638
25.5 Troubleshooting ............................................................................ 658
26 Automation Report ................................................................ 661

26.1 Overview ...................................................................................... 661
26.2 Periodic Jobs - ATM Collection Report ........................................... 661
27 Central Reporting Infrastructure .......................................... 663

27.1 Configuring the System Landscape Directory (SLD) ........................ 667
27.2 Maintaining Logical Systems for the Aggregation Report ................. 667
27.3 Running the Aggregation Report for the CUST_PREFL Group ......... 669
27.4 Creating Variants of the Aggregation Report for Each Group ............ 670
27.5 Activating Central Reporting Baseline and Maintaining Reporting
Tables .......................................................................................... 671
27.6 Scheduling the Collection Report ................................................... 675
27.7 Scheduling the User Master Report ................................................ 679
27.8 Scheduling the Text Master Report ................................................ 680
27.9 Scheduling the Aggregation Report ................................................ 681
27.10 Troubleshooting: Cleaning Up Central Reporting Tables .................. 681
27.11 Maintaining Thresholds for the Key Process Analytics Report .......... 683
27.12 Configuring the Summary Report ................................................... 693
28 SAP Shared Service Framework Integration ...................... 697

28.1 SAP Shared Service Framework Integration Activities ..................... 698
28.2 Maintaining the Initialization Procedure for Service Requests [ERP] . 744
28.3 Mapping the Initialization Procedure to the Service Request
Creation Points [ERP] .................................................................... 745
28.4 Defining Application Areas for Service Request [CRM] .................... 746
29 SRM Integration ..................................................................... 749

29.1 Use Cases .................................................................................... 749
29.2 Determining Purchase Order Types ................................................ 752
29.3 Configuring SRM Purchase Orders ................................................ 753
29.4 Configuring the SRM Mail Infrastructure ......................................... 759
30 PDF Log .................................................................................. 767

30.1 Customizing Profiles for the PDF Log ............................................. 767
30.2 PDF Rendition of IDocs ................................................................. 770
30.3 PDF History Log ........................................................................... 770
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide vii
VIM070500-03-CGD-EN-1
Table of Contents
Part 5 Special Topics 775
31 Background Posting of Non PO (FI) Invoices ..................... 777
32 Tools ....................................................................................... 779

32.1 VIM Notifications ........................................................................... 779
32.2 Testing Roles ................................................................................ 779
32.3 Changing the Work Item Text ......................................................... 781
32.4 Test Tools .................................................................................... 782
33 Using VIM Notifications ........................................................ 783

33.1 Working with the Selection Screen ................................................. 783
33.2 Working with the VIM Notifications List ........................................... 786
33.3 Configuring VIM Notifications ......................................................... 789
33.4 Maintaining a Notification Email Formatting Function Module ........... 797
34 Data Archiving Configuration ............................................... 799

34.1 Configuring Archiving of DP Documents ......................................... 800
34.2 Configuring Archiving of Central Reporting Information .................... 802
35 Rerunning Waiting Process Types ...................................... 807

35.1 Working with the Selection Screen ................................................. 807
35.2 Working with the Monitor List ......................................................... 809
GLS Glossary 811
viii OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-03-CGD-EN-1
Part 1
About Vendor Invoice Management
Part 1 About Vendor Invoice Management
SAP Invoice Management by OpenText (VIM) is a packaged business solution for

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

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

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

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

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

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

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

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

• Connect VIM with Ariba Network Integration for SAP Business Suite.
Suppliers create invoices in the Ariba Network. The invoices are sent to the
SAP ERP system of the buyer. The buyer processes all incoming invoices in
VIM.
Processing From a technical and functional perspective, the overall processing comprises the
blocks following processing blocks:
Document Processing (DP)

for front-end SAP document creation
PO parking processing
for handling parked PO invoices
PO blocking processing
for handling blocked PO invoices
Non-PO parking processing

for handling parked non-PO FI invoices
Invoice Approval
for approving and coding invoices

VIM070500-03-CGD-EN-1
Chapter 1
About This Document
This document describes the configuration of each of the processing blocks (see
“Processing blocks” on page 12). It also describes the various implementation
aspects of configuring VIM to suit the specific business requirements for any
organization. VIM is designed to be highly configurable to accommodate varied
business scenarios.
The structure of this document follows the VIM customizing approach:
“Mandatory Configuration”
These configuration steps describe the basic mandatory customizing. This
customizing must be done with every VIM installation, independent of changes
to the VIM baseline; for example the configuration of roles for the VIM process.
For further information about the VIM baseline, see “Delivery Model”
on page 15.
“Advanced Configuration”
These configuration steps describe the advanced customizing. This customizing
changes the VIM baseline and partly includes extensions and customer exits. An
example is the DP process configuration.
“Optional Configuration”
These configuration steps describe the basic, but optional customizing. This
customizing must be done for optional VIM features, such as the integration of
SAP Shared Service Framework.
“Special Topics”
These configuration steps describe special topics of the VIM customizing, for
example VIM Notifications.
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

VIM070500-03-CGD-EN-1
Chapter 1 About This Document
1.2 Further Information Sources

On the Knowledge Center, you find the OpenText Vendor Invoice Management
Forum where you can post questions and discuss VIM issues: https://
knowledge.opentext.com/knowledge/cs.dll/Open/10361180
Important note for SAP Reseller Customers
For information about all OpenText products resold by SAP (including VIM
and ICC), check SAP Marketplace Note 1791874: SAP Products by OpenText
- Software and Support Lifecycle. This note provides detailed information
about software life cycle, access to Support Packages, access to latest
documentation, language packages, and other patches, as well as Support
ticket handling.

VIM070500-03-CGD-EN-1
Chapter 2
Understanding Vendor Invoice Management
Process steps The Vendor Invoice Management (VIM) business process typically includes the
following main steps:
1. An OCR process (optional) sends metadata and invoice image to VIM. On a

system without OCR, the invoice images go through a standard SAP
ArchiveLink® early archiving scenario.
2. The Document Processing (DP) component validates the metadata and identifies
exceptions.
3. Invoice Exception workflows address the exception issues.
4. After validating the data and handling data exceptions, VIM creates an SAP
invoice.
• If no business rules are violated, VIM posts the invoice.
• Otherwise, VIM parks the invoice for further processing.
5. If needed, VIM triggers the parking exception process workflow.
6. Once the parking workflow is complete and everything is correct, VIM posts the
invoice. Otherwise, VIM deletes or cancels the invoice.
2.1 Delivery Model

As VIM is basically a scenario, its function may best be described as a problem
solution. It enables the flexible configuration of a company's payment workflow. To
this end, VIM is delivered with a so-called Baseline Configuration, a set of pre-defined
configurations that work out of the box. In conjunction with other OpenText
products such as OpenText™ Archive Server it is possible to realize comprehensive
solutions. Core Functions are the technical foundation of VIM: SAP screens, functions,
workflow templates, web pages, etc.

VIM070500-03-CGD-EN-1
Chapter 2 Understanding Vendor Invoice Management
Note: Only end user screens are translated in additional languages other than
English. Customizing screens are provided in English language only.

VIM070500-03-CGD-EN-1
2.2. Workflow Scheme
2.2 Workflow Scheme
Figure 2-1: Workflow scheme
Each VIM workflow process has the same basic steps:
Validate metadata
The metadata or index data are validated against the SAP database. If validation
fails, an exception is triggered.
Check duplicates
The validated metadata is used to check whether the new invoice has been
entered already. If the new invoice is suspected to be a duplicate of any existing
invoice, an exception is triggered.
Apply business rules

Invoice pre-processing: Business rules are applied to detect additional
exceptions before posting.
Post for payment
The invoice is posted and released for payment.

VIM070500-03-CGD-EN-1
Chapter 2 Understanding Vendor Invoice Management
2.3 Process Swimlanes

Business blue print sessions result in a set of finalized swimlane diagrams
representing the to-be process. Figure 2-2 on page 19 is an example of such a
process swimlane that is delivered with the VIM Baseline Configuration. A swimlane
diagram comprises the following main items:
Process Description
The description in the headline represents the process scenario.
Roles
Each lane represents a business role, a unique grouping of people required to
collaborate to complete the process.
Dashboard
The dashboard is the user interface for the actors in the process. The dashboard
type identifies the VIM component that is used to realize a specific functionality.
The following dashboard types are available:
DP dashboard
The DP dashboard represents a process as implemented in the Document
Processing component of VIM.
See section 4 “Working with the DP Dashboard” in OpenText Vendor Invoice
Management for SAP Solutions - User Guide (VIM-UGD).
VIM dashboard
The VIM dashboard represents a process as implemented in the Invoice
Exception component of VIM for parked invoices.
See section 5 “Working with the Invoice Exception Dashboards” in OpenText
Vendor Invoice Management for SAP Solutions - User Guide (VIM-UGD).
VIM line dashboard

The VIM line dashboard represents a process as implemented in the Invoice
Exception component of VIM for blocked PO based invoices for line level
blocks.
VIM header dashboard

The VIM header dashboard represents a process as implemented in the
Invoice Exception component of VIM for blocked PO based invoices for
header level processes.
Options
Various options are available to the actors during the processing of invoices.
These are represented as individual items next to the dashboard block.

VIM070500-03-CGD-EN-1
2.3. Process Swimlanes
Figure 2-2: Swimlane example

VIM070500-03-CGD-EN-1
Chapter 3
Preparing the Configuration
This section describes the activities that need to be done prior to implementing VIM.
For detailed installation steps, refer to OpenText Vendor Invoice Management for SAP
Solutions - Installation Guide (VIM-IGD).
• Install and configure an archiving system that supports SAP HTTP Content
Server interface.
• Complete business process blueprint sessions: Final process design swimlane
diagrams are available.
• Create User IDs with appropriate developer and configuration authorizations.
Authorizations need to include developer as well as workflow administrator
authorizations.
• Create ArchiveLink document types or at least finalize the list of the document
types etc.
• Check for any existing BAdI implementations for definition INVOICE_UPDATE.
Check to see if there is any conflicting code that could prevent parking reasons in
PO/Non PO invoices from showing up.
• Complete appropriate FI and MM-Purchasing customizations, so FI and logistics
invoices can be created in the system.

VIM070500-03-CGD-EN-1
Part 2
Mandatory Configuration
Part 2 Mandatory Configuration
This part describes mandatory configuration steps for VIM. These configuration
steps describe the basic mandatory customizing. This customizing must be done
with every VIM installation, independent of changes to the VIM baseline; for
example the configuration of roles for the VIM process.

VIM070500-03-CGD-EN-1
Chapter 4
Configuring ArchiveLink
This chapter describes the steps needed to configure SAP ArchiveLink document
types. ArchiveLink is responsible for the collaboration between the SAP ERP system
and the Archive Server, for example to save documents from a VIM workflow to the
Archive Server, or to retrieve documents from Archive Server for a VIM process.
Every ArchiveLink document type is assigned to a workflow that will be started

when a document with the given ArchiveLink document type is uploaded by OCR
or the OAWD transaction.
You need to do this configuration when the content repository (Archive Server) is
installed and the basic ArchiveLink settings are completed. Depending on the
customer requirements, the number and attributes of the ArchiveLink settings might
be different.
Note: For further details about ArchiveLink refer to the SAP documentation.
4.1 Early Archiving Scenario

Incoming paper invoices are scanned and archived, using the Early Archiving
scenario. The Early Archiving scenario describes a process in which a scanned
document is archived before the details of the underlying business transaction are
entered into the SAP ERP system.
As a prerequisite, you need to perform the following actions:

• “Creating a Content Repository ID” on page 26
• “Creating the Presetting Folder for VIM” on page 26
• “Creating an ICC Archive Document Type” on page 29
• “Creating an Archive Document Type for a Non-OCR Scenario” on page 32
• “Linking Archive Document Type to VIM Business Object” on page 36
• “Linking Archive Document Types to SAP Business Objects” on page 38

VIM070500-03-CGD-EN-1
Chapter 4 Configuring ArchiveLink
4.1.1 Creating a Content Repository ID

To determine where the scanned document is archived, you must maintain the
Content Repository ID. This is standard ArchiveLink customizing. If you already
have a working ArchiveLink customizing, you can skip this section.
To create a Content Repository ID:
1. Run the OAC0 transaction.
2. In the Change Content Repositories Overview screen, click Create .
3. Enter the following parameters:
Note: For more details on the parameters, see section 9.2.1 “Maintaining
HTTP archive in the SAP application” in OpenText Archiving and Document
Access for SAP Solutions - Scenario Guide (ER-CCS).
• Content Rep.: Content Repository ID

• Description
• DocArea (Document Area): ArchiveLink
• Storage type: HTTP content server
• Protocol: This setting defines the file source for archiving and image
displaying media.
• Version no.: for example, 0046
• HTTP srvr:port (HTTP server and port)
• HTTP script: archive
• Transfer drctry (Transfer directory)
4. Click .
4.1.2 Creating the Presetting Folder for VIM

A presetting folder groups document types that are related by workplace or by
application. Grouping document types together in a presetting folder provides a
more effective overview of document types on the initial screen of the storage
process Store Documents in the OAWD transaction.
For each document type, you determine the agents that are responsible for the work
item. You also choose which storage scenario is used. The following storage
scenarios are available for Early Archiving:
• Storing for subsequent entry
• Storing for subsequent assignment
• Store and enter

VIM070500-03-CGD-EN-1
4.1. Early Archiving Scenario
• Store and assign
The scenario “Storing for subsequent entry”, for example, consists of assigning the
document type and processing the work item.
To create the presetting folder for VIM:
1. Run the OAWS transaction.
2. In the Default setting: Overview screen, click New Entries in the application
tool bar.
3. Create the new presetting folder using the following parameters:
Pr
Enter the presetting folder name, for example Z001.
Long text
Enter a description of the new folder.
4. Click .
To add a document type to the presetting folder:
Note: If you store the Archive Document Type in the presetting folder during
its creation, you do not have to perform this action. Nevertheless, if you need
to reassign any Archive Document Type to another folder or you need to
assign Archive Document Types to the presetting folder, you can perform this
action. Assigning all relevant Archive Document Types to the presetting folder
is useful for identifying the Archive Document Types easily. For more
information, see “Creating an ICC Archive Document Type” on page 29.
1. Run the OAWS transaction.

VIM070500-03-CGD-EN-1
2. Select the presetting folder and double-click Entries.
3. In the Entries Overview screen, click New Entries in the application tool bar.
4. Add the Doc. type, for example /OPT/ICC, and select the appropriate storage
scenario check box, for example Storing for subsequent entry.
Note: Optionally, you can select an Object Type in the OT column and an
Agent ID for the document type.
5. Click to save your changes.

VIM070500-03-CGD-EN-1
4.1.3 Creating an ICC Archive Document Type

In this step, you create an ICC archive document type, for example /OPT/ICC, and
store it in the presetting folder created before. For more information, see “Creating
the Presetting Folder for VIM” on page 26. Then, you assign the ICC archive
document type to Early Archiving (Storing for subsequent entry).
After the ICC archive document type is maintained, every incoming invoice that is
associated with the given document type will be stored in a predefined archive and
a customized workflow will start afterwards.
To create an ICC archive document type:
1. To start the Document Type Customizing Wizard, run the OAD5 transaction.
On the Start screen, click Continue.
2. Document type
Doc.type
Enter a name for the new document type. For example, use archive
document type /OPT/ICC or another document type for your namespace.
Name
Enter a description.
Click Continue in the upcoming screens until you reach the Workflow
document type screen.
3. Workflow document type

Select the Workflow document type check box and click Continue.
4. Document class
Enter Doc. class FAX and click Continue.

VIM070500-03-CGD-EN-1
5. Object, method and tasks

Enter the following information:
Obj. type
/OPT/V1001
Entry
Method
PREPROCESS_OCR
Task
WS00275270
Assignment
Task
WS00275270
Click Continue.
6. In the Workflow Parameter screen, click Continue.

VIM070500-03-CGD-EN-1
7. Storage system and link table

Click Continue.

VIM070500-03-CGD-EN-1
8. Selection from available presettings

Select the ID 0001 and click Continue.
9. In the Create new presettings screen, click Continue.
10. Details of presettings

Select the Storing for subsequent entry check box and click Continue.
11. End
To save the archive document type /OPT/ICC, click Complete and confirm the
changes.
4.1.4 Creating an Archive Document Type for a Non-OCR

Scenario
If you run a Non-OCR scenario, you must create a Non-OCR archive document
type, for example /OPT/NOICC. You store the Non-OCR archive document type in
the presetting folder created before (see “Creating the Presetting Folder for VIM”
on page 26), and assign it to Early Archiving (Storing for subsequent entry).
After the archive document type is maintained, every incoming invoice that is
associated with the given document type will be stored in a predefined archive and
a customized workflow will start afterwards.

VIM070500-03-CGD-EN-1
To create a Non-OCR archive document type:
1. To start the Document Type Customizing Wizard, run the OAD5 transaction.
On the Start screen, click Continue.
2. Document type
Doc.type
Enter the document type. For example, use archive document type /
OPT/NOICC or another document type for your namespace.
Name
Click Continue in the upcoming screens until you reach the Workflow
document type screen.
3. Workflow document type

Select the Workflow document type check box and click Continue.
4. Document class
Enter Doc. class FAX and click Continue.
5. Object, method and tasks

Enter the following information:

VIM070500-03-CGD-EN-1
Obj. type
/OPT/V1001
Entry
Method
PREPROCESS_NON_OCR
Task
WS00275271
Assignment
Task
WS00275271
Click Continue.
6. In the Workflow Parameter screen, click Continue.
7. Storage system and link table

Click Continue.

VIM070500-03-CGD-EN-1
8. Selection from available presettings

Select the ID 0001 and click Continue.
9. In the Create new presettings screen, click Continue.

VIM070500-03-CGD-EN-1
10. Details of presettings

Select the Storing for subsequent entry check box and click Continue.
11. End
To save the archive document type /OPT/NOICC, click Complete and confirm
the changes.
4.1.5 Linking Archive Document Type to VIM Business Object

Every incoming invoice is associated with an ArchiveLink document type and a
business object.
To know where to store the incoming invoice (in which Content Repository, in
which link table), you must maintain the links, as described in this section.
To link the Archive Document Type and the VIM Business Object:

2. In the Links for Content Repositories Overview screen, click New Entries.

VIM070500-03-CGD-EN-1
Object Type
Enter /OPT/V1001
Document type
Enter /OPT/ICC
Link Status
Enter X
Storage system
Enter the Content Repository ID. For more information, see “Creating a
Content Repository ID” on page 26.
Link
Enter TOA01
Notes
• If you want to process incoming emails with several attachments,
perform an identical customizing for the document type /OPT/OTHER.
• Return to Vendor: If you want to archive emails that are sent to the
vendor, perform an identical customizing for the document type /
OPT/HTM. For more information, see “Maintaining Email Archiving”
on page 561.
4. Click .

VIM070500-03-CGD-EN-1
4.1.6 Linking Archive Document Types to SAP Business

Objects
This section describes the steps needed to map the SAP business objects to the
archive document types, which you have created. This is the way how a posted or
parked document can be linked to the documents that are attached to a VIM process.
To link SAP business objects to archive document types:
2. Create new entries, as shown in the following screenshots. The first one is BKPF
for Non-PO invoices and the second one is BUS2081 for PO invoices.
3. Save the new entries.

VIM070500-03-CGD-EN-1
4.2. PDF History Log Scenario
4.2 PDF History Log Scenario

At the end of the VIM process, it is possible to create a PDF log with history
information. The PDF history log file is archived and linked to the DP document and
its SAP invoice. For more information about the PDF history log, see “PDF History
Log” on page 770.
As a prerequisite, you need to perform the following actions:
• “Linking Archive Document Types to the VIM Business Object” on page 39

• “Linking Archive Document Types to SAP Business Objects” on page 40
Additionally, you have to define a profile for the PDF history log and assign it to a
VIM process step. For more information, see “PDF History Log” on page 770.
4.2.1 Linking Archive Document Types to the VIM Business

Object
At the end of the VIM process, it is possible to create a PDF log with history
information. This PDF history log is associated with an archive document type and a
business object. For more information about the PDF history log, see “PDF History
Log” on page 770.
To know where to store the PDF history log (in which Content Repository ID, in
which link table), you must maintain the links, as described in this section.
To link the archive document type and the VIM business object:
2. In the Links for Content Repositories Overview screen, click the New Entries
button in the application tool bar.
3. Enter the following parameters.

VIM070500-03-CGD-EN-1
Object Type
Enter /OPT/V1001.
Document type
Enter /OPT/PDF.
Link Status
Enter X.
Storage system
Enter the Content Repository ID. For more information, see “Creating a
Content Repository ID” on page 26.
Link
Enter TOA01.
4. Click to save your settings.
4.2.2 Linking Archive Document Types to SAP Business

Objects
This section describes the steps needed to map the SAP business objects to the
archive document type for the PDF history log. This is the way how a PDF history
log can be linked to the SAP invoices.
To link SAP business objects to archive document types:
2. Create new entries as shown in the following screenshots. The first one is BKPF
for Non-PO invoices and the second one is BUS2081 for PO invoices.

VIM070500-03-CGD-EN-1
4.2. PDF History Log Scenario
3. Save the new entries.

VIM070500-03-CGD-EN-1
Chapter 5
Roles
Roles refer to the grouping of various business users according to their business
activity. In the swimlane diagrams, roles represent the title for each of the lanes.
Vendor Invoice Management (VIM) has a comprehensive framework for realizing
various requirements in the area of role definition. You can define roles as granular
as needed.
The VIM role framework comprises the following main concepts:
Role
In VIM terminology, role stands for a Process Agent. Role is not the same as the
SAP workflow technical role.
Note: The workflows are delivered by OpenText and hence cannot be

changed at client side.
Template
Any role bases on a template.
Template fields
Templates can have fields that determine the granular logic used in determining
the final set of users. For example, the grouping of roles can base on the
company code or the purchasing organization.
This chapter describes the steps required to create and configure roles needed for
implementing VIM business scenarios.
To configure roles, the following steps are required:

• “Defining Roles” on page 44
• “Defining Role Templates” on page 45
• “Assigning Templates to Roles” on page 49
• “Maintaining Role Determination Settings” on page 51
• “Maintaining Chart of Authority” on page 54

VIM070500-03-CGD-EN-1
Chapter 5 Roles
5.1 Defining Roles

The first step in creating a role is to define the role. Roles in VIM base on product
codes that are defined in VIM. The following product codes are available:
005
Document Processing (DP) based product codes
LIX
LIV based product codes (both for PO parking and PO blocking workflows)
PIR
Product codes for Non-PO parking workflows
Every role assignment bases on the product code/role combination. For example, to
create a role called BUYER in a PO parking process, create a role BUYER with product
code LIX.
OpenText delivers standard roles used in most process scenarios. You can define
your own roles if needed.
To maintain roles:
1. Run the /OPT/CP_9CX5 transaction.
Alternatively, navigate to OpenText Vendor Invoice Management > SAP
menu> Roles > Role Maintenance.

VIM070500-03-CGD-EN-1
5.2. Defining Role Templates
2. Maintain the role data, using the following parameters:
Product Code
Enter the product code such as 005, LIX, PIR. Refer to OpenText product
codes for applicable product code.
Responsible Party
Enter the responsible party (role).
Description
Enter the description of the role.
Role Function Module

Enter a function module for the role. For the interface, see function module
template /PTGWFI/COA_W_ADKY_GET.
Key Determination
Select the check box, if the role is defined by object information – the context
in which the role is used.
Deactivate the check box, if the role is fixed and defined by organization
data, for example: if you want to determine the role by company code, scan
location, or plant.
Object Type
Maintain the object type, based on the workflow.
5.2 Defining Role Templates

This section describes the creation and maintenance of role templates. Every VIM
role is based on a role template. Templates determine the options that control how a
role is resolved finally by the workflow runtime system, that means how the final set
of users is found.
The following types of templates are available:
Key determination (Static)

• Combination of columns
• Depends on the business object attributes.
Example: Company code, scan location and plant define the AP Processor role.
Function Module (Dynamic)

• Set of custom functions that extend baseline functions
Example: Buyer is the PO creator that the function module extracts from the PO.
SAP HR org structure (Semi-Dynamic)

• Always send to the structure such as a position or work center.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
Example: Tax Experts are users attached to a single work center.
5.2.1 Maintaining Role Templates

OpenText delivers standard role templates that are used in most process scenarios.
You can define your own role templates if needed.
To maintain role templates:
1. Run the /opt/cp_9cx2 transaction.

Alternatively, navigate to OpenText Vendor Invoice Management > SAP menu
> Roles > Template Maintenance.
2. In the Product Role Templates Configuration Overview screen, double-click

Template Definition in the navigation pane.
3. Maintain templates using the following parameters:
Template Id
Enter meaningful character value that identifies the template.
Description
Enter the template description.
Type
Select the template type. The following template types are available:
Function Module Based

If you select Function Module Based, the agents for the role are
determined using a function module.

VIM070500-03-CGD-EN-1
5.2. Defining Role Templates
Org Unit
If you select Org Unit, the agents for the role are determined from a
fixed org unit (User, Position, Work Center, and so on)
Key Determination Based
If you select Key Determination Based, the agents for the role are
determined using runtime values of fields in the object data.
For further information on how templates resolve users, refer to
“Maintaining Role Determination Settings” on page 51.
Allow Org
For Key Determination Based templates, only: If the Allow Org flag is set,
you can set an Org Unit instead of a fixed SAP User ID while maintaining
agents for role template in the role determination transaction.
Object Type
For Org Unit based templates only: Select the default value for Agent Type
(User, Position, and Work Center etc.).
Agent Id
For Org Unit based templates only: Select the agent ID.
Function Module
For Function Module Based based templates only: Select the function
module that is used to determine agents for this template. The interface
value for the function module can be found in the OpenText delivered
function /OPT/BL_ROLE_SELF_DIRECTED.
5.2.2 Maintaining Template Fields

Role templates can have template fields that determine the granularity of how the
role is resolved at run time. This subsection describes the steps required for creating
fields for role templates.
To maintain template fields:
1. In the Template Definition Overview screen, select a template from the list and
double-click Template Fields in the navigation pane.
2. Maintain the template fields, using the following parameters:

VIM070500-03-CGD-EN-1
Chapter 5 Roles
Field Id
Enter a freely defined field Id which describes the usage of the field.
Ref. Table/Ref. Field

Select reference table and reference field. When maintaining values for the
field, the system can check the values and provide F4 help for the field
using reference table and reference field.
Search Help
Select the search help. When maintaining values for the field in the role
determination transaction, the system uses this value to provide F4 help for
the field.
Allow Range
Select this check box to allow ranges. The values can have a range from
“Low Value” to “High Value”. The system checks the runtime data for the
product code in which the template is used to validate if it can resolve the
field.
Wild Card
Select this check box to allow the wild card character *. Users can define a
wild card for values in the role determination transaction for the product
code in which the template is used.
Example: If all company codes starting with 10 should be considered to resolve a

role, 10* can be maintained if wild card is selected. If the check box is not set, the
system checks to match the entry as is.
5.2.3 Maintaining Template Field Details

In this step, you define the details for the field ID for each product code. This is
necessary because a template can be reused in different product codes and different
roles.
Example: A field combination of Company Code and Plant could be used to resolve BUYER
in the PO parking process, BUYER in the PO blocking process and PO_BUYER in the Document
Processing process.
To maintain template field details:
1. In the Template Fields Overview screen, select a field Id and double-click

Template Field Details in the navigation pane.

VIM070500-03-CGD-EN-1
5.3. Assigning Templates to Roles
2. In the Template Fields Details Overview screen, maintain the Template Field
Details, using the following parameters:
Product Code
Select the OpenText product code in which the template is used.
Object Type
Select the object type. Object types are defined for each OpenText product
code. You can however create a subtype for the OpenText Object Type to
define your own attributes. At runtime, the system instantiates the object
with the object key. The type should be compatible to the OpenText object
type for the given product code.
Attribute
Select the attribute the system uses for the given OpenText product code for
getting the runtime value for the given field Id.
5.3 Assigning Templates to Roles

When the roles and role templates are created or changed, you need to assign the
templates to specific roles. You can maintain more than one template for a specific
role but only one of the templates will be active for that role. This section describes
how to maintain the assignment of role and role template.
To assign role templates to roles:

> Roles > Template Maintenance.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
2. In the Product Role Templates Configuration Overview screen, maintain the

Product Role Templates, using the following parameters:
Product Code
OpenText product code
Responsible Party
OpenText role
Key Determination Template Id

Template Id defined
Active check box

Select the Active check box to assign the template defined to the product
role combination. The template will be used in determining agents for the
role in OpenText processes. You can only have one active template for a
given product role.

VIM070500-03-CGD-EN-1
5.4. Maintaining Role Determination Settings
5.4 Maintaining Role Determination Settings

In the steps before, you have maintained all the roles, role templates and role/role
template assignments. Now you maintain the actual settings for the roles by specific
user IDs or other objects (like the company code or plant) that are required by the
template. In this step, you define the runtime values that the system uses to resolve
roles for a given product code.
To maintain the role determination settings:

> Roles > Simple Mode Role Maintenance.
2. Maintain the role determination settings, according to the template type.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
Template type Key Determination Based
• The fields in a key determination based role depend on the template

definition.
• Maintain values for the fields displayed.

VIM070500-03-CGD-EN-1
5.4. Maintaining Role Determination Settings
Template type Function Module Based
Func. Module
Enter the custom function module. The interface for the function
module is defined in the /OPT/BL_ROLE_SELF_DIRECTED function
module.
Template type Org Unit
Agent Type
Select the agent type (US for user ID, S for position, and so on).
Agent Id
Depending on the agent type, select the agent Id (SAP user ID, position
etc.).

VIM070500-03-CGD-EN-1
Chapter 5 Roles
5.5 Maintaining Chart of Authority

VIM provides the following method for Invoice Approval:
Level-based This approval method has been introduced with VIM 7.0. Level-based approval is
approval considered only for Non PO document types. For PO document types, a one-step
approval is provided by default.
For more information, see “Configuring Approval Flow Settings” on page 353.
Note: The simple approval flow, which was used in versions of VIM prior to
7.0, was based on Manager’s information provided in the “old” Chart of
Authority (COA). For information about the “old” COA, see section 9.6
“Maintaining Chart of Authority” in OpenText Vendor Invoice Management -
Configuration Guide (VIM060000-CGD). This is the documentation for VIM 6.0.
COA configura- In level-based approval, COA details are checked when the user opens the work
tion item. That means that changes in the COA details are automatically reflected in the
Invoice Approval screen. When a task is performed, the next approval steps are
automatically determined according to the actual setting. Therefore, changes to user-
specific COA details are not critical. Changing or renaming a User ID might be
critical. For more information, see “To activate or deactivate a user:“ on page 58.
This section provides details on how to configure the COA for level-based Invoice
Approval. For a comprehensive description of the level-based Invoice Approval
component, see “Invoice Approval“ on page 335.
Purpose COA is required in the Invoice Approval process to allow users to approve Non PO
invoices. The data combination maintained in the COA helps to determine the
correct approver for a certain invoice in the approval process.
Note: The PO Invoice Approval process does not consider the COA when
determining the next approver. For PO invoices, Baseline implementation
identifies the requester of the PO as the first and only approver.
Approvers can be different with different limits of approvals for different

combinations or different org data, which can be very complex. COA provides a
single interface for maintaining all the combinations of approvers, approval limits,
and coders for the Invoice Approval process.
COA maintenance is performed by functional users who are aware of organizational

objects involved in the Invoice Approval process.
Prerequisites
• The Cost Objects allowed in the Invoice Approval process are maintained. You
can maintain the Cost Objects in the SM30 transaction for the /OPT/BL_T401V
table/view.
Note: The fields Inv. Table and Inv. Field in /OPT/BL_T401V were used in
the old simple approval, but are ignored in level-based approval.

VIM070500-03-CGD-EN-1
5.5. Maintaining Chart of Authority
• The fields required for approval user data in the User Details tab are maintained.
You can maintain the fields in the SM30 transaction for the /OPT/BL_T402V table/
view.
Independently from the /OPT/BL_T402V table/view, the following fields are
always displayed in the User Details tab:
• OPT_USERID
• DELETED
• EMAIL
• MANAGER_ID
• BULKAPPROVAL
• BTEXT
• USER_TYPE
• UTEXT
For all other fields, you must maintain them in the /OPT/BL_T402V table/view to
have them displayed in the User Details tab.
• The levels required for approval limit and approval authorities are maintained.
You can maintain the levels in the SM30 transaction for the /OPT/AT_LEVEL table/
view.
Note: Level 0 is always reserved for Coder Level. Level 1 always represents
Requester Level. All other subsequent levels from 2 to x can be used for
Approval Levels.
Expense type It is possible to build the line-based approval logic on the values of expense type and
and additional other fields that are available in the invoice line items. The expense type is treated as
fields
an item level field. Other fields must already be present in the line item structures of
the invoice. See the /OPT/A_INVOICE_ACCT_ST structure for reference.
Important
You can configure the requester determination using the same COA logic as
used to determine coders (except the first coder) and approvers. However,
this is only supported if you work with real coders, that means, if you have
two steps, first coding and then requester. If you have configured that “coder
= requester”, VIM uses the requester field from the invoice.
To enable new fields for COA logic:
1. Add new fields (except the expense type) to the /OPT/A_COA_FIELDS_ST and /
OPT/BL_4RCOA_DATA structures. To do this, use append structures.
Note: The field names used in both structures must match.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
2. Add new fields to the COA field list in the /OPT/BL_T401V view as line item
fields. You must add the expense type field as a line item field. Make sure the
Header field check box is cleared.
3. Provide a mapping between the invoice fields and the COA fields. You do this
in the VIM customizing for the respective AFS IDs, under Maintain Invoice
Detail Fields and Maintain Coding Fields Mapping. For more information, see
“Configuring Fields for the Invoice Detail Page” on page 376.
Access You can access the COA maintenance using transaction code /OPT/AR_COA.
Alternatively run the /n/OPT/VIM transaction and navigate to OpenText Vendor

Invoice Management > SAP menu > Roles > Level Based Approval Flow > Level
Based Approval - Chart of Authority Maintenance.
The default access to COA is in display mode. Use the Display/Change button to
switch to maintenance mode.
5.5.1 User Details View

The User Details View lists the COA users' general details.
Enter the following details for each user:
OpenText User Id
User Id (generated automatically)
Deleted
Check box indicating if the user is deleted from COA.
Manager ID
Direct superior of the user. In the level based approval flow, the manager is only
used for the notification escalation processing but not for any approval
processing logic. For more information, see “Configuring Notification and Email
Options” on page 789.
Bulk Approval Category
Permission to perform bulk approval, that means, the user can approve or reject
more than one work item at the same time.

VIM070500-03-CGD-EN-1
The following settings are possible:
• A-Approval
• R-Reject
• B-Approval and Reject
• N-None
Last Name
User’s last name
First Name
User’s first name
Middle Name
User’s middle name (optional)
Department
User's department (optional)
Windows Domain
If implementing optional Approval Portal with WAS authentication scenario:
Windows domain. Required if Approval Portal is used with WAS authentication
scenario and users are authenticated using Windows domain.
Windows_ID
If implementing optional Approval Portal with WAS authentication scenario:
Windows ID or the login ID. Required if Approval Portal is used with WAS
authentication scenario and users are authenticated using Windows domain.
Personnel number
Personnel number of the user
SAP User ID
SAP User ID of the user
SAP Portal User ID

If implementing optional Approval Portal with Portal authentication scenario,
this will be the login ID for the user in the portal.
Email Address
User's email address. Identifying field for all COA users (approvers). This field
cannot be duplicated with existing users.
Name and address

Name, other form of user's address (optional)
Telephone number
User's telephone number
In the User Details View screen, you can perform the following actions:

VIM070500-03-CGD-EN-1
Chapter 5 Roles
To create a new user:
1. Click the icon.

A new empty row is created.
2. Maintain the required entries.
3. To save, click the icon.
To create multiple users:
1. Click the icon.

Five new users are inserted.
2. Maintain the required entries for each user.
To activate or deactivate a user:
1. Select an existing user.
2. Click the icon.
Notes
• You cannot delete users in COA but only deactivate them. Before you
deactivate a user, check if the user has open invoices to approve. If yes,
reassign open invoices to another user using the Reassign utility. For
more information, see “Override, Delegation, Substitution, and
Reassign” on page 394.
• Renaming an OpenText User ID is not possible directly. You must create
a new user and deactivate the old user.
• If you are deactivating a user, the COA will issue a warning if there are
any active approval tasks. However, this is only a warning, you can still
proceed.
3. Select User Activate or User Deactivate from the context menu.

The selected user is marked for activation or deactivation. If you deactivate a
user, the Deleted check box is selected.
To maintain user preferences:
The settings here are the same as in the Personalization screen in the Approval
Portal. See section 7.14 “Personalizing Your Views of the Approval Portal” in
OpenText Vendor Invoice Management for SAP Solutions - User Guide (VIM-UGD). Some
parameters apply to the Mobile Integration, as well.
1. Select an existing user.

VIM070500-03-CGD-EN-1
2. Click the User Preferences icon.
3. In the User Preferences dialog box, maintain the following parameters.
Show Details
Select this check box to automatically open the Invoice Detail section in the
Approve Invoice screen.
Clear this check box to display only the Details link in the Approve Invoice
screen.
Show History
Select this check box to automatically open the History section in the
Approve Invoice screen.
Clear this check box to display only the History link in the Approve Invoice
screen.
Default Coder
Enter the default coder that you want to do the coding.
Invoice List Field
Enter the sequence of list fields.
Max. Recent List
Enter how many names should be displayed in the drop-down list for
previously selected persons.
E Notify Active
Select this check box to receive an email notification regarding any new
invoice in your inbox.
Invoice per Page
Enter the number of invoices to be displayed in the Invoice List and the
Processed Invoice List.
Language
Also relevant for Mobile Integration: Enter the default language.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
Date format
Also relevant for Mobile Integration: Enter the date format. Click for a
list of possible formats.
Dec.pt.format
Also relevant for Mobile Integration: Enter the format of the decimal
notation. Click for a list of possible formats.
Currency
Enter the default currency.
Show Attachment
This check box is not relevant. Users can always use the attachment
function, regardless of the Show Attachment check box.
Display Type
Determine where the invoice image should be displayed when opening the
detail page. Click for a selection.
Logical system
Enter the SAP ERP system that you want to use as the user preference for
your Invoice List page.
Time Zone
Also relevant for Mobile Integration (as the time zone in Approval log):
Enter the default time zone for the user. Click for a selection.
4. Click Save and Continue.
5.5.2 Approval Limit/Level View

The Approval Limit/Level View defines the approval levels and amounts,
depending on the Company Code and the Expense Type. In addition, for level based
header processing, the approval limit processing is detailed by the approval
category.
Note: In header based approval, the flow will remain the same as the line
based approval in coder and requester level. The lines have to be coded and
approved, and each line is checked against the COA details of the user in the
corresponding level.

VIM070500-03-CGD-EN-1
Enter the following parameters for the combination of Company Code and
Approval Level:
Company Code
Company Code for which the approval level should apply
Approval Level
Basic value of the level based COA. Select one of the following values from the
list:
0
Coder level (no limit possible)
1
Requester level
2, 3, ...
Approval levels
Expense Type for Invoices

Select an expense type from the list.
Description
Enter a description of the level. The description is optional. It helps to describe
the different levels for the different key fields.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
Amount Limit
Enter an amount. This amount will be considered as the approval limit. The user
can approve the invoice if the amount of a certain pack in the invoice is less than
or equals to the amount mentioned in this column. If the amount exceeds this
limit, the invoice needs next level approval.
Notes
• The pack amount is the sum of different line items assigned to an
approver per company code.
• For the coder level, the amount must always be 0 (zero). It is not allowed
to maintain any limit.
• You must maintain all levels in the hierarchy (0, 1, 2, 3, …). If any of the
level is missing, the hierarchy system shows an error message.
Approval Category
This column is specific to header based approval. Select H-Highest pack only
or A-All pack from the list.
For header based approval, all lines are assigned to one user in each level. This
user is automatically proposed by the system with the following logic:
For each user, the system calculates the approvable lines (pack) and sums up the
amount. The user with the highest pack amount is proposed.
H-Highest pack only

The amount limit within COA is checked against the total invoice amount.
From the levels with an amount limit (level 1 to level n), fetching the next
approver is based on the highest pack. For coder level (level 0), the value
always must be H-Highest pack only.
A-All pack
The amount limit within COA is checked against the pack amount (assigned
and approvable invoice lines). The additional amount is checked against the
sum of not assigned invoice lines.
For an example, see Example 5-1, “Header based approval” on page 62
Additional Amount
Enter an amount. The additional amount is used in the header based approval to
check all packs (All pack scenario).
Example 5-1: Header based approval
Invoice information
Invoice Amount 1000€

Line 1 Cost Center: 1000; Amount 100€

VIM070500-03-CGD-EN-1
COA Authority settings
User A Allowed for Cost Center 1000 and Cost Center 1001
User B Allowed for Cost Center 1001
User C Allowed for Cost Center 1002
The following ways of determining the user are available:
• Calculating each pack value

• Checking the amount limits
Calculating each pack value
(In this case, the approval limit settings have no impact.)
User A Allowed for line 1 and 2: Pack amount 400€

User B Allowed for line 2: Pack amount 300€
User C Allowed for line 3: Pack amount 600€
As User C has the highest pack amount, he will receive the workitem.
Checking the amount limits
(In this case, you must distinguish between the Highest pack only and the
All pack scenarios.)
Highest pack only scenario

COA limit settings: Approver level with the limit 500€
User C gets the invoice and will approve it. His configured limit (500€) is
checked against the total invoice amount which is 1000€. Because user C
is not allowed to approve 1000€, the invoice will be sent to the next level,
where another user will be determined.
All pack scenario

COA limit settings: Approver level with the limit 700€ and an
additional amount of 150€
User C gets the invoice and will approve it. His configured limit (700€) is
checked against his pack (the lines that user C is allowed to approve =
600€). If this limit is passed, his additional amount (150€) will be checked
against the sum of the remaining lines (400€). If one of these checks fails,
the invoice will go a level up to the next approver, otherwise the
approval is finished.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
5.5.3 COA Details View

The COA Details tab enables you to assign cost objects to each user.
For coder and requester (approval level 0 and 1), the cost objects are checked if the
user can code or approve the corresponding cost objects. All lines must be approved
by a legitimated coder or requester. The invoice is forwarded to the next coder or
requester until all lines are coded or approved. Within level based approval, this
process is performed in the same way for header and line based approval scenarios.
For approvers, the COA is used to determine the next approver and also to create
the pack when the approver opens the work item. If more than one approver exists
in the COA for the corresponding cost objects of the invoice line, the first user in the
COA will be determined. For this, the entries will be sorted alphanumerically with
the approver ID and counter.
Note: To change the logic of handling the cases when more than one approver
can be determined, you can redefine the user map class and implement your
own logic of sorting the entries and prioritizing the approvers.
In the COA, you can maintain different cost objects.
Cost object values can be entered using ranges and wildcards (asterisk).
Note: You can choose whether the asterisk will match an empty invoice field
or not. You control this by the constant IAP / AST_ALLOWS_SPACE. When
changing the constant value, be aware that having it enabled may affect the
process of finding the next coding agent for the lines where all COA-relevant
fields are empty.
Without the constant enabled, for lines with empty cost elements, VIM will
propose any existing coding agent to allow the coding process to continue.
With the constant enabled, users that have COA records with asterisks will be
excluded from the search. This means, the line is not empty for them anymore
because the asterisk will fill the space.
If an invoice line has one cost object assigned, this cost object is checked against the
COA.
If an invoice line has more than one cost object assigned, all cost objects are checked
against the COA. There is no precedence of one cost object over the other. All cost
objects that are listed in OPT/BL_T401V are checked.
Cost objects which are not available in the COA (according to configuration of
OPT/BL_T401V) are not checked.
If an invoice line does not have any cost object that can be assigned to a COA cost
object, the line cannot be approved.

VIM070500-03-CGD-EN-1
The COA Details View lists approvers, depending on the Company Code and the
Approval Level.
The user types Coder / Requester and Approver are shown on separate sub-tabs.
Enter the following details for each user:
Company Code
The company code that the user is authorized to approve. For line based
approval, the company code of the invoice line is used to check against the
COA. For header based approval, the header company code is relevant.
Important
In VIM baseline, level based approval does not support cross-company-
code invoices.
Approval Level
Approval level. See “Approval Limit/Level View” on page 60.
UserObjID
OpenText User Id, maintained in the User Details tab
Counter
This column is not editable. It is filled automatically by the system. The counter
is used to indicate the number of times the same user with same level and
company code is assigned to different cost elements. See the lines in the
screenshot at the beginning of this section: Company Code 1000, Approval
Level 000-Coder, and UserObjID CODER1

VIM070500-03-CGD-EN-1
Chapter 5 Roles
Configurable Cost Elements

The cost elements, for example Cost Center or WBS Element, can be maintained
in table OPT/BL_T401.
Depending on your process needs, you can configure VIM to either allow only
one cost object per COA line, or allow several cost objects. To enable multiple
cost object logic, set the constant MULTI_ACCT_ASSIGN for product code IAP to X
in table /PTGWFI/Z_CONST. It is also possible to configure an asterisk (*) for a
cost object.
See the screenshot of the COA Details tab above for an example.
Example 5-2, “Single and multiple cost objects” on page 66 illustrates the
differences between using single and multiple cost objects per COA line:
Example 5-2: Single and multiple cost objects

If in general all combinations of GL accounts 1234 and 5678 and cost
centers 1010 and 1020 are possible, you may maintain the COA without
using the multiple cost elements in the following way:
GL account Cost center

1234
5678
1010
1020
However, using this way, you cannot limit the approval rights at some
selected levels only to a combination of GL account 1234 and cost center
1010. The solution is to enable multiple cost elements in COA and
maintain the COA like this:
GL account Cost center

1234 1010
5.5.4 Coder Settings View

In the Coder Settings tab, you can maintain coders against the Approval Flow ID
(AFS ID). For more information about the AFS ID, see “Configuring Approval Flow
Settings” on page 353.
To maintain coders in the COA:
1. In the COA, click the Coder Settings tab.

2. In Approval Flow ID, enter an AFS ID.
For a list of available AFS IDs, click
3. Press RETURN.

VIM070500-03-CGD-EN-1
4. Enter the following details for each user:

The fields that you can maintain here depend on the coder determination (see
“Configuring Approval Flow Settings” on page 353.)
The company code will only be shown for determination by requester and
company code. If the determination is configured to use requester, there will be
no maintenance view available for this AFS ID.
Requester ID
Person who the invoice belongs to (initial approver). For more information,
see “Driving the Approval Flow for DP Invoices” on page 351 and
“Defining Approval Hierarchy and Approval Level” on page 352.
Company Code
The company code the coder is authorized to perform coding accounting
information for.
Default
Select the check box to set the coder as the default coder for this company
code.
Counter
Counter, cannot be modified.
Coder
User ID of the coder for this combination.
In the Coder Settings view, you can perform the following action:
To create new entries:
1. Click the icon to create new coder entries.

2. Maintain the required entries for the new coders.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
5.5.5 Setting Up a Substitute for the IAP Process

For the Invoice Approval (IAP) process, the VIM workflow administrator can set up
substitutes for other users.
Example: Anne is a substitute for Andrew to approve invoices when Andrew is on vacation.
However, Andrew has not designated Anne as his substitute in the SAP inbox. Andrew is on
vacation and there are invoices waiting for approval.
You as the VIM workflow administrator can set up Anne as Andrew’s substitute so that she
can approve the invoices.
Notes
• When a substitute approves an invoice, the audit trail shows that “XXXX
approves on behalf of YYYY”.
• In the Approval Portal (new interface), you can set up substitutes (delegates)
using the User menu in the header. For more information, see section 7.15
“Specifying Settings for Delegation” in OpenText Vendor Invoice Management
for SAP Solutions - User Guide (VIM-UGD).
To set up a substitute for the IAP process:
1. Run the /ORS/MAIN_SUBS transaction.

Alternatively, in the COA’s User Details View, select a user’s line and click the
Substitute button. If you use this option, continue with Step 5 on page 69.
2. In the User Substitutes Management Utility screen, click the Search User
button to indicate the user to be substituted.
3. In the Search User dialog box, enter search criteria for the substituted user and
click to search for the user ID.
4. To select the user from the list, double-click the corresponding entry in the
Search User dialog box.

VIM070500-03-CGD-EN-1
5. In the User Substitutes Management Utility screen, click the Substitutes tab,
and then click Select a substitute.
6. In the Search User dialog box, enter search criteria for the substitute and click
to search.
7. To select the user from the list, double-click the corresponding entry in the
Search User dialog box.
8. In the User Substitutes Management Utility screen, click to save the

changes.
When the substitute accesses the approval page, they will be able to view and
approve invoices for the substituted user.
5.5.6 Logging with Change Documents

The COA supports logging with change documents. Changes regarding the /
ORS/USERMAP and /OPT/BL_APPCOA tables are logged for the corresponding data
elements.
Note: If you configure the COA using the baseline, logging with change
documents will not be necessary.
For customer-specific mass uploads of the /ORS/USERMAP and /OPT/BL_APPCOA

tables, the following function modules can be integrated to enable change
documents:
/OPT/VIM_BL_CHNG_APCOA
Write changes for /OPT/BL_APPCOA
Note: In VIM 7.5 SP1, the /OPT/VIM_BL_CHNG_APCOA function module is

not supported. Support will be implemented in a future SP.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
/OPT/VIM_BL_CHNG_USRMAP
Write changes for /ORS/USERMAP
You can retrieve the change document in the following ways:
Display changes button

Select a user and click the Display changes button in the ALV grid control.
The change document is only displayed for the selected user.
Menu option Go To > Display changes
Navigate to the menu option Go To > Display changes. The following selection
screen is displayed.
from/to
Enter a dedicated period.
Name
Select the user.
User Mapping Object ID
Enter the change object.
Table Name
Enter /ORS/USERMAP or /OPT/BL_APPCOA.
Click to open the change document.
The change document displays all relevant information about the last changes in a
list view with the changed values and the user who changed the data.
The following fields are not logged:
Table /ORS/USERMAP:
• MIDDLENAME

VIM070500-03-CGD-EN-1
• DEPARTMENT
• WINDOWS_DOMAIN
• SAP_USER_ID
• OTHER_ID
• PHONE
Table /OPT/BL_APPCOA:
• COUNTER
5.5.7 COA Upload Report

Using the COA upload report, you can upload mass data to the respective tables of
the COA. The COA upload report reduces the effort of manual entry in the COA
tabs.
To use the COA upload report:
1. To start the COA upload report, run the /n/OPT/VIM_COAUPLOAD transaction.

The program name is /OPT/COA_UPLOAD_REPORT.
2. Configure the following parameters for the COA upload report:

Processing modes
Delta mode
In this mode, you update the existing record with information provided in
the upload file (*.CSV file).
Inserts a new record if the user does not exist yet.

VIM070500-03-CGD-EN-1
Chapter 5 Roles
Note: To mark a user as deleted, set the deletion flag in the *.CSV file.
Full mode
In this mode, all data from the COA tables is deleted in the database, and is
updated with the data provided in the *.CSV file.
Important
Handle the full mode with care because all existing users are deleted
in the system if you upload the data in full mode.
Note: The processing modes are only applicable to upload (data transfer).
For download, the processing modes are not used.
Update modes
Presentation server
The *.CSV file to be uploaded is selected from the PC (presentation layer).
Application server
The *.CSV file to be uploaded is selected from the application layer.
File path
Path to the *.CSV file that is used to either upload or download the data.
Type of data transfer
Upload
The data provided in the *.CSV file is uploaded to the COA tables.
Download
The data related to the COA tables is downloaded into the *.CSV file.
3. To run the COA upload report, click .
Exits You can overwrite the entire logic using the exits provided in the /
OPT/COA_UPLOAD_REPORT program, using the following Z constants of the IAP
product code in the /PTGWFI/Z_CONST table:
COA_UPLOAD_EXIT_UP
Z constant for upload. The reference FM template for the exit is /
OPT/COA_UPLOAD_EXIT.
COA_UPLOAD_EXIT_DW
Z constant for download. The reference FM template for the exit is /
OPT/COA_UPLOAD_EXIT.
Customization You can configure the fields and the field sequence for the COA upload, according
to the tabs in the new COA. The configuration for the COA upload supports only
three of the four tabs. For details, see the following table.

VIM070500-03-CGD-EN-1
COA tab name COA upload tab type

(table name)
User Details USR
(/ORS/USERMAP)
Approval Limit/Level APL
(/OPT/APPR_LIMIT)
COA Details COA
(/OPT/APPR_COA)
Coder Settings not supported
To configure fields and sequence for the COA upload:
1. To specify the tab type for the COA upload, run the /OPT/VIM_UPLCFG
transaction.
Alternatively, run the /n/OPT/SPRO transaction and navigate to Vendor Invoice
Management > Invoice Approval Configuration > Technical General > COA
Upload Configuration Details.
Note: This configuration is specific to the upload process type only.
2. In the Tab Configuration for COA Upload screen, in the COA Tab selection
field, specify the tab type that you want to configure, and click .
Field entries are inserted into the /opt/coa_uplcfg table.
3. Configure Fields and Sequence, using the following parameters:

VIM070500-03-CGD-EN-1
Chapter 5 Roles
Tab type
COA upload tab type
Table name
Name of the table related to the specified COA upload tab type
Fields
Fields available in this table
Active
Select this check box for the fields that you want to change or update the
information for in the respective tab of the new COA.
Sequence
Specify the order of the fields. This can be flexible, you can determine your
own order or template. Do not duplicate order numbers.

VIM070500-03-CGD-EN-1
Note: Follow the same sequence in the *.CSV file.
The proposal for the COA upload configuration entries is created when you
open the corresponding node in /OPT/SPRO. All the field information related to
the COA tab is read. Already existing records are not overwritten. The data is
inserted or modified in the COA upload configuration table /opt/coa_uplcfg.
You must activate the fields in the proposed list of COA upload configuration
entries according to your process.
*.CSV file The following screenshot shows an example of an *.CSV file.
Notes
• Always maintain the first column of the *.CSV file with the COA upload tab
type, for example USR. Then follow the sequence for the corresponding table,
mentioned in Sequence on page 74.
• The SAP_USER_IDs must already exist as SAP users.

VIM070500-03-CGD-EN-1
Chapter 6
Defining Rollout Criteria for Parking and Blocking
Processes
To determine when parking and blocking processes need to be triggered, you must
define the rollout criteria, for example the company code, for these processes.
Note: The rollout criteria are used for two additional functions:
• for the posted approval process. For more information, see “Configuring
Event Linkage for Posted Approval” on page 346.
• for the creation of accompanying DP documents for documents that are
posted or parked directly in the SAP system, in connection with a
corresponding setting of the Z constants 005 DOCTYPE_NPO and 005
DOCTYPE_PO.
This configuration applies to the following processes:

• “Defining Rollout Criteria for the PO Parking Process” on page 77
• “Defining Rollout Criteria for the PO Blocking Process” on page 80
• “Defining Rollout Criteria for the Non PO Parking Process” on page 82
6.1 Defining Rollout Criteria for the PO Parking

Process
In this step, you define when the VIM PO parked document process needs to be
triggered. For example, you might want to apply VIM for some specific company
code/plants/document types. For other company codes, you might want to use
standard SAP processes. In this case, the rollout must be maintained with correct
company code/plants/document types.
Note: For a description of the configuration necessary for the PO parking

process, see “PO Parking Process Configuration“ on page 265
To completely disallow the PO parked document process, deactivate the event

linkage as described in “Event Linkages” on page 79.
Note: Company codes, document types, and plants are part of the rollout
criteria for the PO parking process and the PO blocking process. For the Non
PO parking process, company codes and document types are part of the rollout
criteria.
• Rollout company codes, plants, and document types are maintained in the
respective tables by using the OpenText Customization:

VIM070500-03-CGD-EN-1
Chapter 6 Defining Rollout Criteria for Parking and Blocking Processes
Company codes
/OPT/VIM_CCODE_A
Plants
/OPT/VIM_PLANT_A
Document types
/OPT/VIM_DTYPE_A
• You can maintain plants only for PO invoices.
To define the rollout criteria:
1. To define the rollout criteria, run the /n/OPT/SPRO transaction and navigate to
Vendor Invoice Management > PO Based Invoice Configuration > Parked
Invoice Processing Configuration > Rollout Criteria (Workflow Start
Conditions) > Allowed Company Codes, Plants, Document Types.
2. In the Allowed Company Codes screen, select either both PO Invoice Process
and Non PO Invoice Process or only one of the check boxes for the respective
Company Code.
3. Click New entries to add a company code.

Save your settings when finished.
4. Double-click Allowed Plants and Allowed Document Types in the navigation

panel to switch to the respective screens and define the rollout criteria for plants
and document types, as described for company codes.
The respective receiver function module triggers the workflow based on the
data in the tables. The workflow is triggered when there is no data maintained
in the table(s) or the data meets all the conditions such as company code,
document type and plant (only for PO invoices).

VIM070500-03-CGD-EN-1
6.1. Defining Rollout Criteria for the PO Parking Process
6.1.1 Event Linkages

In this step, you define the standard event linkage delivered by OpenText as active.
The correctly maintained event that is created for PO Parking ensures that an
appropriate action is carried out when a PO document is parked.
Caution
If you change the configuration in this section, the PO parking process
might not trigger at all.
To define the standard event linkage as active:
1. To access the Event Type Linkages screen, run the /OPT/VIM_IMG241

transaction.
Alternatively, navigate to Vendor Invoice Management > PO Based Invoice
Configuration > Parked Invoice Processing Configuration > Rollout Criteria
(Workflow Start Conditions) > Event Linkages (PO Parked Invoices).
2. Make sure the Linkage Activated check box is selected.

VIM070500-03-CGD-EN-1
6.2 Defining Rollout Criteria for the PO Blocking

Process
In this section, you define when or for which categories the VIM PO blocking
process needs to be triggered. For example, if you want to apply the blocking
process for only a specific subset of company codes, document types, and plants,
you can use the rollout criteria to do it.
Note: For a description of the configuration necessary for the PO blocking

process, see “PO Blocking Process Configuration“ on page 291.
Company codes, document types, and plants are part of the rollout criteria for
the PO parking process and the PO blocking process. For details, see “Defining
Rollout Criteria for the PO Parking Process” on page 77.
To completely disallow the PO blocking process, deactivate the event linkage as

described in “Event Linkages” on page 81.
Vendor Invoice Management > PO Based Invoice Configuration > Blocked
Process Configuration > Rollout Criteria (Workflow Start Conditions) >
Allowed Company Codes, Plants, Document Types.
Company Code.

VIM070500-03-CGD-EN-1
6.2. Defining Rollout Criteria for the PO Blocking Process
4. Double-click Allowed Plants and Allowed Document Types in the navigation

panel to switch to the respective screens and define the rollout criteria for plants
and document types, as described for company codes.
in the table(s) or the data meets all the conditions such as company code,
document type, and plant.

If correctly maintained, the event created for the PO blocking process will ensure
that an appropriate action will be carried out when a PO document is posted with a
blocking reason.
Caution
If you change the configuration in this section, the PO blocking process

transaction.
Configuration > Blocked Process Configuration > Rollout Criteria (Workflow
Start Conditions) > Event Linkages for Process (PO Blocked Invoices).
Notes
• You must activate this linkage if you want to use posted approval for
PO invoices, because the event to trigger posted approval is generated
in the receiver function module /OPT/BL_PO_BLK_RECEIVER. Make sure
that your setting of rollout criteria does not prevent the execution of the
receiver function module.
• The recommended event linkage is with receiver TS00275264. You can
use the /OPT/VIM_IMG311 transaction for the following purposes:
• to switch the event linkage with receiver WS00275264 off
• to switch the event linkage with receiver TS00275264 on or off

VIM070500-03-CGD-EN-1
6.3 Defining Rollout Criteria for the Non PO Parking

Process
In this step, you define when the VIM Non PO parking process needs to be
triggered. For example, you might want to apply VIM for some specific company
code/document types. For other company codes, you might want to use standard
SAP processes. In this case, the rollout must be maintained with correct company
code/document types.
Note: For a description of the configuration necessary for the Non PO parking
process, see “Non PO Parking Process Configuration“ on page 313.
To completely disallow the Non PO parking process, deactivate the event linkage as
described in “Event Linkages” on page 83.
Note: Company codes, document types, and plants are part of the rollout
criteria for the PO parking process and the PO blocking process. For the Non
PO parking process, company codes and document types are part of the rollout
criteria.
Rollout company codes and document types are maintained in the respective tables
by using the OpenText Customization:
Company codes
/OPT/VIM_CCODE_A
Document types
/OPT/VIM_DTYPE_A
Vendor Invoice Management > Non PO Based Invoice Configuration >
Parked Invoice Processing Configuration > Rollout Criteria (Workflow Start
Conditions) > Allowed Company Codes, Plants, Document Types.
Note: You cannot maintain plants for Non PO invoices.

VIM070500-03-CGD-EN-1
6.3. Defining Rollout Criteria for the Non PO Parking Process
Company Code.

4. Double-click Allowed Document Types in the navigation panel to switch to the

Allowed Document Types screen and define the rollout criteria for document
types, as described for company codes.
in the table(s) or the data meets all the conditions such as company code and
document type.

The correctly maintained event that is created for Non PO Parking ensures that an
appropriate action is carried out when a Non PO document is parked.
Caution
If you change the configuration in this section, the Non PO parking process

transaction.

VIM070500-03-CGD-EN-1
Alternatively, navigate to Vendor Invoice Management > Non PO Based

Invoice Configuration > Parked Invoice Processing Configuration > Rollout
Criteria (Workflow Start Conditions) > Event Linkage for Processes (Non PO).

VIM070500-03-CGD-EN-1
Part 3
Advanced Configuration
Part 3 Advanced Configuration
This part describes the advanced customizing. This customizing changes the VIM
baseline and partly includes extensions and customer exits. An example is the DP
process configuration.
Important
If you create new elements from baseline elements in the advanced
configuration, do not change the baseline configuration but only copy it. Use
element names that begin with Z and numeric elements with 800 or 900. If
you need to enhance the VIM document status, use alphanumeric values (for
example Z1). VIM has already occupied the whole range between 00 and 99.

VIM070500-03-CGD-EN-1
Chapter 7
Authorization Checks
VIM implements authorization checks in several reports, for the COA maintenance
transaction /OPT/AR_COA, for the indexing screen, and for VIM Workplace.
In the reports, in the indexing screen, and in VIM Workplace, the authorization
checks ensure that SAP users working with VIM are able to see and process only the
information that they are authorized for. In the COA maintenance, the authorization
checks make sure that the user is allowed to display or maintain the entries.
For backward compatibility reasons, the authorization checks are disabled in the
standard configuration. You can enable them on demand as described in “Enabling
VIM Authorization Checks Globally” on page 95.
With authorization checks activated, the information in the corresponding reports

and in VIM Workplace is filtered according to the settings. The documents or work
items for which the user is not authorized will not be shown. The COA maintenance
transaction also filters out unauthorized records and displays a warning in this case.
7.1 Available Authorization Checks

7.1.1 Reporting
The authorization checks that are currently implemented check the company code of
the document header.
If you run VIM in a multiple backend landscape, the data for the Central Reporting
module is normally collected from more than one system. It may be important to
distinguish between documents arriving from different systems even if they have
the same company code. Because of this, OpenText provides the new authorization
object J_6NIM_BUK, which has the following check fields: activity, logical system,
and company code. The activity checked currently in the reports is 03 - Display.
The logical system and the company code correspond to the document source.
In case of VIM Analytics and Current Liability Report, the data that is displayed
comes from the current (local) system only. Therefore, these reports use a blank
logical system value when checking the authorizations.
Table 7-1 summarizes the available checks.

VIM070500-03-CGD-EN-1
Chapter 7 Authorization Checks
Table 7-1: Authorization checks - Reporting
Transaction code Description Comment

/OPT/VIM_VA2 VIM Analytics Checked with blank logical
/OPT/VIM_VA21 system value.
/OPT/VIM_VA22
/OPT/VIM_VA23
/OPT/VIM_VA24
/OPT/VAN_LIABILITY Current Liability Report Checked with blank logical
system value.
/OPT/VIM_AGING Aging Report Checked with actual logical
system of each document.
/OPT/VIM_AUDIT Central Audit Report Checked with actual logical
/OPT/VIM_EXCP1 Exception Analysis Report Checked with actual logical
/OPT/VIM_KPA1 Key Process Analytics Checked with actual logical
Report system of each document.
/OPT/VIM_PROD1 Productivity Report Checked with actual logical
/OPT/VIM_SUMM Summary Report Checked with actual logical
All reports perform the checks for the blank value of the company code whenever it
is relevant for DP documents. If the authorization checks are active, the documents
with a blank company code are not shown to all users, but are checked as are all
other documents. Therefore, unless you are granting “all values” access with an
asterisk (*), it is important to allow the display by adding the empty company code
value in the authorization profile. The value to enter is ' ', that is a space
surrounded by single quotes. For the OpenText authorization object J_6NIM_BUK,
the authorization profiles in the central system must include entries with blank
company code for the central and satellite systems as needed.
Similarly, to grant access to local documents in VIM Analytics and Current Liability
Report, you must maintain the entries with blank logical system in the authorization
profiles. You must do this even if at the same time, for the multiple backend
scenario, the exact logical system name of the local system is already added into the
authorization profiles.

VIM070500-03-CGD-EN-1
7.1. Available Authorization Checks
7.1.2 COA Maintenance

The COA maintenance transaction is using four new authorization objects, one for
each of its tabs: User Details, Approval Limit/LevelCOA Details, and Coder
Settings.
All authorization checks examine the SAP user group of corresponding SAP user in
the user map, or a blank user group of non-SAP users is entered. The following
screenshot from the SU01 transaction shows the field being checked.
The checks of the approval limits and coder assignments will also check the
company code of the record. All three objects support the following activities for the
authorization checks: 01- Create, 02 - Change, and 03 - Display.
Table 7-2 summarizes the authorization checks available in the COA maintenance.
Table 7-2: Authorization checks - COA
Transaction area Authorization object What is being checked

name
User map J_6NIM_CA1 User group
Approval limits J_6NIM_CA4 Company code
Approver list J_6NIM_CA5 User group, company code
Coder Details J_6NIM_CA3 User group, company code
When maintaining the authorization profiles, it is important to decide whether the

blank values for the user group and company codes have to be included in the
authorizations list.
If you do not use the user group field in the SAP user master of the corresponding
SAP user, enter a <blank> value for the user group in the authorization profile. Also
enter a <blank> value for the user group in the authorization profile if the SAP user is
not maintained (for example for pure portal users). The blank company code will be

VIM070500-03-CGD-EN-1
used whenever the company code is not entered or is entered as “*” in COA Details
or Coder Details.
If Coder Details is set to “Use Requester” mode so that the company code is not
used, empty company code values must be used in the authorization profiles. When
switching the setup from “Use Requester” to other modes, all company code values
in the Coder Details have to be properly populated. If needed, this must be
performed by a user who has the coder maintenance authorization for all company
codes.
Whenever the data is saved, in all four screens, the maintenance transaction
performs consistency checks on the changed data. This also includes the entries that
are not shown to the user because of missing authorization. This means, both the
displayed list and the hidden list are checked together. An inconsistency could be
reported because of the hidden entries. In case of Coder Details checks, the
consistency errors for hidden entries will be reported as any that have the row index
99999. When such problems occur, the COA consistency has to be checked by a user
who has maximum authorizations for all four screens, for example by a Basis
administrator.
7.1.3 Indexing Screen

You can limit the processing of documents during the DP process by authorization
in the indexing screen. This makes it possible that processes cannot be executed
within the workflow by a user who is not authorized to display or maintain data, or
that data is only processed in display mode, if no changes are allowed.
Table 7-3 shows the authorization object used in the indexing screen (DP
dashboard).
Table 7-3: Authorization checks - indexing screen
Transaction area Authorization object Activities What is being

name checked
Processing and change J_6NIM_BC1 Display / Change Company code
mode
7.1.4 VIM Workplace

In VIM Workplace (/OPT/VIM_WP transaction), several authority checks are
implemented to protect UI-related functionalities, selected data content, and the
performing of actions. As VIM Workplace offers full multiple backend support, the
authorizations related to data selection and performing of actions are checked
directly on the corresponding backend system. UI-related authorization checks and
authorization checks controlling the general structure of the VIM Workplace are
always directly performed on the system where the VIM Workplace is currently
running.
Note: With VIM Workplace, you can run work items that are not in your own
inbox, such as Work Views Other, Team, or All. If you want to restrict this

VIM070500-03-CGD-EN-1
7.1. Available Authorization Checks
possibility, you must protect it against the authorization objects J_6NIM_WP8

or J_6NIM_WP9.
Table 7-4 summarizes the authorization checks available in VIM Workplace.
Table 7-4: Authorization checks - VIM Workplace
Transaction area Authorization Activities What is being Where is the

object name checked authorization
check
executed
General J_6NIM_WP0 Change General Local System
Functionality Function (for
example
Maintain
Substitute)
UI Functionality J_6NIM_WP1 Change UI Function Local System
Work Views J_6NIM_WP2 Change Work View Local System
Team J_6NIM_WP3 Display, Activity Local System
Configuration Change
System Selection J_6NIM_WP4 Change Logical System Local System
Selection Tabs J_6NIM_WP5 Display Logical Local System
System, Work
View,
Selection Tab
Data Selection J_6NIM_WP6 Display Work View, Corresponding
Selection Tab, Backend
Company System
Code
Data Selection J_6NIM_WP7 Display Work View, Corresponding
VIM System
Document
Type
Execute Action J_6NIM_WP8 Execute Work View, Corresponding
Action System
Authority
Group,
Company
Code

VIM070500-03-CGD-EN-1
Transaction area Authorization Activities What is being Where is the

object name checked authorization
check
executed
Execute Action J_6NIM_WP9 Execute Work View, Corresponding
Action System
Authority
Group, VIM
Document
Type
Note: If your VIM system does not run in a multiple backend environment, all
authorization checks are performed on the same local system. In this case, a
transaction assignment in SU24 is possible for all authorization checks, using
the proposal provided by OpenText. For more information, see “Configuring
the Authorization Checks” on page 93.
In a multiple backend environment, the authorization checks are performed in

a remote system. Corresponding authorizations must be added to profiles
manually.
7.1.5 Invoice Exception Dashboards

The authorization check with company code is implemented in the following
dashboards:
• Parked Non-PO invoice

• Parked PO invoice
• Blocked PO invoice, line item level
• Blocked PO invoice, header level
The authorization checks use the authorization object J_6NIM_BC1. Any “Display”
or “Change” authorizations allow the user to execute work items.
Table 7-5 shows the authorization object used in the exception dashboards.
Table 7-5: Authorization checks - exception dashboards
Transaction area Authorization object Activities What is being

name checked
Processing and change J_6NIM_BC1 Display / Change Company code
mode

VIM070500-03-CGD-EN-1
7.2. Configuring the Authorization Checks
7.2 Configuring the Authorization Checks

To enable the authorization checks in VIM, you must perform the following steps:
Add or verify the authorizations of SAP users

This may include adding the SAP and VIM authorization objects to the existing
SAP profiles or creating new profiles and assigning them to users. You can also
perform transaction assignments in SU24, to be used later in the profile
generation tool.
Enable VIM authorization checks globally

You can switch the authorization checks on and off completely, using a constant
in the table /PTGWFI/Z_CONST.
7.2.1 Adjusting the SAP Authorization Profiles Manually

Use standard SAP authorization administration tools like Profile Generator PFCG.
After you have adjusted the existing profiles or created new ones, the profile
SAP_ALL needs to be regenerated, for example, in the transaction SU21.
7.2.2 Adjusting Authorizations Assignment

The maintenance of authorization profiles with SU24 using transaction assignment
can be made easier. For this purpose, OpenText delivers standard authorization
assignments for relevant VIM transactions as part of the installation packages. This
section describes the configuration steps relevant for VIM. Refer to the standard SAP
documentation for more information about the relevant SAP transactions.
The installation packages provide only the standard entries for “SAP” assignments,
which means those visible in SU22. Copying of the standard VIM assignments into
the “customer” tables (SU24) must be performed through the standard SAP
download / upload programs RSU22DOWN and RSU22UPLD in the following way.
To copy standard VIM assignments into customer tables:
1. Import the VIM installation packages.
2. Download the authorization to transaction assignment data into a file using

RSU22DOWN for the transaction codes listed in Transaction codes for the
assignments on page 94.
3. Run the upload program RSU22UPLD, and enter the same list of VIM
transactions.
4. Make sure you set the check boxes as shown in the following screenshot:

VIM070500-03-CGD-EN-1
Note: You can perform a test run first (select Test Mode) and also use the
option to create a transport file if needed (select Enter Data in Transport).
5. When asked for the file to use, select the same file created by the download
program.
6. When you have successfully completed the previous steps, adjust the
transaction assignments, if needed, in SU24. Then, you can use them in the
profile generation tool.
Transaction codes for the assignments

• /OPT/VIM_VA2
• /OPT/VIM_VA21
• /OPT/VIM_VA22
• /OPT/VIM_VA23
• /OPT/VIM_VA24
• /OPT/VAN_LIABILITY
• /OPT/VIM_AGING
• /OPT/VIM_AUDIT
• /OPT/VIM_EXCP1
• /OPT/VIM_KPA1
• /OPT/VIM_PROD1
• /OPT/VIM_SUMM

VIM070500-03-CGD-EN-1
7.3. Authorization Group for VIM Tables
• /OPT/AR_COA
• /OPT/VIM_WP
Note: For the authorization checks added or changed in future support

packages, OpenText will be delivering a list of transactions whose assignments
can be completely copied into the “customer” list of SU24, using the procedure
described in this section. The existing transaction assignments must be verified
in SU25 (Postprocess step 2B).
7.2.3 Enabling VIM Authorization Checks Globally

In the default VIM delivery, all authorization checks are disabled by default for
backward compatibility reasons. You can activate the checks by changing or creating
the value of the Z constant with Product Code 009 and Constant
AUTH_CHECK_ACTIVE in the table /PTGWFI/Z_CONST. The value can be changed in the
SM30 transaction. To enable authorization checks globally, set the Constant Value to
X.
7.3 Authorization Group for VIM Tables

VIM uses a specific authorization group /OPT for the VIM specific tables.
Some VIM tables are being delivered without this authorization group. To set this
authorization group on customer’s site, a report is available. The report is called /
OPT/VIM_AUTHGROUP_TABLE_CHNG. You can use it to update:
• only configuration tables, or

• only transaction tables, or
• all VIM tables
If you run the report in test mode, the names and the number of tables with default
authorization group are displayed.
If you run the report in normal mode, the report prompts for a transport request
after successfully updating the data. This transport must be transported to quality
and production clients.

VIM070500-03-CGD-EN-1
Chapter 8
Incoming Document Processing
VIM offers an Incoming Document Handling (IDH) framework to receive and

handle most kinds of incoming e-documents. Therefore, you can customize existing
input channels and also add new channels to the framework. You must define a
framework process and link it to one or more channel IDs to send incoming
documents to the workflow. For the IDOC and ICC channels, no external profile and
Process ID are necessary.
Starting with OpenText™ Business Center for SAP® Solutions (Business Center) 10.0
SP1 and Business Center Solution Integration for Vendor Invoice Management 10.0
SP2, you can use Business Center Inbound Configuration to handle incoming
document processing. For more information, see section 4 “Inbound Configuration”
in OpenText Business Center for SAP Solutions - Configuration Guide (BOCP-CGD).
Note: Business Center Inbound Configuration replaces the Incoming

Document Handling (IDH) framework and the ICC Dispatcher framework
with VIM 7.5 SP3. If you implement VIM new with VIM 7.5 SP3, you must use
Business Center Inbound Configuration. When upgrading to VIM 7.5 SP3, you
can use Business Center Inbound Configuration or ICC Dispatcher and IDH.
However, keep in mind that ICC Dispatcher and IDH will be discarded in the
future.
If you use Business Center Inbound Configuration, only the following customizing
steps are relevant for VIM.
• “Maintaining Channels” on page 98

• “Maintaining the VIM Field Mapping” on page 101
• “Connecting Using the Document Pipeline” on page 112
• “Rendering IDocs to PDF” on page 123
• “Testing an IDoc” on page 126
Each document runs through defined workflow steps indicated by the framework
process. Workflow steps consist of an ordered number of Service Modules. These
Service Modules are integrated components of the framework that offers the defined
functionality. You can enhance the Service Modules by adding new entries in the
customizing.
The Incoming Document Processing customizing structure in the OpenText

Configuration contains all views that are relevant for handling incoming
documents: Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice
Management > Document Processing Configuration > General Configuration >
Incoming Document Processing.

VIM070500-03-CGD-EN-1
Chapter 8 Incoming Document Processing
Note: If additional input channels besides ICC and IDOC are used within the
IDH framework, it is necessary to run periodic jobs. For more information, see
section 5.5 “Scheduling Batch Jobs for the IDH Framework” in OpenText Vendor
Invoice Management for SAP Solutions - Administration Guide (VIM-AGD).
8.1 Maintaining Channels

A channel uniquely identifies the source of an incoming invoice to the VIM system
across the landscape. Channels drive the System Determination Procedure in a
multiple backend system and drive the set of mapping to be performed.
To maintain the incoming channels:
1. Run the /n/OPT/VIM_IDH_CHNL_CL transaction.

Alternatively, in OpenText Configuration, navigate to the menu path Vendor
Invoice Management > Document Processing Configuration > General
Configuration > Incoming Document Processing > Maintain Channels.
The Channel Setup Overview shows a list of all existing Channel IDs.
2. Make sure that all relevant VIM import channels are included in the table.
Important
The Web Dynpro application of the KPI Dashboard can display a maximum
of 10 channels.

VIM070500-03-CGD-EN-1
8.1. Maintaining Channels
8.1.1 Creating a Channel

Important
If you use Business Center Inbound Configuration to handle incoming
document processing, make sure that the channel ID in VIM is identical with
the channel ID in Business Center Inbound Configuration. This is necessary
for a successful mapping.
To create a channel:
1. In the Channel Setup Overview screen, click New Entries.
2. Configure the new channel, using the following parameters:
Channel Type
Select the channel type from the list.
Short Description, Text

Enter the channel description. It is language dependent.
Mapping ID
Enter the Mapping ID.
You maintain mapping IDs for each channel, for example IDOC. The
mapping ID is used to determine whether mapping is done through a
custom function module or field to field.
Sys Det. ID
If you want to link a System Determination ID to the channel, enter the
System Determination ID. If no System Determination ID is linked here, the
Default Company Code Look up system determination can be used in a
multiple system scenario.
Ignore Mapping Error

Errors might occur during the mapping stage, when data from a particular
channel flows into the SAP ERP system.
Select this check box to determine that these errors are ignored for the
channel, and the VIM workflow is started.

VIM070500-03-CGD-EN-1
Clear the check box to determine that, in case of a mapping error,

processing stops at this point and the VIM workflow is not started.
Process ID
Enter the process ID.
You can maintain process IDs for the channel. The process ID is used to
determine which process handling the incoming document is linked to.
Notes
• For the IDoc input channel, a process customizing is not possible.
• If you use Business Center Inbound Configuration to handle
incoming document processing, configuring the process ID is no
longer necessary. The document handler performs this task.
3. Save your settings.
8.1.2 Creating External Profiles

You can add one or more external profiles to a channel ID. An external profile
defines unique identifiers for a specific incoming document channel. This offers the
possibility to handle different input variants according to the characteristics of the
incoming document.
Note: If you use Business Center Inbound Configuration to handle incoming

document processing, creating external profiles is no longer necessary.
To create an external profile:
1. Select a channel in the Channel Setup Overview screen and double-click

External Profiles.
2. To create a new profile, click New Entries.
3. Configure the new profile, using the following parameters:
External Profile
Enter an external profile ID, dependent on the channel type, for example an
email address for channel type Email.
Document Class
Enter the document class.
VIM070500-03-CGD-EN-1
8.2. Maintaining the VIM Field Mapping
Archive Document Type

Enter the archive document type. The entry must match the entered
document class.
Description
Enter the external profile description. It is language dependent.
8.2 Maintaining the VIM Field Mapping

Invoices come through different channels, for example from ICC, from IDoc, or by
email. Parameters or values of the incoming invoice will be mapped to parameters
or values of the indexing document. The mapping can be different, depending on
the channel. Therefore, a mapping set or mapping ID is assigned for every channel.
You can create a Mapping ID to logically group a mapping set for a particular
channel. A Mapping ID is tied to a channel so that proper mapping is performed for
an incoming invoice for that channel.
In this step, you map Intermediate fields to VIM fields.
To configure the VIM field mapping:
1. Run the /n/OPT/VIM_MAPV transaction.

Alternatively, run the /n/OPT/SPRO transaction and navigate to the menu path
Vendor Invoice Management > Document Processing Configuration >
General Configuration > Incoming Document Processing > Maintain
Mapping ID.
2. If you want to configure the complete mapping using a function module,

double-click a line to open the Mapping Setup Details screen.
3. Configure the Mapping ID, using the following parameter:
Ext Field Mapping FM

If simple one-to-one mapping does not suffice, enter a custom function
module to perform the mapping. The function module must be compatible
with the interface /OPT/DO_MAPPING. However, do not use /
OPT/DO_MAPPING itself, or else you will get recursive calls.
VIM070500-03-CGD-EN-1
4. In the Mapping Setup Overview screen, select a Mapping ID and double-click

Field Mapping in the Dialog Structure.
5. Configure the field mapping, using the following parameters:
External Field Name

Intermediate field name (case-sensitive), as supplied by the external system
Field Type
Select field level Header or Item.
Document Field Name
Enter the Index field name (VIM field).
The header level SAP fields come from the structure /OPT/VIM_1RHEAD. The
item level SAP fields come from the structure /OPT/VIM_1RITEM_DATA.
Function name
If there is any necessity to convert the format of the data coming from the
external system, enter a conversion function module for a particular field.
Any function module that you enter here, whether SAP standard or a
custom one, should be compatible with the interface of function module
CONVERSION_EXIT_ALPHA_INPUT.
Ignore
Enter characters that are deleted in an extra step before mapping continues.
This is useful, for example, if there are apostrophes in the Reference
Number. Enter the apostrophe in the Ignore Chars field in the XBLNR line, to
avoid a short dump in duplicate check.
The field can contain up to 6 characters.
Condense
To remove blank characters in the input string, enter X in this field.
Note: Mapping a list of PO numbers or DN numbers from an external channel

to VIM is not as flexible as it was in previous versions of VIM. The strings with
VIM070500-03-CGD-EN-1
8.2. Maintaining the VIM Field Mapping
the PO number list and the DN number list must be presented to VIM with the
fix external names ListPO and ListDN. These are hard-coded keywords for
VIM. VIM will parse the string and enter the numbers into the /
OPT/VIM_1PO_DN table. The mapping is activated, as soon as the keyword is
present in the mapping table.
In addition to the standard field mapping, automated field enhancement offers the
possibility to set or change field values statically or dynamically.
To configure automated field enhancement:
1. In the Mapping Setup Overview screen, select a Mapping ID and double-click

Automated Field Enhancement in the Dialog Structure.
2. Configure the field enhancement, using the following parameters:
Counter
To specify a call order of the field enhancement, enter a number up to 4
digits.
Field Type
Select field level Header or Item.
Document Field Name

Enter the Index field name (VIM field).
Field Processing Type

Select the field processing type from the list.
Field Value
If selected in Field Processing Type, enter a fixed value or a system
variable.
Enhanced Field Function Module

If selected in Field Processing Type, enter the function module to
implement the enhanced field function.
Satellite
If the exit function module must be executed on a satellite system, select this
check box. The check box is only available on the central instance in a
multiple backend system.
VIM070500-03-CGD-EN-1
8.3 Maintaining Service Modules

A Service Module defines a specific functionality that can be used by one or more
processes inside the incoming document framework.
Starting with Business Center 10.0 SP1 and Business Center Solution Integration for
Vendor Invoice Management 10.0 SP2, you can use Business Center Inbound
Configuration to handle incoming document processing. For more information
about how to configure document handler and corresponding service modules, see
section 4.4 “Customizing incoming documents through the document handler” in
OpenText Business Center for SAP Solutions - Configuration Guide (BOCP-CGD).
To create a service module:
1. Run the /n/OPT/VIM_IDH_MODU transaction.

Alternatively, in the OpenText Configuration, navigate to the menu path
General Configuration > Incoming Document Processing > Maintain Service
Modules.
2. In the Service Module Customizing screen, click New Entries.
3. Configure the new module, using the following parameters:
Class Name
Enter the class name of the module where the implementation is coded.
Start Status
Enter the module start status that will be set when the processing of the
module starts.
End Status
Enter the module end status that will be set when the processing of the
module has been finished successfully.
VIM070500-03-CGD-EN-1
8.4. Customizing the Email Channel
Error Status
Enter the module error status that will be set when the processing of the
module ends with an error.
Description
Enter the service module description. It is language dependent.
Time Limit (seconds)
Enter the maximum processing time in seconds. The default entry is set to
60 seconds. If the time limit is reached, the processing of the module is set to
error status.
Function Module
Enter the name of the function module or class that offers additional
functionality, for example a function module or class to parse XML
documents.
Transformation
Enter the name of the stylesheet script used for transformation, for example
a function module to transform XML input.
8.4 Customizing the Email Channel

The kernel of the SAP NetWeaver Application Server ABAP supports the Simple
Mail Transfer Protocol (SMTP). This enables email exchange between the SAP ERP
system and each SMTP mail server, without having to use additional external
components.
All information of the incoming email object is logged. The information can be used
for all purposes later on, for example for reporting. The product standard does not
support sending emails back to the sender or forwarding messages to SAP Business
Workplace.
Prerequisites
• The mail server must be SMTP-compatible.
• The customized address space for the default domain must match the DNS
address on the external mail server.
Important
If you want to process emails with several attachments, make sure that the
document type /OPT/OTHER is correctly maintained in the OAC3 transaction.
See also “Linking Archive Document Type to VIM Business Object”
on page 36.
about how to configure document registration for email and document handler, see
VIM070500-03-CGD-EN-1
section 4.4.2.3 “Customizing the incoming email registration type” in OpenText

Business Center for SAP Solutions - Configuration Guide (BOCP-CGD).
To activate the email processing for Business Center Inbound Configuration, you
must assign the corresponding exit class delivered with Business Center in the
Inbound Processing configuration in the SCOT transaction. For more information,
see “Administering SAPconnect” on page 110.
8.4.1 Customizing the Workflow Using the Email Channel

The incoming email channel allows you to enhance the workflow customizing
triggered by specific email information.
Handling The start of the incoming document workflow can also be triggered by specific
additional information that is extracted from the incoming email. For example, you can specify
documents
which type of attached document should initiate the incoming document workflow.
If the email has other documents with different mime types attached, these
documents are handled as simple attachments to the specific work item.
Customizing The constant parameter IDH_MAIL_ATT_HANDLER sets the specific function module
for additional document handling.
Run the SM30 transaction to maintain the /PTGWFI/Z_CONST table, and locate the
record with Product Code 005 and Constant IDH_MAIL_ATT_HANDLER.
The constant value for baseline delivery is <empty>. Programming example: /

OPT/C_IDH_CUSTOM_MAIL_HANDLER.
Logging email All incoming email data received via the SMTP interface can be viewed in
data SAPconnect.
To display received send requests:
1. To open Inbound Sent Requests (SMTP), run the SCOT transaction.
2. On the Utilities menu, click Inbox Overview.

The program displays send requests received using the SAPconnect interface.
Note: Depending on the selection criteria, you can view all specific
incoming emails.
VIM070500-03-CGD-EN-1
8.4.2 Checking the SMTP Service

1. To check the customizing of the SMTP service, run the SMICM transaction.
2. On the Goto menu, click Services.

The SMTP service is active on port 25.
3. If the port is not set to 25, select the SMTP service. In the Service menu, click
Change.
4. Set the port value to 25 and save the changes.
8.4.3 Configuring the Profile Parameters

If you want to use the SMTP function, you must adjust the system profile of the SAP
ERP system.
To configure profile parameters:
1. To access the Edit Profiles screen, run the RZ10 transaction.
VIM070500-03-CGD-EN-1
2. Choose the instance profile, click Extended maintenance, and then click
Change.
3. Configure the following new profile parameters as a Name = Value pair.

The placeholder <*> stands for the sequence number (starting at zero) of
frequently occurring parameters.
icm/server_port_<*> = PROT=SMTP,PORT=25
This parameter opens a TCP/IP port for receiving emails through the SMTP
plug-in.
Note: After adding this parameter, the ICM service is set

automatically to port 25 when the application server is restarted.
is/SMTP/virt_host_<*> = <host>:<port>, <port>,...;

This parameter defines a virtual email host for receiving emails. If all
incoming emails are received and processed by one single client of the SAP
ERP system, this parameter is not required.
8.4.4 Creating a Service User

You must create a service user for processing incoming emails in every SAP ERP
system client in which you want to receive emails. Every user that receives emails in
an SAP ERP system requires an Internet email address. This is also used as a sender
address.
To create a service user:
1. Run the SU01 transaction.
2. Create a user with type Service and assign the profile S_A.SCON to this user.
VIM070500-03-CGD-EN-1
3. On the Address tab, under E-Mail, enter the Internet email address for the user.
8.4.5 Assigning the SAP ERP System Client to an SMTP

Server
Every SAP ERP system client that receives and processes incoming emails must have
an SMTP server. One SMTP server (called SAPconnect) has already been created in
the SICF transaction and is delivered with every SAP ERP system.
To assign the SAP ERP system client to an SMTP server:
1. Run the SICF transaction and open the Virtual Host SAPCONNECT.
2. Select SAPconnect. To display the Create/Change a Virtual Host screen, click

Change .
3. Configure the following settings on the SMTP servers:
Host Data
Enter the sequence number of the is/SMTP/virt_host_<*> parameter from
the profile. For more information, see “Configuring the Profile Parameters”
on page 107. If you have only created one client and therefore have not
specified this parameter type, enter 0.
Logon Data
Enter the logon data of the system user that you created for the incoming
emails.
Handler List
At position 1, enter CL_SMTP_EXT_SAPCONNECT.
4. For each additional client, create another SMTP server.
Note: You must activate each SMTP server (Service/Virt. Host > Activate)
after creating or changing it. Inactive servers appear dimmed.
VIM070500-03-CGD-EN-1
8.4.6 Administering SAPconnect

You must configure SAPconnect settings for every client that is used for send
processes.
To administer SAPconnect:
1. Run the SCOT transaction.
2. On the Settings menu, click Default Domain.
3. Default Domain
Define the domain of the SAP ERP system client.
This action has the following consequences:
• The SMTP plug-in logs on to the email server using this domain as the ID.
• The message ID of the outbound emails is assembled with this domain.
• An SAP user might not have an Internet email address. If such a user sends
an email, a sender address consisting of the SAP user name and this domain
is generated.
Each client has an SMTP node. This node is created by the SAP ERP system and
cannot be deleted.
4. Nodes
Enter the specific customizing data like output format for SAP documents and
other types of documents. See details in the SAPconnect documentation (http://
VIM070500-03-CGD-EN-1
help.sap.com/saphelp_nw70/helpdata/en/af/73563c1e734f0fe10000000a114084/
content.htm).
5. Inbound Processing
You may want incoming emails that have a particular address or particular
content to automatically start a program that processes these emails. In this
case, configure the following on the menu: Settings > Inbound Processing.
6. Add new entries using the following parameters:
Communication Type
Select Internet Mail.
Recipient Address
Enter email address.
Document Class
Enter a wildcard. This parameter will be set in the channel ID customizing.
For more information, see “Creating External Profiles” on page 100.
Exit Name
Enter the default framework class name /OPT/CL_C_IDH_CHANNEL_EMAIL.
Call Sequence
Enter 1 (not needed).
For a more detailed description of how to enable the Simple Mail Transfer Protocol
Service in SAP ERP, see the SAP Help: http://help.sap.com/saphelp_nw70/helpdata/
en/af/73563c1e734f0fe10000000a114084/content.htm.
VIM070500-03-CGD-EN-1
8.5 Connecting Using the Document Pipeline

You can handle incoming documents using the OpenText Document Pipeline
(Document Pipeline).
You must link the Document Pipeline processing to the defined function module of
the IDH framework inside SAP ERP. You must set a specific RFC mode that must
match the customizing entry on the remote Document Pipeline.
Add a new entry to table J_6NGTE26 with the following values:
RFC_Mode
8
FUNCNAME
/OPT/C_IDH_DP_PIPELINE_HANDLER
The Document Pipeline typically requires one COMMANDS and one IXATTR file in
addition to the actual image file (for example image.pdf) and the LOG file. See the
following example:
Example 8-1: Document Pipeline: COMMANDS and IXATTR file

COMMANDS
R3_CLIENT 800
R3_DESTINATION DW3
USE_VR4WFL 8
DOCTYPE PDF
COMP data PDF image.pdf
ARCHIVID Y4
IXATTR
NEWDOC
ATTRIBUTES /OPT/VIM_1HEAD|MANDT|CC|800|
ATTRIBUTES /OPT/VIM_1HEAD|DOCTYPE|CC|PDF|
ATTRIBUTES /OPT/VIM_1HEAD|LIFNR|CC|1277448|
ATTRIBUTES /OPT/VIM_1HEAD|BLDAT|DD|20120711|
ATTRIBUTES /OPT/VIM_1HEAD|RMWWR|CC|84715|
ATTRIBUTES /OPT/VIM_1HEAD|WAERS|CC|EUR|
ATTRIBUTES /OPT/VIM_1HEAD|WINDOWS_ID|CC|ERICCARTMAN|
ATTRIBUTES TOAV0|MANDT|CC|800|/OPT/VIM_1HEAD|
ATTRIBUTES TOAV0|AR_OBJECT|CC|ZNOOCR|/OPT/VIM_1HEAD|
ATTRIBUTES TOAV0|SAP_OBJECT|CC|/OPT/V1001|/OPT/VIM_1HEAD|
ARCHIVIDATTR TOAV0|ARCHIV_ID|CC|%s|/OPT/VIM_1HEAD|
DOCIDATTR TOAV0|ARC_DOC_ID|CC|%s|/OPT/VIM_1HEAD|
For more details about the Document Pipeline, see OpenText Document Pipelines -
Overview and Import Interfaces (AR-CDP).
VIM070500-03-CGD-EN-1
8.6. Maintaining Processes

about how to configure document registration for Document Pipeline and document
handler, see section 4.4.2.4 “Customizing the Document Pipeline registration type”
in OpenText Business Center for SAP Solutions - Configuration Guide (BOCP-CGD).
To activate the Document Pipeline processing for Business Center Inbound

Configuration, you must assign the corresponding exit function delivered with
Business Center in the J_6NGTE26 table and deliver the data according to the
interface described in section 4.4.2.4.1 “Maintaining general settings” in OpenText
8.6 Maintaining Processes

A process defines a workflow inside the incoming document framework. A process
can be linked to one or more channel IDs and describes a defined order of working
modules in the framework.
Configuration to handle incoming document processing. For more information, see
section 4.4 “Customizing incoming documents through the document handler” in
8.6.1 Creating a Process

1. Run the /n/OPT/VIM_IDH_PROC_CL transaction.
Alternatively, in the OpenText Configuration, navigate to the menu path
Processing.
2. In the Process Setup Overview screen, click New Entries.
3. Configure the new process, using the following parameters:
Process ID
Enter a unique process ID.
VIM070500-03-CGD-EN-1
Initial Status
Enter the initial status of the process, which will be set when starting the
framework process by registering a new work item to the workflow.
For a list of possible statuses with descriptions, click . To display and
expand statuses, refer to the search help table /OPT/VIM_T101.
End Status
Enter the end status of the process, which will be set when the framework
process has finished.
For a list of possible statuses with descriptions, click . To display and
expand statuses, refer to the search help table /OPT/VIM_T101.
Description
Enter the process description. It is language dependent.
8.6.2 Adding Processing Modules

You can add one or more processing modules to a process.
To add a processing module to a process:
1. Mark a process in the Process Setup Overview screen and double-click

Processing Modules in the Dialog Structure.
2. To add a processing module, click New Entries.

3. Add the new processing module, using the following parameters:
Module ID
Enter the module ID.
Counter
To specify a call order of the processing modules, enter a number with up to
4 digits.
Active
To activate the processing module, select this check box.
VIM070500-03-CGD-EN-1
8.7. EDI Configuration
8.7 EDI Configuration

The Electronic Data Interchange (EDI) scenario in VIM is based on the standard SAP
document format Intermediate Document (IDoc). IDocs allow different application
systems to be linked through a message-based interface. The following list shows
some examples of how you can benefit from using IDocs.
• Business documents are exchanged in a structured way in order to process them

automatically.
• The various degrees of structural complexity as displayed by different
application systems can be reduced to a structure which is as simple as possible.
Example: The structure of an SAP application document and the structure of the
corresponding EDI message under the UN/EDIFACT standard.
• IDocs allow extensive exception handling before the data is posted to the
application.
about how to configure document registration for IDoc and document handler, see
section 4.4.2.2 “Customizing the Inbound IDoc registration type” in OpenText
To activate the IDoc processing for Business Center Inbound Configuration, you
must assign the corresponding processing function delivered with Business Center
in the Inbound Function Module configuration in the BD51 transaction. For more
information, see “Defining Settings for the Inbound Function Module” on page 116.
8.7.1 Configuring General Settings

The inbound function module /OPT/DP_INBOUND_IDOC_PROC creates DP documents
from incoming IDocs and sends them to the DP process. To enable this, the
following configuration steps are necessary:
• “Defining Settings for the Inbound Function Module” on page 116

• “Linking the Inbound Function Module to IDoc Type and Message Type”
on page 116
• “Creating a New Process Code” on page 118
• “Configuring the Partner Profile” on page 119
VIM070500-03-CGD-EN-1
8.7.1.1 Defining Settings for the Inbound Function Module

In this step, you choose the input type for the IDocs.
To define settings for the inbound function module:
1. Run the BD51 transaction.
2. In the Characteristics of Inbound Function Modules view, click New Entries.
3. Define the inbound function module, using the following parameters:
Function module (inbound)

Enter /OPT/DP_INBOUND_IDOC_PROC.
Input type
Enter 0 (for Mass processing).
Dialog allowed
If you want to process IDocs in dialog mode, select this check box. With
baseline implementation, the check box is cleared.
4. Click Save .
8.7.1.2 Linking the Inbound Function Module to IDoc Type and Message
Type
In this step, you establish the link between the inbound function module, the basic
IDoc type, and the message type.
To link the inbound function module to IDoc type and message type:
1. Run the WE57 transaction.
2. In the IDoc: Assignment of FM to Log. Message and IDoc Type view, click
Change .
3. Click New Entries.
4. Configure the assignment using the following parameters.
VIM070500-03-CGD-EN-1
Function module
/OPT/DB_INBOUND_IDOC_PROC
Function type
Select Function Module.
Basic type
Enter the basic type, for example INVOIC02.
Message Type
Enter the message type, for example INVOIC.
Direction
Select Inbound.
Description
Enter a meaningful description.
5. Click Save .
VIM070500-03-CGD-EN-1
8.7.1.3 Creating a New Process Code

In this step, you create a new process code and assign the inbound function module
to this process code.
The process code is a logical name for the processing function module. The process
code is used to uniquely determine a function module that processes the received
IDoc data and converts an IDoc to an SAP document.
To create a new process code:

2. In the Inbound process code view, click Change .
3. Click New Entries.
4. Define the new process code, using the following parameters.
Process code
Enter the process code name.
Note: You can choose a name for the process code that suits your
needs.
Description
Enter a meaningful description.
VIM070500-03-CGD-EN-1
Identification
Enter the inbound function module /OPT/DB_INBOUND_IDOC_PROC.
Option ALE
Click Processing with ALE service.
Processing type
Click Processing by function module.
5. Click .
6. Double-click Logical message in the Dialog Structure.
7. Assign the new process code to the logical message using the following
parameters.
Process code
Process code name as defined in Step 4.
Message type
8. Click Save .
8.7.1.4 Configuring the Partner Profile

When data is exchanged between partners, it is important that sender and receiver
define the exact syntax and semantics of the data to be exchanged beforehand. The
partner profile defines the type of data and communication paths of that data
exchange.
In this step, you assign the new process code to the IDoc partner profile. You must
specify partner and partner type. You also must specify whether you define a profile
for inbound or outbound data exchange. You can use an existing partner profile. The
partner type must be Logical system (LS).
Tip: If you want to create a new partner profile, you must first create a new
logical system. See the SAP documentation for details.
VIM070500-03-CGD-EN-1
To configure the partner profile:
2. Select the partner profile under Partner Profiles > Partner Type LS.
3. Below the Inbound parmtrs. panel, click Add .
4. Configure the inbound parameters.
Partner No.
ID of the partner profile
Partn. Type
Partner Type: Enter LS for logical system.
Message type
5. On the Inbound options tab, enter the Process code that you created in
“Creating a New Process Code” on page 118.
6. Click Save .
VIM070500-03-CGD-EN-1
8.7.2 Configuring the Mapping

In an inbound process, when the IDoc hits SAP ERP, a predefined function module
is called to convert an IDoc to an SAP document. Some mapping is required between
the segment fields available in the IDoc and the internal fields that can be used to
create the SAP document.
In the EDI scenario, there are the following levels of mapping:
• The first level of mapping maps the IDoc data to Intermediate fields.
• The second level of mapping maps Intermediate fields to VIM fields (index
fields). The second level of mapping is maintained at the channel level.
Every type of incoming document, for example IDoc, is assigned to a channel.
Based on the mapping ID which is assigned to the channel, every type of
incoming document will be mapped differently. The mapping ID determines the
set of mappings from the Intermediate Fields to the VIM fields. For VIM, the
channel for the EDI scenario is IDOC. The Channel IDOC is assigned to the
mapping ID IDOC.
In multiple backend systems, the incoming IDocs are received and preprocessed in
the central system. After that, they are sent to the satellite system for further
processing. The satellite system is determined based on the company code. Each
system in the multiple backend system is identified by a logical system name. See
“Determining System by Company Code for Multiple Backend Systems”
on page 125.
To configure the mapping, you must do the following:
• “Configuring IDoc Field Mapping” on page 121

• “Configuring the VIM Field Mapping” on page 123
• “Creating a Channel ID” on page 123
8.7.2.1 Configuring IDoc Field Mapping

In this step, you map IDoc segment fields to Intermediate fields. Therefore, you
maintain the /OPT/VIM_T123 table.
To configure the IDoc field mapping:
1. Run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Configuration > Incoming Document Processing > Idoc Data Mapping.
2. In the Document Process - Mapping Fields for Automatic Indexing screen,

double-click a line to open a single field.
VIM070500-03-CGD-EN-1
3. Configure the field mapping, using the following parameters:
Obj. name
Development Object name: the IDoc type INVOIC02
Segm.type
Segment type in IDoc type
Field name
Segment field
IDOC Qualf(Fld/VAl)
Qualifier of the Segment
Qualifier Value
Value of Segment Qualifier
Field Type
Select either Header or Item type from the list.
Document Field Name

Enter the Intermediate field name.
Field Mapping Type

Select one of the following mapping types from the list:
• From IDOC Segment Field
• Constant (fixed value)
• System variable
• Function Module
Value
If you selected Constant (fixed value), System variable, or Function
Module as the field mapping type, enter the corresponding value.
VIM070500-03-CGD-EN-1
If you selected Function Module, you can use the /OPT/GET_YEAR or /

OPT/IDOC_UOM_ISO_TO_SAP function modules as a template.
Note: To transfer a list of PO numbers or delivery note numbers via IDoc, you
must use mapping entries in a special format. Define the key values to point to
the segment where the lists are stored, and use the following fixed values:
Field Type
H for Header
Document Field Name

empty
Field Mapping Type

D for Constant
Value
POLIST or DNLIST
8.7.2.2 Configuring the VIM Field Mapping

In this step, you map Intermediate fields to VIM fields. For details, see “Maintaining
the VIM Field Mapping” on page 101.
8.7.2.3 Creating a Channel ID

You maintain mapping IDs for each channel, for example IDOC. The mapping ID is
used to determine if mapping is done through a custom function module or field to
field. For details, see “Creating a Channel” on page 99.
8.7.3 Rendering IDocs to PDF

Whenever an invoice comes in through an IDoc, mapped IDoc data can be rendered
to a PDF file. Therefore, the PDF log configuration is used; for details, see “PDF Log“
on page 767.
about how to configure document registration for IDoc and document handler, see
section 4.4.2.2 “Customizing the Inbound IDoc registration type” in OpenText
To activate the PDF rendering of Idocs using Business Center Inbound

Configuration, you must assign the same document type in the registration for IDoc
in Business Center, see section 4.4.2.2.5 “Linking inbound IDoc with document
handler, channel, and classification” in OpenText Business Center for SAP Solutions -
Configuration Guide (BOCP-CGD). Additionally, a service module for document
creation must be available and activated in the handler processing , see section
VIM070500-03-CGD-EN-1
4.4.1.2 “Configuring modules for the required processing steps” in OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP-CGD).
Z constant To enable the PDF rendition, you must maintain the Z constant EDI_IMAGES_FM,
product code 005, in table /PTGWFI/Z_CONST. In Constant Value, enter a function
module, using the template /OPT/EDI_IMAGES_EXIT_TEMP. You can use the baseline
function module /OPT/EDI_IDOC_PDF_IMAGE.
To define a profile for the PDF rendition:
1. Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice

Management > Cross Component Configuration > PDF Log > Maintain
Customizing Profiles.
2. For the particular fields, see the following screenshot and “Defining Profiles for
the PDF Log” on page 767. The field description is very similar to the general
PDF log.
The IDoc rendition to PDF shows the following differences from the general
PDF log:
• The fields PDF Timezone and Time Zone do not apply for the IDOC
rendition.
• The Document type must be the same as the IDOC channel archive object
document type.
To assign profiles to VIM process steps:

2. In the Dialog Structure, double-click Assign Profiles to VIM Process Steps.
VIM070500-03-CGD-EN-1
3. Select the step 02 IDOC to PDF Invoice Creation.
4. Optional Maintain the company code (if required).
5. Assign the profile, as shown in the screenshot.
Note: With VIM baseline, only English language is supported. To configure

other languages, you must translate the objects into your languages.
8.7.4 Determining System by Company Code for Multiple

Backend Systems
If you do not maintain the system determination procedure in the channel
configuration, the system uses the baseline (OpenText) configuration which is:
System is determined based on the company code. Based on the company code,
DP documents are created in the satellite systems.
For the EDI scenario, you configure the system determination using Company Code
only in the central system.
For a description of the configuration, see section 3.7 “Maintaining the System
Determination” in OpenText Vendor Invoice Management for SAP Solutions - Scenario
Guide (VIM-CCS).
In the following screenshot, Company code 2000 is mapped to the Logical system
T90CLNT090.
VIM070500-03-CGD-EN-1
8.7.5 Testing an IDoc

You can test the whole process using the WE19 transaction, where you supply the
IDoc and the processing function module.
To test an IDoc:
1. To start the Test tool for IDoc processing, run the WE19 transaction.
You can perform the test in one of the following ways:
• Copying from an old IDoc (as described in this section).

• Creating a new IDoc with entirely new information.
2. Enter an Existing IDoc and click .
VIM070500-03-CGD-EN-1
3. Click the Inbound function module button in the application tool bar. The Test
inbound IDoc via a function module dialog box opens.
4. Enter the function module /OPT/DP_INBOUND_IDOC_PROC and click to

continue.
A new IDoc is created, by copying the existing IDoc.
5. To check the status of the created IDoc, run the WE02 transaction.
VIM070500-03-CGD-EN-1
6. Enter the IDoc number of the new IDoc into the IDoc number field and click .
The IDoc with status information is displayed. Successfully processed IDocs
have the status 53.
VIM070500-03-CGD-EN-1
To identify the DP document number from an IDoc:
1. To access the Data Browser: Initial Screen, run the SE16 transaction.
2. Enter Table name /OPT/VIM_1HEAD and press the RETURN key.
3. Enter the IDoc number in the EDI_DOCNUM field of the selection screen and
click in the application tool bar.
The DP document ID is displayed.

You can display the full information about the document using VIM Analytics.
You can also use the WE02 transaction to check the status of the IDocs. Enter the
date and the Basic Type to check how many IDocs have been received by the
systems and to check their status. See also Step 5 on page 127.
VIM070500-03-CGD-EN-1
8.7.6 Configuring Global Parameters

This section describes the global customization parameters that are available. Global
parameters control various aspects of the inbound EDI processing.
Important
Changes of the global configuration parameters as described in this section
may affect the functionality of the process.
8.7.6.1 EDI Image Exit Function Module

During the inbound EDI processing, it is possible to archive delivered IDOC
visualizations or to create and archive IDOC visualizations directly if required.
Therefore, maintain a suitable custom exit function module.
Note: If document type AR_OBJECT is provided as an input parameter, the

document class for the image is set to the corresponding value of AR_OBJECT. If
AR_OBJECT is not provided, the document class is derived from the mime type
of the images.
To maintain a custom exit function module:
1. Run transaction SM30 and enter table /PTGWFI/Z_CONST.
2. Enter /PTGWFI/Z_CONST in Table/view and click Maintain.
3. In the WebFlow Constant Table, under Product Code 005, double-click the
Constant EDI_IMAGES_FM.
The default value is <None>.

To get the necessary interface definition, you can copy the /
OPT/EDI_IMAGES_EXIT_TEMP template function module.
VIM070500-03-CGD-EN-1
Chapter 9
Document Processing Process Configuration
Document Processing (DP) in Vendor Invoice Management (VIM) is primarily used

to preprocess data before creating SAP business documents. The DP process can be
used as a filter to validate, eliminate potential errors and/or duplicates in the vendor
invoice documents.
Note: For details on country specific configuration, see “Characteristic Specific

Configuration“ on page 461.
Example 9-1: A possible DP process
1. A vendor invoice is scanned, OCR processed and sent to DP.

2. The indexer validates the data passed from OCR to determine the correct
document type, invoice information etc.
3. The indexer submits the document for further processing.
4. The system validates the data using pre-defined business rules, and if all
rules have been passed, creates an SAP document.
DP comprises the following main concepts:
Document types
• Highest level attribute, effect the processing, process flow and user interface.
A more detailed configuration according to the process and screen layouts is
done at the invoice characteristic level; see “Characteristic Specific
Configuration“ on page 461. Therefore it is not necessary to create many
different document types for individual process settings. Use a document
type as a global invoice processing template.
• Determine the SAP transaction to be called during document creation.
Note: The following specialty applies in the context of background

posting: In the MIRO transaction, it is possible to post an invoice directly
to G/L accounts without PO reference. In VIM, this is not possible for
PO documents. A PO reference is always needed for background
posting.
• Determine the metadata (index) collection screen layout and fields.
• Can be derived from OCR data using the document type determination rules
engine.
• Require no one-to-one relation to SAP ArchiveLink document types.
VIM070500-03-CGD-EN-1
Chapter 9 Document Processing Process Configuration
Process types
• Effect the process flow as required by swimlane definition.
• Each swimlane diagram refers to one process type.
• Are similar to parking or blocking reasons in VIM Invoice Exception.
• Can be used in multiple document types.
• Each document type needs at least one process type.
• Determine the initial actor and various collaboration options available to the
various actors during the process flow.
Business rules
• Represent a rudimentary engine for determining
• process type
• document type (in case of OCR or external data input)
• Use configuration to apply logical conditions.
• Allow defining of multiple criteria.
• Can be specified regarding order and exclusivity.
• Can be used for validating data from external systems (OCR).
• Can be automatically applied to the metadata to effect the process flow.
• Can be configured to be called at multiple stages in the process flow.
Roles
• Use the standard OpenText role/actor infrastructure.
• Can use the standard key determination infrastructure to configure complex
actor determination logic without programming.
Options and option types

• Comprise the following main types of options:
• Actions
Actions can be based on transactions or class method or workflow tasks.
• Referrals (for collaboration)
• Can effect the processing logic.
• Can effect the user experience.
• Can trigger the workflow engine to re-run the rules on the most current
metadata to effect the process flow.
• Can be configured to change the document status.
VIM070500-03-CGD-EN-1
BDC IDs
• Build a powerful infrastructure for pre-populating data into SAP

transactions without programming.
• Are optimized for both dialog processing and background processing.
• Allow to set dynamic parameter IDs.
• Can be used to configure new user collaboration actions.
• Eliminate the need to code parameterized transactions.
• Allow to configure BDC success messages.
Duplicate check infrastructure
• Builds a comprehensive infrastructure for configuring different duplicate

check logic.
• Allows specifying multi-step duplicate check logic.
Main steps Implementing process scenarios in the DP workflow component of VIM comprises
the following main steps:
1. Identify the list of DP document types that are needed.
2. Create and configure the association between DP document types and SAP
ArchiveLink process types.
3. Identify the various process types that are required for realization of the process
scenarios.
4. Identify and configure Indexing screen fields.
5. Identify the various roles and configure the roles in the appropriate process
types.
6. Identify and configure the process options according to the swimlanes.
7. Identify and configure the business rules to be executed to identify exception

processing.
8. Configure global customization setting as per customer requirements.
The starting point for any configuration is a set of process flow swimlanes.
Figure 9-1 shows an example for a process swimlane as implemented by the DP
workflow:
VIM070500-03-CGD-EN-1
Figure 9-1: DP process swimlane example
9.1 Configuring DP Document Types

The document type is the key object in the DP component of VIM. The document
type holds key information about how the document is created in the system (from
external data using OCR or manual entry etc.), Invoice Type etc. OpenText provides
standard document types for most scenarios in VIM. For further information about
DP document types, see Document types on page 131.
The DP document type configuration in VIM baseline comprises the following

document types:
NPO_75
for Non PO processing
PO_75
for PO processing
DWN_75
for Down Payment processing
The NPO_75 and PO_75 document types contain a huge amount of business rules,
which are relevant to process Non PO or PO invoices in different countries. Because
not every business rule must be executed in each country, a characteristic
VIM070500-03-CGD-EN-1
9.1. Configuring DP Document Types
customizing is provided, which, in the baseline, depends on the country. This can be
changed to each indexing field. You can determine a characteristic that must appear
in the index data.
The customizing allows specifying if a business rule should be executed for each
characteristic or executed only depending on the characteristic setting. For more
information, see “Characteristic Specific Configuration“ on page 461.
The baseline also contains only a few business rules which are mandatory for further
processing. The intention is to avoid dialog steps to increase efficiency.
With VIM 7.5 and above, baseline document types PO_75, NPO_75 and DWN_75
can be posted automatically. For more information, see “Configuring Automatic
Posting” on page 175.
The DWN_75 document type allows processing of Down Payments (both Non PO
related and PO related) based on a specific set of business rules. After processing the
defined business rules and running through the corresponding approval process (if
required), posting of Down Payment Requests using the F-47 transaction is possible
in dialog or background.
Note: The document types described in this section are the DP document types
in the baseline configuration of VIM.
Of course, you are free to create new DP document types, and, in upgrade
projects, to keep the DP document types that you are used to.
Configuring the DP document types comprises the following steps:

• “Creating a New DP Document Type” on page 136
• “Defining Process Types” on page 141
• “Defining the Process Type Determination Sequence” on page 143
• “Configuring Index Screen Options” on page 146
• “Configuring the Index Header” on page 149
• “Configuring the Index Item Fields” on page 151
• “Mapping ArchiveLink Document Types” on page 152
• “Changing the ArchiveLink Document Type When Changing the DP Document
Type” on page 153
• “Configuring Automatic Image Display” on page 154
• “Maintaining the PO Line Determination” on page 154
• “Maintaining Tax Code Determination” on page 160
• “Configuring Duplicate Check” on page 166
• “Determining PO Invoices by Vendor Table” on page 169
• “Configuring Auto Coding” on page 169
VIM070500-03-CGD-EN-1
• “Mapping for Coding Upload from Excel Sheet” on page 174
9.1.1 Creating a New DP Document Type

1. Run the /OPT/VIM_1CX1 transaction.
Alternatively, navigate to Vendor Invoice Management > Document
Processing Configuration > Document Type Configuration > Maintain
Document Types.
2. In the Document Type Definition Overview screen, double-click a DP

document type.
3. Define the DP document type, using the following parameters.

Basic Configuration group
Description
Enter the document type description.
Number Range
Enter the number range for the number range object. If a custom number
range object is not defined in global configuration, you can maintain the
VIM070500-03-CGD-EN-1
number range for object /OPT/DOCID in the Maintain Number Ranges step;
see “Configuring Global Parameters” on page 246.
Classifier
Select the classifier from the list. The classifier represents a further detailed
classification of special invoice types (for example Down Payments).
Document Index Type

Select the type of indexing to determine how the system determines the
origin of data. The following values are available:
Indexing using OCR

Use this option if the document is scanned and the OCR interface
passes the data to SAP ERP for creating an OpenText document.
Online Indexing
Use this option if archiving a document using the SAP ArchiveLink
Early Archiving process. Indexing is manual and the person responsible
maintains the data and submits for further processing.
In case of online indexing, the first process type that is determined will
be the default process type (see Default Process Type on page 139),
regardless of the list and the sequence of process types configured for
the document type.
No Indexing
Use this option if there is no indexing required and the document is
directly processed. Use this option if there is no scanned image and the
process is triggered using an API provided by OpenText.
Indexing using Idoc

This is not supported at the moment.
Invoice Type
Decide whether the document generates a Non PO Invoice or a PO Invoice.
Default Archive Doc. Type

The following logic applies:
ArchiveLink document type is set for external data

Document types will be checked for the ArchiveLink document type;
not only the field in the global customizing but also the new Archive
Link Mapping table; see “Mapping ArchiveLink Document Types”
on page 152.
• If a match is found, the document type is selected.

• If no match is found, the document type determination is executed.
ArchiveLink document type is not set for external data

The document type determination is executed.
If you have a 1:1 relation between the DP document type and an
ArchiveLink document type, select the ArchiveLink document type defined
VIM070500-03-CGD-EN-1
in the SAP ArchiveLink process, see “Creating an ICC Archive Document

Type” on page 29. If you do not have a fixed relation, you can leave the field
empty or you can use a dummy archive document type which is used for all
DP document types without fixed relationship. The current baseline is
delivered with dummy document type /OPT/ICC.
For further details, see “Document Type Determination Rules Engine”
on page 505.
SAP FI DocType
To determine the SAP document type, enter a fixed document type or a
custom function module.
If you use a function module, enter FM:<Function Module Name>. As the
interface for the function module, use the template /
OPT/BL_IF_DETERMINE_SAP_DTYPE.
You must configure separate FI document types for invoices and credit
memos at the DP document type level. Fill the SAP FI DocType field with
two separate FI document types, separated by comma.
Example: If the value in the field is AA,BB, the system will set the FI document type
AA for invoice and BB for credit memos.
You can still configure a custom function module to determine the FI

document type.
New Indexing Screen
In VIM 7.5 SP1 and higher, configuring the old indexing screen (by selecting
No) is no longer supported.
Tab <X> Program
The indexing screen allows you to configure 5 tabs.
OpenText provides subscreens for managing index data both at header
level and item level. If the layout or information on the subscreen is
inadequate to the business process, you can define your own screens.
For the indexing screen, each tabstrip can be redefined with an own
subscreen and program.
Tab 6 (custom tab) allows you to configure a custom program and
screen. You can use the custom tab for additional fields that are
necessary in your project implementation.
In baseline delivery, the custom program and screen are not configured.
When the Tab 6 Program and Tab 6 Screen Number fields are
configured, a new tab is shown on the indexing screen.
Tab <X> Screen Number
Enter the Screen Number for the respective Tab <X>.
For the custom tab 6, VIM delivers an example screen 1900 in
program /OPT/SAPLVIM_IDX_UI. Screen 1900 provides the following
sample fields:
• ATTRIBUTE1
VIM070500-03-CGD-EN-1
• ATTRIBUTE2
• ATTRIBUTE3
• ATTRIBUTE4
• CUSTOM_FIELD4
• CUSTOM_FIELD5
• CUSTOM_FIELD6
• CUSTOM_FIELD7
• CUSTOM_FIELD8
• CUSTOM_FIELD9
• CUSTOM_FIELD0
Application Sync FM, Label Sync FM

If you want to have a customer specific indexing screen, you must configure
these two function modules.
Maintain and create two sync function modules, one for the application
itself and one for labels. To create the function modules, copy /
OPT/C_IDX_SYNC_APPLICATION and /OPT/C_IDX_SYNC_LABELS.
These two functions must also be available in the function group where you
have your new screens.
Country
In VIM 7.5 SP1 and higher, this field is technically not used.
You can use this field to switch between new (VIM 7.0 and higher) and old
document types. The new document types no longer base on countries. So,
they do not require this field. The old document types need this field filled
to be able to map against the country specific settings, which are renamed to
characteristic specific settings with VIM 7.0 and higher. All the new coding
checks this switch to process the old or new logic.
Process Configuration
Document Posting Configuration group
Default Process Type

Select the process type the system uses if the initial business rule check fails
to result in a valid process type.
Usage - This process type is used if no other process type is determined.
If you use online indexing, it will also be the first process type determined,
regardless of the process types and sequence configured for the document
type.
Example: If a document has no errors and should directly be created in SAP ERP,
you select a default process type for creating the document.
VIM070500-03-CGD-EN-1
Rescan Data group
Rescan Role
Select the role that receives the work item if the document data is not legible
or if the user decides to send the document for rescanning.
Note: A valid role must be already defined, see “Defining Roles”

on page 44.
Dialog Posting Step Options group
Posting Role
Select the role that is responsible for posting the document finally. If the
posting of the document fails in background, this role gets the work item to
post the document in dialog.
Note: A valid role must be already defined, see “Defining Roles”

on page 44.
Display Index Data

Select this check box to display the index document in a separate session
while document posting so the user is able to reference back the index data.
Note: At least one session must be available for display.
Skip Dashboard
Select this check box to skip the dashboard step. The system creates the SAP
document directly during the document posting process for the posting
user.
Example: If the document is all okay, the user might want to post it directly,
without displaying the document data.
Display Image
Select this check box to display the archived image linked to the document
in a separate session when the user processes the work item.
Note: Archiving must be active in the system.
Duplicate Check Data group
Duplicate Check Grp

Select the duplicate check group defined.
Duplicate Check Role
Select the role that gets the work item if the duplicate check fails and system
identifies the document as a potential duplicate.
Tax Configuration - For a description of the fields in the Tax Configuration

group, see “Tax calculation Group” on page 160, “Maintaining Tax Code
Determination” on page 160.
VIM070500-03-CGD-EN-1
Line Item Configuration

Line Processing
Line item data

Select the check box if line item data is used that needs to be managed for
the document (for example PO lines).
Ignore Items from Ext System

Select the check box to achieve that no line items are taken into account.
This means line items are not mapped and not transferred to VIM. You can
use this, for example, for NPO invoices where line items are not relevant.
PO Line Automation - See “Maintaining the PO Line Determination”

on page 154.
9.1.2 Defining Process Types

In this step, you define the valid process types for document types and the BDC Id
for each process type. For further information about process types, see Process types
on page 132.
To define process types:

Document Types.
2. In the Document Type Definition Overview screen, select a document type

and double-click Document Processes.
3. In the Document Processes Overview screen, select a process type and click the
button in the application bar.
VIM070500-03-CGD-EN-1
4. In the Document Processes Details screen, define the process type, using the
following parameters.
Process Type
Select the process type that is valid for the document type.
Active check box

Select this check box to achieve that the process type is considered for the
document type, for example if you want to delimit a specific process type
delivered by OpenText or defined in the system but no longer used.
BDC Transaction Id
Select the BDC Id that the system uses to process an SAP transaction to
create an SAP document in user context.
Background Tran Id
Select the BDC Id that the system uses to process an SAP transaction to
create an SAP document in the background. This is relevant if the user does
not want to see the index data (dashboard) during document posting.
Autopost Flag
The following settings are possible:
• Enter X to let the system try to create an SAP document in the

background, using the BDC Id set in the Background Tran Id field. If
the posting fails, the role defined in the Posting Role field in the
document type definition receives a work item to post the SAP
document in dialog.
• Enter a custom function module that can be used to determine if the
system should automatically post the document. You must enter the
function module as FM:<Function Name>. The interface for the function
module can be found from template /OPT/BL_IF_DETERMINE_AUTOPOST.
• To use the extended determination logic for automatic posting, which is
introduced with VIM 7.5, enter FM:/OPT/VIM_DETERMINE_AUTOPOST. See
also “Configuring Automatic Posting” on page 175.
ParkReason
Enter the parking reason the system uses to park the document.
Prerequisites
• The BDC Id defined for Document Create is used for parking the
document.
• A valid parking reason is defined in the Maintain Parking Reasons step
for Non PO or PO documents; see “Configuring Parking Reasons”
on page 272 and “Configuring Parking Reasons (Non PO Parking
Process)” on page 315.
Example: If the process type determined is to park a PO invoice for missing or

invalid information, create a parking reason and enter that parking reason here.
VIM070500-03-CGD-EN-1
9.1.3 Defining the Process Type Determination Sequence

In this step, you define how the system determines a process type for a given
document type. The system validates each step defined here, and if the step fails, the
process type defined against that step is determined. These process type
determination rules are also referred to as business rules. These steps serve the
purpose of parsing the invoice metadata and of determining any business rules that
are violated.
To define the process type determination sequence:

Document Types.
and double-click Proc. Type. Det. Sequence.
3. Define the process type determination sequence, using the following

parameters:
Step Id
Define a step Id.
Process Type
Define the process type for the step Id.
Exclusive Indicator
Select this check box if the system should stop checking for next process
type even though the current step resolves a process type.
VIM070500-03-CGD-EN-1
Exclude from Simulate

Select this check box to exclude the business rule from simulation.
Bypass possible
Select this check box to enable the Bypass icon on the Bypass/Simulate
Business Rules screen for the user.
Run in Central
This column appears in satellite systems, only.
Select this check box for any business rule to have it run in the central
system by an RFC call from the satellite system. Some business rules are
centralized. Satellite systems can use such centralized rules by this option.
Example: If a PO number is missing or invalid, the system should determine process

type 101 (Invalid PO number).
In the document processes, you can configure the initial role that gets the work item to
resolve the exception (defined in the definition of the process type).
9.1.3.1 Defining Sequence Steps

In this step you define, for a given step Id, the fields that need to be considered for
validating data. This means you specify the fields that will be checked in the
business rule. You can also enter a function module. Then no field is specified but a
step, which will be executed for this business rule.
To define sequence steps:
1. In the Proc. Type. Det. Sequence Overview screen, select a step and double-
click Sequence Steps.
2. Define the sequence steps, using the following parameters:
Step Seq.
Enter a numeric value identifying the step sequence.
Field name
Select the field name in document data that is considered for validation.
Check Type
Select the type of check to be performed:
VIM070500-03-CGD-EN-1
• If Table Field is selected, the system validates that the value of the
document field at runtime exists in the check table mentioned in the
Table field. If the value does not exist, the step is considered to be
successful and the system will determine the process type.
You have to maintain the Table field.
• If Check Function is selected, you can define your own check against
the document field. If the function raises an exception the step is
considered to be successful and the system will determine the process
type.
You have to maintain the Check Function field.
• If Constant Value is selected, you can define a constant value against
which the runtime data of the document is compared. If the runtime
value matches the configured value, the step is considered to be
You have to maintain the value of the constant in the Check Val field.
• If Required Field is selected and if there is blank data in the document
field, it is considered as meeting the criteria. The step is considered to be
You have to maintain the Required Field field.
Note: The business rule check function library offers additional check
function modules that are not directly delivered as pre-customized
business rules. You can use the function modules as new business rules
depending on your needs. The new library is located in function group /
OPT/VIM_PROC_TYPE_LIBRARY, which has been created to collect such
function modules.
If you want to activate one of the library function modules as a new
business rule for any VIM document type, perform the following
customizing steps:
a. To create a new process type depending on your specific needs, run

the /n/OPT/VIM_8CX1 transaction. Assign suitable process options and
an initial actor to the new process type.
b. To integrate the newly created process type within the VIM document
type maintenance, run the /n/OPT/VIM_1CX1 transaction.
VIM070500-03-CGD-EN-1
9.1.4 Configuring Index Screen Options

In this step you define what the index screen looks like for each role in the DP
process. This means which buttons are visible and which are not.
To configure index screen options for document types:

Document Types.

and double-click Index Screen Options.
3. In the Index Screen Options Overview screen, click the New entries button in
the application tool bar to create a new index screen option.
4. Configure index screen options, using the following parameters:
Process Type
Select a valid process type, as defined in “Defining Process Types”
on page 141.
Description
Description of the selected process type
Current role
Role which processes the work item
Allow Changes
Select this check box for a given role to allow all users in the role defined to
change the index data.
Prerequisite - The document should not have been submitted, yet.
VIM070500-03-CGD-EN-1
Example: If INDEXER and AP_PROCESSOR roles should be able to change index

data, select the Allow changes check box in the Index Screen Options screen for
INDEXER and AP_PROCESSOR roles.
Show Duplicates
Select this check box to achieve that the duplicates identified by the system
are displayed below the index data screen for the role that is processing the
work item.
Example: It might be relevant for the DUP_CHECKER role to look at the duplicates to
decide whether the document is actually a duplicate. For the AP_PROCESSOR role,
showing duplicates might not be that important as the document might have
already completed the duplicate check process and might be ready to be posted or
parked.
Initial Tab
With the indexing screen delivered with VIM 7.0 and higher, you can
configure each tabstrip of the indexing screen for the tab that is shown
initially:
Basic Data
Shows the basic indexing information which is also available on the
invoice document
Line Item Data

Shows the relevant line items
Accounting Data
Shows additional SAP specific data for the accountant to post the
document
Tax Data
Shows relevant tax information
Process Data
Shows relevant process information and also provides access to the
duplicated invoices
Simulate and Bypass
Note: These parameters act as an enhancement to the DP Dashboard.

See also section 4.1.2 “Application Toolbar” in OpenText Vendor Invoice
Enable Simulate
Select this check box to simulate skipping certain business rules. The
Simulate process will check the relevant business rules.
Example: If any DP document got an exception Invalid Vendor (PO), you

can simulate this by selecting the current role and selecting Enable Simulate.
Enable Bypass
Select this check box to bypass the business rules.
VIM070500-03-CGD-EN-1
Example: If any DP document got an exception Invalid Vendor (PO), you

can bypass this by selecting the current role and selecting Enable Simulate and
Enable Bypass.
Dis.Obsolete
Select this check box to hide the Obsolete button in the DP Dashboard for
the selected DP document type and the current role.
Dis.Rescan
Select this check box to hide the Rescan button in the DP Dashboard for the
selected DP document type and the current role.
Show Match
Select this check box to display the matching area within the item data
subscreen for PO invoices to the user. This is relevant to execute the
matching for PO related documents based on the SAP proposal.
Disable GL Tab
Select this check box to hide the GL tab on the index screen for the selected
PO document type and the current role.
Code Check Enable
You can configure the check box in the following places:
Document type configuration
/OPT/SPRO > Document Processing Configuration > Document Type
Configuration > Maintain Document Types, option: Index Screen
Options (described in this section)
Configuration in Characteristic
Configuration > Characteristic Specific Document Type
Configuration, option: Characteristic Specific Screen Configuration
(see “Characteristic Specific Screen Configuration” on page 479)
Select the check box for a certain process type and a certain role to show the
Validate Coding button in the DP Dashboard, Line Items tab, G/L Account
tab of the given role and the given process type. This button enables the
agent to validate the coding entered in the indexing screen.
Notes
• To use the Validate Coding button, you must select the Code Check
Enable check box in both places (document type configuration and
configuration in Characteristic) if the Characteristic Check check
box of the process type is selected (see “Defining the Process Type”
on page 225). In baseline, this check box is cleared.
The configuration in Characteristic will overwrite the document
type configuration.
• Coding validation is available for Non PO based DP documents.
Enable Code Upload

You can configure the check box in the following places:
VIM070500-03-CGD-EN-1
Document type configuration

Configuration > Maintain Document Types, option: Index Screen
Options (described in this section)
Configuration in Characteristic
Configuration > Characteristic Specific Document Type
Configuration, option: Characteristic Specific Screen Configuration
(see “Characteristic Specific Screen Configuration” on page 479)
Select the check box for a certain process type and a certain role to show the
Upload Coding button in the DP Dashboard, Line Items tab, G/L Account
tab of the given role and the given process type. This button enables the
agent to upload coding from an Excel sheet.
Notes
• To use the Upload Coding button, you must select the Enable Code
Upload check box in both places (document type configuration and
configuration in Characteristic) if the Characteristic Check check
box of the process type is selected (see “Defining the Process Type”
on page 225). In baseline, this check box is cleared.
The configuration in Characteristic will overwrite the document
type configuration.
• Upload coding is available for Non PO based DP documents.
9.1.5 Configuring the Index Header

You can specify the header fields on the index screen for each document type.
Possible values are Display Only, Hide, Required, and Input.
To configure the index header:

Document Types.
2. In the Document Type Definition Overview screen, select a DP document type

and double-click Index Header Configuration.
VIM070500-03-CGD-EN-1
3. Configure the index header fields, using the following parameters:

Field Stat
Required
Make the field mandatory at runtime.
Input
Define the field as an input field for users.
Display Only
Only display the field.
Hide
Hide the field on the screen.
Note: The attributes Input, Display Only, and Hide are independent
from the processing state. Unlike those, the attribute Required works as
follows: If the processing state is Missing mandatory information, the
field is required and the field will show the Input Required icon. In all
other processing states, the field is a normal input field. Thus, the field
input can be skipped in the early processing steps.
There are some special fields that are not in the database but can be displayed in the
index screen. To use them, you must configure the Field Stat column for the
following parameters:
VORGANG
To display Subsequent Debit and Subsequent Credit for PO in the index
screen, under Invoice Data, Transaction field, set the parameter VORGANG to
Input.
DIFFERENZ
To display the Balance traffic light in the index screen, under Invoice Data, set
the parameter DIFFERENZ to Display Only.
VIM070500-03-CGD-EN-1
DN_LIST, PO_LIST, SES_LIST

To display the DN List, PO List, and SES List buttons in the index screen, under
Invoice Data, set the parameters DN_LIST, PO_LIST, and SES_LIST to Input.
9.1.6 Configuring the Index Item Fields

You can specify the item fields on the index screen for each document type. Possible
values are Display Only, Hide, Required, and Input.
To configure index item fields:
1. Navigate to Vendor Invoice Management > Document Processing

Configuration > Document Type Configuration > Maintain Document Types.

and double-click Index Item Configuration.
3. In the Index Item Configuration Overview screen, configure the index item
fields, using the following parameters:
Field Stat
Every line represents one line item field of the selected DP document type,
indicated by the Field Name.
Required
Make the field mandatory at runtime.
Input
Define the field as an input field for users.
Display Only
Only display the field.
Hide
Hide the field on the screen.
Note: The attributes Input, Display Only, and Hide are independent
from the processing state. Unlike those, the attribute Required works as
follows: If the processing state is Missing mandatory information, the
field is required and the field will show the Input Required icon. In all
other processing states, the field is a normal input field. Thus, the field
input can be skipped in the early processing steps.
VIM070500-03-CGD-EN-1
9.1.7 Mapping ArchiveLink Document Types

You may want to configure more than one ArchiveLink document type for one DP
document type, for example to support more than one mime type. The ArchiveLink
Mapping enables you to perform this configuration.
To map ArchiveLink document types to a DP document type:

Configuration > Document Type Configuration > Maintain Document Types.

and double-click ArchiveLink Mapping.
3. In the ArchiveLink Mapping Overview screen, configure the mapping, using

the following parameters:
Country
Enter a country code to which the ArchiveLink document type is associated.
Doc. Type
Enter an ArchiveLink document type to map it to the selected DP document
type.
Description
Enter a description of the ArchiveLink document type.
You can define country specific archive document types in the document type
configuration. You can also define an archive document type that is not country
specific. This means, it is used for the rest of the countries. If you have only one
archive document type that is not country specific, you can use the default archive
document type in the document type configuration. If you have more of these
document types, leave the default archive document type empty and make archive
document type entries with empty value in the Country column.
Note: Do not use the asterisk as value.
Prerequisites
• The Country field in the DP document type determination must be empty.
• Make sure that the Z constant (product code 005) AR_OBJECT_FROM_DP is set to X.
If this Z constant is set to an empty value or is missing, VIM will not check and
adjust the archive document type when the DP workflow is started (see below).
• Copy between logical archives (see below) is done with SAP CMS function
module SCMS_AO_COPY. Make a test if copy works, you might need changes in
the definition of the logical archives (transfer directory).
The DP document type, the company code, or the Country field might be changed
during DP processing. In this case, VIM checks if the archive document type has to
VIM070500-03-CGD-EN-1
be adjusted, and if so, performs the adjustment. If the new archive document type is
linked to a different logical archive, the images are copied between the archives.
The application log shows messages for object /OPT/VIM, subobject DP, and
document number as external ID. Messages are of the following types:
Information
if there was a copy to a new archive
Warning
if there is no image linked
Error
if there was an exception in one of the called function modules
You can have country specific document types and you can maintain the relation in
the ArchiveLink mapping table. Whenever a company or a country is changed in the
indexing screen, the relation is checked and, if necessary, the archive document type
is adjusted. There are two user exits to change this, controlled by two Z constants:
• AR_OBJECT_DETRM_FM (product code 005)
• AR_OBJECT_TRIG_FM (product code 005)
You can define the logic to determine the archive document type and you can define
the logic when a redetermination should be triggered.
9.1.8 Changing the ArchiveLink Document Type When

Changing the DP Document Type
This references the process option Change Document Type.
If you change the DP document type, attachments are moved from their original
ArchiveLink document type to the ArchiveLink document type of the new DP
document type.
To enable custom solutions for attachments, VIM 7.5 SP3 introduces the /
OPT/ES_VIM_R1AX1 enhancement spot in the /OPT/VIM_R1AX1 program. When
changing the DP document type, this enhancement spot allows implementing a
custom logic to reassign ArchiveLink document types of documents and
attachments to other logical archives.
VIM070500-03-CGD-EN-1
9.1.9 Configuring Automatic Image Display

You can configure that the invoice document linked to the process (not any further
ArchiveLink attachments) is automatically displayed when the DP Dashboard is
opened.
The DP Dashboard provides the possibility to show the image in the Detail pane.
The configuration described in this section is only relevant if you want to deactivate
the image plug-in, or to display the image in a separate window.
To configure automatic image display in a separate window:
1. Run the SM30 transaction.
3. In the WebFlow Constant Table, under Product Code 005, double-click the
Constant DASHBOARD_IMAGE_AUTO.
4. Enter Constant Value X and save.
9.1.10 Maintaining the PO Line Determination

When processing PO based invoices, it is necessary to supply line item data to be
used in invoice posting. This data can be entered manually or received from ICC,
IDoc, or other external sources. In both cases, line item information may be
incomplete. Often, when there is a 1:1 relation between the PO or GR and the
invoice, the line item data can be completely derived from the existing PO lines.
With version 7.5 and higher, VIM provides some options in the logic module
processing to match and derive data even if no 1:1 relation is available.
VIM offers the following functionality:

• Deriving the line item data from the PO(s) and GR(s)
• Matching the PO and GR data against the data provided manually or from
external sources, and, based on the PO and GR data, completing the data in the
line item fields where it is missing.
This section describes the configuration of this functionality.
With VIM 7.5 and higher, the determination of line item data is implemented in logic
module /OPT/CL_D_LM_DETERM_PO_MAP, which is included in logic module
processing Line based processing / enrichment / matching (PO).
Old In VIM versions prior to 7.5, the following DP business rules were used to process
the PO matching and exception handling:
• Manual Check Needed for Indexing Lines (PO), DP process type 110
• Unable to Determine PO Line Number (PO), DP process type 109
VIM070500-03-CGD-EN-1
New These two business rules are replaced by the combination of a logic module and a
business rule:
• Logic module processing: Line based processing / enrichment / matching

(PO)
• Business rule: Manual Check Needed / Missing Data for Indexing Lines (PO),
DP process type 113
Note: In this section, the “OCR” term, which is used to denote the source of the
data, applies equally to the data entered manually or received from external
sources like IDoc.
To maintain the PO line determination:

Management > Document Processing Configuration > General Configuration
> Automated Line Processing > PO Line Determination > Maintain PO Line
Determination Procedures.
2. In the PO Line Determination ID Details screen, enter the following details:
PO Line Det. ID
The ID must be numeric.
You must assign the PO Line Determination ID to the DP document type;
see Step 8 on page 158.
Description
Enter an appropriate description.
Check Function
Optionally, use a custom function module here to determine the PO line
number. By default, the field is blank. An OpenText standard function
module is used.
VIM070500-03-CGD-EN-1
No of Fields to Match (shown if Match All Fields is cleared)

Specify how many fields should be matched before claiming the PO line
number found. The number of fields you specify here should be less than or
equal to the number of fields you maintain for this Determination ID.
Match All Fields
Select this check box to use all fields maintained in the PO line
determination fields for the Determination ID to find a PO line match.
Match Conditional (used in logic module Line based processing /
enrichment / matching (PO))
Select this check box to configure a condition in the fields configuration
between each field within one field group. See Relation on page 157.
Match against Proposal (used in logic module Line based processing /
Select this check box to match not only against PO information but also
against the MIRO proposal. If a unique match is found, also relevant key
fields (GR or SES) are retrieved.
Match within MIRO Tolerance (used in logic module Line based
processing / enrichment / matching (PO))
Select this check box to achieve that matching is also possible within the
tolerances configured in MIRO.
Exclude Invoiced Lines
Select this check box to exclude the lines in the PO that have been marked
as Final Invoice when trying to find the PO line match. This narrows
down the search for the PO line determination.
3. Double-click PO line Determination Fields in the Dialog structure.
The new matching process is used in logic module Line based processing /
enrichment / matching (PO)). To find the PO line number, the matching
VIM070500-03-CGD-EN-1
process first tries to match all fields within step ID 1 (MENGE / NETPR / WRBTR) for
each index line against the PO and the GR. If no unique match is found, step ID
2 is processed. Now, the process takes also the field MAKTX into account. If again
no unique match is found, the process takes step ID 3 with field LFSNR into
account. So it is possible to define various steps with different detail levels to
find a unique match.
4. Maintain the fields you want to use for the PO line determination. Baseline
configuration uses the following fields for the matching:
Step ID
Define the sequence for the matching. The step ID is also the grouping
indicator for the fields to find a unique match.
Field Name
Enter the field used for matching.
Field Step ID (used in logic module Line based processing / enrichment /

matching (PO))
Define the sequence of processing fields within one step ID.
Field Matching Exit (used in logic module Line based processing /

Process your own matching logic. Also in the field matching exit, the
complete line information delivered by OCR is provided to process
individual matching logic.
• Baseline:
/OPT/VIM_DBPF_MATCH_QUANTITY to convert quantity fields from
invoice unit into PO unit
• Baseline:
/OPT/VIM_DBPF_MATCH_TEXT to normalize the invoice material text to
match it against PO material text
Relation
Optional: Enter AND or OR.
The relation is taken into account if conditional matching is enabled. The
relation is used within one step ID.
• If conditional matching is disabled, all fields must match.

• If conditional matching is enabled, an initial condition is used like an OR
condition.
6. Continue with DP Document Type configuration: Run the /n/OPT/SPRO

transaction and navigate to Vendor Invoice Management > Document
Processing > Document Type Configuration > Maintain Document Types.
7. Double-click a line to open the Document Type Definition Details screen.
VIM070500-03-CGD-EN-1
8. Maintain the Determination Logic ID (PO Line Determination ID) you have
just configured.
9. Select the PO Line Determination Setting:
OK (default value)
Use OCR lines as basis without deletion of incomplete lines.
OCR lines are evaluated line by line. All lines based on reference documents
are read from the MIRO proposal. All OCR lines for which matches are
found in the MIRO proposal are overwritten with MIRO Amount/Quantity if
the OCR Amount/Quantity is missing.
• While matching, PO/PO item will be used as a key for Non GR IV case.
• PO/PO item or delivery note will be used as a key for GR IV case.
All lines that could not be matched with MIRO lines stay as they are. Finally,
the modified OCR lines are updated in the indexing item table.
OD
Use OCR lines as basis with deletion of incomplete lines.
OCR lines are evaluated line by line. All lines that are based on reference
documents are read from the MIRO proposal. All OCR lines for which
matches are found in the MIRO proposal are overwritten with MIRO Amount/
Quantity if the OCR Amount/Quantity is missing.
All lines that could not be matched against MIRO lines and that are
incomplete are deleted. Finally, the modified OCR lines are updated in the
indexing item table.
MO
Use MIRO proposal as basis for indexing lines.
All lines that are based on reference documents are read from the MIRO
proposal. All MIRO lines for which matches are found in OCR line items are
overwritten with OCR Amount/Quantity.
VIM070500-03-CGD-EN-1
All lines that could not be matched against OCR lines stay unchanged.
Finally, the modified MIRO lines are updated in the indexing item table.
M2
Use MIRO proposal as basis, change only open lines.
This option has the same logic as MO but it prevents the data in non-open
lines of the MIRO proposal from being overwritten.
Background: Option MO results in overwriting the MIRO proposal lines that
are not open anymore because the data has been manually entered in the
DP document or received from ICC. Although this logic may be wanted in
some situations, VIM is now offering the alternative option M2.
PO (Default for PO Automation)

Use MIRO proposal with no dialog action.
Use only MIRO proposal as indexing lines.
This option is created for an automated scenario. For specific data on
invoices which has to be set up in the document type determination, usually
no dialog steps are expected.
Therefore all lines are read from the MIRO proposal and are moved to the
indexing lines. Existing lines are removed. There is no matching and also
quantity and amount is taken from MIRO proposal.
The business rule only fails if amount or quantity is zero.
10. Select the Level Preference:

Configure if users choose PO/delivery note either at header level (H), or line
level (L), or both levels (B).
11. Select the Ref Doc Preference:

Configure if users choose either purchase order (PO) or delivery note (DN) as
their base for proposal.
12. Save your settings to finish the process.
Important
Level Preference is used in conjunction with Ref Doc Preference. These two
values indicate the starting point for selecting reference documents, in order
to propose lines for invoicing: either purchase orders or delivery notes that
appear either at line item level or at header level.
Example: If Level Preference is L and Ref Doc Preference is PO, the system uses
purchase orders at line item level as the basis for getting proposals.
If no purchase order exists at line item level, the system uses delivery notes at line
item level.
If no documents exist at line level, the system uses the header level and starts with
purchase orders, there.
If no purchase order is supplied, the system uses delivery notes at header level.
VIM070500-03-CGD-EN-1
Note: If the PO line determination doesn’t find the PO line item number while
running the Business Rules, you will get an exception Unable to determine PO
line no (PO). You will also get this exception if the PO line item number is
blank or if it is invalid.
9.1.11 Maintaining Tax Code Determination

When data flows to VIM from external systems like an OCR system, the tax code
may not be supplied. However, for auto tax calculation, the tax code is important.
Therefore, VIM provides a tax code determination rule that tries to determine the tax
code corresponding to the supplied tax rate.
The tax code determination works whenever there is a supplied tax rate. See “Tax
calculation Group” on page 160 for details.
To maintain tax code determination:

Management > Document Processing Configuration > Document Type
Configuration > Maintain Document Types.
2. Double-click a line to open the Document Type Definition Details screen.
In the Tax Code Determination group, the following options are available:
• “SAP Tax Determination Logic with OT Tax Table (Simple Maintenance)”

on page 163
• “Tax Determination using OpenText Tax Table (Simple Maintenance)”
on page 164
• “SAP Tax Determination Logic” on page 165
• “Customer Tax Determination” on page 165
Note: Select the Tax Code from Vendor Master check box to retrieve the
tax code from Vendor Master in case any of the other options fails to
retrieve the tax code.
Tax calculation Group

In the Tax calculation group of the Document Type Definition Details screen (see
screenshot above), you define the tax calculation options for the DP document type.
The following options are available:
VIM070500-03-CGD-EN-1
Auto Calculate Tax

Select this check box if you want the system to calculate the tax based on the tax
code either supplied explicitly during the indexing stage or determined by the
system from the supplied tax rate.
Allow Zero Tax Rate

Select this check box if you want the system to determine the tax code for a 0.00
tax rate (zero tax rate). If blank or empty is supplied, the system cannot
determine the tax code, so the value should be 0.00 or greater.
Allow without Tax

Select this check box for scenarios without input tax, that means, nothing is
supplied from tax perspective and you still want the system to carry it forward.
Note: This option only works if Auto Calculate Tax is not selected.
Calculate Tax on Net

For Non PO DP Approval, use this check box if you want the system to
differentiate between gross and net. The check box is document type specific
instead of user specific, because approval might be accomplished by several
different users.
As a prerequisite, you must configure the global constant CALC_TAX_ON_NET. See
“Configuring Tax Calculation on Net Amount” on page 367 for details.
If the global constant CALC_TAX_ON_NET is set to D, you can define Calculate Tax
on Net document type specific in the Document Type Definition Details
screen:
• Select the Calculate Tax on Net check box to define that G/L account
amounts are to be entered net.
• Clear the Calculate Tax on Net check box to define that G/L account
amounts are to be entered gross.
SAP ERP has two different tax flags that control the line amount and balance on
the Non PO parking screen and VIM Non PO parked approval:
• auto_calc tax flag that is document specific.
• calculate-tax-on-net-amount flag that is user specific.
In the past, VIM had only the auto-calc tax flag for Non PO DP approval. The
calculate-on-net-amount tax flag, known from Non PO processing, was not
available for DP documents. VIM interpreted the missing second flag as being
empty. If the auto-calc flag was selected, the gross amount was expected in the
Non PO DP line items.
The following combinations are possible with the two tax flags:
VIM070500-03-CGD-EN-1
Test Document Flag User Flag Item

Case auto_calc calculate-tax-on-net- Amount
(BKPF-XMWST) amount
(BKPF-XSNET)
1 X Gross
2 Net
3 X X Net
4 X Net
If auto_calc is selected and calculate-tax-on-net-amount is not selected (Gross),

the line items have to be filled with gross amount.
All other combinations require net amounts in the line items in order to have a
correct balance.
Test Case 1
If auto_calc is selected, and calculate-tax-on-net-amount is not selected
(Gross Amount, tax included):
Balance = Header Gross amount - (sum of all line item amounts)
Test Cases 2 and 4

If auto_calc is not selected (Net Amount):
Balance = Header Gross amount - (tax amount in header + sum of all line
item amounts)
Test Case 3
If auto_calc is selected and calculate-tax-on-net-amount is selected (Net
Amount, no header tax available):
Balance = Header Gross amount - (calculated tax + sum of all line item
amounts)
CALCULATED TAX = sum all (line item amount * tax rate on the line)
Tax Jurisdiction Code Determination

Tax procedures that have tax jurisdiction codes need to determine tax jurisdiction
first. The system checks the following to determine the jurisdiction code:
1. If a PO line exists, the system tries to retrieve the jurisdiction code from the PO
line item.
2. If the PO line item does not contain a jurisdiction code, the system checks for a
jurisdiction code based on the plant for the PO line item.
3. If still no jurisdiction code is found or if the invoice is a Non PO invoice, the
system picks up the jurisdiction code from the vendor master.
Note: If no jurisdiction code is found for tax procedures with jurisdiction code,
the tax code determination fails.
VIM070500-03-CGD-EN-1
Possible Reasons for Tax Code Determination Failures

If the tax code determination fails, consider the following possible reasons:
• The PO line item tax code does not match the tax rate supplied.
• There are multiple tax codes belonging to the same tax rate supplied.
• A tax rate may match with one tax code but the tax code contains multiple rates.
• The tax jurisdiction code has not been determined, in case a tax procedure with
jurisdiction code is used.
For example, the United States have the TAXUSJ tax procedure with jurisdiction
code.
If the tax code determination fails, an Invalid Tax Info exception is raised in the
VIM Analytics report. In this case, the workflow is routed to the Tax Expert for
further actions.
9.1.11.1 SAP Tax Determination Logic with OT Tax Table (Simple

Maintenance)
This option uses the following logic:
1. The system reads the tax code from the PO line and checks if the tax rate
supplied by the external system matches uniquely. If the tax code exists in the
PO line item and no match is found, the tax code is considered to not determine
and the system stops checking further.
2. If the tax code does not exist in the PO line or the invoice is not a PO invoice, the
system proceeds as follows:
a. The system checks all tax codes of input tax type for the country and checks
if the tax rate supplied matches uniquely with only one tax code. If no match
is found, the system proceeds further.
b. The system selects the tax code from the OpenText table based on the tax
rate (Simple Maintenance). See “Tax Determination using OpenText Tax
Table (Simple Maintenance)” on page 164.
c. If the above step does not result in a tax code match, the system retrieves the
tax code from Vendor Master if the Tax Code from Vendor Master check
box is selected in the DP configuration. The system checks if the vendor tax
code contains only one tax rate and if that tax rate matches with the tax rate
supplied. If it matches, the tax code is determined.
Note: If the tax procedure with tax jurisdiction is used, the jurisdiction code is
determined first and this code is used in conjunction with tax code to retrieve
the match. For details on the jurisdiction code determination, see “Tax
Jurisdiction Code Determination” on page 162.
VIM070500-03-CGD-EN-1
9.1.11.2 Tax Determination using OpenText Tax Table (Simple

Maintenance)
a. The system selects the tax code from the OpenText tax table based on the tax
rate (Simple Maintenance).
To maintain the Tax Code Determination Configuration:
1. To maintain the table /OPT/VIM_TAX_CFG, run the /

OPT/VIM_BL_TAX_CFG transaction.
2. For a given Country key and Vendor ranges, maintain Tax Rate versus
Tax Code.
For tax procedures with jurisdiction code, additionally use the
Jurisdiction code field to maintain Tax Rate versus Tax Code entries.
b. If the above step does not result in a tax code match, the system retrieves the
VIM070500-03-CGD-EN-1
9.1.11.3 SAP Tax Determination Logic

a. The system checks all tax codes of input tax type for the country and checks
if the tax rate supplied matches uniquely with only one tax code. If no match
is found, the system proceeds further.
b. If the above step does not result in a tax code match, the system retrieves the
9.1.11.4 Customer Tax Determination

You can use a Custom Function Module to determine the tax code. The function
module must be compatible with the interface of the function module /
OPT/VIM_TAX_CODE_DETERMINE:
*"--------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" REFERENCE(LOCATION) TYPE CHAR1 OPTIONAL
*" TABLES
*" INDEX_ITEM STRUCTURE /OPT/VIM_1ITEM
*" CHANGING
*" REFERENCE(INDEX_DATA) TYPE /OPT/VIM_1HEAD OPTIONAL
*"--------------------------------------------------------
VIM070500-03-CGD-EN-1
9.1.12 Configuring Duplicate Check

In this step, you define the duplicate check procedure and assign it to a document
type. In the DP process the system uses this configuration to identify potential
duplicates and routes the work item to the duplicate check role defined in the
document type configuration.
Configuring duplicate check comprises the following steps:
• “To define a duplicate check group:“ on page 166

• “To define duplicate check fields for a group:“ on page 167
To define a duplicate check group:

Processing Configuration > General Configuration > Maintain Duplicate
Check Procedures.
2. To add a duplicate check group, click the New entries button in the application
toolbar.
3. Define the new duplicate check group, using the following parameters:
Duplicate Check Grp

Enter the 3 digit id identifying the duplicate check group.
Description
Enter a description for the duplicate check group.
Duplicate Check Type

Select Function Module or Index Data Fields from the drop down list.
Function Module
Select Function Module to configure duplicate check in a custom
function module. Enter the function module in the Duplicate Chk Func
field. The function module maintained here must have the same
interface as described in the field Ext. Dup. Check Func.
VIM070500-03-CGD-EN-1
Index Data Fields

Select Index Data Fields to configure duplicate check based on the
fields defined in the Group Fields. See “To define duplicate check
fields for a group:“ on page 167.
Ext. Dup. Check Func

Define a function module to define extended duplicate check to check SAP
documents. The interface for the function module is the following:
FUNCTION <FUNCTION>.
IMPORTING
REFERENCE(I_INDEX_DATA) TYPE /OPT/VIM_1HEAD
EXPORTING
REFERENCE(O_DUPLICATES) TYPE /OPT/VIM_1HEAD_T
REFERENCE(O_DUPLICATES_EXT) TYPE /OPT/VIM_DUPL_H_T
TABLES
INDEX_ITEM STRUCTURE /OPT/VIM_1ITEM OPTIONAL
Run Duplicate Check in Central System

This check box appears in satellite systems, only.
In multiple systems scenario, select this check box in any satellite system to
scan for duplicates through all DP documents of all systems in the
landscape, central as well as satellite systems.
The configuration data for Run Duplicate Check in Central System does
not have to be centralized. Local configuration can work without the need
of centralizing configuration data.
Note: The Aggregation Report batch job for the OTH_VMHEAD group
runs periodically and synchronizes the data of SAP IM documents to
the central system. The frequency of the batch job can be adjusted as
needed. Run Duplicate Check in Central System yields desired
results only after the batch job synchronized data with up to date
information. See “Scheduling the Aggregation Report” on page 681
for details.
To define duplicate check fields for a group:
In this step, you define the fields that need to be considered to define a duplicate
check. You can define multiple groups by maintaining them in the same step id.
1. In the Group Definition Overview screen, select a group and double-click

Group Fields in the navigation pane.
VIM070500-03-CGD-EN-1
2. Define duplicate check fields for the selected group, using the following
parameter:
Dup Check Step Id

Enter a value to group different fields from document data.
Example: If a document should be considered duplicate if document date, reference

number and gross amount matches or document date, reference number and PO
number matches, you can define:
• Step Id 1, Field name BLDAT

• Step Id 1, Field name XBLNR
• Step Id 1, Field name GROSS_AMOUNT
• Step Id 2, Field name BLDAT
• Step Id 2, Field name XBLNR
• Step Id 2, Field name EBELN
Currency field In versions before VIM 7.5 SP2 (and VIM 7.0 SP6), the duplicate check automatically
included the Currency field when an amount was configured in the duplicate check
customizing.
Since VIM 7.5 SP2 (and VIM 7.0 SP6), this automatism is removed. The Currency
field is not automatically checked during duplicate check, you have to customize it
explicitly.
This change was done to avoid duplicate postings which occurred if a wrong or
empty currency was delivered, for example, during OCR recognition or other input
channels. In these cases, it could happen that a duplicate was not found due to the
wrong currency check.
The new default delivery is a duplicate check without currency. It can lead to a
higher amount of possible candidates for duplicate check. For upgrade customers,
VIM070500-03-CGD-EN-1
OpenText recommends that you review the current duplicate check settings and
include the currency field (WAERS) to the customizing, if necessary.
9.1.13 Determining PO Invoices by Vendor Table

VIM provides the table /OPT/VT_DOC_DET. You can maintain the table using the
SM30 transaction. Currently, this table is specific to invoices processed in China but,
by design, this table can be used for other countries as well.
The table /OPT/VT_DOC_DET stores the vendors that send PO based invoices. In
China it is possible to send PO based invoices without providing the PO numbers on
it. Using this table, you can configure certain vendors that do this practice, thereby
determining the DP document type correctly.
The system first checks the entries in table /OPT/VT_DOC_DET. If the vendor is found,
the DP document is considered as a PO based invoice. If no vendor entry is found,
the system checks for the existence of any PO numbers on the invoice.
You can maintain vendors per company code and also ranges of company code and
vendor combinations.
To configure vendor table determination of PO invoices:
1. Align the document determination procedure in a way that the PO

determination happens first, followed by the NPO determination.
2. Copy function module /OPT/VIM_DET_DOC_TPE_PO_INV_CN. This function

module contains the determination code based PO determination based on the
vendor for China. For other countries, you must modify it.
3. In the document type determination procedure, add the step details with the
custom function module copied in Step 2. See “Document Type Determination
and Characteristic Customizing” on page 466.
9.1.14 Configuring Auto Coding

The auto coding component enables you to configure dynamically that DP Non PO
documents are automatically coded with the configured cost elements.
Configuration The whole configuration for auto coding is integrated in the OpenText
aspects Configuration tree: Navigate to Vendor Invoice Management > Document
Processing Configuration > General Configuration > Automated Line Processing >
NPO Line Auto Coding.
To configure auto coding, the following steps are necessary:
1. Define dynamic determination for auto coding.
• Define determination fields

• Define determination data
VIM070500-03-CGD-EN-1
2. Integrate a process type for the document type to execute auto coding in the DP
processing.
9.1.14.1 Defining Determination Fields

You can individually configure the fields for the dynamic determination of the auto
coding processing.
To define determination fields:
1. In the OpenText Configuration tree, navigate to Vendor Invoice Management

> Document Processing Configuration > General Configuration > Automated
Line Processing > NPO Line Auto Coding > Auto Coding Determination -
Fields
The following screenshot shows the configuration that is used for the
determination and the coding fields.
2. Define determination fields using the following parameters:
Determination Type
Enter ACO (Auto Coding Configuration)
The determination type is defined in table /OPT/AT_DETTYPE. The type ACO
is delivered within the posted approval baseline configuration.
Field Type
Available values are Header or Item. For the determination, only header
fields are relevant.
Field Name
Select the corresponding field of the /OPT/VIM_1HEAD or /OPT/VIM_1ITEM
table.
Sequence
Define the processing sequence of the determination.
Search Help Name

Configure the search help that will be used in the data determination
configuration.
VIM070500-03-CGD-EN-1
Allow Ranges
Select this check box to allow ranges in the data determination
configuration. For item fields, ranges are not allowed.
9.1.14.2 Defining Determination Data

You can individually configure the data for the dynamic determination of the auto
coding processing, based on the defined fields.
To define determination data:

> Document Processing Configuration > General Configuration > Automated
Line Processing > NPO Line Auto Coding > Auto Coding Determination -
Data
The following screenshot shows the configuration for the fields configured in
“Defining Determination Fields” on page 170.
2. To activate the auto coding configuration, configure the corresponding ranges

and data. You can add or remove lines.
You can use the Skip Stack indicator to automatically skip the coding or
requester step when the approval is triggered. The following values are
possible:
C
Skip the coding step (most common setting).
VIM070500-03-CGD-EN-1
R
Skip the coding step and the requester step.
S
Skip the requester step. However, in case of rejection, the document is still
sent to the requester in the approval process.
3. To open the Detail Configuration, double-click a determination line or click the

Details button .
Configure the corresponding coding.
The coding is used to insert an initial line item with the net amount of the
invoice in the processing. Existing lines are overwritten with the configured
coding.

A transport is created for the corresponding settings.
9.1.14.3 Defining a Process Type for Auto Coding

To execute the auto coding, you must integrate a process type in the document
processing for the following reasons:
• to update the /OPT/VIM_1ITEM table

• to determine if the document has to be coded automatically.
Therefore, you can use the “exception” function /

OPT/VIM_DETERMINE_PROC_LIB003 for custom processing.
To integrate a process type, follow the customizing steps in “Defining the Process
Type” on page 225.
The process type needs the following settings:
• No exception
• No user process options
• Autopost flag activated
• Bypass and simulate deactivated
• Process type determination sequence before Approval Required process option
• Sequence step function module /OPT/VIM_DETERMINE_PROC_LIB003
The following screenshots show example settings of the process type:
Process Type Definition (no other settings relevant); see also “Defining the Process
Type” on page 225:
VIM070500-03-CGD-EN-1
Document Processes; see also “Defining Process Types” on page 141:
Index Screen Options (no other settings relevant): see also “Configuring Index
Screen Options” on page 146:
Process Type Determination Sequence (no other settings relevant); see also
“Defining the Process Type Determination Sequence” on page 143
Sequence Steps: see also “Defining Sequence Steps” on page 144
VIM070500-03-CGD-EN-1
9.1.15 Mapping for Coding Upload from Excel Sheet

The agent who is working with the indexing screen can upload coding lines from an
Excel sheet. This new feature enables the agent to use an existing template of coding
lines available in an Excel sheet.
The corresponding Upload Coding button is added to the indexing screen. You can
configure the button to be shown or hidden. For more information about
configuring the button, see “Configuring Index Screen Options” on page 146.
In this step, you configure the mapping between VIM fields and columns in the
Excel sheet for coding upload in the indexing screen.
To map indexing fields for coding upload from Excel sheet:

Management > Invoice Approval Configuration > Technical General >
Upload/Download File Configuration > Upload Coding in Indexing
Configuration
2. Configure the mapping, using the following parameters.
Application Area
IDX_CODING is specific for coding upload in Indexing.
Table Name
/OPT/CIDX_ITEMS is also specific for coding upload in Indexing.
Note: The Application Area and Table Name fields are not editable.
They will be added to the entries during the configuration.
Fields
Field name in the indexing screen.
VIM070500-03-CGD-EN-1
9.2. Configuring Automatic Posting
Active
Select this check box to specify that the field is considered in the uploading
process.
Sequence
Enter digits that indicate the sequence of Excel sheet columns that will be
mapped. This sequence number must be unique.
Example: The first column of the Excel sheet is mapped to the field with the lowest
sequence number. The second column of the Excel sheet is mapped to the field with
the second lowest sequence number, and so on.
9.2 Configuring Automatic Posting

VIM 7.5 introduces extended configuration options to control the automatic posting
of DP documents. It is not possible to post each and every NPO or PO related
document automatically in background. There might be some restrictions because
the standard SAP BAPI does not support all scenarios that SAP standard
transactions support. There also might be business related reasons that prevent a
document from being posted in background automatically.
With VIM 7.5 and above, the baseline document types PO_75, NPO_75 and DWN_75
will no longer get posted automatically. You must activate them to get posted
automatically.
To activate the automatic posting configuration, you must configure the document
type accordingly: In the process type definition, you must configure the baseline
function module /OPT/VIM_DETERMINE_AUTOPOST for the default process type or the
relevant process types for automatic posting.
Automatic posting might fail, for example, if the scenario is not supported or if the
necessary configuration has not been implemented. In this case, the DP document is
re-routed to the posting role, which is defined in the DP Document Type; see
Posting Role on page 140.
VIM070500-03-CGD-EN-1
For details, see “Defining Process Types” on page 141.
9.2.1 Activating Business Related Automatic Posting

Not every DP document must be posted directly in background. There might be
business related reasons, for example a certain combination of company code and
total amount, to post some documents in background and other documents
manually.
To enable the background posting of DP documents, you must configure a dynamic

activation, as described in this section.
Configuring Automatic Posting: Fields

You can configure the fields for the dynamic determination of the automatic posting
individually.
To configure automatic posting fields:

> Automated Posting Determination > Auto Posting Determination - Fields.
2. Configure the fields for automatic posting, using the following parameters:
Determination Type
The determination type for automatic posting is APO. It is defined in table /
OPT/AT_DETTYPE. The determination type APO is delivered in the baseline
configuration.
Field Type
You can configure Header or Item fields. For the determination, only
header fields are relevant.
Field Name
Select the corresponding field of table /OPT/VIM_1HEAD or /
OPT/VIM_1ITEM.
Sequence
Search Help Name
You can configure a search help, which will be used in the data
determination configuration.
VIM070500-03-CGD-EN-1
Allow Ranges
Select this check box to allow configuring ranges in the data determination
configuration.
Configuring Automatic Posting: Data

You can configure the data for the dynamic determination of the automatic posting
individually, based on the defined fields.
To configure automatic posting data:
• Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice

> Automated Posting Determination > Auto Posting Determination - Data.
“Configuring Automatic Posting: Fields” on page 176.
In this example, all documents of the company codes 1000 to 2000 and vendors
1000 to 9000 will be posted automatically.
9.2.2 Scenario Related Automatic Posting Restrictions

Not every DP document must be posted directly in background. There might be
scenario related reasons that do not support an automatic posting. If the SAP BAPI
does not support a scenario, the document will be excluded from automatic posting.
It must be posted in dialog.
The automatic posting activation function /OPT/VIM_DETERMINE_AUTOPOST also

checks the excluded scenarios in processing class /OPT/CL_D_DETERMINE_AUTOPOST.
For more information, see “Configuring Automatic Posting” on page 175.
The following scenarios are excluded. The scenarios will be enhanced in the future.
VIM070500-03-CGD-EN-1
• NPO - Cross company posting is not supported if the company codes have
different currencies.
• NPO - Specific currency translation for tax
• PO - Mixed Services and Goods in combination with multi account assignment
9.2.3 Scenarios Where Automatic Posting Is Not Supported

The following list describes some specific situations when baseline VIM logic cannot
post invoices correctly. These situations are not supported. In some cases, an attempt
to post the invoice fails with an error. In other cases, the posting works, but with
unwanted side effects. To complement general testing, OpenText recommends that
you verify the posting results carefully in these specific situations. Make sure that
the documents are posted correctly. If they are not posted correctly, decide if you
switch off the automatic posting.
Note: The following list is not guaranteed to be complete. It will be extended if

new limitations are discovered.
• NPO - Fields that are not supported by standard SAP BAPI: LNRZE (Head office
account number)
• PO - Fields that are not supported by standard SAP BAPI: LNRZE (Head office
account number), SECCO (Section Code)
• Distribution logic “by amount” is not supported if it is used in multiple account
assignment of a PO position.
Note: Starting with VIM 7.0 SP7 and VIM 7.5 SP3, this scenario is
supported.
• Posting of material lines for PO invoices is not supported in the same way as the
MIRO transaction does it.
• The line number of a PO invoice might be limited according to the Z constant
NR_ALLOWED_LINEITEMS to maximum allowed lines. The default value is 1,000. If
the line count of the invoice to be posted exceeds the limit, the posting will stop.
• Posting to a tax GL account is supported for NPO invoices with BDC ID 42,
starting with VIM 7.0 SP7 and VIM 7.5 SP3.
• Asset posting is not supported in VIM baseline. If you absolutely need this
functionality, you must implement it as an extension (BDC with the F-90
transaction).
• Until VIM 7.0 SP6 (VIM 7.5 SP2), line by line tax determination based on tax
jurisdiction codes was not supported with BDC ID 34 on latest SAP EHPs. For
details, see the SP list in OSS note 1692637. The reason for this were new
restrictions imposed by the standard SAP posting logic. The check that stops the
posting could be switched off by setting the Z constant SKIP_LINETAX_CHECK.
Starting with VIM 7.0 SP6 (VIM 7.5 SP2), such invoices can normally be posted
when another Z constant USE_ITEM_COUNTER is set.
VIM070500-03-CGD-EN-1
• Net vendor invoices, which typically have SAP document type KN, cannot be
posted with BDC ID 34. VIM does not calculate the discount and does not create
automatic lines for discount posting. OpenText recommends that you use BDC
ID 41 (batch input with the FB60 transaction) or BDC ID 42 (starting with VIM 7.0
SP7 and VIM 7.5 SP3) to post discounts correctly.
• When posting in background with BDC ID 41, pay attention to the way how line
item amounts in the DP document (gross or net) are entered. It must be in sync
with the gross or net setting flag of the user that is used to post the documents,
typically WF-BATCH.
• VIM provides a limited logic of assigning the default values to cost elements.
VIM supports determining the tax jurisdiction code from cost center, WBS
element, network or activity, internal order, and vendor master. The current logic
of assigning the default values may not satisfy your implementation
requirements. In this case, extend the logic with the provided extension
mechanisms or disable automatic posting of such invoices.
• Tax reporting date (VAT date) is posted if the corresponding field exists in the
SAP BAPI structure, which depends on your SAP SP level. Moreover, the
company code must be set up to use VAT date. However, if the company code is
set up for VAT date but the BAPI structure does not allow this, the background
posting stops. The invoice must be posted in dialog.
Note: You can disable the VAT date and BAPI structure check by setting
the Z constant SKIP_VATDATE_CHECK.
• You might want to post an invoice with CPD vendor. If there is no IBAN field in
the BAPI structure, the posting will stop. To avoid this, set the Z constant
SKIP_BAPICHECK_SEPA.
9.2.4 Activating User Related Automatic Posting

Often users themselves are aware if a document can be automatically posted or if it
must be posted in dialog. The indexing screen provides a way how to route a
document accordingly: the Document Creation field. For more information, see
section 4.6 “Posting Invoices for Payment” in OpenText Vendor Invoice Management for
SAP Solutions - User Guide (VIM-UGD).
To activate the Document Creation field on the indexing screen (AUTO_POST field),
see “Configuring the Index Header” on page 149.
Using the Document Creation field, the user can decide whether the document
should be posted automatically in background (A), online in dialog (M), or posted as
configured.
The decision of the user has the highest priority, that means, no matter what is
configured for the document type,
• if Document Creation is set to A (Auto posted), the document will be posted

automatically.
VIM070500-03-CGD-EN-1
• if Document Creation is set to M (Manual), the document must be posted in

dialog.
• if Document Creation is set to <space> (as configured), the document will be
posted automatically when it is configured to be posted automatically or the
Autopost Flag is set to X. For more information, see “Defining Process Types”
on page 141.
9.3 Processing Logic Modules

To increase the automation of the DP process, you can use logic modules, which are
introduced with VIM 7.5.
The task of logic modules is to check whether data is missing for a document and to
add the data where possible. This data enrichment is scheduled before the business
rules run. It might be useful to also trigger some logic modules at a later point of
time, for example if the user has entered data on the indexing screen and presses
Rerun Business Rules. A new business rule has been introduced that “informs” the
user that a logic module has added data to the document. Business rules are
intended to check document data whereas logic modules are intended to also change
document data.
Logic module customizing comprises modules, process IDs and the mapping of
document types to process IDs. The smallest unit is a logic module. It consists of a
class method (including an user exit) running its own checks and its own data
retrieval. The logic modules are clustered together to process IDs obtaining a certain
sequence. There are process IDs for PO documents and Non PO documents.
Some logic modules replace existing mapping function modules, others are
completely new.
• Example for simple mapping

Determination of bank data from vendor master
• Example for complex mapping
Additional cost handling based on line items delivered and marked by OCR.
1. VIM checks whether additional costs have been planned in purchase order.
2. If unplanned additional costs exist, they are moved to header or line items
according to VIM Additional Cost Customizing.
The logic module framework is the underlying technology. It determines which

logic module is carried out at what point(s) of the process.
“Best Practice” in VIM 7.5 means that OpenText delivers a set of logic modules/
process IDs that you can use by assigning them to your document types, according
to your processes.
The configuration of logic module processing is completely integrated in the /

OPT/SPRO tree:
VIM070500-03-CGD-EN-1
9.3. Processing Logic Modules
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
Document Processing Configuration > Document Type Configuration > Logic
Module Processing.
To configure the logic module processing, the following steps are necessary:
• Configuring logic module processing (mandatory)
• Defining dynamic determination for determination type BPF (optional)
• Activating logic module processing - Fields
• Determining logic module processing - Data
9.3.1 Configuring Logic Module Processing

The configuration contains the following steps
• Defining logic modules (mandatory)
• Configuring field change for exception (optional)
• Configuring messages for exception (optional)
• Defining the processing (mandatory)
• Configuring module processing steps (mandatory)
• Mapping the processing definition (mandatory)
9.3.1.1 Defining Logic Modules

Configure modules with the corresponding processing logic and possible exception
handling. When you create your own module, create a delegated class of super
class /OPT/CL_D_LM_SUPER.
To define logic modules:

Configuration > Logic Module Processing > Logic Module Processing.
2. Define the module, using the following parameters:
VIM070500-03-CGD-EN-1
Module ID
Unique ID of the module
Class Name
Enter the processing class of the logic module. The class must have super
class /OPT/CL_D_LM_SUPER. Method /OPT/IF_D_BP_MODULE~PROCESSING
must be redefined to integrate own processing logic.
Process Type Activation
Select how the process type is activated. A process type or exception gets
triggered according to the activation type:
Activate on field change
The process type gets triggered by a field change. See “Configuring
Field Change for Exception” on page 182.
Activate on custom logic
The process type gets triggered by custom logic implemented in Exit
FM.
Process Type
Enter the process type.
Process type 405 is a template for the one time business rule trigger. The
rule gets triggered when a field is changed within the module or by custom
logic (see Process Type Activation on page 182)
Exit FM
Enter the exit function for process type activation on custom logic. Use
template function /OPT/VIM_DBPF_TEMPLATE_PROC_TR to create your own
function module.
9.3.1.2 Configuring Field Change for Exception

In this step, you configure the fields for the process type activation based on field
change. This is only relevant for Activate on field change. Whenever a field is
changed (at least one of the field list) in the logic module, the corresponding
exception is triggered.
To configure field change for exception:

Configuration > Logic Module Processing > Logic Module Processing.
2. In the Module Definition Overview screen, select a Module ID that has Process
Type Activation Activate on field change, and double-click Field Change
for Exception in the Dialog Structure.
3. In the Field Change for Exception screen, configure the fields, using the
Field Type
Select Header or Item.
VIM070500-03-CGD-EN-1
Field Name
Enter the name of the field in the index data table. The table is either /
OPT/VIM_1HEAD or /OPT/VIM_1ITEM.
9.3.1.3 Configuring Messages for Exception

In this step, you configure the messages that are shown in the index screen when the
configured exception (see “Defining Logic Modules” on page 181) occurs.
To configure messages for exception:
1. In the Module Definition Overview screen, select a Module ID that has Process
Type Activation Activate on field change, and double-click Messages for
Exception in the Dialog Structure.
2. In the Messages for Exception screen, configure the messages, using the
Application Area
Enter the message class of the message.
MsgNo
Enter the message number.
Fld.Change
Select this check box to show a message for each field that gets changed
with relevant information:
/OPT/VIM_BPF - 001
Message for item field changes
/OPT/VIM_BPF - 002
Message for header field change
Field Type
Select if the message is shown for Header or Item fields.
9.3.1.4 Configuring the Processing Definition

In this step, you configure the relevant logic module processing definition. Logic
modules are clustered in process IDs in order to have the following:
• a processing sequence
• different processing for PO / NPO document types
• easier configuration: basic enrichment is separate from special handling
(additional costs)
To configure the processing definition:
1. In the Module Definition Overview screen, select a Module ID and double-

click Processing Definition in the Dialog Structure.
VIM070500-03-CGD-EN-1
2. In the Processing Definition screen, define the processing, using the following
parameters:
Process ID
Enter the unique Process ID of the processing steps.
Description
Enter the description of the processing steps.
9.3.1.5 Configuring Module Processing Steps

In this step, you assign the logic modules to the processing definition.
To assign logic modules to the processing definition:
1. In the Processing Definition screen, select a Process ID and double-click

Module Processing Steps in the Dialog Structure.
2. In the Module Processing Steps screen, assign the logic modules to the
processing definition, using the following parameters:
Counter
Enter the sequence of the modules.
Module ID
Enter the unique ID of the module (see “Defining Logic Modules”
on page 181).
Active
Select this check box to activate each module in the process.
Process Mode
Define when to trigger the module: at Process Start, at Rerun Rules
(rerun business rules), or at both times (Start + Rerun).
Relation
Select the relation between the modules: AND or OR
VIM070500-03-CGD-EN-1
You can define if the module has run successfully or not within the
processing class (see “Defining Logic Modules” on page 181).
• If you define an AND relation between two modules and the first module
does not run successfully, the next modules will not be processed at all.
• If you define an OR relation, the next modules in the OR relation will be
skipped if the previous module ran successfully.
Notes
• Use the AND relation as default to run all modules correctly.
• If no relation is available between modules in one process
definition, the process will not continue with the next module.
• Take the process mode into account if you need to configure
different relations: Create different processing definitions for
different process modes.
9.3.1.6 Mapping the Processing

In this step, you map the process definition with the related module processing steps
to the relevant document types, other fields (determination) or other logic (function
module).
You can map the process ID in the following different ways:

• Map to Channel ID and Document Type: use Activation Type Activate by
Constant.
• Map by determination, you can define your own determination fields, see
“Configuring Logic Module Processing Determination - Fields” on page 187: use
Activation Type Activate by Determination.
• Map by using a customer specific function module: use Activation Type
Activate by Custom Function and fill FM to determine Process ID.
To map the process definition:
1. In the Module Definition Overview screen, double-click Processing Mapping

in the Dialog Structure.
2. In the Processing Mapping screen, perform the mapping of the process

definition, using the following parameters:
VIM070500-03-CGD-EN-1
Counter
Define the sequence of processing.
Channel ID
Only relevant for activation type Activate by Constant.
Enter the input channel that is used for the process definition. If it is empty,
all channels are valid.
DP Document Type
Only relevant for activation type Activate by Constant.
Enter the document type that is used for the process definition. If it is
empty, all document types are valid.
Note: When upgrading from older VIM releases, you might like to
have some document types using logical modules and some others
run without logical modules. In this case, you need to remove the
standard entries in the processing mapping with empty document
types. This will prevent the logical modules to be called for all
documents. The removed entries need to be replaced with respective
entries for each document type that will need to have logical modules
called.
Activation Type
Select how your mapping is activated. If you select Activate by Constant,
input channel and document type are the relevant parameters that are taken
into account.
You can also select Inactive, Activate by Custom Function or Activate
by Determination (see “Configuring Logic Module Processing
Determination - Fields” on page 187).
Process ID
Enter the unique ID of the processing steps.
FM to determine Process ID
If applicable, enter the name of the function module to activate the logic
module processing. Use template function /OPT/VIM_DBPF_TEMPLATE_DET
to create your own function module.
VIM070500-03-CGD-EN-1
9.3.2 Configuring Logic Module Processing Determination -

Fields
You can configure the fields for the dynamic determination of the logic module
processing individually.
Important
If there are entries in the logic module processing mapping that have
activation type Activate by Determination, you must define the relevant
fields and the data. Otherwise, you can skip sections “Configuring Logic
Module Processing Determination - Fields” on page 187 and “Configuring
Logic Module Processing Determination - Data” on page 188.
This section describes the configuration of fields that are used for the determination.
The process ID (PROC_ID) field (see screenshot below) is required to assign the
correct process.
To configure fields for the logic module processing determination:

Configuration > Logic Module Processing > Logic Module Processing
Determination - Fields.
2. In the Maintenance View for Logic Module Processing, configure fields for
logic module processing, using the following parameters:
Determination Type
BPF (mandatory)
The determination type for Best Practice Framework Configuration is
BPF. It is defined in table /OPT/AT_DETTYPE. The determination type BPF is
delivered in the baseline configuration.
Field Type
You can configure Header or Item fields. For the determination, only
header fields are relevant.
Field Name
Select the corresponding field of table /OPT/VIM_1HEAD.
VIM070500-03-CGD-EN-1
Sequence
Search Help Name

You can configure a search help, which will be used in the data
determination configuration.
Allow Ranges
Select this check box to allow configuring ranges in the data determination
configuration.
9.3.3 Configuring Logic Module Processing Determination -

Data
You can configure the data for the dynamic determination of the logic module
processing individually, based on the defined fields.
Important
This is only relevant if there are entries in the logic module processing
mapping that have activation type Activate by Determination. Otherwise,
you can skip sections “Configuring Logic Module Processing Determination
- Fields” on page 187 and “Configuring Logic Module Processing
Determination - Data” on page 188.
To configure logic module processing determination data:
• Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice

Configuration > Logic Module Processing > Logic Module Processing
Determination - Data.
The following screenshot shows an example for the fields configured in
“Configuring Logic Module Processing Determination - Fields” on page 187.
VIM070500-03-CGD-EN-1
9.4. Business Rule Framework
In this example, the Logic Module Process ID N_SPEC_001 is used for all
documents of the company code 7000 and vendors 1000 to 3000 + for the
company code 7500 and vendors 4000 to 7000.
9.4 Business Rule Framework

VIM 7.5 provides the Business Rule Framework (BRF), which allows you to
configure the business rule processing in a more detailed way. The usage of the BRF
is optional. If nothing is configured in the BRF Schemata Assignment, the business
rules are carried out as usual.
9.4.1 New Features of the BRF

In previous VIM versions, a business rule (= process type) was either set active or
inactive for a document type. For more information, see “Defining Process Types”
on page 141.
With VIM 7.5, the settings are more refined with respect to check status, check
conditions, vendor grouping, and assignment.
The new check status does not only mean that a business rule run is either on or off.
The check status also considers counter based, random, periodic, or once as possible
triggers for a business rule run.
The new check condition definition allows you to limit business rule runs to either
exceeding a minimum amount or receiving a flag from a custom function.
9.4.1.1 Check Type / Check Status

You can assign the following business rule run statuses. A check type means that you
can configure a business rule run to on, off, random, and so on. See the following
list.
• Random
The business rule might or might not run.
• Condition based (function module)
The business rule runs only if a custom function module delivers a success flag.
• Counter based
If the counter is reached, the business rule runs. The counter can be customized.
• Blind
The business rule runs without stopping in case of an exception.
• Off
The business rule does not run (inactive).
• Check
The business rule runs (active).
VIM070500-03-CGD-EN-1
• Periodic
The business rule runs every x month for a vendor. The x can be customized.
• Once per vendor
The business rule runs once.
9.4.1.2 Check Condition / Check ID

You can assign each business rule, a subset of business rules, or all business rules to
a check condition. The following check conditions are available.
• Amount based
A minimum amount is configured. If the document exceeds this amount, the
business rule is run.
• Function module based
A custom function can be implemented. If it returns a success flag, the business
rule is run.
9.4.1.3 Vendor Group

You can group vendors to white list, grey list, or black list vendor groups. For white
list vendors, you can limit the execution of business rules to the most important
ones. Grey list vendors, however, can be checked more intensely and black list
vendors can be assigned a very strong rule framework.
9.4.1.4 BRF Schemata Assignment

The check types, which control the business rule runs, can be assigned to different
customizing objects, for example a vendor group. Assignments can be very
detailed by entering single process types and company codes or they can be
extensive by only entering a vendor group.
You can assign check types to the following elements.

• Company Code (range)
• Vendor group
• Document type
• Exception Class or Process Type
• Check condition (ID)
VIM070500-03-CGD-EN-1
9.4.2 Configuring the BRF

The configuration of the BRF is integrated in the /OPT/SPRO tree:
Document Processing Configuration > Process Configuration > Business Rule
Framework (BRF).
To configure the BRF, you must perform the following steps:
• Configuring vendor groups (white list, grey list, black list)

• Assigning vendors to the groups; unassigned vendors automatically belong to
the grey list.
• Defining names for the check types
• Defining check IDs if you want to use amount limits or custom function modules
• Defining which check types are valid for which process types and which
documents (document type, company code, vendor group)
9.4.2.1 Configuring Vendor Groups
To configure vendor groups:

Management > Document Processing Configuration > Process Configuration
> Business Rule Framework (BRF) > Maintain BRF Vendor Group.
In the BRF - Vendor Group Overview screen, the following vendor groups are
preset: WHITE, GREY, and BLACK.
2. Optionally, add other vendor groups, using the following parameters:
Vendor Group
Unique name for the vendor group (black, grey, white)
Description
Description of the vendor group
9.4.2.2 Assigning Vendors to Vendor Groups
To assign vendors to vendor groups:

> Business Rule Framework (BRF) > Maintain BRF Vendor Group
Assignment.
VIM070500-03-CGD-EN-1
2. In the BRF - Vendor Group Assignment Overview screen, assign vendors to

vendor groups, using the following parameters:
Company Code from

Enter a single value or the lowest company code in a range.
If this field is empty, the assignment is valid for all company codes.
Company Code to
For ranges only: Enter the highest company code in a range.
Vendor
Enter the vendor number.
If this field is empty, the assignment is valid for all vendors of the company
code(s).
Country
Vendor country code, for example DE for Germany.
Name
Vendor name.
Vendor Group
Enter the vendor group. For more information, see “Configuring Vendor
Groups” on page 191.
Description
Vendor group description. For more information, see “Configuring Vendor
Groups” on page 191.
VIM070500-03-CGD-EN-1
9.4.2.3 Maintaining Check Type ID Names

The following check types are preset:
• RANDOM
• CONDITION
• COUNT
• BLIND
• OFF
• CHECK
• PERIODIC
• ONCE
For more information, see “Check Type / Check Status” on page 189.
To maintain check type ID names:

> Business Rule Framework (BRF) > Maintain BRF Check Type ID Name.
2. In the BRF - Check Type ID Overview screen, fill the check type descriptions
(especially in additional languages), using the following parameters:
• Chck. Type ID
• Check Type name
• Check Type Description
9.4.2.4 Maintaining Check IDs

The check condition definition allows you to limit business rule runs to either
exceeding a minimum amount or receiving a flag from a custom function.
To maintain check IDs:

> Business Rule Framework (BRF) > Maintain BRF Check ID.
VIM070500-03-CGD-EN-1
2. In the BRF - Check ID Overview screen, configure check conditions (check

IDs), using the following parameters:
Check ID
Enter the unique ID of the check condition.
Description
Enter the check condition description.
Check Base
Select which check base you want to use. Possible options:
Amount based
If you select this option, you must enter values in the following fields:
Amount, Currency, Amount Base, and Conversion Date.
Function Module
If you select this option, you must enter a custom check function in the
Check Function field.
Check Function
Enter the exit function for the function module check base. You can use
the /OPT/VIM_DCMP_EX_CONDITION function module as a template.
Amount
Enter a minimum amount for a business rule run.
Currency
Enter the currency for the minimum amount.
Amount Base
Select Gross amount or Net amount.
Conversion Date
Define a currency conversion date. You can select one of the following
options:
• Current System Date
• Date on the Vendor Invoice
• Posting Date
• Date of the supply of the Goods or Services.
Conversion Function
Optionally, enter a custom function for the currency conversion. If you
leave this field empty, the SAP function module
CONVERT_TO_LOCAL_CURRENCY is used.
VIM070500-03-CGD-EN-1
9.4.2.5 Configuring the BRF Schemata

To configure the BRF schemata, you fill in either the Exception Class ID or the
Process Type to limit the validity of the check type. If both fields are empty, the
check type is valid for all active business rules.
To configure the BRF schemata:

> Business Rule Framework (BRF) > Maintain BRF Schemata Assignment.
2. In the BRF - Schemata Assignment Overview screen, configure the BRF

Schemata Assignment, using the following parameters:
Company Code from

Enter a single value or the lowest company code in a range.
If this field is empty, the assignment is valid for all company codes.
Company Code to
For ranges only: Enter the highest company code in a range.
Vendor Group
Enter the vendor group. If you leave the field empty, the Grey list vendor
group is taken.
DP Document Type
Enter a DP document type. If you leave the field empty, the assignment is
valid for all DP document types.
Exception Class ID, Exception Class

To limit the check type, enter an exception class ID, which bundles several
process types. See the definition in “Mapping Exception Classes”
on page 647.
Process Type
If you do not use an exception class ID and you nevertheless want to limit
the check type, enter a process type.
Check ID
To limit the check type, assign a check ID as defined in “Maintaining Check
IDs” on page 193.
Check Type
Select a check type. For more information, see “Maintaining Check Type ID
Names” on page 193.
VIM070500-03-CGD-EN-1
Counter X
If you use Counter Based check type: Enter a numeric value for the counter.
When the counter is reached, the business rule runs.
9.4.3 Additional Configuration

The following Z constants have influence on the BRF.
COMPL_RANDOM_MIN
Valid for check type RANDOM. You can increase or decrease the probability of
exceeding the minimum random value.
This central value is used as a lower limit for the Business Rule Framework. If
check type RANDOM is active for a business rule (process type), the SAP random
number generator is called. It returns a value between 0 and 100. If you want
business rules to run very rarely, you have to enter a high value (for example
90). If you want them to run more often you have to enter a low value (for
example 10).
CUSTOM_FM_COMPLIANCE
You can create a customer specific function module for the BRF matching. Use
template /OPT/VIM_DCMP_EX_MATCH.
COMPL_ALLOW_M_BYPASS
The DP indexing simulation screen shows activate/bypass icons that are set by
the BRF or manually. If a BRF check type exists and this Z constant is empty, the
icon cannot be changed. If no check type exists or this Z constant is set to X,
manual changes are possible.
COMPL_HIDE_CHECKTYPE
If this Z constant is set to X, the DP indexing simulation screen does not show
the check type column. If it is empty, it shows the column.
9.4.4 BRF Test Tool

VIM 7.5 introduces the new /OPT/VIM_CP_TEST transaction. It calls a basic test tool
for the BRF. You can use the test tool for the following purposes:
• to show the processing steps for a group of documents that is defined by:
• DP document type
• Company Code
• Vendor
• to show the processing steps of a DP document.
VIM070500-03-CGD-EN-1
9.4.4.1 Example 1: Group Selection

To show the processing steps for a group of documents:
1. Run the /OPT/VIM_CP_TEST transaction.
2. Select Show Processing Steps (group).
3. Enter DP document type, company code, and vendor, and click .
VIM070500-03-CGD-EN-1
The displayed list covers the following data:

Header data
• DP Document Type
• Characteristic (country)
• Vendor Group
Step data
Step ID
Technical information: processing sequence
Process Type
Technical information: process type ID
Business Rule
Name of the process type (business rule)
VIM070500-03-CGD-EN-1
Activate/Bypass
A business rule can take one of the following statuses:
<empty>
active (no manual bypass possible)
active
inactive / bypassed
bypass possible depending on the check type

The following check types trigger the status “bypass possible”:
Random
At business rule run time, the random function delivers a bypass
variable that is either filled or empty.
Condition
At business rule run time, a custom function delivers a bypass variable
that is either filled or empty.
Count
At business rule run time, the counter is checked for company code,
vendor and process type/exception class. If a predefined value is
reached, the business rule is run. Otherwise, it will be bypassed.
Periodic
At business rule run time, the current date is compared to a predefined
period and last run for company code, vendor and process type/
exception class. If the predefined period is reached, the business rule is
run. Otherwise, it will be bypassed.
Once
At business rule run time, it is checked whether the business rule has
been run once for company code/vendor/document type. If the business
rule has run before, it is bypassed. If it did not run before, it is run now.
Check Type
If a check type has been assigned in the BRF schemata assignment, it is
shown.
Initial Role
Role that is assigned to the business rule.
4. To return to the selection screen, click .
VIM070500-03-CGD-EN-1
9.4.4.2 Example 2: Document Selection

To simulate business rules for a single document:
1. Run the /OPT/VIM_CP_TEST transaction.

2. In the Process Information area, select Simulate Business Rules 1 doc.
3. In the Selection area, enter the DP Document ID and click .
Header data
• Document ID
• DP Document Type
• Characteristics (country)
• Invoice Category
• Vendor Group
Step data is identical to the group result list; see Step data on page 198.
VIM070500-03-CGD-EN-1
9.5. Customizing Profiles for the Indexing Screen
4. To return to the selection screen, click .
9.5 Customizing Profiles for the Indexing Screen

You configure the indexing screen for all global settings within a profile. A profile
describes all relevant default user screen settings and enables you to integrate own
processing logic. You can assign different profiles directly to different users if
specific settings are necessary.
Note: VIM baseline delivers a global profile (DEFAULT), which is called

whenever no specific user profile is configured. The DEFAULT profile must
always be available.
You can assign a specific user profile, using the user parameter /
OPT/CIDX_CUST_PROF.
The following customizing steps are necessary:

• Defining the profile
• Defining profile settings
9.5.1 Defining the Profile

The profile definition describes the overall profile with a unique ID and the
corresponding description.
To define the profile:

> Maintain Customizing Profiles for Index Screen
2. In the Profiles Details screen, define the profile, using the following
parameters:
Customizing profile
Unique ID of the profile
Customizing Profile Description

Description of the profile
VIM070500-03-CGD-EN-1
9.5.2 Defining Profile Settings

The general profile settings comprise pure UI related settings as well as some
important functional application parameters.
The general default profile (DEFAULT) included in the baseline delivery assumes a
minimum screen resolution of 1600 x 900 for all UI related settings.
To define profile settings:
1. In the Profiles Details screen, double-click Profile Settings in the Dialog

Structure panel.
2. Define the profile settings using the following parameters. The corresponding
settings are called during runtime.
Customizing Profile
Unique ID of the profile
Application Class
Enter the application class.
The complete logic of the indexing screen is combined in the application
class of the indexing screen. All relevant attributes and methods of the
global application class are delivered in a baseline indexing screen
application. You can enhance the class by redefining components of the
class within a custom class, which can be maintained instead of the baseline
class.
Default value: /OPT/CL_C_IDX_APPLICATION
UI Class
Enter the UI class.
VIM070500-03-CGD-EN-1
9.5. Customizing Profiles for the Indexing Screen
All relevant screen logic is combined within the UI class of the indexing
screen. Like for the application class, the baseline class delivers the
complete screen logic, which you can redefine.
Default value: /OPT/CL_C_IDX_UI_CONTROLLER
Process Options
Enter the process options class.
This class includes the process options to be executed within the indexing
screen.
Default value: /OPT/CL_C_IDX_PROCESS_OPTIONS
User Class
Enter the user class.
This class includes necessary user settings and configuration of the indexing
screen.
Default value: /OPT/CL_C_IDX_USER
The plug-in options of the profile are used when the user calls the indexing
screen the first time. Changes done during screen processing are stored when
the indexing screen is left and the screen is opened in the same way the next
time. For details about plug-ins, see “Customizing Plug-in Controls for End-
user Screens“ on page 537.
Plug-In Type
Enter the plug-in type that is used within the indexing screen by default.
Default value: VIM_IDX
Plug-In ID
Enter the default plug-in ID that is used in the indexing screen.
Default value: 10 (Image plug-in)
Plug-In Side
Select the default plug-in side where the plug-in is displayed on the screen.
Default value: Right justified
Cont. Pane % Vt.

Content pane size ratio vertical in %: Enter the default plug-in size in
percent of the indexing screen, a % value between 5 and 90.
Default value: 42
VIM070500-03-CGD-EN-1
9.6 Roles in Document Processing

OpenText delivers standard roles for Document Processing (DP) in the baseline.
To display the table of roles, run the /OPT/CP_9CX5 transaction.
Alternatively, navigate to OpenText Vendor Invoice Management > SAP menu >
Roles > Role Maintenance.
To create a new role, follow the process described in “Defining Roles” on page 44,
with product code 005.
9.7 Configuring DP Process Options

In this step, you define the process options that a role gets to see on the DP
dashboard during the DP process. These options are available for use in any process
type configuration.
To configure DP process options:

Processing Configuration > Process Configuration > Maintain Process
Options.
VIM070500-03-CGD-EN-1
9.7. Configuring DP Process Options
2. Configure DP process options using the following parameters:
Option Id
Enter a 5 digit number identifying the process option.
Option Button Text
Enter the text that appears on the button for this option in the users’
dashboard.
Option Button Icon
Enter the icon that appears on the button for this option in the users’
dashboard. If you maintain an icon, the Option Button Text is not used.
Option Text
Enter a description that describes the option in detail.
Option Type
Select the type of option:
BDC Action
A BDC ID is executed if the user chooses this option.
Note: If you select BDC Action you have to maintain the BDC
Configuration Id.
Referral
User can refer the work item to a target role for further processing.
Note: If the Override Res. Actor check box is selected, the user
has an option to send the work item to users other than the ones
determined by the system for the target role.
VIM070500-03-CGD-EN-1
Class Method
At this point, this is not supported.
Call Transaction
The system calls the transaction that is defined in the Transaction Code
field.
Note: If you select Call Transaction you have to maintain the

Transaction Code field.
Workflow Task
The system calls a (sub) workflow or task before continuing the process.
Select Workflow Task to define any custom post processing steps for a
given option.
Auto Action Required

Select this check box to let the system try to post the document (create SAP
document) in background. The transaction that is called for posting
depends on the process type configuration.
Recheck Proc Type

Select this check box to let the system try to run the business rules as
defined.
Confirm Check Rules

Select this check box to let the system try to get a confirmation from the user
to rerun the business rules.
Confirm Execute
Select this check box to let the system get a confirmation from the user to
execute the option.
Confirm Completion
Select this check box to let the system get a confirmation from the user that
the option is successfully executed.
Display Index Data

Select this check box to let the system display indexing data of the DP in a
separate window while executing this process option.
Note: After Display Index Data is selected for a certain Process

Option, the feature is applied to all Document Types.
Comments Required
Select this check box if a comment is required for the action executed. The
comment will be shown in the process log.
Document Status
Select the status set for the document if the option is executed successfully.
VIM070500-03-CGD-EN-1
9.7.1 Using the BDC ID Infrastructure

In VIM, many processes base on configuring the system to perform a sequence of
operations. This concept is implemented by configuring a BDC ID, a very flexible
infrastructure that allows to:
• execute a transaction code without any configuration
• execute a transaction code pre-populating process data without having to code
how the data is read
• configure a custom function module to be executed to achieve the process option
The substeps in the definition of a BDC ID are the following:

• “Defining a BDC ID” on page 207
• “Defining Parameters” on page 210
• “Defining Transaction Data” on page 212
• “Defining Success Messages” on page 215
9.7.1.1 Defining a BDC ID

To define a BDC ID:

Processing Configuration > Process Configuration > Maintain BDC
Procedures.
2. In the BDC Definition Overview screen, double-click a BDC configuration Id.
VIM070500-03-CGD-EN-1
3. Define the BDC ID, using the following parameters:
Note: If the Custom BDC Function at the bottom of the screen is

maintained, the system ignores all other BDC Definition settings.
Description
Enter a meaningful description for the action.
Transaction Code
Enter the related SAP transaction code.
Data Area
Enter Indexing for DP
Processing Mode
Select settings for processing:
Display all screens

Use this option to display all screens.
Display errors
BDC mode E: Stops at Error screen.
Background processing
BDC Mode N: Use this option for background processes.
VIM070500-03-CGD-EN-1
Background processing; debugging possible

Not used
Update
Select the Update mode to call transaction. Possible values: Local,
Synchronous, or Asynchronous.
CATT Mode
Select the CATT mode. The following values are possible:
No CATT
’ ’ No CATT active
CATT without individual screen control

‘N’ CATT without single-screen control
CATT with individual screen control

‘A’ CATT with single-screen control (can be selected for running in
MIRO in background)
Default Size
Select this check box to use the default window size.
Continue after Commit

Select this check box to specify that the transaction does not end at COMMIT
WORK.
Not a BI Session
Select this check box to specify no batch input mode, that is, SY-BINPT =
SPACE.
End: No BI
Select this check box to specify no batch input mode after the end of BDC
data.
Custom BDC Function

Maintain the custom BDC function, and the system will ignore all settings
in the BDC Definition Details screen. Figure 9-2 on page 210 shows the
function module interface.
Exceptions
• You must specify the processing mode that you are using in your
customer function.
• You must specify the transaction FV60 as Transaction code, if you are
calling a transaction to park Non PO invoices in your custom module,
and if you want the parking workflow for the Non PO invoices dialog to
be triggered.
VIM070500-03-CGD-EN-1
Figure 9-2: BDC ID function module interface
9.7.1.2 Defining Parameters

In this section, you define the parameter ids that are set before calling a BDC
transaction.
To define parameters:
1. In the BDC Definition Details screen, double-click Parameters in the
navigation pane.
2. Define the following parameters:
SPA/GPA
Parameter Id (Check definition with SAP Documentation)
Value Det. Type
Function module
Figure 9-3 on page 211 shows example and interface.
VIM070500-03-CGD-EN-1
Figure 9-3: Parameter function module interface
As the data head is structure, it is not specified. Use field symbol to pass
it on to the respective structure.
You can use the function module parameter ID also as exit before
calling BDC transaction.
Create a dummy parameter ID and use the custom function module for
any processing that needs to be done before BDC call.
Application Variable
Application Variable is used to reference index field values.
System Field
System Field is used to reference system fields.
Default Value
Default Value is used to set default values as parameters.
Class Method
Currently not implemented.
VIM070500-03-CGD-EN-1
9.7.1.3 Defining Transaction Data

In this section, you define the transaction data that is passed to various screens when
the transaction is called.
To define transaction data:
1. In the BDC Definition Details screen, double-click Transaction Data in the

navigation pane.
2. In the Transaction Data Overview screen, double-click an Index ID on the very

left of the table.
3. Define the transaction data, using the following parameters:
Index ID
Sequence step number for the BDC data table
Program
Enter the name of the program.
Screen number
Enter the screen number.
Start Screen
Select the check box to indicate a new screen.
Line Number for Item

Enter the line number for the table control line item. Normally blank.
BDC Field Name

Enter the BDC field name.
VIM070500-03-CGD-EN-1
BDC Field Value

Enter the actual value, based on the Value type.
Value Det. Type

The Value Determination Type settings are similar to the settings in
“Defining Parameters” on page 210.
Function Module
The BDC field value can be retrieved dynamically based on a function
module.
Figure 9-4: Transaction data function module interface
Note: BDC infrastructure is used in multiple areas of VIM, so

DATA_HEAD declares the BDC field as field symbol and passes on
the correct structure. Figure 9-4 on page 213 is an example for DP
usage.
VIM070500-03-CGD-EN-1
The value of the table field from table /opt/vim_1head can be used in
the application variable. If you choose Application Variable, enter
the field name from table /opt/vim_1head into the BDC field value
table.
System Field (SYST)

To pass any system variable like date and time, choose field value type
System Field and enter the system variable into the BDC field value.
Default Value (Constant)

To pass on constant values like BDC_OKCODE, use the Constant Value
field type. Enter the value without quotation marks.
Class Method
Currently not implemented.
BDC Extension Function Module

You can use this option to add a screen field to BDC Data structure
based on special logic, for example country specific screen fields. When
you use this option, enter the following values and leave the remaining
fields empty. See the following screenshot.
Program
EXTENSION
VIM070500-03-CGD-EN-1
BDC Field Value

Function module name
The function module interface must be like the one shown in the
following screenshot. Append the BDC field information to the table
BDCDATA for each field.
9.7.1.4 Defining Success Messages

In this step, you define the success messages issued by the system to indicate the
successful completion of the process.
If success messages are maintained, the system checks for the messages at the end of
the transaction, and if they match any other messages returned from BDC, the
system treats it as transaction completed.
To define success messages:
1. In the BDC definition screen, select a BDC Configuration Id and double-click

Success Messages in the navigation pane.
2. Define success messages using the following parameters:
Index
Sequential line item number
Application Area
Select the message class.
Message ID
Select the message number.
VIM070500-03-CGD-EN-1
The success message is not required for all transactions. In a few cases, like MIRO and
FV60 transactions, the transaction itself exports a Process_key-complete flag to
memory ID name as work item ID, and then the system also treats the transaction as
completed.
The following is the example code for exporting a document creation flag in case of
MIRO and FV60 transactions.
DATA l_objkey TYPE swotobjid-objkey.

CALL FUNCTION 'GET_WORKFLOW_ID'
IMPORTING
workitemid = l_objkey
EXCEPTIONS
not_found = 1
OTHERS = 2.
CHECK: sy-subrc EQ 0, l_objkey NE space.
IMPORT process_key TO l_prockey FROM MEMORY ID l_objkey.
CHECK sy-subrc EQ 0.
l_prockey-bus_objtype = 'BUS2081'.
l_prockey-bus_objkey = l_rbkp+3(14).
l_prockey-complete = 'X'.
EXPORT process_key FROM l_prockey TO MEMORY ID l_objkey.
The following screenshot shows the structure to be implemented for /

OPT/PROCESS_KEY.
VIM070500-03-CGD-EN-1
9.7.2 Changing BAPI Configuration

If you need to change the configuration for a certain BAPI® and configure a plug-in
custom function module in BAPI, perform the following steps.
To change the BAPI configuration:

Procedures. See also “Defining a BDC ID” on page 207.
2. Double-click BDC Configuration Id 6.
3. Replace the existing BAPI with custom BAPI compatible to interface /

OPT/VIM_52_BAPI_DOCLINES_PO.
4. Return to the BDC Definition Overview screen, and double-click BDC

Configuration Id 11.
5. Replace the existing BAPI with custom BAPI compatible to interface /

OPT/VIM_52_BAPI_PO_PARK.
You might not want to entirely overwrite the BAPIs with custom BAPIs as described
above. The other way to allow some custom modifications is to use a custom plug-in
function module.
To configure a plug-in custom function module in BAPI:

> Automated Line Processing > PO Line Determination > Maintain PO
Invoice Lines Related Constants.
2. Double-click CUSTOM_FM_PLUGIN.
VIM070500-03-CGD-EN-1
This Z constant allows you to plug in your own function module, in order to
enhance the functionality lines for posting or parking via BAPI. This plug-in
custom function is called within /OPT/VIM_52_BAPI_DOCLINES_PO and /
OPT/VIM_52_BAPI_PO_PARK, just before creating the SAP documents.
3. In Constant Value, enter the name of your custom function module.

The interface of the custom function should look like the following:
EXPORTING
index_header = index_header
TABLES
index_item = index_item
itemdata = lt_bitem
accountingdata = lt_accountingdata
glaccountdata = lt_glaccountdata
materialdata = lt_materialdata
taxdata = l_tax
withtaxdata = lt_withtax "Witholding Tax
vendoritemsplitdata = lt_vendoritemsplit
CHANGING
headerdata = l_bhead
addressdata = ls_addressdata.
The BAPI function to park a PO invoice (/OPT/VIM_52_BAPI_PO_PARK) terminates

processing with an error if no line items are delivered or the line items could not be
matched completely with the SAP proposal.
If the exit function (constant 005 / CUSTOM_FM_PLUGIN) is maintained, the processing

within the function module continues. Within the exit, additional coding can be
executed to park the document correctly.
For the posting BAPI (/OPT/VIM_52_BAPI_DOCLINES_PO), the same functionality

exists for not completed lines according to the SAP proposal.
9.8 Invoice Processing Plug-ins

Invoice processing plug-ins comprise the following:
• Business Add-Ins (BAdI)
• Business transaction events (BTEs).
VIM070500-03-CGD-EN-1
9.8. Invoice Processing Plug-ins
9.8.1 Activating BAdI for Invoice Processing

For PO based invoices (transaction MIRO), Business Add-Ins (BAdI) determine
document completion. The corresponding VIM BAdI exports the Process_Key-
complete flag and also object type and object key.
In this step, you need to verify that the BAdI used for PO based invoice processing is
active. This is important to successfully terminate the document processing
workflow and start PO parked/blocked workflow (if required).
Usage:
• When a PO document is parked, the VIM BAdI triggers an OpenText process to
capture the reason for parking the invoice which triggers the OpenText PO
parked invoice workflow process.
• When a PO document is posted and the PO document is blocked for any reason,
the VIM BAdI triggers the PO blocked invoice workflow process.
To verify BAdI PO park invoice exit:
• Run the SE19 transaction and check the BAdI /OPT/VIM_MIRO_ENH.
The BAdI implementation has to be available and active on the system.

Runtime Behavior must be Implementation is called.
VIM070500-03-CGD-EN-1
There is a second implementation for this BAdI called /OPT/VIM_ENH_SPOT_MIRO.

This implementation is integrated into the Switch Framework, Business Function
Set /OPT/VIM_BFS, Business Function /OPT/VIM_SFW_MIRO, Switch /
OPT/VIM_SWITCH.
Make sure that only one implementation for this BAdI is called. Therefore use the
SE19 transaction to check that the runtime behavior of BAdI /
OPT/VIM_ENH_SPOT_MIRO is Implementation is not called. To prevent activation
of this second BAdi, leave the Planned Status for Business Function /
OPT/VIM_SFW_MIRO empty (in the SFW5 transaction).
To activate the BAdI implementation in the switch framework:
1. Deactivate BAdI /OPT/VIM_MIRO_ENH using the SE19 transaction.
2. Use the SFW5 transaction to set the planned status of business function /
OPT/VIM_SFW_MIRO to “active” and activate the change.
Note: You find the business function under ENTERPRISE EXTENSIONS.
You can check if the activation was successful in SFW5 (bulb is lit) or in
SFW_BROWSER (“Switch position” of business function /OPT/VIM_SFW_MIRO is
green.)
3. Use the SE19 transaction to make sure that runtime behavior of BadI /
OPT/VIM_ENH_SPOT_MIRO is Implementation is called.
VIM070500-03-CGD-EN-1
9.8. Invoice Processing Plug-ins
9.8.2 Activating BTEs for FI Invoice Processing

In this step, you define BTEs (Business Transaction Events in FI invoice processing)
that are delivered with VIM. These BTEs are required to trigger the OpenText Non
PO Parked Invoice Process. For more information on how BTEs work, refer to the
SAP documentation on BTEs.
To verify the BTE Non PO park invoice exit:
1. Run the FIBF transaction.

On the Settings menu, point to Products > of a partner, and click Activate.
The /OPT/VIM product must be active.
2. On the Settings menu, point to P/S Modules, and click of a partner.

The following entries must be available.
New BTE processing for document parking - The parked processing within BTE
2213 has been enhanced and supports the following scenarios:
• NPO parking using enjoy transactions: uses BTE 2213 and BTE 1140
• NPO parking using classic transactions: uses BTE 1020 and BTE 2213
• NPO BDC scenario: uses BTE 2213 and modification in function module /
OPT/VIM_CALL_IDX_TRANSACTION
VIM070500-03-CGD-EN-1
9.9 Extending Document Data

It is possible that OpenText delivered data-fields are not sufficient for business
requirements. In that case, enhance the following structures to capture additional
data.
Note: The maximum length of an enhancement field is 255 characters.
/OPT/VIM_1RDOC_DATA
This structure is used to capture data that is document specific and not process
specific. If a field is applicable for both POs and Non POs, maintain the field
here. An example for that field is the company code which can be for POs and
also for Non POs.
/OPT/VIM_4RAPP_DATA
This structure is used to capture data that is specific for Non PO approvals. If a
field is applicable to Non PO approvals, maintain the field here.
/OPT/VIM_BL_1RIDX_DATA
This structure is used to capture index data which may or may not be used in
subsequent processes. If you want to create a field that is specific to index
documents, extend this structure.
Prerequisites for extending document data

• Developer authorization
• Knowledge of SAP database tables and structures
To extend document data:
1. Run the SE11 transaction.
2. Display the corresponding structure, see above.
3. Click Append Structure.
4. Maintain the Append Structure definition and fields.
5. Activate your settings.
VIM070500-03-CGD-EN-1
9.10. Mapping External System Data (OCR/IDoc)
9.10 Mapping External System Data (OCR/IDoc)

In this step, you map external data to document fields in Document Processing (DP).
If you have defined any fields in “Extending Document Data” on page 222, these
fields show up during the mapping.
Note: This step is only required when external data is sent to SAP ERP using
an OCR interface.
Prerequisites
• Document entry by OCR required
• Document data structures extended as described in “Extending Document Data”
on page 222 (optional)
To map external system data:
2. Create entries to map external data fields to index document fields.
External field
The value in this field is case sensitive.
Field type
Select Header or Item.
Document Field Name

Select the field in document data that will be mapped to.
VIM070500-03-CGD-EN-1
Function for Conversion

If there is any necessity to convert the format of the data coming from the
external system, enter a conversion function module. Any function module
that you enter here, whether SAP standard or a custom one, should be
compatible with the interface of function module
CONVERSION_EXIT_ALPHA_INPUT.
9.10.1 Configuring Line Item Fields for External System Data

Note: If you only use Baseline DP document types and Baseline fields for the
DP document types, you can skip this section.
You might want to add line item fields to the indexing screen for DP document
types, for example to map certain fields from external system input like OCR. In this
case, you must perform the following configuration for these fields to allow them
getting values from the external system. Fields that are not configured here will
remain blank even if data is exported from the external system.
Tip: You can also use this configuration to define how any line item field is
displayed on the indexing screen.
To configure DP line item fields:
1. Every line represents one line item field of a DP document type, indicated by
the Field Name. The table comprises all line item fields of all DP document
types. See also “Configuring the Index Item Fields” on page 151.
2. Configure the fields in the Field Stat column, using the following parameters:
Input
Users can enter values on the indexing screen.
Required
Users must enter values. The field is marked as mandatory.
Hide
The field does not appear on the indexing screen.
Note: If you want to import and store data from an external system
but you do not want to show them in the indexing screen, you can use
this setting.
Display Only
The field appears on the indexing screen, but the user cannot enter values.
VIM070500-03-CGD-EN-1
9.11. Configuring the Process Type
9.11 Configuring the Process Type

A process type in the VIM DP process is used by the system to determine if the
process type is an exception, and to define the initial role that gets the work item.
The user process options for each role define the options on the dashboard for each
role.
9.11.1 Defining the Process Type

To define the process type:
1. Run the /n/OPT/VIM_8CX1 transaction.

Processing Configuration > Process Configuration > Maintain Process Types.
2. To display the Process Type Definition Details screen, double-click a Process
Type line.
VIM070500-03-CGD-EN-1
3. Define the process types using the following parameters:

Basic Configuration
Process Type Number

3 digit unique number identifying the process type.
Process Type
Description of the process type.
Initial Role
Select the initial role that gets the work item.
Initial Actor FM
Select a custom function module to determine the initial role. The system
first checks if there is an initial actor. If there is no initial actor, the system
tries to get the initial actor from the function module.
Is Exception
Select this check box to mark the process type as exception. If this check box
is selected, the process type is not relevant for automatic background
document posting.
Characteristic Check
Relevant for characteristic specific configuration, for the following kinds of
process types:
• Process types that are specific to a single characteristic or multiple

characteristics
• Process types that need to be checked for specific invoice categories in
specific characteristics only
• Custom process types that need to be executed only for certain invoice
categories of a characteristic
Select this check box for these process types.

This check box tells the VIM system to check the characteristics
configurations also before the check defined in the process types is executed
on the invoice.
Baseline configuration provides the check box as selected for the baseline
process types that need additional checks to be performed for the
characteristic configuration.
Note: For the characteristic specific configuration, see “Characteristic

Specific Process Types” on page 477.
Create SR
Relevant for the SAP Shared Service Framework integration. This field is
only available if VIM is integrated with SAP CRM SAP Shared Service
Framework. See “SAP Shared Service Framework Integration“ on page 697.
VIM070500-03-CGD-EN-1
Select this check box to configure that an automatic Service Request is

created in background when this process type is triggered.
Wait / Rerun Settings

The Wait / Rerun option can be used to automatically retrigger rules after a
period of time by the system.
Example: This helps when the system should check that a goods receipt is available
before the process continues without interaction of the user, when the invoice arrives
before the goods receipt is posted.
To rerun process types correctly in background, you must plan a batch job for a
report; see section 5.1 “Scheduling Batch Jobs for Workflows” in OpenText
Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-AGD).
You can also rerun the waiting process types in dialog using the /
OPT/DR_BR_WAIT report or the /OPT/VIM_RULERUN transaction. See also
“Rerunning Waiting Process Types“ on page 807.
Wait / Rerun
With this option, it is possible to send any exception of a business rule into a
wait state. Depending on the selected option, it is possible or not possible to
process the work item:
Background processing only
The work item is sent to the background user (WF-BATCH).
Workitem processing possible
The work item is in a wait state but it can be processed by the user
specified in Wait Role.
Interval (hours)
The interval defines the time in hours after which the business rule is
skipped or placed in the initial actor's inbox if no other action happened.
You can control this using the exclusive indicator; see “Defining the Process
Type Determination Sequence” on page 143). The rule will be skipped if the
exclusive indicator is not set, or the process will stop and the initial actor
has to resolve the process type manually.
Wait Role
Only necessary if the Wait / Rerun option is set to Workitem processing
possible. The specified role gets the work item that is sent into the wait
state. The specified role is able to process the work item.
Workflow Settings
Workflow Type
Select Opentext Approval Workflow from the drop down list to start the
DP based approval workflow. With Opentext Approval Workflow selected,
it is possible to select or clear the Auto Start check box, as the case may be.
Select External Workflow from the drop down list to run any external
workflow (based on SAP technology) outside SAP IM workflows as a part
VIM070500-03-CGD-EN-1
of any business rule. With External Workflow selected, the Auto Start
option is always enabled.
Select SRM System Integration from the drop down list for SRM scenarios
or any other external systems where an email will be sent and the workflow
will be in wait status. See “SRM Integration“ on page 749.
Auto Start
Relevant for DP based approval workflow. If the process type
corresponding to the approval workflow is determined, the system checks
whether the Auto Start check box is enabled. If yes, the system starts the
approval workflow if it is enabled. If Auto Start is not enabled, processing
continues with the initial actor assigned to the current process type. The
initial actor will manually start the approval workflow.
Task
Enter the workflow template to be triggered. The workflow template
container can be of any interface as the binding is controlled by a custom
binding function module.
Binding Function
Enter the Workflow Binding function module.
It must be implemented in the system where the SAP IM workflow is
running, to pass appropriate data to the external workflow. The function
module should have an interface as /OPT/VIM_DASHBOARD_BINDING. Inside
the custom function, in this case, implement Dataflow = E (Inward
Binding). You can access the complete container elements of the DP
workflow from the table parameter CALLING_CONTAINER. Regarding how
actual to implement the binding function, you can refer /
OPT/VIM_DASHBOARD_BINDING.
As a simple implementation, element INDEXDOCUMENT can be accessed from
the container CALLING_CONTAINER. DP (Document Processing number) can
be retrieved and other indexing information can be extracted and passed to
the elements of the CALLED_CONTAINER container, which is the container of
the external workflow. The external workflow must also raise the event /
OPT/V1001.PSS_COMPLETED at the end in the system where the SAP IM
workflow runs so that the SAP IM workflow proceeds further.
Example 9-2: Sample code for the Workflow Binding function

module
FUNCTION Z_SHV_BINDING.
*"-----------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(DATAFLOW) LIKE SWABINDEF-DATAFLOW
*" TABLES
*" CALLED_CONTAINER STRUCTURE SWCONT
*" CALLING_CONTAINER STRUCTURE SWCONT
*"-----------------------------------------------------------
include <cntn01>.
DATA : lcl_indexer TYPE REF TO /opt/cl_vim_doc_processor,

l_curr_role type SWCONT-VALUE.
data : l_head type /opt/vim_1head,
VIM070500-03-CGD-EN-1
lo_v1001 TYPE swc_object,

l_objkey TYPE swotobjid-objkey,
l_docid TYPE /opt/docid,
l_bus2012 TYPE swc_object.
IF DATAFLOW = 'E'. " Task Container <== Workflow Container

" Called_Container -- Calling_container
****************************************************************
* The binding is as follows
* External Workflow Container <=== VIM Workflow Container
* ===================== <=== =======================
****************************************************************
* Convert the Calling Container to Persistent
SWC_CONTAINER_TO_RUNTIME CALLING_CONTAINER.
swc_get_element calling_container:
'IndexDocument' lo_v1001 .
swc_get_object_key lo_v1001 l_objkey.

l_docid = l_objkey.
select single * into l_head from /opt/vim_1head

where docid = l_docid.
swc_set_element called_container: 'HEAD' l_head.

swc_create_object l_bus2012 'BUS2012' l_head-ebeln.
swc_set_element called_container: 'PurchaseOrder' l_bus2012.
SWC_CONTAINER_TO_RUNTIME called_container.
SWC_CONTAINER_TO_PERSISTENT called_container.
ELSEIF DATAFLOW = 'I'. " Task Container ==> Workflow Container

" Called_Container -- Calling_container
****************************************************************
* The binding is as follows
* External Workflow Container ===> VIM Workflow Container
* ===================== =======================
****************************************************************
* Convert the Called Container to Persistent
SWC_CONTAINER_TO_RUNTIME CALLED_CONTAINER.
SWC_CONTAINER_TO_RUNTIME CALLING_CONTAINER.
ENDIF.
ENDFUNCTION.
Logical System
Enter the name of the system where the external workflow is supposed to
run. The external workflow should be based on SAP technology.
SRM Settings
Max Retry Counter, Retry Time (Minutes), Mail Config ID, Receiver Mail
Function, Send Mail Function
These fields are only relevant for the SRM integration. See “Missing Goods
Receipt Scenario” on page 754.
VIM070500-03-CGD-EN-1
9.11.2 Defining User Process Options

In this step, you define process options for each role. Process options are associated
with the process type.
To define user process options:
1. In the Process Type Definition Overview screen, select a process type and
double-click User Process Option in the navigation pane.
2. Define process options, using the following parameters:
Option Id
Process option identifier
Description
Description of the option
From Actor
Select the source role that gets the work item.
To Actor
Select the target role that receives the work item if the action is performed.
This is only available if the option is a referral.
Check FM
Enter a check function module to restrict the option for a role. You find the
interface for the check function module using /
OPT/VIM_BL_CHECK_FM_2012.
Sequence
Optional setting: Enter the sequence of the process options shown in the
dashboard.
VIM070500-03-CGD-EN-1
9.12. Configuring Indexing Line Matching
9.12 Configuring Indexing Line Matching

This section provides information about how to configure the matching of indexing
lines. To implement the derivation of indexing lines, you need to perform the
following configurations.
• “Configuring Indexing Line Matching from OCR Results” on page 231
• “Setting Up the Derivation Infrastructure” on page 233
• “Enhancing MIRO for Pre-population of Data During Online Invoice Creation”
on page 236
• “Implementation Considerations” on page 240
9.12.1 Configuring Indexing Line Matching from OCR Results

OCR can provide all purchase orders and all delivery notes that are found in one
invoice on header level.
Old VIM With VIM 7.0 and lower, the business rule Unable to Determine PO Line no was
approach used to derive PO item numbers for the indexing lines. As an extension for the
feature of line determination for invoicing, VIM provides a business rule Manual
Check Needed for indexing lines. The former rule Unable to Determine PO Line
no stays valid as it complements the line determination.
New VIM In VIM 7.5 and higher, the old approach is replaced with a combination of a logic
approach module and a business rule.
The combination of logic module Line based processing / enrichment /

matching (PO) and business rule Manual Check needed / Missing data for
indexing lines allows deriving all billable lines that are based on purchase orders
or delivery notes at header level. The automatic derivation runs as a background
process in the following cases:
• OCR did not supply any line items.
• OCR supplied incomplete line items.
Line items whose mandatory fields are empty are treated as incomplete.
OCR lines
• If no OCR lines are supplied, the entire proposal that is based on reference
documents is used to form indexing lines, based either on PO orders in the
documents or on Delivery Notes, but not on both.
• If OCR lines are supplied, and all lines’ mandatory fields are filled, no business
exception occurs.
• If OCR lines are supplied, but some lines have empty mandatory fields, these
lines are considered as incomplete.
Incomplete OCR lines are checked if certain fields are complete. According to the
configuration, either the lines proposed by the MIRO transaction or the OCR
VIM070500-03-CGD-EN-1
supplied lines can then form the basis for indexing lines. See “Setting Up the
Derivation Infrastructure” on page 233.
Business exception
A business exception occurs under the following conditions:

• When a line is still considered incomplete due to missing mandatory fields.
• When the system automatically derives a line or a field value.
Completeness check for indexing lines
Indexing lines that contain Non GR-IV based PO line items have the following
mandatory fields:
• PO Number
• PO Item
• Quantity
• Amount
• UOM
Indexing lines that contain GR-IV based PO line items have the following
mandatory fields:
• PO Number
• PO Item
• Delivery Note /GR Reference Document
• Quantity
• Amount
• UOM
Once the system has determined that indexing lines are incomplete, the system
derives the missing mandatory fields based on the configuration described in
“Setting Up the Derivation Infrastructure” on page 233.
VIM070500-03-CGD-EN-1
9.12.2 Setting Up the Derivation Infrastructure

With VIM 7.5, the PO line derivation is processed in the logic module processing.
For more information, see “Processing Logic Modules” on page 180.
The old derivation infrastructure using business rules is still working but you
should not use it any more.
Process Type 110, business rule Manual Check Needed for Indexing Lines, used in
VIM versions prior to 7.5, is replaced with process type 113, business rule Manual
Check Needed / Missing Data for Indexing Lines (PO) with VIM 7.5 and higher.
This business rule has been created for PO data checking.
Conditions for logic module processing
1. Logic module /OPT/CL_D_LM_DETERM_PO_MAP must be available.
2. Process definition and related logic module must be available and active.
3. The process definition must be mapped and activated for the related document
type.
VIM070500-03-CGD-EN-1
To configure the business rule Manual Check Needed / Missing Data for
Indexing Lines (PO):
Document Types.
See also “Defining the Process Type Determination Sequence” on page 143.
2. At DP Document Type level, configure process type 113 Manual Check

Needed / Missing Data for Indexing Lines (PO).
3. Open the Sequence Steps screen for process type 113. See also “Defining
Sequence Steps” on page 144.
VIM070500-03-CGD-EN-1
4. Enter the Check Function /OPT/VIM_DETERMINE_PROC_108.

5. See also “Configuring Line Item Fields for External System Data” on page 224
and “Configuring the Index Item Fields” on page 151.
6. For the DP Document Type, configure the fields as highlighted in the

screenshot.
7. Configure document-type-specific settings. The PO Line Determination is based

on “Maintaining the PO Line Determination” on page 154.
VIM070500-03-CGD-EN-1
9.12.3 Enhancing MIRO for Pre-population of Data During

Online Invoice Creation
This covers the aspects related to online posting via the MIRO transaction via
Enhancement Points (for ECC 6.0 version). Currently, the line items from the
indexing dialog window are lost when a user executes online postings. Due to the
complexity of MIRO, normal BDC is not possible to pass lines from the indexing
screen. The following configurations are necessary:
To ensure that BDC Configuration ID 200 exists in the system:

Procedures. See also “Defining a BDC ID” on page 207.
2. Ensure that the BDC Configuration Id 200 PO Invoice Posting Online -

Special is listed. BDC Configuration Id 200 is used to run the MIRO
enhancement logic. BDC Configuration Id 200 refers to function /
OPT/VIM_PREPOPULATE_MIRO.
To configure the Z Constant entry for BDC Configuration Id 200:

> Automated Line Processing > PO Line Determination > Maintain PO
Invoice Lines Related Constants.
2. Double-click BDC_POSTING_ONLINE.
VIM070500-03-CGD-EN-1
BDC Configuration Id 200 is a special BDC Configuration Id which in turn calls

the standard BDC Configuration Id based on the Z constant
BDC_POSTING_ONLINE.
3. Enter the Constant Value 1.

Baseline uses 1 as the default value which is a normal BDC Configuration Id to
call the MIRO transaction for online posting.
Process option BDC Configuration Id 200 is a special BDC Configuration Id. It, therefore, needs to
be attached to a user process option, which in turn is called from the DP Dashboard.
Either create a new process option or change the existing process option for PO
invoice posting, as shown in the following procedure.
To configure the process option:

Options. See also “Configuring DP Process Options” on page 204.
2. Double-click the line with Option Id 2009 Post PO Invoice
VIM070500-03-CGD-EN-1
3. Enter the BDC Configuration Id 200 PO Invoice Posting Online - Special.

VIM Baseline delivers a special BDC Configuration Id 200 that is configured
within Option Id 2009 as part of the BC set. Option Id 2009 already exists, so
make sure to take a note of BDC Configuration Id 200, before you activate the
BC set for the indexing line matching.
User process You need to configure the user process option 2009 Post PO Invoice for process
option type 110 Manual Check Needed for Indexing Lines.
To configure the user process option:

Processing Configuration > Process Configuration > Maintain Process Types.
2. In the Process Type Definition Overview screen, select process type 110 Manual
Check Needed for Indexing Lines and double-click User Process Option in
the navigation pane. See also “Defining User Process Options” on page 230.
VIM070500-03-CGD-EN-1
3. Maintain process option 2009 Post PO Invoice for appropriate roles under
process type 110, as shown in the screenshot.
Enhancement The following functions need to be plugged in using implicit enhancements:

spots
Note: For each function, you must add the code at the end of forms, just before
the ENDFORM statement.
/OPT/VIM_BUILD_REFERENCE_DOCS
This function is used for passing the reference documents (include LMR1MF3S).
Call this function inside the subroutine ZUORDNUNGSKRITERIEN_AUFBAUEN.
/OPT/VIM_CHANGE_PROPOSAL_MIRO
This function is used to manipulate the lines from proposal (include LMR1MF3U).
Call this function inside the subroutine ZUORDNUNG_DURCHFUEHREN.
********BEGIN OF CODE PIECE**************************
data: vim type c.
VIM070500-03-CGD-EN-1
CALL FUNCTION '/OPT/VIM_CHANGE_PROPOSAL_MIRO'

EXPORTING
RBKPV = rbkpv
IMPORTING
VIM = vim
TABLES
DRSEG_CT = ydrseg
.
***********BEGIN OF ADDITIONAL MIRO CHECKS*******************
if VIM = 'X'.
loop at ydrseg.
CHECK Ydrseg-selkz NE space .
PERFORM menge_pruefen USING rbkpv

'X'
CHANGING ydrseg.
* -------- Bestellpreismenge prüfen ------------------------*

PERFORM bpmng_pruefen TABLES t_errprot
USING 'X'
'X'
rbkpv
CHANGING ydrseg.
* -------- Wert prüfen -------------------------------------*

PERFORM wert_pruefen TABLES t_errprot
USING rbkpv
space
CHANGING ydrseg.
modify ydrseg.
endloop.
endif.
***********END OF ADDITIONAL MIRO CHECKS***********************
********END OF CODE PIECE**************************
9.12.4 Implementation Considerations

The following notes are useful for implementing the indexing line matching from
OCR results:
Notes on the automatic derivation of invoicing lines - The automatic matching

works fine if maximum keys are supplied. This means, supplying PO/PO item ask
keys at least helps the system carrying out matches versus the proposed lines. Keys
include PO number, PO item number, and Delivery Note (if applicable for the
invoice) or Good Receipt (if applicable for the invoice).
Good Receipts If multiple Good Receipts (GRs) are not allowed for a particular item, the PO/PO
item combination is a good key for matching.
VIM070500-03-CGD-EN-1
9.13. Additional Process Configurations
If multiple GRs are allowed for a PO item, the delivery note or GR document needs
to be supplied to find a match.
Only applicable for VIM versions before 7.5: Sometimes, when a delivery note has
multiple GRs linked to it, the business rule 110 Manual Check Needed for Indexing
Lines will result in an exception, even if the delivery note is supplied. If this is the
case, you may need to explicitly supply a GR document.
If the delivery note and the GR document correspond at a 1:1 ratio, supplying the
delivery note along with the PO/PO item is sufficient for finding a match.
PO item You must determine a PO item number before you run the new business rule 110
numbers Manual Check Needed for Indexing Lines for better matching.
Service-based PO line items are not fully supported. If you use MO as the basis for
incomplete OCR lines or always derive lines from the SAP proposal, the service-
based PO line items can be determined. However, if a service-based PO line item is
supplied but incomplete (mandatory fields missing), it may not be possible to
determine missing fields correctly.
Only applicable for VIM versions before 7.5: The older business rule 109 Unable to
determine PO line no complements the new enhanced functionality. Business rule
109 Unable to determine PO line no is used to determine PO item numbers for a
particular indexing line only. If business rule 109 Unable to determine PO line no
derives PO item numbers automatically, the exception is not raised by the Baseline
configuration. The older rule for finding PO item numbers is set up by the
configuration in transaction /OPT/VIM_POL where you set up a PO line
determination ID and then associate this determination ID to the DP document type.
Notes on the MIRO enhancement to pass indexing lines from DP Dashboard - All
the lines from indexing that could be matched are manipulated with Indexing
Amount and Quantity and are highlighted when selected.
Lines that could not be matched stay unselected.
Matching is the key to pass Indexing Amount and Quantity.
Matching works the best when all key values are available for the indexing lines.
9.13 Additional Process Configurations

This section describes the following configurations:
• “Maintaining Rescan Reasons” on page 242

• “Maintaining Obsolete Reasons” on page 242
• “Maintaining Scan Locations” on page 243
• “Maintaining Document Priorities” on page 244
• “Maintaining Dynamic Columns” on page 244
VIM070500-03-CGD-EN-1
9.13.1 Maintaining Rescan Reasons

In this step, you maintain rescan reason codes for the document. The reason will be
used when the user chooses to send the document to rescan.
To maintain rescan reasons:

Processing Configuration > Process Configuration > Maintain Rescan
Reasons.
2. Maintain the rescan reasons using the following parameters:
Code
Rescan reason code.
Description
Description of the rescan reason.
Comm Required
If you select this check box, the user must maintain the comments to
proceed.
9.13.2 Maintaining Obsolete Reasons

In this step, you maintain reasons for setting an obsolete flag for a DP document so
that the process can complete without the creation of an SAP invoice. This reason
code will be used when a user chooses to set a document to “obsolete” status.
To maintain obsolete reasons:

Processing Configuration > Process Configuration > Maintain Obsolete
Reasons.
VIM070500-03-CGD-EN-1
2. Maintain the obsolete reasons using the following parameters:
Code
Obsolete reason code
Description
Description of the obsolete reason
Comm Required
If you select this check box, the user must maintain the comments to
proceed.
9.13.3 Maintaining Scan Locations

In this step, you maintain scan locations for document archiving.
To maintain scan locations:

Processing Configuration > Process Configuration > Maintain Scan Locations.
2. Maintain the scan locations using the following parameters:
VIM070500-03-CGD-EN-1
Scan Location
Scan location for archiving
Description
Scan location description
9.13.4 Maintaining Document Priorities

In this step, you define priorities for documents. With baseline delivery, no priorities
are defined. You can use priorities, for example, as a field in the indexing screen. In
VIM Workplace, you can use the Priority field to sort the result list.
To maintain document priorities:
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
Document Processing Configuration > Process Configuration > Maintain
Document Priorities.
2. In the Document Priority Definition Maintenance Overview screen, define

priorities using the following parameters.
Priority
Enter the priority number.
Description
Enter a description of the priority.
9.13.5 Maintaining Dynamic Columns

In this step, you define how the system determines values for dynamic columns in
the user's inbox during work item processing.
To maintain dynamic columns:

Configuration > Workflow Configuration > Maintain Dynamic Columns.
VIM070500-03-CGD-EN-1
2. Maintain the dynamic columns using the following parameters:
Column Header
Enter text to appear as column header in user's inbox.
Dynamic Col. Type

Define how the dynamic column value is determined. The following values
are possible:
VIM070500-03-CGD-EN-1
Table Field
Data will be populated from the /OPT/VIM_1HEAD table.
Container Expression
Data will be populated from container data from task TS9578003.
Custom Function
Data is derived using a custom function module. A sample interface can
be found from function module /OPT/BL_IF_SET_DYNAMIC_COLUMN.
Note: The change of the settings for dynamic columns in the DP workflow
results in automatic entry of the workflow container elements DYNAMICCOLUMNx
for the task TS00275278 in the table SWLVCUSTOM. All six columns are plain text
fields, and this can result into incorrect sorting for values containing numbers,
for example Invoice Amount. If you need VIM users to see and sort work items
using the Invoice Amount field, you must maintain one dynamic column
directly in the table SWLVCUSTOM (transaction SM30) with the container element
expression &_WI_OBJECT_ID.GROSSAMOUNT& (instead of automatically entered
&DYNAMICCOLUMNx&).
9.14 Configuring Global Parameters

Document Processing (DP) provides enhanced functionality. For this purpose, global
configuration parameters are used.
Important
Take care when you change the global configuration parameters. Changes
can affect the functionality of the process.
To configure global parameters:

Processing Configuration > General Configuration > Global Configuration.
2. The following list defines the usage of the constants:
GR_CHECK_EXIT
Usage
This constant defines the function that is called to check if the Goods
Receipt (GR) for the PO is already done.
This constant is only applicable for Brazil.
Default value
/OPT/VIM_BL_CHECK_GR_EXIT
VIM070500-03-CGD-EN-1
9.14. Configuring Global Parameters
GR_MOVEMENT_TYPE
Usage
This constant defines the movement type to be used when posting the
goods receipt (GR) document in background. It can either be a fixed
value or a function module name.
Default value
For a fixed value, just mention the movement type in the constant
value, for example: 101.
For a function module, use the format FM: <function_name>.
GR_POST_BAPI_EXIT
Usage
This user exit bases on a function module. The function module defined
in this constant is called by the standard program before the SAP BAPI
is called while posting the goods receipt (GR). You can use this user exit
to change values being passed to the BAPI.
Default value
None
The interface of the custom function module must be the same as /
OPT/DPPO_GR_BAPI_POST_EXIT.
DP_NPO_POSTING_EXIT
Usage
This user exit bases on a function module. The function module is called
before calling the non PO invoice posting BAPI
BAPI_ACC_DOCUMENT_POST in function module /
OPT/DNONPO_INVOICE_BAPI. You can use this user exit to modify the
baseline data in BAPI structures.
This constant is applicable for all countries.
Default value
None
The interface of the custom function module must be the same as /
OPT/DNONPO_INVOICE_BAPI_EXIT.
APP_DOCU_URL
Usage
The custom help URL for the DP dashboard. You can provide custom
help for users to look up processing steps they need to take when they
are processing the DP dashboard.
Default value
www.opentext.com
VIM070500-03-CGD-EN-1
IMG_DOCU_URL
Usage
The custom help URL for OpenText IMG. Do not change this constant.
Default value
www.opentext.com
MAIN_WF_TEMPLATE
Usage
The default workflow template that will be triggered for DP. Do not
change this value.
Default value
WS00275269
NUMBER_RANGE_OBJECT
Usage
The default number range object for DP is /OPT/DOCID. If you want to
define a custom number range object for document number ranges,
define the value of the number range object here.
Default value
None
Note: If you change this value, you will have to maintain the number
ranges for the documents separately. The OpenText delivered /
OPT/VIM_1CX6 transaction will not work in this case for maintaining
number ranges.
PREPROCESS_EXIT_FM
Usage
A custom function module can be used as a value for this constant to
change the document values (Index Data etc.) before the workflow
starts.
Default value
None
Interface
CALL FUNCTION <CONSTANT>
CHANGING
INDEXER = LCL_INDEXER TYPE REF TO /OPT/CL_VIM_DOC_PROCESSOR
REMINDER_USER_EXIT
Usage
This configuration value is used to maintain a custom function allowing
to format e-mail content when sending reminders to users holding
work items.
VIM070500-03-CGD-EN-1
Default value
/OPT/VIM_NOTIF_USER_EXIT_TEMP
Interface

EXPORTING
SEND_INFO STRUCTURE/OPT/VIM_S1_REMINDER_DISPLAY
TABLES
OUT_DATA STRUCTURE /OPT/VIM_S1_REMINDER_DISPLAY
FIELDS_CATALOG STRUCTURE LVC_S_FCAT
SORT_FIELDS STRUCTURE LVC_S_SORT
REM_MAIL_DOCTYPE
Usage
This configuration value determines the global format of email sent
from Reminder Notification, Approval Notification and SRM
Notification.
The notification emails can be sent in HTML format with readable
formatting and invoice data presented in the form of HTML tables. To
enable this functionality, you must set the constant 005 /
REM_MAIL_DOCTYPE to HTM. In the /OPT/VIM_8CX50 transaction, you
must configure the Email Type to be Internet Email.
Default value
RAW
REM_MAIL_FORMAT_FM
Usage
This configuration value determines the exit function module where the
customer can manipulate the email content before sending it out.
Default value
empty
SERVICE_ENTRY_BSART (obsolete)
Usage
The service entry document type. This configuration value was
formerly used in business rule 154 Service entry required.
SERVICE_ENTRY_BSTYP (obsolete)
Usage
Purchase document category for service entry. This configuration value
was formerly used in business rule 154 Service entry required.
WI_TEXT_FM
Usage
This configuration value is used to maintain a custom function that
allows formatting the work item text.
VIM070500-03-CGD-EN-1
Prerequisite
Knowledge about work item data
Default value
/OPT/BL_IF_DETERMINE_WI_TEXT
Interface

EXPORTING
VALUE(INDEX_DOCID) TYPE /OPT/DOCID
IMPORTING
REFERENCE(WI_TEXT) TYPE SWW_WITEXT
DP_DASHBOARD_TASKID
Usage
This configuration value is used to determine the dashboard task in DP.
The task should be compatible to task TS00275257.
Prerequisite
Knowledge about workflow tasks
Default value
TS00275257
Note: Do not change this value as a change affects the behavior of the
application.
DUP_CHECK_DELIMIT
Usage
This configuration value is used to determine which characters in the
document reference number are considered as delimiter to determine a
document as a duplicate.
Default value
/-
Example
If a document with reference number REF-1 should be considered as a
duplicate for REF, the delimiter that should be maintained is -.
LIST_WF_STATUSES
Usage
This configuration value is used to determine at which document
statuses the PO parked workflow should be triggered. The document
status in question is the SAP document status.
Possible values:
A: Parked workflow triggered by MIR7 function Save parked document
B: Parked workflow triggered by MIR7 function Save as completed
VIM070500-03-CGD-EN-1
9.15. Excluding Company Codes from Process Types
AB: Parked workflow triggered by MIR7 function Save as completed

and Save parked document
Default value
A
WFDOCTYPE - obsolete (no longer used)
Usage
This configuration value is used to determine for which SAP document
types the PO/Non PO workflow is triggered. This eliminates the
triggering of the workflow for unwanted document types. Separate the
values by comma.
Default value
KR,RE,KG
Example
If you want to trigger the workflow for GL documents (document type
AB) maintain value AB here.
WFTRGPLANT
Usage
This configuration value is used to determine for which plants the PO /
Non PO workflow is triggered. This eliminates the triggering of the
workflow for unwanted plants. If you want to consider all plants,
maintain the value * here.
Default value
*
Example
If you want to stop triggering the workflow for plant 0001, maintain all
plants different from 0001 here.
9.15 Excluding Company Codes from Process Types

In this step, you maintain process types that should not be executed for specific
company codes. This configuration overwrites any other process type configuration.
This configuration is independent from document types and characteristics.
To exclude company codes from process types:

Configuration > Process Configuration > Exclude Company Codes from
Process Types.
VIM070500-03-CGD-EN-1
2. Maintain company codes that should be excluded from process types, using the
Process Type
Enter the process type from which the company code should be excluded
Company Code From, Company Code To
Enter a company code or a company code range that should not execute the
mentioned process type.
Exclude
To activate the exclusion, select this check box.
9.16 Maintaining Additional Cost Handling

VIM provides a feature with regards to the handling of additional costs. It is possible
to handle costs like delivery costs, for example freight. ICC delivers as many
additional costs as possible (line items) based on customer defined keywords. You
must perform some customizing on VIM side, which is described in this section.
Delivery costs are costs that are invoiced for a delivery over and above the value of
the delivery itself. This includes freight charges, customs duty, packaging, material
surcharges, or other costs.
Delivery costs can accrue as line item related costs and as header related costs. There
is also a distinction between planned delivery costs and unplanned delivery costs.
Planned delivery costs

Planned delivery costs are entered in the purchase order as line items. Planned
delivery costs are agreed upon with the vendor, a carrier, or a customs office
before the purchase order is created. They are entered in the purchase order in
the item conditions folders with a certain condition type.
The following differentiation applies:
Costs origin
• Freight charges
• Customs charges
Costs calculation
• Fixed amount, regardless of the delivered quantity
VIM070500-03-CGD-EN-1
9.16. Maintaining Additional Cost Handling
• Amount depending on quantity

• Percentage of the goods’ value
Unplanned delivery costs

Unplanned delivery costs were not agreed on in the purchase order and are not
entered until the invoice is received.
ICC extracts and classifies additional costs from the invoice based on customer
specific keywords. It delivers a separate line for each cost object found. The cost
type, for example freight or packaging, that is delivered within the line is called
“qualifier”.
You can customize VIM to use ICC line item data by setting the PO line
determination setting to OK; see “Maintaining the PO Line Determination”
on page 154. VIM checks whether planned costs of this cost type(s) exist for the
purchase order(s) involved and tries to match the cost amount(s) to the planned cost
amount(s). If the PO line determination setting is not OK, additional cost handling
will not work.
A successfully matched line will be shown with PO details and condition type.
Mismatched cost lines will be handled according to the customizing. For the
available alternatives, see “Maintaining the Handling of Unplanned Costs”
on page 258.
Planned delivery costs are shown on the PO Reference tab of the indexing screen
line item section. They can be recognized by the filled Condition Type. Unplanned
delivery costs are either shown on header level or on the G/L account tab of the
indexing screen line item section. If they are on item level they will show the
qualifier name and the alternative A4 or A5.
Manual or automatic parking or posting of the VIM document covers additional

costs. The respective amounts can be found in the SAP document.
9.16.1 Maintaining Additional Cost Qualifiers

In this step, you maintain qualifier names that ICC delivers to VIM.
To maintain additional cost qualifiers:

Configuration > General Configuration > Incoming Document Processing >
Maintain Handling of Additional Costs > Additional Cost Qualifiers -
Definition.
2. In the Customizing table qualifier texts screen, maintain the qualifiers, for
example FREIGHT or PACKAGING, using the following parameters:
• Description
• Short Description
VIM070500-03-CGD-EN-1
9.16.2 Specifying Additional Cost Qualifiers as Discount

In this step, you specify which qualifier delivered from ICC is a discount and not
additional cost.
To specify additional cost qualifiers as discount:

Maintain Handling of Additional Costs > Additional Costs Qualifiers -
Assign Discount Flag.
2. In the Maintenance View for Qualifier Discount Flag, specify the qualifiers
that are discount, using the following parameters:
• Discount Flag
• Additional Costs
9.16.3 Mapping Additional Cost Qualifiers to Condition Types

In this step, you maintain which qualifier (coming from ICC) is mapped to which
condition types for planned delivery cost in SAP ERP.
A SAP condition type represents some aspect of a company's daily pricing activities.
A different condition type can be defined for each kind of price, discount, or
surcharge that occurs in business transactions.
Example: ZOB1 represents value based customs surcharges.
To map additional cost qualifiers to condition types:

Maintain Handling of Additional Costs > Planned Costs - Mapping of
Qualifiers to Condition Types.
2. In the Customizing table for Conditions, maintain the mapping of Additional

Costs to CTyp (condition types), depending on Company Code and Vendor.
If you leave Company Code or Vendor empty, the settings are used for all
company codes or all vendors.
VIM070500-03-CGD-EN-1
9.16.4 Maintaining Fields for Handling the Determination of

Easymatch
In this step, you maintain the header fields that determine the handling of planned
costs.
Easymatch is a flag for the comparison of extracted line item data with planned
delivery cost in the purchase order. If Easymatch is set, only the cost amount is
compared. If it is not set, the amount is compared in addition with purchase order
number and item.
To maintain fields for handling the determination of Easymatch

Maintain Handling of Additional Costs > Planned Costs - Handling
Determination of Easymatch - Fields.
2. In the Maintenance View for Additional Cost Handling, maintain the fields,
using the following parameters:
Note: You must enter all relevant header fields.
Determination Type
Enter the determination type. For additional planned cost handling, enter
ACP.
Field Type
Select Header from the list.
Field Name
Enter the field name. Click for a list of available fields.
Sequence
Define the sequence for the header.
Easymatch should have the highest number in the list.
Search Help Name

Enter the search help name for the field.
VIM070500-03-CGD-EN-1
Allow Ranges
Select this check box to allow ranges. Ranges are used in handling the
alternative determination.
9.16.5 Maintaining the Handling of Planned Cost (Easymatch)

In this step, you maintain document header data restrictions for planned delivery
cost according to Easymatch. Maintenance is based on header attributes like
company code, vendor, and total amount.
To maintain planned cost handling (Easymatch):

Maintain Handling of Additional Costs > Planned Costs - Handling
Determination of Easymatch - Data.
2. In the Handling of Additional Planned Costs screen, maintain the Easymatch

flag, using header field parameters as defined in “Maintaining Fields for
Handling the Determination of Easymatch” on page 255.
Company Code, Vendor

Enter values to restrict the alternatives.
Note: Do not apply too tight restrictions for the case that ICC does not
fill the appropriate data.
Easymatch
If you set this flag, only the cost amount is compared.
If you do not set this flag, the amount is compared in addition with
purchase order number and item.
VIM070500-03-CGD-EN-1
9.16.6 Maintaining Fields for Handling Determination and Auto

Coding
In this step, you maintain the header fields that determine the handling alternative
for unplanned costs and item fields for auto-coding (valid for Alternative 4 and 5).
For information about the alternatives, see “Maintaining the Handling of Unplanned
Costs” on page 258.
To maintain fields for handling alternatives and auto coding:

Maintain Handling of Additional Costs > Unplanned Costs - Handling
Determination and Auto Coding - Fields.
2. In the Maintenance View for Additional Cost Handling screen, maintain the
fields, using the following parameters:
Note: You must enter all relevant header fields.
Determination Type
Enter the determination type. For additional cost handling, enter ACS.
Field Type
Select Header or Item from the list.
Item fields are used for auto-coding of alternative 4 and alternative 5 G/L
lines.
The following item fields are allowed:
• HKONT
• KOSTL
• KSTRG
• PRCTR
• PROJK
VIM070500-03-CGD-EN-1
• AUFNR
• NPLNR
• GSBER
• LSTAR
• VORNR
• ZUONR
• VBELN
• VBELP
• PAOBJNR
• GEBER
• FISTL
Field Name
Enter the field name. You can select the field from the available field list.
If you want to use auto-coding for GL lines (alternative 4 and 5), you must
enter item coding fields like HKONT or KOSTL.
Sequence
Define the sequence for header and item fields.
ALTERNATIVE must be the first header field with sequence 1.
QUALIFIER must be sequence 2.
DISTR_TYPE must be sequence 3.
HEADER fields must be sequence 4 to x.
Search Help Name

Enter the search help name for the field.
Allow Ranges
Select this check box to allow ranges. The check box is available for header
fields. Ranges are used in handling the alternative determination.
9.16.7 Maintaining the Handling of Unplanned Costs

In this step, you maintain document header data restrictions for alternative handling
of unplanned delivery cost, based on header attributes like company code, vendor,
and total amount.
To maintain unplanned cost handling:

Maintain Handling of Additional Costs > Unplanned Costs - Handling
Determination and Auto Coding - Data.
VIM070500-03-CGD-EN-1
2. In the Handling of Additional Costs screen, maintain alternatives for the

handling of unplanned costs, using header field parameters as defined in
“Maintaining Fields for Handling Determination and Auto Coding”
on page 257.
Alternative
The following alternatives are available:
A1 Add delivery costs together into header field Unplanned Cost

A2 Add delivery costs to the respective item amount (previous line
item without qualifier)
A3 Distribute delivery costs to PO lines (% to line item amount /
same % for all lines)
A4 Add Delivery costs together and post to separate G/L account
A5 Show delivery costs as separate lines
A6 Discard delivery costs
A7 Customer specific
Additional Costs
Enter qualifiers, for example FREIGHT.
Distribution Type for Alternative A3

Select one of the following:
• Distribute equally to all PO lines
• Distribute proportionally to all PO lines
VIM070500-03-CGD-EN-1
Example 9-3: Equal and proportional distribution

A document has two line items.
Line 1 has an amount of 100 Euro.
Line 2 has an amount of 300 Euro.
Additional cost for the document is 20 Euro.
Equal distribution
Line 1 receives 10 Euro (20 Euro / 2) additional cost and ends up
with 110 Euro.
Line 2 receives 10 Euro (20 Euro/2) additional cost and ends up
with 310 Euro.
Proportional distribution
Line 1 receives 5 Euro (20 Euro * 100/[100 + 300]) additional cost
and ends up with 105 Euro.
Line 2 receives 15 Euro (20 Euro * 300/[100 + 300]) additional
cost and ends up with 315 Euro.
Company Code, Vendor

Enter values to restrict the alternatives.
Note: Do not apply too tight restrictions for the case that ICC does not
fill the appropriate data.
Example:
• A1: For company code 3000 and vendors 0 to 3000, the cost will be added to the
Unplanned Cost header field.
• A6: Vendor 1002 claims handling charges, which will always be discarded.
3. To open the Detail Configuration in the Handling of Additional Costs screen,

double-click a determination line or click the Details button .
Configure the corresponding coding using item field parameters as defined in
“Maintaining Fields for Handling Determination and Auto Coding”
on page 257.
You must enter the coding only in A4 and A5 lines.
VIM070500-03-CGD-EN-1
9.16.8 Maintaining a Function Module for Customer Specific

Cost Handling
The ICC additional cost data is delivered on line item level. It can be matched within
a customer specific function module instead of using the VIM standard approach.
To maintain a function module for cost handling:

Maintain Handling of Additional Costs > Customer Specific Cost Handling >
Function Module for Customer Specific Cost Handling.
2. In Constant ADD_COST_FM, in Constant Value, enter the name of your cost

handling function module. The interface of the function module must be
compatible with /OPT/MAP_ADD_COSTS.
9.16.9 Maintaining a Function Module for Customer Specific

Unplanned Cost Matching
This refers to alternative A7 in “Maintaining the Handling of Unplanned Costs”
on page 258. To handle unplanned cost delivered by ICC, you can configure a
customer specific function module instead of using the VIM standard approach.
To maintain a function module for unplanned cost matching:

Function Module for Customer Specific Unplanned Cost Matching.
2. In Constant ADD_UNPL_COST_FM, in Constant Value, enter the name of your

unplanned cost matching function module. The interface of the function module
must be compatible with /OPT/MAP_UNPL_COSTS.
9.16.10 Maintaining G/L Line Relevance of Unplanned Costs

In this step, you maintain whether the customer specific unplanned cost handling
alternative shall be treated as G/L line or not.
Note: This is only necessary if a customer specific cost handling function

module has been implemented.
To maintain G/L line relevance of unplanned costs:

Assign G/L Line Flag to Customer Alternative.
VIM070500-03-CGD-EN-1
2. In the Customizing Table G/L line flag for Handling Alternative screen,
specify whether the customer specific handling alternative is G/L line relevant
or not.
9.17 Maintaining the VAT Date

In some countries, for example in Eastern Europe, the use of the VAT date (tax
reporting date) has become mandatory. In a typical case, this is the date when goods
are received. The VAT date must be used as a reference date for tax calculation. VIM
provides a dedicated field for the VAT date with a corresponding logic to have
documents posted according to the legal requirements.
The VAT date functions in VIM work in conjunction with the global setting of
company codes Tax Reporting Date active. If this setting is activated, VIM checks
if the VAT date is provided in the DP document at the time of posting.
At the time of implementation, SAP ERP supports the field only in the FB60 and
MIRO transactions and in the BAPI function for Non PO posting. The BAPI used to
post PO invoices currently does not support the field. PO invoices can only be
posted online in the company codes that have the VAT date active.
You can enter the VAT Date field during indexing in the DP indexing screen. In
many cases, the value of the supply date, which already exists in VIM, can be
assigned to the VAT date. VIM does not automatically populate the VAT date from
the supply date, but VIM provides the business rule 409 - Copy rule: Supply Date
to VAT Date (NPO / PO) to copy the value. You can activate this business rule when
needed. VIM provides the business rules 407 - Missing VAT Date (NPO) and 408 -
Missing VAT Date (PO) to check if the VAT date is entered in the DP document.
These business rules stop the process with a DP exception before posting.
In the standard configuration, none of the related functions are active. To be able to
use the VAT date, additional configuration is required, as described in the following
sections.
9.17.1 Configuring the Indexing Screen

You must add the VATDATE field into the list of header fields for each DP document
type where it is needed; for more information, see “Configuring the Index Header”
on page 149.
Alternatively, you can add the VATDATE field into the list based on characteristics, as
described in “Characteristic Specific Screen Fields” on page 476. For example, you
can enable the field for Eastern European countries where the VAT date is
mandatory.
VIM070500-03-CGD-EN-1
9.17. Maintaining the VAT Date
9.17.2 Configuring Process Types

VIM delivers the following process types (business rules) to use with the VAT date:
• 407 - Missing VAT Date (NPO)

• 408 - Missing VAT Date (PO)
• 409 - Copy rule: Supply Date to VAT Date (NPO / PO)
The process types 407 and 408 check if the VAT date is provided in the DP
document. If not, the DP processing stops with an exception. Users are required to
enter the VAT date in the DP document. To enable the check, add the respective
process type for DP document or characteristic, with the function /
OPT/VIM_DETERMINE_PROC_407 (same function for 408).
The baseline configuration of the process types 407 and 408 contains predefined
process options. You can adjust the process options list to suit your scenarios.
The process type 409 copies the supply date value into the VAT date. This is not a
dialog process type: it does not trigger an exception. You must use the same process
type for both PO and NPO. You can enable the process type for individual
document types or using characteristics. The process type must be checked with the
function /OPT/VIM_DETERMINE_PROC_409.
In addition to enabling these process types as required for selected DP document

types, there is another configuration task that you must perform: For the
combination of the process types 407/408 and DP document types, you must
maintain index screen options for all relevant roles.
9.17.3 Maintaining Z Constant 005 / SKIP_VATDATE_CHECK

You can set the Z constant 005 / SKIP_VATDATE_CHECK to X in the table /
PTGWFI/Z_CONST. This setting prevents the posting functions from stopping with an
error message in the following situations:
• For Non PO invoices

When the company code is set up to use the VAT date but the corresponding
field does not exist in the SAP BAPI structure.
• For PO invoices
When PO invoices are set up to be posted with SAP BAPI (standard VIM BDC ID
1).
Currently, SAP BAPI does not support the VAT date, but if by some reason you
want the posting to go through (or you are using a user exit to pass the date in
some other way), you can set the constant to X.
VIM070500-03-CGD-EN-1
Chapter 10
PO Parking Process Configuration
Note: In VIM 5.2, the Baseline implementation of handling parked PO and

Non PO invoices has switched to the DP document. This change applies to the
entire exception handling (except price and quantity block on the posted
document) and to Invoice Approval.
Vendor Invoice Management (VIM) provides functionality for managing parked PO

invoices (MIRO transaction) and exceptions therein.
Primarily, invoices can be parked for some further processing. This includes, for
example, waiting for approval, or changing some customizing like vendor data, or
tax data. The invoice will be posted in a later step.
The main processing concept involved in managing parked PO invoices is the

concept of “parking reasons”. Parking reasons define the overall processing of the
invoice as required by the process swimlane.
Main concepts
Parking reasons
• Parking reasons effect the process flow as required by the swimlane
definition.
• Each swimlane diagram translates to one parking reason.
• Parking reasons determine the initial actor and various collaboration options
available to the various actors during the process flow.
Roles
• Roles use the standard OpenText role/actor infrastructure.
• Roles can use the standard key determination infrastructure to configure
complex actor determination logic without programming.
• For the PO parking process, the role concept uses the product code LIX.

• The following main types of options are available:
• Actions
• Actions can base on transactions or class methods or workflow tasks.
• Options and option types can effect the processing logic.
VIM070500-03-CGD-EN-1
Chapter 10 PO Parking Process Configuration
• Options and option types can effect the user experience.

• Options and option types can make the workflow engine rerun the rules on
the most current metadata to effect the process flow.
• Options and option types can be configured to change the document status.
BDC IDs
• BDC IDs build a powerful infrastructure for prepopulating data into SAP
• BDC IDs are optimized for both dialog processing and background
processing.
• BDC IDs can be used to set dynamic Parameter IDs.
• BDC IDs can be used to configure new user collaboration actions.
• BDC IDs eliminate the need to code parameterized transactions.
• BDC IDs can be used to configure BDC success messages.
Main steps The following are the main steps involved in implementing process scenarios in the
PO parking process:
1. Identify the various parking reasons that are required for the realization of the
process scenarios.
2. Identify the subscreen to be called during the document parking process.
3. Identify the roll out criteria.
types.
The starting point for any configuration is a set of process flow swimlanes. The
following swimlane is an example of such a process as implemented by the PO
invoice parking workflow:
VIM070500-03-CGD-EN-1
10.1. Configuring Process Options
The following sections describe the main steps of the PO parking process
configuration:
• “Configuring Process Options” on page 267
• “Configuring Parking Reasons” on page 272
• “Configuring Global Parameters” on page 277
10.1 Configuring Process Options

Process options are the functions that a user can perform in a Dashboard. Process
options interact with workflow processes. This section describes the configuration of
process options used in the following scenarios:
• Parking PO invoice processing
• Blocking PO invoice processing
• Parked Non PO Invoice processing
The process options configuration comprises the following steps:

• “Defining a Process Option” on page 268
• “Configuring User Process Options” on page 270
VIM070500-03-CGD-EN-1
10.1.1 Defining a Process Option

You can always define a new process option to suit to your business process. For
example, if an agent needs to do some action that is not delivered in the VIM
baseline, you can define a new process option for this.
To define a process option:
PO Based Invoice Configuration > Parked Invoice Processing Configuration >
Park Reason Maintenance > Process Option Definition
2. Click the New Entries button in the application toolbar.
3. Define the process option, using the following parameters:
Option Type
Select the option type:
Action
The system executes an SAP transaction code defined against this
action.
Authorization
This option type is relevant only if the option selected is a PO blocked
scenario. It allows the user to complete the line level workflow and the
target role to run the transaction code defined against the authorization
option.
VIM070500-03-CGD-EN-1
Referral
The work item is forwarded to the target role defined in the user
process options configuration.
Approve/Reject
The Approve/Reject option type has more relevance in the Invoice
Approval process as these are predefined options.
BDC Action
Similar to the Action option type, but the transaction/execution has
more flexibility to be configured in the BDC ID defined here.
Workflow Task
Triggers a custom (sub) workflow when the user selects the option.
Note: Some of the following parameters are only available for certain
option types.
Option ID
Enter a 5 digit numeric ID that represents the option.
Description
Option Short Text

Enter the description that is shown on the button in the user dashboard for
this option.
BDC Configuration Id
Select the BDC ID that will be called when the user selects the option for
execution. This field is applicable only if the option type is BDC Action.
Task
Enter the (sub) workflow/task to be triggered when the user selects the
option. The task must be compatible to OpenText workflow task.
Transaction Code
Define a transaction code to be called when the user executes the option.
This is only relevant if the option type is Action or Authorization.
Check Autopost
Define if the system shall try to post a parked document in background
after successful execution of the option:
• Enter X to enable automatic posting.

• Enter FM:<FUNCTION> where <FUNCTION> is a custom function module
to determine if the document will be posted. This is relevant when it is
difficult for the system to define the auto-post criteria directly.
Comments Required
Select this check box to force the user to maintain comments once this
option is executed.
VIM070500-03-CGD-EN-1
Hdr Level Decision

Select this check box to achieve that the system applies the decision to the
entire document rather than to the current line item in the process. This is
applicable in the PO blocked invoice processing scenario where there may
be options that need to be applied to the entire PO invoice and not just the
line item that is being worked on.
Confirm Execution
Select this check box to achieve that the user will be prompted to confirm
the option selected.
Example: If an option deletes the SAP document, a confirmation from the user to
really perform the action makes sense.
Confirm Completion
Select this check box to achieve that the user will be prompted to confirm
successful completion of the option.
Override
Select this check box to achieve that the user will be able to select any SAP
user in the system as the user(s) that will receive the work item when it is
referred, and not just the users the system proposes after running the role
resolution process. This parameter is applicable only in the Referral
option type.
Validate Override User
Select a function module that is used to validate the users that the current
user overrides.
Example: If a work item needs to be sent for approval, which is technically a
referral, and the user is allowed to change the proposed users, this custom
validation is required to disallow users to choose anyone they want.
Run Inv. Verification

Select this check box to run invoice verification when the current process
ends.
Process Complete
Select this check box to end the current process and start the next process.
10.1.2 Configuring User Process Options

In this step, you configure all the process options available for roles when a PO
invoice document is parked.
When a PO invoice is parked with a parking reason, a corresponding workflow is

triggered. It will create a work item for the role to handle the next step. This section
describes how to customize the role who will receive the work item. You can assign
the option defined in “Defining a Process Option” on page 268 to a role in this step.
A role has normally some process options, which are available in the role dashboard.
Tip: The standard SAP authorizations for transactions are checked for the
underlying transactions in a user process option.
VIM070500-03-CGD-EN-1
To configure user process options for PO parked documents:
Technical Configuration > Advanced Process Option Configuration > PSS
User Process Options - OST
2. Click New Entries in the application toolbar.
3. Configure the user process options, using the following parameters:
Block Reason
Select block reason. 9 is the system defined block reason for PO parked
invoices.
From Actor
Select the role that sent the work item.
To Actor
Select the role that receives the work item after successfully processing the
option.
Option Type
Select the type of process option (Action, Referral, BDC Action, Approve,
Reject, etc., see “Configuring Process Options” on page 267)
Option ID
Select the ID of the process option.
Condition FM
• Define a condition function module to restrict availability of an option to

a role even if the availability is defined here.
Example: If you would like to show the option “Change Purchase Info Record”
only if the Purchase Order has a Purchase Info Record (PIR), you can define a
custom function to verify the existence of the PIR and issue an error if there is no
PIR.
VIM070500-03-CGD-EN-1
• If an error is issued in the function module, the option will not be

available to the user.
• For the interface of the condition function module, see function
module /OPT/BL_CONDFM_INFOPROVIDER.
10.2 Configuring Parking Reasons

Figure 10-1 shows the parking reason selection screen.
Figure 10-1: Parking reason selection screen
In this step, you configure the valid parking reasons. Each parking reason represents
a process scenario as represented in a swimlane diagram.
Configuring a parking reason comprises the following actions:

• Define the parking reason.
• Define the roles that are responsible for receiving the first work item in the
process, for posting the PO invoice, and the initial approver.
• Define if the process triggering needs to be delayed.
• Delimit the available options for the role that is responsible for receiving the first
work item.
VIM070500-03-CGD-EN-1
10.2. Configuring Parking Reasons
To configure a parking reason:
Park Reason Maintenance > Parking Reason Definition Maintenance
2. Select a parking reason and click in the application bar.
3. Define the parking reason, using the following parameters:
Description
Enter a description for the parking reason.
Active Indicator
Select this check box to achieve that the user can select the parking reason
during parking of a PO invoice.
VIM070500-03-CGD-EN-1
Approval Required
Select this check box to achieve that the parking reason will be considered
for the Invoice Approval process. For details on the Invoice Approval
process in VIM, see “Invoice Approval“ on page 335.
Subscreen Program/Screen Number

Select a subscreen that can be configured to capture additional information
from the user when the user chooses a particular parking reason.
• You can extend the structure /PTGWFI/M_PRKMTR to capture additional

data during parking a PO invoice.
Example: If a PO invoice needs to be parked for “Service Entry Sheet Required”,

the system needs to know who is the Service Requisitioner. This additional
information can be programmed in a custom subscreen for the parking reason
“Service Entry Sheet Required”.
• Copy the OpenText delivered subscreen program and screen number to
ensure that the common part include /PTGWFI/PRK_COMMON_PART is
defined and data read/transferred properly.
VIM070500-03-CGD-EN-1
10.2. Configuring Parking Reasons
Autopost
Select this check box to achieve that the system tries to post the parked
invoice after the routing is complete.
Posting Actor
Define the role responsible for posting the invoice and also responsible for
handling errors if the posting in background fails.
Initial Actor
Define the role who receives the first work item in the process when the
current parking reason is selected.
VIM070500-03-CGD-EN-1
Example: If a PO invoice is parked for “Currency Mismatch”, the initial role that
needs to look at the invoice is the BUYER to correct the PO. Maintain BUYER as initial
actor.
Initial Actor FM
You can define a custom function module to determine the initial actor.
Example: A PO is parked for a reason that is applicable to BUYER or

REQUISITIONER depending on the availability of a value REQUESTER in Purchase
Info Record or Goods Receipt. You can then define a custom function module to
determine the availability of value for REQUESTER in Purchase Info Record or
Goods Receipt and set the initial actor accordingly.
For the interface of the function module, see function module /
OPT/BL_Q_INIT_ACT_FM.
Available Options
Define the options that are available for the role on the dashboard during
PO parked invoice process for the current parking reason. Separate the
options by semicolon. The option format is AXXXX where A is the option type
and XXXX is the 4 digit value representing the option ID.
The system uses these values in conjunction with the user process options
defined in “Configuring User Process Options” on page 270 to determine
which options show up for the role’s dashboard.
Initial Approver
Define the role of the initial approver if the invoice document is sent for
approval.
Delay Function
• Define the custom function module that can be used to restrict the
immediate triggering of the PO parking process even if the user selected
the current parking reason when the invoice is parked.
Example: The PO is parked for “Credit Memo Required” and you know that
Credit Memo is on its way and will not show up for the next two days. You
might then want to send the work item to the AP's inbox not before two days.
For this purpose, you can define a custom function to restrict the triggering of
the work item for the user for the next two days.
• For the interface of the delay function module, see function module /
OPT/BL_P_DELAYFM_SRM.
VIM070500-03-CGD-EN-1

This section describes the various global customization parameters that are
available. Global parameters control various aspects of the processing logic for PO
invoice parking process flows.
Important
Configuring global parameters comprises the following actions:
• “Configuring Transactions to Create Parked PO Invoices” on page 277

• “Configuring Screen Exits” on page 278
• “Configuring the Option Order” on page 280
• “Defining a Preprocess (Sub)workflow” on page 281
• “Configuring Binding Function Exits” on page 282
• “Configuring the Pre-dashboard Method Exit” on page 283
• “Configuring the Post-dashboard Method Exit” on page 284
• “Configuring a Post Process (Sub)workflow” on page 284
• “Configuring an Autopost Exit” on page 285
• “Configuring a Parked Document Posting Exit” on page 286
• “Configuring the Image Display Function” on page 287
• “Configuring the Parking Functionality” on page 288
• “Configuring Populating Screens for Re-enter Options” on page 289
10.3.1 Configuring Transactions to Create Parked PO Invoices

In this step, you configure the transactions that create parked PO invoices. Any
parked PO invoice that is created with these transactions triggers a corresponding
workflow in VIM.
To configure transactions to create parked PO invoices:
3. In the WebFlow Constant Table, under Product Code PIR, double-click the
Constant PO_BASED_INV_TCODE.
VIM070500-03-CGD-EN-1
4. Enter the Constant Value: MR01;MIR7;/PTGWFI/LIV_CHG_PKRS;
10.3.2 Configuring Screen Exits

In this step, you configure the custom program/subscreen that displays the header
data on the user dashboard.
Example: After you have selected a particular parking reason, you want a particular
subscreen to appear as shown in the following screenshot.
VIM070500-03-CGD-EN-1
To configure screen exits:
1. Copy the OpenText delivered header program and subscreen.
Note: We strongly recommend that you copy the program and subscreen
because the common part /PTGWFI/WLIX_COMMON_PART is required to
communicate to the main program.
2. To access the configuration for PRKPROG and PRKSCREEN, run the /

OPT/VIM_IMG207 transaction.
Configuration > Parked Invoice Processing Configuration > Technical
Configuration > Dashboard Screen Customization > Screen Exits.
3. Configure PRKPROG and PRKSCREEN, using the following parameters:
VIM070500-03-CGD-EN-1
Constant: PRKPROG
Usage
Subscreen program for parked invoice dashboard header subscreen. To
provide additional data on the invoice dashboard, you can define your
custom screen here.
Default Value
/PTGWFI/PRK_SUBSCREEN01
Constant: PRKSCREEN
Usage
Subscreen number for parked invoice dashboard header subscreen. To
custom screen here.
Default Value
9901
10.3.3 Configuring the Option Order

In this step, you configure the order in which the options appear in the user’s
dashboard in the parked invoice process. For details on options, see “Configuring
Process Options” on page 267.
To configure the option order:
1. Run the /OPT/VIM_IMG208 transaction.

Configuration > Dashboard Screen Customization > Option Order
Configuration.
2. Configure the order in which the options will appear in the user’s dashboard,
Description
Enter a description of the option order.
VIM070500-03-CGD-EN-1
Constant Value
Value for the option order. Default value: 10ATR
Individual values
1
Approvals
0
Rejects
A
Actions
T
Authorizations
R
Referrals
Example: If you want all actions to show up first, maintain A10TR. The options will
be shown in order actions, approvals, rejections, authorizations and referrals.
10.3.4 Defining a Preprocess (Sub)workflow

In this step, you define a custom (sub)workflow that needs to be triggered before the
PO parking workflow process is triggered.
This custom (sub)workflow can do some actions that are not delivered in the VIM
standard process. For example, it can notify an agent that a PO invoice is parked and
waiting to be further processed. The (sub)workflow can also update some
monitoring custom tables.
To define a preprocess (sub)workflow:

Configuration > Advanced Process Customization > Pre Process
(sub)Workflow – Parked Invoices.
VIM070500-03-CGD-EN-1
2. In Constant Value, configure the (sub)workflow ID that is used to trigger a

custom (sub)workflow before triggering the PO parked invoice workflow
process.
Default Value - None
10.3.5 Configuring Binding Function Exits

In this step, you define custom function modules that can transfer data that is
related to the parked invoice to the OpenText delivered workflow processes for the
PO parked invoice process. Using such exits, you can manipulate the workflow
container of the process or populate VIM tables with custom data.
To configure binding function module exits:

Configuration > Advanced Process Customization > Binding Function
Module Exit > Dashboard Step.
2. Configure the function module exits, using the following parameters:
Constant PRK_PSS_BIND_FM1
Usage
This function module is used to manipulate the workflow container
during inward binding (task container to workflow container). This
manipulation facilitates many features such as populating Analytics
with custom data etc.
Default value
/PTGWFI/PRK_TMP_BIND_EXT_FM
Constant PRK_PSS_BIND_FM2
Usage
during outward binding (workflow container to task container). This
manipulation facilitates the user to capture process information and
populate with additional information.
VIM070500-03-CGD-EN-1
Default value
/ORS/000007_LIX_PSS_BIND_O
Note: Do not change this value. If you need additional information to be

captured for analytics or other purposes, first call the standard function /
ORS/000007_LIX_PSS_BIND_O within your function. Otherwise,
unexpected failures in the VIM PO Parked Invoice Management process or
subsequent processes may occur.
10.3.6 Configuring the Pre-dashboard Method Exit

In this step, you define a custom function module that will manage custom data
before calling the dashboard.
Example: If the custom data is added to VIM tables and it should be displayed in the
Dashboard in some way, the data must be managed (manipulated) in such method exits.
To configure the pre-dashboard method exit:

Configuration > Advanced Process Customization > Pre Dashboard Method
Exit - Parking.
2. Configure the pre-dashboard method exit, using the following parameters:
Constant Value
This value is used to manage document data before calling the dashboard.
Default value - None
VIM070500-03-CGD-EN-1
10.3.7 Configuring the Post-dashboard Method Exit

In this step, you define custom function modules that will manage custom data after
calling the dashboard.
Example: Custom data is added to VIM tables and it is displayed in the dashboard. This
custom data can be changed in the dashboard. After the dashboard is quit, the data must be
saved. This can be done in the post-dashboard method exit.
To configure the post-dashboard method exit:

Configuration > Advanced Process Customization > Post Dashboard Method
Exit (Parked Invoices).
2. Configure the post-dashboard method exit, using the following parameters:
Constant Value
This value is used to manage document data after calling the dashboard.
10.3.8 Configuring a Post Process (Sub)workflow

In this step, you define custom (sub)workflows that will execute after completing the
PO Parked Invoice document process.
This custom (sub)workflow can do some additional action that is not delivered in
the VIM standard process, for example to notify an agent that the process is
completed, or to update some VIM/custom tables with corresponding data.
To configure a post process (sub)workflow:

VIM070500-03-CGD-EN-1
Configuration > Advanced Process Customization > Post Process

(sub)Workflow - Parked Invoices.
2. Configure a post process (sub)workflow, using the following parameters:
Constant Value
If you want to call a custom subworkflow after completing the PO Parked
Invoice Document process, you can define a workflow template/task here.
10.3.9 Configuring an Autopost Exit

In this step, you define a custom function module that will manipulate data of the
PO parked invoice and/or post the document automatically.
If maintained, the custom function module will be called in the method

postparkedinvoice of the object type /OPT/VIM_BUS2081. The custom function
module is called before the standard posting logic for the PO parked invoice
document is applied. If there is any exception thrown by this function module, the
workflow will run out of the posting step without doing any further action.
To configure an autopost exit:

Configuration > Autopost Global Configuration > Autopost Exit Function.
VIM070500-03-CGD-EN-1
2. Configure an autopost exit, using the following parameters:
Constant Value
• Enter a function module. This function module can be used to

manipulate data and/or post a PO parked document automatically using
a custom function. If the function module configured here throws an
exception, the system will run out of the posting step.
• Default value: None
• For the interface of the function module, see function module /
PTGWFI/PRK_M_TMP_PRE_AUTOPOST.
10.3.10 Configuring a Parked Document Posting Exit

In this step, you define a custom function module that will perform any post process
transaction after the document is posted.

postparkedinvoice of the object type /OPT/VIM_BUS2081. It is called after the PO
parked invoice has been posted. This exit can be used for example to update VIM or
custom tables with additional data or to perform any action after the document is
posted.
To configure a parked document posting exit:

Configuration > Autopost Global Configuration > Parked Document Posting
Exit.
VIM070500-03-CGD-EN-1
2. Configure a parked document posting exit, using the following parameters:
Constant Value
• Enter a function module. This function module can be used to perform

any post process transactions after the document is posted.
• Default value: None
PTGWFI/PIR_F_TMP_POST_EXIT_FM.
10.3.11 Configuring the Image Display Function

In this step, you define custom function modules that will display an SAP
ArchiveLink image associated to the PO invoice document.
To configure the image display function:

Configuration > Image Display > Image Display Function.
2. Configure the image display function, using the following parameters:
VIM070500-03-CGD-EN-1
Constant Value
• Enter a function module. This function module can be used to display an

SAP ArchiveLink image associated to the PO invoice document.
• Default value: /PTGWFI/LIX_F_TMP_DISP_IMG
PTGWFI/LIX_F_TMP_DISP_IMG.

You can configure that images are automatically displayed when the PO Parked
Invoice Dashboard is opened.
To configure automatic image display:
3. In the WebFlow Constant Table, under Product Code LIX, double-click the
10.3.13 Configuring the Parking Functionality

In this step, you define custom function modules that activate the parking
functionality.
To configure parking functionality:
3. Look for Product Code LIX and Constant USR_EXIT_GET_DATA_FM and double-
click the line.
VIM070500-03-CGD-EN-1
4. Configure the parking functionality, using the following parameter:
Constant Value
Enter a function module to be used to activate the parking of PO invoice
documents.
Default value:
Blank.
Baseline does not offer parking.
Optional value:
/PTGWFI/PRK_M_GET_PARK_DATA_N
This is the standard parking implementation function module.
10.3.14 Configuring Populating Screens for Re-enter Options

In exceptions workflows (parking or blocking), the following options are available to
processors: Delete and re-enter as PO/NPO invoice or Cancel and re-enter as PO/
NPO invoice. These options delete the existing invoice, then open a window with
the invoice image and open another window with a SAP transaction, so that users
are supposed to enter all information manually.
VIM provides function module /PTGWFI/VIM_CRE_PO_INV_PREF for this scenario.

This function module populates the new invoice with a subset of the header data of
the deleted document:
• Company code
• Document date
• Vendor reference number
• Currency
• Vendor number
You can insert the function module in the corresponding Z constants or you can
create an own logic on basis of this function module.
For the creation of a PO invoice, maintain table /PTGWFI/Z_CONST, using the SM30
transaction. In Product Code LIX, Constant CREATE_PO_BDC_FM, enter Constant
Value /PTGWFI/VIM_CRE_PO_INV_PREF.
VIM070500-03-CGD-EN-1
Note: The function module /PTGWFI/VIM_CRE_PO_INV calls transaction MIRO

without populating data.
VIM070500-03-CGD-EN-1
Chapter 11
PO Blocking Process Configuration
VIM provides functionality for managing blocked PO invoices (based on MIRO

transaction) and exceptions therein. Invoices are blocked if they show discrepancies,
for example a price discrepancy, that prevent the invoice from paying.
The main processing concept involved in managing blocked PO invoices is the

concept of “blocking reasons”. Blocking reasons define the overall processing of the
invoice as required by the process swimlane. The most important reasons are price
block and quantity block reasons.
Main concepts
Blocking reasons
• Blocking reasons effect the process flow as required by the swimlane
definition.
• Each swimlane diagram translates to one blocking reason.
• Blocking reasons determine the initial actor and various collaboration
options available to the various actors during the process flow.
Roles
• The role concept uses the product code LIX, same as for PO invoice parking
scenarios described in “PO Parking Process Configuration“ on page 265.

• Actions
• Options and option types can also effect the user experience.
VIM070500-03-CGD-EN-1
Chapter 11 PO Blocking Process Configuration
BDC IDs
• BDC IDs build a powerful infrastructure for pre-populating data into SAP
processing.
• BDC IDs can be used to set dynamic Parameter IDs.
blocked PO invoice process configuration:
1. Identify the various blocking reasons that are required for the realization of the
process scenarios.
types.
following swimlane is an example of such a process swimlane, as implemented by
the blocked PO invoice processing workflow:
VIM070500-03-CGD-EN-1
The following sections describe the main steps of the PO blocking process
configuration.
• “Configuring PO Blocking Process Options” on page 294
• “Configuring Blocking Reasons” on page 295
VIM070500-03-CGD-EN-1
11.1 Configuring PO Blocking Process Options

Process options are the functions a user can perform on VIM PO parking, PO
blocking, Non PO parking and Non PO approval processes. For a detailed
description of how to configure process options, see “Configuring Process Options”
on page 267.

When a PO invoice is blocked, a PO blocking workflow is triggered. A work item is
created for a role that is configured to receive such kind of work items. In this step,
you configure all the process options available for roles when a PO invoice
document is blocked. The process options allow the role to carry out a set of specific
actions to solve the blocking.
Configuring the process options comprises the following steps:
• Define user process options for all the roles in the process.
• Delimit available options for the role that is responsible for the first work item
created by each blocking reason. This is done in an individual blocking reason
definition.
To configure user process options for PO blocked documents:
PO Based Invoice Configuration > Blocked Process Configuration > Technical
Configuration > Advanced Process Option Configuration > PSS User Process
Options - OST
VIM070500-03-CGD-EN-1
11.2. Configuring Blocking Reasons
BlockReason
Select the blocking reason. If the invoice is blocked, the SAP invoice sets this
blocking reason.
From Actor
Select the role that sent the work item. Only this role will have the process
option on it's dashboard.
To Actor
Select the role who receives the work item after successfully processing the
option.
Option Type
Option ID
Condition FM

Example: If you would like to show the option “Change Purchase Info Record”
only if the Purchase Order has a Purchase Info Record (PIR), you can define a
custom function to verify the existence of the PIR and raise an error if there is no
PIR.
• If an error is raised in the function module, the option will not be
OPT/BL_CONDFM_INFOPROVIDER.
11.2 Configuring Blocking Reasons

In this step, you configure the valid blocking reasons in the VIM PO blocking
process. The main steps are the following:
• Define the blocking reason.
process.
To configure a blocking reason:
PO Based Invoice Configuration > Blocked Process Configuration > Block
Reason Maintenance > Block Reason Definition
2. Select a blocking reason and click in the application toolbar.
VIM070500-03-CGD-EN-1
3. Configure the blocking reason, using the following parameters:
Block Reason
Click and select the blocking reason from the list.
Description
Enter a description defining the blocking reason.
Delay FM
immediate triggering of the PO blocking process even if the user
selected the current blocking reason when the invoice is blocked.
Example: The PO is blocked for “Quantity Discrepancy” and you know that
additional quantities required to remove the blocking reason automatically are
on their way and will not show up for the next two days. You might then want
to send the work item to the AP's inbox not before two days. For this purpose,
you can define a custom function to restrict the triggering of the work item for
the user for the next two days.
Initial Actor
Define the role who receives the first work item in the process when the
current blocking reason is selected.
VIM070500-03-CGD-EN-1
Example: If a PO invoice is blocked for “Price discrepancies”, the initial role that
needs to look at the invoice is the BUYER to correct the PO. Maintain BUYER as initial
actor.
Initial Actor FM
• You can define a custom function module to determine the initial actor.
Example: A PO is blocked for a reason that is applicable to BUYER or

REQUISITIONER depending on the fact that there is at least one Goods Receipt
posted. You can then define a custom function to determine the availability of a
Goods Receipt for the invoice and to set the initial actor accordingly.
• For the interface of the initial actor function module, see function
module /OPT/BL_Q_INIT_ACT_FM.
Object Type
This parameter is obsolete.
Event
Reference table
Reference field

available. Global parameters control various aspects of the processing logic for PO
blocking process flows.
Important

• “Configuring Dashboard Screen Exits” on page 298
• “Configuring the Option Order” on page 305
• “Configuring Binding Function Exits (Dashboard)” on page 306
• “Configuring the Post Dashboard Method Exit” on page 307
• “Configuring Header Level Dashboard Binding Exits” on page 308
• “Configuring the Send Back Functionality Exit” on page 309
VIM070500-03-CGD-EN-1
11.3.1 Configuring Dashboard Screen Exits

This section describes how to configure the custom program/subscreen that displays
This configuration applies to the following levels:

• “Line Level” on page 298
• “Header Level” on page 302
11.3.1.1 Line Level

data on the user dashboard for line item workflow processes in the PO blocking
process. The following screenshot shows the line level dashboard, the header data
section can be customized to display other information if needed.
VIM070500-03-CGD-EN-1
To configure line level exits:
1. Copy the OpenText delivered header program and sub screen.
Note: We strongly recommend that you copy the program and sub screen
VIM070500-03-CGD-EN-1
2. To access the configuration for LIXPROG and LIXSCREEN, run the /

Configuration > Blocked Process Configuration > Technical Configuration >
Dashboard Screen Customization > Line Level Dashboard Screen > Screen
Exit.
VIM070500-03-CGD-EN-1
3. Configure LIXPROG and LIXSCREEN, using the following parameters:
Constant: LIXPROG
Usage
Subscreen program for blocked invoice dashboard header subscreen. To
custom screen here.
Default Value
/PTGWFI/M_LIX_SUBSCREEN02
Constant: LIXSCREEN
Usage
Subscreen number for blocked invoice dashboard header subscreen. To
custom screen here.
Default Value
9902
Currency A purchase order and the corresponding blocked invoice might have been created or
conversion posted using different currency keys. Therefore, it was often difficult to compare the
amounts displayed in the header section of the blocked line item dashboard due to
the different currency keys. VIM provides a solution that allows different settings
regarding the initial and also a completely flexible currency conversion: the constant
LIXSCREEN_CURR_CONV, available for the product code LIX in table /
PTGWFI/Z_CONST (transaction SM30).
The value of the constant consists of two characters:

• The first character controls which initial default currency conversion method is
used when the blocked line item dashboard is executed.
• The second character controls whether a currency conversion button is displayed
on the screen. Such a button allows flexibly changing the displayed currency at
any time.
VIM070500-03-CGD-EN-1
Possible values for the first character
I
Use the invoice currency for initial currency conversion. The posting date of the
invoice is taken as conversion date.
P
Use the purchase order currency for initial currency conversion. The creation
date of the purchase order is taken as conversion date.
L
Use the local currency (based on the invoice) for initial currency conversion. The
current system date is taken as conversion date.
N
No initial currency conversion takes place.
Possible values for the second character
1
Display the currency conversion button on the screen. The current system date is
always taken as conversion date.
0
Do not display the currency conversion button on the screen.
The default configuration is N0. This means, no initial currency conversion takes
place, and the button for flexible currency conversion is not displayed.
The constant allows different flexible combinations, for example P1: Initial currency
conversion uses the purchase order currency; and additionally the flexible
conversion button is activated. This approach should offer maximum flexibility
when using the blocked line item dashboard.
11.3.1.2 Header Level

In this step, you configure the custom program/sub screen that displays the header
data on the user dashboard for header level workflow processes in the PO blocking
process. The following is a screenshot of the header level dashboard, the header data
section can be customized to display other information if needed.
VIM070500-03-CGD-EN-1
To configure header level exits:
1. Copy the OpenText delivered header program and sub screen.
Note: We strongly recommend that you copy the program and sub screen
because the common part /PTGWFI/WLIXDB_COMMON_PART is required to
VIM070500-03-CGD-EN-1
2. To access the configuration for LIXDBPROG and LIXDBSCREEN, run the /


Dashboard Screen Customization > Header Level Dashboard Screen > Screen
Exit – Header.
VIM070500-03-CGD-EN-1
3. Configure LIXDBPROG and LIXDBSCREEN, using the following parameters:
Constant: LIXDBPROG
Usage
Sub screen program for blocked invoice dashboard header sub screen.
To provide additional data on the invoice dashboard, you can define
your custom screen here.
Default Value
/PTGWFI/M_LIXDB_SUBSCREEN02
Constant: LIXDBSCREEN
Usage
Sub screen number for blocked invoice dashboard header sub screen.
To provide additional data on the invoice dashboard, you can define
your custom screen here.
Default Value
9902
11.3.2 Configuring the Option Order

In this step, you configure the order in which the options appear in the user’s
dashboard in the blocked invoice process. For details on options, see “Configuring
Process Options” on page 267.
To configure the option order:

Dashboard Screen Customization > Line Level Dashboard Screen > Option
Order Configuration.
2. Configure the order in which the options will appear in the user’s dashboard,
VIM070500-03-CGD-EN-1
Description
Enter a description of the option order.
Constant Value
Value for the option order. Default value: 10ATR
Individual values
1
Approvals
0
Rejects
A
Actions
T
Authorizations
R
Referrals
Example: If you want all actions to show up first, maintain A10TR. The options will
be shown in order actions, approvals, rejections, authorizations and referrals.
11.3.3 Configuring Binding Function Exits (Dashboard)

In this step, you define custom functions that can transfer data related to the blocked
PO to the OpenText delivered workflow processes for the PO blocking process.
Using such exits, you can manipulate the workflow container of the process or
populate VIM tables with custom data. The function modules maintained here are
called in the function module /PTGWFI/BIR_F_PSS_BINDING.
To configure binding function exits:

Advanced Process Customization > Line Level Process Customization >
Binding Function Module Exits > Dashboard Step.
VIM070500-03-CGD-EN-1
Constant PSS_BIND_EXIT_FM1
Usage
manipulation facilitates many features such as populating analytics
Default value
None
Usage
Default value
None
11.3.4 Configuring the Post Dashboard Method Exit

In this step, you define custom function modules that will execute to manage custom
data after calling the dashboard.
Example: Some custom data is added to VIM tables and should be displayed in the
dashboard. Therefore, this data must be managed (manipulated) in such method exits. These
exits are called in method SELECTPROCESSBIRV2 of the object type /OPT/VIM_BIR.
To configure the post dashboard method exit:

Advanced Process Customization > Line Level Process Customization > Post
Dashboard Method Exit (Blocked Invoices).
VIM070500-03-CGD-EN-1
2. Configure the post dashboard method exit, using the following parameters:
Constant Value
Default value
/PTGWFI/LIX_BK_TMP_PST_EXT
11.3.5 Configuring Header Level Dashboard Binding Exits

In this step, you define custom functions that can transfer data to OpenText
delivered processes for header level workflow.
Using such exits, you can manipulate the workflow container during inward and
outward binding. If maintained, the custom functions are called in the function
module /PTGWFI/LIX_F_DB_BINDING.
To configure header level dashboard binding exits:

Advanced Process Customization > Header Level Process Customization >
Binding Function Module Exits > Header Level Db – Task.
2. Configure header level dashboard binding exits, using the following

parameters:
Constant DB_BIND_EXIT_FM1
Usage
Default value
None
Constant DB_BIND_EXIT_FM2
Usage
VIM070500-03-CGD-EN-1

Default value
None
11.3.6 Configuring the Send Back Functionality Exit

Work items can be sent back from the header level dashboard using the Send Back
option. For this case, you can define a function to capture additional information
from the dashboard step after a work item is sent back.
To configure the send back functionality exit:

Advanced Process Customization > Header Level Process Customization >
Send Back Functionality Exit.
2. Configure the send back functionality exit, using the following parameters:
Constant DB_SNDBACK_EXIT
Usage
This function module is used to capture option information from the
dashboard step when the work item is sent back successfully in the
header level dashboard.
Default value
None
Interface
The interface of the function module is found in function module /
PTGWFI/LIX_TMP_DB_SBK_EXIT.
VIM070500-03-CGD-EN-1

In this step, you define a custom function module that will execute to display an
SAP ArchiveLink image associated to the PO invoice document.
This custom function module is called in function module /

PTGWFI/LIX_F_CALL_PS_SCREEN.

Image Display > Image Display Function.
Constant IMAGE_DISP_FM
Constant Value
Enter a function module. This function module can be used to display
an SAP ArchiveLink image associated to the PO invoice document.
Default value
/PTGWFI/LIX_F_TMP_DISP_IMG
Interface
For the interface of the image display function module, see function
module /PTGWFI/LIX_F_TMP_DISP_IMG.
VIM070500-03-CGD-EN-1

You can configure that an SAP ArchiveLink image associated to the PO invoice
document is automatically displayed when the PO Blocked Dashboard is opened.

3. In the WebFlow Constant Table, under Product Code LIX, double-click the

VIM provides a function module for this scenario. See “Configuring Populating
Screens for Re-enter Options” on page 289 for details.
VIM070500-03-CGD-EN-1
Chapter 12
Non PO Parking Process Configuration
Note: In VIM 5.2, the Baseline implementation of handling parked PO and

Non PO invoices has switched to the DP document. This change applies to the
entire exception handling (except price and quantity block on the posted
document) and to Invoice Approval.
Vendor Invoice Management (VIM) provides functionality for managing parked Non
PO FI invoices (FV60 transaction) and exceptions therein.
The main processing concept involved in managing parked Non PO invoices is the
concept of “parking reasons”. Parking reasons define the overall processing of the
invoice as required by the process swimlane.
Main concepts
Parking reasons
• Parking reasons effect the process flow as required by the swimlane
definition.
• Each swimlane diagram translates to one parking reason.
• Parking reasons determine the initial actor and various collaboration options
available to the various actors during the process flow.
Roles
• For the Non PO parking process, the role concept uses the product code PIR.

• Actions
• Options and option types can also effect the user experience.
VIM070500-03-CGD-EN-1
Chapter 12 Non PO Parking Process Configuration
BDC IDs
• BDC IDs build a powerful infrastructure for pre-populating data into SAP
processing.
• BDC IDs can be used to set dynamic parameter IDs.
Non PO parking process:
1. Identify the various parking reasons that are required for the realization of the
process scenarios.
2. Identify the sub screen to be called during the document parking process.
types.
following swimlane is an example of such a process as implemented by the Non PO
invoice parking workflow:
VIM070500-03-CGD-EN-1
12.1. Configuring Parking Reasons (Non PO Parking Process)
The following sections describe the main steps of the Non PO parking process
configuration.
• “Configuring Parking Reasons (Non PO Parking Process)” on page 315
12.1 Configuring Parking Reasons (Non PO Parking

Process)
Figure 12-1 shows the parking reason selection screen. You can configure the
dropdown selections based on the instruction in this section.
VIM070500-03-CGD-EN-1
Figure 12-1: Non PO Parking reason selection screen
In this step, you define the valid parking reasons in the VIM Non PO parking
process. Each parking reason represents a process scenario as represented in a
swimlane diagram.
Configuring a parking reason comprises the following actions:

• Define the parking reason.
process, for posting the Non PO invoice, and the initial approver.
• Delimit the available options for the role that is responsible for receiving the first
work item.
To configure a parking reason:
Non PO Based Invoice Configuration > Parked Invoice Processing
Configuration > Park Reason Maintenance > Parking Reason Maintenance
2. Select a parking reason and click in the application bar.
VIM070500-03-CGD-EN-1
3. Define the parking reason, using the following parameters:
Description
Enter a description for the parking reason.
Active Indicator
Select this check box to achieve that the user can select the parking reason
during parking of a Non PO invoice.
Subscreen Program/Screen Number

Select a sub screen that can be configured to capture additional information
from the user when the user chooses a particular parking reason.
• You can extend the structure /PTGWFI/F_PIRMTR to capture additional

data during parking a Non PO invoice.
Example: If a Non PO invoice needs to be parked for “Approval Required”, the

system needs to know who is the Requisitioner. This additional information can
be programmed in a custom sub screen for the parking reason “Approval
Required”.
• Copy the OpenText delivered subscreen program and screen number to
ensure that the common part include /PTGWFI/PIR_COMMON_PART is
defined and data is exchanged properly.
VIM070500-03-CGD-EN-1
Approval Required
Select this check box to achieve that the parking reason is flagged for
approval and that the Invoice Approval process is triggered.
Autopost
Select this check box to achieve that the system automatically posts the
invoice after Invoice Approval is completed.
Initial Actor
Define the role who receives the first work item once this document is
parked for the current parking reason.
Example: If a Non PO invoice is parked for “Approval Required”, the initial role
that needs to look at the invoice is the APPROVER. If the Approval Required check
box is selected, the initial role will be CODER.
Initial Actor FM
You can define a custom function module to determine the initial actor.
OPT/BL_Q_INIT_ACT_FM.
Delay Function
immediate triggering of the Non PO parking process even if the user
selected the current parking reason when the invoice is parked.
• Example: The Non PO invoice is parked for “Approval Required” and you
want to delay the approval for 2 days. You might then want to send the work
item to the AP's inbox not before two days. For this purpose, you can define a
custom function to restrict the triggering of the work item for the user for the
next two days.
VIM070500-03-CGD-EN-1
Initial Approver
Define the role of the initial approver if the invoice document is sent for
approval.
Posting Actor
Define the role responsible for posting the invoice and also responsible for
handling errors if the posting in background fails.
Available Options
Define the options that are available for the role on the dashboard during
Non PO parking process for the current parking reason. Separate the
options by semicolon. The option format is AXXXX where A is the option type
and XXXX is the 4 digit value representing the option ID.
The system uses these values in conjunction with the user process options
defined in “Configuring User Process Options” on page 319 to determine
which options show up for the role’s dashboard.

In this step, you define all the process options available for roles when a Non PO
invoice document is parked.
To configure user process options for Non PO parked documents:
Non PO Based Invoice Configuration > Parked Invoice Processing
Configuration > Technical Configuration > Advanced Process Option
Configuration > PSS User Process Options - OST
VIM070500-03-CGD-EN-1
BlockReason
Select block reason. V is the system defined block reason for Non PO parked
invoices.
From Actor
Select the role that sent the work item.
To Actor
Select the role who receives the work item after successfully processing the
option.
Option Type
Option ID
Condition FM

• Example: If you want to show the option “Change Tax Information” only if the
Non PO invoice has taxable line items, you can define a custom function to
verify the existence of taxable line items and raise an error if there are no taxable
line items.
• If an error is raised in the function module, the option will not be
• For the interface of the condition function module, see function
module /OPT/BL_CONDFM_INFOPROVIDER.

available. Global parameters control various aspects of the processing logic for Non
PO parking process flows.
Important

• “Configuring Transactions to Create Parked Invoices” on page 321
• “Configuring Dashboard Screen Exits” on page 322
• “Defining a Preprocess (Sub)workflow” on page 324
• “Configuring Binding Function Module Exits” on page 325
• “Configuring the Pre PSS Method Exit” on page 326
VIM070500-03-CGD-EN-1
• “Configuring the Post PSS Method Exit” on page 327

• “Configuring a Post Process (Sub)workflow” on page 328
• “Configuring an Autopost Exit” on page 329
• “Configuring a Parked Document Posting Exit” on page 330
• “Configuring a Parallel Workflow Exit” on page 332
• “Configuring the Parking Functionality” on page 332
12.2.1 Configuring Transactions to Create Parked Invoices

In this step, you configure the transactions that create parked Non PO invoices. Any
parked Non PO invoice that is created with these transactions triggers a
corresponding workflow in VIM.
To configure transactions to create parked Non PO invoices:
Constant NONPO_INV_TCODE.
4. Enter the Constant Value: FV60;FB60;/PTGWFI/LIV_CHG_PKRS;/

PTGWFI/PIR_CHG_PKRS;
VIM070500-03-CGD-EN-1
12.2.2 Configuring Dashboard Screen Exits

Example: After you have selected a particular parking reason, you want a particular
subscreen to appear as shown in the following screenshot.
To configure dashboard screen exits:
1. Copy the OpenText delivered header program and subscreen.
Note: We strongly recommend that you copy the program and subscreen
VIM070500-03-CGD-EN-1
2. To access the configuration for PIRPROG and PIRSCREEN, run the /

Invoice Configuration > Parked Invoice Processing Configuration > Technical
Configuration > Dashboard Screen Customization > Dashboard Screen Exits.
3. Configure PIRPROG and PIRSCREEN, using the following parameters:
VIM070500-03-CGD-EN-1
Constant: PIRPROG
Usage
Subscreen program for Non PO parked invoice dashboard header
subscreen. To provide additional data on the invoice dashboard, you
can define your custom screen here.
Default Value
/PTGWFI/PIR_SUBSCREEN01
Constant: PIRSCREEN
Usage
Subscreen number for Non PO parked invoice dashboard header
subscreen. To provide additional data on the invoice dashboard, you
can define your custom screen here.
Default Value
9901
12.2.3 Defining a Preprocess (Sub)workflow

In this step, you define a custom (sub)workflow that needs to be triggered before the
Non PO parking workflow process is triggered.
This custom (sub)workflow can do some actions that are not delivered in the VIM
standard process. For example, it can notify an agent that a Non PO invoice is
parked and waiting to be further processed. The (sub)workflow can also update
some monitoring custom tables.
To define a preprocess (sub)workflow:

Configuration > Advanced Process Customization > Pre-process
(sub)Workflow.
VIM070500-03-CGD-EN-1
2. Configure the Constant Value that is used to trigger a custom (sub)workflow

before triggering the Non PO parking workflow process.
Default Value: None
12.2.4 Configuring Binding Function Module Exits

In this step, you define custom function modules that can transfer (parked invoice
related) data to the OpenText delivered workflow processes for the Non PO parking
process. Using such exits, you can manipulate the workflow container of the process
or populate VIM tables with custom data.
If maintained, these exits will be called in function module /

PTGWFI/PIR_F_PSS_BINDING during inward or outward binding accordingly.
To configure binding function module exits:

Configuration > Advanced Process Customization > Binding Function
Module Exit > Dashboard Step (Binding Exits).
Usage
Default value
None
Usage
VIM070500-03-CGD-EN-1

Default value
/ORS/000007_PIR_PSS_BIND_O
Note: Do not change this value. If you need some additional

information to be captured for analytics or other purposes, first
call the standard function /ORS/000007_LIX_PSS_BIND_O within
your function. Otherwise, unexpected failures in the Non PO
parking process or subsequent processes may occur.
12.2.5 Configuring the Pre PSS Method Exit

In this step, you define custom function modules that will manage custom data
before calling the dashboard.
Example: If the custom data is added to VIM tables and it should be displayed in the
Dashboard in some way, the data must be managed (manipulated) in such method exits.
If maintained, this exit will be called in method SELECTPROCESSLIX of the Object

type /OPT/VIM_BIR. It is called before calling the dashboard.
To configure the pre PSS method exit:

Configuration > Advanced Process Customization > Pre PSS Method Exit
(Non PO).
2. Configure the pre PSS method exit, using the following parameters:
Constant Value
This value is used to manage document data before calling the dashboard.
Default value
None
VIM070500-03-CGD-EN-1
12.2.6 Configuring the Post PSS Method Exit

In this step, you define custom function modules that will manage custom data after
calling the dashboard.
Example: Custom data is added to VIM tables and it is displayed in the dashboard. This
custom data can be changed in the dashboard. After the dashboard is quit, the data must be
saved. This can be done in the post PSS method exit.
If maintained, this exit will be called in method SELECTPROCESSLIX of the Object

type /OPT/VIM_BIR. It is called after the dashboard is processed.
To configure the post PSS method exit:

Configuration > Advanced Process Customization > Post PSS Method Exit
(Non PO).
2. Configure the post PSS method exit, using the following parameters:
Constant Value
Default value
None
VIM070500-03-CGD-EN-1
12.2.7 Configuring a Post Process (Sub)workflow

In this step, you define a custom subworkflow that will execute after completing the
Non PO Parked Invoice document process.
This custom (sub)workflow can do some additional action that is not delivered in
the VIM standard process, for example to notify an agent that the process is
completed, or to update some VIM/custom tables with corresponding data.
To configure a post process (sub)workflow:

Configuration > Advanced Process Customization > Post Process
(sub)Workflow.
2. Configure a post process (sub)workflow, using the following parameters:
Constant Value
If you want to call a custom subworkflow after completing the Non PO
parking process, you can define a workflow template / task here.
Default value
None
VIM070500-03-CGD-EN-1
12.2.8 Configuring an Autopost Exit

In this step, you define a custom function module that will manipulate data of the
Non PO parked invoice and/or post the document automatically.

postparkedinvoice of the object type /OPT/VIM_FIPP. The custom function
module is called before the standard posting logic for the Non PO parked invoice
document is applied. If there is any exception thrown by this function module, the
workflow will run out of the posting step without doing any further action.
To configure an autopost exit:

Configuration > Autopost Global Configuration > Autopost Exit Function.
2. Configure an autopost exit, using the following parameters:
Constant Value
Enter a function module. This function module can be used to post a
document automatically using a custom function. If the function module
configured here raises an exception, the document will not be posted.
Default value
None
Interface
PTGWFI/PIR_F_TMP_PRE_AUTOPOST.
VIM070500-03-CGD-EN-1
12.2.9 Configuring a Parked Document Posting Exit

In this step, you define custom function modules that will perform any post process
transaction after the document is posted.

postparkedinvoice of the object type /OPT/VIM_FIPP. It is called after the Non PO
parked invoice has been posted. This exit can be used for example to update VIM or
custom tables with additional data or to perform any action after the document is
posted.
To configure a parked document posting exit:

Configuration > Autopost Global Configuration > Parked Document Posting
Exit (Non PO).
2. Configure a parked document posting exit, using the following parameters:
Constant Value
Enter a function module. This function module can be used to post process
data after an invoice document is posted.
Default value
None
Interface
PTGWFI/PIR_F_TMP_POST_EXIT_FM.
VIM070500-03-CGD-EN-1

In this step, you define custom function modules that will display an SAP
ArchiveLink image associated to the Non PO invoice document.

Configuration > Image Display > Image Display Function Non PO.
Constant Value
Enter a function module. This function module can be used to display an
SAP ArchiveLink image associated to the Non PO invoice document.
Default value
/PTGWFI/BIR_F_TMP_DISP_IMG
Interface
PTGWFI/BIR_F_TMP_DISP_IMG.

You can configure that images are automatically displayed when the Non PO
Invoice Dashboard is opened.
VIM070500-03-CGD-EN-1
12.2.12 Configuring a Parallel Workflow Exit

In this step, you define custom function modules that will call any workflow parallel
to the Non PO parking workflow.
If maintained, this exit will be called in the method executetransactionpir of the

Object Type /OPT/VIM_FIPP.
To configure a parallel workflow exit:

Configuration > Others > Parallel Workflow Exit.
2. Configure a parallel workflow exit, using the following parameters:
Constant Value
You can use this value to call any workflow parallel to the Non PO parking
workflow.
Default value
None
12.2.13 Configuring the Parking Functionality

In this step, you define custom function modules that activate the parking
functionality.
The function module maintained here will be called in /

PTGWFI/PIR_F_TRIG_USER_EXIT2, which in turn is called in function module /
OPT/BTE_IF_00002213_47.
To configure parking functionality:
VIM070500-03-CGD-EN-1
3. Look for Product Code PIR and Constant USR_EXIT_GET_DATA_FM and double-
click the line.
4. Configure the parking functionality, using the following parameter:
Constant Value
Enter a function module to be used to activate the parking of PO invoice
documents.
Default value:
Blank.
Baseline does not offer parking.
Optional value:
/PTGWFI/PIR_F_GET_PARK_DATA_N
This is the standard parking implementation function module.

Function module /PTGWFI/VIM_CRE_NPO_INV_PREF populates the new invoice with

a subset of the header data of the deleted document:
• Company code
• Document date
• Vendor reference number
• Currency
• Vendor number
VIM070500-03-CGD-EN-1
You can insert the function module in the corresponding Z constants or you can
create an own logic on basis of this function module.
For the creation of a Non PO invoice, maintain table /PTGWFI/Z_CONST, using the
SM30 transaction. In Product Code PIR, Constant CREATE_BDC_FM, enter Constant
Value /PTGWFI/VIM_CRE_NPO_INV_PREF.
Note: The existing function module /PTGWFI/VIM_CRE_NPO_INV calls

transaction FB60 without populating data.
VIM070500-03-CGD-EN-1
Chapter 13
Invoice Approval
Invoice Approval (IAP) is the component of VIM that handles the approval
processes for both Non-PO based and PO based invoices.
13.1 Overview
Level-based approvals can be done as line-based (sequential or parallel flow) and
header-based approvals. For details about level-based approval, see “Configuring
Approval Flow Settings” on page 353.
Features of Level-based approval provides the following set of features:

level-based
approval • Header-based approval
• Sequential approval
• Parallel approval
• Extended approval log
• Approval buffer
• Skipping COA levels
• Inheriting of permissions by substitute
Supported Approvals can be handled at the DP processing stage, after the DP invoice is
invoice types converted in to an SAP parked document, or after the invoice is posted.
DP approval
For DP-document-based approval, the process type for DP approval needs to be
configured in the system. For more information, see “Configuring the Process
Type” on page 338.
Parked approval
In case of parked document approval, the invoice has to be parked with an
appropriate parking reason before an approval process can start. Depending on
the parking reason configuration, an approval workflow starts. For more
information, see “Configuring the Parking Reason” on page 338.
Posted approval
For posted approval, depending on the configuration for this type of approval,
the approval process will be started after the document is posted either in
background or manually with some payment block. For more information, see
“Configuring Posted Approval” on page 341.
VIM070500-03-CGD-EN-1
Chapter 13 Invoice Approval
Approval in The approval workflow supports approvals inside SAP GUI, and outside of SAP
SAP GUI, web, GUI, if the optional OpenText Approval Portal or Mobile Approval Portal is
and mobile
implemented.
Approving invoices in the Approval Portal or in the Mobile Approval Portal does
not require an SAP user ID. Users can be authenticated through the SAP NetWeaver
Portal or the Windows domain instead. However, you must ensure, like with any
other solution, that the indirect usage of SAP data is properly licensed.
The Approval Portal provides a concise and user-friendly web interface for
approving invoices. The interface is designed to deliver the right amount of
information to enable approvers to make a quick decision.
With the Mobile Approval Portal, you can use mobile devices like an iPad, an
iPhone, an Android smartphone, or a Blackberry device for approval purposes. In
the Mobile Approval Portal, coding is not available.
People involved There are several people (roles) that are involved in the IAP process. The actual
in the IAP names might be different, but the activities are the same.
process
Coder
The person who is responsible for entering accounting data. The coder can be
both an SAP user and/or a web user if Approval Portal is implemented.
Goods or Service Requester (Requisitioner)
The person who requested the goods or the service.
Approver
The person who is responsible for approving the invoices. The approver can be
an SAP user or a web user if Approval Portal or Mobile Approval Portal is
implemented.
AP Processor
A member of the Accounts Payable (AP) department who deals with invoices.
The roles that are part of this process are different from the standard roles described
in “Roles“ on page 43. Because the functional requirements are different for IAP
roles compared to other exception processes, a separate role infrastructure is
required. For more information, see “Roles in the IAP Process” on page 390.
Workflow
• The approval workflow is a new subworkflow. Approval steps are a technically
different dialog task, separate from the parking or DP dashboard tasks for the
other VIM workflows.
• The approval workflow supports multi-step approval. For Non PO invoices, you
can achieve this by configuration. For PO invoices, a custom extension is
required. From baseline, PO invoices go through only one approval step, by the
requester of the PO.
• The approval subworkflow is completed when either the Approved completely
or the Rejected completely flag is set on the monitor table.
VIM070500-03-CGD-EN-1
13.1. Overview
Trigger for the The way the IAP process is triggered depends on the kind of invoice document.
IAP process
For parked invoice documents
When an invoice is parked with a parking reason that requires invoice approval,
the IAP workflow is initiated. You can trigger the subworkflow either by
configuring the parking reason to be Auto submit for approval or by clicking
the Submit for approval option. It is possible to delay the start of the IAP
process by first sending the invoice to the AP processor who can subsequently
submit the invoice for approval.
For DP invoice documents

The approval subworkflow can be triggered by configuring the Process Type to
be Auto submit for approval or by clicking the Submit for approval option.
For posted invoice documents

The approval subworkflow can be automatically triggered right after the invoice
is posted. Therefore, the document type must be configured accordingly.
Another way to trigger the approval subworkflow is to click specific process
options created for that purpose.
End of the IAP There are several activities that mark the end of the IAP process:
process
• The invoice is finally approved and posted.
• The invoice is deleted or posted (only for parked invoices).
• The invoice is completely rejected.
• Approval is recalled. The process goes back to DP or parking workflow.
Configuration This section outlines all the aspects of implementation and configuration of the IAP
outline of the component of VIM.
IAP process
Note: You can perform most of the configurations using the VIM Customizing
IMG with the /OPT/SPRO transaction code.
To configure the IAP process, the following steps are necessary:

• Identify the approval parking reasons or process types.
• Identify any parking reason info that needs to be collected during the parking
step.
• Determine the user framework to be used. This deals with configuring or
extending the /ORS/USERMAPPING class.
• Identify the approval steps:
• Identify who is responsible for account assignment (Coder role).
• Identify approval logic:
• Who is the first approver?
• How to go up the approval chain (if needed)?
VIM070500-03-CGD-EN-1
• What marks the end of approval?

• What needs to happen in case of rejections?
• Identify the account assignment screen layout and logic:
• Identify fields to be displayed.

• Identify validation requirements.
• Identify how to display the image during the approval process.
• Identify and configure any global customizing parameters.
13.2 Configuring the Process Type

In case of DP invoice approval, the starting point of the IAP process is the start of the
DP workflow. The DP workflow goes through the process types configured for the
particular DP Document Type. One of the process types needs to be configured for
approval workflow. See “Defining the Process Type” on page 225 for details.
The following screenshot shows the standard process type configuration delivered
for the DP IAP process.
13.3 Configuring the Parking Reason

For parked invoice approvals, the starting point of the IAP process is the parking of
an invoice. The parking reason chosen determines whether an IAP process is
triggered or not. If the parking reason is Approval Required, the IAP process will
be triggered. In that case, the requestor or requisitioner information needs to be
entered in the Choose Parking Reason dialog box so that the IAP process can start
correctly.
To configure the parking reason for PO invoices, run the /n/OPT/SPRO transaction
and navigate to Vendor Invoice Management > PO Based Invoice Configuration >
Parked Invoice Processing Configuration > Park Reason Maintenance > Parking
VIM070500-03-CGD-EN-1
13.3. Configuring the Parking Reason
Reason Definition Maintenance. For details, see “Configuring Parking Reasons”

on page 272
To configure the parking reason for Non PO invoices, run the /n/OPT/SPRO
transaction and navigate to Vendor Invoice Management > Non PO Based Invoice
Configuration > Parked Invoice Processing Configuration > Park Reason
Maintenance > Parking Reason Maintenance.
The following screenshot shows the standard parking reason configuration

delivered for the Non PO IAP process.
For the Non PO IAP process, the following dialog box serves to capture the
requester information:
VIM070500-03-CGD-EN-1
If you need to capture custom logic or customer data during the parking process to
initiate the approval workflow, you have to replace the above screen with a custom
screen. For details, refer to “Configuring Parking Reasons (Non PO Parking
Process)” on page 315.
13.3.1 Configuring Trigger Points for the Parked Invoice

Approval Workflow
In this step, you configure which parking reasons should trigger the IAP process.
To configure trigger points for the approval workflow:

Management > Invoice Approval Configuration > Approval Workflow >
Additional Configuration - Web Approval.
2. Configure the trigger points for the approval workflow, using the following
parameters:
VIM070500-03-CGD-EN-1
13.4. Configuring Posted Approval
BLOCKRSN
• Block Reason 9 is for PO based invoices.

• Block Reason V is for Non PO based invoices.
Start Approval Immediately

Select this check box to start the approval workflow immediately
disregarding the delay function module.
13.4 Configuring Posted Approval

As an enhancement to Invoice Approval, VIM supports the approval of posted
documents, besides the approval of parked or DP based documents.
Benefit Besides the PO blocking scenarios, the VIM process ends with the creation of a
posted document. The posted approval processing enables you to post a Non PO or
PO invoice as fast as possible with an individual blocking reason. Then you can
approve the document with the approval workflow after the document creation.
Invoices do not need to go into a long approval process and then are posted finally.
With posted approval, they are posted before any approval process is started.
Workflow The posted approval subworkflow is available for blocked posted documents that
are processed within the DP process. Stand-alone parked or posted documents are
not supported. You can trigger the subworkflow in one of the following ways:
• Document is manually posted with one of the individual configured payment
blocks.
• Document is automatically posted from DP with a special payment block. The
approval workflow is started automatically.
• Document is automatically posted with specific payment block after the
requester step in approval workflow.
For the posted PO approval scenario, either the existing blocking workflows are
triggered or the approval process is started depending on the posted approval
configuration.
With the final approval of the posted document, the individual payment block is
removed.
Automated In combination with the automatic processing of the posted approval, the coding
coding step can be completely skipped.
Configuration The whole configuration for the posted approval is integrated in the OpenText
aspects Configuration tree: Navigate to Vendor Invoice Management > Invoice Approval
Configuration > Approval Workflow.
To configure the posted approval process, the following steps are necessary:
1. Configure posted approval settings (mandatory)
VIM070500-03-CGD-EN-1
2. Configure event linkage for posted approval trigger and configure the event
queue processing job using transaction SWEQADM (mandatory)
3. Define dynamic determination for the auto processing:
Note: This step is optional: If you configure to use the determination for
the automatic posted approval activation type, then you have to process
this step. If you activate it always or by custom function module, you do
not need to process this customizing.
13.4.1 Configuring Posted Approval Settings

You must configure the posted approval settings for each document type. This
section describes the possible configuration. You must configure it individually; it is
not delivered with baseline configuration.
To configure posted approval settings:

> Invoice Approval Configuration > Approval Workflow > Setup Approval
Chain > Posted Approval Settings.
2. Double-click the DP Document Type that you want to configure.
VIM070500-03-CGD-EN-1
3. Configure the Posted Approval Settings (PAS), using the following parameters:
Process Type
Baseline delivers the process type 149 for PO documents and the process
type 249 for Non PO documents. A posted document that is rejected in the
approval process will be processed within the DP workflow with this
process type. For this process type, baseline delivers the following process
options:
2020
Re-Submit for Approval
2021
Submit for one step Approval
2022
Remove payment block and complete DP
2023
Keep payment block and complete DP
Automatic processing
For Non PO documents

In the DP process, a document can be submitted for approval (manually
or automatically with exception “Approval required”). In this case, the
automatic processing defines that the DP or parked approval process
terminates after the requester step, for the time being. The document is
posted with the configured payment block. After posting, the approval
process is resumed, starting with the first approver step.
When the coding happens in background with auto coding (see
“Configuring Auto Coding” on page 169), also the coding step can be
skipped and the document will be posted directly.
For PO documents
The automatic processing defines that the document is posted
automatically with the configured payment block.
Activation type
• Inactive: Automatic processing is deactivated.
• Active: Automatic processing is activated globally for document

type
• Activate by determination: Automatic processing is activated
dynamically; see “Configuring Posted Approval Determination”
on page 348.
• Activate by custom function: Automatic processing is activated
dynamically with custom logic. Maintain the Posted Approval
Finder field. The field is only available if you select this activation
type.
VIM070500-03-CGD-EN-1
Payment Block
This field is available if posted approval is activated.
Enter the payment block that is used to post the document in the
automatic processing.
Posted Approval Finder
Enter the exit function to activate the automatic processing (interface
check function /OPT/AAFS_DETERMINE_PAS).
Manual processing
For Non PO and PO documents, the configuration of the manual processing
defines that the posted approval process is triggered for manually posted
documents with the configured payment blocks.
Activation type
• Inactive: Manual processing is deactivated.

• Active based on payment block: Manual processing is activated.
Constant Value
Enter Constant Values for payment blocks: Possible payment blocks for
which the posted approval is relevant to be triggered. Maintain the
standard Payment blocks of table T008. Separate them by comma.
PO blocking reason processing
Only relevant for PO based documents: You can maintain an additional
start condition to trigger either the blocking workflow or the approval
workflow, based on the logistic blocks of the invoice.
Approval start cond
Select an approval start condition from the list:
• Start always: The approval workflow is triggered always. The

blocking workflow(s) are not triggered.
• Start only when no logistic block exists: The approval
workflow is only triggered if no logistic block exists. If any logistic
block exists, the blocking workflow(s) are triggered.
• Start only when no logistic block exists besides price: The
approval workflow is only triggered if no block or a price block
exists. For all other logistic blocks, the blocking workflow(s) are
triggered.
Reject processing
Approval restart options
Rejected invoices are processed within DP processing with the
configured process type. This refers to the baseline process options
Submit for one step Approval and Resubmit for Approval for the
baseline Posted Approval process types. The document is submitted
again for approval processing. For these options, you can configure the
following individual settings.
VIM070500-03-CGD-EN-1
Comments Required
Select this check box to determine that a comment is required
within the Resubmit for Approval screen. This comment is used in
the approval process. It is not logged for the process option, which
can also be activated in the process option configuration.
Appr. Search Option

For one step approval, define the search and check functionality for
the selected approver. Possible entries:
Search all User COA

You can select all users from the COA that are configured for
approval.
Search only legitimate Approver COA

You can select users from the COA that are configured for
approval and where also the configured COA fields correspond
to the invoice data (Company Code / Cost Center, ...).
Note: The amount of the invoice is not checked!
Reject by Requester
An automatic processed DP document for posted approval is directly
sent to the assigned approver of the COA during the approval process.
In this scenario, the coding and requester step is already executed.
When the approver rejects the document, it is sent to the previous
approver. With posted approval, the requester is not always the first
approver. It may happen that the requester does not receive the rejected
document.
Select this check box to determine that the document is finally sent to
the requester when the approver rejects the document before the
approval workflow ends.
Processing Exits
You might want to individually trigger the posted approval process and to
keep the DP workflow alive for the posted document. Therefore, you can
maintain custom functions. The payment block, which will be removed in
the final approval step, can be processed individually, as well.
Exit remove block

Enter an exit function to be executed after the final approver approves
the document. With standard configuration, the header payment block
on the posted document is removed. The document will be paid no
matter if there are any blocks on the PO document like price or
quantity.
The interface of the exit function has to be compatible with the
function /OPT/AAFS_CHANGE_BLOCKING_NPO for Non PO documents
and /OPT/AAFS_CHANGE_BLOCKING_PO for PO documents.
VIM070500-03-CGD-EN-1
Exit trigger approval

Integrate an own logic for the posted approval to trigger the processing
according to your end conditions.
All other configurations to trigger the process manually or
automatically are not taken into account (maintained within /
OPT/AT_PAS). Only the own logic within the exit function is used. The
interface of the exit function has to be compatible with the function /
OPT/AAFS_SAMPLE_EXIT_TRIGGER.
Exit confirmation
Integrate an own logic for the posted approval to keep the DP process
alive according to your start conditions. All other configurations to keep
the process alive according to the manual or automatic blocking are not
taken into account (maintained within /OPT/AT_PAS). Only the own
logic within the exit function is used. The interface of the exit function
has to be compatible with the function /
OPT/AAFS_SAMPLE_EXIT_CONFIRM.
13.4.2 Configuring Event Linkage for Posted Approval

To trigger the posted approval after the document is posted, the following
configuration is necessary for Non PO and PO documents.
Run the SWETYPV transaction and activate the event linkage for the posted approval.
The following screenshot shows the relevant settings.
VIM070500-03-CGD-EN-1
Object Type
/ORS/INVAP
Event
POSTED
Receiver Function Module

/OPT/AAFS_POST_RECEIVER
Linkage Activated
Selected
Enable Event Queue

Selected.
You must maintain the event queuing and configure a job (transaction SWEQADM).
Non PO For Non PO documents, the event is raised in the BTE exit 1050 and exit 1030 within
exit function /OPT/BTE_IF_00001050 and /OPT/BTE_IF_00001030. The
corresponding BTE has to be activated. Check transaction FIBF > Settings > P/S
Modules -> …of a partner.
PO For PO documents, the event is raised in the event receiver of function /

OPT/BL_PO_BLK_RECEIVER, which is triggered in the event linkage for object
VIM070500-03-CGD-EN-1
BUS2081 and event POSTED. Check transaction SWETYPV and see “Event Linkages”
on page 81.
13.4.3 Configuring Posted Approval Determination

You can dynamically determine the automatic posted approval processing. The
activation is done within the posted approval settings; see “Configuration aspects”
on page 341.
Note: This step is optional: If you configure to use the determination for the
automatic posted approval activation type, then you have to process this step.
If you activate it always or by custom function module, you do not need to
process this customizing.
13.4.3.1 Defining Determination Fields

You can individually configure the fields for the dynamic determination of the
posted approval processing.
To define determination fields:

Chain > Posted Approval Determination Procedure > Determination - Fields.
The following screenshot shows the configuration of two fields that will be used
for the determination.
2. Define determination fields using the following parameters:
Determination Type
Enter PAS (Posted Approval Settings)
The determination type is defined in table /OPT/AT_DETTYPE. The type PAS
is delivered within the posted approval baseline configuration.
Field Type
Field Name
table.
VIM070500-03-CGD-EN-1
Sequence
Search Help Name

configuration.
Allow Ranges
configuration.
13.4.3.2 Defining Determination Data

You can individually configure the data for the dynamic determination of the posted
approval processing, based on the defined fields.
To define determination data:

Chain > Posted Approval Determination Procedure > Posted Approval
Determination - Data.
“Defining Determination Fields” on page 348.
2. To activate the automatic posted approval configuration, configure the

corresponding ranges and data. You can add or remove lines.

A transport is created for the corresponding settings.
VIM070500-03-CGD-EN-1
13.5 Implementing Invoice Approval

This section describes the implementation of the overall IAP process as far as
process logic is concerned.
• “Defining Multi Level Approval” on page 350
• “Driving the Approval Flow for DP Invoices” on page 351
• “Driving the Approval Flow for Parked Invoices” on page 351
• “Defining Approval Hierarchy and Approval Level” on page 352
• “Configuring Approval Flow Settings” on page 353
• “Defining the Expense Type” on page 362
• “Defining Rejection Reasons” on page 363
• “Cross Company Coding” on page 368
• “Configuring the Email Notification” on page 369
• “Configuring the Certify Message” on page 373
• “Configuring Fields for Invoice Approval” on page 375
• “Configuring Search Help for Web Screen Fields” on page 388
13.5.1 Defining Multi Level Approval

Note: For PO invoices, a custom extension is required for multi level approval.
From baseline, PO invoices go through only one approval step (by the
requester of the PO).
To define a multi level approval process, you have to consider the following aspects:
• How to identify the first approver?
• Who should approve the invoice after the current approver approves the
invoice?
• When is an invoice considered finally approved?
VIM070500-03-CGD-EN-1
13.5. Implementing Invoice Approval
13.5.2 Driving the Approval Flow for DP Invoices

The IAP process starts when a DP PO invoice or a DP Non PO invoice gets the
process type for approval or a user from the Accounts Payable (AP) department
specifically clicks the option Submit for Approval from the DP dashboard. In case of
a DP Non PO invoice, the initial approver is usually entered in the indexing screen
in the field Email Id. For DP PO invoices, the initial approver is picked up from the
requisitioner of the PO. The user from the AP department has the option to choose
the initial approver if the IAP process is started from the DP dashboard.
The subsequent approvers (only for Non PO invoices) are determined when the
current approver approves the invoice. The system determines the next approver
according to the settings in the COA. In the level based approval, the approver is
determined by:
• company code (company code of invoice line(s))
• approval level
• cost object assignment (cost object of invoice line(s))
If the current approver rejects the invoice, the invoice is sent to the previous
approver or to the initial coder, or the complete approval flow is cancelled. This
depends on the configuration of the rejecting process.
All approvers who approve the invoice are stored in the approval stack. So, in case
the current approver rejects the invoice, the system knows the last approver. If the
first approver rejects the invoice, the invoice is sent back to the AP department.
13.5.3 Driving the Approval Flow for Parked Invoices

The IAP process starts when a PO or Non PO invoice is parked, or someone from the
Accounts Payable (AP) department specifically chooses the action Submit for
Approval from the Process Selection Screen. The initial approver is usually entered
when parking the document. Sometimes, the initial approver may be entered as part
of the invoice indexing before parking the SAP document.
Notes
• Implementation note
When you enter the first approver at the parking reason screen or indexing
screen, and you are using search help, OpenText recommends using the
combination of last name, first name and email address. If the combination
fails to identify one user, the system may suggest a list of matching users.
• Technical note
The initial approver is usually stored in the parking monitor table (/
PTGWFI/F_PIRMTR) and retrieved by the /ORS/APPROVER-> NEW method.
The subsequent approvers (only for Non PO invoices) are determined when the
current approver approves the invoice. The system determines the next approver
VIM070500-03-CGD-EN-1
according to the settings in the COA. In the level based approval, the approver is
determined by:
• company code (company code of invoice line(s))
• approval level
• cost object assignment (cost object of invoice line(s))
If the current approver rejects the invoice, the invoice is sent to the previous
approver or to the initial coder, or the complete approval flow is cancelled. This
depends on the configuration of the rejecting process.
All approvers who approved the invoice are stored in the approval stack so that in
case the current approver rejects the invoice, the system knows who the last
approver was. If the first approver rejects the invoice, the invoice is sent back to the
AP department.
Technical Notes
• You can configure who receives the work item after the first approver rejects
the invoice. You perform this configuration in the parking reason table /
PTGWFI/F_PRKRSN for a non-PO invoice or /PTGWFI/M_PRKRSN for a PO
invoice. See “Configuring the Parking Reason” on page 338.
• The approval is considered completed if the current approver has sufficient
authorization for the invoice amount and cost elements.
• You can redefine determination conditions using an extension.
13.5.4 Defining Approval Hierarchy and Approval Level

There are several ways to implement hierarchy and approval level (authorized
amount that an approver may approve):
OpenText delivered approval hierarchy table

With level based approval, settings need to be considered on the COA (see
“Maintaining Chart of Authority” on page 54) and other approval flow settings
(AFS; see “Configuring Approval Flow Settings” on page 353).
The main objective of the level based approval is, that each invoice in a company
is processed in an approval hierarchy, which is associated with different
approval levels. When an invoice or invoice lines are approved on one level by
one or more users, the system checks if an additional approval level is necessary
based on the limit assigned to the approval level.
In the level based approval, the following approval levels are differentiated:
Coder level
The invoice is coded by a dedicated coder. The coder is assigned to a
requester, additionally with company code, see Coder Processing
on page 357. The coder is able to change or delete invoice lines or to add
additional invoice lines. The cost objects entered by the coder are checked
against the COA. As long as there still are invoice lines that have not been
VIM070500-03-CGD-EN-1
approved yet, and that cannot be approved by the current coder, the
document must be forwarded to the next coder until the document is
completely coded and approved. When the document is completely coded
on the coding level (level 0), the document must be processed in the
requester level because there is no limit assigned to the coder level.
Requester level
Coding has been processed. This can also happen on requester level, see
Coder Processing on page 357. Now the invoice is processed on requester
level. If there has been a coder step before, the requester cannot change the
data. If there has been no coder step, the requester can change the data.
Similar to the coder level, all invoice lines are checked against the COA and
the document is forwarded until all lines are approved. Compared to the
coder level, there is the following difference: According to the approval
scenario (header or line based), the invoice or invoice lines can already be
finally approved in the requester level (level 1) if the approval limit of the
requester is sufficient.
Approval level
The approval level is processed according to the approval scenario (header
or line based). The invoice or the invoice lines are processed on one level. It
is checked if additional approval levels have to be processed after one level
has been finished. On the approval level, the invoice cannot be changed any
longer by the approver.
Totally customized solution
VIM is structured in such a way that the approval hierarchy logic can be totally
customized to suite the customer’s business needs.
Technical note
Approval hierarchy and level logic can be customized by extending methods in

the class /ORS/APPROVER.
13.5.5 Configuring Approval Flow Settings

In baseline, level-based approval is considered only for Non PO document types.
For PO document types, a one-step approval is provided by default.
Important
For PO document types, level-based approval cannot be used. Still, only the
“old” simple approval is supported.
To configure an approval with more than one step for PO document types, a custom
extension is required.
Settings need to be considered on the COA (see “Maintaining Chart of Authority”

on page 54) and other approval flow settings (AFS), as described in this section.
Level based approvals can be done header based or line based (sequential or parallel
flow). Levels are defined against approval limits. A pack is defined as a group of
VIM070500-03-CGD-EN-1
lines that are assigned to an approver and that this approver can approve; this
means, the approver has the corresponding authorizations of the cost elements.
Header based processing

The approver is determined by the COA Authority settings. For each user, the
system determines a pack of lines that can be approved due to COA settings.
The user with the highest pack amount (consists of all approvable lines) is
proposed to be the next approver.
When the user opens an approval work item, he acts on header level and
therefore his authorizations for different cost centers and so on are no longer
important. Only the Approval Limit from the COA is relevant to finally approve
the invoice or not.
For more information, see “Configuring Header Based Approval” on page 396.
There are two different limit checks, which can be set in the COA for header
based approval:
Highest pack only scenario

The first limit check just checks the total invoice amount against the
configured limit in the COA.
All pack scenario

The second limit check checks the approvable lines due to COA (pack)
against the approval limit of COA, and it also checks the remaining lines
against the configured Additional Limit of the current level.
For more information, see “Approval Limit/Level View” on page 60.
Line based - sequential processing

The approver is determined by the COA, where you can calculate the approver
by approvable lines. After all packs (lines) within one level are approved, the
next approval level is processed. Therefore, the pack amount is checked against
the limit of the approval level to determine if the pack (lines) is already finally
approved. Approval is completed when all lines are finally approved.
Line based - parallel processing

Similar to sequential line based processing. However, if several approvers are
needed within the same approver level, the approval workitems are sent to all
approvers at the same time. This does not apply to coder or requester levels. For
more information, see “Using Parallel Approval” on page 397.
To use the level based approval, you must configure approval flow settings (AFS).
These settings are divided into the following parts:
• Approval flow settings (AFS) (mandatory)
• Mapping of approval flow settings to VIM document type (mandatory)
• Defining dynamic determination
Note: This action is optional: If you configure to use the determination for
the mapping activation type, you must perform this action. If you activate it
VIM070500-03-CGD-EN-1
always or by custom function module, you do not need to perform this

customizing.
For more information, see “Maintaining the Level Based Approval Flow
Important
OpenText recommends that you do not change the settings of the AFS ID if
there are still open approval processes that were started with this AFS ID.
To configure approval flow settings:
Invoice Approval Configuration > Approval Workflow > Setup Approval
Chain > Approval Flow Settings.
Note: You can access the field configuration for the invoice detail page for
a selected AFS ID, from here: Select an AFS ID, and, in the Dialog
Structure, double-click Maintain Invoice Detail Fields or Maintain
Coding Fields Mapping. For more information, see “Configuring Fields
for the Invoice Detail Page” on page 376.
The AFS ID represents a template for an approval flow. To use an AFS ID, it
must be mapped against a VIM document type. For more information, see
“Maintaining the Approval Flow Settings Mapping” on page 359.
VIM070500-03-CGD-EN-1
2. Configure AFS settings, using the following parameters:
AFS ID
Unique ID for the global approval settings
Important
To keep your system manageable, do not create too many AFS IDs.
Preferably, use the detail configuration to set up the AFS settings.
Approval Flow
Explanation
Detail description of the AFS
AFS Type
Select one of the following AFS types:
H - Header Based Approval
Header based approval is based on the gross amount of the invoice.
S - Line Based - Sequential
Line based approval is based on the line items amount. Sequential
approval sends the invoice to one approver after the other.
P - Line Based - Parallel
Parallel approval allows to send the invoice to more than one approver
at the same time.
Process Classes
Approver Class, Usermap Class

You can define custom Approval Class and Usermap Class. By default, the
following VIM custom classes are used:
Approver class: /OPT/CL_A_LEVEL_BASED_APPROVAL
Usermap class: /OPT/CL_IAP_USERMAP_BL
NPO Invoice Class, PO Invoice Class
You can define custom Invoice Classes. By default, the following VIM
custom classes are used:
NPO invoice class: /ORS/NON_PO_INVOICE_NEW
PO invoice class: /ORS/PO_INVOICE_NEW
Approval Limit
Amount Base
Select Gross Amount or Net Amount. If the AFS Type is Header, approvals
are always based on gross amount.
COA Currency
Select Fixed Currency (Define the currency in the Currency field.) or
Company Code Default Currency.
VIM070500-03-CGD-EN-1
Conversion Date
Select the conversion date for currency conversion. Possible values: Current
System Date, Date on the Vendor Invoice, Date per Function Module.
Conversion FM
If you have selected Date per Function Module in the Conversion Date
field, enter the function module to determine the currency conversion date.
Template: /OPT/DETERMINE_CONVERSION_DATE
Automation Processing
Fallback User FM
Enter a function module to determine a fallback user. A fall back user will
always be available in the user search dialogs (next coder, next requester, or
next approver) if no user can be found in the COA. The purpose of the fall
back user is to send the invoice to a user who takes care to correct the COA
settings. Therefore, you must set up the fallback user with the user details in
the COA.
Template: /OPT/FALLBACK_USER_TEMPLATE
Automatic Forward
Select this check box to let the system automatically choose the next user
within one approval level. It is not possible to change this user.
Note: Automatic Forward is not considered for the Approval Portal.
Coder Processing
Coder Determination
Coders can be defined for each document type. Select one of the following
options:
By Requester
Each requester has an associated coder.
By Company Code
Each company code has an associated coder.
Both Requester and Company Code

The coder is determined by both requester and company code.
Use Requester
The coder is the requester.
Coder Determination FM
You can customize the coding functionality by defining your own function
module. See “Approval Flow Settings Function Modules” on page 361.
Template: /OPT/DETERMINE_CODER_TEMPLATE
VIM070500-03-CGD-EN-1
Use SAP field seq.

Select this check box to use the customized Approval Portal item field
sequence also for the SAP GUI approval screens.
Requester Determ.
Determine the first requester after the coding step. Select one of the
following values from the list:
Determine Requester by COA
The first requester is determined by the maintained data from the COA.
Use Requester from Invoice
The first requester is determined by the email address on the invoice.
Important
You can configure the requester determination using the same COA
logic as used to determine coders (except the first coder) and
approvers. However, this is only supported if you work with real
coders, that means, if you have two steps, first coding and then
requester. If you have configured that “coder = requester”, VIM uses
the requester field from the invoice.
Rejection Processing
Reject Process Type

Select one of the following options:
One Step Back
The rejection process will follow the same sequential flow as the
approval flow did.
Back to Initial Coder
The Rejection process will directly give the control to the initial coder
where the coding step started.
Terminate Approval Process
The Rejection process will terminate the approval.
Rejection FM
Enter a custom function module to customize rejection. See “Approval Flow
Settings Function Modules” on page 361.
Template: /OPT/OPTION_REJECT_TEMPLATE
Additional Settings
In this area you maintain additional settings that affect the approval logic.
Substitutes inherit COA

When a substitute of the original approver approves an invoice, the
substitute’s authorizations are checked. It can happen that the substitute
cannot approve some or all lines assigned to the original approver.
Select this check box if you want substitutes to inherit the COA rights of the
original approver. Then they are able to approve the same set of lines. For
VIM070500-03-CGD-EN-1
more information, see “Override, Delegation, Substitution, and Reassign”

on page 394.
Use approval buffer

Select this check box to enable the use of approval buffer.
Approval buffer allows to prevent sending the invoice for approval to the
same approver again. This could be the case if some lines have been
approved earlier, but the invoice has been rejected after that and then has
been sent to approval again.
This is supported for approver levels but not for coder or requester levels.
For more information, see “Using the Approval Buffer” on page 398.
Skip COA levels

Select this check box to enable skipping of COA approval levels.
Skipping may make sense if the COA is not maintained at some
intermediate levels but maintained at higher levels.
This is supported for approver levels but not for coder or requester levels.
For more information, see “Skipping COA Levels” on page 399.
13.5.5.1 Maintaining the Approval Flow Settings Mapping

The configured approval template with its approval flow ID (AFS ID) must be
mapped to a DP document type. Each document type can be maintained
individually. If an AFS ID is maintained without a specific DP document type (DP
document type empty), this ID will be used for all non specified document types.
To maintain the approval flow settings mapping:
Chain > Mapping for Approval Flow Settings.
2. In the Mapping for Level Based Approval Settings screen, perform the
mapping, using the following parameters:
DP Document Type
Enter a specific DP document type. Alternatively, leave the field empty to
use the AFS ID maintained in this line for all DP document types that are
not configured in the Mapping for Level Based Approval Settings screen.
Activation Type
Select one of the following values from the list:
Inactive
Level based approval is inactive.
Activate by Constant
Level based approval is activated with corresponding AFS ID. You
must maintain the AFS ID field.
VIM070500-03-CGD-EN-1
Activate by Determination
Level based approval is active, based on the Level Based Approval
Flow Determination Procedure. For more information, see “Maintaining
the Level Based Approval Flow Determination” on page 360.
Activate by Custom Function

Level based approval is active, based on a custom function module. You
must maintain the FM to determine AFS field.
Template: /OPT/DETERMINE_AFS_TEMPLATE
13.5.5.2 Maintaining the Level Based Approval Flow Determination

This maintenance step is only relevant if the AFS mapping for Activation Type is set
to Activate by Determination. For more information, see “Maintaining the
Approval Flow Settings Mapping” on page 359.
Fields Determination
You can use the fields determination to filter the determination based on the
fields defined in the field determination. With baseline, the following fields are
supported for the AFS determination type: Company Code (BUKRS) and Vendor
(LIFNR)
To access the fields determination, run the /OPT/SPRO transaction and navigate
to Vendor Invoice Management > Invoice Approval Configuration > Approval
Workflow > Setup Approval Chain > Approval Flow Strategy Determination
Procedure > Determination - Fields.
Determination Type
Enter AFS (Approval Flow Settings).
Field Type
Field Name
table.
Sequence
VIM070500-03-CGD-EN-1
Search Help Name

configuration.
Allow Ranges
configuration.
Data Determination
You can use this interface to enter data for the fields you determined in the
fields determination.
To access the data determination, run the /OPT/SPRO transaction and navigate to
Vendor Invoice Management > Invoice Approval Configuration > Approval
Workflow > Setup Approval Chain > Approval Flow Strategy Determination
Procedure > Approval Flow Strategy Determination - Data.
For each combination of index fields (Company Code and Vendor), you must
configure the corresponding AFS ID.
13.5.5.3 Approval Flow Settings Function Modules

This section describes function modules for the approval flow settings.
AFS Determina- This function module returns the found AFS ID. Level based approval is used,
tion Function which means header, sequential, or parallel approval.
Module
For the AFS Determination Function Module, you can use template /
OPT/DETERMINE_AFS_TEMPLATE.
Currency This function module returns the date for currency conversion. Based on the invoice
Conversion details, you can define a date that will be used for conversion.
Function
Module
For the Currency Conversion Function Module, you can use template /
OPT/DETERMINE_CONVERSION_DATE.
VIM070500-03-CGD-EN-1
Reject Function This function module returns the rejection option. Possible values are 1, 2, 3, 4.
Module These values are the only affected.
For the Reject Function Module, you can use template /

OPT/OPTION_REJECT_TEMPLATE.
Coder Determi- This function module returns coder or requester. Based on the coder details, it will
nation Function find the initial coder. If coder is equal to requester, it will consider the requester as
Module
the initial coder.
For the Coder Determination Function Module, you can use template /
OPT/DETERMINE_CODER_TEMPLATE.
13.5.6 Defining the Expense Type

The expense type is used to categorize invoices that might need a different approval
path. Examples of expense type are Marketing Expense, Office Supply,
Communication, or Utility. For the same approver, you can define different
approval limits for different expense types.
To define expense types:
Chain > Maintain Expense Types.
2. Configure the expense type using the following parameters:
ExpType
Select a unique identifier (two characters).
Description
Enter a description of the expense type.
Approval Req
Activate by typing X if the expense type requires an Invoice Approval
process.
VIM070500-03-CGD-EN-1
Technical note
Table /ORS/EXPENSE_DEC stores the description and the language and table /
ORS/EXPENSE_TYP stores Approval Req and ExpType.
13.5.7 Defining Rejection Reasons

You can define various rejection reasons, which the approvers can use when
rejecting PO based invoices. This step involves adding and configuring rejection
reasons.
To define rejection reasons:

Alternatively, run the SM30 transaction to maintain table /PTGWFI/Z_CONST, and
locate the record with Product Code IAP and Constant REJECTION_REASON.
2. Define the rejection reason, using the following parameters:
Value
This value determines how the rejection reason reacts when taking action in
the coding/approval process. The first value denotes the rejection reason,
the second value denotes the rejection comments. Value 1 is mandatory and
value 0 is not mandatory. Possible values:
1;0
Rejection reason is mandatory.
0;1
Rejection comments are mandatory.
1;1
Both rejection reason and rejection comments are mandatory.
The default value is 0;1.
3. In the Buttons Configuration, perform the following setting (to update the /
OPT/BUTTON table): For Function code Reject, select the Comments Required
check box. For more information about the buttons configuration, see
“Configuring Buttons” on page 384.
VIM070500-03-CGD-EN-1
13.5.8 Configuring Global Parameters

available. Global parameters control various aspects of the processing logic for IAP
process flows.
Important
Take care when you change the global customization parameters. Changes

• “Defining Resubmit for Approval Action Codes” on page 364
• “Defining Supported Currency and Language” on page 366
• “Configuring the Referral Wait Time” on page 367
• “Configuring Tax Calculation on Net Amount” on page 367
13.5.8.1 Defining Resubmit for Approval Action Codes

In this step, you define the process options for resubmitting the parked invoice for
approval. Using this option in the user's dashboard, the user can restart the approval
process for an invoice after the invoice has been rejected.
To define resubmit for approval action codes:

Alternatively, navigate to Vendor Invoice Management > Invoice Approval
Configuration > Approval Workflow > Resubmit for Approval Action Code.
2. Define the resubmit for approval action codes, using the following parameter:
Constant Value
Maintain action codes, separated by comma.
If you want to enable the functionality to submit for approval again after a DP based
approval has been rejected, perform the following steps:
VIM070500-03-CGD-EN-1
To define resubmit for approval for DP based approval:

Options.
2. In the Process Option Definition Maintenance View, double-click the line

Submit For Approval.
3. Configure the DP process option, as shown in the screenshot above. For further
information, see “Configuring DP Process Options” on page 204.
4. Make sure the same DP process option (as above) is maintained also in the Z
constant Entries table, see screenshot below.
VIM070500-03-CGD-EN-1
Mark the Approval related Process Type and click User Process Option in the
navigation panel.
The DP process option should be configured as user option for the Approval
related Process Type.
13.5.8.2 Defining Supported Currency and Language

In this step, you define the currencies and languages supported in the Approval
Portal.
To define supported currency and language:

Configuration > User Experience > Multilingual > Supported Currency /
Language.
2. Define the supported currency and language, using the following parameters:
VIM070500-03-CGD-EN-1
Constant LANGUAGE
Determines which languages are supported in the Approval Portal. You can
maintain multiple languages by using a comma as separator.
Default Value: E,D
Constant SUPPORTED_CURRENCY
Note: With VIM 6.0 and higher, constant SUPPORTED_CURRENCY is no

longer supported.
Determines which currencies are supported in the Approval Portal. You can
maintain multiple currencies by using a comma as separator.
Default Value: USD,DEM
13.5.8.3 Configuring the Referral Wait Time

Approvers/coders have the option to refer the invoice from the approval screen to
other users for information. You can configure the time to wait for the referee to
provide the information.
The “referrer” is the user who has sent the approval invoice to another user (referee)
for more information on the invoice.
The “referee” is the user who provides additional information on the approval
invoice.
To configure the referral wait time:
1. Run the SM30 transaction to maintain table /PTGWFI/Z_CONST.
2. Locate the record with Product Code IAP and Constant REFERRAL_WAIT_TIME.
3. Enter the Constant Value. It indicates the number of days to wait for the referee
to provide information.
After that period, the referral work item is rerouted to the referrer's inbox from
the Resubmission folder of the referrer's SAP Business Workplace.
13.5.8.4 Configuring Tax Calculation on Net Amount

The CALC_TAX_ON_NET constant provides an option to calculate tax on net amount
for Non PO DP Approval: This option enables the system to differentiate between
gross and net. You can configure the option individually for each document type or
centrally for all document types on the system.
The CALC_TAX_ON_NET constant is needed as a prerequisite for the Calculate Tax on

Net check box in the Document Type Definition Details screen, see Calculate Tax
on Net on page 161 for details.
VIM070500-03-CGD-EN-1
To configure tax calculation on net amount:
1. To add a new global CALC_TAX_ON_NET constant for product IAP, run the /
n/OPT/VIM_IMG424 transaction.
Alternatively, run the /n/OPT/SPRO transaction, and navigate to Vendor
Invoice Management > Invoice Approval Configuration > Technical General >
Invoice Approval Configuration.
2. Assign one of the following values to the CALC_TAX_ON_NET constant:
Value Description
X Central setting (for all document types)
G/L account amounts are to be entered net.
<blank> Central setting (for all document types)
G/L account amounts are to be entered gross.
D Individual setting for document types
Each document type can be set individually.
13.5.9 Cross Company Coding

When two or more company codes are involved in a single transaction, cross
company coding is required.
To turn on the cross company coding, activate BUKRS or COMPANY_CODE, as described

in “Configuring Cross Company Coding” on page 369).
Technical note
The OpenText delivered code includes a popup to suggest the correct company
code for the line if the cross company coding is active and the cost center or
internal order entered in the line item does not match the company code in the
header. This feature is supported in the Approval Portal and the SAP GUI.
If the coding is done in the SAP GUI, the popup window to suggest the correct
company code is generated by a function module defined in the Z constant
POPUP_COMPANY_CODE. The OpenText default delivered function module for
this constant is /ORS/000007_POPUP_COMPANY_CODE.
VIM070500-03-CGD-EN-1
13.5.9.1 Configuring Cross Company Coding

Configuring cross company coding adds a company code field on each line item.
You can code this line to a company code different from that on the header. The
header company code will be the initial default. This enables a validation of the cost
center and other coding elements against the new company code on the line item.
To configure cross company coding:

2. Enter table /ORS/APPR_GL_CFG. Locate the field BUKRS and double-click. If the
field BUKRS is not displayed, add a new field.
3. Enter the parameters as shown in the following screenshot:
4. Save the entries.
13.5.10 Configuring the Email Notification

Approvers will receive emails saying that new invoices are waiting in their SAP
inbox. If the optional Approval Portal is implemented, the emails contain a URL link
to either the portal with the invoice iView or the invoice list page.
You can configure the notification email to include some invoice information, such
as vendor name, invoice reference number, or invoice amount. The following is an
example of a notification email:
VIM070500-03-CGD-EN-1
The approval email notification depends on the user configuration. You configure
users in the COA or in the Approval Portal, on the Personalization page. For more
information, see “User Details View” on page 56 (COA) and section 7.14
“Personalizing Your Views of the Approval Portal” in OpenText Vendor Invoice
Note: To send email notification, you can also use VIM Notifications. In this
case, the email is sent without the configuration in the COA or on the
Personalization page. For more information, see “Using VIM Notifications“
on page 783.
13.5.10.1 Implementing the Email Notification in VIM

Sending the email is initiated in method Get_Approver_List of business object
type /ORS/INVAP.
The Business object method Get_Approver_List calls the ABAP class method
sendemail of the ABAP class that implements the user mapping class. The name of
this ABAP class is configured in table /PTGWFI/Z_CONST under the entry IAP, 0,
USERMAP_CLASS. Baseline VIM uses class /OPT/CL_IAP_USERMAP_BL.
The actual function to create the send request is /PTGWFI/CP_SENDMAIL.
Call Sequence:
/ORS/INVAP-> Get_Approver_List
/OPT/CL_IAP_USERMAP_BL-> sendemail
/PTGWFI/CP_SENDMAIL
To overwrite email sending with a customer specific email function:
1. Create a new ABAP class which inherits from /OPT/CL_IAP_USERMAP_BL.

2. Overwrite the sendemail method.
3. Change the configuration in table /PTGWFI/Z_CONST: Insert the new ABAP class
instead of /OPT/CL_IAP_USERMAP_BL.
To debug email sending (with ERP 6.0):
1. To invoke User Maintenance, run the SU01 transaction.

2. Change user WF-BATCH to a dialog user.
VIM070500-03-CGD-EN-1
3. To open the Object Navigator, run the SE80 transaction.
4. Click Utilities > Settings. Click the ABAP Editor tab.
5. In the Debugging tab, insert WF-BATCH in the Users field.
6. Set an external breakpoint, for example in function module /

PTGWFI/CP_SENDMAIL.
7. Make sure that at least one additional SAP GUI session is available.
8. Start the test case.

When the background task for retrieving approvers is called, a debug session
will open.
13.5.10.2 Configuring Email Text Including Dynamic Information

You can configure the email notification as a standard text in SAP ERP, including
dynamic information of the invoice fields, for example the invoice amount.
To configure email text including dynamic information:
1. Run the SO10 transaction.
2. Enter the Text name INVOICE_APPROVAL_NOTIFICATION (for NPO) and

PO_INVOICE_APPROVAL_NOTIF (for PO), select Text ID ST (Standard text) and
click Create.
Note: VIM provides the template PO_INVOICE_APPROVAL_NOTIF. If this

text is not maintained, the existing text INVOICE_APPROVAL_NOTIFICATION
is used for email notification of both PO and NPO invoices.
3. To include contents of invoice fields use the following notation:
&/ORS/INVAP.InvoiceAmount&
These variables will be replaced at runtime by evaluating the current instance of

business object /ORS/INVAP.
The following variables are available:
• ApprovalStatus
• CompanyCode
• Currency
• DocumentNumber
• DueDate
• FiscalYear
• GrossInvoiceAmount
• InvoiceAmount
VIM070500-03-CGD-EN-1
• InvoiceDate
• InvoiceObjectKey
• InvoiceObjectType
• ObjectType
• StatusPosted
• Vendor
• VendorInvocieNumber
Tip: This is the actual spelling.
• VendorName
To provide additional variables:
1. Run the SWO1 transaction.
2. Create a new object type, inherited from /ORS/INVAP.
3. Add an additional database or virtual attributes.
Other option
Overwrite the sendemail method. See “To overwrite email sending with a
customer specific email function:“ on page 370.
13.5.10.3 Additional Information About the Email Notification

Email subject line
The first line of the text stored in SO10 is used as the subject line of the email.
Email format
The email notification can be sent in different formats. The format is configured
in Z Constant (product code 005) REM_MAIL_DOCTYPE. Default value is RAW.
This email format is used globally for all kind of email notification: Reminder
notification, Approval notification, and SRM notification.
The notification emails can be sent in HTML format with readable formatting
and invoice data presented in the form of HTML tables. To enable this
functionality, you must set the constant 005 / REM_MAIL_DOCTYPE to HTM. In the /
OPT/VIM_8CX50 transaction, you must configure the Email Type to be Internet
Email.
User specific notification setting

In the User Preference screen of the Approval Portal, users can choose if they
want to receive a notification email for any new invoice in their inbox.
Therefore, users must select the Receive email notification check box.
This setting is retrieved from table /ors/user_prefer, field e_notify_active.
VIM070500-03-CGD-EN-1
Language limitation
When the email is built, the text stored in the SO10 transaction is retrieved with
language taken from sy-langu.
The workflow language is determined, when the approval workflow is started.
This can be the logon language of the user who scanned the invoice or the logon
language of the last user who processed the invoice in the DP workflow.
Important
If no text can be found for the current value of sy-langu, then no email
is sent.
Therefore the text should be maintained in all languages that are typically used
for logon. The text is retrieved in function module /PTGWFI/CP_SENDMAIL in the
following way:
CALL FUNCTION 'READ_TEXT'

EXPORTING
CLIENT = SY-MANDT
ID = TEXT_ID
LANGUAGE = SY-LANGU
NAME = TEXT_NAME
OBJECT = 'TEXT'
IMPORTING
HEADER = HEADER
TABLES
LINES = TEXT_LINES
EXCEPTIONS
13.5.11 Configuring the Certify Message

During the web approval process, when the approver approves the invoice, a certify
message will be displayed on the screen. You need to configure this message to
adjust it to your needs.
To configure the Certify message:
1. Run the SO10 transaction.
VIM070500-03-CGD-EN-1
2. Enter the Text name, select Text ID ST (Standard text) and click Create.
3. Enter the text of the Certify message and click to save.

Management > Invoice Approval Configuration > Technical General > Invoice
Approval Configuration.
5. To maintain the Z constant CERTIFY_MESSAGE, double-click the respective line.
6. Maintain the Z constant, as shown in the screenshot above.

If no text is maintained, a standard message “Certified as Approved” will be
displayed. The Approval Portal uses the following RFC to fetch this
information: /ORS/000007_READ_PREFERENCE (look for text-054).
VIM070500-03-CGD-EN-1
13.5.12 Configuring Fields for Invoice Approval

The approval screen in the SAP GUI Approval, Approval Portal and Mobile
Approval Portal contains a number of fields that you can configure, depending on
the calling application (SAP GUI / Portal / Mobile). This includes the following kinds
of fields:
• Invoice Detail fields
• Invoice header fields

• Line item fields
• Accounting information fields for Non PO invoices

• Line item and accounting assignment fields for PO invoices
• Coding Configuration
• Invoice List fields
• Processed by me List fields

• Inbox List fields
• All field titles in the approval screen
• Exits to integrate individual screen logic on Approval Portal and Mobile
Approval Portal
• Button configuration
Depending on the application and the scenario (PO / NPO and DP / PARKED /
POSTED), fields can be configured to be changed on the screen if the user has the
corresponding authority (coding).
List of coding You find a list of all fields that are provided for coding in structure /
fields ORS/INVOICE_ACCT_DATA. From baseline, only a subset of the fields is supported to
be posted in background using BAPI or in dialog using BDC IDs. If you want to use
an unsupported field, you must extend the relevant BDC IDs or implement the BAPI
exit.
For use in Invoice Approval, you can configure extended fields that are no baseline
fields. For more information, see section 8.6.4 “Changing BDC IDs” in OpenText
Vendor Invoice Management for SAP Solutions - Scenario Guide (VIM-CCS).
Inside structure /ORS/INVOICE_ACCT_DATA, the include /ORS/ADD_INV_ACCT

contains custom fields, and the include /ORS/ADD_TXT_ACCT contains the text fields
associated to the custom fields.
The following sections describe the configuration you need to perform for the fields.
VIM070500-03-CGD-EN-1
13.5.12.1 Configuring Fields for the Invoice Detail Page

For the invoice detail page, you must configure the header and the item fields to be
shown with the corresponding attributes.
The configuration is necessary to show the invoice detail fields when an invoice is
processed from the invoice inbox list and also when an invoice is selected from the
Process by me list.
For the coding fields, you must also configure all fields separately. This
configuration separates display functionality and the functionality to read and store
data back in the invoice line items, independent of the field status on the screen.
To configure fields for approval, you must perform both configurations, for the
invoice detail page as well as for the coding fields.
Notes
• All configuration for item fields is available for SAP GUI Approval,
Approval Portal, and Mobile Approval Portal.
• For the Approval Portal, the INVOICE_DOC_ITEM field is mandatory for line
items in the Cost Assignment section of any invoice (both PO and Non PO).
• All configuration for header fields is available for Approval Portal and
Mobile Approval Portal. Status for coding fields, custom fields
(CUSTOM_FIELD*) and special fields like expense type and VAT amount
can be changed to be editable.
To configure fields for the invoice detail page:

Management > Invoice Approval Configuration > User Experience > Invoice
Detail Configuration > Maintain Invoice Detail Fields.
2. To display details of a field, double-click the corresponding line.
3. Configure the relevant header and item attributes field, using the following
parameters:
Note: Depending on the values you select, some parameters may be

prefilled. You cannot change these parameters.
Field name
Unique name of the field
Page
Select the page where the field is displayed: Invoice Detail Page
Field Type
Select Header Field or Item Field.
Invoice Type
Select All Invoices, PO based invoices, or Non PO based invoices.
VIM070500-03-CGD-EN-1
Device name
Select Web Approval Portal, Mobile Approval Portal, or SAP GUI.
AFS ID
Select the relevant AFS ID.
Reference Field
Enter a standard data element and press the ENTER key. For example, the
ShortFieldLabel and the Long Field Label are populated. The Label fields
are visible in the Portal.
Field Status
Select the status of the field: Display, Input, Hide, or Required (not
available for line item fields).
Most of the settings will be available for Approval Portal and Mobile
Approval Portal. The Mobile Approval Portal provides only display
functionality. Also, header fields on all other devices will be displayed only.
SAP GUI provides the possibility to change the status for coding fields.
Header fields are always shown on the SAP GUI screen and cannot be
hidden.
List Sequence
Configure the sequence of the field in the page (only for Approval Portal
and Mobile Approval Portal) for header and item fields.
List Display Length
Configure the display length of the field in the page (only for Approval
Portal and Mobile Approval Portal) for header and item fields.
Detail Sequence
Configure the sequence for the item fields (only for Approval Portal and
Mobile Approval Portal) which are shown in the additional accounting
entry screen.
Detail Display Length
Configure the display length for the item fields (only for Approval Portal
and Mobile Approval Portal) which are shown in the additional accounting
entry screen.
COBL Sequence
Only available for PO invoices: Configure the sequence of the field in the
Account Assignment area in the Detail Page sequence.
COBL Display Length
Only available for PO invoices: Configure the length of the field to be
displayed in the Account Assignment area in the Detail Page sequence.
No. of Characters
Configure the number of characters for the value in the field.
Data Type
Configure the data type of the field (string, char, or int). Select a data type
from the list.
VIM070500-03-CGD-EN-1
Search Help Name

Enter the search help name for the field. For details, see “Configuring
Search Help for Web Screen Fields” on page 388.
Note: This is only relevant for Approval Portal, not for SAP GUI and
Mobile Approval Portal.
Search Help Parameter

Enter the search help parameter for the field. For details, see “Configuring
Search Help for Web Screen Fields” on page 388.
Note: This is only relevant for Approval Portal, not for SAP GUI and
Mobile Approval Portal.
Configuring You may want to read and store coding information that is not shown on the screen.
coding Therefore, you must configure all coding fields. This configuration also determines
which SAP field (DP and parked line item field) is mapped to each coding field
(used in the approval screen).
Note: Fields that are not configured or that are not active will not be saved in
the line items.
To configure the coding:

Management > Invoice Approval Configuration > Financial Processing >
Coding Configuration > Maintain Coding Fields Mapping.
This configuration table defines the coding fields. The table determines which
fields are shown and in which sequence they are shown in the coding window.
It also determines which SAP field is mapped to each coding field.
VIM070500-03-CGD-EN-1
3. Configure the field, using the following parameters:
BAPI Field name

Enter the name of the BAPI field that is used to map data between SAP ERP
and the Approval Portal when processing the invoice.
BSEG Field name

Enter the name of the BSEG table related field that is used to map data
between SAP ERP and the Approval Portal when processing the invoice.
BDC Field name

Enter the name of the BDC field that is used to map data between SAP ERP
and the Approval Portal when processing the invoice.
Active
Select this check box to activate the configuration. Even if BAPI Field name,
BSEG Field name and BDC Field name are maintained, the Active check
box must be checked.
Approval Portal: Web Approval Portal supports the following types of custom fields.
Supported
custom fields • Static custom fields
• Dynamic custom fields
Approval Portal: Supported static custom fields
You define the following static custom fields in the /OPT/FIELDS_V table.
Invoice List Page (Inbox View)

Supported custom fields in the Invoice List Page view:
• CUSTOM_FIELD0 [Datatype: Character String, Output Length: 20]
• CUSTFIELD1 [Datatype: Character String, Output Length: 1]
Invoice Details Page - Header Field (Basic Data View)

Supported custom fields in the Invoice Details Page - Header Field view:
VIM070500-03-CGD-EN-1

Invoice Details Page - Item Field (Cost Assignment View)

Supported custom fields in the Invoice Details Page - Item Field view:

• CUSTOM_FIELD5 [Datatype: Date Field (YYYYMMDD) stored as char(8), Output
Length: 10]
• CUSTOM_FIELD6 [Datatype: Character String with only digits, Output
Length: 2]
Length: 4]
Length: 5]
Approval Portal: Supported dynamic custom fields
You define the following dynamic custom fields in the /OPT/FIELDS_V table.
Invoice List Page (Inbox View)

Dynamic custom fields are not supported in this view.
Invoice Details Page - Header Field (Basic Data View)

To use dynamic custom fields in this view, maintain these custom fields in the
ET_CUST table of the /OPT/OAP_GET_INVOICE_DETAIL RFC, using the
EXIT_INVOICE_DETAIL exit.
VIM070500-03-CGD-EN-1
Invoice Details Page - Item Field (Cost Assignment View)

To use dynamic custom fields in this view, maintain these custom fields in the
IT_CUST table of the /OPT/OAP_INVOICE_ACTION RFC, using the
EXIT_INVOICE_ACTION exit.
13.5.12.2 Configuring Invoice List Fields

For all possible inbox fields and Processed by me list fields, you must configure the
list fields to be shown.
For the Approval Portal, users can personalize the list fields according to their
needs. This is possible on the Approval Portal Personalize page. The personalized
fields are then used in the inbox and the Processed by me list.
If no personalized preferences exist, the global default invoice list fields are
configured at the following location: Run the /n/OPT/SPRO transaction and
navigate to Vendor Invoice Management > Invoice Approval Configuration > User
Experience > Invoice List Configuration > Default Invoice List.
Note: All configuration for list fields is available for the Approval Portal and
the Mobile Approval Portal. All fields can only be display fields.
To configure inbox and Processed by me list fields:

List Configuration > Maintain Invoice List Fields.
VIM070500-03-CGD-EN-1
3. Configure the relevant header and item attributes field using the following
parameters:

Field name
Unique name of the field
Page
Select the page where the field is displayed: Invoice List Pages
Field Type
Select Header Field.
Invoice Type
VIM070500-03-CGD-EN-1
Device name
Select Web Approval Portal, Mobile Approval Portal (not supported for
SAP GUI).
Reference Field
Enter a standard data element and press the ENTER key. For example, the
ShortFieldLabel and the Long Field Label are populated. The Label fields
are visible in the Portal.
Field Status
Select the status of the field: Display
List Sequence
Configure the sequence of the field in the list
List Display Length

Configure the display length of the field.
No. of Characters
Configure the number of characters for the value in the field.
Data Type
Configure the data type of the field (string, char, or int). Select a data type
from the list.
13.5.12.3 Configuring Exits

The following exits enable you to integrate own logic in the Approval Portal and
Mobile Approval Portal functions executed during data retrieval and invoice
processing.
To configure relevant Z Constants:
3. In the WebFlow Constant Table, under Product Code IAP, navigate to the
following constants:
• EXIT_INVOICE_ACTION
• EXIT_INVOICE_DETAIL
• EXIT_INVOICE_LIST
4. If you want to configure exit function modules for invoice action, invoice detail,
invoice list, and Processed By Me list, maintain your function module in the
respective Constant Value.
The default template function modules are:
• /OPT/OAP_EXIT_ACTION
• /OPT/OAP_EXIT_DETAIL
VIM070500-03-CGD-EN-1
• /OPT/OAP_EXIT_LIST
13.5.12.4 Configuring Buttons

You can add buttons to the Invoice List and the Invoice Detail page of the Approval
Portal and the Mobile Approval Portal. In the SAP GUI approval screen, you can
add buttons to the Invoice Detail page. You can configure these buttons to be visible
dynamically, based on the type of the invoice and the approver role. You can
maintain custom buttons but also the default buttons.
If you add buttons to the Invoice List page of the Approval Portal, you must select
Button Type List.
To configure buttons for the Invoice List:

List Configuration > Maintain Invoice List Buttons - Inbox.
2. In the Buttons Configuration Overview screen, double-click a line to open the
details.
3. Configure the button, using the following parameters:

VIM070500-03-CGD-EN-1
Function code
Function code that is used to process the invoice
Page
Select the page where the button is displayed: Invoice List or Invoice
Detail Page
Invoice Type
Button Type
Select where the buttons are considered on the page: Header level, Item
level, or List level.
Device name
Select Web Approval Portal or Mobile Approval Portal (SAP GUI is not
supported for invoice list buttons. However, it is supported for detail page
buttons.)
Text
Enter the text for the button to be displayed in the portal.
Quick Info
Enter the tool tip for the button.
Button Code
Select Standard Button or Custom Button.
Standard Button
Baseline buttons are covered in this category.
Custom Button
You can define own buttons and achieve custom functionality.
User Type
Select the user to which this button is applicable: Approver, Coder, or
Everyone.
Reason Required
Select this check box to require a reason on the confirmation screen from the
user when they click the button.
Comments Required
Select this check box to require a comment on the confirmation screen from
the user when they click the button.
Log Activation
See “Custom button logging” on page 387.
Log Act. Txt.
Log Activation Text, see “Custom button logging” on page 387.
Handling Function
The Handling Function determines the RFC function that is called when
the user clicks the button in the approval screen or the Approval Portal.
VIM070500-03-CGD-EN-1
Enter the function module to handle the button. Create a custom function
module by copying the sample function module /OPT/BUTTON_FM.
For buttons on the invoice list page of the Approval Portal (Button Type
List), use the sample function module /OPT/BUTTON_FM_LIST. You can use
the handling function module to call a dynamic URL.
URL
Enter the static URL to be displayed after the button is clicked.
URL Function
Enter the function module to get the URL dynamically. Create a custom
function module by copying the sample function module /
OPT/BUTTON_URL_FM.
Notes
• This field is not relevant for buttons on the invoice list page (Button
Type List).
• Either Handling Function or URL and URL Function will work;
you must decide for one of them, you cannot use both.
To configure buttons for the Detail page:

Detail Configuration > Maintain Invoice Detail Buttons - Process.
2. In the Buttons Configuration Overview screen, double-click a line to open the

details.
3. Configure the button. The parameters are the same as for the Invoice List
buttons. See “To configure buttons for the Invoice List:“ on page 384
Note: The Forward button is only supported in Non-PO scenarios.
Modifying data VIM provides a feature to change the accounting data and header data for custom
for custom buttons. The feature can save the changed header data and item data.
buttons
The feature only works if the following conditions apply:
• The invoice is a Non-PO invoice.

• The button type is either Header or Item.
• The button code is Custom Button.
• Handling Function is maintained; that means a custom function module is
maintained to handle this feature. The custom function module must have the
same interface as function module /OPT/BUTTON_FM.
The feature provides the following functionality:
VIM070500-03-CGD-EN-1
Header button type

• Change header data or item data or both and also delete the line items.
• Copy the selected line and add as the last line item.
Line item button type

• Delete or change the selected line item.
To maintain custom buttons, you must maintain the data in the view /OPT/BUTTONV
or use the transactions /n/OPT/OAP_DETL_BUTTON or /n/OPT/OAP_LIST_BUTTON.
Custom button VIM supports logging for custom buttons in the SAP GUI approval screen and on
logging the Approval Portal. You can customize the log comments.
To activate the custom button logging and to customize the log comments, run the /
n/OPT/OAP_DETL_BUTTON transaction for the detail screen, or run /
n/OPT/OAP_LIST_BUTTON for the list screen.
For a detailed description of all parameters in these two transactions, see “To
configure buttons for the Invoice List:“ on page 384.
The relevant parameters for the custom button logging are the following:
Log Activation
To activate the custom button logging, select this check box.
By default, the custom button logging is inactive when you install VIM. You
must activate it for all the custom buttons as needed.
For the Approval Portal, the custom button logic is there but the Approval
Portal still needs to write the logic to display the customized custom button log.
Note: In the Approval Portal, custom buttons are not handled except the
URL functionality.
Log Act. Txt.

Log Activation Text
Enter customized log content as free text.
If you leave this field empty and logging is active, the default text is displayed in
the log.
Note: For other languages, you must maintain the log activation text in
your required logon languages. If this text is missing in any logon
language, you will see the default text.
VIM070500-03-CGD-EN-1
13.5.13 Configuring Search Help for Web Screen Fields

For web approval, you can configure search help for web screen fields to give users
input help for these fields.
To configure search help for web screen fields:
Invoice Approval Configuration > User Experience > Invoice Detail
Configuration > Maintain Invoice Detail Fields.
2. Double-click the line of the field that needs a search help.
VIM070500-03-CGD-EN-1
3. Configure the search help, using the following parameters (at the bottom of the
screen):
Note: Only elementary search help is supported; collective search help,

which includes search helps, is not supported. See the following
screenshot. You find the search help parameter (export parameter) in the
details of the search help.
Call the SE11 transaction to find the search help and also to display the
attributes of the search help.
Search help name

Enter the name of the search help to be called by the web approval screen
when the user requires input help.
SearchHelpParam
Enter the name of the search help parameter which will actually hold the
value for the web approval screen field.
The following fields are usually configured for search helps:
GL_ACCOUNT
Search help name = SAKO_CORE
SearchHelpParam = SAKNR
COST_CENTER
Search help name = TRAC_KOSTL
SearchHelpParam = KOSTL
COMPANY_CODE
Search help name = H_T001
VIM070500-03-CGD-EN-1
SearchHelpParam = BUKRS
MATERIAL
Search help name = H_WERKS_MATNR_E
SearchHelpParam = MATNR
INTERNAL_ORDER
Search help name = ORDEA
SearchHelpParam = AUFNR
TAX_CODE
Search help name = SH_T007A
SearchHelpParam = MWSKZ
NETWORK_NO
Search help name = AUKOB
SearchHelpParam = AUFNR
WBS_ELEMENT
Search help name = PRPMA
SearchHelpParam = POSID
13.6 Roles in the IAP Process

The roles used in the IAP process are technically different from the ones used in all
other processes. This section describes the main roles that are required for the IAP
process.
13.6.1 Configuring the Coder Role

Coding refers to entering accounting data. The purpose is to assign the invoice to a
certain G/L account and cost collecting objects, such as cost center or internal order.
The person who enters the coding information is normally called “coder”. However,
technically speaking, the coder is just an approver with the Coding flag turned on,
which means the coding section is opened for the coder to enter the accounting data.
The coder still has to click the Approve button to save the accounting data and move
the item to the next approver.
When the invoice is parked for approval, it is sent to the coder first. The following
coder definitions are possible:
By requester
Each requester has an associated coder.
By company
Each company code has an associated coder.
Both
The coder is determined by both requester and company code.
VIM070500-03-CGD-EN-1
13.6. Roles in the IAP Process
Use requester
The coder is the requester.
Configuration The configuration for level based approval is done in the approval flow settings
(AFS). For more information, see “Configuring Approval Flow Settings”
on page 353.
13.6.2 Configuring the Approver Role

User mapping and chart of authority are two important concepts in IAP. User
identities are maintained in the table /ors/usermap and this is accomplished using
the ABAP class /ORS/USERMAPPING. You can extend this class if you need custom
logic to be incorporated.
The following sections describe user map maintenance and Chart of Authority
(COA) maintenance. For a detailed description, see “Maintaining Chart of
Authority” on page 54.
13.6.2.1 User Map Maintenance

User mapping is critical to work with users from separate systems, such as SAP ERP
or SAP NetWeaver Portal. All user IDs have to be mapped to an internal
OPT_USERID. The mapping is maintained in table /ors/usermap and in the /
OPT/AR_COA transaction. For a detailed description, see “Maintaining Chart of
Authority” on page 54.
13.6.2.2 Configuring Approver Persona Attributes

The approver persona is configured by a set of check boxes that define what an
approver can do when approving the invoice.
The definition table for approver persona attributes is /OPT/BL_AP_CONF, which can
be maintained by the SM30 transaction.
Alternatively navigate to OpenText Vendor Invoice Management > SAP menu >
Roles > Coder/Approver Options Configuration.
VIM070500-03-CGD-EN-1
The following check boxes for the approver persona are available:
Approval Flag
Select this check box always.
Approver access rights - Approve or reject an invoice; enter comments.
Coding Flag
Select this check box to achieve that the approver is able to enter accounting
data.
In level based approval, the accounting information can only be entered either in
the coding level (level 0) or in the requester level (level 1). If the requester is
maintained as coder, the requester is able to enter and change the accounting
information. In this case, there is no coding level.
You might want to remove the following buttons from the Approve Invoice
screen, both in the SAP GUI and in the Approval Portal:
• I will enter accounting information
• I want someone else to enter accounting information
The Approve Invoice screen will display the accounting information

immediately.
To perform this configuration, select the Approval Flag and the Coding Flag,
and clear the Coding Delegate check box.
Approver access rights - Enter accounting information.
Coding Display
Select this check box to achieve that the coding block is displayed.
VIM070500-03-CGD-EN-1
If Coding Flag is selected, the coding block is always displayed in change mode.
If Coding Flag is cleared, you can use the Coding Display check box to display
or hide the complete coding block.
Note: The Coding Display check box only takes effect in the SAP GUI
approval.
Approver access rights - View accounting information.
Coding Delegate
Select this check box to achieve that the approver is able to delegate the coding
to others.
In level based approval, the Coding Delegate check box enables or disables the
forward button in the coding level.
If Coding Delegate is selected and, additionally, Coding Flag or Coding
Display is selected, the buttons I will enter accounting information and I want
someone else to enter accounting information are displayed.
If only Coding Delegate is selected (and no Coding Flag or Coding Display
check box), the buttons are not displayed. In the approval screen, you can
delegate the coding. The Please Specify the Coder field is displayed directly.
Approver access rights - Specify a Coder, which means a specialist to enter the
accounting information.
Configuration
Select this check box to achieve that the approver can set the persona for the next
approver.
Approver access rights - Determine next approver’s access options.
Override
Select this check box to achieve that the approver can override the system
generated next approver.
Approver access rights - Override the system-proposed next approver.
Look Ahead
Select this check box to achieve that the approver is able to retrieve all the
approvers.
Approver access rights - View the entire approval chain or pre-determine all the
approvers.
In level based approval, the look ahead option is obsolete.
Custom Flag 1
Select this check box to indicate the expense type as read only.
Custom Flag 2
Select this check box to indicate the approver as a delegated coder.
Custom Flag 3
Not used
VIM070500-03-CGD-EN-1
13.6.2.3 Override, Delegation, Substitution, and Reassign

Because of the compliance implication of the IAP process, Invoice Approval needs to
guarantee that only the designated approver approves the invoice. However, there
are situations that require others to take over the responsibility temporarily, for
example, unexpected termination, illness, or vacation. VIM Invoice Approval
provides the following mechanisms and utilities to address these situations:
Override next approver

The current approver should be able to override the system-generated next
approver. To do so, the approver persona setting needs to have the OVERRIDE
check box selected.
VIM provides a feature to show the approver override in the logging.
A log event N is introduced as value for /ORS/APPR_ACTION.
The log event is written to the approval log file /ORS/APPL_LOG, whenever the
invoice is approved and an override approver has been entered.
The event is shown in the approval log:
The entry does not show directly who executed the override action. To find this
out, look at the corresponding action entry, which has the same time stamp.
VIM070500-03-CGD-EN-1
Coding delegation
If the current coder/approver does not have all the knowledge to provide the
correct coding, the current coder/approver may delegate to another coder. To do
so, the approver persona needs to have the CODING_DELEGATE check box
selected.
Substitution
The approver or coder can set up personal substitutes to temporarily take over
their responsibility. The substitute can be defined by one of the following ways:
• If the optional Web IAP is implemented: From the approval web page, open
the User Preference page and open the Substitution section.
• From the SAP inbox, add substitute from the SAP menu.
Note: This is only available when both substituted and substituting

users are SAP users.
• From User Substitute Management Utility (/ORS/MAIN_SUBS transaction).
This transaction can maintain all the substitute relations in the system.
Note: Only an administrator can execute the substitution.
Substitution features
• When a substitute is specified, one of the following options applies,

depending on the customizing:
• The substitute assumes all the authority of the original approver

regarding the invoices belonging to the original approver.
• The substitute’s own COA rights are considered when approving
invoices.
You can control these options using the Substitutes inherit COA check box
in the Approval Flow Settings for the respective AFS ID; see “Configuring
Approval Flow Settings” on page 353.
• The invoices belonging to the original approver will be added to the
substitute's invoice list.
• When the substitute approves an invoice that is not originally sent to the
substitute, the action will be logged as XXX approves the invoice on behalf
of YYY.
• The original approver can place limitations when setting up the substitute.
Normally, the names are searched by the Name Search method /
ORS/000007_NAME_SEARCH of the usermap class. The method can be
customized to include a logic that restricts the list of legible substitutes to
those with equal or higher authority of the original approver.
VIM070500-03-CGD-EN-1
Note: You can disable the substitute maintenance on the OpenText

Approval Portal from ABAP side. To do this, set the value of the Z constant
IAP / PORTAL_NOTMAINT_SUBS to X.
Reassign
When an employee is not supposed to approve invoices anymore, the
administrator can use the Reassign utility to reassign the work item to others.
• When reassigned, the work item is permanently moved to the new

approver’s inbox. The invoice has to be approved based on the new
approver’s authority.
• The reassign action is logged in the approval log for future audit.
• It is possible to reassign one invoice or the entire inbox of an approver.
The Reassign utility may “recall” the invoice back to the AP department. Once
recalled, the approval workflow is terminated. The AP department may
resubmit the invoice for approval. For more details, see section 15 “Reassigning
Work Items Belonging to Another User” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD).
13.7 Configuring Header Based Approval

This section provides the configuration steps for header based approval. For details
about header based approval in general, see Header based processing on page 354.
To configure header based approval:
1. To access the Approval Flow Settings screen, run the /OPT/SPRO transaction
and navigate to Vendor Invoice Management > Invoice Approval
Configuration > Approval Workflow > Setup Approval Chain > Approval
Flow Settings.
2. In the Approval Flow Settings screen, customize the AFS ID.

For more information, see “Configuring Approval Flow Settings” on page 353.
3. Set the AFS type to H – Header Based Approval.
4. Use the following baseline process classes:

Approver class: /OPT/CL_A_LEVEL_BASED_APPROVAL
Usermap class: /OPT/CL_IAP_USERMAP_BL
NPO invoice class: /ORS/NON_PO_INVOICE_NEW
PO invoice class: /ORS/PO_INVOICE_NEW
5. To access the Mapping for Approval Flow Settings screen, run the /OPT/SPRO
transaction and navigate to Vendor Invoice Management > Invoice Approval
Configuration > Approval Workflow > Setup Approval Chain > Mapping for
Approval Flow Settings.
VIM070500-03-CGD-EN-1
13.8. Configuring Level Based Approval Features
6. To map your customized AFS ID to the wanted VIM Document Type, add the
AFS ID in the mapping configuration.
For more information, see “Maintaining the Approval Flow Settings Mapping”
on page 359.
7. To determine the user that gets assigned the approval work item, configure the
COA, Approval Category column. For more information, see Approval
Category on page 62.
13.8 Configuring Level Based Approval Features

Level based approval provides a set of features, which are described in this section.
13.8.1 Using Parallel Approval

VIM supports parallel approval of invoice line items. This can speed up processing if
the responsibility for approving different line items can be distributed depending on
the line item data. The parallel approval is possible only for the Approval levels,
starting with level 2 in the COA maintenance. The Coder and Requester levels are
still running in a sequential manner.
If an invoice can be sent to multiple approvers, the found approvers are displayed as
a list on the approval confirmation screen. This is possible only when transitioning
to the next level. Therefore only the last approver (or coder) in each level is shown
the list with multiple approvers.
Note: The approvers cannot be overridden in this case, unlike in the case of
sequential approval.
At the Approval level, you can forward an invoice only to an approver that can
approve at least all the line items assigned to the current approver, according to the
COA settings.
Note: In the sequential workflow, invoices can be forwarded to anyone who

can approve at least one line item.
If an invoice is rejected at the Approval level, all other parallel work items are
cancelled. The invoice is routed according to the AFS settings, for example One Step
Back. For details, see Rejection Processing on page 358.
In case of the option One Step Back, the invoice returns to the previous approval
level.
VIM Analytics In the Processes tab of the VIM Analytics report, the invoices that are currently sent
to multiple parallel approvers are displayed with one line for each agent.
In the Unified Dashboard approval log dialog box, the text Multiple approvers
exist is displayed instead of the approver name. A button to display the approvers
list is placed next to this text.
VIM070500-03-CGD-EN-1
13.8.2 Using the Approval Buffer

An invoice might have been approved at some approver level and then have been
rejected at a higher level. The invoice goes back to a requester who probably changes
some line items and then sends the invoice to approvers again. In this case, it might
make sense to skip the approval levels for lines that have not been changed.
The following diagram illustrates the approval flow in such cases.
An invoice gets approved at levels 1 (requester) and 2 (approver), and then gets
rejected at the approver level 3, going back to the requester level.
The numbers in the diagram reflect the approval levels.
VIM provides the approval buffer. If the approval buffer is active and the line items
have not been changed, the following approval at requester level leads to the invoice
being sent to the approver at level 3, bypassing level 2.
You can enable the approval buffer for individual AFS IDs. For more information,
see “Configuring Approval Flow Settings” on page 353.
Conditions With the approval buffer enabled, approval of a specific line item is skipped in the
level if the following conditions apply:
• The line item data was not changed.
VIM070500-03-CGD-EN-1
13.8. Configuring Level Based Approval Features
• The last action performed on the line item was approval.

• The last approver of the line item is still allowed to approve it.
Final approval The final approval is not considered. Final approval steps must be repeated.
Approval flow The approval buffer functionality is implemented only for approver levels (2 and
higher). Both sequential and parallel line-based approval flows are supported.
Header-based approval flow is not supported.
Line item All accounting information fields are considered when comparing line items against
information their earlier state.
Substitution When using substitution during the approval, some line items might be approved
not by their originally assigned approvers but by their substitutes. The check,
whether the last approver of the line item is still allowed to approve it, is done with
the actual approver, that means with the substitute.
Logging The approval steps simulated through the approval buffer are shown in the
extended approval log for the last dialog approval step that is executed. In the
extended approval log, the name of the approver who approved the lines earlier are
shown for simulated steps. The simulated steps are not shown in the standard
approval log.
13.8.3 Skipping COA Levels

You can configure the approval module to skip levels of approval if no COA
information is maintained for those levels, but is maintained for higher levels of
approval.
You can enable the skipping logic for individual AFS IDs. For more information, see
“Configuring Approval Flow Settings” on page 353.
The following diagram illustrates how skipping of COA levels works. In the
example, there are no approvers maintained in the COA at level 2, but there are
approvers maintained at level 3. The invoice skips level 2 and is directly sent to the
approver at level 3.
The numbers in the diagram reflect the approval levels.
VIM070500-03-CGD-EN-1
Restrictions The functionality of skipping the COA levels is implemented only for approver
levels (2 and higher). Both sequential and parallel line-based approval flows are
supported. Header-based approval flow is not supported.
Logging The approval steps simulated by skipping the COA levels are shown in the extended
approval log for the last dialog approval step that is executed. In the extended
approval log, no approver is shown for simulated steps. The simulated steps are not
shown in the standard approval log.
13.9 Coding Validation

If the customer has special requirements for validating the account assignment data
on the invoice coding screens, you can use the following BAdI infrastructure to
implement custom validations.
13.9.1 BAdI Validation for Parked Non PO Invoices

The following is the logic for BAdI validation:
1. Pre-convert check (BAdI method Check_field)

2. Convert to BSEG format (BAdI method convert_field)
3. Post-convert check (BAdI method valid_field)
4. Field status group check (BAdI method validate_fld_status_grp)
5. Final check (Cleanup messages)
The following is an example to validate Non PO invoice accounting data such as

Company Code by BAdI:
• Use OpenText implemented BAdI with name space /ors/.
• Create own BAdI with z name space and implement it.
• Extend validation of accounting data.
To validate Company Code for Non PO invoices by BAdI:
1. Run the SM30 transaction to maintain table /PTGWFI/Z_CONST, and locate the
record with Product Code IAP and Constant NPO_INV_CLASS. Enter Constant
Value /ORS/NON_PO_INVOICE_NEW.
2. Run the SM30 transaction with table /ORS/APPR_GL_CFV.
VIM070500-03-CGD-EN-1
13.9. Coding Validation
3. Select Company_Code (Field ID BUKRS).
4. Click the button.
5. Notice that BADI Field Name has the value Company_Code.
6. Click the BADI Implement button to display an implemented BAdI that

OpenText has delivered. If there is no OpenText delivered object, you can create
a new BAdI object and activate it (see “To modify the validation code for
Company_Code:“ on page 403).
VIM070500-03-CGD-EN-1
7. Test /ORS/COMPANY_CODE.
VIM070500-03-CGD-EN-1
To modify the validation code for Company_Code:
1. If you want to modify the validation code for Company_Code, create your object
and implement it:
Run the SM30 transaction and change the BAdI name from Company_Code to
ZCompany_Code (for example).
To save, click the icon.
2. Click the BADI Implement button and create a new BAdI, called
Z_COMPANY_CODE (for example).
3. Click the Create button.
VIM070500-03-CGD-EN-1
4. Choose the BAdI interface /ors/validation.
5. In Defined filters, select ZCOMPANY_CODE from the drop down list and save.
6. In the Interface tab, select Check_Field (for example).
VIM070500-03-CGD-EN-1
7. Copy code from the OpenText delivered /ORS/COMPANY_CODE, method

CHECK_FIELD, if necessary, and modify the code or create new code. Save and
activate Z_COMPANY_CODE.
8. Test Z_COMPANY_CODE.
VIM070500-03-CGD-EN-1
Coding is validated in the VALIDATEACCTDATA method of the Non PO invoice object.

The original delivered object is /ORS/NON_PO_INVOICE. The most recently delivered
version of this object is /ORS/NON_PO_INVOICE_4, which includes the latest BAdI
infrastructure.
VIM070500-03-CGD-EN-1
13.9.2 Standard Delivered Validations

The standard delivery includes the following fields:
Field
BAdI
G/L Account
/ORS/CL_IM_GL_ACCOUNT
Internal Order
/ORS/CL_IM_INTERNAL_ORDER
Item Text
/ORS/CL_IM_ITEM_TEXT
Material
/ORS/CL_IM_MATERIAL
PAOBJNR (profitability segment)

/ORS/CL_IM_PAOBJNR
Plant
/ORS/CL_IM_PLANT
Profit center
/ORS/CL_IM_PROFIT_CENTER
Tax Jurisdiction Code

/ORS/CL_IM_TAXJURCODE
Tax Code
/ORS/CL_IM_TAX_CODE
Trading Partner
/ORS/CL_IM_TRADING_PARTNER
Unit
/ORS/CL_IM_UNIT
Valuation Type
/ORS/CL_IM_VALUATION_TYPE
WBS Element
/ORS/CL_IM_WBS_ELEMENT
VIM070500-03-CGD-EN-1
13.9.3 Optional Coding

Coding may be optional, that means entering coding information is not always
mandatory. It depends on the following configurations:
• If Coding_delegate is selected in the approver persona (see “Configuring
Approver Persona Attributes” on page 391), and a delegated coder is specified,
coding is not required to approve the invoice. In this case, the coding step can be
skipped.
• If no delegated coding is specified, the coding requirement is controlled by the
constant EMPTY_CODING_MSG. The following configuration values for this
constant are available:
CHECK_SP:ERROR
If special handling is empty, the system issues an error message.
CHECK_SP:WARNING
If special handling is empty, the system issues a warning message.
ERROR
The system issues an error message.
WARNING
The system issues a warning message.
In some cases the coding is not completed but the information is entered in the
special handling instruction section. In these cases, the invoice can go through
the approval process nevertheless.
Note: The validation happens in the VALIDATEACCTDATA method of the Non

PO invoice class.
13.9.4 Approval Validation

13.9.4.1 Activating and Deactivating Approval Validation
During approval processing, Non PO DP documents are validated against an SAP
BAPI check. SAP BAPI requires specific data. The document is also checked to get
posted automatically in background with all relevant data.
You can enable or disable this check with a specific Z constant, product code IAP,
constant SKIP_BAPICHECK, description If set to 'X', BAPI check will not be
processed in Coding / Approval.
VIM070500-03-CGD-EN-1
13.10. Configuring the Profitability Segment Feature
13.9.4.2 Excluding Messages for Approval Validation

Some returned BAPI messages are not relevant to the end user. To avoid such
messages, a table/view /ORS/EXCL_MESS has been created. All success, information
or warning messages maintained in this table will not be shown to the end user.
Error messages, even if maintained in the table, will be shown to the end user.
To exclude messages for approval validation:
1. To maintain table /ORS/EXCL_MESS, use the SM30 transaction.

Alternatively, you can run /n/OPT/SPRO and navigate to Vendor Invoice
Management > Invoice Approval Configuration > Financial Processing >
Maintain Excluded Messages in Approval Validation.
2. Configure messages to be excluded, using the following parameters:
Message Class
Enter the name of the message class that contains the message to be
excluded.
Message ID
Enter the number of the message to be excluded.
Active
Select this check box to activate the exclusion of the message in the approval
validation.
13.10 Configuring the Profitability Segment Feature

A profitability segment is a way of accounting, similar to a cost center, for example.
A profitability segment is defined by a combination of characteristic values.
Characteristics can be concepts that already exist in the SAP ERP system (customer,
product, sales organization, and so on). But you can also define your own concepts
(such as “order size class”). These characteristics can be defined at line item level for
Non PO Invoices in VIM. The profitability segment is relevant for SAP GUI approval
and for the Approval Portal.
VIM070500-03-CGD-EN-1
13.10.1 Activating the Profitability Segment

1. To activate the profitability segment, run the /ORS/PSEG transaction.
2. In the Maintain Profitability Segment Fields screen, enter the Company Code
and click Get Fields.
3. To activate the profitability segment functionality for the given Company Code,
perform the following settings:
For SAP GUI approval

Select the Active check box at least for one row, enter a value 1 in the
respective field of the Seq. Num column, and save.
For the Approval Portal

Select the Active check box for the rows that the Profitability Segment
dialog box shall display. In Seq. Num, determine the order of the fields. The
sequence must start with 1 and should be a continuous sequence of
numbers, without any breaks in between.
Save your settings.
VIM070500-03-CGD-EN-1
13.10.2 Supported Scenarios and Limitations

Scenarios
• Only DP scenarios are supported. For posting the DP documents with
Profitability Segment, use BDC 35 for online posting and BDC 34 for background
posting. BDC 40 also supports the Profitability Segment feature.
• The Profitability Segment feature supports Non PO parked documents that are
parked in SAP ERP and sent for approval in VIM. All kinds of Non PO parked
documents are supported.
Limitations
• The Profitability Segment feature does not support PO documents.
• The DP indexing screen does not support entering Profitability Segment
information.
• Users can enter Profitability Segment information for Non PO documents in the
approval screen only.
13.10.3 Maintaining Custom Enhancements (User Exits)

The following user exit calling areas are available:
EXIT_ADD_FIELDS
While displaying the fields in the portal: can add or delete extra fields to or from
the existing list of fields based on any conditions
EXIT_BDC_BG
If any issue occurs during posting the data in the background mode with the
profitability segment data, the user can modify the profitability segment data
according to their needs.
EXIT_DATA_CHG
Can overwrite the data of the profitability segment before displaying the pop up
EXIT_DEL_VALID
Can add custom validations for portal before deleting profitability segment data
EXIT_READ_VALID
Can add custom validations for portal before displaying the pop up
EXIT_STOR_VALID
Can add custom validations for portal before saving the profitability segment
data
To maintain user exits:
1. Run the /ORS/PSEG transaction.

2. In the Maintain Profitability Segment Fields screen, in the application toolbar,
click Maintain Exits.
VIM070500-03-CGD-EN-1
3. In the Function Module column, enter the custom function modules and save.
For details about the function modules, see the following interface description.
Table 13-1: EXIT_ADD_FIELDS
Parameter Name Parameter Type Type/ Associated Type

Like
invoice_header IMPORTING TYPE /ORS/INVOICE_HDR
t_acct_data TABLES LIKE /ORS/INVOICE_ACCT_DATA
t_ps_segment TABLES LIKE /ORS/PROFIT_SEGMENT
Table 13-2: EXIT_BDC_BG

Like
im_head IMPORTING TYPE /OPT/VIM_1HEAD
t_item TABLES TYPE /OPT/VIM_1ITEM
t_criteria TABLES TYPE BAPIACKEC9
t_valuefld TABLES TYPE BAPIACKEV9
Table 13-3: EXIT_DATA_CHG

Like
ANZEIGE CHANGING
DIALOG CHANGING
I_COBL CHANGING LIKE COBL
I_ERKRS CHANGING LIKE TKEB-ERKRS
VIM070500-03-CGD-EN-1

Like
IS_GLOBAL_FIELDS CHANGING TYPE KEAK_YS_POPUP_GLOBAL
E_COBL CHANGING LIKE COBL
T_COPADATA TABLES LIKE COPADATA
Table 13-4: EXIT_DEL_VALID

Like
return TABLES LIKE BAPIRET2
Table 13-5: EXIT_READ_VALID

Like
Table 13-6: EXIT_STOR_VALID

Like
t_ps_segment TABLES LIKE /ORS/PROFIT_SEGMENT
VIM070500-03-CGD-EN-1
13.11 Logging and Monitoring in Invoice Approval

This section describes how to get logging and monitoring information in the Invoice
Approval, which is specifically helpful in case of errors.
Each step in the approval flow leaves log records, which can be viewed later, for
example for audit purposes. Basic information, for example who approved or
rejected an invoice and when, is being logged for the approval flow.
VIM supports advanced logging for level based approvals, allowing you to see the
accounting data at each step. This can help in reconstructing the accounting data
change history and explaining why the invoice was sent to a particular approver and
was (or was not) approved.
The advanced logging is available from the display of basic logging, for the steps or
actions that can affect the approval flow. The changes of accounting data, approvals
and rejections are recorded; entering the comments is not. For more information, see
“Using the Extended Approval Log” on page 415.
Basic log The basic approval log can be shown from the following locations:
locations
• VIM Workplace, DP dashboard, and DP document display: History pane,
Approval History
• Approval dashboard:
• SAP GUI, at the bottom of the screen

• Approval Portal, Invoice History
• Unified Dashboard, a dialog box will open when you click the View button for
the Invoice Approvals exception reason.
Extended log The extended log can be shown only in SAP GUI screens, wherever basic log is
locations shown. An additional column Display item details shows the Display item details
button for steps where the extended log is available.
Monitoring pos- VIM provides the following additional monitoring possibilities:

sibilities
• Processed by me, including the administrator transaction in SAP GUI, can show
a list of invoices processed by each user. For more information, see “Displaying
Processed Invoices” on page 415.
• VIM Workplace: Other Users View, display invoices of a specific approver.
• Central Reporting and VIM Analytics: search for invoices with specific approver.
• PDF History Log. For more information, see “Using the PDF History Log for
Invoice Approval” on page 416.
VIM070500-03-CGD-EN-1
13.11. Logging and Monitoring in Invoice Approval
13.11.1 Displaying Processed Invoices

You can display an overview of the invoices that individual users have processed. A
list of the processed invoices is displayed in a table. To access the selection screen for
this table, run the /n/ORS/PROCBYME_ADMIN transaction.
To display the Invoice Processed By <Username> table, enter the Approver and
optional additional search criteria, and click in the application toolbar.
The columns displayed in the result list are retrieved from the fields that are
maintained in the user preferences for the corresponding user. See “User Details
View” on page 56. The invoice list fields are reused.
13.11.2 Using the Extended Approval Log

VIM provides an extended log for line based approvals. This enables you to see for
each approval step, which lines were approved by the approver. It also shows what
the accounting data was in the line at the time of action. The extended approval log
is currently limited to the SAP GUI approval dashboard, the unified dashboard, and
the log that is displayed in the VIM Workplace.
For approval log lines corresponding to approval, rejection and change of

accounting information, there is an icon button shown in a new column of the
log.
Click this button to open the extended approval log.
In the following example, three invoice lines were approved by the user at level 1
(requester level).
VIM070500-03-CGD-EN-1
13.11.3 Using the PDF History Log for Invoice Approval

The PDF history log includes information about the Invoice Approval process. For
more information, see “PDF History Log” on page 770.
13.12 Enhancing Invoice Approval Using Extensions

You can use extensions to the Invoice Approval process to adapt the process to your
requirements. For example, you can configure a multi-step PO approval or a custom
usermap sourced from HR data. This section provides some examples for features
that are based on extensions.
13.12.1 Configuring Image Display

For displaying images using SAP GUI, the system uses standard SAP ArchiveLink
image display APIs to retrieve and display the image. So, there is no configuration
necessary for displaying images using SAP GUI.
If implementing the optional Approval Portal, the Approval Portal uses the
following infrastructure for displaying the images from the web browser during the
IAP process.
1. Clicking the View Invoice Image link in the Approval Portal will call SAP ERP
with the following function module:
FUNCTION /ORS/000007_IMAGE_DISP_URL or /ORS/000007_IMAGE_DISP_JPEG
2. This function module will in turn call a configurable function module that is
defined in the OpenText /PTGWFI/Z_CONST table, Product Code IAP. The
VIM070500-03-CGD-EN-1
13.12. Enhancing Invoice Approval Using Extensions
constant for Image Display JPEG is IMAGE_DIS_JPG_FM. The constant for Image
Display URL is IMAGE_DIS_URL_FM.
3. The data that is passed to this pluggable module is:
• Invoice object type

• Invoice object key
4. The output of the function module is a table of URLs if using URL (in most cases
there will be only one URL that is returned) or the binary data if using JPEG. The
Approval Portal will open a browser window.
5. The OpenText delivered base function module for opening the browser window
is the following:
FUNCTION /ORS/000007_TMP_IMAGE_DISP_URL
and /ORS/000007_TMP_IMAGE_DISP_JPEG
6. In the OpenText delivered base function module, the standard SAP function
module ARCHIVELINK_URL_GENERATE is called with the appropriate information
(Archive ID and Archive_Document_ID).
7. If the archiving system is setup as an http Content Server, the standard SAP
function module will generate the appropriate URL which can be used to
display the image in a browser window.
8. It is possible to replace the function module ARCHIVELINK_URL_GENERATE with a

Z-function module and incorporate any logic as deemed fit based on customer
requirements.
13.12.2 Defining the Custom Approver Class

OpenText provides the approver class /OPT/CL_IAP_APPROVER_BL with standard
functions. In this step, you define the custom approver class. You can use this class
for modifying or extending standard functions.
Example: By modifying/extending the method NEXT, you can implement your own logic to
determine the approvers in the approval process.
With the new level based approval flow, you must configure the class on document
type level in Approval Flow Settings (AFS); see “Configuring Approval Flow
To define the custom approver class:

locate the record with Product Code IAP and Constant APPROVER_CLASS.
VIM070500-03-CGD-EN-1
2. Define the custom approver class, using the following parameter:
Constant Value
Maintain the custom approval class. This class should conform to the /
ORS/APPROVER class (sub type).
13.12.3 Defining the Custom Invoice Class

In this step, you define a custom invoice class to modify or extend the functionality
of the OpenText delivered invoice class. The invoice class provided in the baseline
is /ORS/NON_PO_INVOICE_NEW for IAP of Non PO invoices and /
ORS/PO_INVOICE_NEW for IAP of PO invoices.
To define a custom invoice class for Non PO invoices:

Configuration > Technical General > Custom Invoice Class (Exit).
VIM070500-03-CGD-EN-1
13.12. Enhancing Invoice Approval Using Extensions
2. Define the custom invoice class (exit), using the following parameter:
Constant Value
Define the custom invoice class. This class must be a subtype of /
ORS/NON_PO_INVOICE.
You can use this class to extend the following methods:
VALIDATEACCTDATA
Validates the accounting data of invoices.
PROCESS_RETURN_MSG
Formats the return message from SAP ERP to something meaningful
that can be displayed on the web.
GET_NO_CODING_MSG
Returns a message if there is no coding information on the invoice.
CHECK_COBL
Is used to validate the coding block data on the invoice.
CONVERT_STD_FIELD
Converts the value of a field from input format to output format.
GET_FIELD_STATUS_GRP
Sets the display parameters (Optional, Required, Hidden) for invoice
fields while coding.
To define a custom invoice class for PO based invoices:
2. Maintain the value for Product Code IAP, Z constant PO_INV_CLASS.
3. Define the custom invoice class (exit), using the following parameter:
Constant Value
Define the custom invoice class. This class must be a subtype of /
ORS/PO_INVOICE_NEW.
You can use this class to extend the following methods:
VALIDATEACCTDATA
Validates the accounting data of invoices.
CONVERT_TO_RSEG_FORMAT
Converts the value of a field from input format to output format.
VIM070500-03-CGD-EN-1
13.12.4 Defining a Custom Usermap Class

In this step, you define a custom usermap class that can be configured to modify or
extend the standard delivered functionality in managing users in IAP. The standard
OpenText usermap class delivered in the baseline is class OPT/CL_IAP_USERMAP_BL.
To define a custom usermap class:

locate the record with Product Code IAP and Constant USERMAP_CLASS.
2. Define the custom usermap class, using the following parameters:
Constant Value
You can use this custom class to modify or extend the standard usermap
functionality. Methods of class /OPT/CL_IAP_USERMAP_BL can be extended.
13.12.5 Configuring the Bulk Approval Validation Exit

The bulk approval/rejection validation function module /
ORS/AINV_BULK_VALIDATE_INV provides a customer exit. The baseline validation
functionality might not meet your requirements. You can create a new function
module with the same interface as /ORS/AINV_BULK_VALIDATE_INV.
To configure the bulk approval validation exit:
2. Locate the record with Product Code IAP and Constant BULK_VALIDATE_EXIT.
3. Enter the name of your function module in Constant Value.
VIM070500-03-CGD-EN-1
13.13. Configuring the Fiori Invoice Approval Application
The baseline function module calls your function module if it is configured and
ignores the validations provided in baseline.
13.13 Configuring the Fiori Invoice Approval

Application
The Fiori Invoice Approval application (based on SAP Fiori®) runs as a solution
integration for Vendor Invoice Management on top of the OpenText Business Center
for SAP Solutions product. It is an optional component and handles the approval
processes for both Non-PO based and PO based invoices within an Fiori Task App.
Only approval of completely coded invoices is supported. Coding of invoices is not
supported. The Fiori Invoice Approval application offers the same functionality as
the existing (Java-based) Mobile Approval Portal, except the bulk processing of
invoices.
You can configure application settings within the Business Center Configuration and
also the VIM Approval Configuration. The specific baseline customizing is delivered
separately for both components.
The Fiori Invoice Approval application is based on exactly the same processes and
handling as described in “Invoice Approval“ on page 335.
For more information on the Business Center Configuration, see OpenText Business
For more information on the Business Center Solution Integration for Vendor
Invoice Management, see the Release Notes document of OpenText Business Center
for SAP Solutions 10 SP1.
13.13.1 Customizing the Initial Sort Order

Note: You can change the settings described in this section and the following
two sections in the Business Center Configuration.
You can change the initial sort order of the invoices which appear on the inbox list.
Default value is set to invoice due date in ascending sort order. If you want to
change the initial sort order, perform the following steps.
To customize the initial sort order:
1. Run the /n/OTX/PF00_IMG transaction and navigate to OpenText Business

Center for SAP Solutions > Workplace Configuration > Navigation > Nodes.
2. Select Node ID PS03_VIM_APR_INV and double-click Order by in the Dialog

Structure.
VIM070500-03-CGD-EN-1
3. In the Order by screen, remove the existing entry having Priority 1, and
configure a new entry, using the following parameters:
Priority
Enter 1.
Note: Only entry with Priority 1 is supported
Table Name
Enter name of the invoice structure /ORS/INVOICE_HEADER (name is not
shown in full length).
Field Name
Enter the field name that should be used for initial sort order.
Asc./Desc.
Select Ascending or Descending sort order.
4. Save your changes.
For more information see section 7.3.1.2 “Defining the order” in OpenText Business
13.13.2 Customizing the Web Viewer

OpenText™ Imaging Web Viewer (Web Viewer) can be used to display documents
within the Fiori Invoice Approval app. This setting supports to view documents in
Desktop mode only.
As a prerequisite, specific Web Viewer settings must be customized in the

maintenance views /IXOS/OA_CUST_A and /IXOS/OA_DOCTYPE.
For more information, see section 8.2.1 “Configuring basic settings” in OpenText
VIM070500-03-CGD-EN-1
13.13.3 Customizing Logical Systems

The customizing of logical systems is described in section 3.2 “Configuring logical
systems” in OpenText Business Center for SAP Solutions - Configuration Guide (BOCP-
CGD).
You can start the application process on a specific target system when using one
central system for document registration.
As a prerequisite, the central system running Business Center must have at least one
entry customized as logical system (default entry is set to LOCAL).
Multiple-system With special regard to this setup, you can also enable the Fiori Invoice Approval
access application for multiple-system access.
All VIM systems that you want to enable for multiple-system access must have a
valid logical systems entry customized on the central system running Business
Center.
Also a valid ABAP connection must be set up via trusted RFC. You must add new
entries having logical system and RFC destination to the logical systems table within
the general customizing of Business Center.
Notes
• All VIM systems that will be enabled for multiple-system access must have
at least installed VIM version 7.0 SP7 or VIM 7.5 SP3 in combination with the
latest SP of Business Center components.
• The customizing of the fields that are displayed in the Inbox and Header
section are taken from the first valid system entry which is maintained in the
logical systems list.
13.13.4 Customizing Display Fields

Note: You can change the settings described in this section and its sub-sections
in the VIM Approval Configuration.
All fields that can be displayed in the Fiori Invoice Approval application can be
customized within VIM customizing tables and views. Default settings are delivered
with OpenText Approval Portal baseline and can be changed as described in
“Invoice Approval“ on page 335. The Fiori Invoice Approval application is using the
settings stored with device name “Web Approval Portal” for customizing of
Desktop, and “Mobile Approval Portal” for customizing of Tablet and Smartphone
devices.
VIM070500-03-CGD-EN-1
13.13.4.1 Customizing Inbox List Fields

Fields that can be viewed in the inbox list are customized in VIM Invoice List Fields
maintenance view:
Invoice Approval Configuration > User Experience > Invoice List Configuration >
Maintain Invoice List Fields.
For more information, see “Configuring Invoice List Fields” on page 381.
The following fields are initially set on inbox list items and cannot be changed by
customizing:
• INVOICE_AMT
• CURRENCY
• INV_STATUS
The first entry within the sequence sort order will be shown as highlighted title field
in each list item. No description is added to the title field by default. The title field
cannot be one of the fields mentioned above.
Other fields will be shown underneath the title field. These fields cannot be one of
the fields mentioned above. A maximum of two other fields are supported to be
shown together with the title field, depending on the sort order of the sequence
settings. These fields are shown with leading description text. You can also
customize the description text in the VIM Invoice List Field maintenance view.
13.13.4.2 Customizing Detail Fields

Detail fields are shown in the detail pane of the Fiori Invoice Approval application.
They can be separated into three sections:
• Header fields
• Header detail fields
• Item fields
On the Header fields section, the fields that are customized for the Invoice List are
displayed; see “Customizing Inbox List Fields” on page 424.
Header detail fields and Item fields are customized in the VIM Invoice Detail Fields
maintenance view:
Invoice Approval Configuration > User Experience > Invoice List Configuration >
Maintain Invoice List Fields.
Header detail fields are customized with Field Type set to Header Field. If no field
description has been customized, the data is not shown on the UI.
VIM070500-03-CGD-EN-1
Item fields are customized with Field Type set to Item Field. If no field description
has been customized, the default field name is shown on the UI.
Notes
• The number of Item fields that can be shown in the specific item table is
limited to 10 maximum.
• Any field that does not contain a valid value is not displayed on the UI.
13.13.5 User Authorization

An SAP user account is required to use the Fiori Invoice Approval application. The
SAP user account must be available on the SAP FIORI UI / Gateway system and also
on the SAP ERP system having the following authorization objects minimum.
The SAP user account that is used on the SAP FIORI UI / Gateway system requires
the following:
• Authorization object S_SERVICE (with full authorization)

• Authorization object S_USER_GRP (Activity: Display)
The SAP user account which is used on the SAP ERP system requires the following:
• Authorization object J_6NPF_NAV (BC Workplace)

• Authorization object J_6NPF_WTY (BC Workplace)
• Authorization object S_RFC (Activity: Execute)
• Authorization object S_RFCACL (trusted RFC)
Note: The SAP user must have the identical user name on both systems.
13.13.6 Launching the Fiori Invoice Approval Application

If you want to launch the Fiori Invoice Approval application directly, browse the
following relative URL:
/sap/bc/ui5_ui5/otbcwui/pf07_bc_ui/index.html?
nodeId=PS03_VIM_APR_INV&wobjType=
PS03_PRC_VIM_APR&workplaceId=WP_INBOX
The Fiori Invoice Approval application can also be integrated and started as a tile in
a Fiori Launchpad.
For more information, see section 9 “Fiori Task App” in OpenText Business Center for
SAP Solutions - Configuration Guide (BOCP-CGD).
VIM070500-03-CGD-EN-1
Chapter 14
VIM Analytics (New)
The new VIM Analytics (VAN) replaces the “old” VAN, which was in use in VIM
prior to version 7.5.
For documentation of the “old” VAN, see the VIM 7.0 documentation.
VAN gives users a clear data report on their open and completed invoices as well as
the VIM workflows. VAN also includes DP documents and workflows. VAN allows
you to track the documents routed through SAP workflows by VIM or even without
any VIM process.
Note: If you want to track documents without any VIM process in the new
VAN, you must maintain the constants DOCTYPE_NPO and DOCTYPE_PO, product
code 005, of the WebFlow Constant Table /PTGWFI/Z_CONST.
VAN has been completely reworked for VIM 7.5. Here are some of the new features:
• The new VAN is highly optimized for SAP® HANA database systems to support
queries on mass data very quickly.
• The new VAN is based on a completely redesigned data base schema to ensure
high data quality and improved performance.
• The new VAN comes with a central place of configuration in the VIM
configuration tree. The baseline is delivered with default settings for the new
VIM Analytics.
VAN presents the data report results in the SAP List Viewer (ALV).
You can use VAN to check the current document status, the current agent and
exception reason of a particular invoice. Besides the result list, there are further
views available that provide detail information about a selected invoice:
• Process View
This view displays open and completed VIM processes together with the current
workflow status, the current agent and exception reason of this particular
process.
• Image View
This view displays the scanned, linked images.
• Line Item View
This view displays the invoice line items.
• History View
This view displays the VIM process history.
VIM070500-03-CGD-EN-1
Chapter 14 VIM Analytics (New)
• Comments View
This view displays the comments that have been added during the VIM process
and during the approval process.
The new VAN supports all kind of database systems. On a SAP system with SAP
NetWeaver Application Server ABAP 7.40 SP05 or higher, you have the choice
between the following types of data selection:
• ABAP Core Data Services (CDS) views
• Data selection without ABAP CDS views, that means, using standard DDIC
tables and views
You can start VAN by the /OPT/VIM_VA2 transaction, or following OpenText

Vendor Invoice Management > SAP menu > Reports > VIM Analytics (New).
There are further transactions available, tailored to specific roles:

• /OPT/VIM_VA21 (AP Basic)
• /OPT/VIM_VA22 (AP Advanced)
• /OPT/VIM_VA23 (Procurement)
• /OPT/VIM_VA24 (Monitor)
For more details to the role-specific transaction codes, see section 3 “VIM Analytics:
Getting Data Reports” in OpenText Vendor Invoice Management for SAP Solutions -
Reference Guide (VIM-RGD).
14.1 Report for One-time Data Upload and for

Consistency Check of Documents
For documents created before VIM 7.5 SP2, you must run a report once. This report
updates the database tables that the new VAN is working with. Without running
this report, documents created before VIM 7.5 SP2 may be missing or may be
displayed incorrectly in the new VAN.
As the administrator, you may also run this report for chosen documents in case of
any data inconsistency in the database tables that the new VAN is working with.
The report is available with VIM 7.5 SP2.
VIM070500-03-CGD-EN-1
14.1. Report for One-time Data Upload and for Consistency Check of Documents
14.1.1 Scope of the Report

The report is based on data maintained in the following new tables:
/OPT/VIM_2HEAD
Extension table for /OPT/VIM_1HEAD
/OPT/VIM_1PROC
Contains all processes relevant for one document ID
/OPT/VIM_1WI_AGT
Contains the current agents of work items
These tables are filled consistently during the runtime of the work item.
The report has two main scopes:
Initialization mode
When upgrading from a lower VIM version (6.0), the mentioned tables need to
be filled initially for old instances. The new VIM Analytics will not show any
values if the /OPT/VIM_2HEAD table is not filled. You must run this migration
report mode accordingly.
Update mode
As the administrator, run this report mode for chosen document IDs to correct
data in the mentioned tables.
14.1.2 Running the Report

To call the report, run the SE38 transaction for program /
OPT/VR_ANALYTICS_750_INIT.
14.1.2.1 Modes for Running the Report

The following modes for running the report are available.
• Running the report in dialog

• Running the report in background
Running in dialog
• Running in dialog is mainly meant for selected document IDs.
• The report provides a detailed protocol if you use the Extended Display
Options.
• The Test run delivers a preview of the results.
• Productive mode provides update or repair of the selected document IDs.
For more information, see “Using the Selection Screen” on page 430.
VIM070500-03-CGD-EN-1
Running in background
• The report provides only an error protocol.
• In test mode, you can use the report for performance calculation (Performance
Analysis through the SAT or the SE30 transaction).
• Productive mode allows mass processing.
• You can schedule the report as an SAP job. For more information, see VIM 7.5
Upgrade Guide, available in the Knowledge Center: https://
knowledge.opentext.com/knowledge/cs.dll/Properties/59553598.
14.1.2.2 Using the Selection Screen

The selection screen offers the following parameters:
Document selection
Document-ID
Mandatory field: enter the Document IDs.
Select Charge
The processing in the report is done by charges. You can maintain the number of
processed documents before committing (COMMIT). In normal cases, leave this
number on the standard setting. For optimization, you can set this parameter
differently.
Update properties
Test Run
Select this check box to achieve that the report will not update any values in the
database tables. You can use this mode for runtime measurement before
planning the actual productive run or to check what updates would be done in
detail.
VIM070500-03-CGD-EN-1
14.1. Report for One-time Data Upload and for Consistency Check of Documents
Extended Display Options
Note: These options are only available in Test Run mode and in dialog
processing. In background processing, clear the Extended Display Options
check boxes.
Display calculation results

Select this check box to achieve that the report shows a list comparing the
current database values with the ones calculated by the report. For more
information, see “Output” on page 431. You can use this mode especially to
analyze issues with content of the tables for single documents.
Only show inconsistent data

Only relevant in combination with option Display calculation results. Select
this check box to achieve that the protocol will only show lines with differing
content between database and calculation. If the check box is cleared, the
protocol will show all database content compared to the calculated values.
14.1.2.3 Output
The report output differs if Display calculation results is selected or not.
Display The report shows a protocol about successful or unsuccessful execution. You can
calculation access the protocol in the Job Spool when running in the background.
results not
selected
Display
The report calculates all values within the selection range and displays them in
calculation intervals according to the Select Charge setting. On the main screen, you can
results selected analyze the tables for these intervals by pressing the respective buttons. Click Go to
next interval to start the calculation of the next interval.
VIM070500-03-CGD-EN-1
Table view The table view shows a list of all values already present in the database and
compares them to the calculated value. The first line is representing the current
value in the database, the second line the calculated value.
VIM070500-03-CGD-EN-1
14.2. Customizing Profiles for the New VAN
14.2 Customizing Profiles for the New VAN

You configure VAN for all general settings within a profile. A profile describes all
relevant default user screen settings and enables you to integrate your own
processing logic. You can assign different profiles directly to different users if
Note: Within baseline delivery, a general profile (DEFAULT) is delivered, which

is called whenever no specific user profile has been configured. This profile
must always be available in all involved systems where the new VAN runs.
You can assign a specific user profile using the /OPT/VVA2_CUST_PROF user
parameter.
The following customizing steps are necessary to maintain customizing profiles:

• “Defining a Customizing Profile” on page 433
• “Maintaining General Profile Settings” on page 434
• “Defining Field Mapping (Only When Using ABAP CDS Views)” on page 438
• “Defining and Assigning Action Buttons” on page 441
14.2.1 Defining a Customizing Profile

This section describes an overall profile with a unique ID and the corresponding
description.
To define a customizing profile:

Management > Cross Component Configuration > VIM Analytics (New) >
Maintain Customizing Profiles.
2. Define the customizing profile, using the following parameters:
Profile
Define the profile with a unique ID.

Enter a description for the profile.
VIM070500-03-CGD-EN-1
14.2.2 Maintaining General Profile Settings

In this step, you configure general profile settings used by the new VAN during
runtime. The general profile settings comprise pure UI-related settings as well as
some important functional application parameters.
All UI-related settings are taken into account if you run the new VAN for the first
time or if you decide to reset the UI layout to the general default settings.
To maintain general profile settings:

2. Select the customizing profile you want to maintain.
3. In the Define Customizing Profiles screen, in the Dialog Structure, double-

click Define General Profile Settings.
4. Configure the general profile settings, using the parameters described in the
following subsections.
Customizing Profile
Predefined customizing profile, for which the settings are valid.
VIM070500-03-CGD-EN-1
14.2.2.1 Application
Logo Name
Enter the object name of any corporate branding logo image. If you leave the
field empty, no logo image is displayed in the new VAN.
Default value: /OPT/VIM_LLECMLOGOFS
Note: VIM provides the global feature to control whether logo images
should be displayed using the DASHBOARD_NO_LOGO constant, product code
005 of the WebFlow Constant Table /PTGWFI/Z_CONST. If you want to use
this feature, do not change the Logo Name parameter.
Application Class
Enter the application ABAP class that contains the VAN application logic.
Default value: /OPT/CL_V_VA2_APPLICATION
Factory Class
Enter the factory ABAP class that creates the object instances for the new VAN,
for example the object instances for the data providers.
Default value: /OPT/CL_V_VA2_OBJECT_FACTORY
UI Class
Enter the UI controller ABAP class that contains the VAN UI specific logic.
Default value: /OPT/CL_V_VA2_UI_CONTROLLER
Data Class
Enter the data provider ABAP class that contains the VAN data load logic.
Default value: /OPT/CL_V_VA2_DATA_PROVIDER
User Class
Enter the VAN user ABAP class that contains the logic to read and save user-
specific profile settings.
Default value: /OPT/CL_V_VA2_USER
14.2.2.2 Data Selection

Selection Mode
On a SAP system with SAP NetWeaver AS ABAP 7.40 SP 05 or higher, you can
decide whether you want to run VAN with ABAP CDS views or without. ABAP
CDS views are database independent, with some exceptions if the databases do
not yet cover all the functionalities, for example views with parameters. On SAP
NetWeaver AS ABAP versions lower than 7.40 SP 05, VAN will always run
without ABAP CDS views.
Select Selection Mode Use ABAP CDS Views to specify that the data selection is
using ABAP CDS views.
Select Selection Mode Use no views to specify that the data selection is not
using ABAP CDS views, but using standard DDIC tables and DDIC views
instead.
VIM070500-03-CGD-EN-1
Note: Selection Use SAP HANA Views is no longer supported.
Default value: Use no views
Note: Regarding the use of ABAP CDS views, it varies from system to
system which configuration is the best. But based on extensive mass data
tests, OpenText generally recommends the following configuration for
different database systems.
• On an SAP HANA database, select Use ABAP CDS Views.
• On an Oracle® Database system, select Use no views.
• On a Microsoft® SQL Server® database system, select Use ABAP CDS
Views.
• On other database systems, start with Use no views and check whether
the runtime is sufficient. If it is not, you can switch to Use ABAP CDS
Views and the other way round seamlessly.
However, these are general recommendations only. Your system might

react differently from OpenText's test systems. This is why OpenText
strongly recommends that you test the setting for the Selection Mode on
your system and set it accordingly. You can switch the setting whenever
needed.
RFC Selection Function Module for document headers (RFC Doc. Hdr.)
Enter a function module to retrieve the document headers for the result list,
depending on the chosen selection criteria.
Default value: /OPT/V_VA2_DOC_HDR_GETLIST
RFC Selection Function Module for document line items (RFC Line Items)
Enter a function module to retrieve the document line items to a selected
document header for the line item view.
Default value: /OPT/V_VA2_DOC_ITEM_GETLIST
RFC Selection Function Module for document processes (RFC Processes)

Enter a function module to retrieve the workflow processes to a selected
document header for the process view.
Default value: /OPT/V_VA2_DOC_WI_GETLIST
VIM070500-03-CGD-EN-1
14.2.2.3 Action Buttons

Reuse Buttons
The old VAN provides the feature to add function buttons to the ALV toolbar.
Table /OPT/VIM_FCODE contains all function buttons available in the document
view of the old VAN report.
The new VAN provides the feature to add action buttons to the result list, to the
process view, and to the line item view. Regarding the result list, you can decide
whether you want to reuse all the action buttons already defined for the old
VAN or whether you want to configure the action buttons independent from the
old VAN.
The parameter Reuse Buttons allows to configure whether the action buttons
already defined for the old VAN shall be reused for the result list of the new
VAN.
Select this check box to specify that the custom buttons configured for the old
VAN shall be reused for the new VAN.
Clear this check box to specify that the custom buttons assigned to the VAN
customizing profile shall be used instead of reusing the custom buttons of the
old VAN.
Default value: <cleared>
14.2.2.4 Result List

Classical ALV
In the context of SAP HANA, SAP has provided a new version of the SAP List
Viewer, the SAP List Viewer with Integrated Data Access (IDA ALV). The IDA ALV
introduces some major database feature improvements compared to the classical
ALV.
Example:
• Database paging: The result will be selected from the database in pages - there is no
need to transfer the full result set to the application server any more.
• Operations like aggregation, sorting and filtering in the ALV grid will be pushed
down to the database layer.
The IDA ALV can be used not only on a SAP HANA database system but on all
other database systems as well.
With the Classical ALV check box, you configure which version of the SAP List
Viewer you want to use for the result list.
Select this check box to specify that the classical ALV is used for the result list.
Not yet supported:Clear this check box to specify that the IDA ALV is used for the
result list.
Note: This setting influences the result list only. For all details views, the
classical ALV is used.
VIM070500-03-CGD-EN-1
Default value: <selected>
Size Ratio %
Enter the size of the result list in percent of the detail pane. If you do not enter a
value, the system automatically uses a standard value of 50%.
Example: A value of 60 means that 60% of the width of the window are reserved for the
result list and 40% of the width are reserved for the detail pane.
Default value: 50
14.2.2.5 Detail Pane

Detail pane alignment (Det. Pane Agn.)
Select the alignment of the detail pane. Currently there are two values available:
• No Detail Pane: This removes the detail pane.

• <empty>: This displays the detail pane on the right.
Default value: <empty>
Plug-In Type
Enter a predefined plug-in type to get all mapped plug-in definitions that are
available as buttons in the detail pane toolbar.
Default value: VIM_VA2 - VIM Analytics
Plug-In ID
Enter the plug-in that is initially loaded in the detail pane. If you do not enter a
value, the system automatically uses a standard value of 21 (Display Workflow
Processes).
Default value: 21 - Display Workflow Processes
14.2.3 Defining Field Mapping (Only When Using ABAP CDS

Views)
This step is only relevant if your VAN is running on a SAP NetWeaver AS ABAP
7.40 SP05 or higher and if the data selection is configured to be done with ABAP
CDS views.
In this step, you configure the following parameters:
• The input parameters of the ABAP CDS views: Fields of the VAN selection
screen are assigned to input parameters of the ABAP CDS views, restricting the
data to be selected.
• The output parameters of the ABAP CDS views: Fields of the ABAP CDS views
are assigned to fields of the ABAP table containing the selection result.
VIM070500-03-CGD-EN-1
To define field mapping:


click Define Field Mapping.
4. Define the field mapping using the following parameters:
Selection Mode
Select Use ABAP CDS Views if the field mapping is relevant for the data
selection with ABAP CDS views.
Not yet supported: Select Use no views if the field mapping is relevant for the
data selection without ABAP CDS views, that means for the selection with
standard DDIC tables and views.
View
Enter the type of view that the field mapping is related to.
Not supported for ABAP CDS views:Line Item View and Process View.
Note: Header View corresponds to the result list.
Database Field Name

Enter the name of the field of the ABAP CDS view.
Input/Output field of data selection (InOut)

Select Input Field if you want to assign a selection field (parameter or
select-options on the VAN selection screen) to a field of an ABAP CDS view.
VIM070500-03-CGD-EN-1
This means that the selection field works as an input parameter for the
ABAP CDS view.
Select Output Field if you want to define the mapping for an ABAP CDS
view field to a field of the ABAP table containing the selection results. This
means that the selected value is assigned to the respective field in the result
table.
Application Field Name

For an input field, enter the name of the parameter or select-option on the
VAN selection screen. Cut off the first two letters, for example cut of the P_
of parameters and S_ of select-options.
Example: For selection-option S_LIFNR, enter LIFNR.
For an output field, enter the name of the field in the ABAP result table.
This means a field name of structure /OPT/VVA2_CDS_DOC_HDR_ST.
Example 14-1: Vendor selection
The user selects vendors on the VAN selection screen to get all invoices of
these vendors. The select-option for vendors is S_LIFNR. The ABAP CDS
view for the result list has an input parameter LIFNR_I to limit the selection
of document headers regarding vendors.
The mapping entry has the following parameters:
Selection Mode Use ABAP CDS Views

View Type Header View
Database Field Name LIFNR_I
Input/Output field of data selection Input Field
Application Field Name LIFNR
Example 14-2: Vendor display
The user chooses to display the vendor of an invoice in the result list. The
ABAP CDS view for document headers selects the vendor into the output
field LIFNR_O. The ABAP table containing the selection results is based on
the /OPT/VVA2_CDS_DOC_HDR_ST structure. The LIFNR field of this structure
represents the vendor.
The mapping entry has the following parameters:
Selection Mode Use ABAP CDS Views

Database Field Name LIFNR_O
Input/Output field of data selection Output Field
VIM070500-03-CGD-EN-1
Application Field Name LIFNR
14.2.4 Defining and Assigning Action Buttons

VAN allows you to add any action buttons to the result list toolbar, to the process
view toolbar and to the line item view toolbar at any time. In a first step, you
technically define the buttons that are available in the VAN. In a further step, you
assign the button to views of the VAN within a VAN customizing profile.
If you want to integrate OpenText™ Extended ECM for SAP® Solutions into VAN as
a custom button that opens a separate window, see the respective Notes in the
following sections.
14.2.4.1 Defining Action Buttons for VAN

In this step, you technically define the buttons that are available in VAN. The button
Display Dashboard is delivered in the baseline.
To define action buttons:


click Define Action Buttons.
3. Configure the action button using the following parameters:
View
Select the type of view that the button is relevant for.
Button ID
Enter a unique numeric button ID that defines the action button.
Button Type
Select the button type used to generate the button during runtime. Select
one of the following button types:
VIM070500-03-CGD-EN-1
Single action
All buttons defined as single actions are generated as separate buttons
in the button toolbar.
Separator
This setting allows you to insert standard SAP separator lines to group
the generated buttons from a visual point of view.
Button Text
Enter the button text, which is displayed as text label for the generated
button during runtime.
Quickinfo
Enter quick info text, which is displayed for the button during runtime.
Icon name
Assign an icon to the generated button or use the button exit to assign the
icon dynamically.
Button Exit
Enter an exit function module that dynamically performs the following
actions:
• skip the creation of a button during runtime, or

• change the button itself
You can use the exit function template: /OPT/V_VA2_EXIT_TEMPL_BUTTON.
For the Extended ECM for SAP Solutions integration

Function module /OPT/C_XECM_VA2_BUTTON_H is delivered as a
template to create custom implementation if needed.
Action Function
Enter an exit function module that runs the logic of the selected action. You
can use the following exit function templates:
• For result list: /OPT/V_VA2_EXIT_TEMPL_ACTEXE_H.

Example implementation for Display Dashboard: /
OPT/V_VA2_EXIT_ACTEXE_H_DASHB
• For line item view: /OPT/V_VA2_EXIT_TEMPL_ACTEXE_L
• For process view: /OPT/V_VA2_EXIT_TEMPL_ACTEXE_W.
For the Extended ECM for SAP Solutions integration

Enter a function module that calls the workspace window. You can
use function /OPT/C_XECM_VA2_LFA1_ACTEXE_H for vendor
workspace (business object LFA1). You can use this module as
reference to create custom modules for other business objects.
Active
Select this check box to set the button definition to active.
VIM070500-03-CGD-EN-1
14.2.4.2 Assigning Action Buttons

In this step, you assign the buttons to views of the VAN within a VAN customizing
profile. The assignment of button Display Dashboard to the default VAN
customizing profile is delivered in the baseline.
Note: You can configure whether custom buttons configured for the old VAN
shall be reused for the new VAN (see “Action Buttons” on page 437). If the
custom buttons of the old VAN are reused, the assignment of action buttons
described in this section is ignored during runtime.
To assign action buttons:


click Assign Action Buttons.
4. Assign action buttons using the following parameters:
Customizing Profile
Predefined customizing profile for which the button assignment settings are
valid.
View
Select the type of view that the action button shall be assigned to.
Button ID
Enter the ID of the button that shall perform a button action.
Button Text
Button text, which is displayed as text label for the generated button during
runtime.
VIM070500-03-CGD-EN-1
Button Sequence (But. Seq.)

Define the sequence in which the assigned action buttons are generated
within the toolbar of the respective view.
14.3 Layout Variants

One target when implementing the new VAN powered by SAP HANA was a good
performance of the data selection. One principle that we followed was to limit the
number of columns to be read from the database to the number of columns the user
needs.
With layout variants, you define the fields to be read in the result list, the process
view and the line item view. By ensuring that your layout variants contain only
those fields that are needed by your users, you can positively influence the runtime
of VAN.
Besides hiding or displaying columns, layout variants allow you to change the
sequence of the displayed columns or to change the sort order.
VAN delivers some preconfigured layout variants for the ALV grid of the result list,
the process view and the line item view to ensure that only a limited set of fields is
selected:
Result List
• /OPT/VA2_H01: VIM Analytics: Result View 1 – Extended

with nearly all invoice header fields (about 80 out of about 100 fields)
• /OPT/VA2_H02: VIM Analytics: Result View 2 – Basic
with the most important invoice header fields (about 60 out of about 100
fields)
Process View
• /OPT/VA2_P01: VIM Analytics: Process View 1

with the most important fields regarding the VIM workflow processes
Line Item View
• /OPT/VA2_I01: VIM Analytics: Item View 1 – Extended

with the most important invoice line item fields, including a variety of
selected accounting objects (about 40 out of more than 140 fields)
• /OPT/VA2_I02: VIM Analytics: Item View 2- Basic
with the most important invoice line item fields (about 20 out of more than
140 fields)
However, if you experience performance issues or if a good performance is critical

for your business, you should create your own default layout variants for the result
list, the process view and the line item view. Of course it is always possible for the
user to define user-specific layout variants.
VIM070500-03-CGD-EN-1
14.4. Additional Configuration Options for the New VAN
To change layout variants:
• Use the standard SAP function Change layout in the ALV grid control.
To open the layout context menu, click the right portion of the Select layout
button .
For detailed information about the layout features, see the SAP Help: http://
help.sap.com/erp2005_ehp_06/helpdata/EN/8d/
e994374c9cd355e10000009b38f8cf/frameset.htm.
14.4 Additional Configuration Options for the New

VAN
Besides the settings in the customizing profile, VAN offers the following additional
features to adjust the VAN report:
• “Adding Custom Fields in the Selection Screen” on page 445
• “Adjusting the Selection Screen by Variants” on page 449
• “Adding Custom Fields in Output Tables” on page 449
• “Enabling Hot Spot Functionality for Fields in Output Tables” on page 454
• “Specifying Discount Light Settings for VAN” on page 457
14.4.1 Adding Custom Fields in the Selection Screen

VAN allows you to add additional custom fields to be considered at the selection of
invoices. In a first step, the selection screen is extended to add additional custom
fields. Then the data selection needs to be extended. Finally, when using ABAP CDS
views, the mapping between the selection fields and the input fields of the ABAP
CDS view(s) needs to be maintained.
14.4.1.1 Extending the Selection Screen

The /OPT/VIM_ANALYTICS_750_SCREEN report offers the enhancement point /
OPT/EP_VIM_VA2_SEL_SCREEN to add additional selection criteria to an additional
User Extension panel above the Report Options panel.
Ensure that select-options start with S_ and parameters start with P_.
VIM070500-03-CGD-EN-1
Example implementation:
The implicit enhancement option at the end of include /

OPT/VIM_ANALYTICS_750_SCREEN can be used to adjust the text of the custom
selection fields and implement value helps and validity checks.
14.4.1.2 Enhancing the Data Selection

The user input in the additional selection field needs to be considered during the
selection of the invoices. How to enhance the data selection depends on whether you
use ABAP CDS views or not.
With ABAP Class /OPT/CL_V_VA2_DATA_PROV_BE_CDS, together with its superclass /

CDS views OPT/CL_V_VA2_DATA_PROV_BE, is responsible for the data selection with ABAP CDS
views. This class offers enhancement points to pass the user input in the additional
custom selection fields to the actual data selection.
The enhancement points are grouped in the following enhancement spots:
• /OPT/ES_VIM_VA2_DATA_PROV_BE_C for enhancements to class /

OPT/CL_V_VA2_DATA_PROV_BE_CDS
• /OPT/ES_VIM_VA2_DATA_PROV_BE for enhancements to class /
OPT/CL_V_VA2_DATA_PROV_BE
Note: Always read the instructions mentioned in the coding of the classes very
carefully before implementing enhancement points.
To enhance the data selection when using ABAP CDS views:
1. Enhance the appropriate ABAP CDS views by an additional input parameter.
2. Click the Attributes tab of class /OPT/CL_V_VA2_DATA_PROV_BE.
3. Add a new class attribute similar to the existing attributes starting with MR_ as
implicit enhancement. This new class attribute represents a range table for the
new selection criteria. Use type RSELOPTION or any range type appropriate to
your selection criteria.
VIM070500-03-CGD-EN-1
4. Implement the explicit enhancement points of enhancement spot /

OPT/ES_VIM_VA_DATA_PROV_BE for the following purposes:
• to declare local structures for the custom selection ranges

• to refresh the custom selection ranges initially
• to map the user input in the custom selection fields to the custom selection
ranges

OPT/ES_VIM_VA2_DATA_PROV_BE_C
• Enhancement point /OPT/EP_VIM_VA2_DATA_PROV_WHER to pass the user

input in the additional custom selection fields to the WHERE clause of the
SELECT statement on the ABAP CDS views
Example implementation:
lv_db_fieldname = me->get_db_fieldname_hdr( 'ARCHIV_ID' ).
IF NOT mv_dph_view IS INITIAL.

IF NOT mr_archid[] IS INITIAL.
ev_where_clause_dp = |{ ev_where_clause_dp } AND
{ lv_db_fieldname } IN @mr_archid|.
ENDIF.
ENDIF.
IF NOT mv_poh_view IS INITIAL.

ev_where_clause_po = |{ ev_where_clause_po } AND
ENDIF.
ENDIF.
IF NOT mv_npoh_view IS INITIAL.

ev_where_clause_npo = |{ ev_where_clause_npo } AND
ENDIF.
ENDIF.
• Enhancement point /OPT/EP_VIM_VA2_DATA_PROV_FREE to finally free the

resources of the custom selection ranges
Without ABAP Class /OPT/CL_V_VA2_DATA_PROV_BE_STD, together with its superclass /

CDS views OPT/CL_V_VA2_DATA_PROV_BE, is responsible for the data selection without ABAP
CDS views. These classes offer multiple enhancements points to pass the user input
in the additional custom selection fields to the actual data selection.
The enhancement points are grouped in the following enhancement spots:
• /OPT/ES_VIM_VA2_DATA_PROV_BE_S for enhancements to class /

OPT/CL_V_VA2_DATA_PROV_BE_STD
• /OPT/ES_VIM_VA2_DATA_PROV_BE for enhancements to class /
OPT/CL_V_VA2_DATA_PROV_BE
Note: Always read the instructions mentioned in the coding of the classes very
carefully before implementing enhancement points.
VIM070500-03-CGD-EN-1
To enhance the data selection when not using ABAP CDS views:
1. Click the Attributes tab of class /OPT/CL_V_VA2_DATA_PROV_BE. Add a new

class attribute similar to the existing attributes starting with MR_ as implicit
enhancement. This new class attribute represents a range table for the new
selection criteria. Use type RSELOPTION or any range type appropriate to your
selection criteria.

OPT/ES_VIM_VA_DATA_PROV_BE for the following purposes:
• to declare local structures for the custom selection ranges

• to refresh the custom selection ranges initially
• to map the user input in the custom selection fields to the custom selection
ranges

OPT/ES_VIM_VA2_DATA_PROV_BE_S for the following purposes:
• to enhance the WHERE condition of a data selection on /OPT/VIM_1HEAD or /

OPT/VIM_2HEAD tables (if the selection fields are fields in these tables)
• to filter the result list by the custom selection ranges

• to finally free the resources of the custom selection ranges
Note: There are three enhancement points available at different points of time
in the process to filter for custom selection ranges. It may have negative effects
on the runtime when using an inappropriate enhancement point for filtering.
The more restrictive selection criteria is, the more you should use it for filtering
at the beginning of the filter process.
The other way round, if you have to select all VIM documents (technically, all
records of /OPT/VIM_1HEAD) before you can judge whether a document fulfills
the selection criteria or not, you should use the enhancement point at the end
of the filter process.
14.4.1.3 Defining Field Mapping (Only When Using ABAP CDS Views)
The input of the additional selection field needs to be passed to the appropriate
input parameter of the ABAP CDS views. Define an additional field mapping from
the selection field to the ABAP CDS views field in VIM customizing:
Selection Mode Use ABAP CDS views

Database Field Name <Name of ABAP CDS view field>
Input/Output field of data selection Input Field
Application Field Name <Name of the selection field without the leading S_ or
P_>
VIM070500-03-CGD-EN-1
For more details, see “Defining Field Mapping (Only When Using ABAP CDS
Views)” on page 438.
14.4.2 Adjusting the Selection Screen by Variants

If you run VAN with complex search criteria periodically, the process of manually
reentering the information with each report run could be very time-consuming. To
facilitate this process, you can use a report variant. When running a report, you
enter the search criteria once and save it under a unique variant name. Whenever
you need to run the same report, you simply enter the variant name and the system
automatically writes the values stored in the variant to the fields on the selection
screen.
In addition, the VAN selection screen offers more than 80 selection fields. Not all of
these selection fields may be required for all user groups. To keep the selection
screen as clearly as possible, you can use variant-specific attributes. Variant-specific
attributes enable you to hide individual fields, for example, or to write-protect data.
Furthermore, you can store the selection values defined for a selection option as a
separate selection variable. Changes made to the variable then affect all of the
variants in which it is used.
For detailed information about variants on the selection screen, see the SAP help.
14.4.3 Adding Custom Fields in Output Tables

VIM Analytics allows you to add additional custom fields in the following output
tables: result list, line item view, and process view. In a first step, you extend the
output structure for the output tables to add additional custom fields. In a second
step, you populate the custom fields in the output tables.
14.4.3.1 Adding Custom Fields to the Output Structure

In this step, you extend the output structures for the result list, the line item view, or
the process view with custom fields.
To add fields to the output structure of the result list:
1. Run the SE11 transaction to display structure /OPT/VVA2_OUT_DOC_HDR_ST.
2. Create or update an append structure: On the Goto menu, click Append

Structure.
3. When creating a new append structure, enter a short description.
4. Add the customer fields that you want to add into the structure fields and
provide related data elements. The data element will provide the field label, for
example the column heading.
5. Save and activate the append structure and put it into a transport request.
VIM070500-03-CGD-EN-1
6. By default, the new custom fields are not yet displayed in the result list. To get
the custom fields displayed, launch VIM Analytics and change the layout
variant for the result list. For details, see “Layout Variants” on page 444.
To add fields to the output structure of the line item view:
1. Repeat the steps in “To add fields to the output structure of the result list:“
on page 449 for structure /OPT/VVA2_OUT_LINE_ITEM_ST.
2. By default, the new custom fields are not yet displayed in the line item view. To
get the custom fields displayed, launch VIM Analytics and change the layout
variant for the line item view. For details, see “Layout Variants” on page 444.
To add fields to the output structure of the process view:
1. Repeat the steps in “To add fields to the output structure of the result list:“
on page 449 for structure /OPT/VVA2_OUT_WORK_ITEM_ST.
2. By default the new custom fields are not yet displayed in the process view. To
get the custom fields displayed, launch VIM Analytics and change the layout
variant for the process view. For details, see “Layout Variants” on page 444.
14.4.3.2 Populating or Changing Field Content in Output Tables

VIM Analytics allows you to implement program logic to populate custom fields in
the following output tables: result list, line item view, and process view. You can not
only populate custom fields with values but you can also change the content of VIM
standard fields.
How to populate custom fields in the result list depends on whether you use ABAP
CDS views or not. In contrast to this, for the line item view and the process view,
there is no difference how to populate custom fields no matter if ABAP CDS views
are used or not.
The data selection classes /OPT/CL_V_VA2_DATA_PROV_BE_STD, /

OPT/CL_V_VA2_DATA_PROV_BE_CDS, and /OPT/CL_V_VA2_DATA_PROV_BE offer
enhancement points. These enhancement points allow to populate custom fields or
to change the content of VIM standard fields in the mentioned output tables.
Populating or changing field content in the result list with ABAP CDS views -
You may need to read additional fields from the database to populate the field
content in the result list. Depending on the database tables that are concerned, there
are two alternatives how to select these additional fields:
• The ABAP CDS views read data from several database tables already. You want
to read an additional field.
Example: The CDS views select data from database table /OPT/VIM_1HEAD already. You
want to select an additional field from database table /OPT/VIM_1HEAD.
See “To select additional fields by enhancing the ABAP CDS views:“
on page 451
VIM070500-03-CGD-EN-1
• You need to read data from database tables that are not included in the ABAP
CDS views.
Example: You want to get an additional descriptive text from a text table.
See “To select additional fields by selecting data from additional database tables:
“ on page 452
To select additional fields by enhancing the ABAP CDS views:
1. Enhance the appropriate ABAP CDS views by the additional output fields you
need to read.
The data records selected by the ABAP CDS views are read into a local table
lt_result of structure /OPT/VVA2_CDS_DOC_HDR_ST.
2. Create or update an append structure to structure /OPT/VVA2_CDS_DOC_HDR_ST

and add the additional output fields.
3. Pass the additional fields that are read from the ABAP CDS views to the local
table lt_result of structure /OPT/VVA2_CDS_DOC_HDR_ST. In Step 1, you have
added fields to the structure of local table lt_result. Now define the field
mapping between the ABAP CDS view fields and the fields of the result table:
Selection Mode Use ABAP CDS views

Database Field Name <Name of ABAP CDS view field>
Input/Output field of data selection Output Field
Application Field Name <Name of the field in the ABAP result table>
For more details, see “Defining Field Mapping (Only When Using ABAP CDS
Views)” on page 438.
4. In some cases, it may not be enough to just select one field from the ABAP CDS
views per output field but it may be required to select some more fields from
the ABAP CDS views. In this case, you may need to implement enhancement
point /OPT/EP_VIM_VA2_DATA_PROV_ADDF of enhancement spot /
OPT/ES_VIM_VA2_DATA_PROV_BE_C to add some more fields to be selected.
Repeat Step 1 to Step 3 for these additional fields.
Now you have done everything to get data read from the ABAP CDS views into
the local table lt_result. This local table is used to populate the custom output
fields in the result table rt_out_doc_hdr of structure /
OPT/VVA2_OUT_DOC_HDR_ST in a next step. By default all data records of local
table lt_result are moved to the final result table rt_out_doc_hdr by using
the move-corresponding statement. Sometimes this may not be sufficient and
you may need to implement some custom logic.
5. In this case, implement the explicit enhancement point /
OPT/EP_VIM_VA2_DATA_PROV_OUTH of enhancement spot /
OPT/ES_VIM_VA2_DATA_PROV_BE_C.
VIM070500-03-CGD-EN-1
To select additional fields by selecting data from additional database tables:
1. Implement the explicit enhancement point /OPT/EP_VIM_VA2_DATA_PROV_OUTH

of enhancement spot /OPT/ES_VIM_VA2_DATA_PROV_BE_C to populate custom
fields or to change the content of VIM standard fields in the result list.
2. Save and activate the enhancement implementation.
Example 14-3: Example implementation for result list:

TYPES: BEGIN OF custom_fields_ty,
docid TYPE /opt/docid,
zfield1 TYPE xxxx,
END OF custom_fields_ty.
DATA: lt_custom_fields TYPE TABLE OF custom_fields_ty.
FIELD-SYMBOLS: <lfs_doc_hdr_out> LIKE LINE OF lt_doc_hdr_out,

<lfs_custom_fields> LIKE LINE OF lt_custom_fields.
SELECT docid zfield1

INTO CORRESPONDING FIELDS OF TABLE lt_custom_fields
FROM xxxx
FOR ALL ENTRIES IN lt_doc_hdr_out
WHERE docid = lt_doc_hdr_out-docid.
SORT lt_custom_fields BY docid.
LOOP AT lt_doc_hdr_out ASSIGNING <lfs_doc_hdr_out>.

READ TABLE lt_custom_fields ASSIGNING <lfs_custom_fields>
WITH KEY docid = <lfs_doc_hdr_out>-docid
BINARY SEARCH.
IF sy-subrc = 0.
<lfs_doc_hdr_out>-zfield1 = <lfs_custom_fields>-zfield1.
ENDIF.
ENDLOOP.
To populate or change field content in the result list without ABAP CDS views:
1. Implement the explicit enhancement point /OPT/EP_VIM_VA2_DATA_PROV_OUTH

of enhancement spot /OPT/ES_VIM_VA2_DATA_PROV_BE_S to populate custom
fields or to change the content of VIM standard fields in the result list.
Example 14-4: Example implementation for result list:

zfield1 TYPE xxxx,
FIELD-SYMBOLS: <lfs_doc_hdr_out> LIKE LINE OF lt_doc_hdr_out,

SELECT docid zfield1

FROM xxxx
FOR ALL ENTRIES IN lt_doc_hdr_out
WHERE docid = lt_doc_hdr_out-docid.
SORT lt_custom_fields BY docid.
LOOP AT lt_doc_hdr_out ASSIGNING <lfs_doc_hdr_out>.

VIM070500-03-CGD-EN-1
WITH KEY docid = <lfs_doc_hdr_out>-docid

BINARY SEARCH.
IF sy-subrc = 0.
<lfs_doc_hdr_out>-zfield1 = <lfs_custom_fields>-zfield1.
ENDIF.
ENDLOOP.
To populate or change field content in the line item view:
1. Implement the explicit enhancement point /OPT/EP_VIM_VA2_DATA_PROV_OUTI

of enhancement spot /OPT/ES_VIM_VA2_DATA_PROV_BE to populate custom
fields or to change the content of VIM standard fields in the line item view.
Example 14-5: Example implementation for line item view:

itemid TYPE /opt/docitemid,
zfield1 TYPE xxxx,
FIELD-SYMBOLS: <lfs_line_item_out> LIKE LINE OF lt_line_item_out,

SELECT docid itemid zfield1

FROM xxxx
FOR ALL ENTRIES IN lt_line_item_out
WHERE docid = lt_line_item_out-docid
AND itemid = lt_line_item_out-itemid.
SORT lt_custom_fields BY docid itemid.
LOOP AT lt_line_item_out ASSIGNING <lfs_line_item_out>.

WITH KEY docid = <lfs_line_item_out>-docid
itemid = <lfs_line_item_out>-itemid
BINARY SEARCH.
IF sy-subrc = 0.
<lfs_line_item_out>-zfield1 = <lfs_custom_fields>-zfield1.
ENDIF.
ENDLOOP.
To populate or change field content in the process view:
1. Implement the explicit enhancement point /OPT/EP_VIM_VA2_DATA_PROV_OUTW

of enhancement spot /OPT/ES_VIM_VA2_DATA_PROV_BE to populate custom
fields or to change the content of VIM standard fields in the process view.
Example 14-6: Example implementation for process view

wi_id TYPE sww_chckwi,
zfield1 TYPE xxx,
VIM070500-03-CGD-EN-1
FIELD-SYMBOLS: <lfs_work_item_out> LIKE LINE OF lt_work_item_out,

SELECT wi_id zfield1

FROM xxxx
FOR ALL ENTRIES IN lt_work_item_out
WHERE wi_id = lt_work_item_out-wi_id.
SORT lt_custom_fields BY wi_id.
LOOP AT lt_work_item_out ASSIGNING <lfs_work_item_out>.

WITH KEY wi_id = <lfs_work_item_out>-wi_id
BINARY SEARCH.
IF sy-subrc = 0.
<lfs_work_item_out>-zfield1 = <lfs_custom_fields>-zfield1.
ENDIF.
ENDLOOP.
14.4.4 Enabling Hot Spot Functionality for Fields in Output

Tables
Several fields in the result list and in the process view of VIM Analytics provide hot
spot functionality to jump to detail information related to the field.
VIM Analytics allows you to add hot spots to additional fields in the following
output tables: result list, process view, line item view. This includes fields of the
VIM standard as well as custom fields. In a first step, you enable the hot spot for the
field. In a second step, you implement the function behind this hot spot.
14.4.4.1 Enabling Hot Spot Functionality

In this step, you activate the hot spot for fields in the result list, the line item view, or
the process view.
To enable a hot spot for a field in the result list:

1. Implement the explicit enhancement point /OPT/EP_VIM_VA2_SET_FIELDCAT of
enhancement spot /OPT/ES_VIM_VA2_UI_DOC_HDR_ALV to activate the hot spot
functionality for fields in the result list. Set field FIELDNAME of the field catalog
to X for the relevant fields.
Example 14-7: Example implementation for result list
VIM070500-03-CGD-EN-1
To enable a hot spot for a field in the line item view:

enhancement spot /OPT/ES_VIM_VA2_UI_PLUGIN_ITEM to activate the hot spot
functionality for fields in the line item view. Set field FIELDNAME of the field
catalog to X for the relevant fields.
Example 14-8: Example implementation for line item view
To enable a hot spot for a field in the process view:

enhancement spot /OPT/ES_VIM_VA2_UI_PLUGIN_WI to activate the hot spot
functionality for fields in the process view. Set field FIELDNAME of the field
catalog to X for the relevant fields.
14.4.4.2 Adding Custom Logic to a Hot Spot in the Output Tables

In this step, you add the program logic that is called when a user is clicking on a hot
spot in the result list, the line item view, and the process view.
Several fields in the result list and in the process view of the VIM Analytics provide
hot spot functionality to jump to detail information related to the field.
VIM Analytics allows you to change the logic behind hot spots for fields in the result
list, the line item view and the process view. You can not only change the program
logic but you can also add program logic to fields for which you have added a new
hot spot (see “Enabling Hot Spot Functionality for Fields in Output Tables”
on page 454).
To add custom logic to a hot spot for a field in the result list:
1. Implement the explicit enhancement point /OPT/EP_VIM_VA2_HDR_HOTSPOT of

enhancement spot /OPT/ES_VIM_VA2_UI_EVENTS_C to add or change the
program logic to a hot spot for a field in the result list.
VIM070500-03-CGD-EN-1
Example 14-9: Example implementation for result list
To add custom logic to a hot spot for a field in the line item view:
1. Implement the explicit enhancement point /OPT/EP_VIM_VA2_ITEM_HOTSPOT of

program logic to a hot spot for a field in the line item view.
VIM070500-03-CGD-EN-1
Example 14-10: Example implementation for line item view
To add custom logic to a hot spot for a field in the process view:
1. Implement the explicit enhancement point /OPT/EP_VIM_VA2_WI_HOTSPOT of

program logic to a hot spot for a field in the process view.
14.4.5 Specifying Discount Light Settings for VAN

You can define the behavior of the discount light icon that is integrated in the result
list of VAN. You can specify the following values, depending on company codes.
• Number of days before the due date for cash discount 1 to set a yellow discount
light.
• Number of days before the due date for cash discount 1 to set a red discount
light.
VIM070500-03-CGD-EN-1
The settings for the discount light apply for the discount light that is integrated in
the process output list of VIM Workplace. The settings also apply for the discount
light icon that is integrated in the result list of VAN.
For more details and all the steps needed to specify the discount light settings, see
“Specifying Discount Light Settings” on page 535.
14.5 VIM Analytics on Mass Data

You might have several hundred thousand or even millions of VIM invoices on your
system. At this time the latest, you should think about creating indexes on database
tables. Database table /OPT/VIM_1HEAD is the most important database table when
analyzing the runtime of VIM Analytics. However, VIM Analytics uses about 20
database tables for the data selection, not mentioning the additional database tables
needed for the report output.
The selection screen comes with more than 80 different selection fields. The selection
criteria that are used in companies most frequently vary very much. So there cannot
be a general recommendation which database indexes would be the best in your
company.
Analyze the most frequent and time critical queries, for example by using the ST05
transaction. Then create extension indexes on /OPT/VIM_1HEAD and further tables
depending on your company’s most common selection requirements.
In section 3.4 “VIM Analytics and Mass Data” in OpenText Vendor Invoice
Management for SAP Solutions - Reference Guide (VIM-RGD), you find further
recommendations for the end user how to ensure a fast data selection in VIM
Analytics.
Additionally, adjust the layout variants for the result list of VIM Analytics to restrict
the number of output columns to those columns that are needed for the daily
business. For more details, see “Layout Variants” on page 444.
Note: If your SAP system is on SAP NetWeaver AS ABAP 7.40 SP05 or higher,
you have the choice to use the new VIM Analytics report with ABAP CDS
Views or without. This configuration of the Selection Mode may have a high
impact on the run time of the new VIM Analytics report. It varies from system
to system which configuration is the best. But based on extensive mass data
tests, OpenText generally recommends the following configuration for
different database systems.
• On an SAP HANA database, select Use ABAP CDS Views.

• On an Oracle database system, select Use no views.
• On a Microsoft SQL Server database system, select Use ABAP CDS Views.
• On other database systems, start with Use no views and check whether the
runtime is sufficient. If it is not, you can switch to Use ABAP CDS Views and
the other way round seamlessly.
VIM070500-03-CGD-EN-1
14.5. VIM Analytics on Mass Data
For more details about the configuration of the Selection Mode, see “Data
Selection” on page 435.
However, these are general recommendations only. Your system might react
differently from OpenText's test systems. This is why OpenText strongly
recommends that you test the setting for the Selection Mode on your system
and set it accordingly. You can switch the setting whenever needed.
VIM070500-03-CGD-EN-1
Chapter 15
Characteristic Specific Configuration
15.1 Introduction
Within companies, the processing of invoices varies according to legal or specific
company-based settings. VIM supports flexible processing by defining individual
invoice characteristics.
An invoice characteristic is determined during runtime and depends on the

corresponding index data of the document. In the baseline configuration, VIM
delivers the country as a unique invoice characteristic.
With respect to invoice processing, there are various business and regulatory rules
that need to be applied. These rules differ from region to region. VIM provides a
flexible infrastructure for implementing these rules. This empowers customers to
fine tune these rules to be in line with their interpretation of legal rules and for
optimizing their business processes.
There are two main types of rules that need to be implemented:
Completeness check rules

These rules are based on the regulatory requirements that require specific pieces
of information to be on the invoice before the invoice can be paid.
Tax related
Specific pieces of information relating to Value Added Tax (VAT) and other
taxation rules that need to be followed. SAP ERP implements the various tax
rules in the standard software and has a flexible infrastructure to link with tax
software like Vortex and Taxware. VIM by itself does not duplicate any of these
pieces of functionality. VIM provides a way to implement certain metadata-
based business rules that can be implemented before the invoice data is entered
in to the SAP ERP transactions.
VIM implements these requirements with the following:
Core infrastructure
Infrastructure that supports the ability to model and realize different business
process flows depending on the characteristic specific rules.
Baseline content
Out-of-box content that includes common implementation of business rules
specific to the various regions. VIM provides a baseline that is based on country
as a characteristic. However, you can customize this if required.
VIM070500-03-CGD-EN-1
Chapter 15 Characteristic Specific Configuration
15.1.1 Core Infrastructure

The architecture of VIM includes various mechanisms to apply complex business
rules. The following concepts of VIM are critical for the implementation of
characteristic-specific business rules.
15.1.1.1 Document Types

Document types provide a mechanism for configuring the system for implementing
different user interfaces, rules checking and processes specific to different business
needs. You can assign different user interface screens to document types so that data
fields that are specific to the document type are visible to the users while processing
the invoices.
You can use a document type to combine all global settings to process an invoice
within a company. Therefore a document type is a global invoice processing
template. You can configure detailed settings according to specific invoice attributes
within invoice characteristic settings. You can also maintain settings in different
determination procedures, for example approval determination or additional cost
determination.
Obsolete The document types have an attribute to configure a “country code”. The “country
setting code” provides a mechanism for an implementer to configure country-specific
processes. This is obsolete with VIM 7.0 and higher because the country-specific
settings have been replaced by the characteristic-specific settings, which are
specified by the document type determination.
If you still use a fixed country in the document type, and the characteristic is also
configured, the country of the document type is used for the characteristic
processing. Therefore no other characteristic like the country is allowed.
15.1.1.2 Logic Modules

Logic modules provide a mechanism to automatically add data to a document. For
more information, see “Processing Logic Modules” on page 180.
15.1.1.3 Process Types

Process types are a mechanism for implementing exception processing procedures.
Various roles can be attached to these process types and process-specific user
options can be implemented to handle various exception scenarios. Process types
handle exceptions that occur because the characteristic-specific rules fail during
invoice processing.
VIM070500-03-CGD-EN-1
15.1. Introduction
15.1.1.4 Business Rule Framework

The Business Rule Framework (BRF) allows you to configure the business rule
processing in a more detailed way. The usage of the BRF is optional. If nothing is
configured in the BRF Schemata Assignment, the business rules are carried out as
usual. For more information, see “Business Rule Framework” on page 189.
15.1.1.5 Invoice Types

VIM supports PO invoices and Non PO invoices.
15.1.1.6 Simple Invoices

Some invoices are simplified invoices, based on certain characteristic-specific rules.
You can ignore some of the business rules for Simple Invoices. You configure the
business rules to be ignored for Simple Invoices at the characteristic level. See
“Characteristic Specific Process Types” on page 477.
15.1.1.7 Invoice Categories

Certain business rules are applicable to only some invoices that are processed in a
specified characteristic. Other business rules need to be skipped for only some
invoices of a characteristic. The concept of invoice categories is used to identify these
special groups of invoices. Invoice categories help to apply the business rules for
specific invoices.
VIM supports the following invoice categories:
Domestic
Invoices raised by vendors in the same country.
Intra-Community
Invoices raised by vendors in the European Union (EU) to companies in the EU.
Applicable only to EU countries.
Triangulation
Invoices raised by vendors in the EU to companies in the EU for a delivery of
goods or services originating in another EU country. In this case, both the
vendor and the company are in different EU countries. Applicable only to EU
countries.
Import
Invoice raised by vendors outside the company’s country.
Domestic Material
Invoices raised by vendors in India where the Purchase Order is a Material PO.
Applicable only to India.
Domestic Service
Invoices raised by vendors in India where the Purchase Order is a Service PO.
Applicable only to India.
VIM070500-03-CGD-EN-1
Import Material
Invoices raised by vendors outside India where the Purchase Order is a
Standard PO. Applicable only to India.
Import Service
Invoices raised by vendors outside India where the Purchase Order is a Service
PO. Applicable only to India.
Non VAT
Invoices without VAT amount. Applicable only to China.
VAT Common
Invoices with VAT provided but the VAT amount is not deductible. Applicable
only to China.
VAT Special
Invoices with VAT provided and the VAT amount is deductible. Applicable
only to China.
For information on maintaining invoice categories, see “Invoice Categories,

Category Groups, and Mapping” on page 468.
15.1.2 Baseline Content

Baseline content is the implementation of the business rules as interpreted by
OpenText. This implementation content is available for you to modify in order to
meet your requirements. This includes the following:
• Logic modules in general and specific to different invoice types
• Document types specific to different processes
• User interface specific to each process implementation
• Screen field configuration specific to the document types
• Business rules implementation specific to each characteristic
• Business rule framework schemata
In the baseline configuration, VIM delivers three document types as global

processing templates. Specific processing is configured for the PO and NPO invoice
types. In addition, a specific configuration for down payment processing is
provided.
These global templates cover the basic configuration, and in combination with the
country-specific invoice characteristic enable global companies to process invoices.
The following table lists the document types that are delivered as a part of VIM
baseline version.
S.No Document type Description

1 NPO_75 Non PO Processing
VIM070500-03-CGD-EN-1
15.1. Introduction
S.No Document type Description

2 PO_75 PO Processing
3 DWN_75 Down Payment Processing (PO and Non PO)
Each document type has a defined set of business rules. These business rules
determine the DP Exception to be raised in case of missing or invalid data on the DP
indexing screen.
Each business rule is driven either through configuration or a function module

which will in turn trigger the business logic for validating the invoice information.
The DP indexing screen is different for each document type. Based on the document
type, the respective Indexing screen is displayed. The screen configuration for each
document type is a part of the document type configuration.
Besides the global configuration of the document types, the detailed characteristic
configuration provides, in the baseline delivery, settings for all countries. Specific
countries and a global country template are delivered to support all requirements
from the process point of view.
15.1.2.1 Adjusting the Baseline

VIM 7.5 is delivered with preconfigured document types that support important
scenarios. Some data is automatically added by logic modules, depending on the
document type. The business rules that are carried out depend on the document
type as well.
You should copy the baseline document types to “own” document types.
The business rule run can be configured to run different for customer specific
groups. There is no preconfiguration. Some vendors could be grouped as white list
vendors. For this group, the business rules would not all be carried out.
To adjust the baseline:
1. Decide which data shall be added automatically:

Adjust the logic module settings for “own” document types in the Document
Type Configuration – Logic Module Processing. For more information, see
“Configuring Logic Module Processing” on page 181.
2. Decide which checks (business rules) shall be carried out in which sequence:
Adjust the document processes in the Document Type Definition. For more
information, see “Defining the Process Type Determination Sequence”
on page 143.
3. Decide which groups shall be used to have a strict or relaxed business rule run.
For more information, see “Business Rule Framework” on page 189.
VIM070500-03-CGD-EN-1
Figure 15-1: Overview incoming invoice data processing
15.1.3 Document Type Determination and Characteristic

Customizing
The baseline document types are determined in the document type determination
engine. For details, see “Document Type Determination Rules Engine” on page 505.
Besides the global document type, the invoice characteristic is determined and
defined in the determination engine. Within the baseline, VIM delivers the country
for characteristic. This section describes how to define an own invoice characteristic
and how to use the determination based on the invoice characteristic.
Note: You must only change the settings in this section, if you want to enhance
the baseline implementation by using an own characteristic.
To maintain characteristic settings and the document type determination:

Management > Document Processing Configuration >Document Type
Configuration > Maintain Document Type Determination Procedure.
VIM070500-03-CGD-EN-1
15.1. Introduction
You can change the sequence of the procedures, and you can introduce
additional procedures. Because the procedures are performed in alphabetical
order according to their procedure name, you must insert new procedures in
their correct position. The maintained procedures are checked from top to
bottom, and the first matching document type will be chosen.
2. To specify the matching criteria, mark a procedure and double-click Step

Details.
3. If you want to customize characteristics, select the Check Type Characteristic

Value and configure corresponding values for the characteristic in the Check
Value From field. Alternatively, you can specify different values like a function
module or a missing value, constant value, or invalid value.
Note: In contrast to the BL_0000200 and BL_0000300 procedures, the

BL_0000100 procedure, which stands for the PO Automation, does not use
the characteristic customizing. This document type should be only used
for specific values on invoices, for example for vendor or company code.
These settings must be maintained due to customer requirements.
Within the baseline, VIM delivers characteristic-specific countries and also

supports all other countries maintained with an asterisk (*) in characteristic-
specific settings. For more information, see “Characteristic Specific Settings for
Document Types” on page 472.
4. To use the characteristic settings, configure the corresponding characteristics in

Step Details. Within the global template approach, all countries are processed
in the PO_75 or NPO_75 global document type, depending on the invoice type.
In baseline, the asterisk (*) characteristic will be used for all additional
countries. The asterisk is also available in the characteristic settings, where you
can configure screen fields and characteristic-specific business rules.
5. Characteristic customizing
To maintain the characteristic settings, double-click Characteristics Field.
VIM070500-03-CGD-EN-1
Field Name
Specify the characteristic field. Each characteristic setting depends on that
field. In the baseline, LAND1 is delivered to replicate countries for all
characteristics. If this value changes, all characteristic settings have to be
checked and changed.
Search Help Name

Enter a search help to simplify the characteristics mapping.
Text table, Short tx fld n (Short text field name)

Enter the field name of the short text in the configured text table. The short
text is used in the characteristics customizing.
Exit FM
Enter a function module to determine the specified characteristic. In the
baseline, the country is read from the delivered company code.
15.2 Invoice Categories, Category Groups, and

Mapping
OpenText provides a baseline implementation for customizing aspects of invoice
categories, category groups, and mapping. Invoice categories are maintainable, so
you can enhance them if required.
Note: You must only change the settings in this section if you want to enhance
the baseline implementation.
You can use category groups to restrict the number of invoice categories per
characteristic. Category groups are a bundle of different categories.
When defining the business rules for a particular characteristic, you can configure
them by category group. You can define a business rule for all the categories in that
group in one line of configuration.
For a list of invoice categories that are supported for VIM, see “Invoice Categories”
on page 463.
VIM070500-03-CGD-EN-1
15.2. Invoice Categories, Category Groups, and Mapping
15.2.1 Maintaining Invoice Categories

In this step, you maintain custom invoice categories.
To maintain invoice categories:
1. Run the n/OPT/SPRO transaction and navigate to Vendor Invoice Management

> Document Processing Configuration > Category Specific Configuration >
Maintain Invoice Categories.
For the invoice categories provided by VIM Baseline, see the following
screenshot.
2. Maintain the invoice categories that you want to use.
15.2.2 Maintaining Invoice Category Groups

In this step, you maintain custom invoice category groups. These groups can contain
any number of invoice categories.
To maintain invoice category groups:

Maintain Invoice Category Group.
VIM070500-03-CGD-EN-1
2. Maintain the groups that you want to use.
15.2.3 Mapping of Invoice Categories to Groups

In this step, you map invoice categories to specific invoice category groups.
Prerequisites
• Invoice categories must be maintained. For more information, see “Maintaining

Invoice Categories” on page 469.
• Invoice category groups must be maintained. For more information, see
“Maintaining Invoice Category Groups” on page 469.
VIM070500-03-CGD-EN-1
15.2. Invoice Categories, Category Groups, and Mapping
To map invoice categories to groups:

Maintain Invoice Category Mapping.
2. Maintain the invoice categories for each invoice category group. One invoice
category can be assigned to multiple category groups.
15.2.4 Assigning Invoice Category Groups to Specific

Characteristics
In this step, you map invoice category groups to the characteristics that are
supported in your system.
Prerequisites
• Invoice category groups must be maintained. For more information, see
“Mapping of Invoice Categories to Groups” on page 470.
VIM070500-03-CGD-EN-1
To assign invoice category groups to characteristics:

Maintain Invoice Category Group Mapping.
2. Map your invoice category groups to the characteristics that are supported in
your system.
15.3 Characteristic Specific Settings for Document

Types
The Document Type Configuration utility lists all the document types for a
characteristic and provides you with the options to configure the characteristic-
specific attributes and document-specific settings. The configured characteristic
value with an asterisk (*) will be used as fallback characteristic.
To configure characteristic specific settings for document types:
1. To configure or to see what is configured for the baseline version for the
characteristic specific settings for document types, run the /N/OPT/SPRO
transaction to access OpenText Configuration and navigate to Vendor Invoice
Configuration > Characteristic Specific Document Type Configuration.
VIM070500-03-CGD-EN-1
15.3. Characteristic Specific Settings for Document Types
2. In the Characteristic Specific Attributes Overview screen, double-click a

characteristic to display the Characteristic Specific Attributes Details screen,
which allows you to modify the characteristic-specific attributes like posting
date or currency conversion date.
3. Maintain the characteristic-specific attributes, using the following parameters:
Posting date
This attribute determines the date to be used as the Posting date when
creating a SAP Invoice Document from a DP document. This configuration
will be applicable to all the invoices posted to SAP ERP for the
characteristic.
Select one of the following values:
• Date of the supply of the Goods or Services
• Scan Date
• Manual Entry
VIM070500-03-CGD-EN-1
Conversion Date
This attribute determines the date to be used while converting the invoice
amount from foreign currency to company code or local currency.
Select one of the following values:
• Posting Date
• Date of the supply of the Goods or Services
Amt Limit Simple Inv

Enter a number. If the invoice amount is less than this number, the invoice
will be considered as a Simple Invoice. Some process types can be skipped
for such invoices. For more information, see “Characteristic Specific Process
Types” on page 477.
Simplified Inv FM
You can write your own function module to determine if an invoice can be
classified as a Simple Invoice. Add the name of the function module in this
field. Copy the interface of the /OPT/VIM_CHECK_SIMPLE_INVOICE standard
function module to create a custom function module.
The following check boxes are indicators for credit memo check:
CM Ref No. Req.

Select this check box to determine that the credit memo must have a valid
reference invoice number.
CM Ref Date Req.

Select this check box to determine that the credit memo must have a valid
reference invoice date.
CM Data Validate
Select this check box to determine that the credit memo reference number
and the credit memo reference date must match the existing invoice in the
SAP ERP system.
Trg.sp.G/L ind.
This attribute sets the target special G/L indicator when creating an SAP
Down Payment Request from a DP document. This configuration is only
applicable to Down Payment Requests posted to SAP ERP for the
characteristic.
Det. Baseline Date

This attribute determines the date to be used as the default baseline date for
due date calculation. The attribute applies when creating an SAP Invoice
Document or an SAP Down Payment Request from a DP document. This
configuration is applicable to all documents posted to SAP ERP for the
characteristic.
VIM070500-03-CGD-EN-1
Select one of the following values from the list:
• Document Date
• Posting Date
• Supply Date
• Scan Date
• SAP Logic
• Manual Entry
The actual value for the baseline date is derived from the payment terms
according to SAP logic, unless you set the determination procedure to
manual.
If you do not explicitly maintain an option, or if you select the SAP Logic
option, no default value is set. Because there are payment terms in SAP that
do not set a default value by themselves, the setting T (as well as <space>) in
the customizing may result in an empty value for the actual baseline date.
This may be the wanted behavior.
Baseline Date FM
To apply custom logic for the baseline date determination, you can write
your own function module. If you enter a custom function module in this
field, the value for Det. Baseline Date is not considered anymore. However,
you can use the value in the custom function module.
Exit FM
Enter an exit function module to modify the indexing screen fields, for
example /OPT/VIM_SCREEN_EXIT_FM.
Cat. from external

This check box is only relevant for Russia and Brazil, where the invoice
category should not be changed when starting VIM.
Select this check box to indicate that the invoice category comes from a
channel and is not changed when starting VIM.
Note: The baseline date is used for the calculation of the due date in the
following way:
1. The default baseline date is determined using the values given here.
2. The actual baseline date is determined using SAP logic, that means derived
from payment terms.
(Exception: SAP logic is not applied when baseline date determination is
set to Manual Entry.)
3. The due date is determined using the payment terms and the actual
baseline date.
VIM070500-03-CGD-EN-1
15.3.1 Characteristic Specific Screen Fields

The DP Indexing screen can differ from one document to another. Therefore, you
can control the display of the fields on the indexing screen.
As a part of the baseline version, each document type has a different screen attached
with it. Screen configuration is a part of the document type configuration. Based on
the business requirements for each characteristic, respective header and item screens
are attached to the document type.
The baseline document types contain a standard subset of screen fields. These
settings are specified in more detail for each characteristic. For example, the ISR
field for Switzerland is only specified for baseline characteristic CH.
Globally, you configure fields for one document type. For more information, see
“Configuring the Index Header” on page 149. For country level, you configure the
fields on characteristic level, as described in detail in “To configure characteristic
specific screen fields:“ on page 476.
The indexing screen displayed is generated at runtime, based on the document type
and characteristic being processed.
To configure characteristic specific screen fields:
1. To configure or to see what is configured for the baseline version for the screen
fields, run the /N/OPT/SPRO transaction to access OpenText Configuration and
navigate to Vendor Invoice Management > Document Processing
Configuration > Document Type Configuration > Characteristic Specific
Document Type Configuration.
2. Mark a characteristic and double-click Index Header Configuration in the

Dialog Structure.
VIM070500-03-CGD-EN-1
The screenshot displays the various attributes that can be modified for a screen
field. The configuration also allows you to configure screens per role or per
invoice type.
Note: If no role is maintained, the entry is valid for all roles.
3. Input
Select this option to show the field as an input field.
Required
Select this option to make the field mandatory at runtime.
Display Only
Select this option to only display the field.
Hide
Select this option to hide the field on the screen.
4. To configure the attributes for the item screen, double-click Index Item
Configuration in the Dialog Structure.
The attributes are the same as for the index header.
15.3.2 Characteristic Specific Process Types

You must maintain the process type in the characteristic configuration, otherwise the
process type will not result in an exception during the DP processing.
To configure a process type to be used globally within document types to be

processed on characteristic base, follow the description in “Defining the Process
Type” on page 225 and, in the Process Type Definition Details screen, select the
Characteristic Check check box.
To configure characteristic specific process types:
1. On the Characteristic Specific Attributes Overview screen, select a

characteristic and double-click the Characteristic Specific Process Types link in
the Dialog Structure.
VIM070500-03-CGD-EN-1
2. Configure the process types for the characteristic, using the following
parameters:
Process Type
Process type number.
Description
Description of the process type.
InvoiceTyp
Select the invoice type that is applicable to the process type in this country.
The following values are available:
• All invoices
• PO based invoices
• Non PO based invoices
• Not applicable
Ignore Sim
Select this check box to specify that the process type will be ignored for
Simple Invoices.
Cat. Group
Select the invoice category group to which the process type is applicable.
For information about categories, see “Invoice Categories” on page 463.
VIM070500-03-CGD-EN-1
15.4. Z Constants
15.3.3 Characteristic Specific Screen Configuration

You can configure the indexing screen settings depending on the characteristic. All
characteristic specific index screen settings will overrule the index screen settings of
the document type. Make sure that the process type is configured characteristic
specific, as well. If no characteristic specific screen option exists, the screen options
of the document type apply, even if the process type is marked characteristic
specific.
You can configure a process type that is used globally in document types to be
processed on characteristic base. Therefore, follow the description in “Defining the
Process Type” on page 225. In the Process Type Definition Details screen, select the
Characteristic Check check box.
To configure a characteristic specific screen:
1. On the Characteristic Specific Attributes Overview screen, select a

characteristic and double-click the Characteristic Specific Screen
Configuration link in the Dialog Structure.
2. In the Characteristic Specific Screen Configuration Overview screen, maintain
the settings for the screen configuration. For a detailed description of the
configuration parameters, see “Configuring Index Screen Options” on page 146.
15.4 Z Constants
For some characteristic-specific configurations, you need to maintain Z constants. To
access Z constants, run the SM30 transaction with the /PTGWFI/Z_CONST table.
AFTCS_PROCESS_TYPES
Only relevant to invoices processed under Chinese DP document types.
Usage
This Z constant defines the process types that are relevant for the Anti Forge Tax
Control System (AFTCS) file upload/download program. The /
OPT/VR_AFTCS_FILE program only downloads the data of those invoices that
are in process types defined in this Z constant.
You can maintain multiple process types (as in baseline) with each process type
separated by a comma.
Product code
005
Baseline
141, 241
DETERMINE_INV_CAT
Usage
VIM baseline provides several invoice categories. You can also create your own
invoice categories. However, the system will not determine the custom invoice
VIM070500-03-CGD-EN-1
category. You must write your own function module to determine the custom
invoice category. You must define this custom function module in this Z
constant.
Product code
005
Baseline implementation
/OPT/VIM_TEMPLATE_DET_INV_CAT
Template function module

/OPT/VIM_TEMPLATE_DET_INV_CAT
15.5 Configuration for Canada

VIM provides a configuration specific for Canada. For Canada, all business rules as
in the standard rules for the US have been kept intact. One new business rule
Invalid Sales Tax for the Region has been introduced. In Canada, multiple tax
rates (GST, PST, HST, QST) are applicable, based on the province. Therefore, the tax
code derivation feature has been enhanced to derive tax codes that are based on
multiple tax rates.
Before tax code derivation, the system validates whether the supplied tax rate fields
are applicable for the region. Therefore, it uses the Invalid Sales Tax for the
Region business rule. However, to move past the Invalid Sales Tax for the
Region business rule check, the system must know the ship-to-region for the
incoming vendor invoice. The external system (for example OCR or IDOC) might
not supply a ship-to-region. The region can be derived automatically, based on
certain settings. For more information, see “Determining the Ship-to Region”
on page 481.
When the ship-to-region is known and the Invalid Sales Tax for The Region
business exception does not occur, the system proceeds further to determine the tax
code, based on the multiple tax rate fields supplied. For more information, see
“Determining the Tax Code” on page 484.
You can perform all Canada-specific customizing by running the /n/OPT/SPRO

transaction and navigating to Vendor Invoice Management > Document Processing
Configuration > Document Type Configuration > Specific Country Settings >
Canada.
VIM070500-03-CGD-EN-1
15.5. Configuration for Canada
15.5.1 Determining the Ship-to Region

To determine the ship-to region:

Configuration > Specific Country Settings > Canada > Maintain Ship-To-
Region Determination.
2. In the Cty field, enter CA for Canada.

In the CoCd From and CoCd To fields, define a range of company codes.
In the Vendor From and Vendor To fields, define a range of vendors.
3. In the Options column, select one of the following options:
Company Code
The system will determine the region from the address maintained in the
company code address for the range of vendors and company codes.
You do not have to maintain an entry in the Region and Custom FM fields.
Company Code -> Purchase Order

The system will determine the region from the company code address. If no
region is retrieved from the company code, this option automatically
switches to the purchase order to obtain the region. The purchase order can
be selected either from the header data or the item data. The system
determines the region from the plant address that is stored at item level.
You do not have to maintain any entry in the Region and Custom FM
fields.
Purchase Order -> Company Code

Same action as in Company Code -> Purchase Order. However, the system
will first try to obtain the region from the purchase order. If this fails, the
company code is used to obtain the region.
You do not have to maintain an entry in the Region and Custom FM fields.
Fixed Value
You must maintain the region explicitly in the Region field.
VIM070500-03-CGD-EN-1
Custom Function
You can define a custom logic to find the region by defining the Z function
module explicitly in the Custom FM field.
The following is an example interface of the custom function:
FUNCTION ZXXXXXXXXXXX
*"------------------------------------------------------------
*"*"Local Interface:
*" EXPORTING
*" REFERENCE(REGION) TYPE REGIO
*" TABLES
*" INDEX_ITEM STRUCTURE /OPT/VIM_1ITEM OPTIONAL
*" CHANGING
*"------------------------------------------------------------
ICC If ICC is used as OCR, ICC does not explicitly supply the ship-to region. In this case,
VIM uses the Company Code/PO (based on the selected configuration option) to
derive the ship-to region. There might be cases where you cannot use a Company
Code/PO to derive the ship-to region. In these cases, you must use custom functions
or manual entries, for example, if one of the following cases applies:
• The Company Code address cannot be treated as the ship-to address. In this case,
do not use the Company Code option to derive the ship-to region. Use the custom
function option.
• A PO or a combination of multiple POs has any line items with varying ship-to
regions for various PO line items (based on different receiving plants at PO line
item level). In this case, do not use the PO as an option to derive the ship-to
region. Use the custom function option.
• Without the ship-to region determined automatically or supplied, new business
rules for validation of tax rate fields/tax code determination fail on VIM side.
Manual user input is needed.
• ICC does not supply taxes at line item level. ICC should supply taxes only at
header level. The same tax rate at the header is applicable for each line item if no
lines are supplied with a tax rate. Different line items in the vendor invoice might
have different tax rates. For example, if a combination of free goods line (tax-free)
and lines with a tax rate exists in the vendor invoice, use the custom function
option.
VIM070500-03-CGD-EN-1
15.5.2 Maintaining Tax Fields for the Region

An incoming vendor invoice is validated against the tax province relationship table.
This section describes the maintenance of this table.
To maintain tax fields for the region:

Configuration > Specific Country Settings > Canada > Maintain Tax-Province
Relationship.
2. Specify the province-specific taxes for the regions.

Ideally, you can use the default values. If there is any change in the tax codes for
provinces, the default values may no longer make sense. In this case, you can
perform the necessary changes in the Country Specific Tax - Province
Relationship view.
The Invalid Sales Tax for the Region exception is triggered in the following
cases:
• The tax rate fields supplied in the incoming invoice do not match with the
allowed fields maintained.
• The ship-to region is empty. The ship-to region must be determined to
proceed.
VIM070500-03-CGD-EN-1
15.5.3 Determining the Tax Code

You control the tax code determination at the DP document type level (transaction /
n/OPT/VIM_1CX1). For more information, see “Maintaining Tax Code

• SAP Tax Determination Logic with OT Tax Table
• Tax Determination using Open Text Tax Table
• SAP Tax Determination Logic
• Customer Tax Determination
• Tax Code from Vendor Master
SAP Tax Determination Logic with OT Tax Table

The tax code is searched in the standard SAP transaction FTXP by comparing the
tax lines (GST, PST, and so on) for the particular province. If the tax code is still
not determined, the Canada-specific OpenText tax table Tax Code
Determination Configuration for Canada is used to determine the tax code.
To open the Tax Code Determination Configuration for Canada table, run the /
n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
Document Processing Configuration > Document Type Configuration >
Specific Country Settings > Canada > Maintain Tax Code Determination using
OT Table.
In this table, you can maintain tax rates for a region.
Note: Enter * in the Vendor From field if it is applicable for all vendors.
Avoid an overlap of key fields. All fields in the screenshot are key fields,
VIM070500-03-CGD-EN-1
except the Tax Code field. If key fields overlap, the system will pick the tax
code corresponding to the first match.
Tax Determination using Open Text Tax Table

Only the table Tax Code Determination Configuration for Canada is used to
determine the tax code. For more information, see SAP Tax Determination
Logic with OT Tax Table on page 484.
SAP Tax Determination Logic

The tax code is searched in the standard SAP transaction FTXP by comparing the
tax lines (GST, PST, and so on) for the particular province.
The system searches a tax code for multiple tax lines by comparing the
keywords for the tax lines (like GST, PST, and so on). These keywords are
maintained in the customizing transaction: Run the /n/OPT/SPRO transaction
and navigate to Vendor Invoice Management > Document Processing
Configuration > Document Type Configuration > Specific Country Settings >
Canada > Maintain Search Keyword for Tax Rate Fields/Text for Line Item Tax
Fields.
Note: The Find Text for Field at Header and Line Item Level table with its
entries is provided by default. Therefore, you do not have to maintain or
change anything, unless some exceptional cases occur.
Keywords - Assigning a keyword to a particular field specifies the kind of field.

For example, if GST is the keyword for the TAXRATE_1 field, this means that the
TAXRATE_1 field is the GST tax rate field for Canada.
Entries in the KeyWord column are language dependent.
The following fields at header level should be maintained for the tax line
keyword:
VIM070500-03-CGD-EN-1
• TAXRATE_1: Maintain GST, if this field is supposed to store the GST tax
rate.
• TAXRATE_2
• TAXRATE_3
• TAXRATE_4
The following fields at line level should be maintained for the tax line keyword:
• TAXRATE1_1
• TAXRATE2_2
• TAXRATE3_3
• TAXRATE4_4
Labels - Besides maintaining keywords, the Find Text for Field at Header and
Line Item Level table is used for maintaining labels for tax rate fields and tax
amount fields at line item level.
Note: For header level fields, you maintain texts in view /

OPT/VIM_IDX_TV. Use the SM30 transaction or run the /OPT/SPRO
transaction and navigate to Vendor Invoice Management > Document
Processing Configuration > General Configuration > Translations for
Index Screen Fields.
For the line item level, the following fields should be maintained for texts:
• TAXAMT_1
• TAXAMT_2
• TAXAMT_3
• TAXAMT_4
• TAXRATE1_1
• TAXRATE2_2
• TAXRATE3_3
• TAXRATE4_4
Customer Tax Determination

You can create a custom logic to find the missing tax code. Embed the logic in
the Z function module. The following shows an example interface of the custom
function:
*FUNCTION ZXXXXXXXXX
*" TABLES
*" INDEX_ITEM STRUCTURE /OPT/VIM_1ITEM
*" CHANGING
VIM070500-03-CGD-EN-1
Tax Code from Vendor Master

You can select this check box with any of the other options. If the logic fails to
determine the missing tax code from the selected option, the tax code is found
through the vendor master.
VIM070500-03-CGD-EN-1
Chapter 16
ICC Integration
The OCR solution OpenText Invoice Capture Center (ICC) can be integrated into
VIM. ICC automates the capture of paper invoices by using OCR to extract the
invoice data. ICC uses SAP ERP as backend to store and retrieve invoice image
information through the ICC Dispatcher.
about how to configure document registration for early archiving and document
handler, see section 4.4.2.1 “Customizing the early archiving registration type” in
Note: Business Center Inbound Configuration replaces the Incoming

Document Handling (IDH) framework and the ICC Dispatcher framework
with VIM 7.5 SP3. If you implement VIM new with VIM 7.5 SP3, you must use
Business Center Inbound Configuration. When upgrading to VIM 7.5 SP3, you
can use Business Center Inbound Configuration or ICC Dispatcher and IDH.
However, keep in mind that ICC Dispatcher and IDH will be discarded in the
future.
To activate the ICC processing for Business Center Inbound Configuration, you
must activate the BC_INBOUND Z constant.
Note: After you have switched your system to BC_INBOUND, ICC and
OpenText™ Business Center Capture for SAP® Solutions (BCC) cannot access
the ICC application store in your VIM system anymore. This means, that you
must perform a new export of all your ICC/BCC applications. For more
information, see 2.1.1.2 “Application Menu” in ICC/BCC Customizing Guide.
If you use Business Center Inbound Configuration, only the following customizing
steps are relevant for VIM.
• “Defining Frequently Used Default Values” on page 497

• “Maintaining Channel IDs” on page 499
• “Validating DP Documents with Mapping Error” on page 500
• “Maintaining the Mark for Training Function” on page 504
• “Maintaining the Workflow Template for DP” on page 504
• “Document Type Determination Rules Engine” on page 505
• “Download of Recipient Data for ICC Usage” on page 508
VIM070500-03-CGD-EN-1
Chapter 16 ICC Integration
16.1 ICC Dispatcher

The ICC Dispatcher is part of VIM. Using services of the ICC Dispatcher, you can
control all tasks related to the following actions:
• storing documents
• retrieving documents
• extracting documents
• validating documents
You also can distribute these tasks accordingly between different involved
components. To understand the services of the ICC Dispatcher, see Figure 16-1
on page 490 and the description of steps 7, 8, 12, 13.
Figure 16-1: Architecture diagram of the ICC integration into VIM
Note: You can use any scan client and content repository that are certified by
SAP; for example OpenText Imaging Enterprise Scan and OpenText Archive
Server.
Steps from the paper invoice to the VIM workflow:
1. SAP ERP calls the scan client through the Early Archiving scenario, using the
OAWD transaction.
VIM070500-03-CGD-EN-1
16.1. ICC Dispatcher
2. The scan client deposits the image of the paper invoice to the content repository.
The OAWD transaction creates a DP document in SAP ERP using function
module /OPT/VIM_IF_NEW_DOC_INSERT.
This function module inserts an entry to tables /OPT/VIM_1HEAD and /
OPT/VIM_HD_DP with the new DP document number, archive date and time,
document ID, archive document type, and content repository ID.
3. The ICC Extraction engine calls the API (B) via a scheduled batch job /
OPT/VIM_IF_GET_NEW_DOC_LIST on ICC side and gets new documents for
processing:
• Gets all the documents in Scanned status along with Secure URL for image
and XML document which will be created by the ICC Extraction engine.
The documents are presented in a queue sorted by archive date and time.
The sort order can be modified by user exits.
• Updates the DP document status to Sent to OCR.
4. The ICC Extraction engine picks the documents from Step 3 and imports the
corresponding images from the content repository.
5. The Export module of the ICC Extraction engine calls the API (D) /
OPT/VIM_IF_OCR_DATA_UPDATE_N with call point EX:
• Updates the status and OCR data appropriately. This API exports the data to
SAP ERP after completion of the extraction phase. Table /OPT/VIM_1EXT_H
will be updated with extracted data.
• Updates the DP Document status with Extraction Completed.
6. The ICC Extraction engine sends the detailed results XML file of the exported
data to the content repository using the URL retrieved from SAP ERP in Step 3.
The XML file is used by the ICC Validation engine.
Results for each data exported to SAP ERP are stored in an XML file and
archived back to the content repository.
7. A periodic job (program /OPT/VIM_STATUS_EXTR) runs on SAP ERP side, picks

up the DP items with status Sent to OCR and checks the time elapsed. If it
exceeds the configured time, the status is set back to Scanned.
The maximum allowed time for extraction can be maintained in table /
OPT/VIM_RETRY using the SM30 transaction. Table /OPT/VIM_RETRY contains an
entry with call point EX for extraction.
8. A periodic job (program /OPT/VIM_DP_TRIGGER) runs on SAP ERP side, picks

up the DP items with status Extraction Completed. The job runs business
rules to check if validation is required or not. If validation is required, the status
is set to Ready for Validation. If validation is not required, the DP workflow
is started.
If validation is required, the system evaluates the agents for the VALIDATOR role
and updates the SAP tables.
VIM070500-03-CGD-EN-1
9. The ICC Validation engine calls the API (G) /OPT/VIM_IF _GET_VAL_DOC_LIST
and gets a list of documents for validation:
• Gets all the documents in status Ready for Validation.

The documents are presented in a queue sorted by archive date and time.
The sort order can be modified by user exits.
• For each DP document, it gets the secure URL for image and XML
documents which will be used by the ICC Validation Client.
• The function module SCMS_DOC_URL_READ will return the URL by taking
Archiving ID and Archiving Doc ID as input.
10. The ICC Validation engine picks documents (both image and XML) from the
content repository for each validation document, using the URL retrieved from
SAP ERP at Step 9.
11. The ICC Validation engine calls the API (I) /OPT/VIM_IF_OCR_DATA_UPDATE_N
with call point VA:
• Updates the status and OCR data appropriately. This API exports the data to
SAP ERP after completion of the validation phase. Table /OPT/VIM_1EXT_H
is updated with validation data.
• Updates the DP Document status with Validation Completed.
12. A periodic job (program /OPT/VIM_STATUS_VALD) runs on SAP ERP side, picks
up DP items with status Sent for validation, and after elapsed time sets the
status to Ready for Validation.
The maximum allowed time for Validation can be maintained in table /
OPT/VIM_RETRY using the SM30 transaction. Table /OPT/VIM_RETRY contains an
entry with call point VA for validation.
13. A periodic job (program /OPT/VIM_DP_TRIGGER) runs on SAP ERP side, picks
up DP items with status Validation Completed, and starts the DP workflow.
16.2 Maximum Allowed Time for Extraction and

Validation
If a particular DP document is in Extraction or Validation longer than the allowed
time, the ICC Dispatcher changes the DP document status back to Scanned or Ready
for Validation.
You can maintain the maximum allowed time limits for Extraction and Validation,
using table /OPT/VIM_RETRY.
To maintain the maximum allowed time for Extraction and Validation:
1. Run the SM30 transaction, enter the table name /OPT/VIM_RETRY and click the
Maintain button.
VIM070500-03-CGD-EN-1
16.2. Maximum Allowed Time for Extraction and Validation
Alternatively, run the /N/OPT/SPRO transaction and navigate to the menu path
General Configuration > Incoming Document Processing > ICC
Configuration > Maintain Retry Count, Time Limit and Forwarding Option.
Call Point EX represents Extraction.
Call Point VA represents Validation.
2. Maintain the Time limit (in seconds) and the maximum allowed number of
retries until the document status is set to Maximum number of retries reached.
OpenText recommends the following parameter values:
Extraction
Number of Retry
3
Time limit
7200
Validation
Number of Retry
3
Time limit
3600
The extraction time limit of 2 hours is based on the fact, that the URLs to access
the archive are only valid for 2 hours, if a signed archive is used. If you have an
archive that is not signed, you can even use a longer value. The validation time
limit of 1 hour has no special reason. It is just to give the user enough time to
complete the validation.
The number of retries should not be too low, because sporadic errors may occur,
but it should not be too high, so that it does not take too much time, until a real
problem with a document is detected.
Note: If the retry limit is reached, and you want to reset the document to
be processed again, you must reset the retry counters manually.
3. Select the Forwards check box if you want the documents to be moved to the
workflow automatically after the retry limit has been reached.
Note: If you select the check box for automatic move to the workflow, it
will work on all documents in the Retry limit reached status. So make
sure that you have no old and forgotten documents in this status, which
you do not want to be moved. If you have such documents, remove them
using Discard Image.
VIM070500-03-CGD-EN-1
16.3 Validation Framework

The Validation framework determines whether a DP document (created by ICC)
needs validation or not and also assigns the validation agents to validate the DP
document.
The framework bases on the customizing values defined for the archive document
type associated with the DP document created by ICC. The framework determines
whether validation is required for the incoming invoice or not. If required, the
framework determines whether the validation must always be executed or only
when one of the customized fields is missing in the invoice. The framework also
determines who is supposed to validate the incoming invoice.
You must perform the following actions:

• “Creating and Linking the Validation Determination ID” on page 494
• “Defining Frequently Used Default Values” on page 497
• “Maintaining Channel IDs” on page 499
• “Validating DP Documents with Mapping Error” on page 500
• “Assigning Validation Agents” on page 502
• “Maintaining the Mark for Training Function” on page 504
16.3.1 Creating and Linking the Validation Determination ID

To determine whether a DP document needs validation or not, you must create a
Validation Determination ID and link it to the Archive Document Type.
To create a Validation Determination ID:
1. Run the /n/OPT/VIM_ICC_VAL transaction.

Configuration > Validation Determination Procedure (OCR) > Set Up
Validation Determination Condition.
2. To add a Validation Determination ID, click New Entries.
VIM070500-03-CGD-EN-1
16.3. Validation Framework
3. Define the Validation Determination ID, using the following parameters:
Validate Grp
Validation Group, short form of Validation Determination ID
Check Type
Enter the validation check type. Select one of the following values:
• Index Data Fields

• Function Module.
If you select Function Module, you must maintain the field Validate
Chk Func.
Validate Chk Func

Maintain this field if you selected Check Type Function Module. The
Validate Check function module will determine whether validation is
required or not. You can use the function module template /
OPT/VIM_RUN_VALIDATION_RULES.
Click one of the following radio buttons:
Validate For Selected Fields

If you select this option, you must maintain the Validation Determination
Fields that are required, see Step 4 on page 495.
The system will check whether all the listed fields are maintained for the DP
document. If one of the fields is not maintained, it will send those DP
documents for validation to the Validation Client.
Validate Never
Select this option to determine that the DP document will not be sent for
validation and continues with the workflow.
Validate Always
Select this option to determine that all DP documents that are assigned to
this Validation group will be sent to the Validation client for validation.
4. To maintain the Validation Determination Fields, double-click the Validation
Determination Fields link in the navigation panel.
VIM070500-03-CGD-EN-1
To link the Validation Determination ID to the Archive Document type:

Enter the table name /OPT/VIM_VAL_DET.
Click the Maintain button.
Configuration > Validation Determination Procedure (OCR) > Link Archive
Document Type to Validation Group.
2. Link the Document type to the Validation Determination ID, represented by the
Validate Grp.
VIM070500-03-CGD-EN-1
16.3.2 Defining Frequently Used Default Values

OpenText Configuration provides an option to define default values that are used
frequently in the ICC integration. For example, DP_DOC_TYPE determines the default
DP document type value.
If you use Business Center Inbound Configuration to handle incoming document

processing, most of the constants that are listed in this section are no longer relevant.
Exception: all constants that deal with downloading and also jobs for downloading.
Thus, the following constants are still relevant:
• CUSTOM_ICC_PO_DOWNLD
• DP_DOC_TYPE
• PO_REC
• VEND_REC
To define default values:
Configuration > Incoming Document Processing > ICC Configuration >
Advanced Configuration.
Product Code 005 determines Document Processing.
Value is the default value or expected value in the process.
2. Define the default values, according to the following table:
Constant Meaning
CUSTOM_ICC_PO_DOWNLD Customer function module to perform the PO
download.
The signature is the same as standard function
module /OPT/DOWNLOAD_PURCHASE_DATA
Using this user exit, a customer specific function can
be performed to load the items from the staging tables
to the ICC.
CUSTOM_ICC_EX_SORT Customer function module to sort the ICC extraction
CUSTOM_ICC_VA_SORT queue
(deprecated, use the new Customer function module to sort the ICC validation
functions below) queue
Using this user exit, a customer specific sort can be
performed before the documents are selected for
extraction or validation. The function should return a
table and not only one entry, because the first entry
might be locked by a parallel function.
VIM070500-03-CGD-EN-1
Constant Meaning
CUSTOM_ICC_EX_SORT_N Customer function module to sort the ICC extraction
CUSTOM_ICC_VA_SORT_N queue
Customer function module to sort the ICC validation
queue
Using this user exit, a customer specific sort can be
performed before the documents are selected for
extraction or validation.
See function templates /
OPT/VIM_IF_GET_NEW_TEMPLATE for the extraction
queue and /OPT/VIM_IF_GET_VAL_TEMPLATE for
the validation queue.
DP_DOC_TYPE Default DP document type
DP_EX_VA_CANCEL OCR Extraction/Validation is Cancel
DP_EX_VA_ERROR OCR Extraction/Validation is Error
DP_EX_VA_REJECT OCR Extraction/Validation is Reject
DP_EX_VA_SUCCESS OCR Extraction/Validation is Success
DP_SYNC_PROC Process Code to control parallel DP Trigger Process
DP_SYNC_REFRESH_TAB Refresh DP Sync Table
ICC_AR_DELAY Delay before sending document to extraction, format
HHMMSS, 000500 = 5 min
Use this constant if there are frequent situations, when
a document is selected for extraction, but is not yet
accessible from the archive.
ICC_VA_COUNT_LIMIT If set, display limit value instead of real length of
queue for validation. Can be used for better
performance in case of large validation queues.
URL_READ_FM Function module to read the Image/Document URL
PO_REC Maximum batch size for Purchase Order download
data
VEND_REC Maximum batch size for Vendor download data
XML_AR_DELETE_EARLY If set to X, XML documents in the archive will be
deleted as soon as possible.
Use this constant if the archive resources have to be
kept as low as possible. There is another way to get
rid of unused XML files using the ICC dispatcher
cleanup report.
If you are using the Single Click Entry feature, which
is available since VIM 7.5, you must set this Z constant
to an empty value.
VIM070500-03-CGD-EN-1
Constant Meaning
XML_AR_ASSIGN_LATE If set to X, the archive document ID for XML will be
assigned via RFC from ICC.
Set the parameter value to X, if ICC 6.0 SP3 or higher
is used. Leave the parameter empty, if a lower ICC
version is used.
XML_AR_CONTREP Content Repository for XML Document
16.3.3 Maintaining Channel IDs

A channel uniquely identifies the source of an incoming invoice to the VIM system
across the landscape. In this step, you maintain the default ICC channel ID.
To maintain the channel ID:
Maintain Channel ID constants.
2. For Constant ICC_CHANNEL_ID, enter Constant Value ICC.
VIM070500-03-CGD-EN-1
16.3.4 Validating DP Documents with Mapping Error

If any mapping errors occur while mapping extracted data, you may need to
validate such DP documents. You use the /n/OPT/VIM_CHNL transaction to maintain
whether mapping errors should be ignored or not. See also “Maintaining Channels”
on page 98.
In VIM, each communication type has a channel; there is one record for each channel
in the /n/OPT/VIM_CHNL transaction.
To maintain validation of DP documents with mapping error:
1. Run the /n/OPT/VIM_CHNL transaction.
Channel ICC represents the ICC integration. To view details, double-click the
line.
VIM070500-03-CGD-EN-1
Channel ICC is configured to ignore mapping errors.
2. To maintain whether the DP document with mapping errors will be validated

or not, run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Maintain Constants for Validate on Mapping errors.
3. To get DP documents with mapping errors validated, set ConstantValue for

VALIDATE_ON_MAP_ERR to YES.
VIM070500-03-CGD-EN-1
16.3.5 Assigning Validation Agents

If the active template for the VALIDATOR role is set to ARDOCTYPE, you can assign
Validation agents using the Simple Mode Role Maintenance. See also “Maintaining
Role Determination Settings” on page 51.
To assign Validation agents:
1. Run the /n/OPT/CP_9CX4 transaction.
2. In the navigation panel, click VALIDATOR.
VIM070500-03-CGD-EN-1
The VALIDATOR node represents the assigned Validation agents for Product code
005. You can assign Validation agents to Archive Document types and to the
following Agent Types:
A
Work center
AC
Role
C
Job
O
Organizational unit
S
Position
US
User
To maintain the default validator role using OpenText Configuration:
Maintain Validator Role.
2. For Constant VALIDATOR_ROLE, enter Constant Value VALIDATOR.
VIM070500-03-CGD-EN-1
16.3.6 Maintaining the Mark for Training Function

Starting with VIM 7.5 SP2, the ICC function Mark for Training is available as a
Training button in the VIM indexing screen, Process tab. For more information
about the function, see section “Marking Documents for Training” in Invoice Capture
Center Users Guide.
Prerequisite The DOC_ARC_DOC_ID field (XML data from ICC) must be filled for the work item.
For more information, see “Defining Frequently Used Default Values” on page 497
(constant XML_AR_DELETE_EARLY).
To maintain the Training button:
1. Open the index header configuration (see “Configuring the Index Header”
on page 149)
2. Set the MARK_TRAINING field to Display Only, Input, or Required.
The Training button is visible but inactive if one of the following conditions applies:
• The Training Status on the Process tab is C (Completed), W (In Progress), or X
(Obsolete).
• The indexing screen is in display mode.
16.4 Maintaining the Workflow Template for DP

When an invoice comes in from ICC, it is validated if required. Afterwards, the
workflow for DP is started.
16.4.1 Maintaining the Default Workflow Template

OpenText Configuration provides an option to maintain the default workflow
template for Document Processing. The workflow maintained here is triggered if
validation is required.
To maintain the default workflow template:
Maintain Workflow Template Constants.
2. For Constant MAIN_WF_TEMPLATE, enter Constant Value WS00275269.

VIM070500-03-CGD-EN-1
16.5. Document Type Determination Rules Engine
16.4.2 Maintaining the Preprocess Exit

OpenText Configuration provides an option to maintain the default preprocess exit
function module if needed. When an invoice comes from ICC, it will be stored and a
predefined workflow will be started. If the preprocess exit function module is
maintained, it will be called to process data coming from ICC before doing any
further actions in the workflow.
To maintain the preprocess exit:
Maintain Preprocess Exit constants.
2. In Constant Value, enter the preprocess exit function module.
16.5 Document Type Determination Rules Engine

VIM provides a document type determination rules engine to determine the DP
document type from OCR results.
The engine works if the DP document type assigned to the archive document type is
one of the following:
• the default document type; that means the value configured in Z-constant 005
DP_DOC_TYPE
• NPO_75 if the Z-constant 005 DP_DOC_TYPE is empty or not configured
If a different DP document type is assigned to the archive document type, the engine
is skipped. In this case, the assigned DP document type is used for the DP workflow.
VIM070500-03-CGD-EN-1
If you set the Z-constant 005 DP_DOC_TYPE_REDETRMN to X, you make it impossible to

skip the engine.
If you have a 1:1 relation between the DP document type and an ArchiveLink
document type, select the ArchiveLink document type defined in the SAP
ArchiveLink process, see “Creating an ICC Archive Document Type” on page 29. If
you do not have a fixed relation, you can leave the field empty or you can use a
dummy archive document type which is used for all DP document types without
fixed relationship. The current baseline is delivered with dummy document type /
OPT/ICC.
Up to VIM 6.0 SP3, the archive document type in table /OPT/VIM_1HEAD was derived
from the DP document type by the configuration setup using the /OPT/VIM_1CX1
transaction. This determination was changed in VIM 6.0 SP3 to the determination
that is described in this section.
However you can switch to the old determination behavior (as it was before VIM 6.0
SP3), using transaction /OPT/VIM_1CX12: For constant 005 / AR_OBJECT_FROM_DP,
enter Constant Value X.
16.5.1 Methods
The rules engine consists of a sequence of procedures. Each procedure is responsible
for one DP document type. If one procedure says NEXT, the next procedure is
performed. If a procedure says TRUE, the document type of this procedure is applied
to the document. The last procedure should be responsible for the DP document
type NPO_75. This last procedure should always return TRUE.
16.5.2 Configuration
You configure the rules engine in the OpenText Configuration (/OPT/SPRO):
Vendor Invoice Management > Document Processing Configuration > Document
Type Configuration > Maintain Document Type Determination Procedure
For more information, see “Document Type Determination and Characteristic

Customizing” on page 466.
16.5.3 Baseline Procedures

The baseline configuration uses the existence of an invoice order number in the OCR
results for an invoice to tell if the invoice is a Non PO or a PO invoice. The company
code of the OCR results decides on the invoice characteristics.
To configure baseline procedures for the rules engine:
• Configure the baseline procedures, as shown in the screenshot.
VIM070500-03-CGD-EN-1
16.5. Document Type Determination Rules Engine
You can use the Exclusive check box to deactivate a procedure. If the check box
is not selected, the procedure will never return TRUE but always return NEXT.
You can change the sequence of the procedures, and you can introduce
additional procedures. As the procedures are executed in alphabetical order
according to their procedure name, you must insert new procedures in their
correct position. The maintained procedures will be checked top down and the
first matching document type will be chosen.
16.5.4 Steps
The procedures consist of steps, which can be modified. You can use the following
check types:
A
Missing value of an OCR field
B
Constant value of an OCR field
C
Custom function
D
Invalid value of an OCR field (value cannot be found in a check table)
E
Characteristic value of the characteristic customizing criteria
F
PO related invoice type check
You can configure the processing relation between the different steps with the
indicators AND or OR.
VIM070500-03-CGD-EN-1
16.6 Periodic Jobs for ICC Dispatcher

As mentioned in “Steps from the paper invoice to the VIM workflow:“ on page 490,
periodic jobs are necessary to set up the ICC infrastructure completely. For details,
see section 6 “Scheduling Batch Jobs for Data Download from SAP ERP for ICC
Integration” in OpenText Vendor Invoice Management for SAP Solutions - Administration
Guide (VIM-AGD) and section 7 “Scheduling Batch Jobs for the ICC Dispatcher” in
OpenText Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-
AGD).
Note: In a multiple backend environment, the download jobs (section 6

“Scheduling Batch Jobs for Data Download from SAP ERP for ICC Integration”
in OpenText Vendor Invoice Management for SAP Solutions - Administration Guide
(VIM-AGD)) are needed in both the central system and the satellite systems
whereas the jobs for the ICC dispatcher (section 7 “Scheduling Batch Jobs for
the ICC Dispatcher” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD)) are needed only in the central system.
16.7 Download of Recipient Data for ICC Usage

This section describes a one-time download of data to the ICC. The other downloads
of SAP data to the ICC are periodic downloads and are described in OpenText Vendor
Invoice Management for SAP Solutions - Administration Guide (VIM-AGD) (see also
“Periodic Jobs for ICC Dispatcher” on page 508).
16.7.1 Transaction and Report

To generate a text file that can be imported in ICC as recipients database, you can
use the /OPT/VIM_COMP_DN transaction or the /OPT/VIM_COMPCODE_DOWNLOAD
report. The program has to be used in dialog mode.
Note: The report is available with UI languages English, German, French, and
Spanish.
The report generates database lines for every company code in the selection,
respecting all house banks and bank accounts. The address information related to
the company code is the same in all lines.
Note: In most cases, you must edit the text file or the database itself because
the address information generated by the download program will not be
sufficient for a good identification of company codes.
VIM070500-03-CGD-EN-1
16.7. Download of Recipient Data for ICC Usage
16.7.2 User Interface

The /OPT/VIM_COMPCODE_DOWNLOAD program provides the following selection
screen.
Character The processing option With character check checks the address for TAB characters
check inside the strings. These characters would disturb the output format and must be
eliminated.
Processing option With character check will not work in an EBCDIC environment, so
it can be switched off.
Logical system You can set the value for the logical system to be used in the data to a defined value.
So, it is possible to generate databases which are not designated for the logical
system where the download data is taken from.
Output to If you use the option Additional output to screen, the data will be displayed on the
screen screen in an ALV grid. Note that the field sequence is rearranged for optimized
readability. The field sequence does not correspond to the field sequence in the
download file.
VIM070500-03-CGD-EN-1
16.8 Customizing Options for the Reject from

Validation Function
Notes
• If you use Business Center Inbound Configuration to handle incoming
document processing, you cannot use this functionality. If you need it, you
must work with the ICC Dispatcher.
• In Business Center Inbound Configuration, you encounter the following
situation: Documents run into an error during extraction or validation. They
get stuck in the inbound handler. You only have the option to send these
documents to the target process automatically.
In the ICC validation client, users can reject documents from validation, for example
if bad image quality makes them impossible to read. Users can select the following
actions:
• Mark for deletion
• Mark for rescan
• Reject
For more information, see section 2.12 “Rejecting a Document” in OpenText Invoice
Capture Center for SAP Solutions User’s Guide.
In versions prior to VIM 7.5 SP3, the DP workflow in VIM did not respond to these
actions. The document remained in the ICC dispatcher. With VIM 7.5 SP3 and
higher, the DP workflow provides processing these actions. This section describes
the corresponding customizing options.
The documents must be processed in the new process type 243 Check Data After
Reject From Validation. You must add this process type to all document types.
16.8.1 Maintaining the Forwarding Option

For manual and automatic processing of rejected documents, you must maintain the
forwarding option.
To maintain the forwarding option:
1. Run the SM30 transaction, enter the table name /OPT/VIM_RETRY, and click
Maintain.
Alternatively, run the /OPT/SPRO transaction and navigate to the menu path
Configuration > Maintain Retry Count, Time Limit and Forwarding Option.
2. Create an entry or use the existing entry with Call Point RJ Reject from
Validation.
VIM070500-03-CGD-EN-1
16.8. Customizing Options for the Reject from Validation Function
3. If you want to move the documents to the workflow automatically when they
were rejected in validation, select the Forwards check box.
Note: For the entry with Call Point RJ Reject from Validation, the
values in the fields Number of Retry and Time limit have no meaning.
16.8.2 Maintaining the Treatment of Existing Documents

If you activate the forwarding option for Reject from Validation, the option
works on all documents in status 90 Rejected in Validation. This means it also
works on existing documents.
To avoid that existing documents are moved, you can perform one of the following
actions.
• Changing the document status to Discarded
• Setting a start date for the move
To change the document status to Discarded:
1. To open the IDH Admin Tool, run the /OPT/VIM_7AX8 transaction.
2. To change the status of the documents to Discarded, click Discard Image.

For more information, see section 17 “Working with the IDH Admin Tool” in
OpenText Vendor Invoice Management for SAP Solutions - Administration Guide
(VIM-AGD).
To set a start date for the move:
1. Run the /OPT/SPRO transaction and navigate to the menu path Vendor Invoice
> Incoming Document Processing > ICC Configuration > Advanced
Configuration.
Alternatively, run the /OPT/VIM_ICC_ADV_CFG transaction.
2. To set a start date for the move, maintain the Z constant ICC_VA_RJ_FWD.
Documents older than this start date are not moved.
VIM070500-03-CGD-EN-1
16.8.3 Maintaining Automated Processing

Automated processing only works if the forwarding option is activated. For more
information, see “Maintaining the Forwarding Option” on page 510.
Automated processing is possible for documents, that users have rejected with Mark
for deletion or Mark for rescan.
To maintain automated processing:
1. Run the SM30 transaction, enter the table name /OPT/VIM_REJECTV, and click
Maintain.
Alternatively, run the /OPT/SPRO transaction and navigate to the menu path
Configuration > Maintain Background Options for Validation Reject.
2. In the Processing Reject from ICC Validation screen, select the Background
Processing (BP) check box if you want to automatically obsolete the documents
or to automatically move them into the Sent to Rescan exception.
Note: In the User field, you can enter a user ID. This user ID is related to
the user who performed the reject action in the ICC validation client. If
you leave the field empty, the setting works for reject actions from all
users. If you specify a user, the setting works only for the specified user.
3. Enter a Obsolete/Rescan Reason.

For Reject Process 007 Obsolete, the table for Obsolete Reasons is applicable.
For more information, see “Maintaining Obsolete Reasons” on page 242.
For Reject Process 008 Rescan, the table for Rescan Reasons is applicable. For
more information, see “Maintaining Rescan Reasons” on page 242.
There is no search help available. Due to the ambiguity of the tables, you must
find out the appropriate Obsolete/Rescan Reason in an extra session.
VIM070500-03-CGD-EN-1
Chapter 17
Configuring the VIM Workplace
VIM Workplace is intended as a tool for VIM super users, for example the AP
processor. However, also occasional users can work with it. VIM Workplace allows
you to display lists of your work items based on criteria that you have specified. You
also can display work items of other users and of your team as a whole.
17.1 Migration Report for the VIM Workplace

When upgrading from VIM 6.0 to VIM 7.5, old workflow instances are not shown in
the VIM Workplace.
The registration tables need to be filled for existing items so the tabs Inbox, Pending
and Closed are filled correctly. Therefore, a migration report is available with VIM
7.5 SP2.
17.1.1 Scope of the Report

Since VIM 7.0, the VIM Workplace is delivered. It is based on data maintained in the
following tables:
/OPT/CT_PMC_RG00
Contains information about work items in the inbox
/OPT/CT_PMC_RG01
Contains information about work items in the inbox
/OPT/CT_PMC_RG02
Contains information about work items in My Pending
/OPT/CT_PMC_RG03
Contains information about work items in finished items
These tables are filled consistently during the runtime of the work item.
The report has two main scopes:
Initialization mode
When upgrading from a lower VIM version (6.0), the mentioned tables need to
be filled initially for old instances. The VIM Workplace will not show any work
items if these tables are not filled. You must run the migration report
accordingly.
Update mode
As the administrator, run this report mode for chosen document IDs to correct
data in the mentioned tables.
VIM070500-03-CGD-EN-1
Chapter 17 Configuring the VIM Workplace
17.1.2 Running the Report

To call the report, run the SE38 transaction for program /OPT/CR_PMC_REG_UPDATE.
Prerequisite The report is based on data contained in /OPT/VIM_1PROC. This table is initially
filled by the VIM Analytics migration report, which is documented in “Report for
One-time Data Upload and for Consistency Check of Documents” on page 428.
17.1.2.1 Selection Screen

The report offers the following parameters:
Document selection
Document-ID
Mandatory field: enter the Document IDs.
Select Charge
The processing in the report is done by charges. You can maintain the number of
processed documents before committing (COMMIT). In normal cases, leave this
number on the standard setting. For optimization, you can set this parameter
differently.
Update properties
Test Run
Select this check box to achieve that the report will not update any values in the
database tables. You can use this mode for runtime measurement before
planning the actual productive run.
Extended Display Options
Note: These options are only available in Test Run mode.
VIM070500-03-CGD-EN-1
17.1. Migration Report for the VIM Workplace
Display calculation results

Select this check box to achieve that the report shows a list comparing the
current database values with the ones calculated by the report (see “Output”
on page 515). You can use this mode especially to analyze issues with content
of the tables for single documents.
Only show inconsistent data

Only relevant in combination with option Display calculation results. Select
this check box to achieve that the protocol will only show lines with differing
content between database and calculation. If the check box is cleared, the
protocol will show all database content compared to the calculated values.
17.1.2.2 Output
The report output differs if Display calculation results is selected or not.
Display The report shows a protocol about successful or unsuccessful execution. You can
calculation access the protocol in the Job Spool when running in the background.
results not
selected
Display
The report calculates all values within the selection range and displays them in
calculation intervals according to the Select Charge setting. On the main screen, you can
results selected analyze the tables for these intervals by pressing the respective buttons. Click Go to
next interval to start the calculation of the next interval.
VIM070500-03-CGD-EN-1
Table view The table view shows a list of all values already present in the database and
compares them to the calculated value. The first line is representing the current
value in the database, the second line the calculated value.
VIM070500-03-CGD-EN-1
17.2. Configuring the System Landscape Directory (SLD) for the VIM Workplace
17.2 Configuring the System Landscape Directory

(SLD) for the VIM Workplace
The VIM Workplace provides work items in multiple backend systems and in single
system landscapes. Therefore, you must configure the System Landscape Directory
(SLD). See “Configuring the System Landscape Directory (SLD)” on page 667.
Note: As long as you do not configure the SLD, an error message is displayed
when starting or refreshing the VIM Workplace.
17.3 Customizing Profiles for the VIM Workplace

You configure VIM Workplace for all general settings within a profile. A profile
describes all relevant default user screen settings and enables you to integrate your
own processing logic. You can assign different profiles directly to different users if
Note: Within baseline delivery, a general profile (DEFAULT) is delivered, which

is called whenever no specific user profile has been configured. This profile
must always be available on all involved systems where the VIM Workplace
runs or from where the VIM Workplace reads data and performs actions.
You can assign a specific user profile using the /OPT/CPMC_CUST_PROF user
parameter.
The following customizing steps are necessary to maintain customizing profiles:

• “Defining a Profile” on page 517
• “Maintaining General Profile Settings” on page 518
• “Maintaining Output List Field Settings” on page 523
• “Assigning Action Buttons” on page 525
17.3.1 Defining a Profile

This section describes an overall profile with a unique ID and the corresponding
description.
To define a profile:

Management > Cross Component Configuration > VIM Workplace > Maintain
2. Define the profile using the following parameters:
Customizing Profile
Define the profile with a unique ID.
VIM070500-03-CGD-EN-1

Enter a description for the profile.
17.3.2 Maintaining General Profile Settings

In this step you configure general profile settings used by the VIM Workplace
during runtime. The general profile settings comprise pure UI-related settings as
well as some important functional application parameters.
All UI-related settings are taken into account if you run the VIM Workplace for the
first time or if you decide to reset the UI layout to the general default settings. The
general default profile (DEFAULT) included within the baseline delivery assumes a
minimum screen resolution of 1600 x 900 for all UI-related settings.
To maintain general profile settings:

2. In the VIM Workplace: Customizing Profiles: Details screen, double-click

General Profile Settings.
3. Configure the general profile settings using the parameters described in the
following sections:
VIM070500-03-CGD-EN-1
17.3. Customizing Profiles for the VIM Workplace
Customizing Profile
Predefined customizing profile for which the settings are valid.
17.3.2.1 Basic Application

Work View
Select the work view that is initially loaded when starting the VIM Workplace. If
you do not provide a value, the system automatically starts the personal work
view.
Discount Function
Enter the exit function module to determine the discount light indicator
behavior within the process output list of the VIM Workplace.
Default value: /OPT/C_PMC_DATA_SET_DISC_LIGHT
Exit template function: /OPT/C_PMC_EXIT_TEMPL_DISCOUNT
17.3.2.2 Enhanced Application

Transfer Customizing Profile
Select this check box to specify that the currently used customizing profile
(determined for the system where the VIM Workplace has been started) will also
be transferred to any remote systems.
Clear the check box to specify that a corresponding customizing profile has been
specified for each remote system separately.
Logo Name
Enter the object name of any corporate branding logo image. If you leave the
field empty, no logo image is displayed in the VIM Workplace.
Default value: /OPT/VIM_LLECMLOGOFS
Note: VIM provides the global possibility to control whether logo images
should be displayed using the DASHBOARD_NO_LOGO constant, product code
005 of the WebFlow Constant Table /PTGWFI/Z_CONST. If you want to use
this possibility, do not change the Logo Name parameter.
Application Class
Enter the application ABAP class, which contains the VIM Workplace
application logic.
Default value: /OPT/CL_C_PMC_APPLICATION
UI Class
Enter the UI controller ABAP class, which contains the VIM Workplace UI
specific logic.
Default value: /OPT/CL_C_PMC_UI_CONTROLLER
Data Class
Enter the data provider ABAP class, which contains the VIM Workplace data
load logic.
VIM070500-03-CGD-EN-1
Default value: /OPT/CL_C_PMC_DATA_PROVIDER
User Class
Enter the VIM Workplace user ABAP class, which contains logic to read and
save user-specific profile settings.
Default value: /OPT/CL_C_PMC_USER
Action Class
Enter the action handler ABAP class, which contains the logic to perform actions
within the VIM Workplace.
Default value: /OPT/CL_C_PMC_ACT_HANDLER
17.3.2.3 Content Pane

Content Pane Position
Select the initial position of the content pane.
Content Pane Alignment

Select the alignment of the process output list and the detail pane within the
content pane. You can also remove the detail pane completely. If you do not
select a value, the system initially uses a vertical content pane alignment.
Content Pane Horizontal Size In %

If the content pane is initially expanded and the position has been set to Bottom
or Top, enter a percent value between 5 and 90 for the initial horizontal size of
the content pane.
If you do not enter a value, the system automatically uses a standard value of
60%.
Content Pane Vertical Size In %

If the content pane is initially expanded and the position has been set to Left or
Right, enter a percent value between 5 and 90 for the initial vertical size of the
content pane.
If you do not enter a value, the system automatically uses a value of 58%.
ALV Area
Select which UI container area of the content pane is used to initially embed the
ALV process output list.
ALV Ratio
Enter the process list size rate in percent within the content pane.
If you do not enter a value, the system automatically uses a standard value of
65%.
Plug-In Type
Enter a predefined plug-in type in order to get all mapped plug-in definitions,
which are available as buttons in the detail pane toolbar.
Plug-In ID
Enter the plug-in that is initially loaded in the detail pane.
VIM070500-03-CGD-EN-1
17.3.2.4 Selection Pane

Selection Pane State
Specify if you want to expand or collapse the selection pane by default.
Selection Tab
Specify the initially activated tab in the selection pane. If you do not select a
value, the system automatically activates the Inbox selection tab.
Selection Pane Mode
This setting has been introduced with the smart selection feature.
Specify the initially activate selection pane mode. If you do not select a value,
the system automatically activates the classic selection mode.
Note: The selection pane mode is stored in the user specific table /
OPT/CT_PMC_USER every time a user leaves the VIM Workplace. This
ensures that the selection pane always remembers the last used setting.
Moreover, it avoids unnecessary additional clicks every time the VIM
Workplace is opened. The user specific setting always has priority over the
setting that is maintained in the assigned customizing profile. If you want
to restore the user specific setting to the setting of the customizing profile,
you must delete the corresponding user data in table /OPT/CT_PMC_USER.
However, this will also reset all other UI specific settings to the profile
defaults.
Tabscreen Horizontal
Enter the selection pane subscreen that is called when changing the active
selection tab (content pane position Bottom or Top).
Default value: 1001
Note: The horizontal default selection pane subscreen 1001 is separated

into three different subscreen areas to allow easier positioning of the single
selection screen elements. If you do not want to use the predefined
selection screen areas because you have custom enhancements, you can use
the selection pane subscreen 1003 instead.
Tabscreen Vertical
Enter the selection pane subscreen that is called when changing the active
selection tab (content pane position Left or Right).
Default value: 1002
Selection Screen Program
Enter the main program of a function group which contains selection
subscreens.
Default value: /OPT/SAPLVIM_PMC_UI_COMP
Field selection subscreens for horizontal selection tabs
If you assign the selection pane subscreen 1001 as the horizontal selection tab
subscreen, you can maintain each single field selection subscreen area (left,
middle, right) of the corresponding selection tabs separately.
VIM070500-03-CGD-EN-1
As soon as you assign the empty dummy selection pane subscreen 1003 as the
horizontal selection tab subscreen, you only need to maintain the Left field
selection subscreen area values because the screen does not offer any subscreen
area separation.
Field selection subscreens for vertical selection tabs

The Tab<x> Vertical fields allow replacing the vertical field selection subscreens
for each selection tab.
Reset Selection Criteria Function Module

Enter a function module to reset the selection criteria on the currently active
selection pane tab.
Default value: /OPT/C_PMC_SEL_OPTIONS_RESET
Synchronize Selection Criteria Function Module

Enter a function module to synchronize the selection criteria between the
horizontal and vertical selection pane subscreens.
Default value: /OPT/C_PMC_SEL_OPTIONS_SYNC
Lock Selection Screen Function Module

Enter a function module to lock the selection screen input for an active selection
screen tab.
Default value: /OPT/C_PMC_SEL_PANE_LOCK_GET
17.3.2.5 Data Selection

RFC Selection Function
Enter a function module used to retrieve the process output data from all
involved systems, depending on the chosen work view and the selection criteria
entered for the currently active selection tab.
Default value: /OPT/C_PMC_DATA_GET_PROC_RFC
Note: The default function module offers multiple enhancement points or

sections to fulfill custom data selection requirements. Therefore, replacing
the standard function should only be necessary in very special cases.
Always read the instructions mentioned in the coding of the function
module very carefully before implementing enhancement points or
sections or creating a custom function module.
Maximum Hits
Enter the number of hits returned by the process output list for the current work
view and active selection tab. If you do not specify a value, the system
automatically uses a predefined maximum of 500 hits.
Include Substitution
Select this check box to achieve that the output process list also shows work
items for active or adopted substitutions in the personal inbox view, and that the
field Substitution for: contains the original work item receiver.
VIM070500-03-CGD-EN-1
17.3.3 Maintaining Output List Field Settings

In this step, you maintain the basic visual appearance and functionality of the VIM
Workplace output list.
Note: The output sequence of the list fields delivered by the DEFAULT baseline
customizing profile is used as a standard configuration. Each individual user
can change the configuration using the ALV layout variant functionality.
To maintain the output list field settings:


Output Field List Settings.
3. Configure the output list field settings using the following parameters:
Profile
Predefined customizing profile for which the output list field settings are
valid.
Sel. Tab
Selection tab for which the corresponding output list field settings are valid.
Possible values: Inbox, Pending, Completed.
Component name
Field name of the output list field: Select any field that is available in the
output list field reference structure /OPT/CPMC_OUTPUT_PROCESS_ST, using
the input search help.
VIM070500-03-CGD-EN-1
You can select several standard fields and additionally custom fields and
manual classification:
Custom fields
• CUSTOM_FIELD4
• CUSTOM_FIELD5
• CUSTOM_FIELD6
• CUSTOM_FIELD7
• CUSTOM_FIELD8
• CUSTOM_FIELD9
• CUSTOM_FIELD0
MAN_CLASSIFICATION
Manual classification.
Only for custom development: You can use this field to add customer
specific classifications. You can implement a custom logic to fill this
field during runtime.
Out. Key
Output key: Select this check box to mark the output list field as ALV
output key column. All fields marked as output key fields are fixed when
using the horizontal scroll bar in the process output list.
Out. Seq.
Output sequence: Define the sequence of the field within the output list.
Out. Stat.
Output status: To define the status of the output field, select Display or
Hide.
Output Exit Function Module

This function module dynamically decides during runtime whether an
output field is displayed or not. Exit template function: /
OPT/C_PMC_EXIT_TEMPL_FLD_STAT.
Col. width
Output width: Enter the fixed column width for an output field. If you do
not enter a value, the system activates the automatic ALV grid control
column optimization for the output field.
Out. Style
Output style: Define the output style of an output field, for example, if it is
displayed as an Icon or as a Hyperlink.
Out. Icon
Output icon: Enter the icon symbol that is displayed if you selected the
Icon or Executable Icon field output style.
VIM070500-03-CGD-EN-1
Icon Info
Icon quick info: Select this check box to display an icon quick info for the
output icon.
Icon Exit Function Module

Enter an exit function module to dynamically set the output icon symbol
and the corresponding icon quick info during runtime. Exit template
function: /OPT/C_PMC_EXIT_TEMPL_ICON.
Before Action Execute Function

Enter an exit function module that allows performing the following special
functionality:
• To check special preconditions before executing the action itself.

• To cancel an action on different call levels. The following different call
levels are available:
• All selected processes or lines at the calling system level.

• Corresponding bucket of processes or lines relevant at the executing
backend system level.
Exit template function: /OPT/C_PMC_EXIT_TEMPL_PRE_ACT
Action Function
Enter an exit function module that runs the logic of the selected action in the
corresponding backend system. Exit template function: /
OPT/C_PMC_EXIT_TEMPL_ACT_EXE
Auth. Grp.
Action authority group: Assign a predefined action authority group to an
output list field action. The action authority group is used to check whether
the corresponding user is allowed to perform the action or not.
17.3.4 Assigning Action Buttons

The VIM Workplace allows you to add any action buttons to the process output list
toolbar at any time.
To assign action buttons:

Action Button Assignment.
VIM070500-03-CGD-EN-1
3. Assign action buttons using the following parameters:
Profile
Predefined customizing profile for which the button assignment settings are
valid.
Button ID
Predefined button ID to perform a button action.
But. Seq.
Button Sequence: Define the sequence in which the assigned action buttons
are generated within the VIM Workplace process output list toolbar.
Auth. Grp.
Action authority group: Assign a predefined action authority group to an
action button. The action authority group is used to check whether the
corresponding user is allowed to perform the action or not.
17.4 Defining Action Buttons for the VIM Workplace

The VIM Workplace allows you to add action buttons to the process output list at
any time. Before the action buttons can be assigned to a VIM Workplace customizing
profile, you must technically define each button.
To define action buttons:

Management > Cross Component Configuration > VIM Workplace > Define
Action Buttons.
VIM070500-03-CGD-EN-1
17.4. Defining Action Buttons for the VIM Workplace
2. Define the action buttons using the following parameters:
Button ID
Unique numeric button ID that defines an action button.
Button Text
Enter the button text, which is displayed as text label for the generated
button during runtime.
Quickinfo
Enter quickinfo text, which is displayed for the button during runtime.
Butt. Type
Enter the button type used to generate the button during runtime. Select
one of the following button types:
Bulk action
All buttons defined as bulk actions are generated within a special
toolbar button menu called Choose Bulk Action.
Single action
All buttons defined as single actions are generated as separate buttons
in the VIM Workplace process output list button toolbar.
Separator
This setting allows you to insert standard SAP separator lines to group
the generated buttons from a visual point of view.
Notes
• Buttons that are defined as single actions can only be performed for
exactly one marked line in the VIM Workplace process output list. A
bulk action can be performed for one or multiple lines marked by
the Bulk Action check box.
• The Forward bulk action has been introduced for administrators.
Regular end users should use the Refer action instead. The function
is set to inactive by default. You must activate it if required.
OpenText recommends that you protect this function against special
VIM070500-03-CGD-EN-1
authority checks because the function should only be available to

administrators.
Icon name
Assign an icon to the generated button or use the button exit to assign the
icon dynamically.
Button Exit
Enter an exit function module that dynamically skips the creation of a
button during runtime. Exit function template: /
OPT/C_PMC_EXIT_TEMPL_BUTTON
Before Action Execute Function

Enter an exit function module that performs the following special
functionality:
• To check preconditions before performing the action itself.

• To cancel an action on different call levels. The following different call
levels are available:
• All selected processes or lines at the calling system level.

• Corresponding bucket of processes or lines relevant at the backend
system level.
Exit template function: /OPT/C_PMC_EXIT_TEMPL_PRE_ACT.
Action Function
Enter an exit function module that runs the logic of the selected action in the
corresponding backend system. Exit template function: /
OPT/C_PMC_EXIT_TEMPL_ACT_EXE.
Active
Select this check box to set the button definition to active.
17.5 Defining Action Authority Groups for the VIM

Workplace
The VIM Workplace allows the following types of actions, which can be protected
using special authority checks:
Button actions
These actions are defined as single or bulk action buttons within the process
output list button toolbar.
Output Field actions

These actions are defined as executable icons or hotspots within the process
output list itself.
All action-related authority checks are performed based on action authority groups.
An action authority group allows grouping of multiple similar actions for the
VIM070500-03-CGD-EN-1
17.6. Configuring Scanning in VIM Workplace
authority check instead of performing the authority check based on each defined
action separately. This concept simplifies the maintenance of the corresponding
authorizations. If you want to perform an authority check directly for each action,
you must set up a 1:1 relationship between action authority groups and defined
actions.
If you do not want to perform an authority check for a selected action, do not assign
an authority group to the action in the action button assignment or the output field
action setting.
If you have set the global VIM authorization check to inactive using the
AUTH_CHECK_ACTIVE constant for product code 009 of the web flow constant table /
PTGWFI/Z_CONST, the authority check field is not considered. Therefore, all entered
values do not have any effect.
To define action authority groups:

Action Authority Groups.
2. Define action authority groups using the following parameters:
Auth. Grp.
Action Authority Group: Unique technical name that defines an action
authority group.
Action Authority Group Description

Enter a description for the defined action authority group.
Note: If the VIM Workplace involves an active multiple backend system

landscape, the action authority groups must be unique throughout the
whole system landscape. An action authority group is always determined
by the action performed on the system where the VIM Workplace is
currently running. The action authority group is handed over to the
corresponding backend system to perform the authority check.
17.6 Configuring Scanning in VIM Workplace

With VIM 7.5 SP3 (VIM 7.0 SP7), a Scan button is added to VIM Workplace. It allows
you to scan new invoices directly from the VIM Workplace interface.
Prerequisites To use the scanning function, the following prerequisites must be fulfilled.
• VIM-related document types are configured according to OAWD customizing. For

more information, see “Creating the Presetting Folder for VIM” on page 26.
• The available document types are filtered by the VIM object in SOA0.
• Using an authorization check of the S_WFAR_OBJ authorization object, you can
further restrict available document types.
VIM070500-03-CGD-EN-1
When VIM Workplace is started, an authorization check is performed in the General

Functionality transaction area with the J_6NIM_WP0 authorization object. For
more information, see “VIM Workplace” on page 90. If authorization fails, the Scan
button is not displayed.
To scan an invoice:
1. In VIM Workplace, in the application toolbar, click Scan.
2. In the Scan Invoices dialog box, double-click the document type in the tree.
The standard OAWD dialog box Storing for subsequent entry opens.
3. Scan as in SAP standard.
The scan function offers the following enhancement spots.
To configure a replacement with custom implementations:
1. Create a subclass of /OPT/CL_C_SCAN_VIM with custom coding.
2. Use the enhancement spot /OPT/ES_CL_C_SCAN_FACTORY to instantiate the

custom class instead of the default class.
Class: /OPT/CL_C_SCAN_FACTORY
Method: GET_SCAN_INSTANCE
To configure enhancement options within standard:
1. Navigate to package /OPT/VIM and class /OPT/CL_C_SCAN.

Method SELECT_DOCUMENT_TYPE in class /OPT/CL_C_SCAN offers an
enhancement point that is defined in enhancement spot /OPT/ES_CL_C_SCAN.
2. Perform changes, as needed:
• Columns
• Nodes
• Functions
• Tree settings
• Expand and Collapse behavior of the tree
VIM070500-03-CGD-EN-1
17.7. Defining Smart Selections
17.7 Defining Smart Selections

The VIM Workplace selection pane offers a special smart selection mode. Before you
can use the smart selection, you must technically define smart selection criteria. If
suitable, you must define selection restrictions, depending on the smart selection
criteria. Finally, you must assign the defined selection criteria to the relevant
selection pane constellations of the VIM Workplace.
Note: If you use the VIM Workplace smart selection in a multiple backend
environment, make sure to keep the smart selection definition identical on all
involved systems.
17.7.1 Defining Smart Selection Criteria

Smart selection criteria represent a set of attributes or enhanced business logic
aspects. Together, they form a meaningful selection context. Therefore, they allow a
very quick and easy access to corresponding selection results. Smart selection
criteria help you to avoid constructing complex selections using and combining
different classical select options and parameters.
To define smart selection criteria:

Smart Selections.
2. Define smart selection criteria using the following parameters:
Selection Criteria
Enter a unique alphanumeric ID or any other 10 character string that
technically defines a set of selection criteria.
Description
Enter a meaningful text that describes the selection criteria. The text is
available in the VIM Workplace selection criteria list of the smart selection
pane.
Criteria Type
This setting controls the way how the corresponding selection criteria logic
is executed in order to determine the check result.
Select one of the following criteria types:
Static check
Selection criteria checks are based on index data and executed every
time the index data is changed during runtime.
Time based check

Selection criteria checks are based on dynamic time bound dimensions
and therefore can only be executed by the additional criteria check
program /OPT/CR_PMC_BS_CHECK.
VIM070500-03-CGD-EN-1
Note: For more information regarding the functionality and run

frequency of program /OPT/CR_PMC_BS_CHECK, see section 5.6
“Scheduling Batch Jobs for VIM Workplace” in OpenText Vendor
Invoice Management for SAP Solutions - Administration Guide (VIM-
AGD).
Criteria Class
Enter the ABAP class that contains the check logic for the defined selection
criteria. To redefine the available check methods, every entered class must
be inherited from the abstract class definition /OPT/CL_C_PMC_BS.
Note: For more information how to implement additional custom

selection criteria and restriction checks based on the abstract class /
OPT/CL_C_PMC_BS, see section 8.3.2.1 “Creating a Custom Smart
Selection Class Implementation” in OpenText Vendor Invoice
Management for SAP Solutions - Scenario Guide (VIM-CCS).
Active
Select this check box to activate the defined selection criteria and its
dependent restrictions.
If the Active check box is not selected, the selection criteria is not considered
during the selection criteria check and also not available in the VIM
Workplace smart selection pane.
17.7.2 Defining Smart Selection Restrictions

Each smart selection restriction belongs to one higher level selection criteria. You can
use restrictions to further differentiate several smaller brackets. You can also simply
distinguish multiple logically dependent subcategories. If a selection criteria stands
for itself and if a further meaningful separation does not make sense, you do not
have to define any selection restrictions. In other words, the definition of selection
restrictions is an optional activity. You can use it as needed.
To define smart selection restrictions:

Smart Selections.
In the Selection Criteria Definition Overview screen, select an entry, and
double-click Selection Restriction Definition in the Dialog Structure.
2. Define smart selection restrictions using the following parameters:
Restriction
Enter a unique alphanumeric ID or any other 10 character string that
technically defines a selection restriction.
VIM070500-03-CGD-EN-1
17.7. Defining Smart Selections
Description
Enter a meaningful text that describes a selection restriction. The text is
available in the VIM Workplace selection restriction list of the smart
selection pane.
Constant Value
Enter any additional information that can be helpful during the selection
criteria and restriction check. You can freely choose the additional
information, independent from any data format.
17.7.3 Configuring the Selection Pane Assignment

You must assign all defined selection criteria to relevant selection pane
constellations. The assignment is based on work views and selection tabs. Each
selection criteria and its dependent restrictions are only available in the smart
selection pane if the corresponding assignment is configured accordingly.
To configure selection pane assignment:

Smart Selections.
In the Selection Criteria Definition Overview screen, select an entry, and
double-click Selection Pane Assignment in the Dialog Structure.
2. Configure selection pane assignments using the following parameters:
Work View
Select the work view for which a selection criteria should be available.
Possible values: Personal, Team, Other user, All.
Selection Tab
Select the selection pane for which a selection criteria should be available.
Possible values: Inbox, Pending, Completed.
Preview Active
Select this check box to achieve that a special selected hits preview of the
potential selection result is displayed for each selection criteria and
restriction. If no dependent restrictions are defined for a selection criteria,
the preview counter is shown on criteria level only. If there are dependent
restrictions, the selected hits preview is shown on restriction level.
Note: The determination of the selected hits preview counter values

consumes a lot of performance. Use it carefully. Therefore, no selected
hits preview is activated in the baseline delivery for the VIM
Workplace All work view mode.
VIM070500-03-CGD-EN-1
17.8 Maintaining General Teams for the VIM

Workplace
In the VIM Workplace, special team-related functionalities are available based on the
following different types of possible team definitions:
Personal Team
Maintained by each user directly in the VIM Workplace team configuration
dialog.
General Team
Generally maintained by an administrator. Users cannot change the general
team in the VIM Workplace team configuration dialog box.
• General team definition.

• Assignment of members to general teams.
Note: The maintenance of general teams depends on the corresponding SAP

ERP system and therefore no transport of the setting is available.
The general team definition describes the team with a unique ID and the
corresponding description.
To define a general team:
1. Run the /OPT/VIM_WP_TMG transaction.
2. In the General Team Definition Overview screen, define general teams using
the following parameters:.
Team ID
Unique ID for the general team definition.
Description
Enter a description for the defined general team.
To assign members to general teams:
1. Run the /OPT/VIM_WP_TMG transaction.
2. In the General Team Definition Overview screen, select a line and double-click
Team Member Assignment.
3. Assign members to a defined general team using the following parameters:
Team ID
Unique ID for the general team definition.
VIM070500-03-CGD-EN-1
17.9. Specifying Discount Light Settings
OT
Organizational Object Type: This field contains a one or two character code
that represents different types of objects, for example US for user or S for
position.
Agent ID
Corresponding organizational object ID, depending on the selected
organizational object type.
Active
Select this check box to set the member assignment to active.
17.9 Specifying Discount Light Settings

In this step, you define the behavior of the discount indicator light that is integrated
in the process output list of the VIM Workplace and in the result list of VIM
Analytics.
You can specify the following values, depending on company codes:

• Number of days before the due date for cash discount 1 to set a yellow discount
indicator light.
• Number of days before the due date for cash discount 1 to set a red discount
indicator light.
Note: If you do not want to set up the discount indicator light settings for each
company code separately, enter an asterisk (*) in the company code field.
If the number of days before the due date for cash discount 1 is higher than the
specified number of days for the yellow discount indicator light, a green light is
shown. If the corresponding due date for cash discount 1 is reached or is already
overdue, the discount indicator light switches to red.
Note: If you do not want to use the described generic configuration settings
based on the number of days before cash discount 1, do not maintain any
number of days. The following fixed logic for the discount indicator light will
apply automatically:
• Cash discount 1 possible (due date for cash discount 1 >= current date): green
discount indicator light
• Cash discount 2 possible (due date for cash discount 2 >= current date):
yellow discount indicator light
• All possible discounts missed: red discount indicator light
In the following situations, the discount indicator light is hidden:

• The process status is obsolete, cancelled, confirmed duplicate, or deleted.
• The invoice has already been processed by a payment run.
VIM070500-03-CGD-EN-1
• The invoice has been cancelled.

• No due date for cash discount 1 or cash discount 2 is available.
Note: The discount light settings depend on the corresponding SAP ERP
system and therefore no transport of the setting is available.
To specify the discount light settings:
1. Run the /n/OPT/VIM_WP_DSCL transaction.
2. In the VIM Workplace Disc. light settings Details screen, enter your company
code dependent settings.
Note: If you do not want to specify company code specific settings, enter
an asterisk (*) in the Company Code field.
VIM070500-03-CGD-EN-1
Chapter 18
Customizing Plug-in Controls for End-user Screens
Different end-user screens, for example the VIM Workplace or the indexing screen
(DP Dashboard) are enabled to use integrated plug-in views to display detail
information for a process.
You can also use plug-in controls in the Invoice Approval Dashboard, the Parked
Dashboard, and the Blocked Dashboard.
The following customization steps are necessary:

• Define the plug-in type
• Define the plug-in ID
• Assign the plug-in IDs to plug-in types
18.1 Defining the Plug-in Type

To use different plug-ins in different end-user screens, a plug-in type definition is
used to combine all plug-ins within one control.
To define the plug-in type:

Management > Cross Component Configuration > Processing Plug-In
Configuration > Define Plug-In Types.
2. In the Plug-In Type Definition Overview screen, define the plug-in type, using
the following parameters:
Plug-In Type
Unique ID of a plug-in type to be used within an end-user screen.
VIM070500-03-CGD-EN-1
Chapter 18 Customizing Plug-in Controls for End-user Screens
Plug-In Type Description

Enter a description of the plug-in type.
18.2 Defining the Plug-in ID

The plug-in ID definition describes all necessary technical information for the called
plug-in.
VIM baseline delivers the following plug-ins:

• Display archived invoice image (/OPT/CL_C_UI_PLUGIN_DEF_IMAGE).
Note: It is possible to display the archived invoice image using OpenText

Imaging Web Viewer. You must configure the corresponding settings to call
the Web Viewer. For more information, see section 19.2 “Configuration for
Java Viewer/Web Viewer” in OpenText Archiving and Document Access for
SAP Solutions - Scenario Guide (ER-CCS).
• Display line items (/OPT/CL_C_UI_PLUGIN_DEF_ITEM).
• Display DP and approval log (/OPT/CL_C_UI_PLUGIN_DEF_LOG).
• Display DP and approval comments (/OPT/CL_C_UI_PLUGIN_DEF_NOTE).
• Display the Extended ECM for SAP Solutions integration (/
OPT/CL_C_UI_PLUGIN_DEF_XECM).
To define the plug-in ID:

Configuration > Define Plug-In IDs.
2. In the Plug-In Definition Overview screen, define the plug-in ID, using the
Plug-In ID
Unique ID of the plug-in.
Plug-In title
Enter the title of the plug-in, which is displayed on the button in the plug-in
toolbar.
Plug-In description
Enter the tooltip of the plug-in, which is displayed on the button in the
plug-in toolbar.
Plug-In Sequence
Define the order of the buttons for the plug-in.
Plug-In class
To process the corresponding logic for the plug-in, enter the class to be
called during runtime. To integrate custom logic to retrieve data for existing
VIM070500-03-CGD-EN-1
18.3. Assigning the Plug-in IDs to Plug-in Types
plug-ins, you must create a subclass and redefine the

PLUGIN_DATA_CONTEXT_SET method.
Note: To create a new plug-in, you must create your own plug-in class
with superclass /OPT/CL_C_PMC_UI_PLUGIN.
Plug-In Icon
Enter the icon of the plug-in, which is displayed on the button in the plug-in
toolbar.
PI Active
Select this check box to activate the plug-in on the screen.
18.3 Assigning the Plug-in IDs to Plug-in Types

You define the possible plug-ins for a plug-in type within the mapping. For each
defined plug-in type, all plug-in definitions are maintained.
To assign plug-in IDs to plug-in types:

Configuration > Assign Plug-In IDs to Plug-In Types.
2. In the Mapping Plug-In Type <-> Plug-In ID Overview screen, assign plug-in
IDs to plug-in types, using the following parameters:
Plug-In Type
Unique ID of the plug-in type definition.
Plug-In ID
Unique ID of the plug-in definition.
18.4 Customizing the Integration of Extended ECM for

SAP Solutions
VIM provides an integration of OpenText Extended ECM for SAP Solutions as a
plug-in into the following VIM tools:
• Indexing screen
• VIM Workplace
• VIM Analytics
You can also integrate Extended ECM for SAP Solutions into VIM Analytics as a
custom button that opens a separate window. For more information, see “Defining
and Assigning Action Buttons” on page 441.
Extended ECM for SAP Solutions allows displaying content that is stored in the
OpenText™ Content Server in the SAP GUI. You also can upload content from the
SAP GUI to the Content Server.
VIM070500-03-CGD-EN-1
Extended ECM for SAP Solutions can be configured for several business objects.
That means, the solution is open for custom solutions. An example integration for
vendor workspaces is delivered with baseline. You can include custom scenarios
based on other business objects. For more information, see “Implementing Custom
Solutions for the Plug-in Framework” on page 541.
Prerequisites
• Extended ECM for SAP Solutions is installed, at least version 10.5 Service Pack 1.
• Extended ECM for SAP Solutions is customized, as described in OpenText
ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD).
• Workspaces can be created for business objects using the standard Extended
ECM for SAP Solutions GOS menu integration.
To customize the integration of Extended ECM for SAP Solutions:
1. Define the plug-in ID. See the description in “Defining the Plug-in ID”
on page 538.
In Plug-In class, enter the class for the respective VIM tool:
Indexing screen
/OPT/CL_C_IDX_UI_PLUGIN_XECM or your own custom class
VIM Workplace
/OPT/CL_C_PMC_UI_PLUGIN_XECM or your own custom class
VIM Analytics
/OPT/CL_C_VA2_UI_PLUGIN_XECM or your own custom class
2. Assign plug-in IDs to plug-in types. See the description in “Assigning the Plug-
in IDs to Plug-in Types” on page 539.
The plug-in types for the respective VIM tools are the following:
Indexing screen
VIM_IDX
VIM Workplace
VIM_WP
VIM Analytics
VIM_VA2

Management > Cross Component Configuration > Extended ECM Integration
> Configure xECM Integration for Plug-In Framework.
VIM070500-03-CGD-EN-1
18.4. Customizing the Integration of Extended ECM for SAP Solutions
4. Create a new entry to assign the plug-in ID to an extended ECM business object.
Note: If you use the generic classes /OPT/CL_C_IDX_UI_PLUGIN_XECM, /

OPT/CL_C_PMC_UI_PLUGIN_XECM or /OPT/CL_C_VA2_UI_PLUGIN_XECM
(see Step 1 on page 540), the following customizing is mandatory. If you
create a custom implementation where the business object and business
object key is defined directly in the coding, the following customizing is
not necessary.
Plug-In ID
Enter the ID created in Step 1 on page 540.
Object Type
Enter the business object that should be shown in this plug-in. This business
object must be configured in Extended ECM for SAP Solutions. In the
example screnshot: LFA1 for vendor workspace.
H/L
Define the origin of the object key: Header (/OPT/VIM_1HEAD) or Line (first
line of /OPT/VIM_1ITEM).
Reference field
Specify the field in the header or line item table that contains the object key
for the business object. In the example screenshot: /OPT/VIM_1HEAD-LIFNR
contains the object key for the vendor.
18.4.1 Implementing Custom Solutions for the Plug-in

Framework
If you want to display other business objects, you must perform the customizing as
described for the example “Vendor Workspace” in “Customizing the Integration of
Extended ECM for SAP Solutions” on page 539. You must adjust the classes and
function modules used in the customizing to select other object types and keys.
The following classes are delivered with baseline:
VIM070500-03-CGD-EN-1
Class /OPT/CL_C_UI_PLUGIN_DEF_XECM is the abstract superclass to deliver all

relevant methods.
For each plug-in type, one class is delivered:
Plug-In Type Class

VIM Workplace /OPT/CL_C_PMC_UI_PLUGIN_XECM
Indexing screen /OPT/CL_C_IDX_UI_PLUGIN_XECM
VIM Analytics (new) /OPT/CL_C_VA2_UI_PLUGIN_XECM
These classes can handle all Object Types whose object key is directly available in
tables /OPT/VIM_1HEAD or in the first selected line in /OPT/VIM_1ITEM. By using
customizing table /OPT/CT_XECM_PMC, the relevant fields can be customized directly.
Please see the customizing for vendor workspaces in “Customizing the Integration
of Extended ECM for SAP Solutions” on page 539 as a reference.
For more complex scenarios, where additional selects are necessary, you can define
custom classes. For each workspace type, a new implementation is needed. The
following procedure describes the implementation of a subclass of /
OPT/CL_C_IDX_UI_PLUGIN_XECM as a reference. You can implement the other classes
accordingly. Custom implementations for indexing screen and VIM Analytics (new)
can be created accordingly, as well.
To implement a custom class for the plug-in framework:
1. In the SE24 transaction, create a new subclass with class /

OPT/CL_C_IDX_UI_PLUGIN_XECM as superclass.
2. On the Methods tab, redefine the GET_BO_ID method.
VIM070500-03-CGD-EN-1
3. Implement custom coding to get the relevant object key. Return the object key in
the RV_OBJ_ID parameter.
4. Redefine the GET_SAP_OBJECT method.
5. Return the SAP Object type for the Extended ECM for SAP Solutions scenario in
the RV_SAP_OBJECT parameter.
6. Use this custom class in the customizing.
VIM070500-03-CGD-EN-1
18.4.2 Implementing Custom Solutions for the Buttons in VIM

Analytics
Adding button The /OPT/C_XECM_VA2_LFA1_ACTEXE_H function module is delivered to provide a
new button in VIM Analytics for vendor workspaces (SAP Object LFA1).
You can copy this module to a custom implementation. Select the respective Object
Key and SAP Object for the actual scenario. The customizing to activate the button is
described in “Defining and Assigning Action Buttons” on page 441.
VIM070500-03-CGD-EN-1
Hiding button The /OPT/C_XECM_VA2_BUTTON_H function module is delivered to decide during

runtime if a new button in VIM Analytics should be displayed or not.
You can copy this module to a custom implementation to define criteria when the
workspace button is displayed or not.
VIM070500-03-CGD-EN-1
Chapter 19
Configuring VIM Dashboards for Plug-ins
You can use plug-in controls in the Invoice Approval Dashboard, the Parked
Dashboard, and the Blocked Dashboard. You must perform the following
configuration of the dashboards’ customizing profiles.
• Maintaining customizing profiles for dashboards
• Assigning default profiles to product code
19.1 Maintaining Customizing Profiles for Dashboards

To use plug-ins in dashboards, you must maintain the customizing profiles for the
dashboards. This provides further information about which plug-in type should be
used. Additionally, you must set further attributes for the plug-in integration. These
attributes are used when opening one of the dashboards for the first time.
To maintain customizing profiles for dashboards:

Management > Cross Component Configuration > VIM Dashboards >
Maintain Customizing Profiles for Dashboards.
2. In the Profiles: Details screen, enter a profile, using the following parameters:
• Customizing Profile
• Customizing Profile Description
3. Double-click Profile Settings in Dialog Structure.
VIM070500-03-CGD-EN-1
Chapter 19 Configuring VIM Dashboards for Plug-ins
4. In the Profile Settings: Details screen, maintain the settings of the customizing
profile, using the following parameters:
Customizing Profile
Customizing profile defined in Step 2.
Application Class
Enter the application class.
The logic of the plug-in integration is located in the dashboard application
class. All relevant attributes and methods of the global application class are
delivered in a baseline dashboard application. You can enhance the class by
redefining components of the class within a custom class, which can be
maintained instead of the baseline class.
Default value: /OPT/CL_C_DBP_APPLICATION
User Class
Enter the user class.
Enter the dashboard user ABAP class, which contains logic to read and save
user-specific profile settings.
Default value: /OPT/CL_C_DBP_USER
Plug-In Type
Enter the plug-in type, defined in “Defining the Plug-in Type” on page 537.
Default value: VIM_DBP
Plug-In ID
Enter the plug-in ID, defined in “Defining the Plug-in ID” on page 538.
Plug-In Side
Select the location where the plug-in is displayed, right side or left side.
Default value: Right justified
Cont. Pane % Vt.

Content pane size ratio vertical in %: Enter the default plug-in size, in
percentage form, of the dashboard screen.
Show Plug-In
Select this check box to display the plug-in.
VIM070500-03-CGD-EN-1
19.2. Assigning Default Profiles to Product Code
19.2 Assigning Default Profiles to Product Code

By default, the user settings for plug-ins are derived from the user parameter. If
there is no user parameter available, you can configure the system to use a mapping
between default customizing profiles and product codes to determine the user
settings for the plug-in.
For the dashboard plug-in, the following product codes are relevant:
BIR
PO parking
IAP
Invoice Approval
LIX
PO blocking, both for header and item dashboard
PIR
Non PO parking
The user parameters, synchronous to the product codes, are the following:
• /OPT/CBIR_CUST_PROF
• /OPT/CIAP_CUST_PROF
• /OPT/CLIX_CUST_PROF
• /OPT/CPIR_CUST_PROF
Note: VIM baseline delivers a global profile (DEFAULT), which is called

whenever no specific user profile is configured. The DEFAULT profile must
always be available.
To assign default profiles to product code:

Management > Cross Component Configuration > VIM Dashboards > Assign
Default Profiles to Product Code.
VIM070500-03-CGD-EN-1
Chapter 19 Configuring VIM Dashboards for Plug-ins
2. Assign customizing profiles defined in “Maintaining Customizing Profiles for

Dashboards” on page 547 to the product code. To each product code for which
you want to use the corresponding plug-in, you must assign a customizing
profile.
With baseline, the product codes BIR, IAP, LIX, and PIR are assigned to the
DEFAULT customizing profile.
VIM070500-03-CGD-EN-1
Part 4
Optional Configuration
Part 4 Optional Configuration
This part describes the basic, but optional customizing. This customizing must be
done for optional VIM features, such as the integration of SAP Shared Service
Framework.
VIM070500-03-CGD-EN-1
Chapter 20
Extended Withholding Tax
Standard VIM configuration includes extended withholding tax in the tax folder of
the indexing screen. This applies to company codes and vendors that are relevant to
extended withholding tax.
Indexing screen users can change extended withholding tax code, base amount, and
amount. The data is transmitted to posting.
You can configure that the extended withholding tax data is no longer available on
the indexing screen and posting retrieves the withholding tax data from the vendor
master.
The following configuration actions are available for extended withholding tax.
• Hiding extended withholding tax on the indexing screen

• Limited hiding of extended withholding tax on the indexing screen
• Posting of zero withholding tax values
• Custom function that determines whether withholding tax data is transferred to
background posting from VIM or from SAP
• Withholding tax net amount is calculated from gross and tax instead of using the
header net amount
• Withholding tax amount is not transferred to background posting
• Manual check of extended withholding tax data as a business rule
The following configuration is mainly done in the Z constants table /

PTGWFI/Z_CONST under Product Code 005. Generally you access this table in the
following way.
To access Z constants table /PTGWFI/Z_CONST, Product Code 005:

The Constant Table, under Product Code 005, contains the wanted constant.
To configure hiding extended withholding tax on the indexing screen:
1. In the /PTGWFI/Z_CONST Constant Table, under Product Code 005, double-

click the constant WHTAX_FROM_SAP.
VIM070500-03-CGD-EN-1
Chapter 20 Extended Withholding Tax
If you do not want to hide withholding tax for all vendors, you can create a custom
function module that limits the hiding and put it into another constant.
To configure limited hiding of extended withholding tax on the indexing

screen:
1. Create a custom function module.
Note: You can use the following VIM custom function module example as
a base for copying: /OPT/VIM_WT_LIMIT_HIDE.

click the constant CUSTOM_FM_WHHIDE.
3. Enter Constant Value <your custom function module name> and save.
To configure the posting of zero withholding tax values:

click the constant WHT_POST_ZERO.
To configure a custom function that determines whether withholding tax data

is transferred to background posting from VIM or from SAP:

click the constant WHT_EXIT_BAPI.
2. Enter a custom function module and save.
Note: You can use the following VIM custom function module example as
a base for copying: /OPT/VIM_WT_BAPI_TRANS.
To configure that the withholding tax net amount is calculated from gross and
tax instead of using the header net amount:

click the constant WHT_CALC_NET.
2. Enter Constant Value X (which means “calculate”) and save.
To configure that the withholding tax amount is not transferred to background

posting:

click the constant WHTAX_AMT_TR.
2. Do not enter a Constant Value (which means “do not transfer”) but save.
VIM070500-03-CGD-EN-1
To configure manual check of extended withholding tax data as a business
rule:
1. Check for existing process type 289 (NPO) / 415 (PO) in the document type
processing. If it does not exist, create it.

Configuration > Characteristic Specific Document Type Configuration.
3. Select a country.
4. In the Dialog Structure, double-click Characteristic Specific Process Types.
5. Add process type 289 (NPO) or 415 (PO).
Limitations of Extended Withholding Tax

VIM cannot consider every SAP customizing setting for the calculation of
withholding tax. The following limitations apply.
Limitations of extended withholding tax type settings
• The withholding tax base amount must be either net or gross or tax amount.
• Accumulation is not supported.
• Minimum or maximum amounts are not supported.
• Cash discount is not supported.
• Control data is not supported.
• Central invoice is not supported.
Limitations of extended withholding tax code settings
• Percentage subject to tax is supported.

• Withholding tax rate (not fraction, not formula based) is supported.
• Minimum or maximum amounts are not supported.
• Surcharges are not supported.
• Exemption reasons for withholding tax codes are not supported.
• Collection codes are not supported.
Limitation of exemption
• Vendor master based exemption is supported – other exemptions or surcharges

are not supported.
VIM070500-03-CGD-EN-1
Chapter 21
Return to Vendor
The Return to Vendor (RTV) function allows you to inform the vendor by email that
the invoice is being returned. It also terminates the DP workflow. The vendor is
informed by an email, which is generated based on a template that the VIM user
selects. The email lists the reasons for the return. It may contain additional
comments and a signature. It may have the invoice image or additional images
attached. VIM users may select several different return reasons that are maintained
in VIM customizing. You may change the content of the email by implementing
your custom coding in new enhancement spots.
When the user clicks the Return to Vendor process option in the DP dashboard, a
new screen opens where all RTV-related information must be entered.
When the RTV function is performed successfully, the generated email is sent using
standard SAP functionality (SAPConnect). The DP document is set to obsolete, the
DP workflow is finished, and the email is archived. Return reasons are stored along
with the DP step comments. Comments are mandatory.
The following sections describe the activities that are necessary to configure the RTV
function.
• “Configuring SAPConnect and SMTP” on page 558
• “Maintaining Process Options” on page 558
• “Maintaining Return Reasons” on page 558
• “Maintaining Email Templates” on page 558
• “Maintaining the Email Determination User Exit” on page 559
• “Maintaining the Email Signature” on page 559
• “Maintaining Email Archiving” on page 561
• “Maintaining Project Enhancements” on page 561
VIM070500-03-CGD-EN-1
Chapter 21 Return to Vendor
21.1 Configuring SAPConnect and SMTP

RTV uses SAP Business Communication Services (BCS), which in turn relies on
SAPConnect for sending the emails over SMTP protocol. Make sure that
SAPConnect is properly configured on your system.
21.2 Maintaining Process Options

In VIM standard, the new process option 2026 performs the RTV function. The new
process option is not added to any standard VIM process types in VIM baseline
configuration. Maintain this option for selected process types and roles according to
your organizational needs.
Note: Do not use the Comments required setting with RTV. The comments are
mandatory for RTV regardless of this setting, and they must be entered on the
RTV screen and not in the DP dashboard. If you select the Comments required
check box in the process option customizing, you will introduce an
unnecessary processing step.
21.3 Maintaining Return Reasons

The return reasons are maintained in the /OPT/VIM_RTVV table. The following
customizing node is provided:
Run the n/OPT/SPRO transaction, and navigate to Vendor Invoice Management >
Cross Component Configuration > Return to Vendor > Maintain return reasons.
If multiple languages will be used with RTV, each return reason description has to
be translated into the required languages. To translate, select GoTo > Translation in
the table maintenance dialog box.
21.4 Maintaining Email Templates

The email body is built from a template. The template is maintained in the system
and selected by the user. You create templates as standard texts in the SO10
transaction. You may create the templates in several languages depending on VIM
user and vendors preferences. You must name the template with a prefix that is then
maintained in the new Z-constant 005 RTV_TEMPLATE_PREFIX in the /
PTGWFI/Z_CONST table. In the standard configuration it is assumed that template
names begin with /OPT/VIM_RTV, with the following standard configuration:
Product Code
005
Constant
RTV_TEMPLATE_PREFIX
Description
Prefix for standard texts used for Return to Vendor
VIM070500-03-CGD-EN-1
21.5. Maintaining the Email Determination User Exit
Constant Value
/OPT/VIM_RTV
OpenText delivers a sample standard text for vendor email, /

OPT/VIM_RTV_EXAMPLE, in English.
21.5 Maintaining the Email Determination User Exit

The email address to be used is normally read from vendor master (“main” email
address in the email list of XK03). You can override this logic using a user exit, which
is a function module whose name must be maintained in the new Z-constant 005
RTV_GET_EMAIL in the /PTGWFI/Z_CONST table:
Product Code
005
Constant
RTV_GET_EMAIL
Description
User exit / function to retrieve email for Return to Vendor
Constant Value
<Name of the function module>
The function module must include the following parameters:

• Importing
pi_header TYPE /opt/vim_1head

• Changing
pc_email TYPE char80
21.6 Maintaining the Email Signature

The email signature is built from a template. You maintain the template in the
system. Therefore, you create templates as standard texts in the SO10 transaction.
You may create the templates in several languages. To maintain the template name,
use the Z constant 005 RTV_SIGNATURE_NAME in the /PTGWFI/Z_CONST table.
To maintain the email signature template name:
1. Run the SM30 transaction for the /PTGWFI/Z_CONST table.

2. Navigate to the product code 005, constant RTV_SIGNATURE_NAME, description:
SO10 Text Name for email signature used for Return to Vendor
3. Maintain the template name. Default value: /OPT/VIM_SIGNATURE_RTV
Note: OpenText delivers a sample standard text for the vendor signature in
English: /OPT/VIM_SIGNATURE_RTV
VIM070500-03-CGD-EN-1
In the standard text, you can insert variables. They will be enriched from the SAP
user address data at runtime. The following variables are available:
<FULLNAME> Format from SAP user person address data

<FUNCTION> Function from SAP user person address data
<DEPARTMEN Department from SAP user person address data
T>
<ROOM_NO_P> Room Number from SAP user person address data
<FLOOR_P> Floor from SAP user person address data
<BUILDING_P> Building from SAP user person address data
<NAME> Name from SAP user company address data
<NAME_2> Name from SAP user company address data
<STREET> Street from SAP user company address data
<HOUSE_NO> House number from SAP user company address data
<POSTL_COD1 Postal Code from SAP user company address data
>
<CITY> City from SAP user company address data
<PO_BOX> PO Box from SAP user company address data
<POSTL_COD2 Postal Code for PO Box from SAP user company address data
>
<COUNTRY> Country from SAP user company address data
<TEL1_NUMBR Telephone from SAP user communication address data
>
<TEL1_EXT> Extension for Telephone from SAP user communication address data
<FAX_NUMBE Fax from SAP user communication address data
R>
<FAX_EXTENS Extension for Fax from SAP user communication address data
>
<E_MAIL> E-Mail from SAP user communication address data
VIM070500-03-CGD-EN-1
21.7. Maintaining Email Archiving
21.7 Maintaining Email Archiving

Emails that are sent to the vendor will be archived. Therefore, you maintain the
document type AR_OBJECT in the Z constant 005 RTV_AR_OBJECT in the /
PTGWFI/Z_CONST table.
To maintain the email archiving document type:
1. Run the SM30 transaction for the /PTGWFI/Z_CONST table.
2. Navigate to the product code 005, constant RTV_AR_OBJECT, description:

AR_OBJECT for archiving email used for Return to Vendor
3. Maintain the document type. Default value: /OPT/HTM
Note: OpenText delivers a standard document type: /OPT/HTM. To customize

ArchiveLink for the used document type, run the OAC2 and OAC3 transactions.
For more information, see “Linking Archive Document Type to VIM Business
Object” on page 36.
21.8 Maintaining Project Enhancements

You may want to add custom logic to some parts of the email processing. For this
purpose, several enhancement points have been added to the email processing. This
section provides an overview.
Package: /OPT/VIM, Program: /OPT/VIM_RTV_PROCESS

For the /OPT/VIM_RTV_PROCESS program, several enhancement points have
been added. They are defined in the /OPT/ES_VIM_RTV_PROCESS enhancement
spot.
Subroutine: BUILD_FINAL_DATA
The subroutine BUILD_FINAL_DATA performs the email processing and
archiving. The following actions are available:
• Change the email body in the /OPT/ES_VIM_RTV_PROCESS_CB enhancement

point.
• Change the email reasons in the /OPT/ES_VIM_RTV_PROCESS_CR
enhancement point.
• Change the complete email texts in the /OPT/ES_VIM_RTV_PROCESS_CT
enhancement point.
• Change the email document in the /OPT/ES_VIM_RTV_PROCESS_SD
enhancement point.
• Change the email document before it is being sent in the /
OPT/ES_VIM_RTV_PROCESS_SR enhancement point.
• Switch on or off archiving or the email in the /OPT/ES_VIM_RTV_PROCESS_CA
enhancement section.
VIM070500-03-CGD-EN-1
PAI-Module: USER_COMMAND_0001
In the USER_COMMAND_0001 PAI-Module, you may want to implement your own
email processing within the /OPT/ES_VIM_RTV_PROCESS_BFD enhancement
section.
VIM070500-03-CGD-EN-1
Chapter 22
Supplier Self Service
Supplier Self Service is an optional component. It provides a web interface that

enables suppliers to keep track of their invoices’ status. It also shows additional
information like payment status and SAP documents linked to the invoice (for
example Purchase Order number, Delivery Note number).
Figure 22-1: Supplier Self Service architecture
Supplier Self Service can be integrated in a full variant and a lean variant.
• The full variant allows user based access. After the supplier signed in to the
application, an initial view is shown with a list of all relevant invoices and
detailed status information. Furthermore, it provides flexible options to select
invoices and display a sorted hit list.
• The lean variant provides anonymous access to the Supplier Self Service – no
user account required. The user can only search for a single invoice by entering
required search criteria. If mandatory search criteria matches the invoice data in
the backend system, specific invoice status information is shown on the web
page.
The full variant is not part of the VIM 7.5 SP2 delivery. Only the lean variant is
delivered. The full variant will be delivered with a future SP.
Supplier Self Service lean variant is enabled for multiple deployment options:
• HANA Cloud Deployment
VIM070500-03-CGD-EN-1
Chapter 22 Supplier Self Service
• On-Premise
Most of the customization is common for both deployments. So, the customization is
differentiated wherever it is applicable. If you plan to use the On-Premise
deployment, skip “Customizing the HANA Cloud Server (Option)” on page 575.
Supplier Self Service introduces the new report /OPT/WR_3S_COLLECTION, which

must be scheduled as a job. For a detailed description of the report, see section 5.8
“Scheduling Batch Jobs for Supplier Self Service” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM-AGD).
This chapter describes the customization that is necessary to use Supplier Self
Service.
22.1 Customizing the OData Channel on the SAP

NetWeaver Gateway System
SAP NetWeaver Gateway is a development framework, which is available as an SAP
NetWeaver Application Server ABAP add-on. It provides OData access to SAP
Business Suite by establishing a connection to target clients, platforms, and
programming framework.
You must configure your SAP NetWeaver Gateway system to allow the server
applications to retrieve the data requested by the web client. You must perform
additional configuration steps as described in this chapter. As a prerequisite, the
SAP NetWeaver Gateway 2.0 add-ons must be installed on top of an existing SAP
Business Suite or an application platform, as described in part X “Vendor Invoice
Management Component for SAP NetWeaver Gateway Installation” in OpenText
Vendor Invoice Management for SAP Solutions - Installation Guide (VIM-IGD).
Note: Depending on your underlying SAP NetWeaver release, the

configuration settings for the OData Channel and the structure in the
Implementation Guide (IMG) may differ.
You find more detailed information in the SAP NetWeaver Online Configuration
Guide: http://help.sap.com/saphelp_gateway20sp09/helpdata/en/4c/
a670b0e36c4c01ae2b9a042056f9dc/frameset.htm.
VIM070500-03-CGD-EN-1
22.1. Customizing the OData Channel on the SAP NetWeaver Gateway System
22.1.1 Configuring Connection Settings

Supplier Self Service uses RFC for communication between the SAP NetWeaver
Gateway system and the SAP business system. Even if the Gateway add-on is part of
the SAP business system, you must customize the RFC connection as described in
this section.
To configure connection settings:

1. Run the /n/SPRO transaction and navigate to SAP Customizing
Implementation Guide > SAP NetWeaver > Gateway > OData Channel >
Configuration > Connection Settings > SAP NetWeaver Gateway to SAP
System > Manage RFC Destinations
2. Define RFC destinations that point to relevant SAP business systems. If an RFC
destination points to an SAP system alias, this system alias will point to the
corresponding SAP business system.
Note: You can use only RFC destinations of connection type 3 (Connection
to ABAP System).
3. On the Technical Settings tab, add Target Host and System Number of the
SAP business system.
VIM070500-03-CGD-EN-1
4. Force remote logon on the target system: Therefore, on the Logon & Security
tab, manage specific Client, User, and Password information. This setting is
mandatory.
Note: For the communication between SAP NetWeaver Gateway system

and SAP business system, no Trust Relationship is necessary . If you want
to use Trust Relationship, consider all settings that have to be customized,
as described in http://help.sap.com/saphelp_snc700_ehp01/helpdata/en/30/
827be3adda4f099493e76a427bc203/frameset.htm.
VIM070500-03-CGD-EN-1
22.1.2 Configuring System Aliases

In this step, you configure the system aliases that you want to use for the RFC
connection to the SAP business system.
To configure system aliases:

Configuration > Connection Settings > SAP NetWeaver Gateway to SAP
System > Manage SAP System Aliases.
2. In the System Aliases screen, configure a new entry, using the following
parameters:
SAP System Alias

Enter an ID for the new system alias.
Description
Optional: Enter a description for the new system alias.
RFC Destination
Enter or select the name of the RFC destination.
Software Version
Enter or select the software version DEFAULT.
22.1.3 Configuring Gateway Users

Users of the SAP NetWeaver Gateway are grouped in roles, which are needed for
several other configurations. There is no restriction on the number and names of
roles created for SAP NetWeaver Gateway. You must enhance the roles of the users
in your SAP NetWeaver Gateway system with the authorizations contained in the
authorization template /IWFND/RT_GW_USER.
Note: Only a user administrator can create and assign roles to users. Details
about different SAP user administrator types are available in the SAP
NetWeaver Library documentation at http://help.sap.com/nw70.
To configure Gateway users:

Configuration > User Settings > Define Role for SAP NetWeaver Gateway
User.
VIM070500-03-CGD-EN-1
2. In the Role Maintenance screen, enter the role already set up in the system and
assigned to the existing user. (For a new role, set up the role first.)
3. Specify the required SAP NetWeaver Gateway authorizations for this new role.
On the Authorizations tab, click Change Authorization Data.
4. From the list of template roles, select /IWFND/RT_GW_USER and click Adopt
reference. If the list of templates does not appear, click Edit > Insert
Authorization(s) > From template.
5. Assign values to the authorization fields according to the role.
a. Add authorization object S_SERVICE
• Full authorization
b. Add authorization object S_USER_GRP
• Activity: Display
• User group in user master maintenance: Full authorization
6. Generate the profile and save your settings for the role.
VIM070500-03-CGD-EN-1
To assign users to the role:
1. To directly include user IDs in the Change Roles screen, on the User tab, add
the user ID in the User ID field and press ENTER.
Alternatively, run the SU01 transaction and add the role explicitly to the user on
the Display Users screen. Therefore you have to enter or select the role name on
the Roles tab.
22.1.4 Configuring OData Services

OData Channel implementations retrieve the data from an SAP Business Suite
system. After a service has been defined, the service must be registered or activated
on the SAP NetWeaver Gateway system.
To configure OData Services:

Administration > General Settings > Activate and Maintain Services.
2. Activate the ICF Node ODATA for the following services:
VIM070500-03-CGD-EN-1
• /OPT/VIM_3S_CONFIGURE
• /OPT/VIM_3S_DATA_LEAN
• /OPT/VIM_3S_GW_APP_CONF (only needed for lean On-Premise solution)
For every service entry, you must select the ICF Node OData and click Activate
ICF Node.
The traffic light in front of the service switches to green.
3. If required, add the service node to package /OPT/VIM_GATEWAY. In this case,

you are prompted to enter a package name.
22.1.5 Assigning an SAP System Alias to an OData Service

You must assign roles and SAP system aliases to an OData service. With this
assignment, an OData request from an SAP NetWeaver Gateway consumer can be
routed to the corresponding backend system. The system can correctly identify the
SAP system that is responsible for processing the data of an inbound request.
To assign an SAP system alias to an OData service:

Administration > General Settings > Assign SAP System Aliases to OData
Service.
2. In the Assign SAP System Aliases to OData Service screen, configure a new
entry for every OData service, using the following parameters:
Service Doc. Identifier

Enter or select the Service Identifier.
User Role
Enter or select the user role you want to assign to the system alias. Leave
this field blank to assign the system alias independent from roles.
SAP System Alias

Enter or select the name of the SAP system alias.
Default System
Select this check box to set the system as default system.
VIM070500-03-CGD-EN-1
22.1.6 Assign Data Providers to Data Models

In SAP NetWeaver Gateway, entities are defined and connected in object models.
These object models can be exposed as OData services during runtime. The runtime
processing is handled by data provider classes that are assigned to the object
models.
To assign data providers to data models:

Administration > General Settings > Assign Data Provider to Data Model.
2. In the Assign Data Provider to Data Model screen, configure a new entry for
every OData service, using the following parameters:
Model Identifier
Enter or select the ID of the model the data provider is used for.
Type
Select (Adaption) Data Provider (default setting).
Software Version
Enter or select software version DEFAULT (because there is only one data
provider set to a model).
Class/Interface
Enter or select ABAP class /IWFND/CL_ODC_COE_RT_MANAGER.
Description
Optional: Enter explanatory text.
VIM070500-03-CGD-EN-1
22.1.7 Activating SAP NetWeaver Gateway

After you have performed all customizing steps described above, the final step is to
activate SAP NetWeaver Gateway itself. This activity starts all SAP NetWeaver
Gateway services.
To activate the SAP NetWeaver Gateway server:

Configuration > Activate or Deactivate SAP NetWeaver Gateway.
2. If SAP NetWeaver Gateway is not activated, click the Activate button.
Note: If the activation of services fails, use the SICF transaction to activate
services manually.
22.1.8 Configuring the Supplier Self Service On-Premise UI5

Repository
This configuration is relevant only for the lean variant of the Supplier Self Service
On-Premise option. It is not applicable for HANA Cloud deployment.
To configure the Supplier Self Service On-Premise UI5 repository:
1. Run the SICF transaction.
2. Navigate to the following path: default_host > sap > bc > ui5_ui5.
3. Select service ui5_ui5.
4. Right-click service ui5_ui5 and create the new sub-element opt.
VIM070500-03-CGD-EN-1
5. When opt is created, right-click the opt service and create a new sub-element
VIM_3S_PREM.
VIM070500-03-CGD-EN-1
6. To activate the newly created services opt and VIM_3S_PREM, right-click

them, and then click Activate Service.
22.1.9 Configuring the Gateway Service Authorization

The Supplier Self Service On-Premise option allows the UI5 repository to be
uploaded on the Gateway server as a BSP application. The On-Premise URL is
generated for the BSP application with default HTML, and the application is
accessed using this URL.
To bypass authorization issues for the service path, provide logon data to the
following service paths with authorized user.
To provide logon data for OData service paths:
1. Run the SICF transaction, and navigate to the following path: /

default_host/sap/opu/odata/.
2. Double-click the opt service node to get the details.
3. Provide logon data User and Password.
4. Save the data.
VIM070500-03-CGD-EN-1
22.2. Customizing the HANA Cloud Server (Option)
To provide logon data for BSP service paths:

default_host/sap/bc/bsp/.
4. Save the data.
To provide logon data for UI5 service paths:

default_host/sap/bc/ui5_ui5/.
4. Save the data.
22.2 Customizing the HANA Cloud Server (Option)

The SAP HANA Cloud Platform enables you to use Java applications in a cloud
environment. The Supplier Self Service application runs on a runtime container
where it can use the platform services APIs and Java EE APIs according to standard
patterns. After you have deployed the application on the platform, you can
configure and operate it using the SAP HANA Cloud Platform Cockpit.
Note: You need an SAP account for accessing the HANA Cloud. For more
information, see https://help.hana.ondemand.com/help/frameset.htm?
8ed4a705efa0431b910056c0acdbf377.html.
To customize the application settings, log on to the HANA Cloud Platform Cockpit
with your credentials. The cockpit is the central point for managing all activities
associated with your account and for accessing key information about your
applications. It allows you to manage all applications deployed in your account from
a single dedicated web-based user interface. You can log on to the cockpit at the
following URLs. Use the relevant URL for your account type and, in case of
customer and partner accounts, the associated region:
Europe
https://account.hana.ondemand.com/cockpit
United States
https://account.us1.hana.ondemand.com/cockpit
VIM070500-03-CGD-EN-1
22.2.1 Configuring the Java Application

In the SAP HANA Cloud Platform Cockpit, in the Content pane, navigate to Java
Applications. In the Details area, all Java applications that have been deployed
successfully on the HANA Cloud are listed. Make sure that the Supplier Self Service
application is shown. The name of the Java application is set in the deployment step
described in section 40.2 “Deploying the Application on the SAP HANA Cloud
Server” in OpenText Vendor Invoice Management for SAP Solutions - Installation Guide
(VIM-IGD). Click on the application link to view details of the application settings.
To get an overview of the current status of the application, select Dashboard in the
Content pane. This provides key information in a summarized form and allows you
initiating actions, such as starting, stopping, and undeploying applications.
22.2.1.1 Customizing the Connectivity Destination

Connectivity destinations are part of the SAP HANA Cloud Platform connectivity
service. They are used for the outbound communication of a cloud application to a
remote system. The connectivity destinations contain the connection details for the
remote communication of an application. They also resolve the destination at
runtime, based on the symbolic name provided.
Use the Destinations editor in the SAP HANA Cloud Platform Cockpit to configure
HTTP destinations. They connect the Supplier Self Service web application to the
Internet or make it consume an on-premise backend system via HTTP(S).
To customize the connectivity destination:
1. In the Content pane, navigate to Destinations.
2. Click Create New and set up a new destination as described in the following:
VIM070500-03-CGD-EN-1
Name
Enter destination name vimodataservice. This name is used by the
Supplier Self Service application to refer to remote connections.
Description
Optional: Enter a description.
Type
Select HTTP. The HTTP protocol is used for both Internet and on-premise
connections. Additionally, you must specify the destination URL, select the
ProxyType, and then the Authentication type.
URL
Enter the URL of the virtual host for connecting the Cloud connector. Make
sure that you specify the URL exactly as it is specified in the System
Mapping of the Cloud connector.
ProxyType
Select the Proxy Type of the Cloud connector. Default setting: OnPremise
CloudConnectorVersion
Select the version of your Cloud connector from the list.
Note: To use the Connectivity service 2.x and the Cloud connector 2.x
version, you must specify the property for HTTP destinations to 2.
Authentication
Select BasicAuthentication. You must enter User ID and Password.
VIM070500-03-CGD-EN-1
Note: To ensure authorized Gateway access via OData Services,

specify the SAP service user that has the defined role assigned. For
more information, see “Configuring Gateway Users” on page 567.
If you need more information about the SAP HANA Cloud Platform configuration,
see the online documentation: https://help.hana.ondemand.com/help/frameset.htm?
e47748b5bb571014afedc70595804f3e.html.
22.2.2 Customizing the Cloud Connector

After the SAP HANA Cloud connector has been installed and the Cloud connector
daemon has been started, you can log on and perform the necessary customization
to make your Cloud connector operational. This section describes how to do this.
To log in to the SAP Cloud connector:
1. In a web browser, enter: https://<hostname>:8443; where <hostname> refers

to the machine on which the Cloud connector has been installed. If the Cloud
connector has been installed and started successfully, the SAP Cloud Connector
Login screen opens.
2. Login to the Cloud connector, for User Name and Password, enter
Administrator and manage (case sensitive).
Note: When you log in for the first time, you must change the password
before you continue.
22.2.2.1 Configuring the Proxy Connection

After the proxy parameters have been defined, the Cloud connector is able to
connect to the SAP HANA Cloud Platform and download the configuration and
credentials corresponding to your account. When you log in for the first time, the
Cloud connector also collects the necessary information required for this purpose in
the Configuration section of the Settings customizing tab.
VIM070500-03-CGD-EN-1
To configure the proxy connection:
1. Make sure the Landscape Host field specifies the SAP HANA Cloud Platform
landscape that you should use.
2. For Account Name and User Name (user/password), enter the values you
obtained when you registered your account on the SAP HANA Cloud Platform.
3. When you have completed all settings, click Apply.

The Cloud connector starts a handshake with the cloud side and attempts to
establish a secure SSL tunnel to the server hosting account in which your on-
demand applications are running.
However, no requests are yet allowed to pass from the cloud side to any of your
internal backend systems.
4. To allow your on-demand applications to access specific internal backend

systems, proceed with the access configuration, see “Establishing Connections
to the SAP HANA Cloud Platform” on page 580.
VIM070500-03-CGD-EN-1
22.2.2.2 Establishing Connections to the SAP HANA Cloud Platform

After the initial setup has been completed successfully, the tunnel to the cloud
endpoint is open. However, you can manually close (and reopen) the connection to
the SAP HANA Cloud Platform by opening the Home tab and clicking the
Disconnect button (or the Connect button to reconnect to the SAP HANA Cloud
Platform).
The green icon next to Landscape Host and HTTPS Proxy indicates that they both
are valid and work properly. In case of a time-out or a connectivity issue, the icon is
respectively yellow (warning) or red (error), and a tooltip displays the cause of the
problem.
22.2.2.3 Configuring the Cloud Connector for HTTP

To allow your on-demand applications to access a certain backend system on the
intranet, you must insert an extra line into the Cloud connector access control
management.
To configure the Cloud connector for HTTP(S):
1. Go to the Access Control tab and click Add.
2. Configure the Cloud connector for HTTP, using the following parameters:
Virtual Host
Specify the host name exactly as it is specified as the URL property in the
HTTP destination configuration in SAP HANA Cloud.
The virtual host can be a fake name. If you leave the Internal Host
parameters blank, the Cloud connector will try to forward the request to the
network address specified by the virtual host and port. In this case, this
address needs to be real.
VIM070500-03-CGD-EN-1
Virtual Port
Specify the virtual port.
This basically allows you to distinguish between different entry points of
your backend system, for example, HTTP/80 and HTTPS/443, and have
different sets of access control settings for them. For example, some non-
critical resources may be accessed by HTTP, while some other critical
resources are to be called using HTTPS only.
Internal Host
Specify the actual host under which the target system can be reached within
the intranet. The internal host must be an existing network address that can
be resolved on the intranet.
Internal Port
Specify the actual port under which the target system can be reached within
the intranet.
Protocol
Specify the protocol.
The Cloud connector can use HTTP or HTTPS for the connection to the
backend system.
Note: This is completely independent from the settings on SAP

HANA Cloud side.
This means, even if the HTTP destination on SAP HANA Cloud side
specifies http:// in its URL, you can select HTTPS. Therefore, you are
ensured that the entire connection from the on-demand application to the
actual backend system (provided through the SSL tunnel) is SSL-encrypted.
The only prerequisite is that the backend system supports HTTPS on that
port.
If you specify HTTPS and there is a “system certificate” imported in the
Cloud connector, the latter attempts to use that certificate for performing a
client-certificate-based login to the backend system. If there is no system
certificate imported, the Cloud connector opens an HTTPS connection
without client certificate.
For more information, see the online documentation about “Installation of a
System Certificate for Mutual Authentication”: https://
help.hana.ondemand.com/help/frameset.htm?
3f974eae3cba4dafa274ec59f69daba6.html
Back-end Type
Select SAP NetWeaver Gateway.
This is important mainly for metering information: tunnel connections to
any kind of SAP system are free of charge, while using the tunnel for
connecting to a non-SAP system costs a fee.
3. After saving the hostname mapping, use the Check button to trigger a ping
from the Cloud connector to the Internal host. This option allows you to make
VIM070500-03-CGD-EN-1
sure that the Cloud connector can access the Internal system. It also allows you
to catch basic issues like spelling mistakes or firewall problems between the
Cloud connector and the Internal host. In case the ping to the Internal host fails,
the Cloud connector displays a red exclamation mark icon.
22.2.2.4 Limiting the Accessible Services for HTTP(S)

In addition to allowing access to a particular host and port, you also must specify
which URL paths (resources) are allowed to be invoked on that host. The Cloud
connector uses very strict white-lists for its access control. Only those URLs for
which you explicitly granted access are allowed. All other HTTP(S) requests are
denied by the Cloud connector.
To define the permitted URLs (resources) for a particular backend system:
1. In the Resources tab of the Access Control, select the line corresponding to the
backend system.
2. In the Add Resource dialog box, in URL Path, enter the specific URL path that
you want to allow to be invoked: /sap/opu/odate/opt.
3. Select the Enabled check box to specify that the resource shall initially be
enabled.
4. For Access Policy, click Path and all sub-paths.

With this setting, the Cloud connector allows all requests for which the URL
path (not considering any query parameters) begins with the specified string.
The Cloud connector checks that the path part of the URL is exactly as specified in
the configuration. If it is not, the request is denied.
Note: The URL check does not include a possible question mark (?) that may
denote the start of optional CGI-style query parameters.
VIM070500-03-CGD-EN-1
22.3. Customizing Supplier Self Service
For more information about the SAP HANA Cloud connector configuration, see the
online documentation: https://help.hana.ondemand.com/help/frameset.htm?
e7d4927dbb571014af7ef6ebd6cc3511.html.
22.3 Customizing Supplier Self Service

To get Supplier Self Service to run, you must perform some global customizing steps
on the central SAP business system.
To customize Supplier Self Service:

Management > Cross Component Configuration > Supplier Self Service >
Customizing.
2. Perform the customizing, using the following parameters.
Exit for Payment Information

Enter a function module to exchange the retrieval of payment information
with a custom function.
Baseline: /OPT/VIM_3S_GET_PAYMENTS
Exit for Data Retrieval Lean
Enter a function module to exchange the complete data with a custom
function for lean variant.
Baseline: /OPT/VIM_3S_GET_DATA_LEAN
VIM070500-03-CGD-EN-1
Exit for Data Retrieval Full

This parameter currently has no function. It refers to the full variant, which
is not yet supported.
Disclaimer Text (SO10)

Maintain a text element in transaction SO10 to be displayed as disclaimer on
the user interface.
In the Text ID field, select ST for Standard Text.
You can use the disclaimer to provide details to the supplier how to use
Supplier Self Service.
To use the Supplier Self Service lean variant:
a. In the SUPPLIER SELF SERVICE selection pane, enter the search
criteria.
Note: Your entries must match the invoice data exactly.

Otherwise, an error message is displayed when you click Display.
Invoice Amount: Decimal notation is 1,234,567.89
b. Click Display.
The invoice details are displayed, including Invoice Status, Payment
Details, and PO / DN Reference.
In the upper right corner, the processing status of the invoice is
displayed: In Process, Paid, Partially Paid, Received, or Rejected.
c. To clear the selection fields, click Reset.
Fallback Language
Enter the default language. If a user has no language customized or if there
is no translation for the specified language, the default language is taken.
Network
Enter the external supplier network ID to process the status mapping.
Baseline: 3S
The following additional settings can be used for the full variant to integrate a
notification option in the user self registration process for vendors. In baseline
delivery, the notification sends an SAP mail to the administrator who is
responsible for the onboarding process of the users. The email contains the
corresponding information of the user who registers for the application.
Administrator Type, Administrator ID

Configure the administrator with user type and user identification.
Notification Text
Enter a text object for the notification email context. You can maintain text
objects using the SO10 transaction. The first line of the text stored in SO10 is
used as the subject line of the email.
VIM070500-03-CGD-EN-1
22.4. Configuring the Status
Language
Enter the language for the notification mail.
22.4 Configuring the Status

Supplier Self Service determines the invoice status for invoices. The processing
status of the VIM invoice must be mapped to the status codes that are known or
should be shown in Supplier Self Service. For posted invoices, the collection report
already determines a Previous External Invoice Status for paid invoices.
To configure status mapping and description:

Maintain Processing for Supplier Network.
2. In the Define Supplier Networks screen, maintain an entry for the Supplier Self
Service, using the following parameters:
Netw
Enter a two-digit identifier for the external supplier network.
Default value: 3S
Supplier Network
Enter the name of the external supplier network.
Default value: Supplier Self Service
Class Name
Enter the name of the class containing the processing logic for the external
supplier network.
Default value: /OPT/CL_E_SUPPLIER_NETW_3S
Notes
• If you want to overwrite the logic of class /
OPT/CL_E_SUPPLIER_NETW_3S, you can derive a subclass of this
class and adjust it to your needs. Maintain your new class in the
Class Name field afterwards.
• The fields Class Name Outbound and Class Name Inbound are not
relevant for Supplier Self Service.
3. To define the status known in Supplier Self Service, select the entry for Supplier
Self Service and double-click Define External Status in the Dialog Structure.
4. In the Define External Status screen, maintain entries for all status codes
known in Supplier Self Service, using the following parameters:
ExtStatID
External Invoice Status
VIM070500-03-CGD-EN-1
Enter a two-digit, artificial key for the status of the external supplier
network.
Example: IP for the external status inprocess.
External Status
External Invoice Status as known by the Network
Enter the invoice status as known by the external supplier network.
Example: inprocess
Note: Ensure that the status code in the field External Status is exactly
the status code that is delivered by Supplier Self Service. Pay attention
to lower and upper case.
External Status Description Long

Enter a description for the invoice status of the external supplier network.
Example: In process
5. To map the process status of a VIM invoice to the status codes that are known in
Supplier Self Service, double-click Assign External Status to VIM Document
Status in the Dialog Structure.
The process status of a VIM invoice is a combination of the VIM document
status, the SAP document status and the previous status determined by the
external supplier network. A combination of these three status codes determines
the new external status code.
Note: It is not necessary to maintain entries for all combinations of VIM

document status, SAP status, and previous external status. However, you
can define default settings by using the empty value for the fields
Document Status, SAP Status and PrevStat (see the examples in this
section).
The most specific mapping is chosen first. If no exact match is found, the
next less specific mapping is taken and so on.
6. In the Assign External Status to VIM Document Status screen, maintain status
mappings for Supplier Self Service, using the following parameters:
Document Status
Enter the VIM document status.
Example: 00 (Created)
SAP Status
The status of the SAP invoice is not relevant for the Supplier Self Service
component.
PrevStat
Previous External Invoice Status
Enter the artificial key for this previous external invoice status.
VIM070500-03-CGD-EN-1
22.5. Configuring the Layout
Supplier Self Service determines an invoice status for posted invoices: PA for
paid, PP for partially paid.
ExtStatID
Enter the artificial key for the new status that should be given to Supplier
Self Service.
22.5 Configuring the Layout

Regarding the layout, you must configure the following settings:
• Fields that are shown in the web user interface
• Fields that are shown on the user interface, dependent on the user
• Texts for headers
22.5.1 Defining Fields

In this step, you configure fields to be displayed on the user interface of Supplier
Self Service. You can only configure fields of structure /OPT/W_3S_OUT_ST and /
OPT/W_3S_PYMNT_OUT_ST. For structure /OPT/WT_3S_VALUE, only fields EBELN and
LFSNR (related list fields of table /OPT/VIM_1PO_DN) are supported.
To define fields for the user interface:

Layout > Field Definition.
2. In the Supplier Self Service - Possible Fields to be shown in WebUI screen,

define fields that shall be shown in the user interface, using the following
parameters:
Table
Source table for the displayed field
Field name
Name of the displayed field. The name cannot be extended dynamically.
Field Description
Enter text that is shown on the user interface.
Output Length
Enter the length of the field on the user interface.
VIM070500-03-CGD-EN-1
22.5.2 Defining User Dependent Fields

In this step, you configure which fields are shown on the user interface, based on
users. For the lean variant, the DEFAULT entry is chosen. For the full variant, you can
configure individual layouts for specific users, or the DEFAULT is chosen.
To define user dependent fields:

Layout > User Dependent Field Settings.
2. In the Supplier Self Service - Field Configuration per User screen, define fields
that are shown in the user interface dependent on the user, using the following
parameters:
UserID
User for whom the settings are applied
Table
Source table for the displayed field. As defined in the field definition; see
“Defining Fields” on page 587.
Field name
Name of the displayed field. The name cannot be extended dynamically. As
defined in the field definition; see “Defining Fields” on page 587.
Field Status
Specify the status of the field in the user interface: Click Display or Hide in
the list.
Tip: The values Input and Required are not supported.
22.5.3 Defining Texts for Headers

In this step, you define the translatable texts for headers and other labels for the
Supplier Self Service user interface.
To define texts for headers in the user interface:

Layout > Maintain Texts for Headers.
2. In the Supplier Self Service - Output Texts screen, define texts for headers,
Property
User interface related value. It cannot be changed or extended.
VIM070500-03-CGD-EN-1
22.6. Configuring Company Code Settings
Description
Enter text that will be shown in user dependent language.
22.6 Configuring Company Code Settings

Regarding company code settings, you must perform the following configuration.
• Company code definition
• Company code mapping
22.6.1 Defining Company Codes

In this step, you define the company codes that you want to show in the Supplier
Self Service component. Company Code Text and Additional Information are
language dependent. You must configure them for possible log-on languages of the
user.
Note: In a multiple backend environment, you must have unique company

code IDs within all your systems.
To define company codes for Supplier Self Service:

Company Codes > Company Code Definition.
2. In the Supplier Self Service - Company Codes Definition screen, define
company codes, using the following parameters.
Logical System
On the satellite system, configure your logical system. On a central system
within a multiple backend scenario for the Supplier Self Service application,
you must configure all mappings of all relevant systems where data is
collected, or the corresponding aggregation group of Central Reporting
needs to create related entries. For more information, see section 5.8
Company Code ID
Unique company code ID
Company Code Text
Enter text that is shown on the user interface for this company code.
Additional Information
Enter additional text that is shown on the user interface for this company
code, for example the address.
Document Date Required, Vendor Name Required
For searches on the lean variant, define which values are required. Amount
and Invoice Reference Number are always required.
VIM070500-03-CGD-EN-1
Active
Select this check box to activate the company code for the Supplier Self
Service component.
22.6.2 Mapping Company Codes

In this step, you map the company code IDs that you have defined in “Defining
Company Codes” on page 589 to the existing company codes from the master data.
To map your defined company codes to master data company codes:

Company Codes > Company Code Mapping.
2. In the Supplier Self Service - Company Codes Mapping screen, map company
codes, using the following parameters.
Logical System
Company Code
Company code from the master data
Company Code ID
Your defined company code ID
22.7 Configuring the Supplier Settings

Regarding supplier settings, you must perform the following configuration.
• Supplier definition
• Supplier mapping
VIM070500-03-CGD-EN-1
22.7. Configuring the Supplier Settings
22.7.1 Defining Suppliers

In this step, you define the suppliers that you want to show in the Supplier Self
Service component.
To define suppliers for Supplier Self Service:

Suppliers > Supplier Definition.
2. In the Supplier Self Service - Supplier Definition screen, define suppliers,
using the following parameters.
Logical System
Supplier ID
Unique supplier ID
Name
Enter text that is shown on the user interface for this supplier.
Email Address
Enter the email address of the supplier.
Active
Select this check box to activate the supplier for the Supplier Self Service
component.
22.7.2 Mapping Suppliers

In this step, you map the supplier IDs that you have defined in “Defining Suppliers”
on page 591 to the existing vendors from the master data.
To map your defined suppliers to master data vendors:

Suppliers > Supplier Mapping.
2. In the Supplier Self Service - Supplier Mapping screen, map suppliers, using
the following parameters.
Logical System
VIM070500-03-CGD-EN-1
Vendor
Vendor from the master data
Supplier ID
Your defined supplier ID
22.8 Configuring Gateway Host and Application

Parameters
This configuration is intended only for the Supplier Self Service On-Premise solution
for the lean variant.
You must configure all the allowed Gateway-related and application parameters to
run the Supplier Self Service On-Premise solution smoothly on supported browsers.
Therefore, you configure the fields of the /OPT/WT_3S_CONF maintenance table.
To configure field data:

Application Configuration > Gateway and Application Configuration.
2. In the 3S Gateway and Application Configuration Overview screen, click New

Entries.
VIM070500-03-CGD-EN-1
22.8. Configuring Gateway Host and Application Parameters
3. Configure the fields, using the following parameters.
APPNAME
Application Name in read-only-mode. You cannot modify it. This is an
optional field, meant for future usage of the product.
PROTOCOL
SAP NetWeaver Gateway Hosted Server Protocol. Enter HTTP or HTTPS.
HOST
SAP NetWeaver Gateway host. Enter a valid host with domain.
PORT
SAP NetWeaver Gateway port. Enter a valid port.
LEANACTIVE
Enter default value TRUE.
HEADERIMGPATH
Enter default value
RESOURCES/HEADERBAR_VENDOR_INVOICE_MANAGEMENT.PNG.
Note: You can customize this header image. Replace it with a valid
PNG file under the MIMES > resources path of the BSP application,
which is available in the SAP Gateway server.
SHOWHEADER
SHOWFOOTER
VIM070500-03-CGD-EN-1
Chapter 23
Integration with the Ariba Network
Ariba, Inc, founded in 1996, is the leading provider of collaborative business

commerce solutions. The Ariba Network is a global business commerce network,
where companies can collaborate with any other when buying, selling, or managing
cash.
VIM can be integrated with the Ariba Network on the buyer side. In this scenario,
suppliers create invoices within the Ariba Network. The invoices are sent to the SAP
ERP system of the buyer. The buyer processes all incoming invoices within VIM.
Besides local invoice channels (email, or scan, or OCR), the buyer is connected with
the Ariba Network and receives invoices of his suppliers from this channel.
Ariba can be integrated in different ways within the SAP Business Suite.
• On the one hand, an integration with the SAP NetWeaver Process Integration
(PI) in combination with the Ariba PI adapter is possible. Technically, the
invoices are then sent in IDoc format (INVOIC02) to the SAP ERP system of the
buyer.
• On the other hand, it is possible to connect Ariba with the new SAP add-on Ariba
Network Integration for SAP Business Suite. The add-on is built based on web
service technology and can be connected to Ariba Network either direct or
mediated via PI or other middleware. Technically, the invoices are sent in cXML
format. For technical details, see the SAP Service Marketplace.
VIM integration The standard business application (IDOC integration or Ariba SAP add-on
integration) posts or parks the invoices automatically on the SAP ERP backend
system without the possibility to handle exceptions within a workflow. With the
integration of VIM, the DP workflow starts and VIM is the single point of access for
all invoices. VIM processes exceptions, both for invoices received electronically or by
paper. VIM controls the process for the automated reconciliation and posting.
Invoice status During the invoice process, the Ariba Network retrieves status information of the
invoice process in the SAP ERP system. The Ariba Network updates the invoice
status on the network. This enables vendors to see the processing status of their
invoices on the Ariba Network. For details of updating the invoice status on the
Ariba Network for VIM, see “Outbound Processing (StatusUpdate)” on page 605.
VIM070500-03-CGD-EN-1
Chapter 23 Integration with the Ariba Network
23.1 Integrating Ariba SAP Business Suite Adapter

SAP delivers a new add-on “Ariba Network Integration for SAP Business Suite” to
integrate Ariba with different scenarios in the SAP Business Suite. VIM provides an
input channel for the Ariba Network Integration for SAP Business Suite and
provides integration scenarios for invoice processing.
• Processing of incoming invoices in the DP process (various scenarios):
• Standard Invoice (operation = new in cXML)

• Invoice cancellation (operation = delete in cXML)
• Line level credit memo
• Non PO invoices
• Header level invoices
• Header level credit memos and debit memos
• Archiving of different documents:
• cXML InvoiceDetailRequest message

• PDF representation of cXML invoice and additional attachments
• Invoice Status:
• Update of invoice status according to VIM processing
You find details about installation and configuration of the SAP add-on Ariba
Network Integration for SAP Business Suite 1.0 on the SAP Service Marketplace. For
relevant prerequisites, see part XII “Vendor Invoice Management ARIBA Integration
Component Installation” in OpenText Vendor Invoice Management for SAP Solutions -
Installation Guide (VIM-IGD).
VIM070500-03-CGD-EN-1
23.1. Integrating Ariba SAP Business Suite Adapter
23.1.1 Configuring Inbound Processing (InvoiceDetailRequest)

The following sections describe configuration and functionality of the inbound
processing.
about how to configure document registration for custom registration and document
handler, see section 4.4.2.5 “Customizing a custom registration type” in OpenText
To activate the Ariba processing for Business Center Inbound Configuration, you
must activate the BC_INBOUND Z constant.
23.1.1.1 Activating the Inbound Processing

You must activate the VIM integration of the inbound processing with the
corresponding BAdI. You also must maintain the inbound processing for the
corresponding network.
To activate the processing:
1. Run the SPRO transaction and navigate to Integration with Other mySAP.com
Components > SAP Business Suite Integration Component for Ariba >
Application Specific Settings > SAP ERP Integration Component for Ariba >
Business Add-Ins (BAdIs) > BAdI: Inbound Mapping.
2. Make sure that the BAdI implementation /OPT/EH_E_ARB_BADI_INB_MAP is

activated.
VIM070500-03-CGD-EN-1
3. To maintain the inbound processing for the corresponding network, run the /
OPT/SPRO transaction and navigate to Document Processing Configuration >
Processing for Supplier Network.
4. Make sure that the inbound processing default class /OPT/CL_E_ARB_INBOUND

is configured correctly for network AN.
23.1.1.2 Integrating the Processing

The inbound invoice processing happens in two main stages:
1. Processing of inbound cXML messages and storing them in form of key and
value according to the Ariba specific mapping. For more information, see
“Mapping Fields (Ariba Specific Mapping)” on page 599).
2. VIM Inbound Document Handling (IDH) processing with Ariba specific IDH
mapping. At this step, invoice attachments are archived, and a VIM DP
document and corresponding DP workflow is created. See also “Mapping Fields
(IDH Mapping)” on page 600.
To process the inbound cXML messages in case of direct connectivity, the program
ARBFND_FETCH_CXML_MESSAGES must be scheduled to run periodically
(ARBFND_FETCH_CXML_MESSAGES_NEW for SAP components ARBERP SP2 and higher).
In case of mediated connectivity, the interface will be called automatically by PI. You
can monitor errors on this step with standard SAP tools like Application log
(transaction SLG1, to be started with the object ARIBA_INTEGRATION.
You can monitor VIM IDH processing in transaction /OPT/VIM_7AX8. The

processing itself requires the IDH Trigger program /OPT/VIM_IDH_TRIGGER to run
in a periodic job.
The processing of invoice cancellation is described in “Processing Invoice

Cancellations” on page 602.
VIM070500-03-CGD-EN-1
23.1.1.3 Mapping Fields (Ariba Specific Mapping)

The standard inbound Ariba interface converts cXML data into an ABAP structure
of type ARBERP_XINVC_S_CXML. The first mapping is performed referring to that
structure. The goal of the first mapping is to convert the data stored at several
structure levels and including internal tables into the flat key and value list
corresponding to the header and items of the invoice.
Document Processing Configuration > General Configuration > Incoming
Document Processing > Ariba Data Mapping.
The mapping is conceptually similar to the IDoc mapping. It points to the specific
fields in the input structure, allowing to choose the starting point in the structure
and, in case a list of values is provided, search for specific lines of internal tables by
the use of qualifiers.
The following fields can be maintained in each mapping entry:
Path Type
Select the path type:
Header
The mapping path to the field begins at request-invoice_detail_request
of the structure ARBERP_XINVC_S_CXML.
Item common data
The mapping path to the field begins at request-
invoice_detail_request-invoice_detail_order-
invoice_detail_order_info.
Standard item (stock item)

invoice_detail_item.
Service item
invoice_detail_service_item.
Field path
Enter the field path. This setting denotes the further path to the field, starting
where the shortcut set in path type ends. The path is traversed step by step to
find the fields. If there is any internal table used in the path, either its first line is
read, or the qualifier is used to find the line. You can use qualifiers only if the
table is the last element of the path.
Qualifier Field Name
Enter the field name that is used to search lines of internal tables. If the value # is
entered, the qualifier value must be numeric, containing the index of the table
line to read.
VIM070500-03-CGD-EN-1
Qualifier Field Value

Enter the value that will be searched for in the field set in the Qualifier Field
Name to find the needed table line. It can contain a line index if # is used instead
of the qualifier field name.
Field Name
Enter the name of the source field to map.
Document Field Name

Enter the name of the target field to map.
Note: This is not yet the name of DP document fields but the field name to
be used as a source field in the second (IDH) mapping.
Field Mapping Type

Select V for the value to be assigned without any conversions. Alternatively, you
can use a function module (mapping type = M).
Value
Enter the name of the function module to be called for field value conversion.
For header fields, the function module /OPT/VIM_ARB_TEMPLATE_2 provides an
interface template.
For item fields, the function module /OPT/VIM_ARB_TEMPLATE_3 provides the
interface template.
Store Original Value

Select this check box to permanently store the original unconverted values that
were provided in the cXML message. The values can be used later in the VIM
process. For example, they can be shown in the DP indexing screen.
Note: This requires a custom extension.
The values are stored in the /OPT/VIM_IDH_EXT table per IDH registration ID
and mapping field. You can use the /OPT/CT_IDH_HEAD table for lookups of
registration IDs.
23.1.1.4 Mapping Fields (IDH Mapping)

This mapping converts the key and value list created in the first mapping into the
target fields of a DP document. The mapping ID used for the Ariba inbound
interface is ARIBA. For details about the maintenance of this mapping, see
“Maintaining the VIM Field Mapping” on page 101.
VIM070500-03-CGD-EN-1
23.1.1.5 Archiving Invoice Image and Attachments

The invoice PDF file generated by the Ariba Network, additional attached files, and
also the cXML message itself are archived through SAP ArchiveLink. The main
invoice document is chosen depending on the configuration. It is shown later in the
DP dashboard. Other files can be viewed through the Object Services menu.
The selection of the main invoice document is controlled by the external profile
settings in the channel settings for the ARIBA channel. There must be exactly one
entry provided in the external profiles list. If this entry has set the PDF document
class, the PDF file is chosen as the main document. If the XML document class is set,
the cXML message itself is saved as an XML file and is used as the main document.
The archiving document type for the main document is set according to the value in
the external profile.
The archiving document type for other documents is read from the VIM constant
table, the constant 005/ADDL_DOCS_AR_OBJECT.
Note: This setting is common for all Incoming Document Handling processes.
In the following example, the invoice PDF file is set as the main invoice document.
This setting is delivered as standard configuration:
23.1.1.6 Handling Errors

You can monitor errors happening in the inbound SOAP interface in the
SXI_MONITOR transaction. When needed, you can restart processing.
Application log The first (ARIBA specific) mapping is run by the program
ARBFND_FETCH_CXML_MESSAGES / ARBFND_FETCH_CXML_MESSAGES_NEW (for direct
connectivity, or by the PI in case of mediated connectivity) . You can verify the
results of the processing in the application log, transaction SLG1, to be started with
object ARIBA_INTEGRATION.
Error types In case of non-recoverable errors, like missing configuration, the processing aborts at
this step. If you are using custom mapping functions, return a message of type A in
the messages return table to abort the processing. Messages of type E (error) do not
stop the processing but allow the errors to be verified on later DP processing steps.
VIM070500-03-CGD-EN-1
In case of non-fatal errors happening during the data mapping, the processing will
continue. The error messages are stored for later review in the DP process.
Process type To be able to review the messages, enable the new DP process type 403. This process
403 type should be normally configured to be one of the first processes checked for
relevant DP document types. For process type determination, use the function
module /OPT/VIM_DETERMINE_PROC_IDHERR.
When using the process type 403, you must add the process option 2025 (Confirm
errors) to the options list for relevant roles. This new option allows to confirm the
errors in the IDH document mapping and lets the DP processing continue to run.
For details about process type and process option configuration, see “Defining the
Process Type Determination Sequence” on page 143 and “Configuring DP Process
Options” on page 204.
When the DP workflow stops on the process type 403, you can use the Display
Errors button in the DP dashboard to review the errors happened during the data
mapping.
23.1.1.7 Processing Invoice Cancellations

When a vendor has decided to cancel an invoice, a cXML cancellation message is
sent from Ariba Network. The processing is done with the program
ARBFND_FETCH_CXML_MESSAGES / ARBFND_FETCH_CXML_MESSAGES_NEW (for direct
connectivity, or by the PI in case of mediated connectivity). In case of cancellations,
no mapping is involved and the original IDH inbound document is marked for
cancellation.
The cancellation itself is implemented in the program /

OPT/VIM_ARB_CANCELLATIONS that must be scheduled to run periodically. The
program can also be run in dialog mode, as described in the following.
To process Ariba cancellations:
1. Run the /OPT/VIM_ARB_CANCEL transaction.

2. In the Process ARIBA Cancellations screen, configure the cancellation
processing, using the following parameters:
Payload ID
Enter the payload ID of the original invoice cXML message
Document ID
Enter the DP document ID
Registration ID
Enter the IDH document ID
Reversal Reason
Enter the default reversal reason to use when cancelling SAP documents.
If you do not provide a value, the program uses the reversal reason 01
(Reversal in current period). If 01 is not maintained in the SAP ERP
VIM070500-03-CGD-EN-1
system, it will try to use reversal reason 03 (Actual reversal in current

period).
If the corresponding DP document is still in the DP processing, it is obsoleted.

Relevant DP and approval workflows are stopped by the cancellation program. If
the DP document already has corresponding SAP documents, those SAP documents
will be deleted (in case of parked invoices) or cancelled (in case of posted invoices).
Any existing Invoice Exceptions of the Approval workflows for the SAP document
are stopped. The results are reflected in VIM reporting, like VIM Analytics.
The cancellation program tries to cancel documents and stop workflows regardless
whether other steps succeed. If any step fails while other steps succeed (for example
document is obsolete but workflow could not be stopped by some reason), the failed
steps will be retried on the next program run.
23.1.2 Configuring Outbound Processing

(StatusUpdateRequest)
The following configuration activities are needed to configure the outbound
processing.
23.1.2.1 Activating the Output Processing

You must activate the VIM integration of the output processing with the
corresponding BAdI. You also must maintain the outbound processing for the
corresponding network.
To activate the integration of the output processing:
1. Run the SPRO transaction and navigate to Integration with Other mySAP.com
Components > SAP Business Suite Integration Component for Ariba >
Application Specific Settings > SAP ERP Integration Component for Ariba >
Business Add-Ins (BAdIs) > BAdI: Outbound Mapping.
VIM070500-03-CGD-EN-1
2. In the BAdI Implementations dialog box, make sure that the BAdI
implementation /OPT/EH_E_ARB_BADI_OUTB_MAP is activated.
3. To maintain the outbound processing for the corresponding network, run the /
OPT/SPRO transaction and navigate to Document Processing Configuration >
Processing for Supplier Network.
4. In the Define Supplier Networks screen, make sure that the outbound
processing default class /OPT/CL_E_ARB_OUTBOUND is configured correctly for
network AN.
23.1.2.2 Mapping of the VIM Status to the Ariba Status

For a detailed description, see “VIM Status Configuration” on page 606.
VIM070500-03-CGD-EN-1
23.2. Integrating the Ariba SAP NetWeaver Process Integration Adapter
23.2 Integrating the Ariba SAP NetWeaver Process

Integration Adapter
Ariba delivers an adapter based on the SAP NetWeaver Process Integration (PI) to
integrate Ariba within the SAP Business Suite. The adapter supports various
integration scenarios with different technology.
For the PI adapter, VIM provides an integration white paper which describes the
different integration options. The white paper is available for integration partners in
the Knowledge Center: https://knowledge.opentext.com/knowledge/cs.dll/
Overview/38761889.
23.2.1 Inbound Processing (InvoiceIDoc)

The configuration and necessary enhancements are described in the white paper
mentioned in “Integrating the Ariba SAP NetWeaver Process Integration Adapter”
on page 605.
23.2.2 Outbound Processing (StatusUpdate)

Ariba delivers a standard functionality to update the invoice status on the Ariba
Network. The following status codes are available:
Processing
Invoice in process
Reconciled
Invoice posted successfully
Paid
Invoice partially/fully paid
Canceled
Invoice canceled
VIM070500-03-CGD-EN-1
Rejected
Invoice not posted from IDoc
The standard function of the Ariba Network Adapter only tracks the status of
invoices after posting. With the integration of VIM, tracking must also cover
documents that have not yet been posted but are processed inside DP or a parking
workflow. Therefore, VIM delivers functionality to add VIM specific status
information to the status retrieval of the Ariba Network Adapter. This includes a
configuration to map the process status of a VIM invoice to the status codes that are
known in the Ariba Network. It also includes a program include to be called in a
customer exit of the Ariba Network Adapter.
Note: Currently only versions 12s2 and 11s2 of the Ariba Network Adapter are
supported.
23.2.2.1 VIM Status Configuration

The Ariba Network Adapter determines the invoice status for posted invoices. With
VIM, it is possible to overwrite the status of these invoices to ensure that VIM
specific status information can run in. Invoices that are not yet posted but are still
processed inside the DP or parking workflow are added. Therefore, two scenarios
exist: posted invoices and invoices still processed in VIM. For both scenarios, the
processing status of the VIM invoice needs to be mapped to the status codes that are
known in the Ariba Network.
To define the mapping of VIM status to Ariba status:
1. Run the /n/OPT/SPRO transaction and navigate to Document Processing

Maintain Processing for Supplier Network.
2. In the Define Supplier Networks screen, maintain an entry for the Ariba
Network, using the following parameters:
Netw
Enter a two-digit identifier for the external supplier network.
Default value: AN
Supplier Network
Enter the name of the external supplier network.
Default value: Ariba Network
VIM070500-03-CGD-EN-1
Class Name
Enter the name of the class containing the processing logic for the external
supplier network.
Default value: /OPT/CL_E_SUPPLIER_NETW_ARIBA
Note: If you want to overwrite the logic of class /

OPT/CL_E_SUPPLIER_NETW_ARIBA, you can derive a subclass of this
class and adjust it to your needs. Maintain your new class in the Class
Name field afterwards.
3. To define the status known in the Ariba Network, select the entry for the Ariba
Network and double-click Define External Status in the Dialog Structure.
4. In the Define External Status screen, maintain entries for all status codes
known in the Ariba Network, using the following parameters:
ExtStatID
Enter a two-digit, artificial key for the status of the external supplier
network.
Example: CA for the external status canceled.
External Status
External Invoice Status as known by the Network
Enter the invoice status as known by the external supplier network.
Example: canceled
Note: Ensure that the status code in the field External Status is exactly
the status code that is delivered by the Ariba Network. Pay attention
to lower and upper case.
External Status Description Long

Enter a description for the invoice status of the external supplier network.
Example: Invoice canceled
5. To map the process status of a VIM invoice to the status codes that are known in
the Ariba Network, double-click Assign External Status to VIM Document
Status in the Dialog Structure.
VIM070500-03-CGD-EN-1
The process status of a VIM invoice is a combination of the VIM document

status, the SAP document status and the previous status determined by the
external supplier network. A combination of these three status codes determines
the new external status code.
Note: It is not necessary to maintain entries for all combinations of VIM

document status, SAP status, and previous external status. However, you
can define default settings by using the empty value for the fields
Document Status, SAP Status and PrevStat (see the examples in this
section).
The most specific mapping is chosen first. If no exact match is found, the
next less specific mapping is taken and so on.
6. In the Assign External Status to VIM Document Status screen, maintain status
mappings for the Ariba Network, using the following parameters:
Document Status
Enter the VIM document status.
Example: 08 (Confirmed Duplicate)
SAP Status
Enter the status of the SAP invoice (if already existing).
PrevStat
Previous External Invoice Status
Enter the artificial key for this previous external invoice status.
The Ariba Network determines an invoice status for posted invoices.
ExtStatID
Enter the artificial key for the new status that should be given to the Ariba
Network.
Example 23-1: Mapping records
The following mapping records are maintained:
Record Document Doc. SAP Previous ExtStatID External External

number Status Status Status External Status Status
Descriptio Status Descriptio
n n
#1 PR processing Invoice in
process
#2 11 Awaiting PR processing Invoice in
Approval process
#3 11 Awaiting PR PR processing Invoice in
Approval process
VIM070500-03-CGD-EN-1
The Ariba Network has sent an invoice to the SAP ERP system. The invoice
was posted with a payment block and is now waiting for approval in the
VIM process (Posted Approval). The Ariba Network Adapter determines the
external status processing (PR) for this invoice. What mapping record will
be taken?
The VIM document status is 11 (Awaiting Approval), the previous external

status code is PR (processing). Because the mapping record #3 is the most
specific mapping, it will be taken for the determination of the new external
status code. If only the mapping records #1 and #2 were maintained,
mapping record #2 would be chosen. If only the mapping record #1 was
maintained, this mapping record would be chosen.
Example 23-2: Ariba Network status mapping 1
For a posted, paid invoice, the Ariba Network Adapter determines the status
paid. As VIM does not deliver any additional value regarding the status
information, the status should be kept as it is.
Document Status
<empty> (all VIM document statuses)
SAP Status
<empty> (all SAP document statuses)
PrevStat (Previous External Invoice Status)
PD (paid)
ExtStatID (External Invoice Status)

PD (paid)
The VIM invoice has the status Obsolete. An SAP invoice was not created.
The VIM invoice should be treated as a rejected invoice, that is an invoice
that was not “accepted” by the buyer or the buyer's system.
Document Status
08 (Obsolete)
SAP Status
<empty> (Because the invoice is not yet posted, the Ariba Network
Adapter will not provide a status.)
RJ (rejected)
VIM070500-03-CGD-EN-1
VIM knows a big variety of different document statuses. Invoices with status
Obsolete or Confirmed Duplicate should get the Ariba status rejected.
All others should get the Ariba status processing. It is possible to maintain
a default mapping for invoices:
Document Status
<empty> (all VIM document statuses)
SAP Status

<empty> (all Ariba network statuses)

PR (processing)
Additionally, it is required to maintain additional mapping records for

invoices that should not get the default status processing (see
Example 23-2, “Ariba Network status mapping 1” on page 609 and
Example 23-3, “Ariba Network status mapping 2” on page 609).
23.2.2.2 VIM Status Integration

Ariba provides a function (Z_ARIBA_INVOICE_STATUS_UPDATE) that reads relevant
status information for the posted documents that have been created by Ariba. VIM
delivers functionality to add VIM specific status information to these invoices.
Additionally, VIM adds invoices that are not yet posted but are still processed inside
the DP or parking workflow together with status information. To enable this
functionality, a VIM include needs to be integrated in an Ariba function module.
Note: Currently only the Ariba Network Adapter with Version 11s2 or 12s2 is
supported.
To integrate VIM status determination into the Ariba status update:
(for Ariba Network Adapter Version 11s2 on SAP NetWeaver 7.0 and higher)
2. Change function module Z_ARIBA_INVOICE_STATUS_UPDATE. For details, see

the following steps.
3. In the application toolbar, click Enhance .
VIM070500-03-CGD-EN-1
4. Fade in the implicit enhancement options: On the Edit menu, click

Enhancement Operations > Show Implicit Enhancement Options.
5. Navigate to the enhancement option at the end of the function module, that is
the enhancement option directly before the ENDFUNCTION instruction.
6. To create an implementation to this enhancement option, use the context menu.
7. Insert the following instructions.
INCLUDE /OPT/EI_ARIBA_INV_STATUS_11S2.
SORT invoice_status_info BY doc_date doc_time.
The program code should look like the following:
8. Activate the enhancement implementation.
To integrate VIM status determination into the Ariba status update:
(for Ariba Network Adapter Version 12s2)
2. Change function module Z_ARIBA_INVOICE_STATUS_EXT. For details, see the

following steps.
3. In the application toolbar, click Enhance .
4. Fade in the implicit enhancement options: On the Edit menu, click

Enhancement Operations > Show Implicit Enhancement Options.
5. Navigate to the enhancement option at the end of the function module.
6. To create an implementation to this enhancement option, use the context menu.
7. Insert the following instructions.
INCLUDE /OPT/EI_ARIBA_INV_STATUS_12S2.
The program code should look like the following:
VIM070500-03-CGD-EN-1
8. Activate the enhancement implementation.
VIM070500-03-CGD-EN-1
Chapter 24
SAP NetWeaver Business Warehouse Content
Reporting, analysis and interpretation of business data are crucial to preserve and
enhance the competitive edge of companies. They optimize processes and enable
companies to react quickly and in line with market needs. SAP NetWeaver Business
Warehouse (SAP NetWeaver BW) provides tools and functions that enable
companies to attain these goals. In SAP NetWeaver BW, you can integrate,
transform, and consolidate relevant business information from productive SAP
applications and external data sources. SAP NetWeaver BW provides you with a
high-performance infrastructure that helps you evaluate and interpret data. Decision
makers can make well-founded decisions and identify target-orientated activities on
the basis of the analyzed data.
With VIM 7.0 BW content, OpenText delivers preconfigured reporting and analysis
scenarios for SAP NetWeaver BW that are based on consistent metadata.
Note: VIM 7.0 BW content is also used for VIM 7.5.
The VIM BW content provides the relevant BW objects from extraction to analysis, in
an understandable, consistent model. The VIM BW content therefore provides you
with an efficient and cost-effective way to implement SAP NetWeaver BW for VIM
in your company.
The VIM 7.0 BW content focuses on VIM related process data. The key figures that
are available in the KPI Dashboard are either directly available or can be calculated
in the VIM 7.0 BW content also. This comprises the following key figures:
• Number of processed invoices

• Amount of processed invoices in invoice currency and in favorite currency
• FI amount of processed invoices in document currency and in local currency
• Number of exceptions
• Percentage of processed invoices with a certain exception class to all processed
invoices, for instance an exception free rate; this means the rate of “no real
exceptions” to all processed invoices
• Number of invoices processed with delay/on time
• Number of invoices approved with delay/on time
• Total processing time in days from the start of the VIM process to the end of the
VIM process
• Total approval time in days
VIM070500-03-CGD-EN-1
Chapter 24 SAP NetWeaver Business Warehouse Content
The VIM BW content delivered by OpenText can be used either directly or as a

template to be adapted to customer needs.
With VIM 7.0, BW content is delivered for SAP NetWeaver BW 7.0, SAP NetWeaver
BW 7.3, and OLTP systems with ECC 6.0. Technically, the VIM BW content
comprises DataSources together with the following components:
• Extractors
• InfoObjects
• DataStore Objects (DSO)
• InfoCubes
• MultiProviders
• BEx Query Variables
• Transformations
• InfoPackages
• DataTransfer Processes (DTP)
• Process Chains
For a comprehensive list of SAP NetWeaver BW components, see part IV “SAP

NetWeaver Business Warehouse Details” in OpenText Vendor Invoice Management for
SAP Solutions - Reference Guide (VIM-RGD). This list covers the following
components:
• InfoObjects
• DataSources
• DataStore Objects (DSOs)
• MultiProviders
24.1 OpenText VIM Layered Scalable Architecture

(LSA)
The VIM BW content has been designed following the OpenText VIM Layered
Scalable Architecture (LSA), founded on accepted Enterprise Data Warehouse
(EDW) principles. The OpenText VIM LSA is based on the SAP LSA.
The main topic of the LSA is a model with different layers. The model describes the
way of data from the data source to the final data target. You see the data flow in a
tiered way where the data is passing several layers, in which it is transformed,
harmonized, validated and corrected.
The VIM BW content is structured according to the LSA. That means, separate
folders (so called InfoAreas) have been created for VIM to logically group the BW
objects for all layers with physical data storage.
VIM070500-03-CGD-EN-1
24.1. OpenText VIM Layered Scalable Architecture (LSA)
Figure 24-1 shows an overview of the LSA model.
Figure 24-1: OpenText VIM Layered Scalable Architecture (LSA) model

overview
Data Acquisition Layer

This is the entry layer for the data flow into the BW. The data loaded from the
source systems is stored temporarily in the Persistent Staging Area (PSA) tables
as raw data (1:1) as in the source systems. The data is not meant to be saved for
building a history. The data is stored only for a determined time and is deleted
from the PSA tables after releasing a reporting period (making the loaded data
“officially” available for reporting).
Master data is loaded with full update from the source systems into the Data
Acquisition Layer. Transaction data is loaded as delta update with After Images
from the source system(s) into the Data Acquisition Layer.
Corporate Memory
The purpose of the Corporate Memory is to save raw data permanently for
history reasons to help recovery if needed.
The VIM 7.0 BW content provides a Write Optimized DataStore Object (DSO) for
every DataSource (master data and transaction data).
The VIM 7.0 BW content provides both a meta process chain that supplies data
to DSOs of the Corporate Memory and a meta process chain that does not
supply data to the Corporate Memory.
VIM070500-03-CGD-EN-1
Quality and Harmonization Layer

The purpose of this layer is data cleansing/data scrubbing and harmonization,
for example adding missing attributes, conversion of local to global keys, and
date conversion. Conversions do not solve specific reporting requirements but
they ensure that the Data Propagation Layer gets integrated and uniform data of
high quality. Application specific preparation is done in the Business
Transformation Layer.
This layer is a logical layer without physical data storage.
The VIM 7.0 BW content provides the following transformations (together with
DTPs):
• from the Data Acquisition Layer to the Data Propagation Layer and to the
Corporate Memory
• from the Corporate Memory to the Data Propagation Layer
For example, these transformations add missing attributes as company code

group and amount class; and they do time conversions.
Data Propagation Layer

In this layer, the prepared, harmonized, and consistent data is stored
permanently. This layer is not the basis for reporting but is the data basis to
provide data for analytical applications. Thus, the data is stored in a universally
valid form. The data is not yet converted to serve application specific
requirements.
The granularity of data is the same as in the source systems, for example, data
records contain the DP document number.
Ensuring consistency and correctness of data is more important in this layer
than performance. This is one reason for using Standard DSOs in this layer.
For texts and hierarchies, the direct update into InfoObjects is used. For attribute
master data, it is no longer state of the art to use the direct update into
InfoObjects. Thus, attribute master data is loaded into Standard DSOs within the
Data Propagation Layer. From the DSOs, the data is loaded into InfoObjects.
Business Transformation Layer

The purpose of this layer is to provide the data as needed by the Reporting
Layer, that means in an application specific view. If the reporting is based on
aggregated data, the aggregation is done here. Also application specific
calculations are done here. Records which are not needed for reporting are
filtered out here.
This layer is a logical layer without physical data storage.
The VIM 7.0 BW content provides transformations from the Data Propagation
Layer to the Reporting Layer together with DTPs.
Reporting Layer
Data in this layer is provided to serve the requirements of the reports best.
The VIM 7.0 BW content provides standard InfoCubes.
VIM070500-03-CGD-EN-1
24.1. OpenText VIM Layered Scalable Architecture (LSA)
Virtualization Layer
The Virtualization Layer is part of the Reporting Layer. The Virtualization Layer
makes it possible to exchange the physical data models (for example the
InfoCubes) on which the reports are based.
The VIM 7.0 BW content provides MultiProviders based on InfoCubes and on
DataStoreObjects. For more information, see part IV “SAP NetWeaver Business
Warehouse Details” in OpenText Vendor Invoice Management for SAP Solutions -
24.1.1 Overview of VIM BW Content Based on the LSA

Figure 24-2 provides an overview of the VIM BW objects and their transformations
for transaction data.
Figure 24-2: VIM BW objects overview
Figure 24-3 provides an example for the BW objects and their transformations for
master data with the help of the master data amount class.
VIM070500-03-CGD-EN-1
Figure 24-3: VIM BW Objects Overview Master Data
24.2 Installing VIM BW Content

To use the VIM BW content, you must perform the tasks described in the following
sections.
24.2.1 Preparing the VIM BW Content Activation

To prepare the VIM BW content activation:
1. OLTP system(s): Ensure that the following IMG activities of Central Reporting
are maintained properly:
a. On each OLTP VIM system (central and satellite), the VIM exception IDs
have been customized in the OpenText Configuration (/OPT/SPRO): Vendor
Invoice Management > Cross Component Configuration > Central
Reporting > Report Table Maintenance > Exception Definition and
Mapping > Exception Definition Maintenance and Exception Mapping
Maintenance. See “Activating Central Reporting Baseline and Maintaining
Reporting Tables” on page 671.
b. Create company code groups. See “Creating Company Code Groups”
on page 640.
VIM070500-03-CGD-EN-1
24.2. Installing VIM BW Content
Note: Company code groups can be loaded from a single OLTP

system only. If multiple OLTP systems are connected to the SAP
NetWeaver BW system, ensure that there is a leading OLTP system
that provides a complete list of all possible company code groups.
This leading OLTP system may correspond to the central system but
this is not mandatory.
c. On each OLTP VIM system (central and satellite), map company code
groups to company codes:
i. Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice

Management > Cross Component Configuration > Central Reporting
> KPI Dashboard > Company Code Groups > Company Code Groups
Mapping (BW).
ii. Map company code groups to company codes.

In contrast to the KPI Dashboard, one company code can be mapped to
one company code group only.
Note: Whereas company code groups need to be maintained

completely on a leading OLTP system, it is possible to load the
mapping of company code groups to company codes from
multiple OLTP systems.
d. Check time groups and maintain time group ranges. See “Time Groups”
on page 641.
Note: Time groups and time group ranges can be loaded from a
single OLTP system only. If there are multiple OLTP systems
connected to the SAP NetWeaver BW system, ensure that there is a
leading OLTP system that provides a complete list of all time groups
and time group ranges. This leading OLTP system may correspond to
the central system but this is not mandatory.
e. Check vendor groups and map them to vendors. See “Vendor Groups”
on page 643.
Note: Vendor groups can be loaded from a single OLTP system only.
If there are multiple OLTP systems connected to the SAP NetWeaver
BW system, ensure that there is a leading OLTP system that provides
a complete list of all possible vendor groups. This leading OLTP
system may correspond to the central system but this is not
VIM070500-03-CGD-EN-1
mandatory. In contrast to this, the vendor mapping is loaded from

every OLTP system and does not need to be maintained completely in
one leading OLTP system.
f. Check amount classes and maintain amount class ranges. See “Amount
Classes” on page 645.
Note: Amount classes and amount class ranges can be loaded from a
single OLTP system only. If there are multiple OLTP systems
connected to the SAP NetWeaver BW system, ensure that there is a
leading OLTP system that provides a complete list of all possible
amount classes and amount class ranges. This leading OLTP system
may correspond to the central system but this is not mandatory.
g. Check exception classes and map all existing exception IDs to them. See
“Exception Classes” on page 646.
Note: Exception classes and the mapping of exception IDs to

exception classes can be loaded from a single OLTP system only. If
there are multiple OLTP systems connected to the SAP NetWeaver
BW system, ensure that there is a leading OLTP system that provides
a complete list of all possible exception classes and the exception class
mapping. This leading OLTP system may correspond to the central
system but this is not mandatory.
h. On each OLTP VIM system, maintain the constants:
• for the favorite currency (constant name: FAVORITE_CURRENCY),

• for the currency conversion date (constant name:
CURR_CONVERSION_DATE), and
• for the currency conversion day (constant name:
CURR_CONVERSION_DAY)
in the OpenText Configuration (/OPT/SPRO): Vendor Invoice Management

> Cross Component Configuration > Central Reporting > KPI Dashboard
> Maintain KPI Constants. See “KPI Constants” on page 650.
Note: The texts of DP document types and the texts of channels can be
loaded from every OLTP system that is connected to the SAP NetWeaver
BW system.
2. SAP NetWeaver BW system: Ensure that the OLTP source systems have been
assigned to source system IDs in the Data Warehousing Workbench. If this is
not yet the case, maintain source system IDS for the OLTP systems:
a. In the Administrator Workbench, choose Tools > Assignment Source

System to Source System ID.
b. Click Create.
c. Enter the logical system name and a description. Confirm your entries.
d. In the Source System ID column, enter the ID name for the corresponding
source system.
VIM070500-03-CGD-EN-1
e. Save your entries.

3. SAP NetWeaver BW system: Ensure that the fiscal year variants are maintained
properly. To maintain the fiscal year variants, use the SAP IMG activity
Maintain fiscal year variant.
4. SAP NetWeaver BW system: Replicate metadata for OpenText Vendor Invoice
Management for your OLTP source system(s).
a. Start the Data Warehousing Workbench and navigate to the Modeling

view.
b. Go to DataSources.
c. Ensure that the correct OLTP system is chosen. If this is not the case, you
can choose it using the Choose Source System button in the upper left
corner of the toolbar.
d. If the application component OpenText Vendor Invoice Management is not
yet visible, click the button with the green arrow that is rightmost on the
toolbar (Replicate Tree Metadata).
e. Additionally, replicate the metadata for the OpenText Vendor Invoice
Management application components and the DataSources that are needed
for your purposes in the DataSource tree of the Data Warehousing
Workbench Modeling view. The following application components are
available for VIM:
• /OPT/VIM_MD comprising DataSources regarding master data

• /OPTVIM_DOC comprising DataSource regarding VIM documents
• /OPT/VIM_EXC comprising DataSource regarding VIM exceptions
Click Replicate Metadata in the context menu of the above VIM application
components in the DataSource tree of the Data Warehousing Workbench.
f. Click Replicate Metadata in the context menu of the VIM DataSources in
the DataSource tree of the Data Warehousing Workbench. Replicate
metadata only for those VIM DataSources that are needed for your
purposes.
Important
OpenText strongly recommends to launch the replication of
DataSources from the lowest level of application components (for
example from the application component /OPT/VIM_MD for VIM
Master Data). Otherwise the replication and activation of
DataSources may take a lot of time.
Notes
• If there are multiple OLTP systems connected to the SAP
NetWeaver BW system, select only the following DataSources for
the non-leading OLTP system(s) that are needed for your purposes:
• Document Header (/OPT/VIM_DPDOC_H_TRAN)
VIM070500-03-CGD-EN-1
• Exception (/OPT/VIM_EXC_TRAN)
• If you are asked in which format the DataSources should be created
in the BW system, ensure that the DataSources are created as RSDS
DataSources.
Note: The given steps for replicating the metadata describe one possible
way only. Other ways are possible and valid.
For alternative ways and further details about the replication of metadata,
see the SAP documentation regarding the replication of DataSources in
SAP NetWeaver 7.x.
24.2.2 Activating VIM BW Content

SAP NetWeaver BW system: Activate the VIM BW content that is needed for your
purposes within the Data Warehousing Workbench. The VIM BW content is
available below the InfoArea OpenText Vendor Invoice Management.
To activate VIM BW content:
1. Start the Data Warehousing Workbench and go to the BI Content view.

2. Gather objects for activation in Data Flow.
Use the grouping to specify how many objects must be gathered. OpenText
recommends the following steps:
a. Gather the objects for the In Data Flow Before grouping and activate these
objects.
b. Then gather the objects for the In Data Flow Afterwards grouping and
activate these objects.
c. Using the buttons in the right screen area, make the following settings for
gathering dependent objects:
Button Value
Collection Start Manual Collection
Mode
Grouping In Data Flow Before
d. To select the VIM 7.0 Content objects that you want to activate, choose
InfoObjects by InfoAreas or InfoProviders by InfoAreas and then the
OpenText Vendor Invoice Management InfoArea.
e. Select the InfoObjects or InfoProviders that you want to activate from the
VIM scenarios and drag them to the right screen area.
f. Click with the quick info text Gather Dependent Objects. The first
group of objects is listed in the right screen area.
3. Start activation.
In the Active Version Available column, the icon is displayed for any objects
that are already activated and that you do not need to activate again.
VIM070500-03-CGD-EN-1
a. In the Install column, select all objects that you want to activate. Any
objects for which the active and delivered versions differ can be identified
by the selection mark in the Match (X) or Copy column.
b. In the Match (X) or Copy column, select the objects that you want to
compare.
c. Click Apply > Install.
The Activation begins. As soon as the activation is complete, the data is
loaded automatically.
d. Repeat this procedure from Step 2 on page 622 (Gather Objects for
Activation in Data Flow) using the In Data Flow Afterwards grouping.
Recommended Order of Activation

There are a lot of different ways in which order to activate the objects of the VIM BW
content. The following is one possible way:
1. Select InfoObjects.
The characteristics and key figures of the VIM 7.0 BW content are organized in
InfoObject catalogs assigned to InfoAreas representing the different layers of
the LSA.
Select the InfoObject catalogs of the different LSA layers (Corporate Memory,
Data Propagation Layer, Reporting Layer) with the In Data Flow Before
option.
2. Install DataSources and data flow from source systems to Data Acquisition
Layer:
a. Select the leading OLTP source system and install the DataSources that are
needed for your purposes first with the In Data Flow Before option and
then with the In Data Flow After option. The object name of all VIM
DataSources starts with /OPT/.
Note: If you get a short dump with exception condition

“X_MESSAGE” in the ABAP program SAPLRRSI during the
activation, check SAP note 1637935.
b. If there are multiple OLTP systems connected to the SAP NetWeaver BW
system, select only the following DataSources of the non-leading OLTP
system(s) that are needed for your purposes:
• Company Code (/OPT/VIM_COCO_ATTR)

• Document Type (/OPT/VIM_DOCTY_TEXT)
• Document Header (/OPT/VIM_DPDOC_H_TRAN)
• Exception (/OPT/VIM_EXC_TRAN)
• Vendor (/OPT/VIM_VENDOR_ATTR).
First select with the In Data Flow Before option and then with the In Data
Flow After option.
VIM070500-03-CGD-EN-1
Note: The InfoProviders and the data flow between the InfoProviders are
installed with this step as well.
3. Select and activate query element variables.

When creating queries, variables may be interesting. You can use variables to
offer the end user the option to restrict the data to be displayed. For example,
the user may want to see VIM documents of some selected VIM document types
only. Thus, the VIM 7.0 BW content provides some variables that can be used in
queries to offer the user a selection regarding the variables. The names of all
VIM query element variables start with /OPT/.
Select and activate the query element variables that are needed for your
purposes with the Only Necessary Objects option.
4. Select the Meta Process Chains that are needed for your purposes with the In
Data Flow Before option. The object names of all the VIM process chains start
with /OPT/. You can use a filter on the object name to search for the VIM
process chains. The VIM BW content provides the following meta process
chains to be used directly or as a template to be adapted to customer needs:
Meta Process Chain for Delta Load of VIM Data w/o Corp. Mem. (technical
name: /OPT/VIM_ALL_01)
This meta process chain is used to upload master data and transaction data
from the leading OLTP system without storing data records in the
Corporate Memory and to further upload the data to the Reporting Layer,
that means to the InfoCubes.
Meta Process Chain for Delta Load of VIM Data with Corp. Mem. (technical
name: /OPT/VIM_ALL_02)
This meta process chain is used to upload master data and transaction data
from the leading OLTP system with additionally storing the data records in
the Corporate Memory and to further upload the data to the Reporting
Layer, that means to the InfoCubes.
Note: Both meta process chains are designed for a single OLTP system
only. If there are multiple OLTP systems connected to the SAP NetWeaver
BW system, the process chains need to be adapted for the non-leading
OLTP systems. In case of a non-leading OLTP system, the process chain
should restrict the master data to be loaded to the following:
• Company Code Mapping (without loading company code group texts)
• Vendor Group Mapping (without loading vendor group texts)
• Document type texts
VIM070500-03-CGD-EN-1
24.2.3 Configuring VIM BW Content After Activation

To configure VIM BW content after activation:
1. OLTP system: Ensure that the KPI Collection Report /OPT/VR_KPI_COLLECTION

is set up as a periodic job on each involved OLTP system. This report assembles
document and exception data that is needed for the BW extraction. Ensure that
the KPI Collection Report is run and finished before the BW extraction process
is started. For more information about the KPI Collection Report, see
“Collection Job” on page 630.
2. SAP NetWeaver BW system: Initialize the delta load of DP document headers
and exceptions by starting the InfoPackages /OPT/VIM_DPDOC_H_TRAN_INIT
and /OPTVIM_EXC_TRAN_INIT once for every OLTP system. Both InfoPackages
initialize the delta process including a first data transfer.
Note: For further details about InfoPackages, refer to the SAP

documentation.
3. SAP NetWeaver BW system: Schedule a meta process chain to upload VIM data
to the BW periodically.
4. SAP NetWeaver BW system: Trigger the scheduled meta process chain by an

event. You can use report /OPT/VIM_TRIGGER_PC_START to trigger the events
for the meta process chains that are delivered with the VIM 7.0 BW content. You
can set up a periodic batch job for this report. For details, see section 5.10
“Scheduling Batch Jobs for SAP NetWeaver BW” in OpenText Vendor Invoice
5. SAP NetWeaver BW system: The VIM BW content reuses InfoObjects of the SAP
standard content, for example:
• the company code (technical name 0COMP_CODE)

• the vendor (technical name 0VENDOR)
• the purchasing organization (technical name 0PURCH_ORG)
• the purchasing group (technical name 0PUR_GROUP)
Ensure that all BW objects needed for the dataflow from the DataSources to
these InfoObjects are installed from the SAP NetWeaver BW content.
Additionally, ensure that the data for these InfoObjects is loaded. This includes
loading the data for the attributes of the above InfoObjects, for example the
country of a vendor.
VIM070500-03-CGD-EN-1
Chapter 25
KPI Dashboard
The “Key Performance Indicator” Dashboard (KPI Dashboard) is a tool for managers
showing VIM related process data at a glance in graphical charts.
KPI KPIs are used for performance management. Organizations use KPIs to measure
their overall success or the success of a particular activity. For the KPI Dashboard,
the following KPIs have been implemented with several filters:
• Number of processed invoices

• Amount of processed invoices
• Number of occurrences of exception classes
• Exception free rate
• Number of invoices processed with delay
• Number of invoices approved with delay
For information about the user interface of the KPI Dashboard, see “Viewing Data in
Graphical Charts” in OpenText Vendor Invoice Management for SAP Solutions - User
Guide (VIM-UGD).
The KPI Dashboard section provides the following configuration aspects:
• “KPI Dashboard Definitions” on page 627

• “Periodic Jobs - Collection and Aggregation” on page 629
• “Authorizations” on page 637
• “Customizing Settings” on page 638
• “Troubleshooting” on page 658
25.1 KPI Dashboard Definitions

The KPI Dashboard shows monthly VIM data grouped by Channel ID and
Company Code Group.
Definitions for KPI1: Number of Processed Invoices
Processed invoices
Invoices where the VIM end timestamp is in the current period (month)
Number
How many invoices with end timestamp in the current period (month) have
been processed
VIM070500-03-CGD-EN-1
Chapter 25 KPI Dashboard
Definitions for KPI2: Amount of Processed Invoices

Processed invoices
Invoices where the VIM end timestamp is in the current period (month)
Amount
What is the total amount of invoices with end timestamp in the current
period (month) that have been processed
Definitions for KPI3: Number of Occurrences of Exception Classes
Exception
VIM invoice exception in the sense of “process step that requires manual
interference”
All exceptions of an invoice in the VIM process are collected and classified.
The corresponding exception classes are displayed in the period (month) in
which the invoice has the VIM end timestamp.
Exception Class
Group of invoice exceptions defined in the KPI customizing
Definitions for KPI4: Exceptions Free Rate
Exception Free
Some process steps requiring manual interference are considered to be “no
real exception”; therefore they are “exception free”. The exception free rate
reflects the rate of “no real exceptions” and the completely exception free
rate in comparison with the rate of “real exceptions”.
All exceptions of an invoice in the VIM process are collected, classified, and
taken into account for the exception free rate in the period (month) in which
the invoice has the VIM end timestamp.
Definitions for KPI5: Number of Invoices Processed with Delay
Invoices processed with delay

Invoices where the VIM end timestamp is in the current period (month) and
the processing number of days between start and end process timestamp is
greater than a certain threshold value for delay (see “Time Groups”
on page 641)
Definitions for KPI6: Number of Invoices Approved with Delay
Invoices approved with delay

Invoices where the VIM end timestamp is in the current period (month) and
the approval duration is greater than a certain threshold value for delay (see
“Time Groups” on page 641)
VIM070500-03-CGD-EN-1
25.2. Periodic Jobs - Collection and Aggregation
25.2 Periodic Jobs - Collection and Aggregation

To make data available in the KPI target tables, you must set up periodic jobs for
collection and aggregation.
Note: Before running periodic jobs, you must complete all customizing steps
for the KPI Dashboard. See “Customizing Settings” on page 638.
The KPI Dashboard architecture overview shows that different levels of data
preparation are necessary to provide correct KPI data.
Figure 25-1: KPI Dashboard architecture overview
Level 1a
The VIM logging continuously writes data to special Log Tables and Index Data
Tables in the Central System and the Satellite Systems (if involved). The
activation of the KPI Dashboard BC set starts the logging mechanism.
Level 1b
The KPI Data Collection assembles document and exception data from the
logging and saves them in the KPI Source Tables. A periodic collection job is
required on each involved system to fill the KPI Source Tables.
Level 2
The KPI Aggregation selects data from the KPI Source Tables (in different logical
systems if required), aggregates the data, transforms it and saves the data in the
KPI Target Tables. A periodic aggregation job is required only in the Central
System (or Single System) to fill the KPI Target Tables.
VIM070500-03-CGD-EN-1
Level 3
The Web Dynpro uses the KPI Target Tables for visualization in the Web
Frontend.
KPI Source Tables and KPI Target Tables can always be refilled from the logging
tables.
25.2.1 Collection Job

Prerequisite for the Collection Job
On each VIM system (central and satellite), the VIM exception IDs have been
customized in the OpenText Configuration: Vendor Invoice Management > Cross
Component Configuration > Central Reporting > Report Table Maintenance >
Exception Definition and Mapping > Exception Definition Maintenance and
Exception Mapping Maintenance. See “Activating Central Reporting Baseline and
Maintaining Reporting Tables” on page 671.
Collection Job - Report /OPT/VR_KPI_COLLECTION

Run the /OPT/VR_KPI_COLLECTION program.
Manual Run
Run frequency
Ad hoc / on demand
Business background
Ad hoc reporting / short term KPI analysis for a certain period of time
Execution
Manually in dialog or background
Parameter settings
• Process start date from (required)
• Process start date to (optional)
VIM070500-03-CGD-EN-1
• Delta mode check box cleared
If you want to load just a special period of time for the KPI Dashboard, you can use
the KPI collection report on demand manually. All processes which have been
started and also finished within the chosen process start interval are included in the
resulting collection output and stored to the KPI source data tables. From there, the
KPI aggregation report picks up the data and writes it to the KPI target data tables
as data basis for the Web Frontend.
To run the KPI collection report in test mode, select Test mode. This setting will
display the collected data in an ALV grid before saving the result to the database.
Important
When using this ad hoc type of KPI data supply, you must completely clear
the KPI source and target data tables before. Otherwise, reloading just a
special period of time could probably result in inconsistent overall results
and interrupt the regular delta collection runs in a significant way.
Therefore, the following steps are required to fulfill short term ad hoc KPI
reporting requirements whenever needed:
1. Delete KPI target data tables using the report /

OPT/VR_KPI_DELETE_TARGET.
2. Delete KPI source data tables using the report /

OPT/VR_KPI_DELETE_SOURCE.
3. Collect KPI source data for the required special time period using the
KPI collection report /OPT/VR_KPI_COLLECTION
4. Aggregate the collected KPI source data and write it to the KPI target
data tables using the report /OPT/VR_A_AGGREGATION using aggregation
group KPI.
Regular Delta Run

Recommended run frequency
Daily
Business background
Ongoing KPI reporting
Execution
Planned background job
Parameter settings
• No Process start date selection allowed
• Delta mode check box selected
The “Start From” date is the timestamp of the last run. The “Start To” date is
the current timestamp.
VIM070500-03-CGD-EN-1
Test mode
Same processing, but the data is not written to the database, but shown in an
ALV Grid.
Configure the collection program as a job with a variant for the processing option
Delta mode.
When running the KPI collection in the regular delta mode, the report picks up all
processes which have been started and also finished after the last delta run. The
report stores the result to the KPI source data tables. From there, the KPI
aggregation report picks up the data that has been collected after the last
aggregation run and writes it to the KPI target data tables as data basis for the Web
Frontend.
The following steps are required to fulfill ongoing KPI reporting requirements:
1. Run the report /OPT/VR_KPI_COLLECTION in delta mode first.
2. Afterwards run the report /OPT/VR_A_AGGREGATION using aggregation group

KPI.
25.2.2 Aggregation Job

25.2.2.1 Prerequisites for the Aggregation Job
The Aggregation Infrastructure settings in the OpenText Configuration must be
customized, see the following screenshot.
VIM070500-03-CGD-EN-1
The aggregation job prerequisites Aggregation report groups on page 633,

Aggregation report target tables on page 634, and Maintain KPI Settings
on page 636 are only required if the corresponding BC Set has not been activated.
OpenText strongly recommends activating the delivered BC Set instead of doing the
single activities manually.
Back end systems

Maintain the character set for logical systems. See “Maintaining Logical Systems
for the Aggregation Report” on page 667.
Aggregation report groups

Enter KPI as an aggregation report group (ID and description).
VIM070500-03-CGD-EN-1
See “Central Reporting Infrastructure“ on page 663.
Aggregation report target tables

Add KPI entries to the aggregation report target table. See also “Central
Reporting Infrastructure“ on page 663.
The following entries are necessary; all with aggregation group KPI but with
different settings and an ascending sequence number:
VIM070500-03-CGD-EN-1
VIM070500-03-CGD-EN-1
Init source table

Select this check box to delete all source table entries after the aggregation
run. After the next collection run, only new data (delta to last run) is
available.
Init target table
OpenText advises against using this check box. It deletes all target table
entries before it fills them again (with all available data).
Note: For best performance, OpenText recommends that you select only
the Init source table check box for all KPI entries.
The check boxes may not be combined!
Maintain KPI Settings

Make the KPI related sub function modules available in Maintain KPI Settings.
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management
> Cross Component Configuration > Central Reporting >KPI Dashboard >
Maintain KPI Settings.
VIM070500-03-CGD-EN-1
25.3. Authorizations
Enter or check the entries for KPI 1 to 6.
25.2.2.2 Aggregation Job - Report /OPT/VR_A_AGGREGATION

The /OPT/VR_KPI_COLLECTION job runs daily in delta mode. Configure the report /
OPT/VR_A_AGGREGATION to run daily after the /OPT/VR_KPI_COLLECTION job, with a
variant for aggregation group KPI. See also “Running the Aggregation Report for
the CUST_PREFL Group” on page 669.
25.3 Authorizations
The access to the KPI Dashboard is limited to users that have a SAP user on the
central SAP ERP system.
Additionally, the authorization object S_DEVELOP with the following settings is

required:
The OpenText standard delivery restricts the user to see only the company code data
that he is authorized to access. The filter Company Code Group displays only
groups that contain at least one authorized company code. So, the ALL filter in
Company Code Group contains only the company code groups that the user is
authorized to access.
You can abolish this restriction and change the setting to: All users can see all
company code data. Therefore, change the value for constant DO_NOT_CHECK_BUKRS
to X. For details, see “Company Code Authority Check” on page 653.
Important
If the company code check for authorization is running, and different users
have different company code authorizations, they will see different KPI
Dashboard filters and data.
VIM070500-03-CGD-EN-1
25.4 Customizing Settings

25.4.1 Involving a Manager for Business Related KPI
Customizing
The KPI customizing does not only cover technical settings but, what is even more
important: it covers business aspects like the grouping of vendors, amounts or
exceptions. Once defined, the business aspects are used for the monthly data
aggregation and should not be changed afterwards. If you cannot avoid a change,
the aggregation for all previous months must be repeated. Otherwise, the dashboard
screen compares apples and oranges.
Therefore, OpenText highly recommends involving a manager in the definition of

the following customizing that is related to business aspects:
Company Code Grouping

Should company codes be grouped together? If yes: how?
Time Groups
Which number of days should be defined for processing/approval for “on
time” / “almost on time” / “delayed”?
Vendor Groups
Should SAP standard vendor grouping be used or KPI specific? Which vendors
in A/B/C?
Dashboard Currency
Which currency should be used to show invoice amounts on the Web Frontend?
Amount Classes
What is considered to be the range for small / medium / big?
Exception Class Mapping
Which Dashboard exception classes should be used? How should the VIM
exceptions be mapped to the classes?
Company Code Authority Check
Should the display of Dashboard data be limited to the SAP user access rights
for company codes (standard delivery)? Or should every Dashboard user see all
data? If the authority check is active, different users see different data.
Currency Conversion Date
Which conversion date should be used to convert foreign currency invoices: the
system date of the monthly aggregation run? Or the posting date of the
document? Or a fix date in the current year? If a fix date, which one (1st of
January)?
Filter Start Period
Which month-year is the earliest that can be selected in the Dashboard Filter
Time Range From? Be aware that only data is available for display for which the
VIM process has started after introducing the KPI Dashboard on the SAP ERP
system.
VIM070500-03-CGD-EN-1
25.4. Customizing Settings
25.4.2 Customizing Menu

You access the configuration of the KPI Dashboard by running the /OPT/SPRO
transaction and navigating to Vendor Invoice Management > Cross Component
Configuration > Central Reporting > KPI Dashboard.
Grouping A lot of customizing has to do with the grouping of data. The KPI Dashboard is not
the right tool to display a large range of values; for example, to show 20 different
company codes. The KPI Dashboard rather shows grouped data like company code
groups or vendor groups.
VIM070500-03-CGD-EN-1
25.4.3 Company Code Groups

The KPI Dashboard does not show data based on company code but on company
code groups. Therefore, you must create company code groups and map them to
company codes.
Important
You must define at least one company code group. Otherwise, the Web
Frontend of the KPI Dashboard cannot be viewed.
25.4.3.1 Creating Company Code Groups

If you have many different company codes, you should group them. The groups
should represent a certain grouping logic, for example geography or hierarchy.
To create company code groups:
1. In the OpenText Configuration (see “Customizing Menu” on page 639), open

Company Codes Groups Definition.
2. Create groups with a 4 character grouping ID and two descriptive fields (long,
short). Fill both description fields.
Note: Do not use special characters for the Short Description.
If you have between 1 and 20 different company codes that are relevant for the
KPI Dashboard, enter each company code as a company code group and fill the
description fields.
It is also possible to mix new company code groups with company code groups
that are identical with existing company codes.
The Flg: Disp. check box is for future use. It is not relevant now.
VIM070500-03-CGD-EN-1
25.4.3.2 Mapping Company Code Group to Company Code

After creating the company code groups (either new or identical to existing
company codes), you must map the company code groups to company codes.
To map company code groups to company codes:
1. In the OpenText Configuration (see “Customizing Menu” on page 639), open

Company Codes Groups Mapping.
2. Map company code groups to company codes.

One company code can be mapped to more than one company code group.
Important
If one company code is mapped to different company code groups, the
data displayed on the dashboard is not disjoint.
25.4.4 Time Groups

The time grouping refers to processing time and to approval time.
25.4.4.1 Checking Time Groups

OpenText delivers the following customizing with 2 time groups.
Important
Do not change the time groups.
Time group 1 is reserved for processing time.
Time group 2 is reserved for approval time.
In the OpenText Configuration (see “Customizing Menu” on page 639), open Time
Group Definition.
VIM070500-03-CGD-EN-1
You can customize the descriptive text to a certain extent:
• Special characters are not allowed in the Short Description.

• Maximum length of the Short Description text is 30 characters.
The descriptive text is used on the Web Dynpro.
25.4.4.2 Maintaining Time Group Ranges

OpenText delivers the following customizing for time group ranges.
In the OpenText Configuration (see “Customizing Menu” on page 639), open

Maintain Time Group Ranges.
The time types for processing / approval are the following:
• On time
• Acceptable (Almost on time)
• Delayed
Note: The text symbols &1 and &2 in the Short Description will be replaced
during runtime with the Days from and Days to values.
Time Group 1 represents processing time:
VIM070500-03-CGD-EN-1
Enter the maximum number of days for time group 1 and time type On time
(representing the invoices processed on time). In the example, all invoices with a
processing time less or equal 5 days are considered to be on time.
Enter the maximum number of days for time group 1 and time type Acceptable
(representing the invoices processed almost on time). In the example, all invoices
with a processing time more than 6 and less or equal 15 days are considered to be
almost on time.
Enter the minimum number of days for time group 1 and time type Delayed
(representing the invoices with delayed processing). In the example, all invoices
with a processing time more than or equal 16 days are considered to be delayed.
Time Group 2 represents approval time:
Enter the maximum number of days for time group 2 and time type On time
(representing the invoices approved on time). In the example, all invoices with an
approval time less or equal 2 days are considered to be on time.
Enter the maximum number of days for time group 2 and time type Acceptable
(representing the invoices approved almost on time). In the example, all invoices
with an approval time more than 2 and less or equal 4 days are considered to be
almost on time.
Enter the minimum number of days for time group 2 and time type Delayed
(representing the invoices with delayed approval). In the example, all invoices with
an approval time more than or equal 5 days are considered to be delayed.
25.4.5 Vendor Groups

The KPI Dashboard covers three vendor groups and one unclassified group.
Vendors are usually grouped by invoice volume.
25.4.5.1 Checking Vendor Groups

OpenText delivers the following vendor group customizing with 3 + 1 vendor
groups.
Note: Do not change the vendor groups.

Vendor Group Definition.
VIM070500-03-CGD-EN-1
You can customize the descriptive text to a certain extent:

• Special characters are not allowed in the Short Description.
• Maximum length of the Short Description text is 30 characters.
The descriptive text is used on the Web Dynpro.
25.4.5.2 Mapping Vendor Groups

If the SAP standard vendor grouping has been applied (table LFM1 has attribute
LFABC filled for most of the vendors), there is no need to do a KPI specific mapping.

Maintain KPI Constants, constant KPI_VENDOR_CLASS.
<Empty>
Use SAP standard LFM1 mapping (continue with next section)
X
Use KPI Dashboard specific mapping
If you want to use a KPI specific vendor grouping, set the constant value to X,
and fill the vendor mapping table, as shown in the following.

Vendor Mapping.
VIM070500-03-CGD-EN-1
Map vendors to vendor groups.
Vendors that are not mapped to vendor group A, B or C are automatically

considered to be unclassified. The Web Dynpro shows all 4 vendor groups if they
are filled.
25.4.6 Amount Classes

Invoices are grouped into 3 disjunctive invoice amount classes.
25.4.6.1 Checking Amount Classes

OpenText delivers an amount class customizing with 3 amount classes.
Note: Do not change the amount classes.

Amount Class Definition.
The text symbols &1 and &2 will be replaced during runtime with the From amount
and To amount values for the amount classes.
VIM070500-03-CGD-EN-1
25.4.6.2 Maintaining Amount Classes

Maintain Amount Classes.
OpenText delivers amount class maintenance customizing with the following

amount ranges:
Maintain the amounts for the respective amount classes.
The currency must be identical with the favorite currency in the KPI constants.

Maintain KPI Constants, constant FAVORITE_CURRENCY.
25.4.7 Exception Classes

Invoice exceptions are grouped in 5 different classes.
25.4.7.1 Checking Exception Classes

OpenText delivers an exception class customizing with 5 + 1 classes.

Exception Class Definition.
VIM070500-03-CGD-EN-1
Exception Class 1 is considered to be the critical exception that is shown on the

exception related KPI screen.
Note: If you change the texts, do not use special characters for the Short
Description.
25.4.7.2 Mapping Exception Classes

Prerequisite The VIM exception IDs have been customized in the OpenText Configuration:
Vendor Invoice Management > Cross Component Configuration > Central
Reporting > Report Table Maintenance > Exception Definition and Mapping >
Exception Definition Maintenance and Exception Mapping Maintenance. See
“Activating Central Reporting Baseline and Maintaining Reporting Tables”
on page 671.

Exception Class Mapping.
VIM070500-03-CGD-EN-1
Map all existing exception IDs to the 5 +1 exception classes.
Note: The values shown are only examples.
25.4.8 KPI Naming

OpenText delivers 6 KPI IDs with names.
Note: Do not change KPI IDs and names.

Maintain KPIs.
VIM070500-03-CGD-EN-1
25.4.9 KPI Settings

The KPI related sub function modules must be available in the KPI settings.

Maintain KPI Settings.
Check whether the following entries with Aggregation Group ID KPI and KPI
Group 1 are available:
• /OPT/KAGR_SUB_KPI1
• /OPT/KAGR_SUB_KPI2
• /OPT/KAGR_SUB_KPI3_TO_4
• /OPT/KAGR_SUB_KPI5_TO_6
If they are not available, add them.
VIM070500-03-CGD-EN-1
25.4.10 KPI Constants

The following constants have to be maintained:
25.4.10.1 Currency Conversion Date
The constant CURR_CONVERSION_DATE represents the way the currency conversion

date is used:
T
Use the current system date.
P
Use the posting date of the document.
F
Use a fix date for the current year.
If you enter F, it is necessary to enter a value for the constant
CURR_CONVERSION_DAY.
VIM070500-03-CGD-EN-1
25.4.10.2 Currency Conversion Day
The constant CURR_CONVERSION_DAY is only used if the constant

CURR_CONVERSION_DATE has been set to F. It has to be filled with month and day
(MMDD, for example 0631 for June, 31st) for the currency conversion of all data
aggregated in the current year.
25.4.10.3 KPI Dashboard Help URL
The constant DASHBOARD_HELP_URL contains the link to the KPI Dashboard Help
page. Store the help file in the SAP mime repository and use the whole directory
structure in the URL link.
If the field is empty, the help link is not shown on the web page.
VIM070500-03-CGD-EN-1
25.4.10.4 KPI Dashboard Help URL with Multi-language Support
The constant MULTI_LANGU_HELP_URL is delivered without value.
<Empty>
The default help link stored in constant DASHBOARD_HELP_URL is used.
X
The help link URL is changed to language specific setting:
<default help link without file extension> + "_" + sy-langu + <file extension>
Example: /SAP/PUBLIC/BC/UR/DOC/Help_E.html
Keep in mind to store all the language specific help files to the same repository
with restriction of the above naming convention.
25.4.10.5 KPI Dashboard Start URL
For the constant DASHBOARD_START_URL, enter a value according to your specific

environment with the following system parameters:
VIM070500-03-CGD-EN-1
<Protocol>://<SAP ERP system address>:<port>/

sap/bc/webdynpro/opt/vim_kpi_main
Example: http://op60vimd89.optura.local:
8000/sap/bc/webdynpro/opt/vim_kpi_main
This functionality applies for URLs that are up to 80 characters. For URLs with more
than 80 characters, you must maintain the constant value as FM:<CUSTOM FM>, where
FM: indicates that a function module is used, and <CUSTOM FM> indicates your
function module name. As a function module template, use /
OPT/DETERMINE_KPIURL_TEMPLATE.
If the application uses secure http (https) for communication, apply changes as
described in section 11.2 “Setting the Connection for the SAP Web Dynpro Service”
in OpenText Vendor Invoice Management for SAP Solutions - Installation Guide (VIM-
IGD).
25.4.10.6 Company Code Authority Check
The constant DO_NOT_CHECK_BUKRS is delivered without value. For each KPI

Dashboard user, the company code authorization is checked. Some data might not
be displayed to users.
<Empty>
Check for company code authorization.
X
Do not check for company code authorization. Show all data for all users.
VIM070500-03-CGD-EN-1
25.4.10.7 Favorite Currency
Enter the currency in which the amount of all invoices should be displayed. This is a
central constant also used during aggregation.
25.4.10.8 Filter Start Period
The constant FILTER_START_PERIOD represents the first month available in the

Dashboard Filter Time Range when the user clicks the From drop down list.
Important
It is absolutely necessary to enter the value with the YYYYMM notation.
Example: If the year is 2011, and the month is October; enter 201110
VIM070500-03-CGD-EN-1
25.4.10.9 Vendor Class
The constant KPI_VENDOR_CLASS represents the way vendors are classified in

vendor groups.
<Empty>
The standard SAP vendor grouping of table LFM1 is used.
X
You have to fill the KPI specific customizing vendor mapping. See “Mapping
Vendor Groups” on page 644.
25.4.11 KPI URL Parameters

The Web Dynpro requires the definition of several URL parameters.

Maintain URL Parameter.
SAP-CLIENT
Enter the client number of the SAP ERP system where the KPI Dashboard has
been installed and activated.
VIM070500-03-CGD-EN-1
SAP-EP-THEMEROOT
Enter the path from where the theme of the Web Dynpro application is taken (to
use MIME objects, such as pictures and style sheets for visualization). You can
change the parameter for using custom CI-style guides. Default value: OpenText
SAP-LANGUAGE
Only EN, DE, and FR are allowed at the moment.
SAP-SYSTEM-LOGIN-BASIC_AUTH
If you have sap-system-login-basic_auth=X in the URL, a session cookie is
created. That is the reason why you can still load the application without re-
authentication. If you have the IE Developer Toolbar, you can clear session
cookies and try again. It will ask for credentials then.
SHOW_BANNER
Enter Y to show banner images (default setting). To deactivate banners, set the
value to N.
25.4.12 KPI Header Text for Web Dynpro Download

The KPI field names are delivered with English titles and header texts. The header
short text is used for the KPI Dashboard download to Excel.

Maintain Header Text for KPI Download.
VIM070500-03-CGD-EN-1
25.4.13 KPI User Parameter

Every time the KPI Dashboard is opened, the filter has the following setting:
Time Range FROM

Current month/year minus a user specific number of months (user parameter /
OPT/VIM_KPI_MONTHS)
Time Range TO
Current month/year
Company Code Group

All
Channel
All
With the user parameter /OPT/VIM_KPI_MONTHS, you can set the KPI Dashboard
Time Range filter From. The value entered represents the number of months that
the KPI Dashboard goes into the past to collect data. The value must be a number
between 1 and 12. Other values are not allowed.
For users without this user parameter, the default value of 8 months is used.
Note: The KPI constant FILTER_START_PERIOD can be set to date that is higher
than the time range calculated as current month/year minus user specific
number of months. In this case, the value FILTER_START_PERIOD is used for
the initial display.
Example: FILTER_START_PERIOD is 201106 and the calculated Time Range FROM value
would be 201103. In this case, the initial display uses 201106.
25.4.14 Checking Channel IDs

Channels indicate where the invoices come from. The Channel IDs should have been
customized already in the General Configuration. See “Maintaining Channels”
on page 98.
In the OpenText Configuration, navigate to the menu path Vendor Invoice

Management > Document Processing Configuration > General Configuration >
Incoming Document Processing > Maintain Channels.
VIM070500-03-CGD-EN-1
Make sure that all relevant VIM import channels that you want to see in the KPI
Dashboard are included in the table.
Important
The Web Dynpro application of the KPI Dashboard can display a maximum
of 10 channels.
25.5 Troubleshooting
25.5.1 Problems with Excel Download
Users might have problems downloading the KPI data from the Dashboard to Excel.
In this case, change the browser’s internet security settings in the Downloads sub
tree as shown in the following screenshot:
VIM070500-03-CGD-EN-1
25.5. Troubleshooting
25.5.2 Communication Error on Accessing Web Dynpro Page

After successfully signing in to SAP NetWeaver Portal, users may get a
COMMUNICATION_ERROR when accessing to the Web Dynpro page.
In this case, check the settings of the RFC destination IGS_RFC_DEST (TCP/IP
connection) on the backend system. Set the Program ID to IGS.<SID>; where SID is
the System ID of the SAP ERP system.
Perform a Connection Test.
VIM070500-03-CGD-EN-1
If the connection is successful, users should be able to access the KPI Dashboard
using the Web Dynpro page.
VIM070500-03-CGD-EN-1
Chapter 26
Automation Report
26.1 Overview
The automation report is a tool that provides data about automated and manual
processing steps of VIM documents. For more information, see section 5 “Using the
Automation Report” in OpenText Vendor Invoice Management for SAP Solutions -
Important
Data for the automation report is based on change documents for object
class /OPT/VIM_IDXDAT, which is a completely new feature with VIM 7.0
SP2. Therefore, it is not possible to show automation data for documents that
have been processed in older VIM versions.
26.2 Periodic Jobs - ATM Collection Report

The ATM collection report fills the /OPT/VT_ATM_SRC table, which contains data
about automated and manual processing steps of VIM documents. The table
contents can be viewed and evaluated directly by standard SAP reports or custom
reports (for example based on SQVI).
The VIM program “automation report” allows you to view and export the table
contents.
To run the ATM collection report:
1. Run the /OPT/VR_ATM_COLLECTION program.
Run frequency
OpenText recommends that you run this report daily, in delta mode, in the
background.
2. Configure the following parameters for the ATM collection report:
Main selection fields

You can leave the selection fields Company Code and Document Id empty.
Processing options
Delta mode
To run the ATM collection report in delta mode, select this check box.
This is the default setting.
To run the ATM collection report in full mode, clear the check box. You
need the full mode only if the data structures have been changed. This
may be the case when a new VIM SP is installed.
VIM070500-03-CGD-EN-1
Chapter 26 Automation Report
Note: Review the Release Notes of the SP to confirm if a full mode

run is necessary.
Test mode
To run the ATM collection report in test mode, select this check box.
This setting will display the collected data in an ALV grid before saving
the result to the database.
VIM070500-03-CGD-EN-1
Chapter 27
Central Reporting Infrastructure
The Central Reporting infrastructure provides reporting across the landscape in

multiple backend systems. In single system scenarios, it also provides useful
reporting. It provides several reports that enable you to measure certain properties
of VIM documents and their work items, in order to optimize working with VIM. In
particular, the following reports are provided:
• Summary Report (see section 7 “Using the Summary Report” in OpenText Vendor
Invoice Management for SAP Solutions - Reference Guide (VIM-RGD))
• Central Audit Report (see section 8 “Using the Central Audit Report” in
OpenText Vendor Invoice Management for SAP Solutions - Reference Guide (VIM-
RGD))
• Key Process Analytics Report (see section 9 “Using the Key Process Analytics
Report” in OpenText Vendor Invoice Management for SAP Solutions - Reference Guide
(VIM-RGD))
• Exception Analysis Report (see section 10 “Using the Exception Analysis Report”
in OpenText Vendor Invoice Management for SAP Solutions - Reference Guide (VIM-
RGD))
• Productivity Report (see section 11 “Using the Productivity Report” in OpenText
Vendor Invoice Management for SAP Solutions - Reference Guide (VIM-RGD))
• Aging Report (see section 12 “Using the Aging Report” in OpenText Vendor
Invoice Management for SAP Solutions - Reference Guide (VIM-RGD))
Aggregation To ensure good performance for the reports in Central Reporting, the data used for
the reports must be aggregated and saved in Reporting Data Tables. To achieve this
goal, the data is prepared in several different activities:
1. The Collection Report, the User Master Report and the Text Master Report get master
data and transaction data from their original tables and save the data in the
Source Data Tables. See “Scheduling the Collection Report” on page 675 for
details.
2. The Aggregation Report selects data from the Source Data Tables (in different
logical systems, if required), aggregates, transforms and saves the data in the
Reporting Data Tables of the current system. See “Scheduling the Aggregation
Report” on page 681.
3. The reports in Central Reporting are end user reports based on the content of the
Reporting Data Tables.
Configuration To configure Central Reporting, you have to perform the following steps:
steps
1. Maintaining logical systems and System Landscape Directory (SLD)
2. Running the Aggregation Report for the CUST_PREFL group
VIM070500-03-CGD-EN-1
Chapter 27 Central Reporting Infrastructure
3. Creating variants of the Aggregation Report for each group
4. Maintaining report tables
5. Activating Central Reporting Baseline
6. Scheduling batch jobs for Central Reporting:
• Collection Report
• User Master Report
• Text Master Report
• Aggregation Report with variants for each aggregation group
Groups Data in Source Data Tables changes during the use of VIM. Therefore, the
aggregation of data to the Reporting Data Tables must run regularly. OpenText
strongly recommends scheduling batch jobs for this purpose. For different tables, the
necessary frequency to update will differ considerably. For example, the SAP
Vendors Table will change much less frequently than the Workitem Agents Table.
For this reason, several default groups, comprising specific tables, are set up for the
aggregation:
Groups beginning with OTH* are used by the Central Audit Report only. The other
groups are used by the other central reports.
CUST_PREFL
Comprises Roles and Exception Mapping. This group is used to prefill the
customizing tables for roles and exceptions (see “Activating Central Reporting
Baseline and Maintaining Reporting Tables” on page 671) to ease customizing.
TRANSACT
Comprises Document Header, Workitem, Workitem Activities, and Workitem
Agents. This group will have to be executed most frequently because its content
is changed most frequently.
MASTER
Comprises Company Codes, Vendors, and Document Types.
USER
Comprises Users and the assignment of users to organizational objects within
SAP Organizational Management.
KPI
Builds up the KPIs which are offered by the KPI Dashboard.
Scheduling the Aggregation Report for the KPI group is only required if you
want to use the KPI Dashboard. See “KPI Dashboard“ on page 627.
Scheduling the Aggregation Report for the following groups is only necessary in a
multiple backend system.
VIM070500-03-CGD-EN-1
OTH_MASTER
Recommended to run once. Depending on how frequently Parking Reasons,
Process Type Definitions and Blocking Reasons are maintained, schedule the job
accordingly.
OTH_DCHEAD
Recommended to run twice a day. The frequency can vary depending on
business needs. Group ID OTH_DCHEAD replicates the data from table /
OPT/VT_DOC_HEAD to the Central System. This table is useful for Central Audit
Report output.
OTH_VMHEAD
business needs. Group ID OTH_VMHEAD replicates the data from table /
OPT/VIM_1HEAD to the Central System. This data replication is useful for system
wide duplicate check for an incoming invoice.
OTH_AGENT
business needs. Group ID OTH_AGENT replicates the data from table /
OPT/VT_WI_AGENT to the Central System. This data replication is useful for
current agent display in the Central Audit Report.
Baseline To display the groups that are delivered with Baseline, run the /n/OPT/SPRO
groups transaction and navigate to Vendor Invoice Management > Cross Component
Configuration > Central Reporting > Aggregation Infrastructure > Aggregation
report groups.
Note: OpenText strongly recommends that you do not change the Baseline
groups.
VIM070500-03-CGD-EN-1
Target data To display the Baseline target data tables that will be filled by the Aggregation
tables Report, run the /n/OPT/SPRO transaction and navigate to Vendor Invoice
Management > Cross Component Configuration > Central Reporting >
Aggregation Infrastructure > Aggregation report target tables.
Target and source tables are displayed, depending on the Aggregation Group ID.
Note: OpenText strongly recommends that you do not change the Baseline
target data tables.
VIM070500-03-CGD-EN-1
27.1. Configuring the System Landscape Directory (SLD)
27.1 Configuring the System Landscape Directory

(SLD)
You can configure the System Landscape Directory (SLD) by running the /
N/OPT/VIM_SLD transaction.
For details, see section 3.4 “Working with the System Landscape Directory (SLD)” in
OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide (VIM-CCS).
Make sure the following is configured correctly:
Multiple backend landscape
1. Central system - All satellite systems are maintained with proper RFCs and
classifications. The own logical system for the Central system itself is configured
with classification Central and with RFC destination NONE for system
communication.
2. Satellite system - The Central System logical system name is maintained with
proper RFC and classification. The own logical system for the Satellite system
itself is configured with classification Satellite and with RFC destination NONE
for system communication.
Note: Collection Report, User Master Report, and Text Master Report always
run in all systems involved. The Aggregation Report runs only in the central
system.
Single system scenario
1. The concerned system is configured with no RFC destination and the

classification is either blank or Single system landscape.
Note: Collection Report, User Master Report, Text Master Report, and
Aggregation Report all run in the concerned system.
27.2 Maintaining Logical Systems for the Aggregation

Report
As a prerequisite, you must maintain the logical systems (local system and back end
systems) to be used in the Aggregation Report. You define logical systems in table /
OPT/VT_A_BKESYS, using the /OPT/VIM_ABE transaction:
To maintain logical systems for the Aggregation Report:
1. To display the Aggregation report: Back end systems screen, run the /
OPT/VIM_ABE transaction.
Alternatively, navigate to Vendor Invoice Management > Cross Component
Configuration > Central Reporting > Aggregation Infrastructure > Back end
systems
VIM070500-03-CGD-EN-1
2. Click New Entries to add a logical system.
Notes
• As table /OPT/VT_A_BKESYS is also used as a check table for other data,
you must insert an entry for the local system.
• Add all logical systems you want to use in the Aggregation Report.
3. Optional Define the encoding.
Note: The wrapper function on the logical system returns the source table
content as an XML stream to the central system, because it is not possible
to hand over internal tables as generic types in RFC. If the fields Character
set and Byte order remain blank, the system default will be used. In case
of XML conversion problems during execution of the Aggregation Report,
you can specify the encoding to be used in these fields.
In this case, define the encoding, using the following fields:
Character set
Enter the character set, for example UTF-8.
Byte order
Enter the byte order, for example 1 if the character set uses big endian byte
ordering.
Note: For character sets and byte orders supported by SAP, see the
SAP documentation.
If you are not sure about the correct settings for your system, try the following:
a. In the related back end system, call the SE37 transaction and execute
function module SYSTEM_CODEPAGE.
VIM070500-03-CGD-EN-1
27.3. Running the Aggregation Report for the CUST_PREFL Group
The codepage of the system is displayed.
b. Call the SE16 transaction and enter table name TCP00.
c. Use the codepage number returned by the previous function module call
(for example 4103) as selection value for field CPCODEPAGE.
In the selected dataset, the field CPCOMMENT contains most often a
description of the character set it contains (for example ISO-8859-1 or
UTF-16BE).
d. Try this character set first in back end system settings.
27.3 Running the Aggregation Report for the

CUST_PREFL Group
You can run the Aggregation Report for all groups, using the SA38 transaction and
program /OPT/VR_A_AGGREGATION. However, OpenText recommends scheduling
batch jobs for the TRANSACT, MASTER, and USER group. In a multiple backend system,
also schedule batch jobs for the groups starting with OTH*.
Important
If you don’t want to use the default mapping from OpenText supplied
baseline content, use the CUST_PREFL group and run the report. Running the
Aggregation Report for the CUST_PREFL group prefills the customizing for
roles and exceptions.
You must manually map roles and exceptions in Central Reporting; see “Activating
Central Reporting Baseline and Maintaining Reporting Tables” on page 671.
To run the Aggregation Report for the CUST_PREFL group:
1. Run the SA38 transaction.
2. Enter program /OPT/VR_A_AGGREGATION and click .
3. Configure the Aggregation Report, using the following parameters:
Group ID
Enter the group ID, in this case CUST_PREFL.
VIM070500-03-CGD-EN-1
Back end system

If you want to select data only from a subset of back end systems, enter the
back end systems you want to run the Aggregation Report for. If you leave
the field empty, all back end systems will be considered.
Back end related processing

Select this check box to have the Aggregation Report continue even if an
error occurs in one of the back end systems or if data of a back end system
could not be aggregated or modified. A rollback is performed only for the
affected back end system. A commit is performed when all data of the
affected back end system has been modified successfully.
If this check box is not selected, the Aggregation Report cancels if any errors
occur. For all data changes in the central system, a rollback is performed. A
commit is performed when all data is successfully updated.
Asynchronous selection
Select this check box to have a new task opened for every call of the
selection function. If there are more than 35 Reporting Data Tables, this is
required to avoid overflow of buffer when creating generic subroutines
(used to define structures of internal tables dynamically).
Note: If this check box is selected, debugging of the selection function

requires system debugging enabled.
4. To run the Aggregation Report, click .
27.4 Creating Variants of the Aggregation Report for

Each Group
In order to schedule batch jobs for the Aggregation Report, you must create variants
of the Aggregation Report for the TRANSACT, MASTER, USER, and KPI group. In a
multiple backend system, you must also create variants for the groups starting with
OTH*. The variants are included in the batch job, later.
To create variants of the Aggregation Report for each group:
1. Invoke the Aggregation Report screen, see “To run the Aggregation Report for
the CUST_PREFL group:“ on page 669.
2. Enter the Group ID and configure the report for this group, according to your
needs. See Step 3 on page 669.
3. Click to save as variant.
4. In the ABAP: Save as Variant screen, enter Variant name and Description and
save.
5. Repeat the procedure for the other groups.
VIM070500-03-CGD-EN-1
27.5. Activating Central Reporting Baseline and Maintaining Reporting Tables
27.5 Activating Central Reporting Baseline and

Maintaining Reporting Tables
Note: Before activating the Central Reporting Baseline, make sure, you have
configured the System Landscape Directory (SLD), see “Configuring the
System Landscape Directory (SLD)” on page 667.
Central VIM Baseline delivers exception mapping and role mapping as part of the BC set
Reporting activation. To access these mappings, run the /n/OPT/SPRO transaction and navigate
Baseline
to Vendor Invoice Management > Cross Component Configuration > Central
Reporting > Report Table Maintenance. The mappings have one key field Logical
System that remains empty as the logical system key is not supplied in the Baseline
implementation.
If you want to configure custom user roles, add your settings before activating
Central Reporting Baseline. Maintain the roles manually in the Role Mapping
Maintenance without providing the logical system name as the key.
If you want to configure exceptions of your own, add your settings before activating
Central Reporting Baseline. Maintain exceptions in the Exception Mapping
Maintenance without providing the logical system name as the key.
To associate the mappings with the logical systems in the landscape, activate Central
Reporting Baseline by running the /n/OPT/VIM_SYS_ACTIV transaction. It is a one
time activity on each system involved. Perform it as a part of post installation
activity. If you activate Central Reporting Baseline, it provides default mapping of
role IDs and exception IDs from Baseline.
Maintaining If the baseline mapping of roles and/or exceptions does not suit your needs or if you
reporting tables want to enhance the mapping, some maintenance is required, before you can use the
reports in Central Reporting.
You have to perform the following tasks:

• Role Maintenance: Define the roles to be used in the reports. See “To maintain
roles for Central Reporting:“ on page 672.
• Exception Definition Maintenance: Define the exceptions to be reported. See “To
maintain exceptions for Central Reporting:“ on page 672
• Role Mapping Maintenance: Map roles from all the logical systems that have
been maintained for usage in the Aggregation Report. See “To map roles from
several back end systems:“ on page 673.
• Exception Mapping Maintenance: Map exceptions from all the logical systems
that have been maintained for usage in the Aggregation Report. See “To map
exceptions for several back end systems:“ on page 674.
VIM070500-03-CGD-EN-1
To maintain roles for Central Reporting:
1. In the OpenText Configuration, navigate to Vendor Invoice Management >

Cross Component Configuration > Central Reporting > Report Table
Maintenance > Role Definition and Mapping > Role Maintenance.
2. Maintain Role ID and Role text.

Click New entries to add roles.

The roles defined here are used to map roles from several back end systems
during Role Mapping Maintenance, see below.
To maintain exceptions for Central Reporting:

Maintenance > Exception Definition and Mapping > Exception Definition
Maintenance.
VIM070500-03-CGD-EN-1
27.5. Activating Central Reporting Baseline and Maintaining Reporting Tables
2. Maintain Exc. ID and Exception text.

Click New entries to add exception definitions.

The exceptions defined here are used to map exceptions from several back end
systems during Exception Mapping Maintenance, see below.
Once you have run the Aggregation Report for the CUST_PREFL group, the
customizing tables for Role Mapping Maintenance and Exception Mapping
Maintenance are prefilled. To map roles/exceptions from several back end systems,
perform the following steps:
To map roles from several back end systems:

Maintenance > Role Definition and Mapping > Role Mapping Maintenance.
VIM070500-03-CGD-EN-1
The columns Product Code and Responsible Party have been prefilled
automatically.
2. Assign the Role ID (as defined in “To maintain roles for Central Reporting:“
on page 672) to each responsible party (role) for specific product code.
To map exceptions for several back end systems:

Maintenance > Exception Definition and Mapping > Exception Mapping
Maintenance.
VIM070500-03-CGD-EN-1
27.6. Scheduling the Collection Report
The columns Exc. Type and Exc.typeID (Exception Type ID) have been prefilled
automatically.
2. Assign the Exc. ID (as defined in “To maintain exceptions for Central Reporting:
“ on page 672) to each Exception Type ID for specific exception type.
27.6 Scheduling the Collection Report

Important
For archiving object WORKITEM, data must not be data archived before the
Collection Report is run. You must align the interval for data archiving with
the Collection Report runs.
Note: For a description of the KPI Collection Report that is needed for the KPI
Dashboard, see “Collection Job” on page 630.
The Collection Report collects data from VIM transactional tables and SAP workflow
tables and populates the Source Data tables. The Source Data tables are later
aggregated by the Aggregation Report into Reporting Data tables.
Scheduling You can schedule the Collection Report by running the /

OPT/VR_COLLECTION_REPORT program with appropriate start date and time in all
VIM070500-03-CGD-EN-1
the systems involved. OpenText recommends running this report twice a day.
However, depending on how frequently data is needed, you can schedule it
accordingly.
Figure 27-1: Collection Report
Cut-off date The only mandatory selection criterion is Creation Date From. You must set this
date. It refers to the cut-off date, the work item creation date. Any invoices that have
been created before this date are not considered in reporting. The (Creation Date) to
field is relevant only for partial load, see “Partial load” on page 676. You can
combine the Creation Date From field with the Creation Time From field. If you
also provide Creation Time From, date and time together decide the cut-off time
period.
Cut-off is important because Central Reporting is based on workflow task container

elements and a DP workflow template that have been created in VIM 5.2. You
cannot use data from VIM versions older than 5.2 for the reports. The cut-off time
period is used to filter out any data that belongs to older versions.
With a new installation, use the installation or go-live date for the Creation Date
From. With an upgrade, use the date of upgrading.
Do not maintain selection parameters other than Creation Date From and Creation
Time From (and to for partial load).
Note: However, you can use the parameters Task and ID for testing purposes.
The parameters refer to the workflow dialog task and the work item ID.
Delta and full Once scheduled, this report always runs in delta mode. Only those work items and
mode documents are considered that have changed since the last run. Delta mode is
default and fixed. To change to full mode, you must clean table /OPT/VT_JOB; see
“Troubleshooting: Cleaning Up Central Reporting Tables” on page 681.
Partial load VIM provides the “partial load” feature for the Collection Report. Without partial
load, the Collection Report only supported full and delta loads, therefore it was not
VIM070500-03-CGD-EN-1
27.6. Scheduling the Collection Report
possible to collect process information only for a special period of time, which can be
done using partial load. Partial load also makes it possible to correct any data
inconsistencies that can occur if at least one Collection Report run has been
performed using wrong selection criteria in the past.
To prevent such collection inconsistencies, configure the selection criteria

accordingly. Consider the following:
• What are the longest work item processing times?

• How can you avoid downloading too many already downloaded work items
over and over again?
Note: Further considerations might result from your specific system

environment.
Single processes may still be shown as in process by the Central Reporting tools
but they have already been completed in the meantime. The reason for this could be
that the regular Collection Report delta load (usually scheduled as background job)
only considers work items that have been finished since the last collection run, and
the cut-off date has been set in a too restrictive way; see Example 27-1, “Collection
Report inconsistencies” on page 677.
The partial load feature allows to correct such inconsistencies at any time by
updating all corresponding work items of a certain period of time again.
To run the Collection Report in partial load mode, you use a new selection field
“Work Item Creation Date To” (to) in combination with Creation Date From. If you
provide a value in the to field, the Collection Report runs a “partial load” for the
specified creation date range.
Figure 27-1 on page 676 shows a partial load example for exactly one day.
Note: OpenText recommends that you only run the partial load manually if
really required. Do not schedule the partial load job regularly as a background
job.
Example 27-1: Collection Report inconsistencies
Example work item: creation date 3rd of July, completed by posting on 4th of
July
Creation Date From of the Collection Report: Current system date
Depending on when it is running, the Collection Report will show the

following behavior:
Collection Report run scheduled on 3rd of July

The work item is not finished yet and therefore only downloaded as
open work item.
VIM070500-03-CGD-EN-1
Collection Report run scheduled on 4th of July

The work item is finished in the meantime but not updated because the
creation date is 3rd of July (selection criteria used is 4th of July, current
system date).
Trying to download the missed work item at a later time will not help
anymore since the date of the last Collection Report run will be enhanced
every time during the regular scheduled job run.
In this example, the Creation Date From is set too restrictive because the
following parameters were ignored:
• the processing time of the work item
• the gap between the data loads
Assume that the longest work item processing time is 2 weeks and (to make
it simple for this example) a download is triggered only once a day (note that
the recommendation is twice a day or even more often). This means that all
work items that were created 15 days or less ago would have to be
downloaded again to ensure that the correct work item status is uploaded.
Creation Date From of the Collection Report: Current system date minus 2
weeks minus gap between the data loads. In our case this is: 4th of July
(current system date) - 14 days - 1 day (gap between the data loads) = 19th of
June
Collection Report run scheduled on 4th of July , with Creation Date From
set to 19th of June
The work item is finished in the meantime and is updated because the
creation date is 3rd July.
Example 27-2: Partial load
You can use the to date (partial load) to correct data inconsistencies that
happened in the past.
Assume that the current system date is 14th of October. Since 4th of October,
the upload is correctly done with a Creation Date From as the current
system date minus 15 days; for details, see Example 27-1, “Collection Report
inconsistencies” on page 677. Before 4th of October, the upload was done
with the current date as Creation Date From.
The work item created on 3rd of July still shows the wrong status.
Collection Report run on 14th of October , with Creation Date From set to
3rd of July , and to date set to 19th of September
All work items created in the given time frame are updated correctly
now.
VIM070500-03-CGD-EN-1
27.7. Scheduling the User Master Report
Partial load may also be an option if the assumed longest work item
processing time was exceeded for a limited period of time in the past (more
than 15 days ago).
Table / The last run time of the Collection Report is stored in table /OPT/VT_JOB. At the first
OPT/VT_JOB time the Collection Report runs, table /OPT/VT_JOB is empty. Thereafter, the last run
time always gets updated in this table.
Note: If you select Test Mode, the data is not saved to source tables or any
table. Even /OPT/VT_JOB will remain unchanged.
27.7 Scheduling the User Master Report

You can schedule the User Master Report by running the /
OPT/VR_USER_MASTER_REPORT program in all the systems involved. OpenText
recommends running this report twice a day. However, depending on how
frequently data is changed and how frequently it is needed, the report can be
scheduled accordingly.
Schedule the User Master Report to run only after a previous run of the Collection
Report because the User Master Report uses the information from the tables filled in
by the Collection Report. So, if the Collection Report has never run, running the User
Master Report will not produce the desired results.
The User Master Report collects additional user information like first name, last
name, and OpenText user ID when new users appear in the system or any changes
happen to users. This information is used, for example, in the Central Audit Report:
You can click a link in the Current Role column to display details of the agents
associated with the role.
The User Master Report always runs in full update mode.
The following screenshot shows the required selection criteria:
VIM070500-03-CGD-EN-1
27.8 Scheduling the Text Master Report

The Text Master Report provides texts needed for Exception Reasons that appear in
the Central Audit Report. You can schedule the Text Master Report by running the /
OPT/VR_TEXT_MASTER_REPORT program in all the systems involved. OpenText
recommends running the Text Master Report monthly. It should run after the User
Master Report. Depending on how frequently data is changed and how frequently it
is needed, you can schedule the report accordingly. The Text Master Report always
runs in full update mode.
The following screenshot shows the recommended selection criteria:
VIM070500-03-CGD-EN-1
27.9. Scheduling the Aggregation Report
27.9 Scheduling the Aggregation Report

You can schedule the Aggregation Report by running the /OPT/VR_A_AGGREGATION
program with the appropriate Group IDs in the Central System only. See “Central
Reporting Infrastructure“ on page 663.
The Aggregation Report depends on the results of the Collection Report. Therefore,
schedule the Collection Report, the User Master Report, and the Text Master Report
before the Aggregation Report.
Example: The User Master Report runs every Sunday at 20:00. The Aggregation Report with
group USER should be scheduled afterwards, for example every Sunday at 20:10. If the
Aggregation Report would be scheduled before the User Master Report, for example at 19:00,
it would result in user data that is almost one week old.
Single system In a single system scenario, the Central System is the same as the current system.
Schedule the Aggregation Report with all Group IDs, except the Group IDs that start
with OTH_*.
Multiple In a multiple backend system, schedule the Aggregation Report with all Group IDs,
backend including the Group IDs that start with OTH_*.
27.10 Troubleshooting: Cleaning Up Central Reporting

Tables
Important
The Program to clean up VIM report tables is for internal use, only.
You might need to clean up the Central Reporting tables, for example to reload data
after fixing some issues. Whereas VIM Analytics bases on real time VIM tables,
Central Reports base on tables that are not real time. Collection Report, User Master
Report, and Text Master Report pull information from real time VIM tables and
provide data to Source Data Tables. The Aggregation Report selects data from the
Source Data Tables and provides data to the Reporting Data Tables. As Source Data
Tables and Reporting Data Tables are not real time, these tables can be reloaded.
Note: All VIM runtime tables, for example /OPT/VIM_1HEAD, remain

untouched.
In a first step, consider if it is really required to completely clean up the Central

Reporting tables, or if there is just a special time frame with inconsistencies:
• If you know that there is a special time frame with inconsistencies, you can use
the partial load mode of the report /OPT/VR_COLLECTION_REPORT to correct it.
See “Partial load” on page 676.
• If you cannot identify which inconsistencies occurred, you can use the cleanup
report /OPT/VR_CLEAN_TABLES (see “Cleanup report” on page 682) and reload
all reporting data afterwards again; see “To reload reporting data:“
on page 682.
VIM070500-03-CGD-EN-1
Cleanup report To run the cleanup report, run the SA38 transaction with program /
OPT/VR_CLEAN_TABLES.
Report Tables
Select this check box to delete Reporting Data Tables.
Important
This will clean up all data in the end user Central Reports.
Source Tables
Select this check box to delete Source Data Tables.
This will not impact the end user Central Reports, except the Central Audit
Report.
Note: If you reload the whole data, consider the corresponding data volume
that needs to be reloaded.
To reload reporting data:
1. Run the reports /OPT/VR_TEXT_MASTER_REPORT and /

OPT/VR_USER_MASTER_REPORT regardless of the overall data volume.
2. If the data volume is extremely high, use the partial load mode of the Collection
Report to reload the data in buckets. For example, always gather three months
of data, starting from the go-live-date until today.
If the data volume is small, run the Collection Report in the regular mode (with
go-live-date as start date). This results in a “full load” for the very first time. All
later runs are considered as “delta loads”.
3. After data is completely reloaded (either by some “partial loads” or just one
“full load”), schedule the Central Reporting reports as described in “Scheduling
the Collection Report” on page 675 and the subsequent sections.
VIM070500-03-CGD-EN-1
27.11. Maintaining Thresholds for the Key Process Analytics Report
27.11 Maintaining Thresholds for the Key Process

Analytics Report
The Key Process Analytics Report provides a threshold functionality for the
following report panels:
• Total Liability panel
• Processed / In Process Documents panel
• First Pass panel
You can define threshold values for an attention status and a critical status. If the
attention value is exceeded in a cell (or falls below it for the First Pass panel), the cell
is highlighted in orange. If the critical value is exceeded in a cell (or falls below it for
the First Pass panel), the cell is highlighted in red.
The following screenshot shows an example in the Total Liability panel:
To control the threshold functionality, you must maintain the following

corresponding constants:
• “Constant KPA_TS_1STPASS_NO” on page 684
• “Constant KPA_TS_1STPASS_PERC” on page 686
• “Constant KPA_TS_LIAB_AMOUNT1” on page 687
• “Constant KPA_TS_PROCDOCS_NO” on page 690
• “Constant KPA_TS_PROCDOCS_PERC” on page 691
To maintain thresholds for the Key Process Analytics Report:
1. To enter the WebFlow Constant Table where you maintain the constants, run
the /n/OPT/VIM_KPA_CFG transaction.
VIM070500-03-CGD-EN-1
Alternatively, in the OpenText Configuration, navigate to Vendor Invoice

Management > Cross Component Configuration > Central Reporting >
Maintain Constants > Maintain Constants for Key Process Analytics.
2. To maintain a constant, double-click its line.
27.11.1 Constant KPA_TS_1STPASS_NO

Using this constant, you set the thresholds for the Total # First Pass fields in the
First Pass panel. KPA_TS_1STPASS_NO comprises 6 different values separated by a
semicolon:
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>
where you must replace all <value> fields with a number, as follows:
• Value 1 and 2 define the lower and upper threshold for the total number of First
Pass PO Invoices.
• Value 3 and 4 define the lower and upper threshold for the total number of First
Pass NPO Invoices.
• Value 5 and 6 define the lower and upper threshold for the total number of all
First Pass Invoices.
If the total number of First Pass invoices is lower than value 1/3/5, the respective cell
is marked red.
If the total number of First Pass invoices is greater or equal than value 1/3/5 but
lower than value 2/4/6, the respective cell is marked orange.
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
VIM070500-03-CGD-EN-1
Example 27-3: Constant KPA_TS_1STPASS_NO - all values
If the total number of First Pass PO Invoices is lower than 10,000, the
respective cell will be marked red.
If the total number of First Pass PO Invoices is greater or equal than 10,000
but lower than 30,000, the respective cell will be marked orange.
If the total number of First Pass NPO Invoices is lower than 10,000, the
If the total number of First Pass NPO Invoices is greater or equal than 10,000
If the total number of all First Pass Invoices is lower than 20,000, the
If the total number of all First Pass Invoices is greater or equal than 20,000
VIM070500-03-CGD-EN-1
Example 27-4: Constant KPA_TS_1STPASS_NO - values only for 1 line
The total number of first pass invoices is checked against the thresholds for
the All Invoices line, only.
If the total number of all First Pass Invoices goes below 20,000, the respective
cell will be marked red.
If the total number of all First Pass Invoices is greater or equal than 20,000
27.11.2 Constant KPA_TS_1STPASS_PERC

Using this constant, you set the thresholds for all percentage fields in the First Pass
panel. KPA_TS_1STPASS_PERC comprises 6 different values separated by a
semicolon:
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>
where you must replace all <value> fields with a percentage quotation, as follows:
• Value 1 and 2 define the lower and upper threshold for the percentage of First
Pass PO Invoices.
• Value 3 and 4 define the lower and upper threshold for the percentage of First
Pass NPO Invoices.
• Value 5 and 6 define the lower and upper threshold for the percentage of all First
Pass Invoices.
If the percentage of First Pass invoices is lower than value 1/3/5, the respective cell is
marked red.
If the percentage of First Pass invoices is greater or equal than value 1/3/5 but lower
than value 2/4/6, the respective cell is marked orange.
VIM070500-03-CGD-EN-1
Example 27-5: Constant KPA_TS_1STPASS_PERC
If the percentage of First Pass PO Invoices/First Pass NPO Invoices/all First

Pass Invoices goes below 0.1%, the respective cell will be marked red.
If the percentage of First Pass PO Invoices/First Pass NPO Invoices/all First

Pass Invoices is greater or equal than 0.1% but lower than 1%, the respective
cell will be marked orange.
27.11.3 Constant KPA_TS_LIAB_AMOUNT1

Using this constant, you set the thresholds for the amount of blocked documents in
the Total Liability panel. KPA_TS_LIAB_AMOUNT1 comprises 3 different values
separated by a semicolon:
<Value1>;<Value2>;<Value3>
where you must replace all <value> fields with data, as follows:
• Value 1 defines the currency.
• Value 2 and 3 define the lower and upper threshold for the amount of Blocked
Documents.
If the amount of Blocked Documents is greater than the lower threshold but smaller
or equal than the upper threshold, the respective cell is marked orange.
If the amount of Blocked Documents exceeds the upper threshold, the respective cell
is marked red.
The currency value must be maintained if you want to use the threshold
functionality. If any of the other values is not maintained, the respective check is not
done and the cell will not be colored.
VIM070500-03-CGD-EN-1
Example: A Constant Value of USD;;20000 results in the following:
If the amount of Blocked Documents is greater than 20,000 USD, the respective cell is marked
red. The cell will never be marked orange because the respective value is not maintained.
Example 27-6: Constant KPA_TS_LIAB_AMOUNT1
If the amount of Blocked Documents is greater than 10,000 USD but smaller
or equal than 20,000 USD, the respective cell is marked orange.
If the amount of Blocked Documents is greater than 20,000 USD, the

respective cell is marked red.

Using this constant, you set the thresholds for the amount of parked documents in
the Total Liability panel. KPA_TS_LIAB_AMOUNT2 comprises 3 different values
• Value 2 and 3 define the lower and upper threshold for the amount of Parked
Documents.
If the amount of Parked Documents is greater than the lower threshold but smaller
or equal than the upper threshold, the respective cell is marked orange.
If the amount of Parked Documents exceeds the upper threshold, the respective cell
is marked red.
VIM070500-03-CGD-EN-1
If the amount of Parked Documents is greater than 20,000 USD, the respective cell is marked
red. The cell will never be marked orange because the respective value is not maintained.
If the amount of Parked Documents is greater than 5,000 USD but smaller or
equal than 15,000 USD, the respective cell is marked orange.
If the amount of Parked Documents exceeds 15,000 USD, the respective cell
is marked red.

Using this constant, you set the thresholds for the amount of pre-process documents
in the Total Liability panel. KPA_TS_LIAB_AMOUNT3 comprises 3 different values

• Value 2 and 3 define the lower and upper threshold for the amount of Pre-
Process Documents.
If the amount of Pre-Process Documents is greater than the lower threshold but
smaller or equal than the upper threshold, the respective cell is marked orange.
If the amount of Pre-Process Documents exceeds the upper threshold, the respective
cell is marked red.
VIM070500-03-CGD-EN-1
If the amount of Pre-Process Documents is greater than 20,000 USD, the respective cell is
marked red. The cell will never be marked orange because the respective value is not
maintained.
If the amount of Pre-Process Documents is greater than 20,000 USD but

smaller or equal than 30,000 USD, the respective cell is marked orange.
If the amount of Pre-Process Documents exceeds 30,000 USD, the respective

cell is marked red.
27.11.6 Constant KPA_TS_PROCDOCS_NO

Using this constant, you set the thresholds for Total # fields in the Processed / In
Process Documents panel. KPA_TS_PROCDOCS_NO comprises 8 different values
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>;<Value7>;<Value
8>
where you must replace all <value> fields with a number, as follows:
• Value 1 and 2 define the lower and upper threshold for the total number of
processed PO Invoices.
• Value 3 and 4 define the lower and upper threshold for the total number of PO
Invoices in process.
• Value 5 and 6 define the lower and upper threshold for the total number of
processed NPO Invoices.
• Value 7 and 8 define the lower and upper threshold for the total number of NPO
Invoices in process.
If the number of invoices is greater than the lower threshold but smaller or equal
than the upper threshold, the respective cell is marked orange.
If the number of invoices is greater than the upper threshold, the respective cell is
marked red.
VIM070500-03-CGD-EN-1
Example 27-9: Constant KPA_TS_PROCDOCS_NO
There is no check for the total number of processed PO Invoices.
If the total number of PO Invoices in Process is greater than 100,000 but

smaller or equal than 200,000, the respective cell is marked orange.
If the total number of PO Invoices in Process exceeds 200,000, the respective

cell is marked red.
There is no check for the total number of processed NPO Invoices.
If the total number of NPO Invoices in Process is greater than 150,000 but
smaller or equal than 250,000, the respective cell is marked orange.
If the total number of NPO Invoices in Process exceeds 250,000, the

respective cell is marked red.
27.11.7 Constant KPA_TS_PROCDOCS_PERC

Using this constant, you set the thresholds for all percentage fields in the Processed /
In Process Documents panel. KPA_TS_PROCDOCS_PERC comprises 8 different values
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>;<Value7>;<Value
8>
where you must replace all <value> fields with a percentage quotation, as follows:
• Value 1 and 2 define the lower and upper threshold for the percentage of
Processed PO Invoices.
• Value 3 and 4 define the lower and upper threshold for the percentage of PO
Invoices in Process.
VIM070500-03-CGD-EN-1
• Value 5 and 6 define the lower and upper threshold for the percentage of
Processed NPO Invoices.
• Value 7 and 8 define the lower and upper threshold for the percentage of NPO
Invoices in Process.
If the percentage of invoices is greater than the lower threshold but smaller or equal
than the upper threshold, the respective cell is marked orange.
If the percentage of invoices is greater than the upper threshold, the respective cell is
marked red.
Example 27-10: Constant KPA_TS_PROCDOCS_PERC
There is no check for the percentage of Processed PO Invoices.
If the percentage of PO Invoices in Process is greater than 5.5% but smaller

or equal than 80%, the respective cell is marked orange.
If the percentage of PO Invoices in Process exceeds 80%, the respective cell is

marked red.
There is no check for the percentage of processed NPO Invoices.
If the percentage of NPO Invoices in Process is greater than 50% but smaller
or equal than 80%, the respective cell is marked orange.
If the percentage of NPO Invoices in Process exceeds 80%, the respective cell
is marked red.
VIM070500-03-CGD-EN-1
27.12. Configuring the Summary Report
27.12 Configuring the Summary Report

The Summary Report provides the summary of all documents processed through
VIM.
Note: The Summary Report evaluates data from the offline reporting table /
opt/vt_doc_h.
You can configure the report to assign individual document statuses to different
categories and groups.
At the highest level, the summary report distinguishes between invoices and credit
memos. All group IDs created during configuration are applicable to both invoices
and credit memos.
To configure the Summary Report:
1. Run the /n/opt/spro transaction and navigate to Vendor Invoice

Management > Cross Component Configuration > Central Reporting > Report
Table Maintenance > Summary Report Configuration > Summary Report
Maintenance Configuration.
Groups are the highest level unit in the Summary Report. They have one or
more Category IDs assigned to them. In the Report output, groups appear as
headings. Baseline configuration provides the following group IDs:
In process
Invoices that are in VIM processes
Pre Processed
Invoices that are in OCR processing
Processed
Invoices that are posted
Others
Invoices that have statuses, for example Obsolete, or Rescan completed
VIM070500-03-CGD-EN-1
2. To configure the mapping of Category IDs and text, double-click Category id/
text Configuration in the Dialog Structure panel. Each category is assigned to a
group ID. Baseline configuration provides the following category IDs:
3. To configure the assignment of Category IDs and Status Codes, select a

Category line and double-click CategoryID/Status Configuration in the Dialog
Structure panel.
StatusCode
Enter the Status Code for the Category ID. You can assign multiple Status
Codes for each Category ID.
When the Summary Report is run, the program distinguishes the invoice
documents depending on the Status Code. Then, the program categorizes
and displays the Category (text) in the report, as a subsection of the Group.
If the Status Code of a Category is not found in the Summary Report, the
corresponding Category Text is not displayed in the report.
VIM070500-03-CGD-EN-1
27.12. Configuring the Summary Report
4. To configure the assignment of Category IDs and Group IDs, double-click

Category/Group ID configuration in the Dialog Structure panel.
VIM070500-03-CGD-EN-1
Chapter 28
SAP Shared Service Framework Integration
As part of Business Suite 2010 (ERP 6.0 EhP5 and SAP CRM 7.0 EhP1), SAP delivers
SAP Shared Service Framework. SAP Shared Service Framework contains a rich set
of tools to improve and automate Shared Service Center operations.
Technically, SAP Shared Service Framework is based on SAP Customer Relationship

Management (SAP CRM), specifically on the Interaction Center. In case of the VIM
integration, this is the Accounting Interaction Center (AIC). The Interaction Center is
part of SAP Shared Service Framework. SAP CRM provides software for ticket
systems, for example in the Accounts Payable department.
SAP Shared Service Framework integrates the leading CRM system with the
backend ERP systems, for example VIM. Shared Service Center agents work entirely
in their AIC, with access to the backend ERP systems that they are responsible for.
The AIC provides the means to support communication with employees, suppliers
and customers.
VIM can be integrated with SAP Shared Service Framework. The VIM integration
provides the feature to display VIM Analytics (VAN) inside the CRM interaction:
• to display all invoices to a selected vendor and
• to add links to VIM invoices from a SAP CRM Service Request.
In both cases, still the old VAN is displayed instead of the new VAN.
VIM leverages SAP Shared Service Framework and provides integration scenarios
with the AIC. See the following examples:
Example:
• The integration allows searching and finding invoices in VIM from AIC.
• VIM users in the ERP backend system can open service requests from VIM work items and
exceptions.
• Specific exceptions can be configured to automatically create a service request in CRM/
AIC.
Among others, the benefits of SAP Shared Service Framework integration are the
following:
• automation in the Shared Services environment
• cost reduction
• enhanced efficiency
• reduction of operational risk
VIM070500-03-CGD-EN-1
Chapter 28 SAP Shared Service Framework Integration
VIM provides a feature to automatically create Service Requests for specific

exceptions in background. You can configure this feature during the configuration of
the process type, see “Defining the Process Type” on page 225.
28.1 SAP Shared Service Framework Integration

Activities
To put the SAP Shared Service Framework integration into operation, you must
perform the following configuration tasks:
Note: You must perform the tasks either in the SAP ERP (VIM) system or in
the CRM system. The system is indicated in square brackets, for example
[ERP], in the title of each section.
• “Maintaining a Logical System for the CRM System in VIM [ERP]” on page 698
• “Creating an ITS Service in the Backend ERP System [ERP]” on page 699
• “Defining Transaction Launcher Logical Systems and URL [CRM]” on page 707
• “Creating a Transaction Launcher for VIM Work Centers to Call VIM Analytics
(Service Request) [CRM]” on page 710
• “Creating a Transaction Launcher for VIM Work Centers to Call VIM Analytics
(Account ID Confirmation) [CRM]” on page 717
• “Configuring Work Centers for VIM Analytics [CRM]” on page 718
• “Configuring Business Context Links for OpenText Linked Objects in Service
Request [CRM]” on page 723
• “Configuring the OpenText Vendor Factsheet BSP Component [CRM]”
on page 729
• “Maintaining the Logical System in OpenText Configuration Tables [CRM]”
on page 741
• “Defining Prefill Business Role Settings for RFC (Service Request Display)
[CRM]” on page 742
28.1.1 Maintaining a Logical System for the CRM System in

VIM [ERP]
To integrate the SAP CRM SAP Shared Service Framework system into VIM, you
must maintain a logical system for the CRM system in the backend ERP system
(VIM system). Support for SAP CRM SAP Shared Service Framework will only be
activated if the logical system of the CRM is maintained. This setting generates the
Service Requests button in the dashboards and the Create SR check box in the
process type definition.
The procedure to maintain a logical system is described in section 30.2 “Maintaining

a Logical System for the CRM System in VIM” in OpenText Vendor Invoice
Management for SAP Solutions - Installation Guide (VIM-IGD).
VIM070500-03-CGD-EN-1
28.1. SAP Shared Service Framework Integration Activities
28.1.2 Creating an ITS Service in the Backend ERP System

[ERP]
In this section, you maintain a new ITS service in the backend ERP system (VIM
system). This ITS Service is used by the CRM transaction launcher to launch the
OpenText transaction for VIM Analytics in the VIM system.
The transaction launcher is a tool that you can use to allow agent access to business
transactions directly from the IC WebClient screen (in case of VIM, this is the AIC).
Essentially, the transaction launcher is a collection of shortcuts to available functions
or transactions within SAP CRM and ERP systems.
You can create own service names in the nodes in the SICF transaction. The Service
Name creation in this section is an example to create own services under the ITS
node.
To create an ITS service:
1. Run the SICF transaction.
2. Enter the Service Name, for example ITS, and execute.
VIM070500-03-CGD-EN-1
3. Expand default_host > sap > bc > gui > sap > its and right-click the ITS Service
name.
VIM070500-03-CGD-EN-1
4. Click New Sub-Element.
Note: If you get a popup with information about the SAP namespace,
confirm it by clicking .
VIM070500-03-CGD-EN-1
5. Enter the Name of Service Element to Be Created, for example OPT_LTX.

Click Independent Service.
Click .
VIM070500-03-CGD-EN-1
6. Configure the settings as shown in the screenshot above.

In the Service Data tab, click GUI Configuration.
VIM070500-03-CGD-EN-1
7. Maintain the following service parameters:
Note: You can create own service names in the nodes in the SICF
transaction. However, for GUI Configuration in the Service Data tab, you
must set the following Parameter Name and Value. The ERP transaction
that OpenText SSF Transaction Launcher ITS Services depend on is /
OPT/VIM_SSF_LAUNCH. This transaction is called when the dependent
transaction launcher is called.
Parameter Name Value

~AUTOSCROLL 0
~COOKIES 0
~GENERATEDYNPRO 1
~LISTSCROLLING 0
~POPUPS 1
~STYLE DHTML
~WEBGUI 1
~TRANSACTION /OPT/VIM_SSF_LAUNCH
~FLICKERFREE 1
~DISCONNECTONCLOSE 1
~THEME 99
VIM070500-03-CGD-EN-1
~WEBGUI_SIMPLE_TOOL 114
BAR
Click to continue.
8. In the Handler List tab, set the Handler class name CL_HTTP_EXT_ITS.
9. Save the Service.

When prompted, enter the name of a development package and click .
Note: If you do not have a development package for your own

developments, create a new development package.
When prompted, enter a workbench request and click .

Exit the screen to create a Service.
10. To activate the service, select the service and right-click.
VIM070500-03-CGD-EN-1
11. Click Activate Service.

Confirm the popup asking if you want to activate the service with Yes.
12. To activate the parent node where you have created the new service name,
select the node default_host > sap and right-click.
13. Click Activate Service.
VIM070500-03-CGD-EN-1
Click .
28.1.3 Defining Transaction Launcher Logical Systems and

URL [CRM]
The ITS defined in “Creating an ITS Service in the Backend ERP System [ERP]”
on page 699 will be registered in the CRM system. In this section, you maintain the
mapping name, the logical system name, the ITS client, and the URL for ITS. Based
on this information, the CRM transaction launcher can use the ITS service on the
backend ERP system to launch the OpenText transaction for VIM Analytics in the
VIM system.
To define transaction launcher logical systems and URL:
1. In the CRM system, navigate to SAP menu > Interaction Center > Interaction
Center WebClient > Administration > System Parameters > Define
Transaction Launcher Logical Systems and URLs.
Alternatively, run the CRMS_IC_CROSS_SYS transaction.
VIM070500-03-CGD-EN-1
2. Maintain the Mapping name and the corresponding backend ERP Logical
System name with the ITS Client and the URL of ERP ITS, specifically for
OpenText components.
Determine the URL of ITS, for example: <http>://<Host Name>:<Port>/
<sap><created service name path>?sap-client=<CLIENT>.
Example: <http>://<host name>:<port>/sap/bc/gui/sap/its/OPT_LTX?

sap-client=800
If SAP Shared Service Framework for Financials is enabled in your SAP ERP
backend system, use the WEBGUI ITS service instead of your newly created
service:
Note: SAP Shared Service Framework for Financials is enabled in your

SAP ERP backend system
• if you are using SAP ERP 6.0 enhancement package 5 (or higher), or
• if you have implemented all the SAP notes regarding the enablement of
the Financials Shares Service Center (see SAP note 1454759).
Example: <http>://<host name>:<port>/sap/bc/gui/sap/its/webgui/!?

~transaction=IC_LTXE&~okcode=ICEXECUTE
Notes
• Mapping logical systems and setting the URLs for standard SAP objects
like Vendor Links in business context must follow SAP conventions to
determine the URLs.
• You must maintain 2 URLs for each backend ERP system, one URL for
standard SAP objects and another URL for OpenText objects.
• Mapping names for OpenText objects follow a convention: The first 5
characters in the mapping name are ZZZZZ, followed by free text that
identifies the backend ERP system, for example ZZZZZD94.
VIM070500-03-CGD-EN-1
3. If your CRM system is connected to more than one SAP ERP backend system,
mark the MultiSys check box for your OpenText object URL links.
4. Save and exit.
Example 28-1: URLs

There is a backend ERP system called D94. SAP Shared Service
Framework for Financials is not enabled in system D94.
There is another backend ERP system called D95. SAP Shared Service
Framework for Financials is enabled in system D95.
The following two URLs are maintained:
URL for OpenText objects (--> see “Maintaining the Logical System in
OpenText Configuration Tables [CRM]” on page 741)
Mapping: ZZZZZD94
Logical system: D94CLNT800
Local ITS:
ITS Client: 800
URL of ITS: http://op60vimd94.optura.local:
8000/sap/bc/gui/sap/its/opt_ltx?sap-client=800
Mapped Logical System Description: D94CLNT800
URL for standard SAP objects

Mapping: ZZZZZD95
Logical system: D95CLNT800
Local ITS:
ITS Client: 800
URL of ITS: http://op60vimd95.optura.local:
8000/sap/bc/gui/sap/its/webgui/!?~transa
ction=IC_LTXE&~okcode=ICEXECUTE
Mapped Logical System Description: D95CLNT800
VIM070500-03-CGD-EN-1
28.1.4 Creating a Transaction Launcher for VIM Work Centers

to Call VIM Analytics (Service Request) [CRM]
In this section, you configure a new transaction launcher to call VIM Analytics with
regards to a Service Request. VIM Analytics is launched with Vendor as prefilled
parameter in the selection screen. The Service Request that is currently open in CRM
can be attached to other DP documents that VIM Analytics displays for the prefilled
Vendor.
To create a transaction launcher for VIM work centers to call VIM Analytics
(Service Request):
1. In the CRM system, navigate to SAP Customizing Implementation Guide >

Customer Relationship Management > Interaction Center WebClient > Basic
Functions > Transaction Launcher > Configure Transaction Launcher (Wizard)
2. Click Continue.
VIM070500-03-CGD-EN-1
3. Enter the Launch Transaction ID, for example ZVIM_TL_CONFIG_SRQ, and the
Component Set ALL.
Click Continue.
VIM070500-03-CGD-EN-1
4. Enter a meaningful Description.

Enter Handler Class, for example ZVIM_TL_CONFIG_SRQ.
Click Continue.
VIM070500-03-CGD-EN-1
5. In the Transaction Type list, select A BOR Transaction and fill in the following
details:
Logical System
Example: D94CLNT800 (belonging to mapping ZZZZZD94)
See “Defining Transaction Launcher Logical Systems and URL [CRM]”
on page 707.
BOR Object Type

/OPT/V1001
Method Name
DISPLAY
6. Click Continue.
VIM070500-03-CGD-EN-1
7. In Parameter, enter ICWEBCLIENTBORKEYPARAMETER Object Key.

Click Continue.
VIM070500-03-CGD-EN-1
8. In Parameter, enter ICWCPROCESSEDOBJECT /OPT/V1001

Click Continue.
VIM070500-03-CGD-EN-1
9. Click Complete.
10. Change the Handler Class of the newly created Transaction Launcher ID.
Perform the following steps:
a. Navigate to SAP Customizing Implementation Guide > Customer

Relationship Management > Interaction Center WebClient > Basic
Functions > Transaction Launcher > Copy/Delete Launch Transactions
b. Select the newly created Launch Transaction ID and click .
c. Change the Handler Class entry for the selected Launch Transaction ID
to /OPT/CL_VIM_TL_CONFIG_SRQ.
d. If SAP Shared Service Framework for Financials is enabled in your SAP

ERP backend system, change the Source Session Type to Simple ABAP
Messaging.
VIM070500-03-CGD-EN-1
Note: SAP Shared Service Framework for Financials is enabled in

your SAP ERP backend system
• if you are using SAP ERP 6.0 enhancement package 5 (or higher), or
• if you have implemented all the SAP notes regarding the
enablement of the Financials Shares Service Center (see SAP note
1454759).
e. Check that the Definition fields are populated as follows:

Definition 1: /OPT/V1001
Definition 2: DISPLAY
Definition 3: <Mapping name for logical system of ERP system>, for example
ZZZZZD94.
If the Definition fields are not populated correctly, delete the newly created
Launch Transaction and repeat the above steps beginning from Step 1. Check
the fields in Step 5 carefully.
28.1.5 Creating a Transaction Launcher for VIM Work Centers

to Call VIM Analytics (Account ID Confirmation) [CRM]
In this section, you configure a new transaction launcher to call VIM Analytics with
regards to account ID confirmation. The transaction launcher with regards to
account ID confirmation launches the backend ERP VIM Analytics report with
prefilling the Vendor number in the VIM Analytics selection screen. The Vendor
number is mapped to the CRM confirmed Account ID.
To create a transaction launcher for VIM work centers to call VIM Analytics
(account ID confirmation):
1. Create a new Launch Transaction ID with name ZVIM_TL_CONFIG and

description OpenText Transaction Launcher.
Therefore, follow Step 1 to Step 9 in “Creating a Transaction Launcher for VIM
Work Centers to Call VIM Analytics (Service Request) [CRM]” on page 710.
Note: When entering the same handler class in Step 4, the fields in the
Details section are prefilled automatically in Step 5.
2. Change the Handler Class of the newly created Transaction Launcher ID.
Perform the following steps:
a. Navigate to SAP Customizing Implementation Guide > Customer

Relationship Management > Interaction Center WebClient > Basic
Functions > Transaction Launcher > Copy/Delete Launch Transactions
VIM070500-03-CGD-EN-1
b. Select the newly created Launch Transaction ID and click .
c. Change the Handler Class entry for the selected Launch Transaction ID
to /OPT/CL_VIM_TL_CONFIG.
28.1.6 Configuring Work Centers for VIM Analytics [CRM]

In this section, you configure appropriate work centers for VIM Analytics, one
regarding Service Requests and another one regarding Account identification. The
work centers are used to launch the created Transaction Launchers, see “Creating a
Transaction Launcher for VIM Work Centers to Call VIM Analytics (Service
Request) [CRM]” on page 710 and “Creating a Transaction Launcher for VIM Work
Centers to Call VIM Analytics (Account ID Confirmation) [CRM]” on page 717.
In the CRM Interaction Center, the work centers are displayed as buttons in the
navigation bar.
VIM070500-03-CGD-EN-1
To configure work centers for VIM Analytics:
1. Navigate to SAP Customizing Implementation Guide > Customer

Relationship Management > UI Framework > Technical Role Definition >
Define Navigation Bar Profile.
Double-click Define Logical Links in the Dialog Structure panel.
VIM070500-03-CGD-EN-1
2. In the Define Logical Links screen, click New Entries and create a new Logical
Link ID using the following parameters:
Logical Link ID
<Name of the Logical Link ID>, for example ZAIC_LINK1
Type
Launch Transaction
Target ID
EXECLTX
Parameter
<Your Launch Transaction ID>, for example ZVIM_TL_CONFIG_SRQ; see
“Creating a Transaction Launcher for VIM Work Centers to Call VIM
Analytics (Service Request) [CRM]” on page 710
Parameter Class
CL_CRM_UI_LTX_NAVBAR_PARAM
Title
VIM Analytics SRQ
Description
VIM Analytics SRQ
Save the new Logical Link ID and exit.
3. Click New Entries again and create another new Logical Link ID using the
VIM070500-03-CGD-EN-1
Logical Link ID
<Name of the Logical Link ID>, for example ZAIC_LINK2
Type
Launch Transaction
Target ID
EXECLTX
Parameter
<Your Launch Transaction ID>, for example ZVIM_TL_CONFIG; see “Creating a
Transaction Launcher for VIM Work Centers to Call VIM Analytics
(Account ID Confirmation) [CRM]” on page 717
Parameter Class
CL_CRM_UI_LTX_NAVBAR_PARAM
Title
VIM Analytics Account ID
Description
VIM Analytics Account ID
Save the new Logical Link ID and exit.
4. Double-click Define Work Centers in Dialog Structure.

In the Define Work Centers screen, click New Entries.
VIM070500-03-CGD-EN-1
5. Create one work center for VIM Analytics with regards to Account ID and
another work center for VIM Analytics with regards to Service Request. Enter
the Logical Link ID, created in Step 2 and Step 3.
6. In Dialog Structure, double-click Define Navigation Bar Profiles. Select the

Navigation Bar Profile you want to enhance.
Note: SAP's default navigation bar profile for the Accounting Interaction
Center Agent is AIC_AGENT. SAP strongly recommends that you never
alter the SAP Standard Navigation Bar Profiles. Always create a new one
or use an existing copy of the Navigation Bar Profiles. See the SAP
documentation for more information about copying the Navigation Bar
Profiles, assigning them to business roles, and so on.
7. In Dialog Structure, double-click Assign Work Centers to Navigation Bar

Profile. In the Assign Work Centers to Navigation Bar Profile view, click New
Entries.
VIM070500-03-CGD-EN-1
8. Assign the 2 work centers you have created and enter the position at which the
work centers should be located within the navigation bar.
Save your changes.
28.1.7 Configuring Business Context Links for OpenText

Linked Objects in Service Request [CRM]
The purpose of this section is to launch the Transaction Launcher to call VIM
Analytics appropriately when the user clicks OpenText linked objects, for example a
DP document link attached to a Service Request in the Business Context. When a
user clicks a DP document link in the Business Context, VIM Analytics is launched
and directly displays the DP document detail output without displaying the VIM
Analytics selection screen
To configure Business Context links:

Relationship Management > Transactions > Settings for Service Requests >
Define Settings for Business Context.
2. In the Define Object Link Types screen, click New Entries.
VIM070500-03-CGD-EN-1
3. Define a Link Type with the same name as business object name: /OPT/V1001
with Description of Object Link Type: OpenText DP document and save the
Link Type.
Note: Ignore a warning to choose the key from the allowed namespace.
4. Select the Link Type /OPT/V1001 and double-click Define Object Link Type
Details in Dialog Structure.
5. In the Define Object Link Type Details screen, click New Entries.
6. Enter Object Link Class /OPT/CL_FSSC_BC_LINK_DP for the Object Link

Type /OPT/V1001 and save the configuration.
7. Double-click Define Object Link Profile in Dialog Structure and select the
Link Prof. SSF_AIC.
.
8. Double-click Assign Object Link Types in Dialog Structure.
VIM070500-03-CGD-EN-1
9. Click New Entries and assign the new entry /OPT/V1001 to the Link Types of
Object Link Profile SSF_AIC and save the configuration.
10. In Dialog Structure, double-click Define Business Context Profile and select
the SSF_AIC Business Context Profile.
11. In Dialog Structure, double-click Assign Object Link Types.
VIM070500-03-CGD-EN-1
12. Click New Entries, define the new entry /OPT/V1001.

Save the configuration.
13. In Dialog Structure, double-click Define Business Context Profile and select
the Business Context Profile SSF_ALL.
14. In Dialog Structure, double-click Assign Object Link Types.
15. Click New Entries, define the new entry /OPT/V1001.


Relationship Management > UI Framework > Technical Role Definition >
Define Navigation Bar Profile.
In Dialog Structure, double-click Define Logical Links.
VIM070500-03-CGD-EN-1
17. In the Define Logical Links screen, click New Entries and create a new Logical
Link ID for Service Request Business Context DP links, using the following
parameters:
Type
Enter Link.
Parameter
Enter the already created Launch Transaction ID (see “Creating a
Transaction Launcher for VIM Work Centers to Call VIM Analytics (Service
Request) [CRM]” on page 710) with regards to the Service Request work
center.
18. In Dialog Structure, double-click Define Navigation Bar Profiles and select the
custom Navigation Bar Profile.
19. In Dialog Structure, double-click Define Generic Outbound Plug Mapping.
VIM070500-03-CGD-EN-1
20. In the Define Generic Outbound Plug Mappings screen, click New Entries,
create a new entry with name WRAPPED_/OPT/V1001, and assign the Logical
Link ID created for Business context links, for example ZOPTBC.
Note: The Object Type should be concatenated with text WRAPPED_.
21. Repeat Step 18 to Step 20 for all custom Navigation Bar Profiles that are
affected; that means, also for the navigation bar profile belonging to the SAP
Shared Service Framework Occasional User (for example, navigation bar profile
ZVIM_SSF_OCC_USER).
Note: SAP's default navigation bar profile for the SAP Shared Service
Framework Occasional User is SSF_OCC_USER. SAP strongly recommends
that you never alter the SAP Standard Navigation Bar Profiles. Always
create a new one or use an existing copy of the Navigation Bar Profiles.
Please see the SAP documentation for more information about copying the
Navigation Bar Profiles, assigning them to business roles, and so on.
22. To create an OpenText Business Context object type in Table/View

BSPDLCV_OBJ_TYPE, run the SM30 transaction to maintain BSPDLCV_OBJ_TYPE.
Click New Entries.
VIM070500-03-CGD-EN-1
Object Type
WRAPPED_/OPT/V1001
Description
OpenText Document
GenIL Component Name

SO2
BOL Object Name

ICBORWrapper
BOR Object Type

/OPT/V1001
24. Save and exit.
28.1.8 Configuring the OpenText Vendor Factsheet BSP

Component [CRM]
The OpenText Vendor Factsheet is a consolidated report for a selected vendor in
VIM that is displayed in the CRM UI.
The Factsheet provides you with an immediate and condensed overview of

information about business partners. The information is taken from several sources
such as business partner master data, statistical and transaction data, derived from
SAP CRM, SAP ERP, and SAP NetWeaver BI. The Factsheet helps you to quickly
retrieve information about customers before you interact with them. Thus it enables
you to improve the handling of customer queries.
The Factsheet uses the Business Server Page (BSP) component to display the loading
data in a web browser.
VIM070500-03-CGD-EN-1
To configure the OpenText Vendor Factsheet BSP component:

Relationship Management > CRM Cross-Application Components > Generic
Interaction Layer/Object Layer > Basic Settings.
Note: All OpenText CRM BC SETs must be activated before the following
step.
2. Define a new entry in Component Definition with a new custom Component

Name, for example ZOPTVS. To create a new Component Definition, click New
Entries in the Component Set Definition screen. Use the following parameters:
Implementation Class
/OPT/CL_FACTSHEET
Object Table
/OPT/FS_OBJECT
Model Table
/OPT/FS_MODEL
3. Double-click Component Set Definition in Dialog Structure.

To create a new custom Component Set entry, click New Entries.
VIM070500-03-CGD-EN-1
Enter a Component Set name, for example ZOPTCOMPSET, and a meaningful

Description. Save the configuration.
4. Select the newly created Component Set and double-click Component

Assignment in Dialog Structure.
In the Component Assignment screen, click New Entries, assign the newly
created Component Name to the newly created Component Set, and save the
configuration.
5. To assign models to the Business Component, run the BSP_WD_CMPWB

transaction (UI Component Workbench), enter the Component /
OPT/VENDOR_FS, and click Display.
6. Click Runtime Repository Editor, expand the Models node and click to
switch to edit mode.
VIM070500-03-CGD-EN-1
7. Select the existing Model /OPT/VENDOR_FS, right-click, and click Remove.

Save and exit from the transaction.
8. Run the BSP_WD_CMPWB transaction (UI Component Workbench), enter the

Component /OPT/VENDOR_FS, and click Display.
Click Runtime Repository Editor and click to switch to edit mode.
9. Open the Models node. Right-click Models and click Add Model.
VIM070500-03-CGD-EN-1
10. Enter the Component Set name created in Step 3 on page 730, for example
ZOPTCOMPSET.
Save and exit from the transaction.
11. To configure the view in the BSP component, run the BSP_WD_CMPWB transaction
(UI Component Workbench), enter the Component /OPT/VENDOR_FS, and click
Display.
Click Component Structure Browser.
12. Expand the Views node and double-click /

OPT/VENDOR_FS/vendorfactsheetview
Click the Configuration tab and click New Configuration.
VIM070500-03-CGD-EN-1
13. Keep the default prefilled values:
Parameter Name Value

Role Config. Key <DEFAULT>
Note: If you use a customer specific Role Config.

Key, do not enter <DEFAULT> but your customer
specific Role Config. Key.
Component Usage <DEFAULT>
Object Type <DEFAULT>
Object Subtype <DEFAULT>
Click .
Press the ENTER key and assign to a Transport Request.
VIM070500-03-CGD-EN-1
14. Select the fields in Available Fields and move them to Displayed Fields.
Note: You must move the fields one by one.
15. When you have moved all fields to Displayed Fields, save and exit from the
transaction.
16. To maintain the Factsheet, navigate to SAP Customizing Implementation

Guide > Customer Relationship Management > UI Framework > UI
Framework Definition > Fact Sheet > Maintain Fact Sheet.
17. Choose the Fact Sheet ID to plug the OpenText Vendor Factsheet. You can add
the BSP Component /OPT/VENDOR_FS to any of the Fact Sheet IDs. In the
example, the BSP Component /OPT/VENDOR_FS is added to Fact Sheet ID
FSSC_VEND_FS.
Select the Fact Sheet ID FSSC_VEND_FS and double-click View Assignments in
Dialog Structure.
VIM070500-03-CGD-EN-1
18. Create a new entry with the following details:
Component Name
/OPT/VENDOR_FS
Interface View
Select /OPT/VENDOR_FS/MainWindow from the drop-down list (F4 help).
Inbound Plug
DEFAULT
Title
OpenText Vendor Factsheet ID
Save and exit from the customizing.
19. To link the configured Factsheet ID to the BSP Vendor Factsheet ID, run the
BSP_WD_CMPWB transaction (UI Component Workbench), enter the Component
BSP_DLC_FS, and click Display.
VIM070500-03-CGD-EN-1
20. Click Component Structure Browser.

Expand the Views node and double-click BSP_DLC_FS/factsheet.
Click the Configuration tab and then click Edit.
21. From the drop-down list, select the Factsheet where you added the OpenText
business component. In the example, the BSP Component /OPT/VENDOR_FS was
added to Factsheet ID FSSC_CUST_FS
Select the Factsheet FSSC_CUST_FS and click New.
22. From the drop-down lists, select the Fact Sheet ID FSSC_CUST_FS and the Role
Key Accounting IC Default Key and click Next.
Note: If you use a customer specific role configuration key, select your
role configuration key for the field Role Key instead of selecting the
default role configuration key Accounting IC Default Key.
VIM070500-03-CGD-EN-1
23. From the drop-down lists, select the Page Type, for example Tiles, and the
Tile Layout, for example 2_X_3 (2 columns and 3 rows), then click Next.
Each cell (tile) in Tiles represents a View. Tiles are grouped under a Tiles group
which is displayed in the CRM UI page.
24. To move the OpenText Vendor Factsheet to any of the tiles, select a tile, then
select the OpenText Vendor Factsheet ID, and click the down arrow which will
place the OpenText Vendor Factsheet into the selected tile.
Use the Up and Down arrows to move the OpenText Vendor Factsheet to the
target position within the tile.
VIM070500-03-CGD-EN-1
Click the Configuration link to the right of the assigned OpenText Vendor
Factsheet.
25. Click New.
26. Click Continue.
A new Configuration is added as a new line.

Scroll down to the Available Fields area.
VIM070500-03-CGD-EN-1
27. Select the Available Fields and move them to the Displayed Fields. To do so,
select each field and click the arrow button.
Align the Displayed Fields by using the Up and Down buttons.
28. Click Back.
VIM070500-03-CGD-EN-1
29. Click Save and then click Finish. The new configuration is saved.
Exit from the transaction.
28.1.9 Maintaining the Logical System in OpenText

Configuration Tables [CRM]
SAP Shared Service Framework integrates the leading CRM system with the
backend ERP systems, for example VIM. In this section, you maintain all backend
ERP systems that are connected with the CRM system.
Every backend ERP system is mapped with a unique mapping name as a logical
system. Maintain the mapping names for each logical system in tables/views /
OPT/LOGSYS_MAP.
Note: Mapping names for OpenText objects follow a convention: The first 5
characters in the mapping name are ZZZZZ, followed by free text that identifies
the backend ERP system, for example ZZZZZD94.
To map the logical system of the backend ERP:
1. In the CRM system, run the SM30 transaction.
2. In Table/View, enter /OPT/LOGSYS_MAP and click Maintain.
VIM070500-03-CGD-EN-1
3. In the Mapping column, enter an appropriate mapping name for the Logical
system of the VIM system. See also “Defining Transaction Launcher Logical
Systems and URL [CRM]” on page 707.
28.1.10 Defining Prefill Business Role Settings for RFC (Service

Request Display) [CRM]
You can use this customizing activity to trigger service request creation and service
request search from SAP GUI based applications, for example ERP.
This setting restricts the user not to display all other work centers when opening a
Service Request from VIM Analytics.
To define prefill business role settings for RFC:

Relationship Management > Transactions > Settings for Service Request >
Settings for UI Launch > Define Prefill Business Role Settings for RFC.
2. In the Define Prefill Business Role Settings for RFC screen, add a new entry
with the following values:
RFC Name
CRM_PREFILL_SRVQ_RFC_DISPLAY
VIM070500-03-CGD-EN-1
Business Role
<Name of your business role for the SSF Occasional User>, for example
ZVIM_SSF_OCC
Object Type
CRM_SRQM_INCIDENT
Object Action
Display
4. Repeat Step 2 and Step 3 to create a second entry with the following values:
RFC Name
CRM_PREFILL_SRVQ_RFC_CREATION
Business Role
ZVIM_SSF_OCC
Object Type
CRM_SRQM_INCIDENT
Object Action
Create
5. Repeat Step 2 and Step 3 to create a third entry with the following values:
RFC Name
CRM_PREFILL_SRVQ_RFC_SEARCH
Business Role
ZVIM_SSF_OCC
Object Type
CRM_SRQM_INCIDENT
Object Action
Search
VIM070500-03-CGD-EN-1
28.2 Maintaining the Initialization Procedure for

Service Requests [ERP]
The initialization procedure defines the fields in the CRM service request that will be
initialized.
When creating a CRM service request, some fields can be set initially. The
initialization procedure defines the initial values (the default values) for some fields
in a CRM service request. Moreover, the initialization procedure provides the
configuration options to set initial values to these fields.
To maintain the initialization procedure for service requests:
Invoice Management > Cross Component Configuration > CRM Integration >
Maintain Initialization procedure for service requests.
2. In the Initializing Procedure Overview screen, select the Initializing Procedure

Default and double-click Field config for Initializing Procedure.
3. Configure the fields, using the following parameters:
Field Type
Select Table or Field from the drop-down list.
Value Determination Type

Select one of the following types from the drop-down list:
• Default value (Constant)
• Function Module
• System field (SYST)
• Application variable
Field value
Enter the field value, depending on the setting in Value Determination
Type.
VIM070500-03-CGD-EN-1
28.3. Mapping the Initialization Procedure to the Service Request Creation Points [ERP]
Default value (Constant)

Provide the exact value that needs to be passed to the field.
Function Module
Provide the name of the function module that will provide the value of
the field. The interface of this function module must be exactly the same
as /OPT/SR_DETERMINE_FIELD_VALUE.
System Field (SYST)
Provide any field from the standard structure SYST.
Provide any field from the table /OPT/VIM_1HEAD.
28.3 Mapping the Initialization Procedure to the

Service Request Creation Points [ERP]
You must assign the initialization procedure to the Service Request creation points,
which are VIM dashboards or screens. With baseline implementation, all VIM
dashboards are assigned to a single initialization procedure.
Prerequisites The initialization procedure is maintained. See “Maintaining the Initialization

Procedure for Service Requests [ERP]” on page 744.
To map the initialization procedure to the Service Request creation points:
Invoice Management > Cross Component Configuration > CRM Integration >
Mapping of Initialization procedures to SR creation points.
2. In Init Proc, enter the initialization procedure that you maintained in

“Maintaining the Initialization Procedure for Service Requests [ERP]”
on page 744.
VIM070500-03-CGD-EN-1
28.4 Defining Application Areas for Service Request

[CRM]
VIM supports creating CRM Service Requests from different VIM screens in the ERP
backend. To enable this functionality, you must define an application area for VIM.
An application area is used to combine activities of an application. You can then

perform common customizing settings for all activities within the application area.
Based on the application area, it is also possible to determine service request
attributes from the application context.
To define application areas for VIM:
1. Run the SPRO transaction and navigate to the menu path Cross-Application
Components > Processes and Tools for Enterprise Applications > Shared
Service Framework > Integration with SAP CRM > Integration with Service
Request > Define Customer Application > Define Application Areas.
Application
FINANCIALS
Note: This name corresponds to the value of field SCENARIO in the

initialization procedure (see “Maintaining the Initialization Procedure
for Service Requests [ERP]” on page 744).
Application Area
VIM
Application Area Name

Vendor Invoice Management
Request > Define Customer Application > Define Activities.
VIM070500-03-CGD-EN-1
28.4. Defining Application Areas for Service Request [CRM]
Application
FINANCIALS
Note: This name corresponds to the value of field SCENARIO in the

Activity
SAIC
Note: This name corresponds to the value of field ELEMENT in the

Application Area
VIM
Request > Processing > Activate Manual Service Request Creation for
Activities.
Application
FINANCIALS
Activity
SAIC
Application Area
VIM
VIM070500-03-CGD-EN-1
Man. Creat
Select the check box.
Request > Processing > Determine Service Request Attributes from
Application Context.
Application
FINANCIALS
Application Area
VIM
Trans. Type
SAIC
9. Based on the application area, you can perform some further settings, for
example determine service request attributes from the application context. For
example, you may want to populate the subject category fields. For more
information, see the SAP documentation of the IMG activities mentioned in this
section.
VIM070500-03-CGD-EN-1
Chapter 29
SRM Integration
SAP Supplier Relationship Management (SRM) automates, simplifies, and

accelerates procure-to-pay processes for goods and services. For details on SRM, see
http://www.sap.com/solution/lob/procurement/software/srm/index.html.
VIM supports the following scenarios for SRM related purchase order invoices:
• Missing goods receipt (GR) for SRM related purchase orders (SRM scenario
“Classic” and “Extended Classic”)
• Quantity discrepancy in invoice for SRM related purchase orders which requires
confirmation in the SRM system (SRM scenario “Classic”)
• Price discrepancy in invoice for SRM related purchase orders which requires
changes in the purchase order located in the SRM system (SRM scenario
“Extended Classic”)
See “Use Cases” on page 749 for details.
Note: For details about the scenarios, see “Configuring SRM Purchase Orders”
on page 753.
This chapter describes the activities necessary for configuring the SRM integration.
29.1 Use Cases

The following swimlane diagrams show the scenarios for SRM related purchase
order invoices:
VIM070500-03-CGD-EN-1
Chapter 29 SRM Integration
Figure 29-1: Goods Receipt Missing
VIM070500-03-CGD-EN-1
29.1. Use Cases
Figure 29-2: PO Quantity Block
VIM070500-03-CGD-EN-1
Figure 29-3: PO Price Block
29.2 Determining Purchase Order Types

First, you need to determine if a purchase order (PO) is an SRM related PO.
Therefore, you maintain the PO statuses that are related to SRM.
To determine purchase order types:
Invoice Management > PO Based Invoice Configuration > SRM Integration >
SRM PO Statuses.
VIM070500-03-CGD-EN-1
29.3. Configuring SRM Purchase Orders
2. Check the values in table EKKO, field STATU, for SRM related purchase orders
and maintain the appropriate statuses in the Constant Value field, separated by
semicolons.

The function module /OPT/S_DETERMINE_SRM_PO_TYPE uses this constant value
to determine if a purchase order is an SRM related purchase order.
Z constant The Z constant SRM_PO_CHECK for the product code LIX enables you to write custom
SRM_PO_CHE logic to determine if a particular PO is an SRM PO. You must write the custom logic
CK
in a custom function module. This function module is called from the standard
function /OPT/S_DETERMINE_SRM_PO_TYPE. Your custom function module must
have the same interface as the standard function module /
OPT/S_DETERMINE_SRM_PO_TYPE.
29.3 Configuring SRM Purchase Orders

This section covers the configuration steps for the SRM integration, according to the
scenarios:
• “Missing Goods Receipt Scenario” on page 754
• “Quantity Discrepancy Scenario” on page 754
• “Price Discrepancy Scenario” on page 756
• “SRM Scenario Type” on page 759
To access the respective menu items for this section, run the /N/OPT/SPRO
transaction and navigate to the menu path Vendor Invoice Management > PO
Based Invoice Configuration > SRM Integration.
VIM070500-03-CGD-EN-1
29.3.1 Missing Goods Receipt Scenario

If an SRM related invoice has a purchase order line item with activated GRIV flag
(Goods Receipt based Invoice Verification) and no goods receipt is posted, an email
will be sent to the SRM user (purchase order requester).
Process type VIM Baseline contains process type 162 for SRM. See “Configuring the Process
maintenance Type” on page 225 for details on maintaining the process type.
Verify that the following fields are maintained for the SRM process type:
• Workflow Type: SRM System Integration
• Max Retry Counter: Maximum number of retries to send the email for one PO
• Retry Time (Minutes): The email will be sent again after the time internally
maintained here if no Goods Receipt is posted meanwhile. For each time, the
counter is incremented by 1.
• Mail Config ID
• Function Module for Receiver Email, for example /
OPT/S_GET_SRM_USER_EMAIL_ID
• Function Module to send email, for example /OPT/S_DP_EMAIL_NOTIFICATION
Program to Schedule the program /OPT/CR_RERUN_RULES_JOB to clean up the work item

rerun rules waiting after the number of retries exceeds or the time limit from last run exceeds.
This program publishes the events PSS_Completed and
ProcessCompletedExternally which will complete the wait step. The business
rules will be rerun. After the number of retries exceeds or the wait period completes,
the work item will be routed to the AP Processor.
Option to send VIM Baseline contains the option ID 2740 which will enable the AP Processor to
email send an email to the SRM user. You can configure the email text based on the mail
configuration ID maintained in the process option. See “Configuring the SRM Mail
Infrastructure” on page 759 for details on how to maintain the email text.
29.3.2 Quantity Discrepancy Scenario

An invoice based on an SRM purchase order might be blocked due to quantity
discrepancy. In this case, an email will be sent to the SRM user (purchase order
requester) and the workflow will be in delay status.
In the quantity discrepancy scenario, you need to maintain the DP process type for
the Missing goods receipt scenario; see “Missing Goods Receipt Scenario”
on page 754. The SRM process type will be used to determine attributes like the
delay time and get the receiver email ID.
To configure the Quantity Block process type:
1. Run the SM30 transaction to maintain table /PTGWFI/Z_CONST, and locate the
record with Product Code LIX and Constant SRM_QTY_BLK_PROCTYPE.
VIM070500-03-CGD-EN-1
2. Enter the SRM Quantity Block process type in the Constant Value field. The
OpenText Baseline value is 162.
The maximum number of days (delay time) will be based on the process type.
The delay time will be calculated as the Maximum Number of retry time
multiplied by the Maximum Retry time limit.
The Email Receiver function module to get the receivers is also derived from the
process type.
To configure the mail configuration ID:

1. In the OpenText Configuration, under SRM Integration (see “Configuring
SRM Purchase Orders” on page 753), open SRM Quantity Block Mail config
ID.
2. Enter the mail configuration ID in the Constant Value field and save your
settings. For details on the mail configuration ID, see “Configuring the SRM
Mail Infrastructure” on page 759.
VIM070500-03-CGD-EN-1
You must determine the initial actor who will receive the work item after the wait
period completes.
To determine the initial actor:

SRM Purchase Orders” on page 753), open SRM Quantity Block Proxy Role.
2. Enter the initial actor's role in the Constant Value field and save your settings.
29.3.3 Price Discrepancy Scenario

For the price discrepancy scenario, the following conditions must apply:
• The invoice is based on an SRM purchase order.

• The SRM scenario type is “Extended Classic”.
• The invoice has a price block.
If these conditions apply, an email will be sent to the SRM requester to change the
purchase order. The workflow will be in wait status for the specified time, based on
the configuration. After the time has lapsed or the block has been removed, the work
item will be completed.
In this scenario, you must perform the following configuration steps.
The mail configuration ID is used for sending emails out. You can modify the actual
email content, see “Configuring the SRM Mail Infrastructure” on page 759.
To configure the mail configuration ID:

SRM Purchase Orders” on page 753), open SRM Price Block Mail config ID.
VIM070500-03-CGD-EN-1
2. Enter the mail configuration ID in the Constant Value field and save your
settings. For details on the mail configuration ID, see “Configuring the SRM
Mail Infrastructure” on page 759.
To configure the email receiver function module:

SRM Purchase Orders” on page 753), open SRM Price Block Email Func
Module.
2. Enter /OPT/S_GET_SRM_USER_EMAIL_ID in the Constant Value field and save

your settings.
The constant value function module determines the SRM user email.
You must determine the initial actor who will receive the work item after the wait
period completes.
VIM070500-03-CGD-EN-1
To determine the initial actor:

SRM Purchase Orders” on page 753), open SRM Price Block Proxy Role.
2. Enter the initial actor's role in the Constant Value field and save your settings.
After the workflow has sent an email to the SRM user, the workflow is in wait
status. You can configure the amount of time for the wait period.
To configure the wait period:

SRM Purchase Orders” on page 753), open SRM Price Block Delay days.
2. Enter the amount of time for the wait period (in minutes) in the Constant Value
field and save your settings.
VIM070500-03-CGD-EN-1
29.4. Configuring the SRM Mail Infrastructure
29.3.4 SRM Scenario Type

The SRM scenario type determines which SRM scenario you use. Possible values are
“Extended Classic” or “Classic”.
Note: For the price discrepancy scenario, only the “Extended Classic” SRM
scenario is relevant.
To configure the SRM scenario type:

SRM Purchase Orders” on page 753), open SRM Scenario type.
2. Enter EXTENDED_CLASSIC or CLASSIC in the Constant Value field and save your
settings.
29.4 Configuring the SRM Mail Infrastructure

The SRM mail infrastructure creates emails for the following SRM scenarios:
• Missing goods receipt scenario
• Quantity discrepancy scenario
• Price discrepancy scenario
Email body and email subject base on the business object type and object key.
Email format The SRM email notification can be sent in different formats. The format is configured
in Z Constant (product code 005) REM_MAIL_DOCTYPE . Default value is RAW. This
email format is used globally for all kind of email notification : Reminder
notification, Approval notification, and SRM notification.
The notification emails can be sent in HTML format with readable formatting and
invoice data presented in the form of HTML tables. To enable this functionality, you
VIM070500-03-CGD-EN-1
must set the constant 005 / REM_MAIL_DOCTYPE to HTM. In the /OPT/VIM_8CX50

transaction, you must configure the Email Type to be Internet Email.
The following screenshot shows the general format of the emails.
To configure the SRM mail infrastructure:

SRM Purchase Orders” on page 753), navigate to Mail Setup > Mail
Configuration.
2. To add a new entry in the Mail config definition overview screen, click New
Entries in the application tool bar.
VIM070500-03-CGD-EN-1
3. Define the mail configuration, using the following parameters:
Object type
Enter the VIM object type. The following values are possible:
/OPT/V1001
Object type for DP
/OPT/LIV
Object type for blocking
Text Block 1
Enter a text object for the email context header, like addressing and
description of the issue. For example, /OPT/VIM_DP_SRM_QTY_HEADER is a
text for the DP email header.
Note: You can maintain text objects using the SO10 transaction.
Text Block 2
Enter a text object for the URL Header; for example, /
OPT/VIM_DP_SRM_QTY_URL_HEAD.
Text Block 3
Enter a text object for the conclusion and/or the address of the email
generating location. For example, /OPT/VIM_DP_SRM_QTY_FOOTER is a text
for the email footer.
Include Image Attachment
Select this check box to attach the invoice image to the email.
URL Function Module
Enter the function module that will generate the URL for user reference.
This URL will contain the tracking information for the PO. For example, the
function module /OPT/CNOTIF_GET_URL_LIST populates the URL with the
VIM070500-03-CGD-EN-1
Importing parameters
I_MAIL_CFG_ID
Mail configuration ID
I_OBJTYPE
Object type
I_OBJKEY
Object key
Exporting parameters
T_URL
Table of URLs
URL
Enter a URL that is used in the mail body, in case the URL generating
function module is not maintained.
Line Item Function Module

Enter the function module that will populate the line item information and
construct the table. For example, the function module /
OPT/CNOTIF_GET_LINE_ITEM_DATA will populate the line item information
with the following parameters:
Importing parameters
I_MAIL_CFG_ID
Mail configuration ID
I_OBJTYPE
Object type
I_OBJKEY
Object key
I_GROUP_BY
Group by (used as SRM PO Requester in baseline)
Exporting parameters
T_LINE
Table parameter, with PO line item information
4. To configure the mail fields which need to be populated in the email content,
double-click Mail field list and description in the Dialog Structure panel.
VIM070500-03-CGD-EN-1
The list shows all object key fields that can be shown in the email. These fields
derive from the object type defined in Step 3 on page 761.
5. Maintain the field description.
Note: You can maintain the field description in different languages.

Therefore, log in using a different language.
6. To configure the mail subject line, double-click Mail subject/Title in the Dialog
Structure panel.
VIM070500-03-CGD-EN-1
Maintain the (language dependent) mail subject. The mail sending function
module will populate the appropriate subject if it is not set while invoking the
mail.
You must enable the email sending program to send invoice images as attachments
with the correct file extension. Therefore, you maintain the attachment extensions
for each archive object type.
To maintain the archiving image file extensions:

SRM Purchase Orders” on page 753), navigate to Mail Setup > Maintain
Archiving Image file extentions.
2. Enter the file extension for the archive object type.
VIM070500-03-CGD-EN-1
In the example, the Image File extension TIF is maintained for the archive
object type /OPT/ICC. For /OPT/ICC, invoice images will be archived and
attached to emails as *.TIF.
VIM070500-03-CGD-EN-1
Chapter 30
PDF Log
At various locations throughout VIM, a PDF log can be created. At the beginning of
the VIM process, it is possible to create PDFs of incoming IDocs. At the end of the
VIM process, it is possible to automatically create a PDF history log.
Note: If any issues occur during the creation of the PDF log, a log message is
written to the application log for the /OPT/VIM object with subobject DP. For
more information about the application log and how to display log messages,
see section 27 “Working with the Application Log” in OpenText Vendor Invoice
30.1 Customizing Profiles for the PDF Log

You configure the PDF log within a profile. This profile describes all settings for the
creation of the PDF log. You assign this profile to a VIM process step.

• “Defining Profiles for the PDF Log” on page 767
• “Assigning Profiles to VIM Process Steps” on page 769
30.1.1 Defining Profiles for the PDF Log

In this step, you configure the general profile settings used by the PDF log during
runtime.
To define the profile for the PDF log:

2. In the Define Profiles screen, define the profile, using the following parameters:
PDF Profile
Enter the unique ID of the profile.
Profile Description
Enter the description of the profile.
PDF Log Class

Enter the name of the class containing the logic for creation of the PDF log.
As an example, see the /OPT/CL_C_PDF_LOG class for the PDF history log,
which is delivered with the baseline.
VIM070500-03-CGD-EN-1
Chapter 30 PDF Log
You can enhance the baseline classes for the specific PDF log by redefining
components of the class within a custom class, which you can maintain
instead of the baseline class.
PDF Form Type
Enter the type of the PDF form.
There are different ways to create a PDF file in a SAP ERP system, for
example by creating a local spool request, by using SAP Script, SAP Smart
Forms, or SAP Interactive Forms by Adobe. SAP Smart Forms are included
in the baseline delivery. Currently, Smart Forms is the only available entry
for this field. However, it is also possible to redefine the logic of the PDF log
classes within custom classes to support other techniques, for example SAP
Interactive Forms.
Form Name
Enter the name of the SAP Smart Forms form.
As an example, see the /OPT/C_WORKFLOW_HISTORY01 SAP Smart Form for
the PDF history log, which is delivered with the baseline.
You can copy the SAP Smart Forms of the baseline using the smartforms
transaction and adjust them to your needs. You can maintain the adjusted
Smart Form in the Form Name box instead of the baseline Smart Form.
PDF Language
Select the language to be used for the PDF log. The following values are
available:
Fixed Language
A fixed language key is used for the PDF log. If you enter Fixed
Language, it is necessary to enter a value in the Language box.
Company Code Language

The language key of the company code of the DP document is used for
the PDF log.
System Language
The language key of the current system (sy-langu) is used for the PDF
log.
Language
If you have selected Fixed Language in the PDF Language field, enter the
language, for example EN, in this box.
PDF Timezone
Select the time zone to be used for time values in the PDF log. The following
values are available:
Fixed Time Zone
A fixed time zone is used for the PDF log. If you enter Fixed Time
Zone, it is necessary to enter a value for the Time Zone box.
System Time Zone

The time zone of the current system is used for the PDF log.
VIM070500-03-CGD-EN-1
30.1. Customizing Profiles for the PDF Log
Time Zone of Current User

The time zone of the current user (sy-zonlo) is used for the PDF log.
Time Zone
If you have selected Fixed Time Zone in the PDF Timezone field, enter the
time zone in this box.
Document type
Enter the archive document type to be used for archiving the PDF log.
Important
The document type must be different from the one used for the
invoice image.
Overwrite
Select this check box to overwrite PDF logs that have already been linked to
the DP document and its SAP invoice with the same archive document type.
Selecting the Overwrite check box deletes the physical PDF log and its links
to the DP document and the SAP invoice.
30.1.2 Assigning Profiles to VIM Process Steps

A VIM process step defines the point in time when the PDF log is created. Currently
there are two possible VIM process steps:
VIM process is finished

The VIM process is finished as soon as the DP document workflow is finished.
The VIM process history can be rendered to a PDF file.
Note: There are old scenarios (direct posting/direct parking scenario)

which do not have a DP document workflow running. In this case, this
process step is not triggered.
IDoc to PDF Invoice Creation

An invoice comes in through an IDoc. The mapped IDoc data can be rendered to
a PDF file.
To assign a profile to a VIM process step:

2. In the Dialog Structure, double-click Assign Profiles to VIM Process Steps.
3. In the Assign Profiles to VIM Process Steps screen, assign a profile to a

combination of VIM Process Step and Company Code.
If you leave Company Code empty, the setting is used for all company codes.
VIM070500-03-CGD-EN-1
Chapter 30 PDF Log
30.2 PDF Rendition of IDocs

You can use the PDF log to render PDF documents from incoming Idocs. For more
information, see “Rendering IDocs to PDF” on page 123.
30.3 PDF History Log

At the end of the VIM process, it is possible to automatically create a PDF log file
with history information of the VIM process. This PDF history log comprises the
logged process activities and approval activities of the DP document and its SAP
invoice. It also comprises the workflow log in case of blocked PO invoice items. All
comments that have been entered at any of the process and approval steps are
included in the PDF history log file.
The PDF history log file is archived and linked to the DP document and its SAP
invoice.
The following illustration shows an example of a PDF history log.
VIM070500-03-CGD-EN-1
30.3. PDF History Log
30.3.1 Customizing Profiles for the PDF History Log

You configure the PDF history log within a profile. This profile describes all settings
for the creation of the PDF history log. You assign this profile to a VIM process step.
You must specify that the PDF history log will be created at the end of the VIM
process. To enable the creation of the PDF history log, you must assign the profile
for the PDF history log (default profile: HISTORY) to the VIM process “VIM process
is finished”. Without this, the PDF history log will not be created at the end of the
VIM process.
Note: Within baseline delivery, a profile (HISTORY) is delivered, which

creates a PDF file with history information of the VIM process. This PDF file is
archived and linked to the invoice.
VIM070500-03-CGD-EN-1
Chapter 30 PDF Log
30.3.1.1 Defining Profiles for the PDF History Log

In this step, you configure the general profile settings used by the PDF history log
during runtime.
To define the profile for the PDF history log:

2. In the Define Profiles screen, define the profile. The following parameters are
specific for the PDF history log.
Note: For a description of the profile definition for PDF logs in general,
see “Defining Profiles for the PDF Log” on page 767.
PDF Log Class

The complete logic of the PDF history log is included in the PDF log class /
OPT/CL_C_PDF_LOG, which is delivered with the baseline. You can enhance
the class by redefining components of the class within a custom class, which
you can maintain instead of the baseline class.
Default value: /OPT/CL_C_PDF_LOG
PDF Form Type
Enter the type of the PDF form.
Currently, Smart Forms is the only available entry for this field. However, it
is also possible to redefine the logic of the PDF log class /
OPT/CL_C_PDF_LOG within a custom class to support other techniques, for
example SAP Interactive Forms.
Default value: Smart Forms
Form Name
Enter the name of the SAP Smart Forms form.
VIM070500-03-CGD-EN-1
30.3. PDF History Log
Baseline delivery includes a Smart Form /OPT/C_WORKFLOW_HISTORY01.

You can copy the Smart Form using the smartforms transaction and adjust
it to your needs. You can maintain this adjusted Smart Form in the Form
Name box instead of the baseline Smart Form.
The baseline Smart Form uses the SAP Smart Style /OPT/C_SF_STYLE01 for
the format options of the Smart Form, for example the font and the font size
of headers or default paragraphs. You can copy the Smart Style using the
smartstyles transaction and adjust it to your needs. Additionally, copy the
Smart Form and maintain your new Smart Style in the Output Options tab
of the Form Attributes screen of the Smart Form.
Default value: /OPT/C_WORKFLOW_HISTORY01
Document type
Enter the archive document type to be used for archiving the PDF history
log.
Note: Within baseline, the archive document type /OPT/PDF is

delivered. You must link the archive document type to the VIM
Business Object and to SAP Business Objects. For more information,
see “Linking Archive Document Types to the VIM Business Object”
on page 39 and “Linking Archive Document Types to SAP Business
Objects” on page 40.
Default value: /OPT/PDF
Overwrite
Select this check box to overwrite PDF history logs that have already been
linked to the DP document and its SAP invoice with the same archive
document type.
It is possible to create a PDF history log to a DP document manually by
using the /OPT/CR_PDF_LOG report. When using this report, a PDF history
log linked to the DP document and its SAP invoice can already exist.
For more details about the /OPT/CR_PDF_LOG report, see section 26
“Creating a PDF History Log File” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM-AGD).
Selecting the Overwrite check box deletes the physical PDF document (the
PDF history log) and its links to the DP document and the SAP invoice. This
PDF history log can either be created manually or automatically.
Default value: <selected>
VIM070500-03-CGD-EN-1
Chapter 30 PDF Log
30.3.1.2 Assigning the Profile to a VIM Process Step

For general information about assigning profiles to VIM process steps, see
“Assigning Profiles to VIM Process Steps” on page 769.
With baseline delivery, a profile (HISTORY) is delivered, which creates a PDF file
with history information of the VIM process.
To create this PDF history log at the end of the VIM process, you must assign the
profile to the VIM process is finished process step for your company codes. If you
leave Company Code empty, the setting is used for all company codes.
Note: The VIM process is finished process step is triggered only if there is a
DP document workflow running. This is not the case for the old direct posting
and direct parking scenario. If you want to create a PDF history log
nevertheless, use the /OPT/CR_PDF_LOG report. For more information about the
report, see section 26 “Creating a PDF History Log File” in OpenText Vendor
Invoice Management for SAP Solutions - Administration Guide (VIM-AGD).
VIM070500-03-CGD-EN-1
Part 5
Special Topics
Part 5 Special Topics
This part describes the configuration of VIM special topics, like VIM Notifications.
VIM070500-03-CGD-EN-1
Chapter 31
Background Posting of Non PO (FI) Invoices
VIM offers different ways of posting Non PO invoices in background. Each way has
its own advantages and limitations. This section discusses these ways, with the goal
to help you select the right way to post invoices. The posting BDC IDs that are listed
in this section correspond to the baseline configuration.
BDC ID 34, function module /OPT/DNONPO_INVOICE_BAPI

Most commonly used for Non PO posting, this function module is also used in
Invoice Approval and DP indexing screen to perform invoice data validation.
The document gets posted (or simulated) with the BAPI_ACC_DOCUMENT_POST
SAP BAPI. VIM performs all calculations. You can control the calculation logic
with a number of Z constants. Some specific scenarios are not supported by this
posting function. For more information, see Table 31-1: “Scenarios of posting
BDCs” on page 778.
BDC ID 41, batch input with the FB60 transaction

This posting BDC uses batch input data passed into the FB60 transaction. This
way is slower than the others but it supports some scenarios that do not work
with the BDC ID 34. In particular, this is the discount posting of net vendor
invoices.
BDC ID 42, function module /OPT/VIM_NPO_POST_VIA_LIV

This BDC is available since VIM 7.0 SP7 and VIM 7.5 SP3. To post GL account
lines, the BDC and the corresponding posting function module call the MM-LIV
BAPI function BAPI_INCOMINGINVOICE_CREATE or, if available,
BAPI_INCOMINGINVOICE_CREATE1. The BDC supports some new scenarios, see
Table 31-1: “Scenarios of posting BDCs” on page 778. Some scenarios are,
however, not supported when compared with other BDC IDs. The accounting
assignment of line items is limited to the fields that are supported by the SAP
BAPI functions, but the most commonly used fields are supported. For more
information, see the SAP BAPI documentation. This posting function creates an
LIV document in addition to the FI document. That LIV document is not shown
in VIM reporting whereas the FI document is shown everywhere.
Table 31-1: “Scenarios of posting BDCs” on page 778 lists some known scenarios
where the logic differs between the posting BDCs listed in this section. Use this table
as a guide when deciding which BDC ID is suitable for your process.
VIM070500-03-CGD-EN-1
Chapter 31 Background Posting of Non PO (FI) Invoices
Table 31-1: Scenarios of posting BDCs
Scenario/ BDC ID 34 BDC ID 41 BDC ID 42

function
Gross/net Gross and net Gross and net Net only
amounts on line
items
Profitability Supported Supported Not supported
segment
Discount posting Not supported Supported Supported
(net vendor
invoices, type
KN)
Posting to tax GL Not supported Not supported Supported
account
VAT date (tax Supported Supported Not supported
reporting date) (currently, SAP BAPI
does not support this)
Determination of VIM logic - tax Determination by the VIM logic - tax
default values jurisdiction code FB60 transaction jurisdiction code
determined from cost determined from cost
center, WBS element, center, WBS element,
and so on and so on
Calculation of tax All calculation is done Done by the FB60 Done by SAP LIV
lines in VIM. transaction BAPI
VIM070500-03-CGD-EN-1
Chapter 32
Tools
VIM provides some tools that help to use the application. The following tools are
available:
• “VIM Notifications” on page 779
• “Testing Roles” on page 779
• “Changing the Work Item Text” on page 781
• “Test Tools” on page 782
32.1 VIM Notifications

The VIM Notifications program provides an easy way to configure sending
notification emails to end users based on the process defined and a set of
configuration. For a detailed description of VIM Notifications, see “Using VIM
Notifications“ on page 783.
32.2 Testing Roles

You might want to test a particular role to see if it is working correctly, based on the
process type, invoice information, and responsible party. For this purpose you can
use the VIM Role Test Utility.
To test roles with the VIM Role Test Utility:
1. Run the /OPT/VIM_ROLETEST transaction.

> Roles > /OPT/VIM_ROLETEST – Role Test Utility.
2. Enter the relevant information for the role you want to test. For example:
Company Code, Document Number, and Responsible Party.
VIM070500-03-CGD-EN-1
Chapter 32 Tools
3. Click to execute the test.
The result for that role shows the default user maintained for this role:
REQUESTER1.
VIM070500-03-CGD-EN-1
32.3. Changing the Work Item Text
32.3 Changing the Work Item Text

You might want to change the text for a work item to match your business process.
This work item text is displayed as the title of a dialog task in the agent's SAP inbox.
In VIM, the following workflow dialog tasks are available:
TS00275253
Approve Invoice
TS00275260
Non-PO Invoice Dashboard
TS00275262
PO Parked Invoice Dashboard
TS00275265
PO Invoice Dashboard (Line Level)
TS00275267
PO Invoice Dashboard (Header WF)
TS00275278
DP Document Dashboard
TS00275283
Reference requested
This section describes the steps to change the text.
To change the work item text:
1. Run the /OPT/VIM transaction and navigate to OpenText Vendor Invoice

Management > SAP menu > WF Administration > /PTGWFI/M_LANG – WI
text update Utility
2. In the Multi Language Workitem Text Maintenance Utility screen, enter the
task ID (TS00275257 in the example) and press the ENTER key.
VIM070500-03-CGD-EN-1
Chapter 32 Tools
3. Select the Language that you want to view or modify.
4. Change the text in the Task Text field and click the Update button.
32.4 Test Tools

This section lists some tools that you can use to start a DP process for test purposes.
Important
Actually, these tools are internal tools. Although you can use them,
OpenText does not provide customer support for these test tools.
Transaction /OPT/VIM_7AX1
Non-OCR Scenario
OCR Scenario
OCR Test Utility
VIM070500-03-CGD-EN-1
Chapter 33
Using VIM Notifications
The VIM Notifications program (called VIM Reminder in earlier versions) provides a
way to remind users about the invoices waiting in their inbox to be processed. The
program sends email notifications for all overdue invoices and for invoices that have
spent a particular number of days in the user inbox. You can customize the number
of days.
To start the VIM Notifications program, run the /OPT/REMINDER transaction. The
program is typically scheduled as a batch job so that the agents get notifications of
their reminders regularly.
This chapter covers the following topics:

• “Working with the Selection Screen” on page 783
• “Working with the VIM Notifications List” on page 786
• “Configuring VIM Notifications” on page 789
• “Maintaining a Notification Email Formatting Function Module” on page 797
33.1 Working with the Selection Screen

All functions of VIM Notifications are controlled via a common selection screen.
To work with the VIM Notifications selection screen:
1. Run the /n/OPT/REMINDER transaction.

The VIM Notifications selection screen is displayed.
VIM070500-03-CGD-EN-1
Chapter 33 Using VIM Notifications
The selection screen allows you to enter search criteria and process options. The
selection screen is divided into the following panels:
• Invoice Information
• Document Process
• Workitem Date Range
• Process Options
• Recipient of Reminder
2. Enter search criteria, using the following parameters:
Tip: Where applicable, use for multiple selection and for search
help.
VIM070500-03-CGD-EN-1
33.1. Working with the Selection Screen
Invoice Information panel
• Company Code
• Document Number
• Fiscal Year
• Line Item
Document Process panel

Enter search criteria for Document Processing (DP) information:
• Document ID: the number that was generated for the document during
the DP process
Workitem Date Range panel

Enter search criteria for work item information:
• Workitem Creation Date
Recipient of Reminder panel

Enter search criteria to filter the list of notifications for specific users:
• SAP User ID
• OpenText User Id
Note: When adding user IDs as search criteria, the system does not
consider the substitutes for the user, if there are any.
3. Select processing options, using the following parameters:
Process Options panel

This panel comprises the following parts:
Scenario
Select the corresponding check box(es) to include work items of the
following types:
• Document Processing
• PO Block Invoices - Header
• PO Block Invoices – Line
• PO Parked Invoices
• NPO Parked Invoices
• PO Approval Inv. (Parked/DP)
• NPO Approval Inv. (Parked/DP)
• PO Referred Invoices
• NPO Referred Invoices
VIM070500-03-CGD-EN-1
Mode
Select one of the process modes:
Test
The program generates a list of eligible work items for notification.
The program does not send the notifications. Users can select the
work items to send the notification.
Background
The program sends the notification to users and displays the work
items.
4. Once you finished entering the search criteria and selecting the process options,
click in the application tool bar to display the VIM Notifications List with
the search results.
33.2 Working with the VIM Notifications List
The VIM Notifications List comprises the following sections:

• “Application Tool Bar” on page 787
• “ALV Grid Control” on page 787
• “ALV Grid (Data View)” on page 788
VIM070500-03-CGD-EN-1
33.2. Working with the VIM Notifications List
33.2.1 Application Tool Bar

The application tool bar comprises the following buttons:
Send Notification
To send an email or an SAP note to an agent, select the agent in the list and click
the Send Notification button.
SAPconnect
To run the SCOT transaction, click the SAPconnect button.
The SAPconnect Administration (system status) screen is displayed.
SAPconnect allows the connection of external communication components to the
SAP ERP system.
33.2.2 ALV Grid Control

The ABAP list viewer (ALV) is a standard SAP tool to show table data inside SAP
ERP. The functions listed in this section also apply to other lists in ALV mode. The
following function buttons are available:
Details: Select a line in the list and click this button to display details for the
selected line.
, Sort: Select a report column in the list and click one of these buttons to sort it in
either ascending or descending order.
Find: Click this button to open the Find dialog that allows you to search the list
for any keyword.
Filter: Select a report column in the list and click this button. The Filter criteria
dialog is displayed, allowing you to restrict the criteria in the selected column
without having to rerun the report with new search criteria.
VIM070500-03-CGD-EN-1
Tip: Use for multiple selection.
Layout: Click this button to select a saved layout. To change, save or manage
layouts of the list, click the icon next to the Layout button.
33.2.3 ALV Grid (Data View)

The ALV grid is the actual list of work items that match the search criteria. In the
ALV grid, the following report columns are available:
Notes
• The following list only covers columns whose meaning is not obvious.
• Some of the column headers might be abbreviated. Expand the column to see
the full text.
• The columns might not be displayed or might not be in the following
sequence. You can add or remove columns, or change the sequence by using
the Layout function, see “ALV Grid Control” on page 787.
Column Description
Current Agent Current agent who owns items
Process Type Type of the document (DP, PO document, Non PO document…); see the
list in Scenario on page 785.
VIM070500-03-CGD-EN-1
33.3. Configuring VIM Notifications
Sub Process Sub Process Type for each process type, for example Approval
Type Required for Non PO Invoice Approval process type
Document SAP document number
Number
Document ID DP document ID
Vendor Vendor number
Name 1 Vendor name
Inbox Days Number of days the work item lies in the inbox
Before Due Days before the due date of the work item
Due Date Due date of the work item
First name First name of the current agent
Last name Last name of the current agent
Responsible Role that is responsible for the work item
Party
Receiver ID Email address of the current agent
ID Work item ID
33.3 Configuring VIM Notifications

Configuring the VIM Notifications program comprises the following actions:
• “Configuring Notification and Email Options” on page 789

• “Configuring the Notification Email Body” on page 792
• “Configuring the Notification Email Title” on page 794
• “Excluding Notification Users” on page 794
• “Configuring User Preferences” on page 796
• “Configuring Email Format” on page 797
33.3.1 Configuring Notification and Email Options

You can configure several options for VIM Notifications and the corresponding
emails.
To configure notification and email options:
1. To access the Process Configuration screen, run the /n/OPT/VIM_8CX50

transaction.
2. To edit an existing notification, mark the respective line in the Process

Configuration Overview screen, and click the button in the application tool
bar. See the parameter description in Step 3.
VIM070500-03-CGD-EN-1
Note: You cannot change the Notification Type and the Notification Sub
Type for an existing notification.
3. To add a notification, click the New entries button in the application tool bar.
Configure the notification, using the following parameters:
Notification Type
Select the notification scenario. Possible values:
• Document Processing
• PO Parked Invoices
• PO Blocked Invoices - Line Level
• PO Blocked Invoices - Header Level
• NPO Parked Invoices
• NPO Approval Invoices (Parked/DP)
• PO Approval Invoices (Parked/DP)
• NPO Referred Invoices
• PO Referred Invoices
Notification Sub Type

Select the notification sub scenario. Possible values depend on the selected
notification scenario.
Example: Notification sub scenarios for the NPO Parked Invoices notification
scenario:
• Approval Required
• Vendor Maintenance
VIM070500-03-CGD-EN-1
• Vendor Audit Required

• Tax Audit Required
• All Scenarios
Responsible Party
Select the role for the notification. All users assigned to this role will receive
the notification.
Notify Substitutes
Select this check box to have all notifications also sent to substitutes of users
that receive the notification.
Notify Manager, Notification Counter

The notification program enables you to also inform the manager about
approval work items that are too long in the inbox of an approver. This
configuration is available for the Approval and Referred notification types.
Select the Notify Manager check box, to send the notification email in CC to
the related manager, too.
In the Notification Counter field, enter the number of notification mails
that have been sent to a user, before a notification mail is sent to the
manager, too. Therefore only one invoice needs to be over the limit in the
list of invoices which the notification program collects.
For the level based approval, it is also possible to configure the manager
within COA. The manager will only be used for the notification escalation
processing but not for any approval processing logic.
Inbox Days, Days Before Payment Due

Use these two fields to decide if the reminder will be sent. The system
calculates the work item creating date plus the inbox days or the days
before payment is due. If the result is less or equal today's date, then a
reminder will be sent.
Email Type
Select the notification type. At the moment, only Internet Email is
available.
Notification Text
Select the SAP text name to be used for the notification email body.
Notification Receiver Function

Select the function module that determines the email address for the
notification. The interface for this function module is same as for the /
OPT/VIM_NOTIF_EMAIL_ADDRESS function module.
Note: The Notification Receiver Function is only applicable for NON

approval scenarios.
If you select a different function model in this field, VIM Notifications will
run this function module first. If the function module cannot find a valid
VIM070500-03-CGD-EN-1
email address, VIM Notifications will run the default function module /
OPT/VIM_NOTIF_EMAIL_ADDRESS.
4. To save your changes, click .
33.3.2 Configuring the Notification Email Body

The VIM Notifications report will create a list in the email body. The displayed fields
in this list depend on the specifications you enter in the Mail Configuration screen.
To configure the notification email body:
1. To access the Mail Configuration screen, run the /OPT/VIM_8CX50 transaction

and double-click Mail Configuration in the Dialog Structure panel.
2. Configure the notification email body, using the following parameters:
Field name
You find the field names in structure /OPT/VIM_S1_REMINDER_MAILBODY.
Each field name represents a column in the generated VIM Notifications
email.
Note: You cannot change this parameter in the Mail Configuration

screen.
Language
VIM supports the following languages:
• Czech (CZ)
VIM070500-03-CGD-EN-1
• German (DE)
• English (EN)
• Spanish (ES)
• French (FR)
• Hungarian (HU)
• Italian (IT)
• Japanese (JA)
• Dutch (NL)
• Polish (PL)
• Portuguese (PT)
• Romanian (RO)
• Russian (RU)
• Slowakian (SK)
Note: The Slowakian translation does not include KPI Dashboard

and Central Reporting.
• Turkish (TR)
• Chinese (ZH)
Note: You cannot change this parameter in the Mail Configuration

screen.
Position
Specify the sequence of the fields in the email body.
Field Length
Specify the length of the field.
If you leave Field Length empty, the system uses the Length parameter
from structure /OPT/VIM_S1_REMINDER_MAILBODY, which contains the
email body fields.
Text
Enter the title for each field in the respective language.
VIM070500-03-CGD-EN-1
33.3.3 Configuring the Notification Email Title

You must configure a title for the notification email.
To configure the notification email title:
1. To access the Mail Title Configuration screen, run the /OPT/VIM_8CX50

transaction and double-click Mail Title Configuration in the Dialog Structure
panel.
2. Configure the notification email title, using the following parameters:
Language
For a list of languages that are supported by VIM, see Language
on page 792.
Notes
• You cannot change this parameter in the Mail Title Configuration
screen.
Mail Title
Enter the title of the notification email in the respective language(s).
33.3.4 Excluding Notification Users

Based on the specification in table /opt/t853, VIM Notifications will exclude users
from the user list when sending emails.
The following ways of excluding users are available:

• excluding named users
• disabling and enabling the exclude status for oneself
To exclude named users:
VIM070500-03-CGD-EN-1
2. To exclude another user, click the New entries button in the application tool bar
of the Excluded Receivers for Notifications Overview screen.
3. Specify the user to be excluded, using the following parameters:
User Type
Select SAP User Id or OpenText User ID from the list.
User Id
Enter the user ID to be excluded, corresponding to the selected user type.
Disable Notification
Mark this field with X to disable VIM Notifications emails.
Single Notification
Mark this field with X to have VIM Notifications emails sent only once per
work item instead of multiple times during the notification period.
Language Pref
on page 792.
To disable and enable the exclude status for oneself:
Follow the description in “Configuring User Preferences” on page 796.
VIM070500-03-CGD-EN-1
33.3.5 Configuring User Preferences

You can configure some personal preferences for VIM Notifications.
Note: The preferences are set for the currently logged-in user.
To configure user preferences:
1. Run the /OPT/VIM_8AX50 transaction.
2. Configure notification preferences, using the following parameters:
Disable Notification
Select this check box if you want to receive no VIM Notifications emails
regarding the SAP inbox or Web Approval.
Clear the check box to receive VIM Notifications emails.
Single Notification (One Time Reminder)

Select this check box if you want to receive only one VIM Notifications
email for a SAP inbox or Web Approval work item.
Clear the check box to receive VIM Notifications emails more than once,
regarding the same work item.
User Language
on page 792.
VIM070500-03-CGD-EN-1
33.4. Maintaining a Notification Email Formatting Function Module
33.3.6 Configuring Email Format

You can configure the email format in the Z Constant (product code 005)
REM_MAIL_DOCTYPE. This format is used globally for all types of email notification,
like Reminder notification, Approval notification, and SRM notification. The default
value is RAW.
The notification emails can be sent in HTML format with readable formatting and
invoice data presented in the form of HTML tables. To enable this functionality, you
must set the constant 005 / REM_MAIL_DOCTYPE to HTM. In the /OPT/VIM_8CX50
transaction, you must configure the Email Type to be Internet Email.
33.4 Maintaining a Notification Email Formatting

Function Module
You can modify VIM Notifications email messages before sending by maintaining a
custom formatting function module.
To maintain a notification email formatting function module:

Enter /PTGWFI/Z_CONST in Table/View and click Maintain.
2. Access the constant corresponding to Product Code 005 and Constant

REM_MAIL_FORMAT_FM.
The default value is None.
3. Enter your custom notification email formatting function module in Constant

Value.
To get the necessary interface definition, you can copy the template function
module /OPT/VIM_NOTIF_EMAIL_FORM_TEMP.
VIM070500-03-CGD-EN-1
Chapter 34
Data Archiving Configuration
In the context of VIM, archiving only considers the VIM data tables of:
• DP invoices
• Reporting data from Central Reporting
For a list of tables you can archive data from and a short description of the archiving
process itself, see section 20 “Archiving VIM Information” in OpenText Vendor Invoice
You should use archiving, if one of the following applies:

• The data size of the VIM tables has increased to an extent that reduces the
performance of the database.
• The old transaction data is not relevant anymore and not accessed regularly.
Important
OpenText recommends archiving data of the VIM tables only, when the data
is not required in everyday tasks and it is not relevant from auditing
perspective. Make absolutely sure that you run license reporting before you
archive data. Otherwise, you might lose data that is needed for license
reporting. For more information, see section 21.1 “Using the ICC and VIM
License Report” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD).
Notes
• Once the data is archived, all reports and transactions will not be able to
show the data anymore. However, VIM Baseline provides a program to
reload the data into the database: Run the SARA transaction, and enter
archiving object /OPT/DOC. On the Goto menu, click Reload.
• There are no known dependencies on data archiving of standard SAP objects
like invoice documents, workflow logs, archive link entries, and so on.
Regarding archiving, you can perform the following configuration.

• “Configuring Archiving of DP Documents” on page 800
• “Configuring Archiving of Central Reporting Information” on page 802
VIM070500-03-CGD-EN-1
Chapter 34 Data Archiving Configuration
34.1 Configuring Archiving of DP Documents

You have the archiving object /OPT/DOC in your system. Follow the standard SAP
archiving procedures for archiving DP documents.
To configure archiving of DP documents:
1. Use the standard SAP transaction FILE to create the logical file name. The
logical file name is needed in Step 5.
2. To invoke the View Cluster Maintenance screen, run the AOBJ transaction.
3. Select Archiving Object /OPT/DOC and click .
Important
Do not change the Structure Definition of the archiving object; see the
following screenshot. This would cause inconsistency between the
programs and the structure.
VIM070500-03-CGD-EN-1
34.1. Configuring Archiving of DP Documents
4. Double-click Customizing Settings in the navigation panel.
VIM070500-03-CGD-EN-1
5. Assign the logical file name created in Step 1 to the archiving object in the
Logical File Name field.
6. Enter the customizing settings for the archiving object for Archive File Size and
Settings for Delete Program according to your requirements.
Note: The Baseline settings provided are for guidance only.
34.2 Configuring Archiving of Central Reporting

Information
You have the archiving object /OPT/REP in your system. Follow the standard SAP
archiving procedures for archiving the reporting tables.
Note: You must first archive the DP documents and then archive the reporting
information of the DP documents. If you do not archive the DP documents
first, the data is populated back to the reporting tables again, when the
background jobs scheduled to collect data for the reporting tables are executed.
To configure archiving of Central Reporting information:
1. Use the standard SAP transaction FILE to create the logical file name, see Step 5.
VIM070500-03-CGD-EN-1
34.2. Configuring Archiving of Central Reporting Information
2. To invoke the View Cluster Maintenance screen, run the AOBJ transaction.
3. Select Archiving Object /OPT/REP and click .
Important
Do not change the Structure Definition of the archiving object, see the
following screenshot. This will cause inconsistency between the
programs and the structure.
VIM070500-03-CGD-EN-1
4. Double-click Customizing Settings in the navigation panel.
VIM070500-03-CGD-EN-1
34.2. Configuring Archiving of Central Reporting Information
5. Assign the logical file name created in Step 1 to the archiving object in the
Logical File Name field.
6. Enter the customizing settings for the archiving object for Archive File Size and
Settings for Delete Program according to your requirements.
Note: The Baseline settings provided are for guidance only.
VIM070500-03-CGD-EN-1
Chapter 35
Rerunning Waiting Process Types
The process types within a wait step can be monitored. You can execute the
corresponding process types again, or you can finish the wait step manually.
To start the respective program, run the /OPT/VIM_RULERUN transaction. The

program is typically scheduled as a batch job so that processing of the waiting rules
is executed in background. For more information, see “Program: /OPT/
DR_BR_WAIT” in section 5.1 “Scheduling Batch Jobs for Workflows” in OpenText
Vendor Invoice Management for SAP Solutions - Administration Guide (VIM-AGD).
35.1 Working with the Selection Screen

1. Run the /n/OPT/VIM_RULERUN transaction.
VIM070500-03-CGD-EN-1
Chapter 35 Rerunning Waiting Process Types
2. Enter search criteria and select options.
Invoice Information, Process Information

You can search for the corresponding processes according to invoice
information and process information.
Rerun waiting in dialog, Rerun waiting in background
To rerun all waiting process types, either in dialog or background, click the
respective button.
Note: If you want to execute the program in background for the

waiting rules, set the corresponding parameters Rerun waiting in
background and Write log background processing.
Rerun non waiting in background

To execute all process types (waiting rules excluded) of any running DP
workflow, click this button.
VIM070500-03-CGD-EN-1
35.2. Working with the Monitor List
If you use the Rerun non waiting in background option, the following
search fields are not processed for the execution of the program:
• Date of status creation

• Time of status creation
• Status Wait / Rerun
3. When you have finished entering the search criteria and selecting the process
options, click in the application tool bar to display either the dialog result list
or to execute the report in background.
35.2 Working with the Monitor List
The Monitor list shows all entries for the waiting rules according to your selection.
The Monitor list highlights (in green) all process types where the waiting step has
already been finished.
The Monitor list provides access to the business data and the monitoring processing
of the rerun execution like the following:
• Status of rerunning the process type
• Creation timestamp of waiting process type
• Change timestamp of execution
The status can have the following values:
1
Wait step created
2
An error occurred during rerun execution, for example the terminating event of
the task could not be processed.
6
Process was skipped / reassigned manually.
7
Exception occurred again during rerun processing.
VIM070500-03-CGD-EN-1
Chapter 35 Rerunning Waiting Process Types
8
Period exceeded and process type was skipped / reassigned.
9
Process type was executed successfully.
Within the list, you can mark one or many entries. For the marked entries, you can
perform the following actions, using the buttons:
Rerun Process Type

Click this button to execute the rule again and change the status accordingly and
change the timestamp (entries with status 9 and 8 and 6 will not be processed).
Reassign / Skip Process Type

Click this button to end the process type. According to the configuration, the
process continues with the next process type within sequence processing (skip).
Alternatively, the process type must be resolved manually by the initial actor for
this process type.
VIM070500-03-CGD-EN-1
Glossary
AAK
See SAP Add-On Assembly Kit (AAK).
After Image
Technical option to realize an delta upload from the source systems into the SAP
NetWeaver BW system. A data record loaded as After Image provides the status
of the record after it has been changed, or after data has been added.
Aging Report
Part of the Central Reporting infrastructure. The Aging Report reports about the
aging of documents and work items in the current system.
AP processor
Accounts Payable personnel
Application Component Hierarchy
Hierarchy of folders to structure DataSources in SAP NetWeaver BW.
Approval chart of authority (COA)
The Approval chart of authority (COA) determines first approver and next
approver for an invoice by combinations of Company Code (specific or range),
Expense Type (marketing expense, utility), Cost Objects (G/L account, Cost
Center), and HR objects (Position, Job code).
Approval Portal
VIM web interface for approving invoices.
Archive system
Computer system that enables storage, management and retrieval of archived

data and documents
ArchiveLink document types
Document types that need to be customized for ArchiveLink
ArchiveLink
Service integrated in the SAP NetWeaver Application Server ABAP for linking
archived documents and the application documents entered in the SAP ERP
system
VIM070500-03-CGD-EN-1
Glossary
Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can perform in the SAP ERP system. These authorizations are
stored in Authorization profiles.
Automation Report
Tool that provides data about automated and manual processing steps of VIM
documents
BAdI
See Business Add-Ins (BAdI).
BAPI®
SAP programming interface: Business Application Programming Interface
Baseline
Set of functionality with pre-defined configuration and the starting point to

implement VIM
BasisCube
See InfoCube.
BDC ID
Business Data Communication ID. The BDC ID is used by the system to process
an SAP transaction to create an SAP Document in user context.
Block
Situation where an invoice has a price or quantity variance that prevents invoice
from posting
BTE
See Business Transaction Event (BTE).
Business Add-Ins (BAdI)
Business Add-Ins (BAdI) is an SAP enhancement technique based on ABAP

objects. BAdI can be inserted into the SAP ERP system to accommodate user
requirements too specific to be included in the standard delivery.
Business rules
Rules that describe the operations, definitions and constraints that apply to an
organization
Business Transaction Event (BTE)
Event used for extending a Non PO invoice functionality to call a custom program
VIM070500-03-CGD-EN-1
Glossary
Buyer
Person who is in charge of the PO. This role should have authorization to create
and change the purchase order. This role is also responsible for negotiating and
communicating with vendors.
Central Audit Report
Part of the Central Reporting infrastructure. The Central Audit Report is a

slimmed VIM Analytics (VAN). The main difference to VAN is that the Central
Audit Report serves as a single point of access in a multiple backend scenario.
Central Reporting
Reporting infrastructure that provides several reports that enable you to measure
certain properties of VIM documents and their work items, in order to optimize
working with VIM. Central Reporting comprises the following individual reports:
Aging Report, Central Audit Report, Exception Analysis Report, Key Process Analytics
Report, Productivity Report, and Summary Report.
Characteristic
Type of InfoObject in SAP NetWeaver BW that represents descriptions of fields,

such as Vendor ID, Invoice Number, Unit of Measure, and Posting Date.
COA
See Approval chart of authority (COA).
Coding
Coding allocates an invoice to G/L account and cost object if required.
Contract agent
Person who can create and modify SAP contracts.
Dashboard
User interface that organizes and presents information in a way that is easy to
read. Users can also perform actions from the dashboard.
Data Transfer Process (DTP)
Object in SAP NetWeaver BW to transfer data from source objects to target objects
DataSource
Set of fields in SAP NetWeaver BW that provide the data for a business unit for
data transfer to the SAP NetWeaver BW system; technically, it contains an extract
structure and an extraction function module.
VIM070500-03-CGD-EN-1
Glossary
DataStore Object (DSO)
Storage location for consolidated and cleansed data in SAP NetWeaver BW
DocuLink
OpenText™ DocuLink for SAP Solutions enables the archiving, management and
retrieval of SAP CRM or SAP ERP documents from within the SAP infrastructure.
Document Processing (DP)
VIM component that captures invoice metadata including line items for PO and
performs preconfigured business rules
Document type
Type of document such as PO, Non PO, OCR, Non OCR
DP
See Document Processing (DP).
DSO
See DataStore Object (DSO).
DTP
See Data Transfer Process (DTP).
Duplicate analyzer
Person who is responsible to identify duplicate invoices
EDI
See Electronic Data Interchange (EDI).
Electronic Data Interchange (EDI)
Method for transferring data between different application systems in the form of
messages. SAP applications support EDI with messages sent in an SAP
Intermediate Document (IDoc) format. VIM supports the creation of vendor
invoices through the EDI/IDoc interface.
Event Type Linkage
Error handling method. Event Type Linkage determines what the application
should do in case an error could not be handled.
Exception Analysis Report
Part of the Central Reporting infrastructure. The Exception Analysis Report

reports all work items with exceptions, grouped by exception, company code or
vendor.
VIM070500-03-CGD-EN-1
Glossary
Exception
Action that is not part of normal operations or standards
FI
See Financial Accounting (FI).
Financial Accounting (FI)
SAP module for the Finance and Accounting department
IAP
See Invoice Approval (IAP).
ICC
See Invoice Capture Center (ICC).
IDoc
See Intermediate Document (IDoc).
IE
See Invoice Exception (IE).
Indexer
Person responsible for entering index data
Indexing
Process of entering or storing data into the system
InfoArea
Folder in SAP NetWeaver BW to organize InfoCubes, DataStore Objects, InfoObjects,

and InfoObject Catalogs
InfoCube
Self-contained dataset in SAP NetWeaver BW, for example, of a business-oriented

area; an InfoCube is a quantity of relational tables arranged according to the
enhanced star schema: A large fact table in the middle surrounded by several
dimension tables
InfoObject Catalog
Folder structure in SAP NetWeaver BW to organize InfoObjects
InfoObject
Smallest information unit in SAP NetWeaver BW. Key figures and Characteristics
are collectively called InfoObjects.
VIM070500-03-CGD-EN-1
Glossary
InfoPackages
Object in SAP NetWeaver BW that specifies when and how to load data from a
given source system to the SAP NetWeaver BW system
InfoProvider
Object in SAP NetWeaver BW for which queries can be created or executed.

InfoProviders are the objects or views that are relevant for reporting.
Information provider
Receiving role for option Refer for Information
Intermediate Document (IDoc)
Standard SAP message document format for the EDI interface.
Invoice Approval (IAP)
VIM component that enables users to perform coding, approving and rejecting
invoices
Invoice approver
Person who approves invoices
Invoice Capture Center (ICC)
Optional VIM OCR component
Invoice characteristic
A value specific to each invoice (for example country) that allows flexible
processing in VIM. An invoice characteristic is determined during runtime and
depends on the corresponding index data of the document.
Invoice coder
Person who enters the accounting info on invoices to allocate the cost
Invoice Exception (IE)
VIM component that handles the exceptions that arise after an SAP invoice is
created
Invoice requester
Person who requested goods and services for Non PO invoices
Key Figure
Type of InfoObject in SAP NetWeaver BW that represents numeric values or

quantities, such as Number of Invoices and Gross Invoice Amount.
VIM070500-03-CGD-EN-1
Glossary
Key Process Analytics Report
Part of the Central Reporting infrastructure. The Key Process Analytics Report
reports about a variety of key figures regarding the VIM process: It shows the
accumulated amounts of all documents in the DP workflow, in parked state and
in posted state.
KPI Dashboard
Tool for managers showing VIM related process data at a glance in graphical
charts.
LIV
See Logistic invoice (LIV).
Logistic invoice (LIV)
purchase order invoice
Materials Management (MM)
Materials management module of the SAP ERP software package. Materials

management is used for procurement and inventory management.
MM
See Materials Management (MM).
Mobile Approval Portal
VIM component for approving invoices on mobile devices.
MultiProvider
Object in SAP NetWeaver BW that is based on InfoCube(s), DataStore Object(s),

and/or InfoObject(s). A MultiProvider is used as a layer for the creation of end user
queries; the MultiProvider itself does not contain any data; rather, data resides in
the BasisCubes.
Namespace
Name range reserved by SAP for customer objects and SAP objects to make sure
that objects are not overwritten by SAP objects during the import of corrections or
an upgrade
Non purchase order (Non PO)
Order that is not based on a PO
Non purchase order (Non PO) invoice (PIR)
Invoice based on a Non purchase order (Non PO)
VIM070500-03-CGD-EN-1
Glossary
Number range
Array of numbers that can be used for an object in the SAP ERP system
OCR
See Optical character recognition (OCR).
Optical character recognition (OCR)
Mechanical or electronic translation of images of handwritten, typewritten or

printed text (usually captured by a scanner) into machine-editable text
Park
Situation where an invoice is not posted and is waiting for further processing
Parked invoice document
Temporary document that the AP processor can change and post. SAP assigned
document number becomes real number when posted.
Persistent Staging Area (PSA)
Data staging area in SAP NetWeaver BW. It allows to check data in an

intermediate location before the data is sent to its destinations in SAP NetWeaver
BW.
PIR
See Non purchase order (Non PO) invoice (PIR).
PO
See Purchase order (PO).
Posted invoice document
Invoice that has already been posted in SAP ERP. Only free-form text fields can
be changed. Related documents such as POs or good receipts may be created or
changed to effect the invoice. If the document is not needed, it must be cancelled
( PO invoice) or reversed ( non-PO invoice).
Price variance
Situation where the price on the invoice is different from the price in the purchase
order
Process Chain
Sequence of processes in SAP NetWeaver BW that are scheduled to wait in the

background for an event; used to automate, visualize and monitor the processes.
VIM070500-03-CGD-EN-1
Glossary
Process options
Processing options for the user in the dashboard, such as Referral, Authorization,
and Actions
Process type
Process type for a document. The process type determines the initial actor and
various collaboration options available to the various actors during the process
flow.
Productivity Report
Part of the Central Reporting infrastructure. The Productivity Report reports

about the productivity of users/roles and the activities of users/roles.
PSA
See Persistent Staging Area (PSA).
Purchase order (PO) invoice
Invoice based on a Purchase order (PO)
Purchase order (PO)
SAP module. PO indicates a document sent from a buyer to a seller. The purpose
of the document is to order the delivery of goods or services.
Quantity variance
Situation where the quantity on the invoice is different from the quantity in the
purchase order
Receiver
Person who can create and reverse the goods receipt in SAP ERP
Requisitioner
Person who requested goods and services
Roles
Set of predefined roles for the SAP user
SAP Add-On Assembly Kit (AAK)
Standardized delivery procedure for software
SAP Customer Relationship Management (SAP CRM)
SAP application that provides software for ticket systems, for example in the
Accounts Payable department.
VIM070500-03-CGD-EN-1
Glossary
SAP NetWeaver Business Warehouse (SAP NetWeaver BW)
SAP application that allows to integrate, transform, and consolidate relevant

business information from productive SAP applications and external data
sources.
SAP Shared Service Framework
SAP software that contains a rich set of tools to improve and automate Shared
Service Center operations.
SAP Supplier Relationship Management (SAP SRM)
SAP application that automates, simplifies, and accelerates procure-to-pay

processes for goods and services.
Scan operator
Person who scans the invoices into images (may not have a SAP ID)
Service approver
Person who approves a service entry
Service requisitioner
Person who enters a service entry
Summary Report
Part of the Central Reporting infrastructure. The Summary Report provides a

summary of all documents processed through VIM.
Swimlane
Diagram representing a specific VIM process. A swimlane comprises the process

description, roles, user interface and options of the process.
Tax expert
Person who advises on invoices that need tax audit. Normally tax department
personnel.
Transformation (TRF)
Object in SAP NetWeaver BW to connect source objects to data targets; it allows

to consolidate, cleanse and integrate data
TRF
See Transformation (TRF).
VAN
See VIM Analytics (VAN).
VIM070500-03-CGD-EN-1
Glossary
Vendor Invoice Management (VIM)
Packaged business solution that solves a business problem – paying correct

amount to vendors on-time and with the lowest cost. VIM delivers not technology
but best-practice business processes. VIM provides values to customers in process
efficiency, visibility and compliance.
Vendor maintenance
Person who is responsible for creating and maintaining the vendor master
records
VIM Analytics (VAN)
VIM component that gives users a clear data report on their invoices in progress.
VIM Analytics allows to track the documents routed through SAP workflows via
VIM.
VIM Workplace
Tool for VIM super users, which allows users to display lists of their work items
that meet a selection they have entered before. Users also can display work items
of other users and of their team as a whole.
Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP ERP system.
VIM070500-03-CGD-EN-1

OpenText VIM 7.5 SP3 - Config Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText VIM 7.5 SP3 - Config Guide

Uploaded by

Copyright:

Available Formats

OpenText™ Vendor Invoice Management

for SAP® Solutions

The OpenText™ Vendor Invoice Management for SAP®

40 Avenue Monterey , Luxembourg, Luxembourg L-2163

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

No Warranties and Limitation of Liability

1 About This Document ............................................................. 13

2 Understanding Vendor Invoice Management ....................... 15

3 Preparing the Configuration ................................................... 21

Part 2 Mandatory Configuration 23

4 Configuring ArchiveLink ......................................................... 25

6 Defining Rollout Criteria for Parking and Blocking

Part 3 Advanced Configuration 85

7 Authorization Checks .............................................................. 87

8 Incoming Document Processing ............................................ 97

8.4 Customizing the Email Channel ..................................................... 105

9 Document Processing Process Configuration ................... 131

10 PO Parking Process Configuration ...................................... 265

11 PO Blocking Process Configuration .................................... 291

12 Non PO Parking Process Configuration .............................. 313

13 Invoice Approval .................................................................... 335

iv OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide

13.6 Roles in the IAP Process ............................................................... 390

14 VIM Analytics (New) .............................................................. 427

15 Characteristic Specific Configuration ................................. 461

16 ICC Integration ....................................................................... 489

17 Configuring the VIM Workplace ........................................... 513

OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide v

17.9 Specifying Discount Light Settings .................................................. 535

18 Customizing Plug-in Controls for End-user Screens ......... 537

19 Configuring VIM Dashboards for Plug-ins .......................... 547

Part 4 Optional Configuration 551

20 Extended Withholding Tax ................................................... 553

21 Return to Vendor ................................................................... 557

22 Supplier Self Service ............................................................. 563

23 Integration with the Ariba Network ...................................... 595

24 SAP NetWeaver Business Warehouse Content .................. 613

vi OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide

25 KPI Dashboard ....................................................................... 627

26 Automation Report ................................................................ 661

27 Central Reporting Infrastructure .......................................... 663

28 SAP Shared Service Framework Integration ...................... 697

29 SRM Integration ..................................................................... 749

30 PDF Log .................................................................................. 767

Part 5 Special Topics 775

31 Background Posting of Non PO (FI) Invoices ..................... 777

32 Tools ....................................................................................... 779

33 Using VIM Notifications ........................................................ 783

34 Data Archiving Configuration ............................................... 799

35 Rerunning Waiting Process Types ...................................... 807

GLS Glossary 811

SAP Invoice Management by OpenText (VIM) is a packaged business solution for

VIM is SAP® centric.

VIM consists of the following components:

Figure 1: VIM components

10 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide

• Capture invoice metadata.

• Receive a list of invoices to be approved.

• Java based Approval Portal infrastructure running on SAP NetWeaver

• Approve invoices on a mobile device, for example a Blackberry, an iPhone,

Exception Handling (Invoice Exception)

• Handle the exceptions that arise after a SAP invoice is created.

VIM Reporting / VIM Analytics