OpenText™ Vendor Invoice Management

for SAP® Solutions

Reference Guide for Invoice Solution

This guide collects reference information that is helpful when

configuring and administering the Invoice Solution of OpenText
Vendor Invoice Management (VIM) for SAP Solutions.

VIMZ230402-RGD-EN-01
OpenText™ Vendor Invoice Management for SAP® Solutions
Reference Guide for Invoice Solution
VIMZ230402-RGD-EN-01
Rev.: 2024-Oct-29
This documentation has been created for OpenText™ Vendor Invoice Management for SAP® Solutions 23.4 SPS2.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.

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: [Link]
For more information, visit [Link]

© 2024 Open Text

Patents may cover this product, see [Link]

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
 Table of Contents
1 About OpenText Vendor Invoice Management (VIM) for
SAP Solutions .......................................................................... 13
1.1 Architectural Overview ..................................................................... 15
1.2 About this document ........................................................................ 16
1.2.1 Target audience .............................................................................. 16
1.2.2 Related documentation .................................................................... 16

Part 1 Third party interface support 19

2 Interface Remote Functions ................................................... 23

2.1 Interface Remote Function 1 ............................................................ 23
2.2 Interface Remote Function 2 ............................................................ 24
2.3 Interface Remote Function 3 ............................................................ 27

Part 2 Reporting 31

3 VIM Analytics: Detailed Invoice Report ................................. 33

3.1 Starting remote enabled VAN ........................................................... 34
3.2 Using the selection screen ............................................................... 36
3.3 Understanding selection screen fields ............................................... 38
3.4 Using report results ......................................................................... 44
3.5 VIM Analytics and mass data ........................................................... 65

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

4.1 Using the selection screen ............................................................... 69
4.2 Using the report views screen .......................................................... 73
4.3 Viewing and grouping report results .................................................. 77

5 Using the Automation Report ................................................. 83

5.1 Using the selection screen ............................................................... 83
5.2 Using the report screen ................................................................... 85

6 Using the Invoice Life Cycle Report ...................................... 91

6.1 Using the selection screen ............................................................... 91
6.2 Using the report screen ................................................................... 93

7 Using the common infrastructure of Central Reporting

reports ...................................................................................... 97
7.1 Using the selection screen ............................................................... 97
7.2 Using the report screen ................................................................... 99

8 Using the Summary Report .................................................. 101

8.1 Using the selection screen ............................................................. 101

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution iii

Table of Contents

8.2 Using the report screen ................................................................. 103

9 Using the Central Audit Report ............................................ 105

9.1 Using the selection screen ............................................................. 105
9.2 Using the report screen ................................................................. 107

10 Using the Key Process Analytics Report ............................ 109

10.1 Using the Frame Selection panel .................................................... 110
10.2 Using the individual report panels ................................................... 112

11 Using the Exception Analysis Report .................................. 121

11.1 Using the selection screen ............................................................. 121
11.2 Using the report screen ................................................................. 123

12 Using the Productivity Report .............................................. 127

12.1 Using the selection screen ............................................................. 127
12.2 Using the report screen ................................................................. 129

13 Using the Aging Report ........................................................ 133

13.1 Using the selection screen ............................................................. 133
13.2 Using the report screen ................................................................. 135

14 Using the Intermediate Data Report .................................... 139

14.1 Using the selection screen ............................................................. 139
14.2 Using the report screen ................................................................. 140

15 Using Capture Analytics ....................................................... 141

15.1 Calling Capture Analytics and authorization check ........................... 142
15.2 Using the selection screen ............................................................. 143
15.3 Using the details pane ................................................................... 143

16 Using Capture Dashboard .................................................... 145

16.1 Calling Capture Dashboard ............................................................ 145
16.2 Using the Capture Dashboard ........................................................ 146
16.3 Using the selection screen ............................................................. 151
16.4 Using the details pane ................................................................... 152
16.5 Authorization check ....................................................................... 153

Part 3 Comparison Approval Portal to VIM Fiori apps 155

17 Comparison Approval Portal to Approve Invoices app ..... 157

18 Comparison Approval Portal to Enter Cost Assignment

Advanced app ........................................................................ 163

Part 4 SAP NetWeaver Business Warehouse details 167

iv OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Table of Contents

19 InfoObjects ............................................................................. 169

19.1 Key figures ................................................................................... 169
19.2 Characteristics .............................................................................. 173
19.3 Units ............................................................................................ 185

20 DataSources ........................................................................... 187

20.1 DataSources for transaction data ................................................... 187
20.2 DataSources for master data ......................................................... 188

21 DataStore objects (DSOs) ..................................................... 197

21.1 DSOs of the Data Propagation Layer .............................................. 197
21.2 DSOs of the Corporate Memory Layer ............................................ 201

22 MultiProviders ........................................................................ 207

Part 5 Transactions and roles 209

23 Transaction profiles for various roles ................................. 211

Part 6 Business rules 217

24 General information about business rules ......................... 219

25 Business rules for PO invoices ............................................ 221

25.1 Invalid PO Number (PO) ................................................................ 221
25.2 Invalid Vendor (PO) ....................................................................... 222
25.3 Invalid UOM (PO) .......................................................................... 222
25.4 Invalid Currency (PO) .................................................................... 222
25.5 Suspected Duplicate (PO) ............................................................. 223
25.6 PO Not Released or Incomplete ..................................................... 224
25.7 Unable to Match PO Lines (PO) ..................................................... 224
25.8 Manual Check Needed / Missing Data for Indexing Lines (PO) ......... 225
25.9 Unable to Determine PO Line Number (PO) .................................... 226
25.10 Manual Check Needed for Indexing Lines (PO) ............................... 228
25.11 Invalid PO Item Number (PO) ........................................................ 229
25.12 Invalid Vendor VAT Number (PO) .................................................. 230
25.13 Incomplete Credit Memo (PO) ........................................................ 231
25.14 Vendor Address Mismatch (PO) ..................................................... 232
25.15 Missing Item Quantity (PO) ............................................................ 233
25.16 Missing Item Unit Price (PO) .......................................................... 234
25.17 Missing Invoice Date (PO) ............................................................. 234
25.18 Invalid Tax Info (PO) ..................................................................... 234
25.19 Missing Date of Supply (PO) .......................................................... 237
25.20 ISR Number Mismatch (PO) .......................................................... 237

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution v

Table of Contents

25.21 Invalid Recipient VAT Number (PO) ............................................... 238

25.22 Payment Terms Mismatch (PO) ..................................................... 239
25.23 Invalid Siret Number (PO) (France) ................................................ 239
25.24 Invalid Company Address (PO) ...................................................... 240
25.25 Vendor Invoice Reference Missing (PO) ......................................... 241
25.26 Payment Method Mismatch (PO) .................................................... 241
25.27 Missing/Invalid Tax Exempt Text (PO) ............................................ 242
25.28 Missing Import Special Text (PO) ................................................... 242
25.29 Missing Item Description (PO) ........................................................ 242
25.30 Missing Mandatory Information (PO) .............................................. 243
25.31 Missing/Invalid Triangulation Text (PO) ........................................... 244
25.32 Invalid Sales Tax for the Region (PO) ............................................. 244
25.33 Vendor Audit Required (PO) .......................................................... 246
25.34 Vendor Maintenance (PO) ............................................................. 246
25.35 Vendor Mismatch (PO) .................................................................. 246
25.36 Service Entry Required (PO) .......................................................... 247
25.37 Currency Mismatch (PO) ............................................................... 248
25.38 Unit of Measure Mismatch (PO) ..................................................... 248
25.39 Approval Required (PO) ................................................................ 249
25.40 Freight on Invoice (PO) ................................................................. 249
25.41 Tax Audit Required (PO) ............................................................... 250
25.42 Invalid Requisitioner (PO) .............................................................. 250
25.43 PO Credit Memo Processing (PO) .................................................. 251
25.44 Company Code Mismatch (PO) ...................................................... 252
25.45 Confirmation Required from SRM (PO) ........................................... 252
25.46 Invalid Payment Reference (PO) .................................................... 253
25.47 Missing Invoice Code (PO) ............................................................ 253
25.48 Invalid Invoice Code Format (PO) .................................................. 253
25.49 Invalid Characters in Secret Code (PO) .......................................... 254
25.50 Invoice Older than Allowed (PO) .................................................... 254
25.51 Invalid Vendor Invoice Number (PO) .............................................. 254
25.52 Invalid Common Ordinary Invoice (VAT Exists) (PO) ....................... 254
25.53 Check Hand Written (PO) .............................................................. 255
25.54 Verification Required (PO) ............................................................. 255
25.55 Validate Bank Details (PO) ............................................................ 255
25.56 Invalid/Missing Vendor ABN Number (PO) ...................................... 256
25.57 Invalid/Missing Recipient ABN Number (PO) ................................... 256
25.58 Missing Vendor Name (PO) ........................................................... 256
25.59 Missing Recipient Name (PO) ........................................................ 256
25.60 Invalid Tax Description (PO) .......................................................... 256
25.61 GR Not Done - Simple Check ........................................................ 257
25.62 Missing Vendor ECC Number (PO) ................................................ 257

vi OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Table of Contents

25.63 Mismatch Vendor ECC Number (PO) ............................................. 257

25.64 Missing Vendor CST Number (PO) ................................................. 257
25.65 Mismatch Vendor CST Number (PO) .............................................. 258
25.66 Missing Vendor TIN/TOT Number (PO) .......................................... 258
25.67 Mismatch Vendor TIN/TOT Number (PO) ....................................... 258
25.68 Missing Vendor LST Number (PO) ................................................. 258
25.69 Mismatch Vendor LST Number (PO) .............................................. 259
25.70 Missing Vendor PAN Number (PO) ................................................ 259
25.71 Mismatch Vendor PAN Number (PO) ............................................. 259
25.72 Missing Vendor STC Number (PO) ................................................. 259
25.73 Mismatch Vendor STC Number (PO) .............................................. 260
25.74 Wait for GR - Simple Check (PO) ................................................... 260
25.75 Wait for GR - Enhanced Check (PO) .............................................. 260
25.76 Service Entry Required (PO) - Enhanced Check ............................. 260
25.77 SCB Indicator / Supplying Country Missing (PO) ............................. 261
25.78 Brazil - Missing NF Data (PO) ........................................................ 261
25.79 Brazil - Missing NF Customizing (PO) ............................................. 261
25.80 Brazil - NF Validation Check Failed (PO) ........................................ 261
25.81 Brazil - Wait for GR - Simple Check (PO) ........................................ 261
25.82 Brazil - Wait for GR - Enhanced Check (PO) ................................... 262
25.83 Russia - Wait for TORG-12/ACT - Simple Check (PO) ..................... 262
25.84 Russia - Wait for TORG-12/ACT - Enhanced Check (PO) ................ 262
25.85 Russia - Original Invoice Mismatch (PO) ......................................... 263
25.86 Invalid Withholding Tax Code / Type (PO) ...................................... 263
25.87 Withholding Tax Base Amount Bigger than Total Net Amount (PO) .. 263
25.88 Check BPF Added Data (PO) ......................................................... 263
25.89 Tolerance Exceeded (PO) ............................................................. 264
25.90 Missing VAT Date (PO) ................................................................. 264
25.91 Check Withholding Tax Data (PO) .................................................. 264
25.92 Down Payment Clearing (PO) ........................................................ 264
25.93 Missing/Invalid GST Partner (PO) .................................................. 265
25.94 Missing/Invalid Vendor GST Reg. No (PO) ...................................... 265
25.95 Missing/Invalid HSN/SAC code (PO) .............................................. 265
25.96 Missing/Invalid Receiving Location GST Registration No (PO) ......... 266
25.97 Cannot Verify Quantity/Price Exceptions (PO) ................................. 266
25.98 Quantity/Price Mismatch (PO) ........................................................ 266
25.99 Quantity/Price Confirmation Required (PO) ..................................... 267
25.100 Missing Company Code (PO) ......................................................... 267
25.101 Missing Gross Amount (PO) .......................................................... 267
25.102 Check for Reduction Invoice (PO) .................................................. 267
25.103 Check Vendor/Company Address (PO/NPO) .................................. 268
25.104 Invoice subject for payment split (PO) ............................................. 268

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution vii

Table of Contents

25.105 Missing UUID Number (PO) ........................................................... 268

25.106 Missing lean services entry sheet (PO) ........................................... 268
25.107 Check lean services - invoice amount vs GR amount (PO) ............... 269
25.108 Missing/Invalid Invoice Reference Number (PO) .............................. 269
25.109 Portugal - Missing QR code/ATCUD (PO) ....................................... 269

26 Business rules for NPO invoices ......................................... 271

26.1 Invalid Vendor (NPO) .................................................................... 271
26.2 Invalid Currency (NPO) ................................................................. 271
26.3 Invalid Requestor ID (NPO) ........................................................... 272
26.4 Suspected Duplicate (NPO) ........................................................... 272
26.5 Non-PO Credit Memo Processing .................................................. 273
26.6 Derivation Rule - Non-PO Expense Type ........................................ 273
26.7 Invalid Vendor VAT Number (NPO) ................................................ 273
26.8 Incomplete Credit Memo (NPO) ..................................................... 274
26.9 Vendor Address Mismatch (NPO) .................................................. 274
26.10 Missing Invoice Date (NPO) ........................................................... 275
26.11 Invalid Tax Info (NPO) ................................................................... 275
26.12 Invalid Recipient VAT Number (NPO) ............................................. 276
26.13 ISR Number Mismatch (NPO) ........................................................ 277
26.14 Payment Terms Mismatch (NPO) ................................................... 277
26.15 Missing Date of Supply (NPO) ....................................................... 278
26.16 Invalid Siret Number (NPO) (France) .............................................. 278
26.17 Invalid Company Address (NPO) .................................................... 279
26.18 Vendor Invoice Reference Missing (NPO) ....................................... 279
26.19 Payment Method Mismatch (NPO) ................................................. 280
26.20 Determine Expense Type .............................................................. 280
26.21 Missing/Invalid Tax Exempt Text (NPO) .......................................... 281
26.22 Missing Import Special Text (NPO) ................................................. 281
26.23 Missing Item Description (NPO) ..................................................... 281
26.24 Missing Mandatory Information (NPO) ............................................ 282
26.25 Missing/Invalid Triangulation Text (NPO) ........................................ 282
26.26 Invalid Sales Tax For The Region (NPO) ........................................ 283
26.27 Non PO Approval Required (NPO) ................................................. 284
26.28 Vendor Audit Required (NPO) ........................................................ 284
26.29 Tax Audit Required (NPO) ............................................................. 285
26.30 Validate Bank Details (NPO) .......................................................... 285
26.31 Validate Accounting Data (NPO) .................................................... 286
26.32 Invalid Payment Reference (NPO) .................................................. 286
26.33 Missing Invoice Code (NPO) .......................................................... 287
26.34 Invalid Invoice Code Format (NPO) ................................................ 287
26.35 Invalid Characters in Secret Code (NPO) ........................................ 287

viii OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Table of Contents

26.36 Invoice Older than Allowed (NPO) .................................................. 287

26.37 Invalid Vendor Invoice Number (NPO) ............................................ 288
26.38 Invalid Common Ordinary Invoice (VAT Exists) (NPO) ..................... 288
26.39 Check Hand Written (NPO) ............................................................ 288
26.40 Verification Required (NPO) ........................................................... 288
26.41 Invalid/Missing Vendor ABN Number (NPO) ................................... 288
26.42 Invalid/Missing Recipient ABN Number (NPO) ................................ 289
26.43 Missing Vendor Name (NPO) ......................................................... 289
26.44 Missing Recipient Name (NPO) ...................................................... 289
26.45 Invalid Tax Description (NPO) ........................................................ 289
26.46 Missing Vendor PAN Number (NPO) .............................................. 289
26.47 Mismatch Vendor PAN Number (NPO) ........................................... 290
26.48 Missing Vendor STC Number (NPO) .............................................. 290
26.49 Mismatch Vendor STC Number (NPO) ........................................... 290
26.50 Missing Vendor CST Number (NPO) .............................................. 290
26.51 Mismatch Vendor CST Number (NPO) ........................................... 291
26.52 Missing Vendor TIN/TOT Number (NPO) ........................................ 291
26.53 Mismatch Vendor TIN/TOT Number (NPO) ..................................... 291
26.54 Missing Vendor LST Number (NPO) ............................................... 291
26.55 Mismatch Vendor LST Number (NPO) ............................................ 292
26.56 SCB Indicator / Supplying Country Missing (NPO) ........................... 292
26.57 Check BPF Added Data (NPO) ...................................................... 292
26.58 Missing VAT Date (NPO) ............................................................... 292
26.59 Check Withholding Tax Data (NPO) ............................................... 293
26.60 Missing/Invalid GST Partner (NPO) ................................................ 293
26.61 Missing/Invalid Vendor GST Reg. No (NPO) ................................... 293
26.62 Missing/Invalid HSN/SAC code (NPO) ............................................ 293
26.63 Missing/Invalid Receiving Location GST Registration No (NPO) ....... 294
26.64 Missing Company Code (NPO) ...................................................... 294
26.65 Missing Gross Amount (NPO) ........................................................ 294
26.66 PO Data Exists (NPO) ................................................................... 294
26.67 Invoice subject for payment split (NPO) .......................................... 294
26.68 Missing UUID Number (NPO) ........................................................ 295
26.69 Validate Changes on Advanced Tax data (NPO) ............................. 295
26.70 Missing/Invalid Invoice Reference Number (NPO) ........................... 295
26.71 Portugal - Missing QR Code/ATCUD (NPO) .................................... 295

27 Business rules for Transportation Management invoices 297

27.1 General business rules for TM invoices .......................................... 297
27.2 Check for Transportation Management PO ..................................... 298

28 General business rules ......................................................... 299

28.1 Check Data after Restart ............................................................... 299

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution ix

Table of Contents

28.2 Check Inbound Interface Errors ...................................................... 299

28.3 Copy rule: Supply Date to VAT Date ............................................... 299
28.4 Invalid QR Bill data ........................................................................ 300
28.5 Check maximum exchange rate difference ...................................... 300

29 Summary tables ..................................................................... 301

29.1 Table: Business rules for PO invoices ............................................. 301
29.2 Table: Business rules for NPO invoices .......................................... 307
29.3 Table: General business rules ........................................................ 310

30 Customer library .................................................................... 313

30.1 Check country consistency ............................................................ 313
30.2 Check balance .............................................................................. 313
30.3 Check and update coding for auto coding ....................................... 313
30.4 General business rules template .................................................... 314

Part 7 Logic modules 315

31 General information about logic modules .......................... 317

32 Global Processing Logic Modules ....................................... 319

32.1 Change Vendor Group .................................................................. 319
32.2 Determine Bank Data .................................................................... 319
32.3 Determine SAP Document Type ..................................................... 320
32.4 Determine Invoice Category ........................................................... 320
32.5 Determine Payment Terms ............................................................ 321
32.6 Determine Payment Baseline Date ................................................. 321
32.7 Determine Posting Date ................................................................. 321
32.8 Determine Tax Code ..................................................................... 322
32.9 Determine New Credit Memo Flag .................................................. 322
32.10 Determine Vendor Address ............................................................ 322
32.11 Determine Vendor Group ............................................................... 323
32.12 Determine Vendor Name ............................................................... 323
32.13 Determine Withholding Tax ............................................................ 323
32.14 Synchronize Item Text ................................................................... 324
32.15 Determine Purchasing Document Category .................................... 325
32.16 Copy vendor tax/VAT ID after a flexible check ................................. 325
32.17 Normalization of vendor and company code tax IDs ........................ 325
32.18 Tax Invoice Determination ............................................................. 326
32.19 Create Held/Parked/Completely Parked Document in Background ... 326
32.20 Create Held Document in Background ............................................ 327
32.21 Create Completely Parked Document in Background ...................... 327
32.22 Create Parked Document in Background ........................................ 328
32.23 Calculation of Capture Analytics ..................................................... 328

x OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Table of Contents

32.24 Determine Invoice Receipt Date ..................................................... 329

32.25 Determine Payment Method Supplement ........................................ 329

33 PO related logic modules ..................................................... 331

33.1 Determine Currency ...................................................................... 331
33.2 Determine Delivery Date ................................................................ 331
33.3 Determine PO Item Data ............................................................... 332
33.4 Determine Matching Single Line PO Data for Vendor ...................... 332
33.5 Determine Vendor ......................................................................... 333
33.6 Determine CPD Vendor Address Data from PO .............................. 333
33.7 Determine Additional Costs ............................................................ 333
33.8 Use PO Header Data to Overwrite Line Items ................................. 334
33.9 Verify PO Data .............................................................................. 334
33.10 Process Line Items from OCR ........................................................ 335
33.11 Determine Invoice Reference for Credit Memos .............................. 335
33.12 Consolidate line items referring framework orders ........................... 336
33.13 Populate TM object lists ................................................................. 336

34 NPO related logic modules ................................................... 337

34.1 Determine Expense Type .............................................................. 337
34.2 Determine NPO Line ..................................................................... 337
34.3 Determine NPO Auto Coding ......................................................... 338
34.4 Process Line Items from OCR ........................................................ 338
34.5 Enrich NPO Line Items .................................................................. 338
34.6 Enrich smart coding cost line items ................................................ 339
34.7 Determine Invoice Reference for Credit Memos .............................. 339

35 Country specific logic modules ........................................... 341

35.1 Determine Ship-to Region for Canada ............................................ 341
35.2 Determine Corrective Items for Russia ........................................... 341
35.3 Determine Service PO for Russia ................................................... 342
35.4 Determine KIDNO for Denmark ...................................................... 342
35.5 Enrich Country Specific Data for China ........................................... 342
35.6 Enrich Country Specific Data for France ......................................... 343
35.7 Enrich Country Specific Data for India ............................................ 343
35.8 Determine Invoice Reference for Spain ........................................... 343

Part 8 Automated Field Enhancement 345

36 Configuring Automated Field Enhancement ...................... 347

37 Baseline of Automated Field Enhancement ........................ 349

Part 9 Z constants 353

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution xi

Table of Contents

38 Z constants for product code 002 and 009 ......................... 355

39 Z constants for product code 005 ........................................ 359

40 Z constants for product code IAP ........................................ 397

41 Z constants for product code IEM ....................................... 411

42 Z constants for product code LIX ........................................ 413

43 Z constants for product code VAN ...................................... 421

GLS Glossary 425

xii OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 1
About OpenText Vendor Invoice Management (VIM)
for SAP Solutions

OpenText Vendor Invoice Management (VIM) for SAP Solutions is an ABAP add-on
solution to SAP S/4HANA. It automates the processing of incoming documents into
SAP.

Document-centric business processes like the processing of incoming invoices from

vendors or incoming sales orders from customers are typical use cases. After
capture, data is enriched and validated against predefined business rules.

If the business rules pass, the document is posted in SAP without human
intervention. Although a straight through, no-touch process is the ultimate objective,
OpenText VIM for SAP also supports the fast and efficient handling and resolution
of exceptions. Exceptions are routed via workflow to the relevant user or user group
based on the role assigned to the exception.

For managers, OpenText VIM for SAP offers a comprehensive suite of operational
and analytical reports. In addition, it offers the tools to identify common exceptions
that should be addressed to achieve even higher levels of automation.

OpenText VIM for SAP includes the following solutions:

• Invoice Solution
• Procure to Pay Solutions

– Order Confirmation
– Delivery Note
– Quotation
• Order to Cash Solutions

– Sales Order
– Remittance Advice

Each solution consists of a best practice implementation for a specific document

scenario. It includes preconfigured mapping rules, enrichment rules, business rules,
user roles and user actions. Learning-based enrichments features embedded easy to
configure machine learning that automates input based on previous user input.

Since OpenText VIM for SAP resides inside SAP, enrichments and business rules
have direct access to SAP master and transactional data, which avoids complex
interfaces and the replication and duplication of data.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 13

Chapter 1 About OpenText Vendor Invoice Management (VIM) for SAP Solutions

Each solution offers a Workplace to manage and monitor outstanding and

completed work items. Each solution includes a preconfigured set of analytical
measures tailored for the specific document scenario. Solutions can be enhanced to
support company-specific business requirements.

VIM Solutions use features offered by its powerful feature rich Foundation.

VIM Foundation consists of the following components:

• Inbound
• Process
• Workplace
• Analytics

OpenText VIM for SAP offers you a wide range of functionality:

• It supports custom solutions where a preconfigured solution is not available for a

specific, less common business process.
• It offers a simple and intuitive user interface.
• You can choose between the classic SAP GUI or the modern SAP Fiori interface.
SAP Fiori offers a responsive web-based user interface that supports desktop and
mobile devices.
• It supports various input channels including scan, fax¸ email and web services.
• It supports various input formats, including paper, PDF, TIFF, IDoc and XML.
• It requires an ArchiveLink-compliant SAP-certified content repository for the
storage of incoming documents. OpenText recommends OpenText™ Archiving
and Document Access for SAP Solutions or OpenText™ Core Archive for SAP®
Solutions for the storage of documents.
• It integrates seamlessly via its Inbound component with OpenText™ Core
Capture for SAP Solutions and OpenText™ Capture for SAP® Solutions, which

14 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 1.1. Architectural Overview

use advanced machine learning algorithms to extract metadata from imaged-

based documents like PDF and TIFF.
• It offers integration with OpenText Content Management for SAP Solutions and
OpenText Document Presentment for SAP Solutions.

1.1 Architectural Overview

The following figure gives an overview of the basis architecture. It shows how the
core components are integrated into SAP and which additional OpenText
components like Document Pipeline, Document Storage, Capture, and WebViewer
complete the solution.

Note: Capture is used in this documentation as a common technical term for

both of the following OpenText products:

• OpenText™ Capture for SAP® Solutions

• OpenText™ Core Capture for SAP Solutions

Beside the components of this graphic, OpenText VIM for SAP offers additional
components such as SAP NetWeaver Business Warehouse or BW/4Hana for specific
solutions which are not shown in this basis architectural overview.

Figure 1-1: Technical system landscape

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 15

Chapter 1 About OpenText Vendor Invoice Management (VIM) for SAP Solutions

1.2 About this document

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

1.2.1 Target audience

This document addresses those who participate in the customization and
implementation of OpenText VIM for SAP. This includes:

• SAP Basis Administrators

• SAP Workflow Administrators
• SAP Configuration and Development Support

1.2.2 Related documentation

Product docu- The following documentation is available on OpenText My Support (https://
mentation [Link]/csm?id=kb_article_view&sysparm_article=KB0778393):

• OpenText Vendor Invoice Management for SAP Solutions - User Guide for Invoice
Solution (VIMZ-UGD)
• OpenText Vendor Invoice Management for SAP Solutions - Installation Guide (VIMZ-
IGD)
• OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD)
• OpenText Vendor Invoice Management for SAP Solutions - Administration Guide
(VIMZ-AGD)
• OpenText Vendor Invoice Management for SAP Solutions - Reference Guide for Invoice
Solution (VIMZ-RGD)
• OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide for Invoice
Solution (VIMZ-CCS)
• OpenText Vendor Invoice Management for SAP Solutions - Security Guide (VIMZ-
GSM)
• OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Foundation (VIMZ-CGF)
• OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Solutions Beyond Invoice (BOCPZ-CCS)
• OpenText Vendor Invoice Management for SAP Solutions - User Guide for Solutions
Beyond Invoice (BOCPZ-UGD)

Release Notes Release Notes describe:

• The software supported by the product

• Requirements

16 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 1.2. About this document

• Restrictions
• Important dependencies
• New features
• Known issues
• Fixed issues
• Documentation extensions

The Release Notes are updated continuously. The latest version of the Release Notes
is available on OpenText My Support.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 17

 Part 1
Third party interface support
Part 1 Third party interface support

A third party interface is one channel to import an invoice to OpenText VIM for
SAP. Third party vendors provide the routing of invoices from the vendor to the
customer. “Middlemen” handle the responsibility of sending the invoice from
vendor to customer. These middlemen may also communicate back to the vendor
regarding the progress of the invoice processing on customer side. Third party
vendors can use any middleware technology like EDI, and so on.

Figure 2 depicts the suggested data and process flow for a third party service
provider scenario.

Figure 2: Third party service provider scenario - overview

Process flow

1. The third party provider module receives digitally signed invoices from
vendors.

2. The third party provider module verifies the authenticity of the digital
signature using Digital Signature Application.

20 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3. The third party provider module calls OpenText VIM for SAP APIs.
4. An OpenText provided API (FM1) returns the archiving URL.

5. The third party provider module archives the invoice image to the OpenText™
Archive Center via HTTP Post action.

Note: HTTP Post is obsolete and may not work with recent archive server
software. Use HTTP Put instead.

6. The third party provider module calls the second API (FM2) to trigger the
invoice processing in SAP S/4HANA.
7. While invoice processing continues in SAP S/4HANA, the third party provider
module can query the status of the document by calling the third API (FM3).

Third party service provider responsibility

The third party service provider must provide the following:

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

Note: OpenText VIM for SAP workflow is started directly when you use this
scenario. Therefore, the status of the steps before the start of the workflow
cannot be monitored with tools like VIM Central Workplace. As soon as the
workflow is started, the document is visible in VIM Analytics and other
reports.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 21

Chapter 2
Interface Remote Functions

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

2.1 Interface Remote Function 1

This function module allows archiving a document. This facilitates the generation of
the URL that the third party provider module uses to archive the invoice image to
the content repository. The following is the interface of the function module:
FUNCTION /OPT/ARCHIV_DOC_URL_CREATE.
*"-----------------------------------------------------------------
*"*"Local Interface:
*" IMPORTING
*" VALUE(ARCHIV_ID) TYPE /OPT/VIM_1RHEAD-ARCHIV_ID OPTIONAL
*" VALUE(SIGNATURE) TYPE CHAR1 OPTIONAL
*" VALUE(AR_OBJECT) TYPE SAEOBJART OPTIONAL
*" EXPORTING
*" VALUE(ARCHIV_DOC_ID) TYPE /OPT/VIM_1RHEAD-ARC_DOC_ID
*" VALUE(MIMETYPE) TYPE CHAR128
*" VALUE(RC) TYPE SUBRC
*" TABLES
*" URL_ROWS STRUCTURE /OPT/VIM_URL
*" RETURN STRUCTURE BAPIRET2
*"-----------------------------------------------------------------

Import parameters

The third party provider must enter the correct parameters to match the SAP
ArchiveLink® configuration.

Parameter Name Data Type Size Comments

ARCHIV_ID 2 Content Repository Identification
(constant)
SIGNATURE 1 Signature authentication is used in SAP
ArchiveLink configuration (X = yes; Space
= no)
AR_OBJECT 10 SAP Archive Document Type

Export parameters

Parameter Name Data Type Size Comments

ARCHIV_DOC_ID Char 40 SAP ArchiveLink Document ID
( generated for the image)
MIMETYPE Char 128 Mime Type
RC Numeric 2 Value 0 means successful. Value 8 means
error.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 23

Chapter 2 Interface Remote Functions

Parameter Name Data Type Size Comments

URL_ROWS Table Type Table of URL rows to archive image /
OPT/VIM_URL

RETURN Table Type Table of messages BAPIRET2

Error handling

If the RFC raises an exception, the call has failed. The call can be resubmitted if
possible. If the RC returns value 8, a data error has occurred. This record should be
placed into a separate queue for error handling. Resubmitting without investigation
will not make much sense.

2.2 Interface Remote Function 2

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

Import parameters

When calling this function, provide the following information:

1. Archived image info:

Parameter Name Data Type Size Comments

ARCHIV_ID Char 2 Content Repository Identification
(constant)
ARC_DOC_ID Char 40 SAP ArchiveLink Document ID
(returned from Interface Remote
Function 1)
AR_OBJECT Char 10 SAP Archive Document Type

24 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 2.2. Interface Remote Function 2

2. Channel info:

Parameter Name Data Type Size Comments

CHANNEL_ID Char 10 SAP Channel ID (Constant).
Recommended to be supplied. It helps
in identifying the source of any
supplied invoice.
SYSTEM Char 10 Logical name of the SAP S/4HANA
target system

3. Invoice info captured from External Partner:

Parameter Name Data Type Size Comments

EXTDATA_HEAD Table Type Header info, for example Vendor
number, total amount, etc. Refer to
structure /OPT/VIM_1REXTDATA.
EXTDATA_ITEM Table Type Line item info, for example PO line,
Material, Quantity, etc. Refer to
structure /OPT/VIM_1REXTDATA.

Structure/OPT/VIM_1REXTDATA:

Field Name Data Type Size Comments

EXTFIELD Char 50 Field Name from External Partner
System
EXTVALUE Char 255 External Field Value

For each invoice field passed, the External Partner must specify field name
(EXTFIELD) and value (EXTVALUE).
4. Other optional parameters:

Parameter Name Data Type Size Comments

DOCTYPE Char 10 Processing Document Type
I_DOC_HEADER Structure Structure of Indexing Document
Type Header /OPT/VIM_1HEAD
I_DOC_ITEMS Table Type Table of Indexing Document Item /
OPT/VIM_1ITEM

LOGDATA Table Type Table of Document Process Log data /

OPT/VIM_1LOG

COMMENTS Table Type Table of Comments in structure /

OPT/EXT_COMMENTS. Comments can
be assigned to an entry in LOGDATA.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 25

Chapter 2 Interface Remote Functions

Export parameters

Parameter Name Data Type Size Comments

RC Numeric 2 Value 0 means successful. Value 8 means
error.
RETURN Table Type Table of messages BAPIRET2
E_WF_ID Numeric 12 Work item ID of the triggered Document
Processing Workflow in OpenText VIM
for SAP
DOC_STATUS Structure The Document Processing Number
Type generated in OpenText VIM for SAP and
its corresponding status is passed in this
parameter. Refer to structure /OPT/VIM_
DP_STATUS1.

Error handling If the RFC raises an exception, the call has failed. The call can be resubmitted if
possible. If the RC returns value 8, a data error has occurred. This record should be
placed into a separate queue for error handling. Resubmitting without investigation
will not make much sense.

Basic scenarios The function supports two basic scenarios concerning the import parameters, the
mapping scenario and the data scenario. Consider these scenarios. Which one of
these basic scenarios is taken, will be decided by the content of parameter
I_DOC_HEADER. If this parameter is initial, the mapping scenario is assumed. If
this parameter is not initial, the data scenario is assumed.

Mapping scenario
In this scenario, mapping is performed according to the value of CHANNEL_ID.
Data is expected in table EXTDATA_HEAD and EXTDATA_ITEM. Data
provided in I_DOC_ITEMS will be ignored.
Parameters DOCTYPE and AR_OBJECT can be left empty. Their values are
calculated according to configuration and document type determination engine.
If one or both of these parameters are provided, the given value will override
the configuration.

Data scenario
In this scenario, data is taken from I_DOC_HEADER and I_DOC_ITEMS. Data
provided in EXTDATA_HEAD and EXTDATA_ITEMS is ignored.
Parameters DOCTYPE and AR_OBJECT can be left empty. Their values are
calculated according to configuration and document type determination engine.
If one or both of these parameters are provided, the given value will override
the configuration.
If you are providing a posting date BUDAT in the data scenario, be sure to
assign a value to the posting date determination method POST_DATE_DET as well.
The appropriate value is E for provided externally.

26 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 2.3. Interface Remote Function 3

Additional notes

The document type AR_OBJECT can be provided as import parameter for

additional images. If it is not provided, the document type for additional
images is determined by the global configuration constant 005 ADDL_DOCS_AR_
OBJECT.

The document class (TIF, PDF, and so on) is determined the following way:

If document type AR_OBJECT is provided as input parameter, the document

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

2.3 Interface Remote Function 3

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

Import parameters

When calling this function, provide the following information:

1. Channel info:

Parameter Name Data Type Size Comments

CHANNEL_ID Char 10 SAP Channel ID (Constant).
Recommended to be supplied. It helps
in identifying the source of any
supplied invoice.
SYSTEM Char 10 Logical name of the SAP S/4HANA
target system

2. Query Table parameter:

Parameter Name Data Type Size Comments

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 27

Chapter 2 Interface Remote Functions

Export parameters

Parameter Name Data Type Size Comments

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

Error handling

If the RFC raises an exception, the call has failed. The call can be resubmitted if
possible. If the RC returns value 8, a data error has occurred. This record should be
placed into a separate queue for error handling. Resubmitting without investigation
will not make much sense.

Notes

• Error messages will be stored in the application log. The RETURN table will
not be filled.

• RC will always be 0.

The function delivers the document status of documents with the following
peculiarities on import and export parameters:

CHANNEL_ID
The function delivers documents which have the specified channel ID. If
CHANNEL_ID is empty, only documents with empty channel ID are
considered.

SYSTEM
The function delivers documents from the specified logical system. If SYSTEM is
empty, the documents are checked in all active systems of the system landscape.

DOC_QUERY
If this table parameter is empty, all documents are delivered.

DOC_QUERY-DOCID
The function delivers the document with the specified document number(s).

DOC_QUERY-LOGICAL_SYSTEM
This import parameter is ignored.

DOC_STATUS
The resulting table is sorted by document numbers. This gives an easy overview
on the status of documents in different systems.

28 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 2.3. Interface Remote Function 3

DOC_STATUS-LOGICAL_SYSTEM
This export parameter shows the logical system where the information of the
table entry was taken from.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 29

 Part 2
Reporting
Part 2 Reporting

OpenText VIM for SAP provides the following reporting components:

• VIM Analytics
• VIM Analytics Current Liability Report
• Automation Report
• Central Reporting, comprising the following reports:

– Summary Report
– Central Audit Report
– Key Process Analytics Report
– Exception Analysis Report
– Productivity Report
– Aging Report

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

32 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 3

VIM Analytics: Detailed Invoice Report

VIM Analytics (VAN) is one of the most important and widely used reports in
OpenText VIM for SAP. It provides a detailed view of vendor invoices with an
exhaustive list of selection fields to filter from.

With the wide range of selection fields available in VAN, invoices can be filtered by
DP number, vendor, company, status, due date, accounting data, work item data,
and many other options.

VAN makes it easier for a user to search for a particular DP, track status, check
triggered exceptions, find out the current agent, and view document attachments for
an invoice or invoices. In addition, this report enables a user with forward
navigation to DP document and SAP screens to drill down further for more details.

The user can see DP information on a single screen, including a detail pane offering
additional runtime information. This pane includes the following views:

• Process View
This view displays open and completed OpenText VIM for SAP 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 OpenText VIM for SAP process and approval history.

• Comments View
This view displays the comments that have been added during the OpenText
VIM for SAP process and during the approval process.

Invoices posted directly from SAP or using a OpenText VIM for SAP process can
both be viewed and tracked in this report.

VIM Analytics is highly optimized for SAP® HANA database systems and supports
queries on mass data swiftly.

Transactions There are different transaction codes to start VIM Analytics.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 33

Chapter 3 VIM Analytics: Detailed Invoice Report

/OPT/VIM_VA2
This transaction launches VIM Analytics with the full set of more than 80
selection fields.
/OPT/VIM_VA21 (AP Basic) - using report variant /OPT/VA2_L01
This transaction launches VIM Analytics with a subset of selection fields tailored
to an accounting expert. This variant allows searches for specific invoices using
invoice data like invoice numbers, document date, total amount, and reference
number.
/OPT/VIM_VA22 (AP Advanced) - using report variant /OPT/VA2_L02
This transaction launches VIM Analytics with a subset of selection fields tailored
to a higher level accounting expert or special roles as duplicate checker, financial
administrator or tax expert. This variant allows searches for specific invoices
using invoice data like invoice numbers, document date, total amount, reference
number, but also process data, accounting data and due dates.
/OPT/VIM_VA23 (Procurement) - using report variant /OPT/VA2_L03
This transaction launches VIM Analytics with a subset of selection fields tailored
to a purchase agent in the procurement department. This variant allows searches
for specific invoices using invoice data like invoice numbers, document date,
total amount, reference number and requisitioner, but also purchasing data.
/OPT/VIM_VA24 (Monitor) - using report variant /OPT/VA2_L04
This transaction launches VIM Analytics with a subset of selection fields tailored
to a person who needs to monitor invoices and their processes. This variant
allows searches for invoice data like document date, total amount and reference
number, but also accounting data, due dates, document dates and OpenText
VIM for SAP exceptions.

Tip: You can switch between the different report variants with Get Variant .

3.1 Starting remote enabled VAN

With version 7.5 SP4 and later, the new VAN is enabled to extract data from
multiple backend systems, using the System Landscape Directory (SLD).

Note: This new logic includes some restrictions on the possible values for the
Target System field. Some documents with unexpected values in Target
System might not be visible any more. If you want to use the old logic, set up
your system as Single System Landscape. The old logic does not try to match the
target system values of the documents to the SLD.

You can start or run VAN on the central system or on any of the satellite system as
defined in the SLD. In version 7.5 SP4, the following new reports are introduced for
this:

/OPT/VIM_VA25 Remote enabled VAN - for a single remote system

This transaction launches VIM Analytics to read DP data from one remote
system.

34 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.1. Starting remote enabled VAN

/OPT/VIM_VA26 Remote enabled VAN - for multiple remote systems

This transaction launches VIM Analytics to read DP data from two or more
remote systems.

The following procedures show how to start remote enabled VAN.

/OPT/VIM_ This transaction launches VAN to read DP data from one remote system.
VA25
To start remote enabled VAN for a single remote system:

1. Run the /OPT/VIM_VA25 transaction.

2. Enter the Target System (logical system of satellite or remote system) or click
to select it from a list.

3. To launch the new VAN (/OPT/VIM_VA2 transaction) on the remote system, click
.

/OPT/VIM_ This transaction launches VAN to read DP data from two or more remote systems.
VA26
To start remote enabled VAN for multiple remote systems:

1. Run the /OPT/VIM_VA26 transaction.

The VAN selection screen is displayed, showing the General Data area, which
is specific for VAN for multiple remote systems.

2. Enter the following parameters or click to select them from a list.

Target System
Systems according to the SLD configuration from logon system. For more
information, see Section 4.4 “Working with the System Landscape Directory
(SLD)” in OpenText Vendor Invoice Management for SAP Solutions - Scenario
Guide for Invoice Solution (VIMZ-CCS).

DP Document Type
DP document types from the selected target systems (satellite or central)

Company Code
Company codes from the selected target systems (satellite or central)

Users can additionally restrict the data selection, based on other selection fields,
for example PO, DP, or Cost Center numbers. Therefore, users must know the
respective values. The reason for this is that currently the F4 help is not enabled
for master and transaction data fields because the data is not available on the
current (logon) system.

3. To run the VAN report, click in the application toolbar.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 35

Chapter 3 VIM Analytics: Detailed Invoice Report

3.2 Using the selection screen

To start VIM Analytics:

• Run the /OPT/VIM_VA2 transaction or any of the specific transactions /OPT/VIM_

VA21 to /OPT/VIM_VA24. For more information, see “Transactions” on page 33.
Alternatively, navigate to OpenText VIM - Invoice Solution > SAP menu >
Reports > /OPT/VIM_VA2 - VIM Analytics

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

The selection screen controls all functions of VIM Analytics. The selection screen
comprises the application toolbar and selection field panel. The following list
summarizes the features of these panels.

Application toolbar
Using the buttons in the application toolbar, you can perform the following
actions:
Execute
VIM Analytics creates and displays a report, using the current settings in
the selection field panel.

36 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.2. Using the selection screen

Get report variant.

You can save your selection criteria and use the variant button to retrieve
the previous saved one. To create a report variant, click on the selection
screen. A report variant controls the selection screen. For example, you can
do the following.

• Hide selection fields (or even complete selection blocks)

• Declare fields as required
• Save selection criteria entered

Example: You search for Document Currency = EUR and click to save the
selection criteria. Next time, you can click to retrieve the search you saved
before. This is useful if you often perform a selection with different search criteria.

Get all selections.

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

Selection field panel

Selection fields explanation – For explanation on selection fields that are not
self-explanatory, see “Understanding selection screen fields” on page 38.
Tips

• Where applicable, click the icon for a list of available values.

• For search criteria with two entry fields joined by a to, you can enter a
value range.
• If you do not specify search criteria in a field, the search includes all
available values.

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

Layout
Click to select a layout variant from the list. With baseline, a basic and an
extended layout variant are available. You can create a layout variant for the
result list. Use the ALV buttons Change Layout and Save Layout on the result
list.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 37

Chapter 3 VIM Analytics: Detailed Invoice Report

Reporting Currency
The amount fields in the result list like Gross invoice amount, Discount
Amount 1, and Discount Amount 2 can be displayed in document currency but
also in any user-defined reporting currency.
Select the reporting currency. You can set a default reporting currency by setting
the user parameter FWS. If no user parameter is maintained, USD is used as
default reporting currency.

Currency Translation Date

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

3.3 Understanding selection screen fields

This section provides explanations for fields of the selection screen that are not self-
explanatory. The fields are sorted according to their appearance in the selection
screen.

Invoice Data

Transaction/Event
Categorization of invoice documents into invoices, credit memos, subsequent
debits, subsequent credits and down payments

Vendor and Purchasing Data

Reference
Reference document number from the invoice
Purchasing Document
Purchasing document number

Note: Both the actual purchasing document in line items and potential
purchasing documents from header level and purchase order list (PO list)
are taken into account.
Purchasing Group
Purchasing group assigned to purchasing document

38 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.3. Understanding selection screen fields

Note: Both the actual purchasing document in line items and potential
purchasing documents from header level and purchase order list (PO list)
are taken into account.

Plant
Plant from the invoice line items

Transportation Management (TM) Data

Freight Order
Freight Order number/Freight Booking number
Freight order is a transportation document that is used for road and rail
transportation. Freight booking is a transportation document that is used for air
and ocean transportation

Freight Settlement Document

A freight settlement document is a document that is used for posting the freight
cost accruals. It forms the basis of invoice verification in Materials Management
(MM) for freight documents such as freight orders, freight bookings, and service
orders.

House Bill of Lading

A bill of lading (B/L) is a document that must be issued by the carrier to the
shipper, booking party, and so on. It is a receipt for the goods, proof of the
contract of carriage, and also a document of title.

Air Waybill
Air Waybill is a document that covers both domestic and international flights
transporting goods to a specified destination. A House Air Waybill (HAWB) is
issued by a freight forwarder. It details the agreement between the freight
forwarder and the shipper. The HAWB is used when a freight
forwarder consolidates multiple shipments into one master shipment under a
single Master Air Waybill (MAWB).

Process Data

Invoice Document Number

SAP MM invoice number

Accounting Document Number

SAP FI invoice number

VIM Process Type

OpenText VIM for SAP supports different process types from the DP process to
standalone scenarios (parked and blocked invoices). This selection field allows
to select one of the following:

• Invoices of all Process Types. This means invoices with and without
OpenText VIM for SAP processes

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 39

Chapter 3 VIM Analytics: Detailed Invoice Report

• Invoices with DP Process. Technically, this means that a DP workflow was

started.

• Parked/Blocked Inv., w/o DP. This means invoices with at least one
OpenText VIM for SAP process (parking, blocking, approval) but without a
DP process.

• Invoices without VIM Process. This means invoices without any OpenText
VIM for SAP process

Invoice Type
Type of invoice, indicating whether the invoice is purchase order based or not

Overall Process Status

The Overall Process Status enables you to select for invoices in a specific
processing status. You can select for predefined status scenarios and for a SAP
invoice status or a OpenText VIM for SAP processing status.

Specific Scenario
Specific Scenario provides predefined scenarios, for example All Invoices,
Open Invoices, and Completed Invoices.

An open invoice in this context is defined as an invoice that has an open

OpenText VIM for SAP process (if existing) or where the SAP invoice (if
existing) is not deleted, not cancelled, or not yet ready for payment (this
means not yet posted without any fiscal and logistic payment block).
A completed invoice in this context is defined as an invoice where both all
OpenText VIM for SAP processes (if existing) are completed and the SAP
invoice is deleted, or cancelled, or ready for payment (this means posted
without any fiscal and logistic payment block).
You can also select for invoices in different approval scenarios supported by
OpenText VIM for SAP: approval of posted documents, or approval of
parked or DP based documents.
With the Fiscal Year Changed scenario, you can select all invoice documents
that ran through the year end program of OpenText VIM for SAP. In other
words, you can select all invoice documents whose SAP invoice documents
were deleted due to a change in the year end posting period.

Selected Status
Selected Status enables you to select for the status of the SAP invoice or for
the OpenText VIM for SAP processing status. The value help offers a big
range of different status values. SAP statuses start with the prefix SAP_. They
represent different states of the SAP invoice, for example Parked, Posted, or
Blocked. Statuses without prefix SAP_ represent DP statuses.

Note: An invoice is not in status Posted but Blocked as long as any

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

40 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.3. Understanding selection screen fields

Accounting Data

G/L Account, Cost Center, and other accounting objects

Actual accounting object of invoice line item and purchase order in case of PO
based DP document

Due Dates

Due date
Due date of invoice
Days to Due
Number of days until the invoice is due for payment
This field allows negative values, as well, to get invoices whose due date was a
number of days ago.
Note: A possible difference of time zones between payer and invoicing
party is not taken into account.
Overdue
Check box to indicate that the invoice is overdue for net payment
Note: A possible difference of time zones between payer and invoicing
party is not taken into account.
Days to Cash Discount Date 1
Number of days until the cash discount applied to the shortest payment period
is due
This field allows negative values, as well, to get invoices whose cash discount 1
was a number of days ago.
Note: A possible difference of time zones between payer and invoicing
party is not taken into account.
Days to Cash Discount Date 2
Number of days until the cash discount applied to the second payment period is
due
This field allows negative values, as well, to get invoices whose cash discount 2
was a number of days ago.
Note: A possible difference of time zones between payer and invoicing
party is not taken into account.

Work Item Data

Workflow Type
Type of the OpenText VIM for SAP workflow that is or was active for processing
an invoice.

Example:

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 41

Chapter 3 VIM Analytics: Detailed Invoice Report

• 1 – Document Process Workflow

• 2 – Parked PO Invoice Workflow

Work Item Priority

Priority of OpenText VIM for SAP workflow that is or was active for processing
an invoice
Work Item Status
Current status of any OpenText VIM for SAP workflow assigned to an invoice.
The following values are available:
50 - Waiting
These are workflows with a current work item that is not yet visible in the
VIM Invoice Workplace. This can have one of the following reasons:

• The work item could be created but the condition for the step Create
Work Item is not yet fulfilled (SAP work item status: CHECKED).

• The work item cannot be executed yet and therefore cannot be seen in
the Business Workplace or the VIM Invoice Workplace yet (SAP work
item status: WAITING).

51 - In Process
These are workflows with a current work item that has one of the following
statuses:

• Available for execution (SAP work item status: READY),

• Reserved by a recipient (SAP work item status: SELECTED),
• Currently being processed (SAP work item status: STARTED)
• Already been executed once but processing is not yet completed (SAP
work item status: COMMITED)

52 - Completed
These are workflows with the following statuses:

• Processed fully and successfully (SAP work item status: COMPLETED)

• No longer processed (SAP work item status: CANCELLED)

54 - Error in Workflow
These are workflows with a current work item that has the following status:

• Error status (SAP work item status: ERROR)

Document Dates

Start Date
Date when the invoice entered the SAP system

42 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.3. Understanding selection screen fields

DP Start Date
Date when the DP workflow started
Parking Date
Date when the parked SAP invoice was created or when the SAP invoice was
parked
Update Date
Date of the last change of the invoice.
Note: Even doing an approval step is defined as a change in this context.

Unblocking Date (MM)

Date when the payment block was removed from the MM invoice document or
posting date if there was no payment block
Posting Date in the Document
Posting date in the invoice; this date is used when entering the document in
Financial Accounting or Controlling
Posting Date
Date when the posted SAP invoice was created or when the SAP invoice was
posted
End Date
Date when the last OpenText VIM for SAP process was finished
Processing Time (in Days)
Duration of OpenText VIM for SAP processes in days from the entry time (Start
Date/Start Time) of the OpenText VIM for SAP invoice in the SAP system to the
end time (End Date/End Time) of the latest OpenText VIM for SAP process
Note: In this context, a day is defined as 24 hours independent of a day
change. A duration from 18 p.m. to 4 a.m. on the next day is less than a
complete day, this means 0 days. However, a duration from 18 p.m. to 20
p.m. on the next day is 1 day.
Payment Date
Date of the last partial or complete payment

Process Flow

Company Code of Orig. Doc.

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 43

Chapter 3 VIM Analytics: Detailed Invoice Report

Fiscal Year of Original Doc.

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

3.4 Using report results

This section describes the report results that are available when running VIM
Analytics.

The following sections explain the general layout and the various areas of the report
results.

3.4.1 General layout

To run a report:

1. In the selection screen, enter the criteria you want to run a report for.

2. Click in the application toolbar.

The report results comprise the following sections:

1
Menu toolbar

44 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

2
Application toolbar
3
Result list
4
Detail pane

Personal layout You can change the layout of the report results screen, according to your needs:

• Show or hide the detail pane.

• Select the tab to be displayed in the detail pane: Processes, Image, Line Items,
History, or Comments. For more information, see “Detail pane” on page 52.
• Define the ratio between result list and detail pane by dragging the borderline.

When you leave the report results screen, using the , , or button,

VIM Analytics remembers your current state, and will show it again the next time
you open the report results.

Layout variants Using the button, you can define and save layout variants in the result list, the
Processes tab, and the Line Items tab in the detail pane.

3.4.2 Menu toolbar

The following actions are available in the menu toolbar:

VIM Analytics > Refresh

Get the newest data for the displayed report results. Refresh is also available as a
button in the application toolbar:
Settings > Hide Detail Pane / Show Detail Pane
Toggle between view with detail pane and view without detail pane. This
setting is also available in the application toolbar.
Settings > Reset to Default
Reset the layout settings to the default settings.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 45

Chapter 3 VIM Analytics: Detailed Invoice Report

3.4.3 Application toolbar

Hide Detail Pane / Show Detail Pane

See “Menu toolbar” on page 45

Refresh
Get the newest data for the displayed report results.

3.4.4 Result list

ALV grid control The ALV grid control on top of the result list provides various buttons for the ALV
list viewer. The following buttons are specific for VIM Analytics:

Choose Layout
Choose, change, save, and manage layouts. Click the small arrow on the right
side of the Choose Layout button.

Choose Layout
Select a saved layout from the list.

Change Layout
Add columns to the result list by shifting columns from Column Set to
Displayed Columns, using the arrow button.
Remove columns from the result list by shifting columns from Displayed
Columns to Column Set, using the arrow button.
Change the order of displayed columns using the up and down arrows in
Displayed Columns.
Click to save your layout.

Save Layout
Save your current layout status under an existing or a new name.
To keep the layout only for you, select the User-specific check box.
To load the layout as default layout when the result list is opened, select the
Default setting check box.

Manage Layouts
Define default settings of layouts and delete layouts.

Dashboard
Access the OpenText unified dashboard for the selected document.

Vendor Workspace
Display the Vendor Workspace (OpenText™ Content Management for SAP®
Solutions) for the work item in a separate window. OpenText Content
Management for SAP Solutions allows you to access related OpenText™
Content Server items in the business workspace without leaving the SAP
system.

46 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

For a comprehensive description, see Section 6 “Working in SAP ERP with the
Business Content window” in OpenText Content Management for SAP Solutions -
User Guide (ERLK-UGD)

Result list (ALV The result list provides details on invoice header level. The most important fields of
grid) the result list are described in “Understanding result list fields” on page 47.

OpenText delivers one basic and one extended layout variant for the result list in the
baseline. However, you can define your own layout variant to add fields to the
result list, to remove fields from the result list, or to change the sorting of the result
list.

Note: For performance reasons, OpenText recommends that you restrict the
layout to those columns that you really need.

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

The asterisk (*) in a cell indicates that there is more than one value in this cell. This
can be the case with, for example, Purchasing Document, Current Agent or
accounting objects. Cells showing an asterisk do not serve as links. (Exception:
Current Agent in the Processes tab of the detail pane)

3.4.5 Understanding result list fields

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

Accounting Document No.

SAP FI invoice number
Approval Status Text
In case of an active approval process, this field indicates whether the coding step
has already been finished or not. Possible values:

• Awaiting Approval – Coding is not yet finished

• Awaiting Approval – Coding is finished

Cash Disc 1 Due Date

Due date for cash discount applied to the shortest payment period
Cash Disc 2 Due Date
Due date for cash discount applied to the second payment period
Clearing Document
Clearing document of last partial or complete payment
Currency Translation Date
Date that was used for the conversion of amount related fields into the reporting
currency (as entered in the selection screen)

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 47

Chapter 3 VIM Analytics: Detailed Invoice Report

Current Agent
Agent that is currently assigned for processing the invoice
If multiple different agents are assigned, * is displayed.
Cycle Time
Duration of OpenText VIM for SAP processes from the entry time (Start Date/
Start Time) of the OpenText VIM for SAP invoice in the SAP system to the end
time (End Date/End Time) of the latest OpenText VIM for SAP process
Days to Cash Disc.1
Days to due date for cash discount applied to the shortest payment period
Days to Cash Disc.2
Days to due date for cash discount applied to the second payment period
Days to Due
Number of days until the invoice is due for net payment.
This field is cleared for completed invoices (this means obsolete, deleted, or
cancelled invoices and confirmed duplicates) or if the invoice is already fully or
partially paid.
Discount 1 Percentage
Cash discount percentage rate applied to the shortest payment period
Discount 2 Percentage
Cash discount percentage rate applied to the second payment period
Discount Amount 1
Amount of cash discount for the shortest payment period in document currency
Discount Amount 1 in Rep. Crcy
Amount of cash discount for the shortest payment period in reporting currency
(as entered in the selection screen)
Discount Amount 2
Amount of cash discount for the second payment period in document currency
Discount Amount 2 in Rep. Crcy
Amount of cash discount for the second payment period in reporting currency
(as entered in the selection screen)
Discount Light Icon
Icon that is indicating,

• whether cash discount 1 (shortest payment period) or cash discount 2

(second payment period) are still possible or have been missed, or
• how far it is to cash discount 1 date (shortest payment period),

depending on the configuration settings in your system.

The quick info to the discount light icon provides some more details.
Document Status
Status ID of DP document

48 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

DP ID before restart
ID of a previous DP document that was deleted and for which a new DP process
was started

Due Date
Due date of the invoice

End at
Time at which the last OpenText VIM for SAP process was finished

End on
Date when the last OpenText VIM for SAP process was finished

Enter at
Time at which the invoice entered the SAP system

Enter on
Date when the invoice entered the SAP system

Exception Reason
Current exception of the invoice, for example the current process type of a DP
document or the parking reason of a parked invoice

Invoice Type
Type of invoice, indicating whether the invoice is purchase order based or not

Invoice Type Text

Text for invoice type, indicating whether the invoice is purchase order based or
not

MM Invoice Document No.

SAP MM invoice number

Net Amount
Net Amount, as calculated in the DP indexing screen

Obsolete Reason Code

ID of reason code that was entered when deleting an invoice

Obsolete Reason Code Text

Text of reason code that was entered when deleting an invoice

Old Company Code

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

Old Doc Num

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

Old Fiscal Year

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 49

Chapter 3 VIM Analytics: Detailed Invoice Report

Paid at
Time of the last partial or complete payment
Paid on
Date of the last partial or complete payment
Parked at
Time at which the parked SAP invoice was created or at which the SAP invoice
was parked
Parked on
Date when the parked SAP invoice was created or when the SAP invoice was
parked
Plant
Plant from invoice line items
If multiple different plants are assigned, * is displayed.
Posted at
Time at which the posted SAP invoice was created or at which the SAP invoice
was posted
Posted by
User who created the posted SAP invoice or who posted the SAP invoice
Posted on
Date when the posted SAP invoice was created or when the SAP invoice was
posted
Posting Date
Posting Date in the invoice; this date is used when entering the document in
Financial Accounting or Controlling
Predecessor Object Key
Object key of an invoice that was deleted or cancelled and re-entered by another
invoice
Priority
Document priority
Purchasing Document
Purchasing document number from invoice header, invoice items and purchase
order list.
If multiple different purchase orders are assigned, * is displayed.
Reversal Doc#
Number of reversal document
Revsed F_Year
Fiscal year of reversal document
SAP Process Status
Status ID of the SAP invoice

50 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

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

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

SAP Process Status Text

Status of the SAP invoice

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

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

Start at
Time at which the DP workflow started

Start on
Date when the DP workflow started

Successor Object Key

Object key of the successor invoice that was entered after deletion or
cancellation of another invoice

Tax Code
SAP tax code

Total Amount in Rep. Crcy.

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

Unblock at
Time at which the payment block was removed from the MM invoice document
or posting time if there was no payment block

Unblock on
Date when the payment block was removed from the MM invoice document or
posting date if there was no payment block

Update Date
Date of the last change of the invoice

Note: Even doing an approval step is defined as a change in this context.

Update Time
Time of the last change of the invoice

Note: Even doing an approval step is defined as a change in this context.

Vendor Name
First and last name of the vendor as entered in the invoice. If there are no values
in the invoice, the names of the vendor are taken from the vendor master data.

VIM Process Status Text

Overall process status of the invoice

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 51

Chapter 3 VIM Analytics: Detailed Invoice Report

3.4.6 Detail pane

The detail pane displays additional information about the document that is selected
in the result list. You can choose the following tabs:

• Processes
• Image
• Line Items
• History
• Comments
• Vendor Workspace

Further (or less) tabs may be available depending on the configuration.

If you change the selection in the result list, the detail pane automatically switches to
the newly selected document.

Processes
This tab shows the OpenText VIM for SAP workflows of the document that is
selected in the result list.

The ALV grid control of the Processes tab provides some action buttons.

Click the small arrow on the right side of the button to choose or change the
layout. For more information, see Choose Layout on page 46.

Display Workflow Log

Select a workflow in the Processes tab and click this button to display detailed
workflow information.

The Process State column displays one of the following icons, indicating the status
of the workflow:

The workflow is currently processed in the background.

The workflow is currently waiting for a user action.

The workflow is completed.

The workflow is currently in error (technical workflow error).

52 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

The font and background color in the lines of the Processes tab indicate whether
user interaction is required.

Black
Black font indicates that user interaction is required.
Gray
Gray font and a very light gray as background color indicate completed
workflows or workflows that are currently processed in background.
Red
The background color is red if the process is on error.

In case of a parallel workflow, the Processes tab displays more than one line with
different agents.

Image
This tab displays the scanned image of the original invoice that is selected in the
result list.

Line Items
This tab displays the line items of the document that is selected in the result list.

The ALV grid control of the Line Items tab provides an action button.

Click the small arrow on the right side of the button to choose or change the
layout. For more information, see Choose Layout on page 46.

History
This tab displays the history of the document that is selected in the result list. It
displays Process History and Approval History.

The ALV grid control of the History tab provides an action button.

Click the small arrow on the right side of the button to choose or change the
layout. For more information, see Choose Layout on page 46.

Comments
This tab displays the comments of the document that is selected in the result list. It
displays Process Comments and Approval Comments.

The translation service might be implemented on your system. To display

translations of the comments, click next to the Comments tab, and then click the
wanted language.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 53

Chapter 3 VIM Analytics: Detailed Invoice Report

Vendor Workspace
This tab displays the OpenText Content Management for SAP Solutions plug-in for
the work item. OpenText Content Management for SAP Solutions allows you to
access related OpenText Content Server items in the business workspace without
leaving the SAP system.

For a comprehensive description, see Section 6 “Working in SAP ERP with the
Business Content window” in OpenText Content Management for SAP Solutions - User
Guide (ERLK-UGD)

3.4.7 Understanding process view fields

This section provides explanations for fields in the process view that are not self-
explanatory. The fields are sorted alphabetically by name.

Accounting Document No.

SAP FI invoice number
Note: This field is populated only for OpenText VIM for SAP processes
that are related to a SAP FI invoice, for example at the parking workflow of
a SAP FI invoice.
Approval Path
Approval path in case of parallel approval processes
Block Reason
Block reason in case of a blocked workflow
Company Code
Company Code of the SAP invoice document
Note: This field is populated only for OpenText VIM for SAP processes
that are related to a SAP FI invoice, for example at the parking workflow of
a SAP FI invoice.
Current Agent
Agent that is currently assigned for processing the OpenText VIM for SAP
process
If multiple different agents are assigned, * is displayed.
Current Role
Role that is currently assigned for processing the OpenText VIM for SAP process
Current Task
Technical ID of the current workflow task
Current Workitem ID
Work item ID of the current workflow task
Cycle Time
Duration of the OpenText VIM for SAP process from the point in time when the
workflow was started to the point in time when the workflow was finished

54 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

Dialog Flag
Indicator whether the current task is a dialog task or not (background task)

Document ID
DP Document ID

End at
Time at which the OpenText VIM for SAP workflow was finished

End on
Date when the OpenText VIM for SAP workflow was finished

Exception Reason
Current exception of the OpenText VIM for SAP process, for example the
current DP process type, the parking reason or the block reason

Fiscal Year
Fiscal year of the SAP invoice document

Note: This field is populated only for OpenText VIM for SAP processes
that are related to a SAP FI invoice or a SAP MM invoice, for example at
the parking workflow of a SAP FI invoice or of a SAP MM invoice.

Invoice Item
Item number of SAP invoice that is processed by the OpenText VIM for SAP
workflow

Note: This field is populated only for the block workflow on SAP MM
invoice line items

MM Invoice Document No.

SAP MM invoice number

Note: This field is populated only for OpenText VIM for SAP processes
that are related to a SAP MM invoice, for example at the blocking
workflow of a SAP MM invoice.

Option Id
ID of the last process option executed

Option Text
Text of the last process option executed

Option Type
Type of the last process option executed

Park Reason
Parking reason in case of a parking workflow

Priority
Priority of the OpenText VIM for SAP workflow

Process State
For a description of this field, see “Processes” on page 52.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 55

Chapter 3 VIM Analytics: Detailed Invoice Report

Process Type
DP process type
Start at
Time at which the OpenText VIM for SAP workflow was started
Start on
Date when the OpenText VIM for SAP workflow was started
Update Date
Date when the OpenText VIM for SAP workflow was processed the last time
Update Time
Time at which the OpenText VIM for SAP workflow was processed the last time
WF Type Text
Text for the OpenText VIM for SAP workflow type

Example:

• Document Process Workflow

• Parked PO Invoice Workflow

WI Status
Current status of the OpenText VIM for SAP workflow. The following values are
available:
50 - Waiting
These are workflows with a current work item that is not yet visible in the
VIM Invoice Workplace. This can have one of the following reasons:

• The work item could be created but the condition for the step Create
Work Item is not yet fulfilled (SAP work item status: CHECKED).

• The work item cannot be executed yet and therefore cannot be seen in
the Business Workplace or the VIM Invoice Workplace yet (SAP work
item status: WAITING).

51 - In Process
These are workflows with a current work item that has one of the following
statuses:

• Available for execution (SAP work item status: READY),

• Reserved by a recipient (SAP work item status: SELECTED),
• Currently being processed (SAP work item status: STARTED)
• Already been executed once but processing is not yet completed (SAP
work item status: COMMITED)

52 - Completed
These are workflows with the following statuses:

56 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

• Processed fully and successfully (SAP work item status: COMPLETED)

• No longer processed (SAP work item status: CANCELLED)

54 - Error in Workflow
These are workflows with a current work item that has the following status:

• Error status (SAP work item status: ERROR)

WI Status Text
Text for the current status of the OpenText VIM for SAP workflow
Workflow
Work item ID of the workflow instance
Workflow Definition
Technical ID of the workflow template
Workflow Type
ID of OpenText VIM for SAP workflow type
Example:

• 1 – Document Process Workflow

• 2 – Parked PO Invoice Workflow

3.4.8 Understanding line item fields

This section provides explanations for fields in the line item view that are not self-
explanatory. The fields are sorted alphabetically by name.

Amount
Amount in document currency
Amount in Rep. Crcy.
Amount in reporting currency (as entered in the selection screen)
Document ID
DP Document ID
Document Item ID
ID of DP document line item
Item
Item number of purchasing document
Text
Line item text
G/L Account, Cost Center, and other accounting objects
Accounting object of invoice line item or purchase order in case of PO based DP
document

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 57

Chapter 3 VIM Analytics: Detailed Invoice Report

If multiple different G/L accounts, cost centers, and so on exist, * is displayed.

3.4.9 Getting aggregated key figures

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

• how many invoices are currently processed per role

• the average or the maximum processing time of documents per vendor
• the total invoice amount per company code, separated in PO based and NPO
based invoices

These key figures and many more can be determined by ALV grid standard features.
This section gives you an idea how this works and what is possible. For more
detailed information to the ALV grid and its features, see the SAP documentation.

[Link] Example 1: Getting the number of invoices currently processed

per role
To get the number of invoices currently processed per role:

1. Launch the new VAN report with selection criteria Current Role not equal to
the empty value.

To get all invoices displayed, you may have to change the value for selection
field Maximum Number of Records.

Important
If you have thousands or even millions of invoices, ensure that you add
further selective selection criteria, for example a range for the document
date, a vendor and a company code. If runtime is still slow, ask your
system administrator to check for appropriate database indexes.

2. In the list of all invoices that are currently being processed, click the small arrow
on the right side of the Choose Layout button.

3. Click Change Layout.

4. In the Change Layout dialog box, select the Current Role column and use the
arrow buttons to set this column at the first position of the Displayed Columns
pane.

5. Select the Number of Documents column and use the arrow buttons to set this
column at the second position of the Displayed Columns pane.

6. Select the Aggregation check box for the Number of Documents column.

58 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

7. To close the Change Layout dialog box, click .

8. In the Results list, select the first column header (the Current Role column) and
press the Subtotal button to get subtotals per role.
You may want to see the lines with the subtotals as a summary without the
documents in between. In this case, continue with the following steps.

9. Click the small arrow on the right side of the Subtotal button.

10. Click Drilldown Total Level.

11. In the Determine drilldown totals level dialog box, select Level 1 Current
Role.

12. To close the dialog box, click .

The number of invoices currently processed per role is displayed.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 59

Chapter 3 VIM Analytics: Detailed Invoice Report

13. You may want to know which invoice documents there are in detail for one
role. In this case, click the icon next to the current role.
You may want to return to the view where all documents are shown with
subtotals. In this case, continue with the following steps.

14. Click the small arrow on the right side of the Subtotal button.

15. Click Drilldown Total Level.

16. In the Determine drilldown totals level dialog box, select Level 0 Non-total
lines.

17. To close the dialog box, click .

Note: You can save your preferred layout with the Save Layout option of
the Choose Layout button.

60 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

[Link] Example 2: Getting the average or maximum processing time of

documents per vendor

To get the average or maximum processing time of documents per vendor:

1. Launch the new VAN report with appropriate selection criteria.

Important
If you have thousands or even millions of invoices, ensure that you enter
selective selection criteria. If runtime is still slow, ask your system
administrator to check for appropriate database indexes and the
configuration of the VAN report.

You get a list of all invoices matching your selection criteria.

2. Click the small arrow on the right side of the Choose Layout button.

3. Click Change Layout.

4. In the Change Layout dialog box, select the Vendor column and use the arrow
buttons to set this column at the first position of the Displayed Columns pane.

5. Select the Processing Time (in Sec) column and use the arrow buttons to set
this column at the second position of the Displayed Columns pane.

6. To close the Change Layout dialog box, click .

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 61

Chapter 3 VIM Analytics: Detailed Invoice Report

7. Select the second column header (the ProcTime column) in the Results list, and
click the small arrow on the right side of the Total button.

8. If you want to get the average processing time of documents per vendor, click
Mean Value.
If you want to get the maximum processing time of documents per vendor, click
Maximum.

9. In the Results list, select the first column header (the Vendor column) and click
the Subtotal button to get the subtotals per vendor.
You may want to see the lines with the subtotals as a summary without the
documents in between. In this case, continue with the following steps.

10. Click the small arrow on the right side of the Subtotal button.

11. Click Drilldown Total Level.

12. In the Determine drilldown totals level dialog box, select Level 1 Vendor.

13. To close the dialog box, click .

Depending on your selection in step 8, you get a list of the average processing
time or the maximum processing time in seconds per vendor.
You may want to know which invoice documents there are in detail for one
vendor.

14. In this case, click the icon next to the vendor.

You may want to return to the view where all documents are shown with
subtotals. In this case, continue with the following steps.

15. Click the small arrow on the right side of the Subtotal button.

16. Click Drilldown Total Level.

17. In the Determine drilldown totals level dialog box, select Level 0 Non-total
lines.

18. To close the dialog box, click .

Note: You can save your preferred layout with the Save Layout option of
the Choose Layout button.

62 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.4. Using report results

[Link] Example 3: Getting the total invoice amount per company code,
separated in PO and Non PO invoices
You want to see the total invoice amount per company code. For every company
code, you want to have a subtotal for PO based and for Non PO based invoices.

Getting the total invoice amount per company code, separated in PO and NPO
invoices:

1. Launch the new VAN report with appropriate selection criteria.

Important
If you have thousands or even millions of invoices, ensure that you enter
selective selection criteria. If runtime is still slow, ask your system
administrator to check for appropriate database indexes and the
configuration of the VAN report.

You get a list of all invoices matching your selection criteria.

2. Click the small arrow on the right side of the Choose Layout button.

3. Click Change Layout.

4. In the Change Layout dialog box, select the Company Code column and use the
arrow buttons to set this column at the first position of the Displayed Columns
pane.

5. Select the Invoice Type Text column and use the arrow buttons to set this
column at the second position of the Displayed Columns pane.

6. Select the Total Amount in Rep. Crcy column and Reporting Currency, and use
the arrow buttons to set theses columns at the third and fourth position of the
Displayed Columns pane.

7. Select the Aggregation check box for the Total Amount in Rep. Crcy column.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 63

Chapter 3 VIM Analytics: Detailed Invoice Report

8. To close the Change Layout dialog box, click .

9. Select the first column (Company Code) and the second column (Invoice Type
Text) in the Results list and click the Subtotal button to get subtotals for the
company code and invoice type combination.

You may want to see the lines with the subtotal as a summary without the
documents in between. In this case, continue with the following steps.

10. Click the small arrow on the right side of the Subtotal button.

64 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.5. VIM Analytics and mass data

11. Click Drilldown Total Level.

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

13. To close the dialog box, click .

You get a list of the total invoice amounts for the company code and invoice
type combination.

14. You may want to know which invoice documents there are in detail for one
company code and invoice type combination. In this case, click the icon next
to the invoice type text.
All invoice documents of this company code and invoice type combination are
shown.
You may want to return to the view where all documents are shown with
subtotals. In this case, continue with the following steps.

15. Click the small arrow on the right side of the Subtotal button.

16. Click Drilldown Total Level.

17. In the Determine drilldown totals level dialog box, select Level 0 Non-total
lines.

18. To close the dialog box, click .

Note: You can save your preferred layout with the Save Layout option of
the Choose Layout button.

3.5 VIM Analytics and mass data

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

Use restrictive selection criteria

This is the most important principle. Try to limit the number of invoices to be
selected to a minimum. Therefore, use appropriate selection values on the
selection screen. Do not select a huge number of invoices and then filter and sort
in the result list.
Notes

• When working without ABAP Core Data Services views (ABAP CDS
views), the selection fields Overall Process Status and Maximum
Number of Records are not working as restrictive selection criteria. Find
more details in Selection fields for the Overall Process Status

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 65

Chapter 3 VIM Analytics: Detailed Invoice Report

on page 66 and Selection field Maximum Number of Records

on page 67.
• In case you use very restrictive selection criteria but experience very
slow performance nevertheless, ask your OpenText VIM for SAP
consultant or system administrator to check if a database index might
help.
Limit the number of output fields in the result list
The result list provides about 100 columns. The more records you want to be
displayed in the result list, the more important becomes the number of columns
in the result list. Adjust the existing layout variants or create a new layout
variant for the result list. So you restrict the number of output columns to those
columns you need for your daily business. For more details about layout
variants, see Section 14.3 “Layout variants” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).

VIM Analytics There are additional recommendations when VIM Analytics was configured to work
without ABAP without ABAP CDS views on your system.
CDS views
Tips

• On a SAP® HANA database system, you can easily check if VIM Analytics
was configured to work with ABAP CDS views: Have a look at the title of
VIM Analytics. If it is VIM Analytics powered by SAP HANA, VIM
Analytics works with the ABAP CDS views. If it is VIM Analytics, VIM
Analytics does not use ABAP CDS views.
• On any database system different to SAP HANA, contact your system
administrator to get the information if VIM Analytics was configured to
work with ABAP CDS views or not.

Selection fields for the Overall Process Status

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

Example 3-1: Overall Process Status selection criteria

VIM Analytics is run with the following selection criteria:

66 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 3.5. VIM Analytics and mass data

Channel ID: SCAN

Overall Process Status - Selected Status: Blocked
Let us assume that there are five million invoices on the system. One
million of these invoices have channel SCAN, only 5,000 invoices are
blocked. When running VIM Analytics with these selection criteria, first, all
one million invoices with channel SCAN are selected and read into the
memory. Then, those 5,000 blocked invoices are filtered out. This means
that 995,000 invoices were read into the memory without need.

OpenText strongly recommends that you choose additional restrictive selection

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 67

Chapter 4
Using the VIM Analytics Current Liability Report

The VIM Analytics Current Liability Report is part of VIM Analytics. It offers you a
clear data report on documents that are parked in the system. The purpose of the
Current Liability Report is to provide the Accounts Payable department with
accurate information about the current liabilities at any point in time.

As a primary use, the Current Liability Report helps the Accounts Payable
department to do the accruals at month or period end. The Current Liability Report
provides you with various views of the data, enabling you to analyze the liability
information from various forms. The various views address the different accrual
procedures used by various companies.

The Current Liability Report considers parked invoice documents and optionally
credit memos that are in parked status. It also considers DP documents that were
created but have not been processed as SAP documents. Both PO invoices and Non
PO invoices are supported. There are various controls within the report, allowing
you to calculate sub totals, or to download to Excel.

You can restrict the output to lines that are within a certain amount range. This is
useful if your company’s internal policy is to ignore all lines that are below a certain
money limit.

4.1 Using the selection screen

You control all functions of the Current Liability Report using a common selection
screen.

To start the Current Liability Report:

• Run the /n/OPT/VAN_LIABILITY transaction.

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 69

Chapter 4 Using the VIM Analytics Current Liability Report

70 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 4.1. Using the selection screen

Note: Your screen might look different as you can configure what
selection fields should appear in the screen, using the Edit menu in the
menu toolbar.

Application toolbar
In the Application toolbar, the following button is available:
Execute the query. This action opens the report views screen, based on the
search criteria entered in the selection field panel.

Selection field panel

In the selection field panel, you enter the search criteria for the Current Liability
Report. You restrict the number of invoices that are considered for the report, by
entering appropriate criteria values.

Notes

• Your screen and the selection criteria might differ from the screenshot.
• For search criteria with two entry fields joined by a to, you can enter a value
range.
• If you run the query without entering any criteria, the report will consider all
criteria values.
• The following list only covers elements whose meaning is not obvious.

General Information

In this panel, enter general search criteria for the invoices.

Include Documents

In this panel, enter search criteria regarding which documents should be included.

Docs with no Acct Assignmt

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

Report View Group By

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 71

Chapter 4 Using the VIM Analytics Current Liability Report

Cost Center/GL Account (example for dual elements)

Group the result based on the Cost Center and then on the GL Account.

DP In Process
Select this check box to include DP documents that are still in process in the
result, for example, a document without an SAP document number that is not
deleted.
Note: If you are searching for DP documents by selecting the DP In
Process check box, the Company Code, Vendor, and Fiscal Year search
criteria are also considered when querying for DP documents.

SAP Invoice Information: Header Information

In this panel, enter search criteria for the invoice's header item.

Document Number
Enter the accounting document number of the invoice.
Fiscal Year
Enter the fiscal year when the invoice was blocked or parked.

DP Information

In this panel, enter search criteria for the Document Processing information.

Tip: Where applicable, click the icon for a list of available values.

Doc w/o Company Code or Vendor

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

72 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 4.2. Using the report views screen

4.2 Using the report views screen

The following views and major grouping options are available for the report:

Views

SAP Document Header View

Displays the data based on the document (SAP documents only); see “SAP
Document Header View” on page 77.
SAP Document Lines View
Displays the data based on the line item (SAP documents only); see “SAP
Document Lines View” on page 78.
DP View
Displays the DP document only; see “DP Information View” on page 79.

Groupings

Header Groups
Allows you to group the result based on the header level; see “Document header
grouping” on page 79.
Line Groups
Allows you to group the result based on the line level; see “Document lines
grouping” on page 81.

You can select views and groupings in the Report View Group By field of the
selection screen, see “General Information” on page 71. But also in the report views
screen, you can toggle between views and groupings in the menu bar and the
application toolbar.

Executing a search in the selection screen displays the report views screen, based on
the search criteria entered in the selection field panel.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 73

Chapter 4 Using the VIM Analytics Current Liability Report

The report views screen comprises the following sections:

• “Menu toolbar” on page 74

• “Application toolbar” on page 75
• “Overview section” on page 75
• “Report results (ALV Grid)” on page 75

4.2.1 Menu toolbar

Views menu
Switch between the different views.

Head Groups menu

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

Line Groups menu

Switch between different Line groupings.

Switch
Toggle sections in the report views screen on and off:
Header Off/Header On
Hide and unhide the Overview section.
Total On/Total Off
Hide and unhide the display of the Total in the report views screen.

74 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 4.2. Using the report views screen

4.2.2 Application toolbar

Header Off/Header On
See “Menu toolbar” on page 74.
Total On/Total Off
See “Menu toolbar” on page 74.
By Vendor/By Comp.
Group the results by Header: Vendor or Company Code
SAP Doc View/SAP Lines View/DP View
Switch between the different views of the report.

4.2.3 Overview section

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

4.2.4 Report results (ALV Grid)

The actual report results are displayed in the ALV Grid. The different views and
groupings have different columns; for a detailed description, see “Viewing and
grouping report results” on page 77. To get more details about the results, double-
click a row in the ALV Grid.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 75

Chapter 4 Using the VIM Analytics Current Liability Report

The Related List for the Chosen Items shows details of the documents that belong
to the chosen grouping. There are two different panels in the screen:

Document Header View

This panel lists the SAP documents that belong to the chosen grouping. In the
example screenshot, the panel shows all the documents that belong to Company
Code 3000 and Vendor 3000 from the ALV Grid.
DP Information
This panel lists the DP documents that belong to the chosen grouping.

Note: The DP Information panel only appears if you have selected the DP
In Process check box in the General Information panel of the selection
field panel. Moreover, the report views screen must be grouped By
Company Code or By Vendor.

In the example screenshot, the panel shows all DP documents that belong to
Company Code 3000 and Vendor 3000 from the ALV Grid.

76 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 4.3. Viewing and grouping report results

4.3 Viewing and grouping report results

For a list of the views and grouping options, see “Using the report views screen”
on page 73.

Note: You might notice that when you switch from one view to another view,
the total number of items does not equal or some of the items are missing. This
is by design; some of the items might be missing the appropriate grouping
column. For example, if you choose WBS Element grouping and the item does
not have any WBS Element, it will not be included in the Group View by WBS
Element.

4.3.1 SAP Document Header View

This view groups the report results based on the Document Number. It only
displays SAP documents even if the search returned DP documents.

To display the SAP Document Header View, click SAP Doc View in the application
toolbar.

The SAP Document Header View comprises the following columns in the ALV
Grid:

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

Reference #
Reference number of the vendor
Total Amount
Gross amount specified in the header level
Line Amount
Line amount of the invoice
# of Lines
Total number of lines in the SAP document. In case of PO invoices, it is the
number of PO lines in the invoice. In case of Non PO invoices, it is the number
of G/L lines.
User Name
User who created the invoice

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 77

Chapter 4 Using the VIM Analytics Current Liability Report

4.3.2 SAP Document Lines View

This view groups the report results based on the invoice lines. It only displays SAP
documents even if the search returned DP documents.

To display the SAP Document Lines View, click SAP Lines View in the application
toolbar.

The SAP Document Lines View comprises the following columns in the ALV Grid:

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

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

78 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 4.3. Viewing and grouping report results

4.3.3 DP Information View

This view groups the report results based on the DP document number.

To display the DP Information View, click DP View in the application toolbar.

Note: If you have entered search criteria other than Fiscal Year, Company
Code and Vendor in the selection screen, those other criteria are not
considered in the DP Information View because those criteria are not relevant
in DP documents.

The DP Information View comprises the following columns in the ALV Grid:

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

Document ID
DP document number

Credit Memo
An X in this column indicates that the DP document is a credit memo.

Document Date
Date when this DP document was created

Reference
Reference number of the vendor

Purchasing Document
PO of the document

Total Amount in Document Currency

Gross amount specified in the header level

Total Amount in Report Currency

Total amount in the currency that is selected in the selection field panel

4.3.4 Document header grouping

The following groupings by document header are available:

• Company Code
• Vendor

To group the report results by Company Code or Vendor, click the appropriate
Group by button in the application toolbar. The following example screenshot
shows a grouping by Company Code.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 79

Chapter 4 Using the VIM Analytics Current Liability Report

A section In the A section of the example screenshot, all items have a Company Code, a
Vendor # and a Vendor Name assigned. This indicates that all documents are
already processed and have a Company Code and a Vendor Number. If you have
selected the DP In Process check box in the General Information panel of the
selection field panel, the row will also include DP items. These DP items have been
indexed with both Company Code and Vendor Number.

B section In the B section of the example screenshot, all items have no Company Code and no
Vendor # assigned. The Vendor Name is DP not Indexed. This indicates that the
documents in this section are DP documents that were created but not indexed at all.

Note: This section is displayed only if you have selected the DP In Process
check box in the General Information panel of the selection field panel.

The document header grouping comprises the following columns in the ALV Grid:

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

# of Docs
Number of documents in the group

Total Amount
Gross amount specified in the header level

Line Amount
Amount from all invoice lines of the invoice

80 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 4.3. Viewing and grouping report results

4.3.5 Document lines grouping

The following groupings by document lines are available:

• By Cost Center/ GL account

• By Internal Order / GL account
• By WBS Element/ GL account
• By Network Activity/ GL account
• By GL / Cost Center
• By GL / Internal Order
• By GL / WBS Element
• By GL / Network Activity
• By Balance Sheet

Example: If you select the grouping By Cost Center/ GL account, the result is grouped based
on the Cost Center first and then based on the GL Account.

To group the report results by document lines, click the appropriate menu entry in
the Line Groups menu. The following example screenshot shows a grouping By
Cost Center/ GL account.

The document lines grouping comprises the following columns in the ALV Grid:

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 81

Chapter 4 Using the VIM Analytics Current Liability Report

Notes

• The following list only covers columns whose meaning is not obvious.
• Depending on the grouping, some of the columns might not be displayed.

Internal Order
Internal Order number of the invoice's line item
WBS Element
WBS Element of the invoice's line item
Network
Network ID
Activity
Activity ID
G/L Account
General Ledger Account
# of Lines Included
Number of accounting lines in the group
Line Amount
Amount from all invoice lines of the invoice

82 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 5
Using the Automation Report

The Automation Report is a tool that provides data about automated and manual
processing steps of OpenText VIM for SAP documents.

Note: The Automation Report has been designed to track documents coming
in using a channel that includes OCR extraction. If no OCR extraction has been
done for the document, you do not find the document in the Automation
Report.

The data is contained in table /OPT/VT_ATM_SRC. The table is filled by the ATM
collection report, which can be scheduled in the background. For details about the
ATM collection report, see Section 29 “Automation report” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).

The program “Automation Report” allows to view and export the table contents.
The current version of the Automation Report does not do any counting or
calculation.

5.1 Using the selection screen

You control all functions of the Automation Report using a common selection
screen.

To start the Automation Report:

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

Alternatively, in OpenText VIM - Invoice Solution, navigate to SAP menu >
Reports > Automation Report.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 83

Chapter 5 Using the Automation Report

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

Company Code, Vendor

Restrict the output according to the current value of vendor and company
code in the /OPT/VIM_1HEAD table.
Document ID, Channel ID, DP Document Type
Restrict the output according to DP document number, Channel ID, and DP
Document Type.
Vendor from Capture/Extraction
Restrict the output according to the vendor after extraction. In particular,
you can select <empty> to have an overview over the documents where the
vendor could not be found by OpenText Core Capture for SAP Solutions or
OpenText Capture for SAP Solutions.
Document Date, Scan Date, Posting Date
Restrict the output according to document creation date, scanning date, and
posting date.

Report Options

Only Finalized Documents

Select this check box to consider only documents that are posted and not
blocked. These documents are in a final status for the Automation Report
and will never be changed again. For a long-term evaluation and for a
comparison over time, you should only consider these entries.

84 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 5.2. Using the report screen

Layout
Select one of the defined layouts if you have saved a personal layout using
the ALV grid control, before. For more information, see “Custom layouts
for the ALV grid” on page 89.

3. Create variants in the selection screen.

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

5.2 Using the report screen

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

5.2.1 ALV grid control

The ALV grid control of the Automation Report displays some standard options for
the ALV grid and three additional buttons to navigate to the document image, to the
DP document, and to the SAP document.

To navigate to the change documents, double-click into column No of Changes, see

also Table 5-3: “Automation related fields” on page 87, column No of Changes.

Notes

• Change documents for object class /OPT/VIM_IDXDAT build the basis of data
for the automation report.
• Change documents are technically stored in two SAP tables: CDHDR for the
header data and CDPOS for the detailed data.

5.2.2 Report results (ALV grid)

The report screen shows a number of columns, which are arranged in two parts by
default:

• Invoice data
• Automation data

Use the horizontal scroll bar to display all columns.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 85

Chapter 5 Using the Automation Report

Invoice data

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

Table 5-1: Key fields

Technical Field Description (column Meaning - Usage - Notes

Name name)
* LOGSYS Logical system Name of the current logical system
DOCID Document Id DP document number to identify the
document. The Document Id matches /
OPT/VIM_1HEAD.

Table 5-2: Document related fields

Technical Field Name Description (column Meaning - Usage - Notes

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

86 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 5.2. Using the report screen

Technical Field Name Description (column Meaning - Usage - Notes

name)
BLDAT Document Date From /OPT/VIM_1HEAD
LIFNR_SAP Vendor From /OPT/VIM_1HEAD, field LIFNR
CHANNEL_ID Channel ID From /OPT/VIM_1HEAD
SCAN_DATE Scan date From /OPT/VIM_1HEAD
BUDAT Posting Date From /OPT/VIM_1HEAD
INV_TYPE Invoice Type From /OPT/VIM_1HEAD, field DP_
DOCTYPE and /OPT/VIM_T100, field
inv_type

* SENT_TO_SYSTEM Receiving System From /OPT/VIM_1HEAD, field

TARGET_SYSTEM

Automation data

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

Table 5-3: Automation related fields

Technical Field Name Description (column Meaning - Usage - Notes

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 87

Chapter 5 Using the Automation Report

Technical Field Name Description (column Meaning - Usage - Notes

name)
FLAG_POSTED_BG Posted in BG From CDHDR, Tcode POSTING. Check
box is selected if username is WF-
BATCH (hardcoded).

FLAG_VAL_SKP Vali Skipped From CDHDR, Tcodes EXTRACTION

and VALIDATION. The check box is
selected if an EXTRACTION header
entry exists, but no VALIDATION
header entry.
FLAG_FIRST_PASS First Pass From /OPT/VIM_1HEAD , field
NOFIRSTPASS (inverted value). The
First Pass check box means that an
invoice could be posted without any
exceptions. For more details, see “First
Pass” on page 117.

Note: This value is taken from

the data collection for the Key
Process Analytics Report.
FLAG_BLOCKED Blocked From /OPT/VIM_1LOG and /OPT/
CT_LG_HIST (check box)

Note: The indicator is set if the

invoice was blocked in the
posting. It does not display the
current status, that means, if the
invoice was blocked and
subsequently released, this
particular report shows it as
blocked, to indicate that there
have been discrepancies and the
data quality might need to be
checked.
NUMBER_OF_CDHDR No of Changes From CDHDR. Number of header
entries. To view the change
documents, these fields allow
navigation to the SAP standard report
RSSCD100: Double-click in the
respective field.
NUMBER_OF_MANCHG No of Manual From CDHDR. Number of header
Changes entries with Tcode VALIDATION,
APPROVAL, or INDEXSCREEN.

NUMBER_OF_TOUCH Number of Touches From /OPT/VT_WI. This field requires

the Central Reporting infrastructure.

Note: This value is taken from

the data collection for the
Productivity Report.

88 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 5.2. Using the report screen

Technical Field Name Description (column Meaning - Usage - Notes

name)
VALIDAT_CHANGE ValidationChg The indicator is set to V if any of the 7
fields listed at the end of this table has
been changed during validation.
VIM_CHANGE VIM Changed The indicator is set to D if any of the 7
fields listed at the end of this table has
been changed during OpenText VIM
for SAP processing.
SAP_CHANGE SAPChanged The indicator is set to P if any of the 7
fields listed at the end of this table has
been changed after OpenText VIM for
SAP processing.
ATM_FINAL Final Status The indicator is set to C if the
document is in a final state, that is
posted and not blocked.

STATUS_BUKRS CompCodeChg These 7 fields are checked when

displaying the values for the indicators
STATUS_LIFNR VendorNbrChg VIM changed, SAP changed, and
STATUS_XBLNR ReferenceNbrChg Validation changed.
If at least one of these fields has been
STATUS_EBELN PONumberChanged changed in validation, OpenText VIM
STATUS_WRBTR Amount Chg for SAP processing, or during posting,
the respective indicator is set.
STATUS_VAT_AMT Vat Amt Chg
Note: For Amount Chg, only
STATUS_WAERS Currency Chg gross amount is considered.

5.2.3 Custom layouts for the ALV grid

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

If you do not maintain the Central Reporting infrastructure, OpenText recommends

that you remove the column Number of Touches from the layout.

If you are using a multiple backend configuration, it might be useful to have

different layouts for the central system and the satellite systems.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 89

Chapter 6

Using the Invoice Life Cycle Report

The Invoice Life Cycle Report (ILC) is a tool that provides data about the complete
life cycle of a OpenText VIM for SAP document. All OpenText VIM for SAP
processes that a document goes through can be monitored using the ILC.

The source data for the ILC is contained in the /OPT/VT_ILC_SRC table. This table is
filled by the ILC collection report, which can be scheduled in the background. For
details about the ILC collection report, see Section 7.1.2 “Scheduling batch jobs for
Invoice Life Cycle” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIMZ-AGD).

6.1 Using the selection screen

You control all functions of the ILC using a common selection screen.

To start the ILC:

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

Alternatively, in OpenText VIM - Invoice Solution, navigate to SAP menu >
Reports > Invoice Life Cycle Report.

2. In the Life Cycle Report selection screen, configure the following parameters
for the report:

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 91

Chapter 6 Using the Invoice Life Cycle Report

Process Data

Document ID
Enter the DP ID of the document in OpenText VIM for SAP.
Company Code
Enter the company code in the DP document.
Vendor
Enter the vendor in the DP document.
Document Date
Enter the date of the document.
DP Document Type
Enter the document type of the DP document (NPO_S4, PO_S4, and so on).
Process Type
Enter the current exception of the document (for example Invalid vendor
number or Invalid UOM).

Document Status
Enter the current status of the DP document (for example Posted, Indexed,
or Obsolete).
Fiscal Year
Enter the fiscal year of the document.
Current Agent
Enter the current agent with whom the document is currently available.
Current Role
Enter the current role with whom the document is currently available.

The ILC report can be displayed in 2 forms based on the following selection:
Layout

• Click Classical ALV, also known as Simple ALV (default).

If you have saved a personal layout using the ALV grid control, before, you
can also enter one of your personal layouts in the Layout field. For more
information, see “Custom layouts for the ALV grid” on page 96.
• Click Hierarchy ALV.
• For more information , see the following sections.

92 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 6.2. Using the report screen

6.2 Using the report screen

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

Note: To get the data in ILC, the ILC collection report must be executed once in
Full mode to get the data in the source table.

6.2.1 ALV grid control

Classical ALV If run as classical ALV, the ALV grid control of the ILC displays some standard
options for the ALV grid and two additional buttons VIM Analytics and Sync:

VIM Analytics
Click this button to navigate to VIM Analytics for the selected documents.
Sync
Click this button to update the source table for the selected document instantly.
This is useful if any changes have been made in the DP and the ILC collection
report has not been run.
Note: If you do not want to update the document instantly in the source
table using the Sync button, it is updated when the ILC collection report
runs again the next time.

Hierarchy ALV In the current version, the hierarchy ALV does not provide any add-on functionality
in the ALV grid control, apart from the standard ALV grid options.

6.2.2 Report results

Classical ALV The report displays the document information in the following 2 parts:

• The first line for all documents is the header line. It contains the fields that are
common for all logs, such as Company Code, Vendor, DP Document Type, and
so on.
• The lines after the header line contain the information of the work item. All the
processes that the DP document has gone through, are displayed in descending
order. This means, the latest work item is displayed on top. The work item
information lists the respective exceptions, status, responsible agents, and so on.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 93

Chapter 6 Using the Invoice Life Cycle Report

Hierarchy ALV Like in the classical ALV, the results are displayed with header and work item data
separated.

The first line always shows the header. Click the + icon to expand the details and
display the work item data.

In the current version, it is not possible to navigate to VIM Analytics or to

synchronize the source table, when ILC is run in hierarchy mode.

Table 6-1: Header fields in ILC

Description (column
Technical field name Meaning - usage - notes
name)
DP document number to
identify the document. The
DOCID Document ID
document ID matches /OPT/
VIM_1HEAD.

94 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 6.2. Using the report screen

Description (column
Technical field name Meaning - usage - notes
name)
The logical system for which
the ILC is run. (currently not
LOGSYS Logical system
supporting multiple backend
systems)
The SAP accounting document
Accounting document
BELNR_FI number for the DP from /OPT/
number
VIM_2HEAD

Company code of the DP

BUKRS Company code
from /OPT/VT_ILC_SRC
Name of company code or Name of company from /OPT/
BUTXT
company VT_BUKRS

Account number of Vendor number for the DP

LIFNR
vendor from /OPT/VIM_1HEAD
Vendor name from /OPT/VIM_
VEND_NAME Vendor name
1HEAD

DP document type from /OPT/

DOCTYPE Document type
VT_ILC_SRC

DP document status from /

STATUS Document status
OPT/VT_ILC_SRC

Status text from /OPT/VIM_

STATUS_TEXT Document status text
T101T

Fiscal year of the DP from /

GJAHR Fiscal year
OPT/VIM_1HEAD

PROCESS_DURATION Cycle time Calculated

Table 6-2: Work item fields in ILC

Description (column
Technical Field Name Meaning - Usage - Notes
name)
The ID of the work item logs, the
LINEID Line number
order in which they were executed.
Description of the action from /
FUNC_TEXT Function text
OPT/VT_ILC_SRC

Log type (DP, AP, BL, and Type of work item log from /OPT/
LOGTYPE
so on) VT_ILC_SRC

Exception description from /OPT/

PROC_TEXT Process type
VIM_T800T

The responsible role for the

ACTUAL_ROLE Responsible party
individual work item
OpenText user mapping The responsible agent for the
ACTUAL_AGENT
object ID individual work item

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 95

Chapter 6 Using the Invoice Life Cycle Report

Description (column
Technical Field Name Meaning - Usage - Notes
name)
The actual start date of the WI
START_DATE Actual start date
process
The actual start time of the WI
START_TIME Actual start time
process
The actual end date of the WI
END_DATE Actual end date
process
The actual end time of the WI
END_TIME Actual end time
process
Time taken for the WI process to be
completed
Processing time (in
PROCTIME Calculated only for the dialog
seconds)
processes and not for background
processes

6.2.3 Custom layouts for the ALV grid

OpenText recommends that you create custom layouts for the ALV grid of the ILC
report. In the ALV grid control, you can use Choose Layout to choose, change,
save, and manage layouts.

96 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 7
Using the common infrastructure of Central
Reporting reports

The reports in Central Reporting mostly share a common infrastructure. This

chapter describes the infrastructure elements that are the same in all reports. For
specific elements valid only for a particular report, see the chapter of the respective
report. The following elements are identical for all reports:

Selection screen
You control all functions of the particular report using a common selection
screen.
Note: In the Key Process Analytics Report, the selection is integrated into
the main screen that also shows the individual report panels. However, the
functionality is equal to the other reports.
Report screen
The report screen comprises: Header Section, ALV Grid Control, Report Results
(ALV Grid), and Details Screen
Notes

• In the Central Audit Report, only ALV Grid Control and Report Results
(ALV Grid) are available.
• The Key Process Analytics Report does not display the results in a report
screen but in individual report panels; see “Using the individual report
panels” on page 112.

7.1 Using the selection screen

To start a report, navigate to OpenText VIM - Invoice Solution > SAP menu >
Reports > Central Reporting, and double-click the report.

The selection screen opens. It comprises the application toolbar and the selection
field panel.

Figure 8-1 on page 102 shows an example of the selection screen.

Application toolbar
You can perform the following action:
Execute.
The report creates and displays a report, using the current settings in the
selection field panel.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 97

Chapter 7 Using the common infrastructure of Central Reporting reports

Selection field panel

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

Tips

• Where applicable, click the icon for a list of available values.

• For search criteria with two entry fields joined by a to, you can enter a
value range.
• If you do not specify search criteria in a field, the search includes all
available values.

System or Logical System

Enter the logical system name. Logical systems are the central system and
the satellite systems in a multiple backend scenario.

Channel or Channel ID
Enter the Channel ID. The channel indicates the input mode of invoices into
OpenText VIM for SAP. For example, the channel ID IDOC stands for
invoices imported using Electronic Data Interchange.
This parameter is not available in the Summary Report.
Currency or Reporting Currency
Mandatory field. Enter the currency for the report. The amounts of all
documents will be translated into this currency, using the exchange rate
valid at the Currency Translation Date.
The currency parameters are not available in the Central Audit Report, the
Productivity Report, and the Aging Report.

Currency Translation Date

Select the date whose exchange rate should be used for currency translation:
C
Current date
D
Document date
P
Process start date
P is the default value.

Layout
Enter the layout for the report if you have saved a personal layout using the
ALV grid control, before.

98 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 7.2. Using the report screen

7.2 Using the report screen

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

Figure 8-2 on page 103 shows an example of the report screen.

The report screen comprises:

Header Section
The header section of the report screen displays date and time of the last update,
and of the current run of the respective report.

Tip: If you feel the data needs to be updated, contact your administrator.

For some reports, the header section also shows the selection criteria that you
have entered in the selection field panel.

ALV Grid Control

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

Report Results (ALV Grid)

The report results differ for the particular reports. Therefore, see the respective
Report Results (ALV Grid) sections of the particular reports.

Details Screen
The details screen differs for the particular reports. The following button in the
ALV grid control of the details screen is common for all reports that have a
details screen (except the Aging Report):

Image
You can display the scanned image of the original invoice of a OpenText
VIM for SAP document in the Image Viewer that is installed and configured
on your desktop: Select a line in the table and click Image.

For individual settings of the details screens, see the respective Details Screen
sections of the particular reports.

Notes

• The Key Process Analytics Report does not display the results in a report
screen but in individual report panels; see “Using the individual report
panels” on page 112.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 99

Chapter 7 Using the common infrastructure of Central Reporting reports

• In the Central Audit Report, only ALV Grid Control and Report Results
(ALV Grid) are available.

100 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 8
Using the Summary Report

The Summary Report provides a summary of all documents processed through

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

8.1 Using the selection screen

You control all functions of the Summary Report using a common selection screen.

To start the Summary Report:

• Run the /n/OPT/VIM_SUMM transaction.

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 101

Chapter 8 Using the Summary Report

Figure 8-1: Summary Report selection screen

Selection field panel

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

102 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 8.2. Using the report screen

8.2 Using the report screen

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

Figure 8-2: Summary Report report screen

1
Header section

2
ALV grid control

3
Report results (ALV grid)

For a description of the elements that are common for all reports, see “Using the
report screen” on page 99.

8.2.1 Report results (ALV Grid)

The actual report results are displayed in the ALV Grid. The ALV comprises the
Invoice and Credit Memo section, according to your settings in the selection field
panel. Your administrator can configure groups and categories of the report results.
The baseline configuration provides the following groups and categories:

In process

• Non Approval Exception

• Approval

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 103

Chapter 8 Using the Summary Report

Pre Processed

• Pre Processed (OCR)

Processed

• Posted

Others

• Cancelled
• Deleted
• Confirmed Duplicate
• Obsolete
• Rescan Complete

8.2.2 Details screen

The Summary Report allows you to display details about the report results. To open
the Summary Report drill down list, double-click a cell in one of the Count
columns.

Tip: The selected line in the ALV Grid must contain data. Otherwise, the
Summary Report drill down list cannot be displayed.

104 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 9
Using the Central Audit Report

The Central Audit Report is a slimmed VIM Analytics (VAN). The main difference
to VAN is that the Central Audit Report serves as a single point of access in a
multiple backend scenario. Therefore, you must run the Central Audit Report in the
central system. The Central Audit Report lists documents from all systems, central
and satellite. By 2 clicks in the Central Audit Report's report screen, you can directly
access VAN on the respective satellite system. You do not have to log on to the
satellite system, when using trusted RFC connections.

Note: Ask your administrator whether trusted RFC connections are used. The
administrator can configure RFC connections, using the System Landscape
Directory (SLD).

The selection screen of the Central Audit Report contains the most important
selection fields of VAN. Additionally, it provides an additional selection field for the
systems of a multiple backend scenario.

Note: The Central Audit Report considers only documents that have a DP
document number.

9.1 Using the selection screen

You control all functions of the Central Audit Report using a common selection
screen.

To start the Central Audit Report:

• Run the /n/OPT/VIM_AUDIT transaction.

Alternatively, in OpenText VIM - Invoice Solution, navigate to SAP menu >
Reports > Central Reporting > Audit Report.
For a description of the elements that are common for all reports, see “Using the
selection screen” on page 97.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 105

Chapter 9 Using the Central Audit Report

Selection field panel

The selection fields in the Central Audit Report mainly repeat the most
important selection fields that are displayed in VAN. See Selection field panel
on page 37 for details.
The following selection fields are specific for the Central Audit Report:
Only Inprocess Documents
Select this check box to consider only DP documents whose workflow status
is In Process.

106 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 9.2. Using the report screen

9.2 Using the report screen

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

The report screen comprises the following sections:

• “ALV Grid control” on page 107

• “Report results (ALV Grid)” on page 108

9.2.1 ALV Grid control

The ALV Grid control of the Central Audit Report displays the following buttons.

Workflow Log
Select a document's line in the ALV Grid and click this button to display
detailed workflow information.
Image
Select a document's line in the ALV Grid and click this button to display the
scanned image of the original invoice in the Image Viewer installed and
configured on your desktop.
Dashboard
Select a document's line in the ALV Grid and click this button to access the
OpenText unified dashboard.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 107

Chapter 9 Using the Central Audit Report

Link to VAN
Select a document's line in the ALV Grid and click Link to VAN to open VAN
for the selected document, see “VIM Analytics: Detailed Invoice Report“
on page 33.
In a multiple backend scenario, VAN is opened directly on the system where the
document resides. You do not have to log on to the system, when using trusted
RFC connections.
Note: Ask your administrator whether trusted RFC connections are used.
The administrator can configure RFC connections, using the System
Landscape Directory (SLD).

9.2.2 Report results (ALV Grid)

The ALV Grid of the Central Audit Report is very similar to the Result List of VAN;
see “VIM Analytics: Detailed Invoice Report“ on page 33. The ALV Grid of the
Central Audit Report provides the following specific columns:

Logical System
The Logical System column at the very left of the ALV Grid indicates on which
system in the multiple backend system the document resides.
MultiAgent
The column MultiAgent might be marked for a document. This indicates that
more than one agent is assigned to the document. In this case, click the link in
the Current Role column to display the IDs and names of the assigned agents.

108 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 10
Using the Key Process Analytics Report

The Key Process Analytics Report reports about a variety of key figures regarding
the OpenText VIM for SAP process: It shows the accumulated amounts of all
documents in the DP workflow, in parked state and in posted state.

The individual report panels of the Key Process Analytics Report highlight the
following aspects:

Total Liability
This panel provides an overview of the total liability.
Amounts that are exceeding certain thresholds are highlighted in orange or red.
Your administrator can customize these thresholds.
Processed / In Process Documents
This panel provides an overview of OpenText VIM for SAP invoices, processed
and currently in process.
If the number or percentage of processed or in process documents exceeds
certain thresholds, the respective cells are highlighted in orange or red. Your
administrator can customize these thresholds.
Channel Analysis
This panel provides an overview of OpenText VIM for SAP invoices per
channel.
First Pass
This panel provides an overview of first pass OpenText VIM for SAP invoices,
that means OpenText VIM for SAP invoices that could be posted without any
exceptions.
If the number or percentage of first pass OpenText VIM for SAP invoices goes
below certain thresholds, the respective cells are highlighted in orange or red.
Your administrator can customize these thresholds.
Top Exceptions by Count
This panel provides an overview of the most frequent exceptions during the
OpenText VIM for SAP process. You can select the number of exceptions to be
listed.
Top Vendors by Amount
This panel provides an overview of the vendors with the highest purchase
amount, based on the gross amount of all OpenText VIM for SAP invoices. You
can select the number of vendors to be listed.

The Key Process Analytics Report supports the conversion of amount fields to
different currencies.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 109

Chapter 10 Using the Key Process Analytics Report

You can display report data as graphics, using standard SAP ALV grid functionality.
You can choose between different chart types, for example bar chart or pie chart.

Utility report /OPT/VIM_BL_SINGLE_SYS_ACT_UTL

To display exception data correctly in the Key Process Analytics Report, valid data
needs to be maintained in tables /OPT/VT_ROLESDET and /OPT/VT_EXCDET. This can be
achieved by running utility report /OPT/VIM_BL_SINGLE_SYS_ACT_UTL (transaction /
OPT/VIM_SYS_ACTIV).

10.1 Using the Frame Selection panel

Unlike the other reports in Central Reporting, the Key Process Analytics Report does
not provide a separate selection screen. The Frame Selection panel is integrated into
the main screen that also shows the individual report panels.

To start the Key Process Analytics Report:

• Run the /n/OPT/VIM_KPA1 transaction.

Alternatively, in OpenText VIM - Invoice Solution, navigate to SAP menu >
Reports > Central Reporting > Key Process Analytics Report.

110 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 10.1. Using the Frame Selection panel

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

Application toolbar
You can perform the following action:

Refresh.
Alternatively, press the RETURN key.
The Key Process Analytics Report creates and displays a report, using
the current settings in the Frame Selection panel. The report results
are displayed in the individual report panels.
Note: A new selection from the database is triggered only if you
change the selection criteria.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 111

Chapter 10 Using the Key Process Analytics Report

Frame Selection panel

The following selection fields are specific for the Key Process Analytics
Report:
Date Range
Enter the date range you want to run the report for. The date refers to
the Created at date of the OpenText VIM for SAP document. This
corresponds to the P date in Currency Translation Date; see Currency
Translation Date on page 98.
Package Size
You can configure the package size. It is used for fetching the data from
the database. Default value is 10,000.
The system fetches this number of records from the database, it
processes the records, and again fetches the same number of records
until all records that are met by the selection criteria are fetched.
How to use the package size parameter

• If the report is too slow, you can try to increase the parameter, for
example to 20,000.
• If the report is terminating, you can try to decrease the parameter,
for example to 5,000.

Exclude DPs outside VIM

To exclude DP documents that are posted outside of OpenText VIM for
SAP, select this check box. To include these documents, clear the check
box.

Individual report panels

See “Using the individual report panels” on page 112.

10.2 Using the individual report panels

After you finished your selection in the Frame Selection panel, click or press
RETURN to run the report.

The individual report panels in the main screen get populated with data.

112 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 10.2. Using the individual report panels

Figure 10-1: Key Process Analytics Report results

The following sections describe the individual report panels.

All report panels are displayed using the standard SAP ALV list viewer with the
respective ALV grid control. The ALV grid control provides various standard SAP
buttons for the ALV list viewer. For example, you can change the layout of the
report, move, remove or add columns.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 113

Chapter 10 Using the Key Process Analytics Report

10.2.1 Total Liability

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

The Total Liability panel comprises the following columns:

Category
The following states of documents are listed:

• Blocked Documents
• Parked Documents
• Pre-Process Documents (all documents that are still in process and did not
yet result in an SAP invoice)

Total Amount
Total Amount of all documents
Crcy
Reporting Currency, as selected in the Frame Selection panel

Details To show details for a specific cell in the Total Amount column, double-click the cell
in the ALV grid. The Document List opens, showing detailed information on the
OpenText VIM for SAP documents of the Category referred to in the selected cell.

Tips

• The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.
• For the columns Category and Crcy, no document lists are available.

Threshold func- In the Total Liability panel, the threshold functionality is available. Your
tionality administrator can define threshold values for an attention status and a critical status.
If the attention value is exceeded in a cell, the cell is highlighted in orange. If the
critical value is exceeded in a cell, the cell is highlighted in red.

10.2.2 Processed / In Process Documents

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

The Processed / In Process Documents panel provides an overview of OpenText

VIM for SAP invoices, processed and currently in process. It comprises the following
columns:

Invoice Type

• PO Invoices
• NPO Invoices
• Unclassified

114 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 10.2. Using the individual report panels

An unclassified invoice is not yet classified as a PO or NPO invoice.

Total # Processed
Total number of invoices that are already processed, that means with status
Posted.

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

PO Based
Indicator if the invoice is PO based or not. Possible values: Y for Yes, N for No, U
for Unclassified.
This column can be useful if you export the data, for example to Microsoft Excel.
Processed (%)
Percentage of invoices that are already processed, that means with status
Posted.

In Process (%)
Percentage of invoices that are currently in process

Details To show details for a specific cell, double-click the cell in the ALV grid. The
Document List opens, showing detailed information on the OpenText VIM for SAP
documents according to Invoice Type and Document Status referred to in the
selected cell.

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

The ALV grid control in the Document List contains the following button:

Image
You can display the scanned image of the original invoice of a OpenText VIM
for SAP document in the Image Viewer installed and configured on your
desktop: Select a line in the table and click Image.

Threshold func- In the Processed / In Process Documents panel, the threshold functionality is
tionality available. Your administrator can define threshold values for an attention status and
a critical status. If the attention value is exceeded in a cell, the cell is highlighted in
orange. If the critical value is exceeded in a cell, the cell is highlighted in red.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 115

Chapter 10 Using the Key Process Analytics Report

10.2.3 Channel Analysis

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

The Channel Analysis panel provides an overview of OpenText VIM for SAP
invoices by Channel ID. The channel indicates the input mode of invoices into
OpenText VIM for SAP, for example OCR. The Channel Analysis panel comprises
the following columns:

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

Channel ID
Channel ID, for example IDOC for invoices imported using Electronic Data
Interchange
Channel Text
Description of the channel
Total # Unclassified
Total number of unclassified invoices (not yet classified as PO or NPO invoices)

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

PO Invoices (%)
Percentage of PO invoices
NPO Invoices (%)
Percentage of NPO invoices
Unclassified (%)
Percentage of unclassified invoices

Details To show details for a specific cell, double-click the cell in the ALV grid. The
Document List opens, showing detailed information on the OpenText VIM for SAP
documents, according to Invoice Type and Channel ID referred to in the selected
cell.

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

116 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 10.2. Using the individual report panels

10.2.4 First Pass

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

The First Pass panel provides an overview of first pass OpenText VIM for SAP
invoices, that means OpenText VIM for SAP invoices that could be posted without
any exceptions. The following types of exceptions can happen:

• DP process types, for example 101 - Invalid PO Number (PO)

• Parking reasons, for example 151 - Vendor Audit Required
• Blocking reasons, for example Price Discrepancy

Not every DP process type, parking reason and blocking reason is automatically
seen as an exception. Which DP process type, which parking reason and which
blocking reason is actually treated as an exception, is defined in the configuration of
exceptions for Central Reporting. For more information, see Section 30.5 “Activating
Central Reporting Baseline and maintaining reporting tables” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD), especially “To maintain exceptions for Central Reporting” and “To map
exceptions for several back end systems”.

The First Pass panel comprises the following columns:

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

First Pass (%)

Percentage of First Pass documents

Total # First Pass

Total number of First Pass documents

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

PO Based
Indicator if the invoice is PO based or not. Possible values: Y for Yes, N for No.
This column can be useful if you export the data, for example to Microsoft Excel.

Details To show details for a specific cell, double-click the cell in the ALV grid. The
Document List opens, showing detailed information on the OpenText VIM for SAP
documents, according to the Invoice Type referred to in the selected cell.

Tips

• The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.
• There is no Document List available for the column Total # Documents.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 117

Chapter 10 Using the Key Process Analytics Report

Threshold func- In the First Pass panel, the threshold functionality is available. Your administrator
tionality can define threshold values for an attention status and a critical status. If the value in
a cell falls below the attention value, the cell is highlighted in orange. If the value in
a cell falls below the critical value, the cell is highlighted in red.

10.2.5 Top Exceptions by Count

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

The Top Exceptions by Count panel provides an overview of the most frequent
exceptions during the OpenText VIM for SAP process.

You can select the number of exceptions to be listed in the panel. Therefore, the ALV
grid control of the Top Exceptions by Count panel provides the Top button:

Top
Click this button to select the number of exceptions that are listed. Possible
values: 3, 5, 10, or 20

The Top Exceptions by Count panel comprises the following columns:

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

Exception ID
ID of the exception in the system
Exception Text
Description of the Exception

Details To show details for a specific line, double-click the line in the ALV grid. The Work
Items with Exception List opens, showing detailed information on the work items,
according to the Exception ID referred to in the selected line.

10.2.6 Top Vendors by Amount

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

The Top Vendors by Amount panel provides an overview of the vendors with the
highest purchase amount, based on the gross amount of all OpenText VIM for SAP
invoices.

You can select the number of vendors to be listed in the panel. Therefore, the ALV
grid control of the Top Vendors by Amount panel provides the Top button.

Top
Click this button to select the number of exceptions that are listed. Possible
values: 3, 5, 10, or 20

The Top Vendors by Amount panel comprises the following columns:

118 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 10.2. Using the individual report panels

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

Name 1
Vendor name
Total Amount
Total amount for the vendor
Currency
Reporting Currency, as selected in the Frame Selection panel

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

Name 2
Only useful if this field is maintained for the vendors in the system

Details To show details for a specific line, double-click the line in the ALV grid. The
Document List opens, showing detailed information on the OpenText VIM for SAP
documents, according to the Logical System and the Vendor referred to in the
selected line.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 119

Chapter 11
Using the Exception Analysis Report

The Exception Analysis Report reports all work items with exceptions, grouped by
exception, company code or vendor. The Exception Analysis Report provides the
following features:

• Finds and tracks exceptions with the highest impact on your business.
• Monitors how often exceptions occur.
• Finds companies or vendors who cause the highest number of exceptions.
• Indicates the invoice amount that is affected by work items with exceptions.

11.1 Using the selection screen

You control all functions of the Exception Analysis Report using a common selection
screen.

To start the Exception Analysis Report:

• Run the /n/OPT/VIM_EXCP1 transaction.

Alternatively, in OpenText VIM - Invoice Solution, navigate to SAP menu >
Reports > Central Reporting > Exception Analysis Report.
For a description of the elements that are common for all reports, see “Using the
selection screen” on page 97.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 121

Chapter 11 Using the Exception Analysis Report

Selection field panel

The selection field panel comprises the following sections:
Doc Characteristics
Invoice types
Click PO Invoices, Non-PO Invoices, or All Invoices (All Invoices
includes PO, Non PO and unclassified invoices).
Note: Unclassified invoices are not yet classified as PO or NPO
invoices.
IM Document Type
Enter the DP document type, depending on the logical system.
Vendor
Enter the vendor number, depending on the logical system.

122 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 11.2. Using the report screen

Include In Process Items

By default, the Exception Analysis Report only considers finished
documents, with status Posted. Select this check box to include also
documents that are still in process.
Note: This setting only considers documents in the current date
range, not in the comparison period.
Include Deleted/Obsolete/Cancelled/Confirmed Duplicate/Rescan
Complete
To include finished documents of any of the mentioned states, select this
check box.
Note: This setting considers documents in the current date range
and in the comparison period.

Time Characteristics
Date Range
Enter the date range you want to run the report for. The date refers to
the Created at date of the document.
Comparison Period
Click Previous Week, Previous Month, Previous Quarter or Previous
Year. The date refers to the Created at date of the document.

Grouping
Select the parameter to group the report by. Click Exception, Vendor or
Company Code.

11.2 Using the report screen

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 123

Chapter 11 Using the Exception Analysis Report

For a description of the elements that are common for all reports, see “Using the
report screen” on page 99.

11.2.1 ALV Grid control

The following button is specific for the Exception Analysis Report:

Group By
Click this button to change the grouping of the report. This has the same effect
as the Grouping settings in the selection screen. Click Exception, Vendor or
Company Code.

11.2.2 Report results (ALV Grid)

The actual report results are displayed in the ALV Grid. The Grouping setting
determines the layout of the columns.

If the report is grouped by Vendor or Company Code, the logical systems are
displayed at the very left of the table, followed by the Vendor or Company Code
information. If the report is grouped by Exception, the Exception information is
displayed at the very left of the table.

Next to the right, the following columns are displayed, first for the selected period,
next for the comparison period, indicated by Previous Period or Prev. in the column
title:

Notes

• You can change the layout of the report results; for example, you can shift,
remove or add columns. So, your actual table might differ from the
following description.
• The following list only covers columns whose meaning is not obvious.

124 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 11.2. Using the report screen

Total Amount
This value is recalculated from the original currency to the reporting currency.
Avg. Time
Average time of work on the work item
Avg. Wait Time
Average time elapsed on one OpenText VIM for SAP document before all the
work items related to this OpenText VIM for SAP document have been touched
by a user for the first time.
One OpenText VIM for SAP document can comprise several work items. Every
work item has a wait time before it is touched for the first time. The report sums
up these wait times and averages them.
Note: The columns containing time data display the time in <xx>d <xx>h
<xx>m <xx>s format. You can add corresponding columns that display the
time in seconds as a numeric value. This is useful, for example, if you want
to export data to an Excel spreadsheet.
Avg. # of Touches
Average number of how often the work item has been touched
Avg. # of Referrals
Average number of how often the work item has been referred to an agent

11.2.3 Details screen

To show details for a specific line, double-click the line in the ALV Grid. The Work
Items with Exception List opens, showing detailed information on every work item
that appears in the # Work Items with Exceptions column in the selected line.

Tip: The selected line in the ALV Grid must contain data. Otherwise, the Work
Items with Exception List cannot be displayed.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 125

Chapter 12

Using the Productivity Report

The Productivity Report reports about the productivity of users/roles and the
activities of users/roles. The Productivity Report comprises the following features:

• Provides an overview of the processing times (total and average) and wait times
(average) per user/role.

• Enables the comparison of productivity of a freely selectable period to a

comparison period.

• Provides a snapshot of reserved and in process items per user/role.

• Enables the analysis of the average number of touches (per invoice) of users/
roles.

• Enables the analysis of the average number of referrals (per invoice) of users/
roles.
• Allows displaying a detailed list of:

– documents processed by a single user/role

– currently reserved items of a single user/role

– currently processed items of a single user/role

Note: The time stamps that are used for the Productivity Report are based on
the time information in the SAP work item tables and are not directly related to
the time stamps in the OpenText VIM for SAP process history.

12.1 Using the selection screen

You control all functions of the Productivity Report using a common selection
screen.

To start the Productivity Report:

• Run the /n/OPT/VIM_PROD1 transaction.

Alternatively, in OpenText VIM - Invoice Solution, navigate to SAP menu >
Reports > Central Reporting > Productivity Report.
For a description of the elements that are common for all reports, see “Using the
selection screen” on page 97.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 127

Chapter 12 Using the Productivity Report

Selection field panel

The following selection fields are specific for the Productivity Report:

Agent Info
Agent ID
Enter the IDs of the agents (users) you want to run the report for.
Role ID
Enter the IDs of the roles you want to run the report for.
Org Object
Enter the Org object you want to run the report for. The Org object
refers to the organizational objects maintained in the standard SAP
Organizational Management. Using the icon, you can restrict the
value range to Organizational unit, Position, or Organizational units
and Positions (All).

128 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 12.2. Using the report screen

Note: To use this selection criterion, the organizational structure

must be maintained within SAP Organizational Management on
the different logical (back end) systems.

Doc Characteristics
Click PO Invoices, Non-PO Invoices, or All Invoices (All Invoices includes
PO, Non PO and unclassified invoices).
Note: Unclassified invoices are not yet classified as PO or NPO
invoices.

Time Characteristics
Date Range
Enter the date range you want to run the report for. The date refers to
the Created at date of work items related to the OpenText VIM for SAP
document, not the execution/completion date.
Comparison Period
Click Previous Week, Previous Month, Previous Quarter or Previous
Year. The date refers to the Created at date of work items related to the
OpenText VIM for SAP document.

Grouping
Select the parameter to group the report by. Click Agent or Role.

12.2 Using the report screen

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

For a description of the elements that are common for all reports, see “Using the
report screen” on page 99.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 129

Chapter 12 Using the Productivity Report

12.2.1 ALV Grid control

The following button is specific for the Productivity Report:

Group By
Click this button to change the grouping of the report. This has the same effect
as the Grouping settings in the selection screen. Click Agent or Role.

12.2.2 Report results (ALV Grid)

The actual report results are displayed in the ALV Grid. The Grouping setting
determines the layout of the columns. If the report is grouped by Agent, the logical
systems are displayed at the very left of the table, followed by the Agent
information. If the report is grouped by Role, the Role information is displayed at
the very left of the table.

Note: The Validator role (ID 13) is not covered by the Productivity Report
although it is configured in the baseline. Data for this role is not shown in the
report results.

Report period Next to the right, the following columns are displayed for the report period:
results
Note: You can change the layout of the report results; for example, you can
shift, remove or add columns. So, your actual table might differ from the
following description.

Total # Processed
Number of OpenText VIM for SAP documents that have been worked on in the
report period. Work is not necessarily completed; that means, the invoice may
be already posted or not.
Reserved
Number of OpenText VIM for SAP documents that are reserved at the moment;
that means, at least one work item belonging to the OpenText VIM for SAP
document is reserved. The moment of time is determined by the last update of
the data.
The value in the Reserved column is a subset of the value in the In Process
column.
In Process
Number of OpenText VIM for SAP documents that have at least one work item
in the following states at the moment:

• waiting to be worked on in an inbox of the SAP Business Workplace, not yet

touched by any user
• reserved by a user
• worked on by a user

The moment of time is determined by the last update of the data.

130 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 12.2. Using the report screen

Total Time Spent

Time the agent/role spent working on OpenText VIM for SAP documents
Avg. Time
Average time the agent/role spent working on one OpenText VIM for SAP
document
Avg. Wait Time
Average time elapsed on one OpenText VIM for SAP document before all the
work items related to this OpenText VIM for SAP document have been touched
by a user for the first time.
One OpenText VIM for SAP document can comprise several work items. Every
work item has a wait time before it is touched for the first time. The report sums
up these wait times and averages them.
Note: The columns containing time data display the time in <xx>h <xx>m
<xx>s format. You can add corresponding columns that display the time in
seconds as a numeric value. This is useful, for example, if you want to
export data to an Excel spreadsheet.
Avg. # of Touches
Average number of how often a OpenText VIM for SAP document has been
touched
Avg. # of Referrals
Average number of how often a OpenText VIM for SAP document has been
referred to another agent

Comparison To the right of the report period columns, the following columns are displayed for
period results the comparison period (indicated by Prev. in the column title):

Prev. Total # Processed

Number of OpenText VIM for SAP documents that have been worked on in the
comparison period
Prev. Total Time Spent
Time the agent/role spent working on OpenText VIM for SAP documents
Prev. Avg. Time
Average time the agent/role spent working on one OpenText VIM for SAP
document
Prev. Avg. Wait Time
Average time elapsed on one OpenText VIM for SAP document before all the
work items related to this OpenText VIM for SAP document have been touched
by a user for the first time.
One OpenText VIM for SAP document can comprise several work items. Every
work item has a wait time before it is touched for the first time. The report sums
up these wait times and averages them.
Note: The columns containing time data display the time in <xx>h <xx>m
<xx>s format. You can add corresponding columns that display the time in

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 131

Chapter 12 Using the Productivity Report

seconds as a numeric value. This is useful, for example, if you want to

export data to an Excel spreadsheet.
Prev. Avg. # of Touches
Average number of how often a OpenText VIM for SAP document has been
touched
Prev. Avg. # of Ref.
Average number of how often a OpenText VIM for SAP document has been
referred to another agent

12.2.3 Details screen

To show details for a specific cell, double-click the cell in the ALV Grid. The
Document List opens, showing detailed information on the OpenText VIM for SAP
documents referred to in the selected cell.

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

The Document List displays data for an Agent in a Logical System or a Role,
depending on the grouping of the report. Displaying the Document List for a cell is
possible in all columns, except the columns containing time data. The layout of the
Document List depends on the selected column.

132 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 13
Using the Aging Report

The Aging Report reports about the aging of documents and work items in the
current system. The Aging Report comprises the following features:

• Provides an overview of the processing times of documents that have not been
posted without error.
• Provides a snapshot of documents that have not been posted and are still work in
process.
• Provides a snapshot of work items that are still work in process.
• Allows displaying a detailed list of:

– documents still in process, grouped by document type.

– work items still in process, grouped by role.

13.1 Using the selection screen

You control all functions of the Aging Report using a common selection screen.

To start the Aging Report:

• Run the /n/OPT/VIM_AGING transaction.

Alternatively, in OpenText VIM - Invoice Solution, navigate to SAP menu >
Reports > Central Reporting > Aging Report.
For a description of the elements that are common for all reports, see “Using the
selection screen” on page 97.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 133

Chapter 13 Using the Aging Report

Selection field panel

The following selection fields are specific for the Aging Report:

Org Related
Channel
Enter the channel. The channel indicates the input mode of invoices into
OpenText VIM for SAP, for example OCR.

Doc Characteristics
Click PO Invoices, Non-PO Invoices, or All Invoices (All Invoices includes
PO, Non PO and unclassified invoices).

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

invoices.

Vendor
Enter the vendor number, depending on the logical system.

134 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 13.2. Using the report screen

Role ID
Enter the IDs of the roles you want to run the report for.

Grouping
Select the parameter to group the report by: Click Document Type or Role.

Report Options
Buckets (in Days)
The report results are displayed in 4 so-called buckets, each of them
representing a time range of how long documents or work items have
stayed in the system. Each bucket corresponds with a table column in
the report screen. By default, the following buckets are defined:

• 0 to 30 Days
• 31 to 60 days
• 61 to 90 days
• > 90 days

Using the Buckets (in Days) fields, you can change the limits for the
buckets. Replace the default values 30 / 60 / 90, according to your needs.
For example, the screenshot in “Using the report screen” on page 135
shows buckets that are defined with 50 / 75 / 100

13.2 Using the report screen

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 135

Chapter 13 Using the Aging Report

For a description of the elements that are common for all reports, see “Using the
report screen” on page 99.

13.2.1 ALV Grid control

The following button is specific for the Aging Report:

Group By
Click this button to change the grouping of the report. This has the same effect
as the Grouping settings in the selection screen. Click Doc Type or Role.

136 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 13.2. Using the report screen

13.2.2 Report results (ALV Grid)

The actual report results are displayed in the ALV Grid. The Grouping setting
determines the layout of the columns. If the report is grouped by Doc Type, the
logical systems are displayed at the very left of the table, followed by the Doc Type
information. If the report is grouped by Role, the Role information is displayed at
the very left of the table.

With Doc Type grouping, the data cells contain information about OpenText VIM
for SAP documents.

With Role grouping, the data cells contain information about work items.

Report results Next to the right, the following columns are displayed:

Note: You can change the layout of the report results; for example, you can
shift, remove or add columns. So, your actual table might differ from the
following description.

Description
Description of the document type if you have grouped by Doc Type.
Description of the role if you have grouped by Role.

0 to 30 Days
This is the default setting. You can change the setting, using the Buckets (in
Days) parameter in the selection field panel. See Buckets (in Days) on page 135.
Number of documents that are work in process and have been in the system for
0 to 30 days.

31 to 60 Days
This is the default setting. You can change the setting, using the Buckets (in
Days) parameter in the selection field panel. See Buckets (in Days) on page 135.
Number of documents that are work in process and have been in the system for
31 to 60 days.

61 to 90 Days
This is the default setting. You can change the setting, using the Buckets (in
Days) parameter in the selection field panel. See Buckets (in Days) on page 135.
Number of documents that are work in process and have been in the system for
61 to 90 days.

>90 Days
This is the default setting. You can change the setting, using the Buckets (in
Days) parameter in the selection field panel. See Buckets (in Days) on page 135.
Number of documents that are work in process and have been in the system for
more than 90 days.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 137

Chapter 13 Using the Aging Report

13.2.3 Details screen

To show details for a specific cell, double-click the cell in the ALV Grid.

With Doc Type grouping, the Document List opens, showing detailed information
on the OpenText VIM for SAP documents referred to in the selected cell. The
Document List shows documents with a specific Logical System and Document
Type.

With Role grouping, the Work Items with Exception List opens, showing detailed
information on the work items referred to in the selected cell. The Work Items with
Exception List shows work items with a specific Role.

Tips

• The selected cell in the ALV Grid must contain data. Otherwise, the
Document List or Work Items with Exception List cannot be displayed.
• Displaying the Document List or Work Items with Exception List for a cell
is possible in all columns with numeric values, except the cells containing
the Total.
• The layout of the Document List or Work Items with Exception List
depends on the selected column.

138 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 14
Using the Intermediate Data Report

The Intermediate Data Report provides the option to view the intermediate
processing data for Central reports, before aggregation of data. Intermediate data
can be displayed for the following reports:

• Aging Report
• Summary Report
• Central Audit Report
• Exception Analysis Report
• Key Process Analytics Report
• Productivity Report

14.1 Using the selection screen

You control all functions of the Intermediate Data Report using a common selection
screen.

To start the Intermediate Data Report:

• Run the /n/OPT/VIM_INTERM_DATA transaction.

Alternatively, run the /OPT/SPRO transaction and navigate to SAP menu >
Reports > Display Central Report Intermediate Data > Intermediate Data

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 139

Chapter 14 Using the Intermediate Data Report

Central Report
Select the report for which you want to view intermediate data.
Common Data
This options in this section apply to all available reports. For a description of the
elements that are common for all reports, see “Using the selection screen”
on page 97.
Report-specific data
The section at the bottom of the screen contains options specific to the central
report you selected.

14.2 Using the report screen

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

The reports show only intermediate data with fields particular to each individual
report from the selection.

140 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 15
Using Capture Analytics

Capture Analytics reports the key figures of the extraction process in Inbound phase
based on the feedback results.

Capture Analytics provides the following key figures and information:

• Provides the inbound information like channel, handle ID, classification ID,
document layout ID.
• Provides the process information like Document ID, document type, start date,
and so on.
• Provides the business data of the invoice document like Company Code, Vendor,
SAP document number.
• Provides Capture generic key figures, for example how many header/item fields
are extracted, how many are correct, the rate of correct extraction of all header/
item fields.
• Provides Capture invoice-specific key figures, for example how many times a
certain field is extracted, how many times it is correctly extracted and the rate in
% of correct extraction of the field.
• Provides the Details Pane where some additional information of a process is
provided: the image, the line items, the history and comments.
• A selection screen is provided for Capture Analytics. Selection fields like Doc ID,
Channel ID, Start Date, and business data fields allows you to select a subset of
documents for your needs. The selection field Start Date allows to restrict the
volume of documents, which can improve the performance of the report.

In order to add, remove, or change some fields in Capture Analytics, see Section 8
“Workplace Configuration” in OpenText Vendor Invoice Management for SAP Solutions
- Configuration Guide for Foundation (VIMZ-CGF).

The work object type PS03_DEA_INV is delivered in the standard BC sets.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 141

Chapter 15 Using Capture Analytics

15.1 Calling Capture Analytics and authorization

check
Capture Analytics is integrated into VIM Central Workplace.

To start Capture Analytics:

1. Open VIM Central Workplace with the /n/OTX/PF03_WP transaction.

2. Select the work center Supplier Invoices.

3. Go to the node Capture Analytics.

4. Double-click the sub-node Validation or Process End to display all processes

associated with Capture and the corresponding feedback mechanism.

In order to be able to work with the work center Supplier Invoices, users must be
authorized for the project ID of this work center. Additionally, only documents of
authorized company code will be displayed for them.

Authorization
Description Fields
Object
J_6NPF_PRJ
The authorized Project ID
J_6NPF_PRJ Open Text Business Center - Project ID
ACTVT '03'
Display
BUKRS
The authorized Company
OpenText VIM for SAP: Basic processing
J_6NIM_BC1 Code
authority by company code
ACTVT '03'
Display

Note: The authorization check for company codes is performed when Invoice
Solution authorization checks are globally activated with the Z constant 009 /
AUTH_CHECK_ACTIVE. For more details, see Section 6 “Authorization checks” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).

Using standard ALV functions, you can change the layout, do summarize, sorting,
and so on. You can also export the list to an external file.

Using the Show list, you can restrict the number of entries to be displayed.

142 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 15.2. Using the selection screen

15.2 Using the selection screen

To hide or to show the selection screen, click the button Hide Selection Pane or
Show Selection Pane, which is provided in the menu bar.

The selection fields comprise process fields like Doc ID, Document Type, Channel
ID, Start date, Document Layout ID, and business data like Company Code, Vendor,
PO, document date, and so on.

The following buttons are available in the selection screen:

Apply
Click this button after you enter some selection fields.
Edit
Click this button to edit the applied selection fields.
Reset
Click this button to erase all selection fields.

15.3 Using the details pane

To hide or to show the details pane, click the button Hide Details Pane or Show
Details Pane, which is provided in the menu bar.

In the details pane, the following tabs are available, which display the Image, the
Line items, the History, the Comments, and the Comparison for each entry in the
ALV grid.

On the Comparison tab, you see the comparison either between extracted values
and validated values (Validation - Extraction), or between extraction values and
values in finished document (Process Finished - Extraction).

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 143

Chapter 16

Using Capture Dashboard

Capture Dashboard, along with Capture Analytics allows to evaluate the extraction
results, accuracy, and the effectiveness of the learning process of OpenText™
Capture for SAP® Solutions and OpenText™ Core Capture for SAP Solutions.

Capture Dashboard is integrated in VIM Central Workplace - Work Center Supplier

Invoices. By default, the Capture Dashboard is not visible. For more information
about how to activate it, see Section 7.2.4 “Capture Dashboard” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).

16.1 Calling Capture Dashboard

Capture Dashboard is integrated in VIM Central Workplace.

To start Capture Dashboard:

1. Open VIM Central Workplace with the /n/OTX/PF03_WP transaction.

2. Select the work center Supplier Invoices.

3. Double-click the node Capture Dashboard.

The following parts are provided in Capture Dashboard:

• Capture Dashboard – For details, see “Using the Capture Dashboard”

on page 146.

• Selection screen – “Using the selection screen” on page 151.

• Details pane – “Using the details pane” on page 152.

The following modes are available:

• Normal Mode – The Capture Dashboard is executed without comparison. This

mode allows the evaluation in the selected time-period.

• Comparison Mode – The Capture Dashboard is executed with comparison. This

mode allows the comparison of the KPIs of 2 selected time-periods.

In the Comparison Mode some KPIs are colored based on the comparison results.
The coloring of compared KPIs is defined as following:

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 145

Chapter 16 Using Capture Dashboard

KPIs Color Description

Green/Red Document Recognition Rate. The field
is green if the value is greater or equal
DOC_CORRECT_RATE
to the value in the previous time
period. Otherwise it is red.
Green/Red Rate of correctly extracted Invoice
Header fields. The field will be green if
DOC_IH_REQ_RATE the value is greater or equal to the
value in the previous time period.
Otherwise it is red.
Green/Red Rate of correctly extracted Invoice Item
fields. The field is green if the value is
DOC_TI_REQ_RATE greater or equal to the value in the
previous time period. Otherwise it is
red.
Green/Red Rate of documents which went
through validation step. The field is
DOC_VALIDAT_RATE green if the value is smaller or equal to
the value in the previous time period.
Otherwise it is red.
Green/Red Rate of documents which were
rejected. The field is green if the value
DOC_REJECT_RATE is smaller or equal to the value in the
previous time period. Otherwise it is
red.
Orange Total number of pages. It is colored for
TOTAL_PAGES
the current period.
AVR_NO_PAGE Orange Average number of pages. It is colored
for the current period.
Orange Maximal number of pages. It is colored
MAX_NO_PAGE
for the current period.

16.2 Using the Capture Dashboard

The Capture Dashboard provides 3 groups of key figures per capture profile:

Group 1
KPIs indicating the extraction counts and rate of header fields or line item fields
or both per capture profile. These KPI are calculated based on data from solution
tables.
For each category the following numbers are provided with postfix:

• COUNT (xxx = COUNT): Number of extracted fields of the given category.

• OK (xxx= OK): Number of correctly extracted field of the given category.
• RATE (xxx = RATE): Rate of the correctly extracted fields of the given
category. It is calculated as (# of OK/# of COUNT) *100.

146 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 16.2. Using the Capture Dashboard

All categories provided in Group 1 are listed in the following table:

Category Name Description

All fields All fields (header or items),
DOC_A_ALL_XXX configured as required or optional to
be extracted.
Required fields All fields (header or items),
DOC_A_REQ_XXX configured as required to be
extracted.
Optional fields All fields (header or items),
DOC_A_OPT_XXX configured as optional to be
extracted.
Header fields Header fields, configured as required
DOC_H_ALL_XXX
or optional to be extracted.
Required header Header fields, configured as required
DOC_H_REQ_XXX
fields to be extracted.
DOC_H_OPT_XXX Optional header Header fields, configured as optional
fields to be extracted.
Invoice Header Invoice Header fields including string
DOC_IH_ALL_XXX fields lists like POs or DNs, configured as
required or optional to be extracted.
Required Invoice Invoice Header fields including string
DOC_IH_REQ_XXX Header fields lists like POs or DNs, configured as
required to be extracted.
Optional Invoice Invoice Header fields including string
DOC_IH_OPT_XXX Header fields lists like POs or DNs, configured as
optional to be extracted.
Item Table fields Table items fields, configured as
DOC_TI_ALL_XXX
required or optional to be extracted.
Required Item Table items fields, configured as
DOC_TI_REQ_XXX
Table fields required to be extracted.
Optional Item Table items fields, configured as
DOC_TI_OPT_XXX
Table fields optional to be extracted.
Table 1 fields Tax Table items fields, configured as
DOC_T1_ALL_XXX
required or optional to be extracted.
Required Table 1 Tax Table items fields, configured as
DOC_T1_REQ_XXX
fields required to be extracted.
Optional Table 1 Tax Table items fields, configured as
DOC_T1_OPT_XXX
fields optional to be extracted.
Number of Number of completed inbound
recognized documents, for that a solution process
NO_DOC_CORRECT documents started. Furthermore, all required
header fields and required item fields
are extracted correctly.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 147

Chapter 16 Using Capture Dashboard

Category Name Description

Document Rate of documents for that all
Recognition rate required header fields and required
DOC_CORRECT_RATE item fields are extracted correctly. It is
calculated as (NO_DOC_CORRECT /
NO_ENTRIES)* 100.
Technical, internal Number of documents from solution
number tables that are considered in the
NO_ENTRIES
calculating all Capture Dashboard
KPIs of group 1.

Group 2
KPIs providing configuration aspects per capture profile. They provide numbers
of fields configured as required to be extracted, as optional to be extracted, or
sum of 2 numbers per capture profile. Those numbers can be changed with the
time depending on the configuration of the given capture profile. In the Capture
Dashboard the maximal value of them per capture profile in each selected
period is shown.
Available profile configuration numbers are listed in the following table:

Profile configuration
Name Description
numbers
Profile Configured Number of all header fields
Header Fields configured as required or optional
PRFL_H_ALL_CNT
to be extracted for the applied
Inbound Profile.
PRFL_H_REQ_CNT Profile Required Number of all header fields
Header Fields configured as required to be
extracted for the applied Inbound
Profile.
Profile Optional Number of all header fields
Header Fields configured as optional to be
PRFL_H_OPT_CNT
extracted for the applied Inbound
Profile.
Invoice Header Number of all header fields
Fields (including string lists like POs or
PRFL_IH_ALL_CNT DNs) configured as required or
optional to be extracted for the
applied Inbound Profile.
PRFL_IH_REQ_CNT Required Invoice Number of all header fields
Header Fields (including string lists like POs or
DNs) configured as required to be
extracted for the applied Inbound
Profile.

148 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 16.2. Using the Capture Dashboard

Profile configuration
Name Description
numbers
Optional Invoice Number of all header fields
Header Fields (including string lists like POs or
PRFL_IH_OPT_CNT DNs) configured as optional to be
extracted for the applied Inbound
Profile.
Profile Configured Number of all table item fields
Item Table Fields configured as required or optional
PRFL_TI_ALL_CNT
to be extracted for the applied
Inbound Profile.
Profile Required Number of all table item fields
Item Table Fields configured as required to be
PRFL_TI_REQ_CNT
extracted for the applied Inbound
Profile.
PRFL_TI_OPT_CNT Profile Optional Number of all table item fields
Item Table Fields configured as optional to be
extracted for the applied Inbound
Profile.
Profile Configured Number of all tax table item fields
Table 1 Fields configured as required or optional
PRFL_T1_ALL_CNT
to be extracted for the applied
Inbound Profile.
Profile Required Number of all tax table item fields
Table 1 Fields configured as required to be
PRFL_T1_REQ_CNT
extracted for the applied Inbound
Profile.
PRFL_T1_OPT_CNT Profile Optional Number of all tax table item fields
Table 1 Fields configured as optional to be
extracted for the applied Inbound
Profile.

Group 3
KPIs indicating the statistics of inbound processes per capture profiles. All
inbound statistics are calculated in each selected period. They are listed in the
following table:

Inbound KPIs Name Description

Number of processed Number of processed
documents inbound documents. They
NO_DOCS
include rejected documents
and trained documents.
Number of completed Number of documents
documents completed in inbound, for
NO_DOC_COMPLETED
which a solution process is
started.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 149

Chapter 16 Using Capture Dashboard

Inbound KPIs Name Description

Number of validated Number of processed
documents inbound documents that
NO_DOC_VALIDATED
went through validation
step.
Document Validation rate Rate of documents that went
through validation step. It is
DOC_VALIDAT_RATE calculated as
(NO_DOC_VALIDATED /
NO_DOCS)* 100.
Number of rejected Number of processed
NO_DOC_REJECTED documents inbound documents that
were rejected.
DOC_REJECT_RATE Document Rejection rate Rate of documents that were
rejected. It is calculated as
(NO_DOC_REJECTED /
NO_DOCS)* 100.
Number of trained Number of processed
NO_DOC_TRAINED documents inbound documents that
were used for training.
Document trained Rate Rate of documents that were
used for training. It is
DOC_TRAINED_RATE calculated as
(NO_DOC_TRAINED /
NO_DOCS)* 100.
Number of Layout IDs Number of unique Layout
NO_LAYOUT_ID
IDs.
Total Number of Processed Sum of pages of each
TOTAL_PAGES
Pages inbound document.
Average Number of Pages Average number of pages
AVR_NO_PAGE
per Document per capture profile.
Maximal Number of Pages Maximal number of pages
MAX_NO_PAGE
per Document per capture profile.
Minimal Number of Pages Minimal number of pages
MIN_NO_PAGE
per Document per capture profile.

Using standard ALV functions, you can change the layout, do summarize,
sorting, and so on. You can also export the list to an external file. In Comparison
Mode the sorting function is disabled.
To add, remove, or change some fields in the main screen, see Section [Link]
“Configuring Capture Dashboard” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
Using the Show list, you can restrict the number of entries to be displayed.

150 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 16.3. Using the selection screen

Notes

• If there are 2 evaluation points (VA and PF) available for one inbound
document, the evaluation point VA will be considered in the calculation.
This happens when an inbound process goes through the validation
step, and the corresponding solution process is posted.
• The Capture Dashboard is a calculation-intensive report, it is highly
recommended that the Capture Dashboard is visible only for the key
user. This can be achieved by assigning the Node ID only to the key user.
Refer to Section 8 “Workplace Configuration” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Foundation (VIMZ-
CGF).
• KPIs of Group 3 (Inbound Statistics) is calculated for the current
Inbound system. As a prerequisite, there is only one Inbound system. A
mixture of several Inbound systems is not supported.
• Some unexpected results could be observed in the Capture Dashboard
due to the following facts:

– The data set used for calculating the KPIs of group 1 and 2 is the
subset of the data set for KPIs of group 3. Even when the Inbound
processed are completed (counted as NO_DOC_COMPLETED), they
will be counted for calculating KPIs of group 1, only when they either
went through validation in Inbound, or the corresponding solution
processes are completed (or posted). This may lead to some
discrepancies in the numbers.
– Therefore, if Max Number of Docs is small and contains only
Processed Inbound Documents which are completed in inbound, but
either not going through validation, or the solution processes not
completed, then the Capture Dashboard will be empty.

16.3 Using the selection screen

A selection screen is provided for Capture Dashboard.

To hide or to show the selection screen, click Hide Selection Pane or Show
Selection Pane provided in the menu bar.

The left part of the selection screen comprises business data fields like Company
Code, Vendor, and inbound fields like Capture Profile, Registration ID. They allow
the drill down evaluation of a certain subset of data.

The parameter Max Number of Docs indicates the number of inbound documents
that have been processed. Therefore, it helps to avoid too long processing time for a
big volume of data. All KPIs provided in the main screen and in the plugins are
calculated for this set of data. The most current inbound documents (the highest
Registration IDs) will be included in this set.

The right part of the selection screen comprises inputs relating to the selected period:

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 151

Chapter 16 Using Capture Dashboard

• Click Interval and select the time period available in the menu. All KPIs will be
calculated for inbound documents registered (started) in this time period. Time
period, for example, for Today or Yesterday is the time from 00-hour 00 minute
00 second to 23-hour 59 minute 59 second of that day.
• Select the Compare with the same period before check box if you want to
compare KPIs of the current selected period with the KPIs of the previous period.
Previous period is defined as the day/week/month/quarter/year before last day
(Today or Yesterday)/week/month/quarter/year.
• Click Date and enter the date range for which you want to see the KPIs. All KPIs
will be calculated for inbound documents registered (started) in this time period.
Date range from Date_1 to Date_2 is the time from 00-hour 00 minute 00 second
of Date_1 to 23-hour 59 minute 59 second of Date_2.
• Select the Compare with check box and enter the time range for which you want
to compare the KPIs.

The following buttons are available in the selection screen:

Apply
Click after you enter some selection fields.
Edit
Click to edit the applied selection fields.
Reset
Click to erase all selection fields.

Some user-specific values like Max number of Docs, or Show hits in the Capture
Dashboard and sub-dashboards in plugins will be saved and be used for the next
call.

Note: The default value of Max number of Docs is 10000. For performance
reasons, if you apply a number higher than this default value, the default value
will be used in the next call.

16.4 Using the details pane

Along with the Capture Dashboard, two plugins are provided in the Details Pane.

To hide or to show the details pane, click the button Hide Details Pane or Show
Details Pane provided in the menu bar.

KPIs provided in the plugins are calculated based on the capture profile currently
selected in the Capture Dashboard and other input like time-period or comparison
options in the selection screen.

• Document Layouts: This sub-dashboard provides all KPIs listed in Group 1 and
Group 3. They are calculated per Layout ID (see “Using the Capture Dashboard”
on page 146).

152 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 16.5. Authorization check

• Vendors: this sub-dashboard provides all KPIs listed in Group 1 (see “Using the
Capture Dashboard” on page 146). They are calculated per Vendor.

Using standard ALV functions, you can change the layout, do summarize, sorting,
and so on. You can also export the list to an external file.

To add, remove, or change some fields in the main screen, see Section [Link]
“Configuring Capture Dashboard” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).

Using the Show list, you can restrict the number of entries to be displayed.

16.5 Authorization check

To work with the work center Supplier Invoices, users must be authorized for the
project ID of this work center.

Authorization object Description Fields

J_6NPF_PRJ
Open Text Business Center - The authorized Project ID
J_6NPF_PRJ
Project ID ACTVT '03'
Display

Note: The Capture Dashboard is a calculation-intensive report. OpenText

highly recommends that the Capture Dashboard is visible only for the key
user. This can be achieved by assigning the Node ID only to the key user. Refer
to Section 8 “Workplace Configuration” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide for Foundation (VIMZ-CGF).

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 153

 Part 3
Comparison Approval Portal to VIM Fiori
apps
Part 3 Comparison Approval Portal to VIM Fiori apps

This part provides a comparison regarding the features of OpenText Approval

Portal and the VIM Fiori apps VIM Approve Invoices Fiori appand the VIM Enter
Cost Assignment Advanced Fiori app.

Legend

x
Available
-
Not available
(x)
Functionality in the Fiori app is not as comprehensive as in the Approval Portal.

156 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 17
Comparison Approval Portal to Approve Invoices
app

Table 17-1: Approval Portal features compared to the Approve Invoices app

Area Feature Fiori app -

Portal Fiori app
comment
Document types Non PO based DP
x x
documents
PO based DP
x x
documents
Parked documents
(PO and Non PO)

Note:
Parked
documents
x x
are
supported
in the
context of
DP process
only.
Held documents
(PO and Non PO)

Note: Held
documents
are x x
supported
in the
context of
DP process
only.
Posted documents
x x
(PO and Non PO)
Include credit
x x
memos
Include invoices
with mixed credit x x
and debit lines

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 157

Chapter 17 Comparison Approval Portal to Approve Invoices app

Area Feature Fiori app -

Portal Fiori app
comment
Handling
instructions x -
Handling instructions displayed
Inbox Displays invoices
x x
count
Customizable Restricted to
x x
default fields maximum 5 fields
Customizable
x x
default sorting
Status displayed
x x
for invoice item
The Approve
Invoices (bulk
- x mode) app
provides direct
Inbox Approve approval.
The Approve
Invoices (bulk
- x mode) app
provides direct
Inbox Reject reject.
Bulk Bulk Approve is
not applicable for
referred invoices
x x
and invoices
whose coding is
Bulk approve not completed.
Bulk reject x -
Customizable for
x - Mandatory and
Bulk comments Optional
Invoice details Basic data x x
Basic data custom
x -
fields
Cost assignment x x
Cost assignment
x -
custom fields
Attachments x x
Comments x -
Invoice history x x

158 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Area Feature Fiori app -
Portal Fiori app
comment
Additional
x -
accounting
Configurable in
the Approval
x -
Profitability Portal Admin
Segment console
Account
Assignment (PO
based DP and
x -
parked
documents): only
display
Dynamic custom
x -
Extensions fields support Not out of the box
Attachments Add attachments x x
Delete
x x
attachments
Comments View comments x x
Only within
x x confirmation
Add comments screen
View invoice
x x
History history
Invoice actions Approve x x
Select next
approver from x x Restricted to 100
COA users in list
Reject x x
Refer / inquire x x
Single refer x x
Multi refer x x
Forward x x
Custom actions x -
Document viewing Native browser
x x
plug-in
Web Viewer x x
History Displays
x -
processed invoices

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 159

Chapter 17 Comparison Approval Portal to Approve Invoices app

Area Feature Fiori app -

Portal Fiori app
comment
Displays the
status of each x x
invoice
Pagination
x x
support
Search/Filter
x x
history invoices
Personalisation/ Fields for invoice
x -
Settings list
Initial sort x -
Invoice document:
x N/A
auto-display
Email notification x x
User settings of
Region and x x SAP user login in
language Fiori server
Maintain
x -
substitute
Display invoices
from multiple
x -
systems in one
Multiple backend inbox
Fiori-enabled Provide as tile in
x[a] x
Fiori Launchpad
Semantic
navigation (for
example for - x
Fiori Launchpad vendor id, PO
features number)
Deployment Requires
NetWeaver/SAP x -
Portal
Released for Fiori
in the cloud based
on SAP Business
Technology
- x
Platform, with
versions 16.3.1
Cloud and 7.5 SP7 (plus
deployment CIs)

160 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Area Feature Fiori app -
Portal Fiori app
comment
Requires SAP user
- x
User management (SU01)
[a] can be included as tile but technically not a UI5 app

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 161

Chapter 18
Comparison Approval Portal to Enter Cost
Assignment Advanced app

Table 18-1: Approval Portal features compared to the Enter Cost Assignment
Advanced app

Fiori app -
Area Feature Portal Fiori app
comment
Not Not
designed for designed for
Description
Positioning and a specific a specific
target role role/person role/person
OpenText VIM for coder/ coder/
SAP role requester requester
Non PO based DP
x x
documents
(x -
PO based DP limitations,
-
documents requires
extension)
Parked documents
x -
(PO and Non PO)
Document types
Held documents
- -
(PO and Non PO)
Posted documents
- x
(PO and Non PO)
Credit memos x x
Mix of credit and
x x
debit lines
Basic data x x
Supports simple
Cost assignment x x and complex cost
assignment
Invoice Details
Attachments x x
Comments x -
Invoice history x x
Header based
Coding type x x
coding

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 163

Chapter 18 Comparison Approval Portal to Enter Cost Assignment Advanced app

Fiori app -
Area Feature Portal Fiori app
comment
Item based coding x x
Mix of cost object
x x
types
Cost object: Cost
x x
center
Cost object: Profit
x x
center
Cost object: WBS
x x
element

Cost object types Cost object: Internal

x x
order
Cost object:
x x
Network
Cost object: Sales
x x
document
Cost object: FISTL x x
Cost object: KBLNR x x
Custom field x -
Re-use of coding Coding templates x x
User can insert/
GL accounts change GL accounts x x
(more than one)
Forward x x
Inquire x x
Confirm x x
Invoice actions Decline x x
Custom x -
Select next approver Maximum 100 users
x (x)
from COA in list
Upload attachments x x
Attachments
Delete attachments x x
Display my
x -
processed invoices
History
View invoice
x x
history

164 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Fiori app -
Area Feature Portal Fiori app
comment
Display invoices
from multiple
Multiple backend x -
systems in one
inbox
Status display
Status x x
(inquiry/on behalf)
Balance Calculate balance x x
Export to Excel x x
Coding data Import as a CSV file
handling Import from Excel x x is possible, not as an
Excel file.
View comments x -
Comments
Add comment x x
Mandatory input
x x
fields
Configurable input Input fields x x
fields
Read-only fields x x
Custom fields x -
Handled from
Fields for invoice
x x backend
list
configurations
Handled from
Initial sort x x backend
configurations

Personalisation/ Invoice document:

x N/A
settings auto-display
Email notification x -
Region and User settings of
x x
language Fiori user
Handled from
Substitute x x backend
configurations
Tax data Tax data in items x x
Handling
Handling
instructions x -
instructions
displayed
Provide as tile in
Fiori-enabled x[a] x
Fiori Launchpad

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 165

Chapter 18 Comparison Approval Portal to Enter Cost Assignment Advanced app

Fiori app -
Area Feature Portal Fiori app
comment
Semantic navigation
Fiori Launchpad (for example for
- x
features vendor ID or PO
number)
Requires
NetWeaver/SAP x -
Portal

Deployment Released for Fiori in

the cloud based on
Cloud deployment - x SAP Business
Technology
Platform
Requires SAP user
User management - x
(SU01)
[a] Can be included as tile but technically not a UI5 app

166 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Part 4
SAP NetWeaver Business Warehouse
details
Part 4 SAP NetWeaver Business Warehouse details

This part covers details about the following objects that are part of the OpenText
VIM for SAP BW content for SAP NetWeaver Business Warehouse (SAP NetWeaver
BW):

• InfoObjects
• DataSources
• DataStore Objects (DSOs)
• MultiProviders

Note: The KPI Dashboard is discontinued in version 23.4. However, OpenText

VIM for SAP BW needs some features of the KPI Dashboard. In the following
sections, “KPI Dashboard customizing” is mentioned frequently. For a
collection of relevant documentation sections, see Section 27.4 “KPI Dashboard
content for OpenText VIM for SAP BW” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD). For the
complete KPI Dashboard content, see Section 29 “KPI Dashboard” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIM200407-CGD) (documentation of version 20.4 SPS7).

For more information, see Section 27 “SAP NetWeaver Business Warehouse content”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).

168 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 19

InfoObjects

Business evaluation objects are known in SAP NetWeaver BW as InfoObjects.

InfoObjects are the basic information providers of SAP NetWeaver BW. They
structure the information needed to create data targets.

InfoObjects are divided into the following objects:

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

19.1 Key figures

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

Technical data

Available as of 7.0
Release
Data element /B7999/OIKDURDAY
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No

FI Amount in Key figure: 0DEB_CRE_DC

Document
Currency
This key figure shows the amount of the SAP FI document (financial accounting
document) that was created from the OpenText VIM for SAP invoice in document
currency (0DOC_CURRCY).

For technical data, see the SAP documentation.

FI Amount in Key figure: 0DEB_CRE_LC

Local Currency

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 169

Chapter 19 InfoObjects

The key figure shows the amount of the SAP FI document (financial accounting
document) that was created from the OpenText VIM for SAP invoice in local
currency (0LOC_CURRCY), which means the currency of the company code.

For technical data, see the SAP documentation.

Gross Invoice Key figure: /OPT/KIVGAFC

Amount in
Favorite This key figure shows the gross invoice amount of an OpenText VIM for SAP
Currency
invoice in the favorite currency. The favorite currency is taken from the KPI
Dashboard customizing in the SAP S/4HANA system.

Technical data

Available as of 7.0
Release
Data element /OPT/KIVGAFC
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No
Currency /OPT/UF_CURR

Gross Invoice Key figure: 0LIV_IVGAIC

Amount in
Invoice This key figure shows the gross invoice amount of an OpenText VIM for SAP
Currency
invoice in invoice currency (0INV_CURR). Technically, it is populated with the
value of field GROSS_AMOUNT of table /OPT/VIM_1HEAD.

For technical data, see the SAP documentation.

Number of Key figure: /OPT/KIVCT

Invoices
This key figure shows the number of invoices.

Technical data

Available as of 7.0
Release
Data element /B7999/OIKIVCT
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value

170 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 19.1. Key figures

Restriction No

Number of Key figure: /OPT/KIVECT

Invoices per
Exception This key figure shows the number of invoices to an exception ID.

Technical data

Available as of 7.0
Release
Data element /B7999/OIKIVECT
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No

Number of Key figure: /OPT/KIVEXCT

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

Technical data

Available as of 7.0
Release
Data element /B7999/OIKIVEXCT
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No

Total Approval Key figure: /OPT/KAPDURD

Time (in Days)
This key figure shows the total approval time of an OpenText VIM for SAP invoice
in days. This key figure is calculated as sum of the durations of all approval
processes during the OpenText VIM for SAP process.

Technical data

Available as of 7.0
Release
Data element /B7999/OIKAPDURD

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 171

Chapter 19 InfoObjects

Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No

Total Approval Key figure: /OPT/KAPDURS

Time (in
Seconds) This key figure shows the total approval time of an OpenText VIM for SAP invoice
in seconds. This key figure is calculated as sum of the durations of all approval
processes during the OpenText VIM for SAP process.

Technical data
Available as of 7.0
Release
Data element /B7999/OIKAPDURS
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No

Total Time (in Key figure: /OPT/KTODURD

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

Technical data
Available as of 7.0
Release
Data element /B7999/OIKTODURD
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No

Total Time (in Key figure: /OPT/KTODURS

Seconds)
This key figure shows the total processing time of an OpenText VIM for SAP invoice
in seconds. The total processing time is the time from the start of the DP process

172 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 19.2. Characteristics

until the end of the DP process; this means the time from the start until the end of
the DP workflow.

Technical data

Available as of 7.0
Release
Data element /B7999/OIKTODURS
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No

19.2 Characteristics
Accounting Characteristic: 0AC_DOC_NO
document
number This characteristic shows the document number of the SAP invoice that was created
from the OpenText VIM for SAP invoice.

For technical data, see the SAP documentation.

Amount Class Characteristic: /OPT/CAMTCL

This characteristic classifies OpenText VIM for SAP invoices into different categories
according to their invoice amount. An example for an amount class from the
baseline is “Small amounts” for invoices below 10,000 EUR. The amount classes and
their ranges are maintained in the KPI Dashboard customizing in the leading SAP S/
4HANA system.

Technical data

Available as of 7.0
Release
Data element /B7999/OICAMTCL

Change Run ID Characteristic: 0CHNGID

For details, see the SAP documentation.

Channel Characteristic: /OPT/CCHANNL

This characteristic shows the input channel of the OpenText VIM for SAP invoice.
The channels are maintained in the OpenText VIM for SAP customizing of the
leading SAP S/4HANA system.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 173

Chapter 19 InfoObjects

Technical data

Available as of 7.0
Release
Data element /B7999/OICCHANNL

Company Code Characteristic: 0COMP_CODE

This characteristic shows the company code of the OpenText VIM for SAP invoice.

For technical data, see the SAP documentation.

Company Code Characteristic: /OPT/CCOCOGR

Group
This characteristic groups company codes logically. The company code groups are
maintained in the KPI Dashboard customizing of the leading SAP S/4HANA system.
The mapping of company codes to company code groups is maintained in the local
SAP S/4HANA system of the OpenText VIM for SAP invoice.

IMG activity: Run the /n/OPT/SPRO transaction and navigate to OpenText Vendor
Invoice Management Invoice Solution > Cross Component Configuration >
Central Reporting > KPI Dashboard > Company Code Groups > Company Code
Groups Mapping (BW).

Technical data

Available as of 7.0
Release
Data element /B7999/OICCOCOGR

Created at Characteristic: /OPT/CCREACM

(Calendar Year/
Month) This characteristic shows the calendar year and calendar month when the OpenText
VIM for SAP invoice was created in the SAP S/4HANA system.

Technical data

Available as of 7.0
Release
Data element /B7999/OICCREACM
Reference 0CALMONTH
characteristic

Created at Characteristic: /OPT/CCREADT

(Date)
This characteristic shows the date when the OpenText VIM for SAP invoice was
created in the SAP S/4HANA system.

174 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 19.2. Characteristics

Technical data

Available as of 7.0
Release
Data element /B7999/OICCREADT
Reference 0DATE
characteristic

Created at Characteristic: /OPT/CCREATM

(Time)
This characteristic shows the time when the OpenText VIM for SAP invoice was
created in the SAP S/4HANA system.

Technical data

Available as of 7.0
Release
Data element /B7999/OICCREATM
Reference 0TIME
characteristic

Created at Characteristic:/OPT/CCREATE
(UTC Time
Stamp in Short
This characteristic shows the time stamp in UTC time (Coordinated Universal Time)
Form
(YYYYMMDDh when the OpenText VIM for SAP invoice was created.
hmmss))
Technical data

Available as of 7.0
Release
Data element /B7999/OICCREATE

Credit Memo Characteristic: /OPT/CCMIND

Indicator
This characteristic classifies the OpenText VIM for SAP invoice as invoice or as
credit memo.

Technical data

Available as of 7.0
Release
Data element /B7999/OICCMIND

Currency Characteristic: /OPT/CCCDTFC

Conversion

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 175

Chapter 19 InfoObjects

Date for This characteristic shows the date that was used for the conversion of the gross
Conversion into invoice amount of an OpenText VIM for SAP invoice from the invoice currency into
Favorite
Currency the favorite currency. The favorite currency and the conversion date are determined
from the KPI Dashboard customizing in the SAP S/4HANA system.

Technical data

Available as of 7.0
Release
Data element /B7999/OICCCDTFC
Reference 0DATE
characteristic

Document Characteristic: /OPT/CDOCID

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICDOCID

Document Characteristic: /OPT/CDOCSTA

Status
This characteristic shows the document status of the OpenText VIM for SAP invoice.

Technical data

Available as of 7.0
Release
Data element /B7999/OICDOCSTA

Document Type Characteristic: /OPT/CDOCTY

This characteristic shows the OpenText VIM for SAP document type of the
OpenText VIM for SAP invoice. The OpenText VIM for SAP document types are
maintained in the OpenText VIM for SAP customizing of the SAP S/4HANA system.

Technical data

Available as of 7.0
Release
Data element /B7999/OICDOCTY

Due Date Characteristic: /OPT/CDUEDT

176 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 19.2. Characteristics

This characteristic shows the due date of the OpenText VIM for SAP invoice.

Technical data
Available as of 7.0
Release
Data element /B7999/OICDUEDT

Exception Class Characteristic: /OPT/CEXCCL

Invoice exceptions that occur during the OpenText VIM for SAP process are
grouped in exception classes. This characteristic shows the exception class of an
exception. Examples for exception classes from the baseline are “Compliance issue”
and “Authorization mismatch”. The exception class is determined from the
exception class mapping in the KPI Dashboard customizing of the leading SAP S/
4HANA system.

Technical data
Available as of 7.0
Release
Data element /B7999/OICEXCCL

Exception ID Characteristic: /OPT/CEXCEPT

This characteristic shows the exception ID of an exception that occurred during the
OpenText VIM for SAP process. The exception IDs are maintained in the Central
Reporting customizing in the leading SAP S/4HANA system. Technically, the
exception IDs represent DP process types, header blocks, line blocks or PO/NPO
parking reasons that are to be seen as exceptions.

Technical data
Available as of 7.0
Release
Data element /B7999/OICEXCEPT

Finished at Characteristic: 0CALYEAR

(Calendar Year)
This characteristic shows the calendar year when the processing of the OpenText
VIM for SAP invoice was finished. Technically, this is the calendar year when the DP
workflow was finished.

For technical data, see the SAP documentation.

Finished at Characteristic: 0CALMONTH

(Calendar Year/
Month) This characteristic shows the calendar year and calendar month when the processing
of the OpenText VIM for SAP invoice was finished. Technically, this is the month
when the DP workflow was finished.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 177

Chapter 19 InfoObjects

For technical data, see the SAP documentation.

Finished at Characteristic: 0CALQUARTER

(Calendar Year/
Quarter) This characteristic shows the calendar year and calendar quarter when the
processing of the OpenText VIM for SAP invoice was finished. Technically, this is
the calendar quarter when the DP workflow was finished.

For technical data, see the SAP documentation.

Finished at Characteristic: /OPT/CFINIDT

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICFINIDT
Reference 0DATE
characteristic

Finished at Characteristic: /OPT/CFINITM

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICFINITM
Reference 0TIME
characteristic

Finished at Characteristic /OPT/CFINISH

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

Technical data

Available as of 7.0
Release

178 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 19.2. Characteristics

Data element /B7999/OICFINISH

Fiscal Year Characteristic: 0FISCYEAR

This characteristic shows the fiscal year of the SAP invoice that was created from the
OpenText VIM for SAP invoice.

For technical data, see the SAP documentation.

Fiscal Year Characteristic: 0FISCVARNT

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

For technical data, see the SAP documentation.

Indicator if Characteristic: /OPT/CPOBAS

Invoice is PO
Based or not This characteristic shows whether the OpenText VIM for SAP invoice refers to a
purchase order or not.

Technical data

Available as of 7.0
Release
Data element /B7999/OICPOBAS

Indicator if Characteristic: /OPT/CAPPIND

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICAPPIND

Indicator if Characteristic: /OPT/CBLKIND

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICBLKIND

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 179

Chapter 19 InfoObjects

Indicator if Characteristic: /OPT/CREFIND

Invoice was
Referred or not This characteristic indicates if the OpenText VIM for SAP invoice was referred at
least once.

Technical data

Available as of 7.0
Release
Data element /B7999/OICREFIND

Indicator if Characteristic: /OPT/CREJIND

Invoice was
Rejected or not This characteristic indicates if the OpenText VIM for SAP invoice was rejected at
least once.

Technical data

Available as of 7.0
Release
Data element /B7999/OICREJIND

Parked at Characteristic: /OPT/CPARKCM

(Calendar Year/
Month) This characteristic shows the calendar year and calendar month when the OpenText
VIM for SAP invoice was parked.

Technical data

Available as of 7.0
Release
Data element /B7999/OICPARKCM
Reference 0CALMONTH
characteristic

Parked at Characteristic: /OPT/CPARKDT

(Date)
This characteristic shows the date when the OpenText VIM for SAP invoice was
parked.

Technical data

Available as of 7.0
Release
Data element /B7999/OICPARKDT
Reference 0DATE
characteristic

180 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 19.2. Characteristics

Parked at Characteristic: /OPT/CPARKTM

(Time)
This characteristic shows the time when the OpenText VIM for SAP invoice was
parked.

Technical data

Available as of 7.0
Release
Data element /B7999/OICPARKTM
Reference 0TIME
characteristic

Parked at (UTC Characteristic: /OPT/CPARKED

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICPARKED

Posted at Characteristic: /OPT/CPOSTCM

(Calendar Year/
Month) This characteristic shows the calendar year and calendar month when the OpenText
VIM for SAP invoice was posted.

Technical data

Available as of 7.0
Release
Data element /B7999/OICPOSTCM
Reference 0CALMONTH
characteristic

Posted at Characteristic: /OPT/CPOSTDT

(Date)
This characteristic shows the date when the OpenText VIM for SAP invoice was
posted.

Technical data

Available as of 7.0
Release
Data element /B7999/OICPOSTDT

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 181

Chapter 19 InfoObjects

Reference 0DATE
characteristic

Posted at Characteristic: /OPT/CPOSTTM

(Time)
This characteristic shows the time when the OpenText VIM for SAP invoice was
posted.

Technical data

Available as of 7.0
Release
Data element /B7999/OICPOSTTM
Reference 0TIME
characteristic

Posted at (UTC Characteristic: /OPT/CPOSTED

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICPOSTED

Purchasing Or- Characteristic: 0PURCH_ORG

ganization
This characteristic shows the purchasing organization of the purchase order that the
OpenText VIM for SAP invoice refers to. This characteristic is populated only

• for PO based invoices, and

• if there is only one purchase order assigned.

For technical data, see the SAP documentation.

Purchasing Characteristic: 0PUR_GROUP

Group
This characteristic shows the purchasing group of the purchase order that the
OpenText VIM for SAP invoice refers to. This characteristic is populated only

• for PO based invoices, and

• if there is only one purchase order assigned.

For technical data, see the SAP documentation.

Record Type Characteristic: 0RECORDTP

182 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 19.2. Characteristics

For details, see the SAP documentation.

Request ID Characteristic: 0REQUID

For details, see the SAP documentation.

Source System Characteristic: 0LOGSYS

This characteristic shows the name of the logical system of the OLTP source system
(SAP S/4HANA system).

For technical data, see the SAP documentation.

Source System Characteristic: 0SOURSYSTEM

ID
Source systems can be assigned and logically grouped to source system IDs in the
SAP NetWeaver BW system. This characteristic shows the source system ID. The
assignment of source system to source system IDs is maintained in the SAP
NetWeaver BW system (transaction code RSA1).

For more details, see the SAP documentation.

Time Group Characteristic: /OPT/CTIMEGR

This characteristic determines whether key figures with duration stand for the
process time or the approval time. The time group definitions are maintained in the
KPI Dashboard customizing in the leading SAP S/4HANA system.

Technical data

Available as of 7.0
Release
Data element /B7999/OICTIMEGR

Time Type Characteristic: /OPT/CTIMETY

This characteristic shows the time type of a duration value. The time type classifies
durations within the OpenText VIM for SAP process. An example for a time type
from the baseline is “On time” for OpenText VIM for SAP invoices that have been
processed in 0 to 5 days. The time types are maintained in the KPI Dashboard
customizing in the leading SAP S/4HANA system. The compounded characteristic
Time Group determines whether the time type refers to the processing time or the
approval time.

Technical data

Available as of 7.0
Release
Data element /B7999/OICTIMETY

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 183

Chapter 19 InfoObjects

Compounding /OPT/CTIMEGR

Time Type of Characteristic: /OPT/CAPTITY

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICAPTITY

Time Type of Characteristic: /OPT/CTOTITY

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICTOTITY

Updated at Characteristic: /OPT/CUPDTS

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

Technical data

Available as of 7.0
Release
Data element /B7999/OICUPDTS

Vendor Characteristic: 0VENDOR

This characteristic shows the vendor the OpenText VIM for SAP invoice was sent
from.

For technical data, see the SAP documentation.

184 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 19.3. Units

Vendor Group Characteristic: /OPT/CVENDGR

This characteristic shows the vendor group, the OpenText VIM for SAP invoice is
assigned to. The vendor group classifies vendors into different groups regarding
their total invoice volume. An example for a vendor group from the baseline is
“Vendor Group A (high volumes)”. You maintain the vendor groups in the KPI
Dashboard customizing of the leading SAP S/4HANA system. You maintain the
mapping of vendors to vendor groups in the local SAP S/4HANA system of the
OpenText VIM for SAP invoice. If the vendor of the OpenText VIM for SAP invoice
is not assigned to a vendor group, the ABC indicator from the purchasing
organization data of the vendor master data is taken.

Technical data
Available as of 7.0
Release
Data element /B7999/OICVENDGR

19.3 Units
Currency of Unit: 0INV_CURR
Invoice
This unit shows the document currency of the OpenText VIM for SAP invoice.

For technical data, see the SAP documentation.

Document Unit: 0DOC_CURRCY

Currency
This unit shows the currency of the SAP FI document (financial accounting
document) that was created from the OpenText VIM for SAP invoice.

For technical data, see the SAP documentation.

Favorite Unit: /OPT/UF_CURR

Currency
This unit shows the favorite currency of amount values. The favorite currency is
taken from the KPI Dashboard customizing of the SAP S/4HANA system.

Technical data
Available as of 7.0
Release
Data element /B7999/OIUF_CURR
Reference unit 0CURRENCY

Local Currency Unit: 0LOC_CURRCY

This unit shows the local currency (this means the currency of the company code) of
the SAP FI document (financial accounting document) that was created from the
OpenText VIM for SAP invoice.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 185

Chapter 19 InfoObjects

For technical data, see the SAP documentation.

186 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 20

DataSources

A DataSource is a set of fields that provide the data for a business unit for data
transfer into an SAP NetWeaver BW system. DataSources can be divided into:

• DataSources for transaction data

• DataSources for master data

20.1 DataSources for transaction data

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

Technical data

Application OpenText VIM for SAP > DP Documents

Component
Available as of OpenText VIM for SAP 7.0 (SAP ERP 6.0)
Release
Delta-Capable Yes
Delta Process AIE = After-Images Via Extractor
Extraction from No
Archives
Extraction by Function module /OPT/BGET_DPDOC_H
Extraction /OPT/BEXTR_DPDOC_H_TRAN_ST
Structure

Exception DataSource Transactional Data: OPT/VIM_EXC_TRAN

This structure serves to consistently extract exception data to OpenText VIM for SAP
invoices from OpenText VIM for SAP to a SAP NetWeaver BW system. Only
exceptions of finished invoices (= DP workflow is finished) that are not obsolete or
canceled are extracted.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 187

Chapter 20 DataSources

Technical data

Application OpenText VIM for SAP > Exceptions

Component
Available as of 7.0 (SAP ERP 6.0)
Release
Delta-Capable Yes
Delta Process AIE = After-Images Via Extractor
Extraction from No
Archives
Extraction by Function module /OPT/BGET_EXCEPTIONS
Extraction /OPT/BEXTR_EXC_TRAN_ST
Structure

20.2 DataSources for master data

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

Technical data

Application OpenText VIM for SAP > Master Data

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

Amount Class DataSource Texts: /OPT/VIM_AMTCL_TEXT

(Texts)
This structure serves to consistently extract texts of amount classes from OpenText
VIM for SAP to a SAP NetWeaver BW system. The amount class classifies OpenText
VIM for SAP invoices into different categories according to their invoice amount. An
example for an amount class text from the baseline is “Small amounts”. The amount

188 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 20.2. DataSources for master data

classes and their texts are maintained in the KPI Dashboard customizing of
OpenText VIM for SAP in the leading SAP S/4HANA system.

Technical data

Application OpenText VIM for SAP > Master Data

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

Channel DataSource Master Data Attributes: /OPT/VIM_CHANNEL_ATTR

(Attributes)
This structure serves to consistently extract master data on input channels from
OpenText VIM for SAP to a SAP NetWeaver BW system. The channels are
maintained in the OpenText VIM for SAP customizing of the leading SAP S/4HANA
system.

Technical data

Application OpenText VIM for SAP > Master Data

Component
Available as of 7.0 (SAP ERP 6.0)
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB View/Table /OPT/VIM_CHNL
Extraction /OPT/ESVIM_CHANNEL_AT0001
Structure

Channel (Texts) DataSource Texts: /OPT/VIM_CHANNEL_TEXT

This structure serves to consistently extract the texts of input channels from
OpenText VIM for SAP to a SAP NetWeaver BW system. The channels and their
texts are maintained in the OpenText VIM for SAP customizing of the leading SAP
S/4HANA system.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 189

Chapter 20 DataSources

Technical data

Application OpenText VIM for SAP > Master Data

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

Channel Type DataSource Texts: /OPT/VIM_CHATY_TEXT

(Texts)
This structure serves to consistently extract texts of channel types from OpenText
VIM for SAP to a SAP NetWeaver BW system. The channel types and their texts are
read from the leading SAP S/4HANA system.

Technical data

Application OpenText VIM for SAP > Master Data

Component
Available as of 7.0 (SAP ERP 6.0)
Release
Delta-Capable No
Extraction from No
Archives
Extraction by Fixed values of domain /OPT/CHANNEL_TYPE

Company Code DataSource Master Data Attributes: /OPT/VIM_COCO_ATTR

(Attributes)
This structure serves to consistently extract the mapping of company codes to
company code groups from OpenText VIM for SAP to a SAP NetWeaver BW
system. The mapping of company codes to company code groups is maintained in
the KPI Dashboard customizing of OpenText VIM for SAP in the SAP S/4HANA
system(s).

Technical data

Application OpenText VIM for SAP > Master Data

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

190 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 20.2. DataSources for master data

Extraction from No
Archives
Extraction by DB view/table /OPT/BT_CCGP
Extraction /OPT/ESVIM_COCO_ATTR0001
Structure

Company Code DataSource Texts: /OPT/VIM_CCGROUP_TEXT

Group (Texts)
This structure serves to consistently extract texts of company code groups from
OpenText VIM for SAP to a SAP NetWeaver BW system. The company code group
groups company codes logically. The company code groups and their texts are
maintained in the KPI Dashboard customizing of OpenText VIM for SAP in the
leading SAP S/4HANA system.

Technical data

Application OpenText VIM for SAP > Master Data

Component
Available as of 7.0 (SAP ERP 6.0)
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB View/Table /OPT/KAGR_C_CCGT
Extraction /OPT/ESVIM_CCGROUP_TE0001
Structure

Document DataSource Texts: /OPT/VIM_DOCSTA_TEXT

Status (Texts)
This structure serves to consistently extract texts of document status from OpenText
VIM for SAP to a SAP NetWeaver BW system. The document status and their texts
are maintained in the OpenText VIM for SAP customizing of the leading SAP S/
4HANA system.

Technical data

Application OpenText VIM for SAP > Master Data

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 191

Chapter 20 DataSources

Extraction /OPT/ESVIM_DOCSTA_TEX0001
Structure

Document Type DataSource Texts: /OPT/VIM_DOCTY_TEXT

(Texts)
This structure serves to consistently extract texts of OpenText VIM for SAP
document types from OpenText VIM for SAP to a SAP NetWeaver BW system. The
OpenText VIM for SAP document types and their texts are maintained in the
OpenText VIM for SAP customizing of the SAP S/4HANA system(s).

Technical data
Application OpenText VIM for SAP > Master Data
Component
Available as of 7.0 (SAP ERP 6.0)
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/VIM_T100T
Extraction /OPT/ESVIM_DOCTY_TEXT0001
Structure

Exception DataSource Master Data Attributes: /OPT/VIM_EXCEPT_ATTR

(Attributes)
This structure serves to consistently extract the mapping of exception IDs to
exception classes from OpenText VIM for SAP to a SAP NetWeaver BW system. The
mapping of exceptions to exception classes is maintained in the KPI Dashboard
customizing of OpenText VIM for SAP in the leading SAP S/4HANA system.

Technical data
Application OpenText VIM for SAP > Master Data
Component
Available as of 7.0 (SAP ERP 6.0)
Release
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/KAGR_C_EXCP
Extraction /OPT/ESVIM_EXCEPT_ATT0001
Structure

Exception DataSource Texts: /OPT/VIM_EXCEPT_TEXT

(Texts)
This structure serves to consistently extract the texts of exception IDs from OpenText
VIM for SAP to a SAP NetWeaver BW system. The exception IDs and their texts are

192 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 20.2. DataSources for master data

maintained in the Central Reporting customizing of OpenText VIM for SAP in the
leading SAP S/4HANA system.

Technical data

Application OpenText VIM for SAP > Master Data

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

Exception Class DataSource Texts: /OPT/VIM_EXCCL_TEXT

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

Technical data

Application OpenText VIM for SAP > Master Data

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

Time Group DataSource Texts: /OPT/VIM_TIMEGR_TEXT

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 193

Chapter 20 DataSources

Technical data

Application OpenText VIM for SAP > Master Data

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

Time Type DataSource Master Data Attributes: /OPT/VIM_TIMETY_ATTR

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

Technical data

Application OpenText VIM for SAP > Master Data

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

Time Type DataSource Texts: /OPT/VIM_TIMETY_TEXT

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

194 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 20.2. DataSources for master data

Technical data

Application OpenText VIM for SAP > Master Data

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

Vendor DataSource Master Data Attributes: /OPT/VIM_VENDOR_ATTR

(Attributes)
This structure serves to consistently extract the mapping of vendors to vendor
groups from OpenText VIM for SAP to a SAP NetWeaver BW system. The mapping
of vendors to vendor groups is maintained in the KPI Dashboard customizing of
OpenText VIM for SAP in the SAP S/4HANA system(s).

Technical data

Application OpenText VIM for SAP > Master Data

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

Vendor Group DataSource Texts: /OPT/VIM_VENDGR_TEXT

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 195

Chapter 20 DataSources

Technical data

Application OpenText VIM for SAP > Master Data

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

196 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 21
DataStore objects (DSOs)

A DataStore object (DSO) serves as a storage location for consolidated and cleansed
transaction data or master data on a document (atomic) level. When being used as a
storage location for history reasons, the DSO may also store raw data.

The OpenText VIM for SAP BW content has been designed following the OpenText
VIM for SAP Layered Scalable Architecture (LSA), which groups the SAP
NetWeaver BW objects into different logical layers. The OpenText VIM for SAP LSA
is based on the SAP LSA. For details, see Section 27.1 “OpenText VIM for SAP
Layered Scalable Architecture (LSA)” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD). The OpenText VIM
for SAP BW content uses DSOs in the Data Propagation Layer and in the Corporate
Memory Layer.

21.1 DSOs of the Data Propagation Layer

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

21.1.1 DSOs of the Data Propagation Layer for transaction

data
DP Documents DataStore object: /OPT/DPDOC

This DSO contains OpenText VIM for SAP invoice headers from the SAP S/4HANA
system on a granular level. The DSO is directly supplied from the DataSource /OPT/
VIM_DPDOC_H_TRAN.

Data Sources/Data Targets – As a source of the DSO, the Document Header

DataSource (/OPT/VIM_DPDOC_H_TRAN) is used. This means that finished invoices (=
DP workflow is finished) that are not obsolete or canceled can be loaded into the
DSO.

Most relevant fields are updated in a 1:1 mapping into the DSO. Some fields
(amount class, company code group) are derived from the active tables of the Amount
Class DSO (/OPT/DPAMC) and the Company Group Mapping for Company Code DSO (/
OPT/DPCCG). Several time fields are derived from time stamps.

As a further source of the DSO, the DP Documents DSO (/OPT/DCDOC) from the
Corporate Memory Layer can be used for recovery purposes.

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

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 197

Chapter 21 DataStore objects (DSOs)

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

• InfoCube DP Documents: Volume and Amount (/OPT/CRDOC01)
• InfoCube DP Documents: Times (/OPT/CRDOC02)
• MultiProvider DP Documents: Details (/OPT/MVDOC03)

Exception DataStore object: /OPT/DPEXCD

Classes with
DP Documents This DataStore object contains OpenText VIM for SAP invoices together with their
exception classes, which they have exceptions to. It also contains OpenText VIM for
SAP invoices without any exception.

Data Sources/Data Targets – As a source of the DSO, the DP Documents DSO (/OPT/
DPDOC) and the Exceptions DSO (/OPT/DPEXC) are used.

Most relevant fields from the DP Documents DSO are updated in a 1:1 mapping into
the DSO. The exception class is derived from the active table of the Exception Class
Mapping for Exception DSO (/OPT/DPEID). If the DP document does not have any
exceptions, 0 is set as an initial value in the field Exception Class (/OPT/CEXCCL).

The exception specific fields from the Exceptions DSO are updated in a 1:1 mapping
into the DSO. The end routine adds DP document data from the active table of the DP
documents DSO (/OPT/DPDOC). The field Number of Invoices per Exception Class (/
OPT/KIVEXCT) is set to 1, which indicates that there is one invoice to this exception
class. Even if a DP document has several exceptions to an exception class, the invoice
is counted only once.

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

• InfoCube Exception Classes: Occurences (/OPT/CREXC01)

• MultiProvider Exception Classes: Details (/OPT/MVEXC01)

Exceptions DataStore object: /OPT/DPEXC

This DataStore object contains exceptions to OpenText VIM for SAP invoices from
the SAP S/4HANA system. The exception IDs are maintained in the Central
Reporting customizing in the leading SAP S/4HANA system. Technically, the
exception IDs represent DP process types, header blocks, line blocks or PO/NPO
parking reasons that are to be seen as exceptions.

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

OPT/VIM_EXC_TRAN) is used. This means that exceptions of finished invoices (= DP
workflow is finished) that are not obsolete or canceled can be loaded into the DSO.

Most relevant fields are updated in a 1:1 mapping into the DSO. The exception class
is derived from the active table of the Exception Class Mapping for Exception DSO
(/OPT/DPEID). As a further source of the DSO, the Exceptions DSO (/OPT/DPEXC)
from the Corporate Memory Layer can be used for recovery purposes.

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

198 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 21.1. DSOs of the Data Propagation Layer

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

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

Exceptions with DataStore object: /OPT/DPEXD

DP Documents
This DataStore object contains OpenText VIM for SAP invoices together with their
exceptions. It also contains OpenText VIM for SAP invoices without any exception.

Data Sources/Data Targets – As a source of the DSO, the DP Documents DSO (/OPT/
DPDOC) and the Exceptions DSO (/OPT/DPEXC) are used.

Most relevant fields from the DP Documents DSO are updated in a 1:1 mapping into
the DSO. The exception class is derived from the active table of the Exception Class
Mapping for Exception DSO (/OPT/DPEID). If the DP document does not have any
exceptions, the Exception ID field (/OPT/CEXCEPT) is kept empty and the field
Exception Class (/OPT/CEXCCL) is set to 0 as an initial value.

The exception specific fields from the Exceptions DSO are updated in a 1:1 mapping
into the DSO. The end routine adds DP document data from the active table of the DP
documents DSO (/OPT/DPDOC). The field Number of Invoices per Exception (/OPT/
KIVEXT) is set to 1, which indicates that there is one invoice to this exception.

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

• InfoCube Exceptions: Occurences (/OPT/CREXC02)

• MultiProvider Exceptions: Details (/OPT/MVEXC03)

21.1.2 DSOs of the Data Propagation Layer for master data

Amount Class DataStore object: /OPT/DPAMC

This DataStore object contains the amount classes together with their amount ranges
from the leading SAP S/4HANA system. The amount classes and their ranges are
maintained in the KPI Dashboard customizing of the leading SAP S/4HANA system.

Data Sources/Data Targets – As a source of the DSO, the Amount Class DataSource
(/OPT/VIM_AMTCL_ATTR) is used. As a further source of the DSO, the Amount Classes
DSO (/OPT/DCAMC) from the Corporate Memory Layer can be used for recovery
purposes. For both sources, all fields are updated in a 1:1 mapping into the DSO.

As a target of the DSO, the InfoObject Amount Class (/OPT/CAMTCL) is supplied.

Additionally, the active table of the DSO is used within transformations to
determine the amount class for a DP document.

Channel DataStore object: /OPT/DPCHA

This DataStore object contains the input channels together with their channel type
from the leading SAP S/4HANA system. The channels are maintained in the
OpenText VIM for SAP customizing of the leading SAP S/4HANA system.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 199

Chapter 21 DataStore objects (DSOs)

Data Sources/Data Targets – As a source of the DSO, the Channel DataSource (/OPT/
VIM_CHANNEL_ATTR) is used. As a further source of the DSO, the Channel DSO (/OPT/
DCCHA) from the Corporate Memory Layer can be used for recovery purposes. For
both sources, all fields are updated in a 1:1 mapping into the DSO.

As a target of the DSO, the InfoObject Channel (/OPT/CCHANNL) is supplied.

Company DataStore object: /OPT/DPCCG

Group Mapping
for Company This DataStore object contains the mapping of company codes to company code
Code
groups from all the connected SAP S/4HANA systems. The company code groups
itself are maintained in the KPI Dashboard customizing of the leading SAP S/
4HANA system. The mapping of company codes to company code groups is
maintained in the KPI Dashboard customizing of all SAP S/4HANA systems that are
connected to the SAP NetWeaver BW system.

Data Sources/Data Targets – As a source of the DSO, the Company Code DataSource
(/OPT/VIM_COCO_ATTR) is used. As a further source of the DSO, the Company Code
Group Mapping for Company Code DSO (/OPT/DCCCG) from the Corporate Memory
Layer can be used for recovery purposes. For both sources, all fields are updated in a
1:1 mapping into the DSO.

There is no target of the DSO. The active table of the DSO is used within
transformations to determine the company code group to a company code.

Exception Class DataStore object: /OPT/DPEID

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

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

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

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

Additionally, the active table of the DSO is used within transformations to
determine the exception class to exceptions.

Time Type DataStore object: /OPT/DPTTY

This DataStore object contains the time types to all time groups together with their
ranges. The time types and their ranges are maintained in the KPI Dashboard
customizing of the leading SAP S/4HANA system.

Data Sources/Data Targets – As a source of the DSO, the Time Type DataSource (/
OPT/VIM_TIMETY_ATTR) is used. As a further source of the DSO, the Time Types
DSO (/OPT/DCTTY) from the Corporate Memory Layer can be used for recovery
purposes. For both sources, all fields are updated in a 1:1 mapping into the DSO.

200 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 21.2. DSOs of the Corporate Memory Layer

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

Additionally, the active table of the DSO is used within transformations to
determine the time type to the processing time/the approval time of a DP document.

Vendor Group DataStore object: /OPT/DPVEN

Mapping for
Vendor This DataStore object contains the mapping of vendors to vendor groups from all
connected SAP S/4HANA systems. The vendor groups itself are maintained in the
KPI Dashboard customizing of the leading SAP S/4HANA system. The mapping of
vendors to vendor groups is maintained in the KPI Dashboard customizing of all
SAP S/4HANA systems that are connected to the SAP NetWeaver BW system.

Data Sources/Data Targets – As a source of the DSO, the Vendor DataSource (/OPT/
VIM_VENDOR_ATTR) is used. As a further source of the DSO, the Vendor Group Mapping
for Vendor DSO (/OPT/DCVEN) from the Corporate Memory Layer can be used for
recovery purposes. For both sources, all fields are updated in a 1:1 mapping into the
DSO.

There is no target of the DSO. The DSO can be used to determine the vendor group
to vendors within transformations.

21.2 DSOs of the Corporate Memory Layer

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

21.2.1 DSOs of the Corporate Memory Layer for transaction

data
DP Documents DataStore object: /OPT/DCDOC

This DataStore object contains the OpenText VIM for SAP invoice headers as raw
data as extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Document Header

DataSource (/OPT/VIM_DPDOC_H_TRAN) is used. All relevant fields are updated in a 1:1
mapping into the DSO.

As a target of the DSO, the DSO DP Documents (/OPT/DPDOC) is supplied.

Exceptions DataStore object: /OPT/DCEXC

This DataStore object contains exceptions to OpenText VIM for SAP invoices as raw
data as extracted by the corresponding DataSource.

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

OPT/VIM_EXC_TRAN) is used. All relevant fields are updated in a 1:1 mapping into the
DSO.

As a target of the DSO, the DSO Exceptions (/OPT/DPEXC) of the Data Propagation
Layer is supplied.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 201

Chapter 21 DataStore objects (DSOs)

21.2.2 DSOs of the Corporate Memory Layer for master data

Amount DataStore object: /OPT/DCAMC
Classes
This DataStore object contains the amount classes together with their amount ranges
from the leading SAP S/4HANA system as raw data as extracted by the
corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Amount Class DataSource
(/OPT/VIM_AMTCL_ATTR) is used. All fields are updated in a 1:1 mapping into the
DSO.

As a target of the DSO, the DSO Amount Class (/OPT/DPAMC) of the Data Propagation
Layer is supplied.

Amount Class DataStore object: /OPT/DCAMCT

Texts
This DataStore object contains the texts of amount classes from the leading SAP S/
4HANA system as raw data as extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Amount Class Text
DataSource (/OPT/VIM_AMTCL_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.

As a target of the DSO, the InfoObject Amount Class (/OPT/CAMTCL) is supplied.

Channels DataStore object: /OPT/DCCHA

This DataStore object contains the possible input channels of OpenText VIM for SAP
invoices as raw data as extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Channel DataSource (/OPT/
VIM_CHANNEL_ATTR) is used. All fields are updated in a 1:1 mapping into the DSO.

As a target of the DSO, the DSO Channel (/OPT/DPCHA) of the Data Propagation
Layer is supplied.

Channel Texts DataStore object: /OPT/DCCHAT

This DataStore object contains the texts of the possible input channels of OpenText
VIM for SAP invoices as raw data as extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Channel Text DataSource
(/OPT/VIM_CHANNEL_TEXT) is used. All fields are updated in a 1:1 mapping into the
DSO.

As a target of the DSO, the InfoObject Channel (/OPT/CCHANNL) is supplied.

Channel Type DataStore object: /OPT/DCCHTT

Texts

202 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 21.2. DSOs of the Corporate Memory Layer

This DataStore object contains the texts of the possible types of input channels of
OpenText VIM for SAP invoices as raw data as extracted by the corresponding
DataSource.

Data Sources/Data Targets – As a source of the DSO, the Channel Type Text
DataSource (/OPT/VIM_CHATY_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.

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

Company Code DataStore object: /OPT/DCCCG

Group Mapping
for Company This DataStore object contains the mapping of company codes to company code
Code
groups as raw data as extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Company Code DataSource
(/OPT/VIM_COCO_ATTR) is used. All fields are updated in a 1:1 mapping into the DSO.

As a target of the DSO, the DSO Company Code Group Mapping for Company Code (/
OPT/DPCCG) of the Data Propagation Layer is supplied.

Company Code DataStore object: /OPT/DCCCGT

Group Texts
This DataStore object contains the texts of company code groups as raw data as
extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Company Code Group Text
DataSource (/OPT/VIM_CCGROUP_TEXT) is used. All fields are updated in a 1:1
mapping into the DSO.

As a target of the DSO, the InfoObject Company Code Group (/OPT/CCOCOGR) is

supplied.

Document DataStore object: /OPT/DCDSTT

Status Texts
This DataStore object contains the document status texts of OpenText VIM for SAP
invoices as raw data as extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Document Status Text
DataSource (/OPT/VIM_DOCSTA_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.

As a target of the DSO, the InfoObject Document Status (/OPT/CDOCSTA) is supplied.

Document Type DataStore object: /OPT/DCDTYT

Texts
This DataStore object contains the texts of OpenText VIM for SAP document types as
raw data as extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Document Type Text
DataSource (/OPT/VIM_DOCTY_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 203

Chapter 21 DataStore objects (DSOs)

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

Exception Class DataStore object: /OPT/DCEID

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

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

OPT/VIM_EXCEPT_ATTR) is used. All fields are updated in a 1:1 mapping into the DSO.

As a target of the DSO, the DSO Exception Class Mapping for Exception (/OPT/
DPEID) of the Data Propagation Layer is supplied.

Exception Class DataStore object: /OPT/DCECLT

Texts
This DataStore object contains the texts of exception classes as raw data as extracted
by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Exception Class Text
DataSource (/OPT/VIM_EXCCL_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.

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

Exception Texts DataStore object: /OPT/DCEIDT

This DataStore object contains the texts of exceptions as raw data as extracted by the
corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Exception Text

DataSource (/OPT/VIM_EXCEPT_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.

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

Time Group DataStore object: /OPT/DCTGRT

Texts
This DataStore object contains the texts of time groups as raw data as extracted by
the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Time Group Text
DataSource (/OPT/VIM_TIMEGR_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.

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

Time Types DataStore object: /OPT/DCTTY

This DataStore object contains the possible time types as raw data as extracted by the
corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Time Type DataSource (/
OPT/VIM_TIMETY_ATTR) is used. All fields are updated in a 1:1 mapping into the DSO.

204 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 21.2. DSOs of the Corporate Memory Layer

As a target of the DSO, the DSO Time Type (/OPT/DPTTY) of the Data Propagation
Layer is supplied.

Time Type DataStore object: /OPT/DCTTYT

Texts
This DataStore object contains the texts of time types as raw data as extracted by the
corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Time Type Text DataSource
(/OPT/VIM_TIMETY_TEXT) is used. All fields are updated in a 1:1 mapping into the
DSO.

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

Vendor Group DataStore object: /OPT/DCVEN

Mapping for
Vendor This DataStore object contains the mapping of vendors to vendor groups as raw data
as extracted by the corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Vendor DataSource (/OPT/
VIM_VENDOR_ATTR) is used. All fields are updated in a 1:1 mapping into the DSO.

As a target of the DSO, the DSO Vendor Group Mapping for Vendor (/OPT/DPVEN) of
the Data Propagation Layer is supplied.

Vendor Group DataStore object: /OPT/DCVGRT

Texts
This DataStore object contains the texts of vendor groups as extracted by the
corresponding DataSource.

Data Sources/Data Targets – As a source of the DSO, the Vendor Group Text
DataSource (/OPT/VIM_VENDGR_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 205

Chapter 22
MultiProviders

This chapter focuses on the final data targets in the Virtualization Layer: the
MultiProviders.

SAP recommends to create reports, for example BEx Queries, on MultiProviders and
not on InfoCubes directly. Therefore the version 7.0 BW content delivers
MultiProviders for all its InfoCubes. Technically, the MultiProviders are assigned to
the Virtualization Layer and can be found below the InfoArea with the same name
(OpenText VIM for SAP > Reporting Layer > Virtualization Layer).

The version 7.0 BW content provides the following MultiProviders based on

InfoCubes:

Note: A finished invoice in this context is an invoice that has finished the
OpenText VIM for SAP process. Cancelled and obsolete invoices are excluded
(they are not loaded into the SAP NetWeaver BW system).

MultiProvider DP Documents: Volume and Amounts (technical name: /OPT/

MVDOC01)
This MultiProvider is based on InfoCube /OPT/CRDOC01 and provides answers to
questions as:

• How many finished invoices have been processed?

• What is the total amount of finished invoices?

MultiProvider DP Document: Times (technical name: /OPT/MVDOC02)

This MultiProvider is based on InfoCube /OPT/CRDOC02 and provides answers to
questions as:

• How many finished invoices have been processed with delay/on time?
• How many finished invoices have been approved with delay/on time?

MultiProvider Exception Classes: Occurences (technical name: /OPT/MVEXC02)

This MultiProvider is based on InfoCube /OPT/CREXC01 and provides answers to
questions as:

• How many finished invoices ran into the different exception classes?
• What is the total amount of finished invoices in the different exception
classes?
• What is the percentage of finished invoices with a certain exception class to
all finished invoices?

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 207

Chapter 22 MultiProviders

• What is the exception free rate, which is the rate of “no real exceptions”, to
all finished invoices?

MultiProvider Exceptions: Occurences (technical name: /OPT/MVEXC04)

This MultiProvider is based on InfoCube /OPT/CREXC02 and provides answers to
questions as:

• How are the exceptions of finished invoices distributed in an exception class?

• How many finished invoices ran into the different exceptions?
• What is the total amount of finished invoices in the different exceptions?

Additional MultiProviders based on DataStore Objects are provided to allow detail

views on data using the Report-to-Report Interface in BW Reporting:

Important
For performance reasons, the following MultiProviders are not meant to be
used for extensive reporting. These MultiProviders are based on DataStore
Objects and therefore should be used for a drill down with a very restrictive set
of characteristics only.

MultiProvider DP Document: Details (technical name: /OPT/MVDOC03)

You can use this MultiProvider to get a list of DP documents to a specific,
restrictive combination of characteristics.

Example: List of all DP documents with document type NPO_S4 and channel SCAN to
vendor 1000.

MultiProvider Exception Classes: Details (technical name: /OPT/MVEXC01)

You can use this MultiProvider do get a list of DP documents to a specific
exception class and further restrictive characteristics.

Example: List of all DP documents with document type NPO_S4 and channel SCAN to
vendor 1000 that had at least one exception to exception class Auth. mismatch.

MultiProvider Exceptions: Details (technical name: /OPT/MVEXC03)

You can use this MultiProvider to get a list of DP documents to a specific
exception and further restrictive characteristics.

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

208 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Part 5
Transactions and roles
Part 5 Transactions and roles

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

210 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 23
Transaction profiles for various roles

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

Table headings

1 Indexer
2 AP Processor
3 AP Supervisor
4 Buyer
5 Receiver
6 Requester
7 Coder
8 Approver
9 WF Admin

Transaction Description 1 2 3 4 5 6 7 8 9
VIM
Notifications
VIM /OPT/REMINDER program X X
VIM Analytics
/OPT/ Current
VIM VAN_LIABILITY Liability Report X X
VIM Invoice
VIM /OPT/VIM_WP Workplace X X X X X
SAP Business
SAP SBWP Workplace X X X X X
VIM /OPT/VIM_AGING Aging Report X X
Summary
VIM /OPT/VIM_SUMM Report X X
Central Audit
VIM /OPT/VIM_AUDIT Report X X
Exception
VIM /OPT/VIM_EXCP1 Analysis Report X X
Key Process
Analytics
VIM /OPT/VIM_KPA1 Report X X

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 211

Chapter 23 Transaction profiles for various roles

Transaction Description 1 2 3 4 5 6 7 8 9
Productivity
VIM /OPT/VIM_PROD1 Report X X
Automation
VIM /OPT/VIM_ATM Report X
VIM /OPT/VIM_7AX8 Admin Tool X X X
Change
VIM /OPT/VIM_1AX1 document type X X X
Display
IDocument
VIM /OPT/VIM_1AX13 (indexed) X X X X X X X X
Change process
VIM /OPT/VIM_1AX2 type X X X
VIM /OPT/VIM_1AX3 Send for rescan X X X
Display BDC
VIM /OPT/VIM_1AX4 log X X X
Approval
baseline COA
VIM /OPT/AR_COA maintenance X X
Maintain
notification
VIM /OPT/VIM_8AX50 settings for me
VIM /OPT/VIM_VA2 VIM Analytics X X X X X X X X
VIM Analytics -
VIM /OPT/VIM_VA21 AP Basic X
VIM Analytics –
VIM /OPT/VIM_VA22 AP Advanced X
VIM Analytics -
VIM /OPT/VIM_VA23 Procurement X
VIM Analytics -
VIM /OPT/VIM_VA24 Monitor X
Display special
handling
VIM /ORS/DISP_SH instructions X X X X X
Resubmit Non-
/ORS/ PO invoice for
VIM RESUB_NPO_INV approval X X X
Resubmit PO
invoice for
VIM /ORS/RESUB_PO_INV approval X X X

212 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Transaction Description 1 2 3 4 5 6 7 8 9
Submit Non-PO
/ORS/ invoice for
VIM SUBMIT_NPO_INV approval X X X
Submit PO
/ORS/ invoice for
VIM SUBMIT_PO_INV approval X X X
Cancel PO
/PTGWFI/ invoice, re-enter
VIM CANC_INV_05 PO X X
Cancel PO
/PTGWFI/ invoice, re-enter
VIM CANC_INV_06 Non-PO X X
Delete Non-PO
/PTGWFI/ invoice, re-enter
VIM DEL_INV_01 Non-PO X X
Delete Non-PO
/PTGWFI/ invoice, re-enter
VIM DEL_INV_02 PO X X
Delete PO
/PTGWFI/ invoice, re-enter
VIM DEL_INV_03 PO X X
Delete PO
/PTGWFI/ invoice, re-enter
VIM DEL_INV_04 Non-PO X X
/PTGWFI/ Change vendor
VIM F_CHG_VEN (centrally) X X
/PTGWFI/ Delete park
VIM F_PINV_DEL invoice X X
Year end
program - Non-
VIM /PTGWFI/IE_YEND5 Po invoices X X
Year end
cleanup
program - Non-
VIM /PTGWFI/IE_YEND6 Po invoices X X
/PTGWFI/ Change parking
VIM LIV_CHG_PKRS reason X X X
/PTGWFI/
VIM M_CHG_CONTR Change contract X
Change logistic
VIM /PTGWFI/M_CHGLIV invoice X X

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 213

Chapter 23 Transaction profiles for various roles

Transaction Description 1 2 3 4 5 6 7 8 9
Goods receipt
for purchase
VIM /PTGWFI/M_CR_GR order X
Display
VIM /PTGWFI/M_DIS_REQ requisition X X X
Purchasing
documents for
VIM /PTGWFI/M_LIST_PO material X X X X
Release LIV
VIM /PTGWFI/M_LIX_REL blocked invoice X X
/PTGWFI/ Short pay LIX
VIM M_LIX_SHORTP invoice X X
Reverse goods
VIM /PTGWFI/M_REV_GR receipt for PO X
/PTGWFI/ Short pay:
VIM M_SPAY_2_CM credit memo X X
Short pay:
/PTGWFI/ subsequent
VIM M_SPAY_4_SC credit X X
Short pay:
/PTGWFI/ delete invoice/
VIM M_SPAY_INV create invoice X X
/PTGWFI/ Change parking
VIM PIR_CHG_PKRS reason X X X
All OpenText
VIM for SAP
VIM /OPT* transactions X
All OpenText
VIM for SAP
VIM /ORS* transactions X
All OpenText
VIM for SAP
VIM /PTGWFI* transactions X
Workflow
SAP SW* transactions X
Development
SAP SE* transactions X
System
SAP SM13, SM50, SM12 monitoring X
SAP ST22, ST05, Dump analysis X
SAP SQ* SAP query X

214 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Transaction Description 1 2 3 4 5 6 7 8 9
SAP SCATT Test procedures X
SAP SHDB, SM35, SM35P BDC analysis X
OAWS, OAWD,
OAC2, OAC3, OAC0, SAP
OAA3, SOA0, OAM1, ArchiveLink
SAP OANR transactions X
Post NPO
SAP FB60 invoice X X
Display NPO
SAP FB03 invoice X X X X X X X X X
SAP MIRO Post PO invoice X X
Display PO
SAP MIR4 invoice X X X X X X X X X
SAP ME23N Create new PO X
SAP ME22N Change PO X
Change vendor
SAP XK02 master X
Create new
SAP XK01 vendor X
Create new
SAP ME51N requisition X
Change
SAP ME52N requisition X
List PO by
SAP ME2L vendor X X X X
SAP MIGO Post/reverse GR X
Unblock PO
SAP MRBR invoice X X X
Cancel PO
SAP MR8M invoice X X X
SAP ME31K Create contract X
SAP ME32k Change contract X
Update info
SAP ME12 record X
List PO by
SAP ME2M material X
Display change
SAP RSSCD100 documents X

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 215

Chapter 23 Transaction profiles for various roles

Authorization objects

Class Authorization Description 1 2 3 4 5 6 7 8 9

Display
change
documents
(in
S_SCD0: TCODE=*, Automation
BC_Z ACTVT=08 Report) X
Create new
bank entry in
F_BNKA_MAN: OTV dialog
AAAB ACTVT=01 (optional) X X

216 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Part 6
Business rules
Part 6 Business rules

This part provides an overview of all business rules applied in OpenText VIM for
SAP. This part also provides some technical insight to ease the using of the business
rules. If needed the related configuration aspect is mentioned.

218 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 24
General information about business rules

At the beginning of each business rule, a check is performed whether the business
rule is relevant for this specific document based on the customizing stored in table /
OPT/VIM_T005A (Characteristic Specific Process Types Configuration). The following
check is done:

• Invoice Characteristics
• Invoice type: A for All, N for NPO and P for PO. For example: If the coming
invoice is of type NPO but the rule is applicable for PO, the rule is not executed.
• Simplified Invoice (ignored or not): If this indicator is set, a FM is called to check
whether the invoice is a simplified one.
The check is executed based on the customizing in table /OPT/VIM_T005
(Characteristic Specific Process Types Configuration). If the fixed amount limit is
maintained, the amount of the invoice will be compared with this limit.
Otherwise if the Simplified Invoice Check FM is maintained, the FM is called.
When the invoice is determined as simplified, the rule is not applied for
simplified invoices.
• Invoice category: The invoice category maintained for the business rule (all
categories, intra-community, domestic, import, ...) is compared with the invoice
category of the indexing data. If it does not match, the rule is not executed.

Configuration Run the /OPT/SPRO transaction and navigate to OpenText Vendor Invoice
point Management Invoice Solution > Document Processing Configuration > Document
Type Configuration > Characteristic Specific Document Type Configuration.

Double click the document type. The Characteristic Specific Attributes view opens.

In Dialog Structure, double-click Characteristic Specific Process Types.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 219

Chapter 25
Business rules for PO invoices

This chapter describes the various business rules for PO invoices. The business rules
are delivered out of the box with the product including the high level business logic
of each of these rules.

25.1 Invalid PO Number (PO)

When this business rule is applied, the purchase order number mentioned on the
invoice should be available in SAP S/4HANA. There can be two scenarios as
described in the following:

Matching
The PO number mentioned on the supplier’s invoice matches with the PO
number in SAP S/4HANA, and the PO number is not marked as Deleted. In this
case, no action is taken and the document proceeds to the next logical step.
Mismatch
The PO number mentioned on the supplier’s invoice does not match with the
PO number in SAP S/4HANA, or the PO number is marked as deleted in the
LOEKZ flag. The exception Invalid PO Number (PO) is raised, and the invoice is
automatically routed to the preconfigured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_101
information
All PO numbers if given in one of the following locations are checked against table
EKKO.

• in field PO number on header level

• in field PO list (if available), which are separated by comma, on header level
• in column PO number in the line items

If only one of them is not found in table EKKO, or found with deletion flag set, the
exception Invalid PO Number (PO) is raised.

The business rule writes detailed information about the invalid PO numbers into the
message table.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 221

Chapter 25 Business rules for PO invoices

25.2 Invalid Vendor (PO)

The supplier mentioned on the invoice should be available in the SAP S/4HANA
system. There can be two scenarios as described in the following:

Exists
The invoice supplier exists in the SAP S/4HANA system as a vendor. In this
case, no action is taken and the document proceeds to the next logical step.
Does not exist
The invoice supplier does not exist in the SAP S/4HANA system as a vendor.
The exception Invalid Vendor (PO) is raised. The invoice is automatically
routed to the pre-configured agent depending on the role for further action.

Technical The value from table /OPT/VIM_1HEAD corresponding to the field entered in the
information customizing table of this rule is checked against the LFA1 table.

25.3 Invalid UOM (PO)

The unit of measure (UOM) provided on the invoice should exist in the SAP S/
4HANA system. There can be two scenarios as described in the following:

Exists
The UOM on the supplier invoice exists in SAP S/4HANA. In this case, no action
is taken and the document proceeds to the next logical step.
Does not exist
The UOM on the supplier invoice does not exist in SAP S/4HANA. The
exception Invalid UOM (PO) is raised and the work item is automatically routed
to the pre-configured agent depending on the role for further action.

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

25.4 Invalid Currency (PO)

The currency provided on the invoice should exist in the SAP S/4HANA system.
There can be two scenarios as described in the following:

Exists
The currency on the supplier invoice exists in SAP S/4HANA. In this case, no
action is taken and the document proceeds to the next logical step.
Does not exist
The currency on the supplier invoice does not exist in SAP S/4HANA. The
exception Invalid Currency (PO) is raised, and the work item is automatically
routed to the pre-configured agent depending on the role for further action.

222 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.5. Suspected Duplicate (PO)

Technical The value from table /OPT/_VIM_1HEAD corresponding to the field entered in the
information customizing table of this rule is checked against the table TCURC.

25.5 Suspected Duplicate (PO)

This specific business rule checks for a duplicate invoice based on specific fields
configured in the configuration. There can be two scenarios as described in the
following:

Not a duplicate
If the invoice is not a duplicate, no action is taken and the document proceeds to
the next logical step.

Duplicate
If the invoice is a duplicate, the exception Suspected Duplicate (PO) is raised
and the work item is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_DUP
information
Based on the Duplicate Check Group ID maintained for the Document Type, a
different algorithm is applied to check the duplicate.

The duplicate check can be running on the local system or on the central system
depending on the system landscape (table /OPT/VIM_SYS_LD).

In baseline configuration, there are 2 Duplicate Groups, ID1 for NPO and ID 02 for
PO. FMs (if required) are different for 2 groups.

The Duplicate Group is configured in table /OPT/VIM_T112 with Duplicate Check

Type, Duplicate Check FM for the single and external FM for the multiple backend
landscape. The central system is also maintained here if the multiple backend
landscape is configured.

Duplicate Check Type can be either Function Module (A) or Index Data Fields (B).

In case of A, the function module maintained for this Duplicate Group is called.

In case of B, the fields maintained in table /OPT/VIM_T113 for the Duplicate Group ID
are used to compare the index data of the current document with all existing
documents in table /OPT/VIM_1HEAD. Only documents with relevant status (table /
OPT/VIM_T101) are considered in the checking process. Documents with status 06
(Rescan complete), 10 (Obsolete), and 72 - 90 (OCR specific) are not considered.

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 223

Chapter 25 Business rules for PO invoices

25.6 PO Not Released or Incomplete

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

Released or complete
If the PO is released or complete, no action is taken and the invoice document
proceeds to the next logical step.
Not released or incomplete
If the PO is not released or incomplete, the exception PO Not Released or
Incomplete is raised, and the work item is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_106
information
The following check is carried out for all POs given in the indexing data, either in
field PO number or in field PO list or in the line items:

• Release group of a PO (field FRGGR) if filled will be read from table EKKO for the
given PO. If the release group is not released (indicator KZFRE in table T16FB) ->
Exception.
• If there is no Release group available, and the field Memory (the indicator that PO
is not yet complete) is set -> Exception.

25.7 Unable to Match PO Lines (PO)

This business rule matches the number of lines mentioned on the invoice against the
SAP PO lines. There can be two scenarios as described in the following:

Matches
The number of PO lines on the invoice matches with the number of SAP PO
lines. In this case, no action is taken and the document proceeds to the next
logical step.
Mismatches
The number of PO lines on the invoice exceeds the number of SAP PO lines. The
exception Unable to Match PO Lines (PO) is raised, and the work item is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_107
information
For every PO given in the line items, the number of line item with the same PO
number is counted. If for a certain PO there are more lines in the document than in
the PO, the exception is raised.

If the PO item is a service PO item, the number of service entries in table ESLL is
considered as a reference.

224 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.8. Manual Check Needed / Missing Data for Indexing Lines (PO)

Note: This business rule can be replaced by business rule Manual Check Needed
for Indexing Lines (PO).

25.8 Manual Check Needed / Missing Data for

Indexing Lines (PO)
Since version 7.5, this business rule replaces “Manual Check Needed for Indexing
Lines (PO)” on page 228.

When this business rule is applied, the PO invoice is checked if all data - header and
item lines - is fully provided.

In contrast to the pre-7.5 business rule, this new version additionally checks if the
invoiced quantity on each line does not exceed the GR quantity (that has not been
invoiced yet). This can be switched off if needed, to achieve that the 7.5 business rule
performs only completeness checks. The corresponding configuration is described in
this section.

Note: The check of line item quantity against the GR is performed for each line
item independently. It will not attempt to sum up the quantities of line items
related to the same GR. If you want to perform a check with such grouping of
line items, consider using the business rules “Tolerance Exceeded (PO)”
on page 264 or “Wait for GR - Enhanced Check (PO)” on page 260.

If line item data is complete, that means all mandatory fields are fully supplied, the
business rule is completed without any exception and the document proceeds to the
next logical step.

A line is considered incomplete if one or more mandatory fields are not fully
supplied.

Technical FM /OPT/VIM_DETERMINE_PROC_108
information
In this FM, all mandatory fields of item indexing data are checked.

Mandatory fields for a PO invoice item without GR-based IV:

• PO number
• PO item
• Quantity
• Amount
• UOM

Mandatory fields for a PO invoice item with GR-based IV:

• PO number
• PO item

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 225

Chapter 25 Business rules for PO invoices

• GR reference document
• Delivery note number (if available)
• Quantity
• Amount
• UOM

The exception is raised if at least one line is incomplete or missing (empty). The
missing fields are then determined by the settings of the document type
configuration, PO line determination maintenance.

As mentioned above, this business rule additionally checks whether the invoice
quantity on each line item does not exceed the corresponding GR quantity that is not
invoiced yet. For service POs, SES is checked similarly. This check is made by
default in version 7.5, but can be switched off if needed, to make this business rule
behave similarly to the 7.0 business rule and make only completeness checks. To
switch the additional checks off, create a new entry in the table /PTGWFI/Z_CONST,
using the SM30 transaction:

• Product code: 005

• Version: empty
• Constant name: DISABLE_GR_CHECK
• Constant description: Set to X to disable additional GR checks in PO line
determination (BR 113)
• Constant value: X

25.9 Unable to Determine PO Line Number (PO)

This exception is raised when a corresponding PO line number can not be
automatically determined based on the information mentioned on the supplier’s
invoice. There can be two scenarios as described in the following:

Determined
The corresponding PO line number is determined based on the supplier’s
invoice information. In this case, no action is taken and the document proceeds
to the next logical step.
Unable to Determine
The corresponding PO line number is not determined based on the supplier’s
invoice information. The exception Unable to Determine PO Line Number (PO) is
raised, and the work item is automatically routed to the pre-configured agent
depending on the role for further action.

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

226 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.9. Unable to Determine PO Line Number (PO)

The item number is determined based on the PO Line Determination logic group ID
(POL_GROUPID). This POL Group ID is maintained for each document type in the
Document Type configuration.

The POL Group ID configuration is stored in table /OPT/VIM_TPOL.

If check FM is maintained for the POL Group ID, this FM is called. Otherwise the
Baseline FM /OPT/VIM_DETERMINE_PO_LINES is called. In this FM, fields maintained
for the POL Group ID (which are store in table /OPT/VIM_TPOL3) will be subjects to
be checked. That means the values of such fields in the invoice are used to find the
best match.

The logic of /OPT/VIM_DETERMINE_PO_LINES is the following:

• If the POL Group ID is not maintained in /OPT/VIM_TPOL3, nothing will be done.

• If the PO number is not given in the item line, this value will be read from the
header data of the invoice.
• All item lines from table EKPO are considered for the matching.

The number of fields that shall be matched is also configurable.

If field ALL_MATCH is set, all fields must be matched. Otherwise the number of
matched fields is given in field NOF_FIELDSMATCH.

If field INVOICED_LINES is checked, only item lines marked as Final Invoice (field
EREKZ is marked – meaning that the item is already invoiced and no further invoice
is expected) will be considered.

After the matching, each pair PO number and determined Item Number are checked
against table EKPO. If there is no match -> Exception.

Configuration Run the /n/OPT/SPRO transaction and navigate to OpenText Vendor Invoice
point Management Invoice Solution > Document Processing Configuration > General
Configuration > Automated Line Processing > PO Line Determination > Maintain
PO Line Determination Procedures.

Notes

• The field entered in the POL configuration shall be a valid field. A field that
exists in /OPT/VIM_1ITEM can be entered in the configuration, but it will be
ignored in the POL logic if it does not exist in SAP table EKPO. Except the
following fields which are internally re-mapped from OpenText VIM for
SAP fields to SAP fields:

– BSTME -> MEINS

– WRBTR -> BRTWR
– TAX_AMOUNT -> NAVNW
– TAX_CODE1 -> MWSKZ
– LFSNR -> XBLNR

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 227

Chapter 25 Business rules for PO invoices

• There is a special option for single line POs in single line invoices. The line
item matching is skipped and the line number in the DP document is set to
the number of the single PO line item unless Z constant 005 SINGLE_LINE_
PO_MATCH is set to X.

25.10 Manual Check Needed for Indexing Lines (PO)

Since version 7.5, this business rule is replaced by “Manual Check Needed / Missing
Data for Indexing Lines (PO)” on page 225.

When this business rule is applied, the PO invoice is checked if all data – header and
item lines – is fully provided. The difference between this business rule and the
business rule Unable to Determine PO Line Number is listed in the following:

• This business rule not only checks the PO line number, it checks also other
mandatory fields of the PO.
• Not only the PO line number, but also other mandatory fields, which are not
supplied in the document, will be derived in background.

There can be two scenarios as described in the following:

Complete
If line items data is complete, that means all mandatory fields are fully supplied,
the business rule is completed without any exception and the document
proceeds to the next logical step.
Incomplete or not supplied
If line items are incomplete or not supplied, their mandatory fields will be
derived in background based on the PO number or Delivery numbers provided
in the header. The exception Manuel Check Needed for Indexing Lines (PO) is
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action. A line is considered incomplete if one
or more mandatory fields are not fully supplied.

Technical FM /OPT/VIM_LINES_DERIVE_PO
information
In this FM, all mandatory fields of item indexing data coming from OCR are
checked. Mandatory fields of a Non GR-IV based PO invoice:

• PO number
• PO item
• Quantity
• Amount
• UOM

Mandatory fields of a GR-IV based PO invoice:

• PO number

228 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.11. Invalid PO Item Number (PO)

• PO item
• Delivery Note/GR Reference Document
• Quantity
• Amount
• UOM

The completeness of mandatory fields are checked against data of the PO/DN in
tables EKBE and EKPO.

The exception is raised if at least one line is incomplete or missing (empty). The
missing fields are then determined by the settings of the document type
configuration, PO line determination maintenance.

25.11 Invalid PO Item Number (PO)

When this business rule is applied, the purchase order item number mentioned on
the invoice should be available in SAP S/4HANA. There can be two scenarios as
described in the following:

Matching
The PO item number mentioned on the supplier’s invoice exists within the PO in
SAP S/4HANA, and the PO item number is not marked as Deleted. In this case,
no action is taken and the document proceeds to the next logical step.
Mismatch
The PO item number mentioned on the supplier’s invoice does not exist within
the PO in SAP S/4HANA, or the PO item is marked as deleted with the LOEKZ
flag. The exception Invalid PO Item Number (PO) is raised, and the invoice is
automatically routed to the preconfigured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_ITEMS
information
All item lines with PO number and PO item number are checked in table EKPO.

If at least one of them is not found in table EKPO, or found with deletion flag set, the
exception Invalid PO Item Number (PO) is raised.

The business rule writes detailed information about the invalid PO item numbers
into the message table.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 229

Chapter 25 Business rules for PO invoices

25.12 Invalid Vendor VAT Number (PO)

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

Match
The supplier VAT/Tax number provided on the invoice matches with the VAT/
Tax number mentioned in the vendor master. In this case, no action is taken and
the document proceeds to the next logical step.
Mismatch
The supplier VAT/Tax number provided on the invoice does not match with the
VAT/Tax number mentioned in the vendor master in SAP S/4HANA. The
exception Invalid Vendor VAT Number (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

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

The following fields in the Vendor master data (table LFA1) for VAT ID are
considered in this business rule:

STCEG
VAT Registration Number
STCD1
Tax Number 1
STCD2
Tax Number 2
STCD3
Tax Number 3
STCD4
Tax Number 4

In the indexing screen, the field vendor_vat_no is strictly mapped to field STCEG. The
field vendor_tax_no is mapped to STCD1, STCD2, STCD3, or STCD4. Therefore, if the
vendor applies only STCDx (where x is 1, 2, 3, or 4) in the master data, the field
vendor_tax_no must be used instead of vendor_vat_no in the indexing screen.

The check logic is the following:

If the value in field vendor_vat_no does not match the value in STCEG in vendor
master data, it will be checked against the foreign VAT ID of the vendor, which is

230 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.13. Incomplete Credit Memo (PO)

maintained in table LFAS. If the field vendor_vat_no is filled and checked

successfully, no further checking will be executed.

Otherwise, the field vendor_tax_no will be checked according to the following logic:

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

25.13 Incomplete Credit Memo (PO)

The supplier’s credit memo should have the following information:

• The supplier’s original invoice number (reference number)

• The invoice date of the supplier’s original invoice

When this business rule is applied, the credit memo should have the original
suppliers invoice number and the original invoice date. Also, the original invoice
number mentioned on the credit memo must be present in the SAP S/4HANA
system. The following scenarios are possible:

Present and matching

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

Technical FM: /OPT/VIM_DETERMINE_PROC_121

information
First the customizing related to the Credit Memo (CM) for the specific country is
read from table /opt/vim_t005. At least one of the two checkboxes CM Ref No Req
and CM Ref Date Req must be checked. Otherwise the check is not executed.

If CM Ref No is required for CM but the field CM REF NUMBER in the indexing is
left blank -> Exception

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 231

Chapter 25 Business rules for PO invoices

If Ref Date is required for CM but the field CM REF DATE in the indexing is left
blank -> Exception

If CM Ref Data Validate is not checked -> No further check is executed.

If CM Ref Data Validate is required, the rule will search for a document with the
Posting date = CM Ref date (if CM_Ref_Date is required) and the Reference number
= CM Ref No (if CM_Ref_No is required). The searching will be carried out in the
following logic:

• First the DP documents are searched (table /OPT/VIM_1HEAD).

• If not found, the SAP parked document (table vbkpf) is searched.
• If not found, the posted documents (table rbkp for PO) are searched.
• If no matched document found at all, the exception Incomplete Credit Memo
(PO) is raised.

Customizing Run the /OPT/SPRO transaction and navigate to Document Processing

Configuration > Document Type Configuration > Characteristic Specific
Document Type Configuration.

Double-click the characteristic (country).

On the Characteristic Specific Attributes screen, there are 3 check boxes:

CM Ref No Req.
CM reference number is required.
CM Ref Date Req.
CM Reference Date is required.
CM Ref Data Validate
The correctness of the CM Ref No and Ref Date is validated against data in the
DP documents (OpenText VIM for SAP tables) or in the SAP documents (SAP
tables).

This customizing is stored in table /opt/vim_t005 for the specific country.

25.14 Vendor Address Mismatch (PO)

The Remit-To-Address (supplier’s address to which the billing should happen)
should match with the SAP Vendor Master’s address as this is a required
information on the suppliers invoice. There can be two scenarios as described in the
following:

Match
The Remit-To-Address provided on the Invoice matches with the address on the
vendor master. In this case, no action is taken and the document proceeds to the
next logical step.

232 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.15. Missing Item Quantity (PO)

Mismatch
The Remit-To-Address does not match with the address on the vendor master.
The exception Vendor Address Mismatch (PO) is raised and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

The following SAP vendor address fields are matched:

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

Technical FM /OPT/VIM_DETERMINE_PROC_122
information

25.15 Missing Item Quantity (PO)

The supplier invoice should have the quantity of the goods being supplied or the
extent of the services being provided.

When this business rule is applied, the quantity on the DP index document line item
should have been filled. There can be two scenarios, as described in the following:

Entered
No action is taken and the document proceeds to the next logical step.
Not entered
The exception Missing Item Quantity (PO) is raised and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 233

Chapter 25 Business rules for PO invoices

25.16 Missing Item Unit Price (PO)

When this business rule is applied, the Unit price on all items on the DP index items
should have been filled. Otherwise the exception is raised.

Normally, if the business rule Manual Check Needed for Indexing Lines (PO) is
applied in some step before, the information like Unit Price is already derived from
PO and no exception is raised.

25.17 Missing Invoice Date (PO)

When this business rule is applied, the invoice date on the DP index document
header should have been filled. There can be two scenarios, as described in the
following:

Entered
No action is taken and the document proceeds to the next logical step.
Not entered
The exception Missing Invoice Date (PO) is raised and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical If field BLDAT of the indexing data is not filled -> Exception
information

25.18 Invalid Tax Info (PO)

The supplier’s invoice should carry the total VAT amount and (or) the VAT %
indicating the VAT payable.

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

Tax information present and matching

The tax information entered on the DP document has a corresponding valid SAP
tax information. The document proceeds to the next logical step.

Example: The VAT % mentioned on the invoice has a corresponding VAT tax code.

Tax information present and not matching

The tax information entered on the DP document does not have a corresponding
valid SAP tax information. The exception Invalid Tax Info (PO) is raised and

234 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.18. Invalid Tax Info (PO)

the document is automatically routed to the pre-configured agent depending on

the role for further action.

Example: The VAT % mentioned on the invoice does not have a corresponding VAT tax
code in SAP S/4HANA.

Tax information not present

The tax information is not present on the invoice. The exception Invalid Tax
Info (PO) is raised and the document is automatically routed to the pre-
configured agent depending on the role for further action.

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

Technical FM /OPT/VIM_DETERMINE_PROC_126 (for countries like DE, US, …)

information
The following logic applies:

• Firstly, the country key (for example US, DE, JP) is determined. If PO numbers
are given in the header data, the country key is derived from the PO. If there is
no PO number in the header, the country key is derived from the very first PO in
the lines. If there are no PO numbers available in the header and in the lines, the
country will be determined based on the company code.
• FM /OPT/VIM_TAX_CODE_DETERMINE is called. This FM will determine the tax code
based on the tax rate if there is any. The logic used for the tax code determination
can be configured in /OPT/SPRO. The tax jurisdiction code is also determined here
if required.
• Specific for Canada:

– The tax code determination function module is /OPT/VIM_CA_TAX_CODE_

DETERMINE.

– FM /OPT/VIM_SHIP_TO_REG_DETERMINE is called to determine the ship to

adress.
– For Canada or for companies where the country is maintained in table /OPT/
VIM_CTRY, tax_rate is calculated as sum of all tax_rate 1 to 4, zero_tax_rate =
sum of all zero_tax_rate from 1 to 4. The same is executed to the tax_rate and
zero_tax_rate on all item lines.

After the step of tax code determination is executed, the tax rate and tax code are
checked as described in the following (for all countries).

• For PO invoice at both levels, header and line item:

– If tax rate is given and not 0.00, tax code is blank -> Exception. That means the
tax rate is not valid and no corresponding tax code can be determined.
– The combination tax rate = 0.00, tax code is blank is only allowed if the option
Allow zero tax is not checked. That means if the option Allow zero tax is
checked, there must be a valid tax code for the tax rate 0.00.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 235

Chapter 25 Business rules for PO invoices

• The tax code, if given or determined by the logic mentioned above, either in the
header or in the line items, will be checked by the following logic.

– Look in table t005 for the procedure for calculating tax maintained for the
country key, for example TAXD. If the tax code is given in the invoice and the
Procedure key is found (not initial), they will be checked against table T007A.
If tax code is not given -> exception
• Tax amount if given in the invoice is checked in the following steps. If not, the
value in the total tax amount is used. The logic:
If auto_calc (Auto calculate Tax) is not checked:

– If tax_amount # 0 but tax_code in header or in all line items is not given ->
Exception
– If tax_amount = 0, the check is successful only if the tax_rate = 0 and
allow_free_tax = X, OR both tax_rate and tax_code are initial, in header as
well as in the line items.

If auto_calc is checked:

– If tax_code in header and in all line items is initial -> Exception.

– If tax_code is given in header or in line items, it is checked in table t007a.

Customization You can customize the logic for tax code determination in /OPT/SPRO > Document
point Processing Configuration > Document Type Configuration > Maintain Document
Types. Double-click the DP Document Type.

You can also customize the options like Auto Calculate Tax, Allow Zero Tax, Allow
without Tax here.

Auto Calculate Tax

The system will calculate the tax based on the tax code supplied by the indexing
or determined by the logic mentioned above.
Allow Zero Tax
The system will determine the tax code for the tax rate 0.00. If blank or empty,
the system cannot determine the tax code.
Allow without Tax
If tax information is not given in the invoice, the exception is not raised. The
business rule is successful.
Calculate Tax on Net
If this option is selected, the tax is calculated like it is done in the SAP
transaction FV60 when the Editing Option Calculate tax on net amount is
selected.

For all Canada-specific customizing, run the /n/OPT/SPRO transaction and navigate
to OpenText Vendor Invoice Management Invoice Solution > Document

236 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.19. Missing Date of Supply (PO)

Processing Configuration > Document Type Configuration > Specific Country

Settings > Canada.

25.19 Missing Date of Supply (PO)

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

Date of supply present

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

Date of supply not present

The date of supply on the vendor’s invoice is not present. In this case, the
exception Missing Date of Supply (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

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

information

25.20 ISR Number Mismatch (PO)

This business rule is specific for Switzerland. The supplier’s invoice should have the
ISR number on the invoice as this is a required information.

When this business rule is applied, the ISR number on the DP index document
header should be present and matching with the vendor master. There are the
following scenarios:

ISR number present and matching

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

ISR number present and not matching

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

ISR number not present

If the ISR number is not mentioned on the invoice but the vendor master has it,
the exception ISR Number Mismatch (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_129
information
• If the Z constant ESR_CHECK_REQUIRED for product 005 is set to X, both ISR
numbers in the header data and in the vendor master must be given. Otherwise,
the exception is raised.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 237

Chapter 25 Business rules for PO invoices

• If both ISR numbers on invoice and in the vendor master data are given, they are
checked irrespectively whether the Z constant is set or not. The check logic is the
following:

– The ISR number in the header data must contain the ISR number given in the
vendor master data (table lfa1). Otherwise, the exception will be thrown.
– The ISR number in the vendor master data is allowed to contain the dash
symbol, for example 01-162-8 where 01 represents the ESR code, 162 the
participant number, and 8 the check digit.
• If the Z constant ESR_CHECK_REQUIRED for product 005 is not set, the check will be
successful even if the ISR number in the invoice or the ISR number in the vendor
master data or both are not available.

25.21 Invalid Recipient VAT Number (PO)

Every country has its typical VAT structure. This information can be found in the
Company Master Data. For some countries, the recipient’s VAT number is a
mandatory information for some kind of invoices (for example for intra-community
invoices or triangulation invoices).

When this business rule is applied, the recipient VAT number provided on the
invoice must match with the company’s VAT Number provided in the company
code in SAP S/4HANA. The following scenarios are possible:

Match
The recipient’s VAT number provided on the invoice matches with the VAT
number mentioned in the company code information. In this case, no action is
taken, and the document proceeds to the next logical step.
Mismatch
The recipient’s VAT number provided on the invoice does not match with the
VAT number mentioned in the company code in SAP S/4HANA. The exception
Invalid Recipient VAT Number (PO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.
Not present
If the recipient’s VAT number is not present on the invoice, the exception
Invalid Recipient VAT Number (PO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.

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

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

• If the field Recipient VAT number is filled with a value, this value is compared
with the value in field STSEG (VAT Registration Number) in table T001 for the
Company Code on the invoice. If the VAT Registration Number is not blank and
does not match the Recipient VAT Number given in the invoice -> Exception

238 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.22. Payment Terms Mismatch (PO)

Note: The Company Code is either given in the invoice header or can be
derived from PO information (for PO invoice).

For Austria the check will be carried out only when the gross amount exceeds some
specific amount (for example 10,000 in the local currency).

25.22 Payment Terms Mismatch (PO)

The payment terms mentioned on the suppliers invoice should match with the
payment terms configured in the SAP S/4HANA system. There can be two scenarios
as described in the following:

Match
The payment terms provided on the vendor’s invoice matches with the payment
terms mentioned in the purchase order or vendor master in SAP S/4HANA. In
this case, no action is taken and the document proceeds to the next logical step.
Mismatch
The payment terms provided on the vendor’s invoice does not match with the
payment terms maintained in the purchase order or vendor master in SAP S/
4HANA. The exception Payment Terms Mismatch (PO) is raised and the invoice
is automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_130
information
If payment terms are not given in the invoice, no check will be executed.

If payment terms are given in the invoice, they must match with the payment terms
determined for the invoice.

The payment terms of a PO invoice are determined from the PO data (table EKKO) if
given, or from the purchasing data of the vendor (table LFM1). If not found, it is
determined from the vendor company code data.

If the payment terms do not match, the exception is raised.

25.23 Invalid Siret Number (PO) (France)

The SIRET number provided on the invoice is matched against the SIRET number
maintained in the vendor master. There can be two scenarios as described in the
following:

Match
The SIRET number provided on the invoice matches with the SIRET number in
the vendor master. In this case, no action is taken and the document proceeds to
the next logical step.
Mismatch
The SIRET number provided in the invoice does not match with the SIRET
number in the vendor master. The exception Invalid SIRET Number (PO) is

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 239

Chapter 25 Business rules for PO invoices

raised, and the invoice is automatically routed to the pre-configured agent

depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_229
information
The SIRET number (field siret_no) given in the invoice is compared with the tax
number stored in the master data of the vendor.

• If the tax number is maintained for the vendor and it does not match the number
given in the invoice, the exception is raised.
• If the tax number is not maintained for the vendor, no exception is raised.

Customizing There are 4 tax numbers available in the master data of the vendor (table lfa1). In
order to determine which number is applied for the SIRET, the Z constant VENDOR_
SIRET_NO_FLD for product code 005 (table /PTGWFI/Z_CONST) must be maintained
with a correct value. Possible values are STCD1, STCD3, and STCD4.

25.24 Invalid Company Address (PO)

The recipient address provided on the invoice should match with the SAP S/4HANA
company code’s address. There can be two scenarios as described in the following:

Match
The recipient address provided on the invoice matches with the company code
address. In this case, no action is taken and the document proceeds to the next
logical step.
Mismatch
The recipient address does not match with the address of the company code.
The exception Invalid Company Address (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_132
information
The company code address is read from table T001 (Company Code Master Data)
and is compared with the address given in the section Ship-To-Address in the
indexing. If the address of the company code is not maintained (blank) or does not
match with the Ship-To-Address in the invoice -> Exception

Customization The address of the company code can be maintained and displayed in the SAP
Reference IMG (transaction SPRO): Financial Accounting > Company Code > Enter
Global Parameters. Click the Address button to maintain or display the company
code address.

240 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.25. Vendor Invoice Reference Missing (PO)

25.25 Vendor Invoice Reference Missing (PO)

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

Invoice number present

The invoice number on the vendor’s invoice is present. In this case, no action is
taken and the document proceeds to the next logical step.
Invoice number not present
The invoice number on the vendor’s invoice is not present. In this case, the
exception Vendor Invoice Reference Missing (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical If field XBLNR of the indexing data is not filled with the reference number ->
information Exception

25.26 Payment Method Mismatch (PO)

The payment method mentioned on the supplier’s invoice should match with the
payment method configured in the SAP S/4HANA system. There can be two
scenarios as described in the following:

Match
The payment method provided on the vendor’s invoice matches with the
payment method mentioned in the vendor master in SAP S/4HANA. In this
case, no action is taken and the document proceeds to the next logical step.
Mismatch
The payment method provided on the vendor’s invoice does not match with the
payment method maintained in the vendor master in SAP S/4HANA. The
exception Payment Method Mismatch (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM /OPT/VIM_DETERMINE_PROC_134
information
If the payment method is not given in the invoice, no check is executed.

If the payment method is given in the invoice, it must match with the payment
method maintained in the vendor master data in the current company code (table
LBF1).

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 241

Chapter 25 Business rules for PO invoices

25.27 Missing/Invalid Tax Exempt Text (PO)

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

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

25.28 Missing Import Special Text (PO)

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

Special text present

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

Special text not present

The special text on the vendor’s invoice indicating tax exemption is not present.
In this case, the exception Missing Import Special Text (PO) is raised and the
invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_136
information
The function will check the tax rate given on the invoice. If the tax rate is zero and
there is no text entered in the field Import Text, the exception is raised.

If the tax rate is not zero but there is some text given in the field Import Text, the
exception is raised as well.

25.29 Missing Item Description (PO)

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

Item description present

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

Item description not present

The item description on the vendor’s invoice is not present. In this case, the
exception Missing Item Description (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

242 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.30. Missing Mandatory Information (PO)

Technical FM /OPT/VIM_DETERMINE_PROC_137
information
All line items of the invoice are checked.

If both fields SGTXT (Item Text) and MAKTX (Material Description) (in table /OPT/VIM_
1ITEM) of one of the line items are empty, the exception is raised.

25.30 Missing Mandatory Information (PO)

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

Field value entered in mandatory field

In this case, no action is taken and the document proceeds to the next logical
step.
Field value not entered in mandatory field
In this case, the exception Missing Mandatory Information (PO) is raised, and
the invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_138
information
Fields with status Required are read from table /opt/vim_nw_scrn. If there is one
required field that is not filled in the indexing data of the invoice, the exception is
raised.

The item fields are considered as well (table /opt/vim_i_scrn).

The header field groups SHIP_TO_ADDRESS and REMIT_TO_ADDRESS are evaluated. If

such a group is declared as mandatory, all address components except house
number and region must be filled.

Configuration Fields on the DP document can be maintained in /OPT/SPRO on the following levels:
point

On header level
OpenText Vendor Invoice Management Invoice Solution > Document
Processing Configuration > Document Type Configuration > Maintain
Document Types.
Select the DP Document Type. In Dialog Structure, double-click Index Header
Configuration.
On item level
OpenText Vendor Invoice Management Invoice Solution > Document
Processing Configuration > Document Type Configuration > Maintain
Document Types.
Select the DP Document Type. In Dialog Structure, double-click Index Item
Configuration.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 243

Chapter 25 Business rules for PO invoices

25.31 Missing/Invalid Triangulation Text (PO)

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

Triangulation text present

The special text on the vendors invoice indicating triangulation is present. In this
case, no action is taken and the document proceeds to the next logical step.
Triangulation text not present
The special text on the vendor’s invoice indicating triangulation is not present.
In this case, the exception Missing/Invalid Triangulation Text (PO) is raised,
and the invoice is automatically routed to the pre-configured agent depending
on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_139
information

25.32 Invalid Sales Tax for the Region (PO)

This business rule is only relevant for Canada. When this business rule is applied,
the ship-to address region, tax type and tax rate mentioned on the invoice is
matched against the allowed tax type and the tax rates for that region in SAP S/
4HANA. In case of any deviations, the exception Invalid Sales for the Region
(PO) is raised, and the invoice is routed to the pre-configured agent depending on
the role for further action. There are many scenarios that could arise depending on
the configuration. In the following, some of the possible scenarios are described:

Information matching
The ship-to region and tax types entered on the DP document matches with the
configured SAP S/4HANA tax type for that region. The document proceeds to
the next logical step.

Example: For the region Ontario, the tax type GST is supplied, and the tax type GST is
configured in SAP S/4HANA for that region.

Information not matching

The ship-to region and tax types entered on the DP document does not have a
corresponding valid configured SAP S/4HANA tax type for that region. The
exception Invalid Sales Tax for the Region (PO) is raised and the document is
automatically routed to the pre-configured agent depending on the role for
further action.

Example: For the region Ontario, the tax type GST is supplied, and the tax type
configured in SAP S/4HANA is PST for that region.

Information not present

The ship-to region information is not present on the invoice. Depending on the
configuration option:

244 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.32. Invalid Sales Tax for the Region (PO)

Default Region
Company code address/PO address are used as ship-to region. The business
rule proceeds with the above scenarios. You can configure this derivation of
the ship-to region on OpenText VIM for SAP side.

Blank
Keep the not present information as blank and raise exception Invalid Sales
Tax for the Region (NPO). The document is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM /OPT/VIM_CHECK_TAX_RATE
information

First step
If tax rates (1 to 4) on line items are not given at all, they are copied from the tax
rates in the header data. The missing tax rates are determined (as much as
possible) based on the ship-to region and the configuration maintained in table /
OPT/VIM_TAX_PRO (Country Specific Tax - Province Relationship) for the region.

If the ship-to region is not given in the invoice (field SHIP_TP_REGION), it is

determined based on the options maintained in the customizing table /OPT/VIM_
STR_DET. A different logic is used for every possible option.

Possible options are the following:

Company Code
The ship-to region is determined based on the company code and read from
table T001.

Company Code -> PO

The ship-to region is determined based on the company code. If not found,
the ship-to region is determined based on the PO given in the invoice.

PO -> Company Code

The ship-to region will firstly be determined based on the PO given in the
invoice. If not found, the ship-to region is determined based on the company
code. To determine the ship-to region based on the PO, the PO is read from
the header. If not given, the first PO in the line items is considered. Based on
the plan given in the PO, the ship-to region is read from table T001W.

Fixed Value
The region maintained in table /OPT/VIM_STR_DET is used as ship-to region.

Function Module
The FM maintained in table /OPT/VIM_STR_DET is used to determine the
ship-to region.

Second step
After all tax rates (in header as well as on line items) are determined, they will
be checked against table /OPT/VIM_TAX_PRO. If some tax rates are required
according to the customizing table, but not given in the invoice or cannot be
determined in the first step, the exception is raised.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 245

Chapter 25 Business rules for PO invoices

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

25.33 Vendor Audit Required (PO)

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

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

Technical FM /OPT/VIM_DETERMINE_PROC_151
information
If the vendor number is maintained in table /OPT/VIM_BL_VAUD with flag Audit
Required set, the exception Vendor Audit Required (PO) is raised for all invoices of
this vendor. The wildcard * in column Vendor Number means “All Vendors”.

Customization point

• Run the /OPT/VIM_BL_VAUD transaction or

• run the /n/OPT/VIM transaction and navigate to OpenText VIM - Invoice
Solution > SAP menu > Customization > Vendor Audit List Configuration.

25.34 Vendor Maintenance (PO)

This business rule is not in use yet.

25.35 Vendor Mismatch (PO)

The vendor number of the invoice should match with the purchase order vendor
number in the SAP S/4HANA system. There can be two scenarios as described in the
following:

Match
The vendor number provided matches with the vendor number of the purchase
order in SAP S/4HANA. In this case, no action is taken and the document
proceeds to the next logical step.
Mismatch
The vendor number provided does not match with the vendor number of the
purchase order in SAP S/4HANA. The exception Vendor Mismatch (PO) is raised

246 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.36. Service Entry Required (PO)

and the invoice is automatically routed to the pre-configured agent depending

on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_153
information
The check is executed for every PO given in the invoice: in the header, in the PO list,
or in the line items. The vendor for each PO is read from table EKKO and is checked
against the vendor given in the invoice header.

• If matched, no further processing is required.

• If not matched, the partner functions maintained in the Z constant EXIT_VEND_
PARTN_FUNC for product 005 (table /PTGWFI/Z_CONST) is used to fetch the partner
vendor from table EKPA for a certain PO. If the vendor is not found in table EKPA,
determine if the vendor in the DP document is a partner (table WYT3). If this check
fails, further check if the vendor is maintained as invoicing party in PO or if the
vendor is maintained in conditions. If all these checks are not successful, the
exception is triggered.
• If the Z constant EXIT_VEND_PARTN_FUNC does not exist in the Z table or is blank,
the exception is raised as well.

25.36 Service Entry Required (PO)

When this business rule is applied, the service based invoice received by the
recipient is checked for the service entry sheet in the SAP S/4HANA system. There
can be two scenarios as described in the following:

Exists
The service entry sheet exists. In this case, no action is taken and the document
proceeds to the next logical step.
Does not exist
The service entry sheet does not exist. In this case, the exception Service Entry
Required (PO) is raised, and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_154
information
The PO number given in the invoice is checked in the following logic:

• Check whether any PO positions of the related POs have the GR flag enabled
(indicator WEPOS). If, for any of those positions, no service entry sheet can be
found in the current MIRO line item proposal , the exception is raised.
• With version 7.0 SP3 and later, the two Z constants SERVICE_ENTRY_BSTYP and
SERVICE_ENTRY_BSART (product code 005) are not used any more.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 247

Chapter 25 Business rules for PO invoices

25.37 Currency Mismatch (PO)

This business rule exception gets triggered when the currency provided on the
invoice does not match with the purchase order currency. There can be two
scenarios as described in the following:

Match
The currency provided on the vendor’s invoice matches with the purchase order
currency in SAP S/4HANA. In this case, no action is taken, and the document
proceeds to the next logical step.
Mismatch
The currency provided on the vendor’s invoice does not match with the
purchase order currency in SAP S/4HANA. The exception Currency Mismatch
(PO) is raised, and the invoice is automatically routed to the pre-configured
agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_155
information
The currency given in the header data of the invoice is compared with the currency
of all POs given in the invoice. All POs that are entered in the header and in the line
items are considered.

The POs given in the new field PO List is not considered yet.

25.38 Unit of Measure Mismatch (PO)

This business rule exception gets triggered when the unit of measure (UOM)
provided on the invoice does not match with the purchase order unit of measure.
There an be two scenarios as described in the following:

Match
The UOM provided on the vendor’s invoice matches with the purchase order
UOM in SAP S/4HANA. In this case, no action is taken, and the document
proceeds to the next logical step.
Mismatch
The UOM provided on the vendor’s invoice does not match with the purchase
order UOM in SAP S/4HANA. The exception Unit of Measure Mismatch (PO) is
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_156
information
For service POs, the MIRO proposal is calculated and the UOM is compared to the
MIRO proposal.

For normal POs, if all UOMs in the tables (EKPO, EKBE, MSEG) are the same, the UOM
is compared directly to the UOM in the line item. If the UOMs in the tables are

248 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.39. Approval Required (PO)

different, the MIRO proposal is calculated and the UOM is compared to the MIRO
proposal.

Additional change in version 7.0 and higher: Line items with qualifiers (additional
costs) are not considered for UOM matching because they are line items that
transport costs only.

25.39 Approval Required (PO)

This business rule exception gets triggered when one of the PO numbers, which are
given in the invoice header or in the line items, is maintained in the table of
Approval-required POs (table /OPT/VIM_BL_POAP). This business rule does not
consider the POs given in the PO list.

Technical FM /OPT/VIM_DETERMINE_PROC_150
information
Customization Run the /n/OPT/VIM transaction and navigate to OpenText VIM - Invoice Solution >
point SAP menu > Customization > PO Invoice Approval Configuration.

Note: If the exception is triggered, a work item is created and forwarded to the
requisitioner of the PO if this requisitioner is maintained in COA (Chart of
Authority). If not, no agent can be found for the current work item.

25.40 Freight on Invoice (PO)

This exception is triggered when the unplanned freight on the invoice is greater than
the freight amount maintained in the global configuration. There can be two
scenarios as described in the following:

Does not exceed

The unplanned freight amount on the vendor’s invoice does not exceed the
freight amount maintained in the global configuration. In this case, no action is
taken and the document proceeds to the next logical step.

Exceeds
The unplanned freight amount on the vendor’s invoice exceeds the freight
amount maintained in the global configuration. The exception Freight on
Invoice (PO) is raised, and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_157
information
The freight amount given on the invoice header is compared with the maximal
freight amount maintained in the Z constant 005 / FREIGHT_AMOUNT. If the freight
amount on the invoice exceeds the amount maintained in the Z constant, the
exception is raised. If no value is maintained for this Z constant, no check is
executed.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 249

Chapter 25 Business rules for PO invoices

25.41 Tax Audit Required (PO)

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

No tax audit required

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

Technical FM /OPT/VIM_DETERMINE_PROC_158
information
The configuration maintained in table /OPT/VIM_BL_TAX is checked. If company
code, material group, and vendor number on the invoice are maintained with the
flag set in table /OPT/VIM_BL_TAX, the exception Tax Audit Required (PO) is raised.

The wildcard in all columns means “All”.

Customization point

• Transaction /OPT/VIM_BL_PTX, or
• run the /n/OPT/VIM transaction and navigate to OpenText VIM - Invoice
Solution > SAP menu > Customization > Tax Audit Configuration for PO
Invoices.

25.42 Invalid Requisitioner (PO)

This exception is raised when the requisitioner mentioned on the supplier invoice
does not match with the SAP purchase order requisitioner. There can be two
scenarios as described in the following:

Match
The supplier invoice requisitioner matches with the SAP purchase order
requisitioner. In this case, no action is taken and the document proceeds to the
next logical step.
Mismatch
The supplier invoice requisitioner does not match with the SAP purchase order
requisitioner. The exception Invalid Requisitioner (PO) is raised and the
invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_303
information

250 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.43. PO Credit Memo Processing (PO)

Process of the business rule

1. The system checks the requester on the original invoice, if present. It must be
validated against PO requester (@ 1st item) or PO creator. If both are not the
same, the exception is raised.
2. The system checks whether the invoice is going through the approval process or
not. The check logic is the same as in the /OPT/VIM_DETERMINE_PROC_
150 function module. For more information, see “Approval Required (PO)”
on page 249. Only if the invoice is going through the approval process, the
system will perform the following checks.
3. The system checks if the Requester is available in the indexing screen or not. If
the requester is available, the system checks whether the requester exists in the
user map table /ORS/USERMAP (COA) or not. If not, the exception is raised.
4. If the requester is not available, the system checks if the Requisitioner/
Requester is available (field AFNAM in table EKPO). If the AFNAM field is available,
the system checks the user map table. If the user is not available there, the
exception is raised.
5. If the field AFNAM is not available, the system checks for the creator of the PO
(field ERNAM in table EKPO). If the ERNAM field is available, the system checks the
user map table. If the creator is not available, the exception is raised.

25.43 PO Credit Memo Processing (PO)

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

Not a Credit Memo

If the invoice is not a Credit Memo, no action is taken and the document
proceeds to the next logical step.
Credit Memo
If the invoice is a Credit Memo, the exception PO Credit Memo Processing (PO)
is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical The field CREDIT_MEMO is checked. If it is selected, the invoice is handled as a

information Credit Memo and the exception is raised.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 251

Chapter 25 Business rules for PO invoices

25.44 Company Code Mismatch (PO)

The company code of all POs entered in the invoice should match with the company
code in the header if the Company Code field of the header is filled. There can be
two scenarios as described in the following:

Match
The company code of all POs entered in the header and in the line items matches
the company code of the invoice. In this case, no action will be taken and the
document proceeds to the next logical step. If the company code is not given in
the header, no matching is executed.
Mismatch
The company code of at least one PO that is entered in the header and in the line
items does not match the company code of the invoice. The exception Company
Code Mismatch (PO) is raised and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.

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

The company codes of all POs entered in the header and in the line items of the
invoice is read from table EKKO. The company codes of each PO are compared with
the company code of the invoice. If there is at least one mismatch, the exception is
raised.

When the exception occurs, the first “mismatching” PO number is returned in the
header structure if the constant FAIL_PO_HEADER_SET for product code 005 is set.

The business rule writes detailed information about the mismatches found into the
message table.

25.45 Confirmation Required from SRM (PO)

Important
This business rule is deprecated.

If this business rule is maintained as active for the given Document Type, all POs on
the invoice are checked whether there is a SRM-related PO. If there are some SRM-
related POs, some items of these POs are flagged as GRIV but there is no GR posted
for those items. The exception is raised, and the invoice is automatically routed to
the pre-configured agent depending on the role for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_162
information
• All POs on the invoice are checked whether they are SRM-related or not. If there
is a FM maintained in the constant LIX / SRM_PO_CHECK, this FM is called for the
checking. If there is no FM maintained, the status of the PO is compared with all

252 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.46. Invalid Payment Reference (PO)

statuses maintained in the Z constant LIX / SRM_PO_STATUS. If the status matches,

the PO is considered as SRM-related.
• If the PO is SRM-related, a line item has a GRIV flag, and no GR or multiple GRs
exist for this item -> exception

25.46 Invalid Payment Reference (PO)

The business rule checks the payment reference using the SAP S/4HANA function
module FI_PAYREF_CHECK. Payment reference check is used in Norway, Sweden and
Finland.

If the check fails, the exception Invalid Payment Reference (PO) is raised, and the
invoice is automatically routed to the pre-configured agent depending on the role
for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_176
information

25.47 Missing Invoice Code (PO)

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

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

25.48 Invalid Invoice Code Format (PO)

If the Invoice Code (INVOICE_CODE) field length is not equal to 10 or 12, the
exception Invalid Invoice Code Format (PO) is raised.

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

Technical FM: /OPT/VIM_DETERMINE_PROC_112

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 253

Chapter 25 Business rules for PO invoices

25.49 Invalid Characters in Secret Code (PO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_114

information

25.50 Invoice Older than Allowed (PO)

If the difference of system date and invoice date is greater than the number of days
mentioned in the Z constant 005 / INVOICE_DAYS_OLD, the exception Invoice Older
than Allowed (PO) is raised, and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_116

information

25.51 Invalid Vendor Invoice Number (PO)

The vendor reference value (XBLNR) length must be 8. Otherwise, the exception
Invalid Vendor Invoice Number (PO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_117

information

25.52 Invalid Common Ordinary Invoice (VAT Exists)

(PO)
If the invoice category is Non VAT (N) and a VAT amount (VAT_AMOUNT) exists,
the exception Invalid Common Ordinary Invoice (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_118

information

254 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.53. Check Hand Written (PO)

25.53 Check Hand Written (PO)

If the gross amount is greater than 100000 and the Not hand written
(NOT_HAND_WRITTEN) check box is not selected, the exception Check Hand
Written (PO) is raised, and the invoice is automatically routed to the pre-configured
agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_119

information

25.54 Verification Required (PO)

If the AFTCS_VALIDATION field is empty, the exception Verification Required (PO)
is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_141

information

25.55 Validate Bank Details (PO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_270

information
The business rule consists of the following checks:

• Check if bank entry exists in database in case of one-time-vendor

• Check if bank data is provided in case of one-time-vendor
• Check if bank data and vendor fit together
• Check if IBAN number has valid syntax and does not contradict the other bank
details
• Check if SWIFT code has valid syntax and does not contradict the other bank
details
• Check SWIFT code in bank data table BNKA, if SWIFT code is given (SEPA check
according SAP note 1400525)

The business rule writes detailed information about the error reason into the
message table.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 255

Chapter 25 Business rules for PO invoices

25.56 Invalid/Missing Vendor ABN Number (PO)

If the vendor VAT number (VENDOR_VAT_NO) field is empty, or if the vendor VAT
number (VENDOR_VAT_NO) is not matching with the vendor master data, the exception
Invalid/Missing Vendor ABN Number (PO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_172

information

25.57 Invalid/Missing Recipient ABN Number (PO)

If the recipient VAT number (RECIPIENT_VAT_NO) field is empty, or if the recipient
VAT number (RECIPIENT_VAT_NO) is not matching with company code master
data, the exception Invalid/Missing Recipient ABN Number (PO) is raised and the
invoice is automatically routed to the pre-configured agent depending on the role
for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_173

information

25.58 Missing Vendor Name (PO)

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

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

25.59 Missing Recipient Name (PO)

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

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

25.60 Invalid Tax Description (PO)

This business rule is specific to India. If the vendor belongs to India and the Tax
Description (TAX_DESC) field is empty, the exception Invalid Tax Description (PO)
is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_190

information

256 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.61. GR Not Done - Simple Check

25.61 GR Not Done - Simple Check

If a PO is GR-IV based and the Good Receipt is not done, the exception GR Not Done -
Simple Check is raised, and the invoice is automatically routed to the pre-configured
agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_189

information

25.62 Missing Vendor ECC Number (PO)

This business rule is specific to India. If the vendor belongs to India and the ECC
Number (ECC_NO) field value is empty, the exception Missing Vendor ECC Number
(PO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_177

information

25.63 Mismatch Vendor ECC Number (PO)

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

• The vendor belongs to India.

• The material in the DP document is excisable material.
• The ECC Number (ECC_NO) field value does not match with the vendor master
data.

If these conditions apply, the exception Mismatch Vendor ECC Number (PO) is raised,
and the invoice is automatically routed to the pre-configured agent depending on
the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_178

information

25.64 Missing Vendor CST Number (PO)

This business rule is specific to India. If the vendor belongs to India and the CST
Number (CST_NO) field value is empty, the exception Missing Vendor CST Number
(PO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_179

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 257

Chapter 25 Business rules for PO invoices

25.65 Mismatch Vendor CST Number (PO)

This business rule is specific to India. If the vendor belongs to India, and the CST
Number (CST_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor CST Number (PO) is raised and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_180

information

25.66 Missing Vendor TIN/TOT Number (PO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_181

information

25.67 Mismatch Vendor TIN/TOT Number (PO)

This business rule is specific to India. If the vendor belongs to India, and the TIN/
TOT Number (TIN_TOT) field value does not match with the vendor master data, the
exception Mismatch Vendor TIN/TOT Number (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_182

information

25.68 Missing Vendor LST Number (PO)

This business rule is specific to India. If the vendor belongs to India and the LST
Number (LST_NO) field value is empty, the exception Missing Vendor LST Number
(PO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_183

information

258 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.69. Mismatch Vendor LST Number (PO)

25.69 Mismatch Vendor LST Number (PO)

This business rule is specific to India. If the vendor belongs to India and the LST
Number (LST_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor LST Number (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_184

information

25.70 Missing Vendor PAN Number (PO)

This business rule is specific to India. If the vendor belongs to India and the PAN
Number (PAN_NO) field value is empty, the exception Missing Vendor PAN Number
(PO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_185

information

25.71 Mismatch Vendor PAN Number (PO)

This business rule is specific to India. If the vendor belongs to India and the PAN
Number (PAN_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor PAN Number (PO) is raised and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_186

information

25.72 Missing Vendor STC Number (PO)

This business rule is specific to India. If the vendor belongs to India and the STC
Number (STC_NO) field value is empty, the exception Missing Vendor STC Number
(PO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_187

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 259

Chapter 25 Business rules for PO invoices

25.73 Mismatch Vendor STC Number (PO)

This business rule is specific to India. If the vendor belongs to India and the STC
Number (STC_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor STC Number (PO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_188

information

25.74 Wait for GR - Simple Check (PO)

If a PO is GR-IV based and the Good Receipt is not done, this exception is raised.
This rule is optimized to be maintained for a waiting process type.

• For any PO number within indexing data (header/item), the PO lines are checked
if any line has the GR-IV based flag set.
• For these lines, it is checked that at least one open invoicing line exists.

Technical FM: /OPT/VIM_DETERMINE_PROC_164

information

25.75 Wait for GR - Enhanced Check (PO)

If a PO is GR-IV based and the Good Receipt is not done, this exception is raised.
This rule is optimized to be maintained for a waiting process type.

• For any PO item within indexing data (header/item), the delivered PO lines are
checked if any line has the GR-IV based flag set.
• For each of these lines, it is checked that there is an open proposal item (GR) with
the same quantity as the invoice line.

Note: An exact quantity match is performed, not a tolerance check.

Technical FM: /OPT/VIM_DETERMINE_PROC_165

information

25.76 Service Entry Required (PO) - Enhanced Check

The DP process should stop with an exception Service Entry Required (PO) -
Enhanced Check, when trying to process a “Service PO” invoice where the amount is
higher than the open amount for invoicing.

For this, a new business rule 166 Service Entry Required (PO) - Enhanced Check
has been introduced in version 7.5 SP5. If the DP line item amount is higher than the
open amount to be invoiced, the system raises the exception.

Technical FM: /OPT/VIM_DETERMINE_PROC_159

information

260 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.77. SCB Indicator / Supplying Country Missing (PO)

25.77 SCB Indicator / Supplying Country Missing (PO)

This business rule checks if the SCB Indicator (field SCB_IND) and Supplying
Country (field SUPCOUNTRY) has been entered.

Technical The rule needs to be activated for relevant countries in the Country/Characteristic-
Information specific settings for foreign vendors. There is no function module used, the check is
achieved using configuration only.

25.78 Brazil - Missing NF Data (PO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_191

information

25.79 Brazil - Missing NF Customizing (PO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_192

information

25.80 Brazil - NF Validation Check Failed (PO)

For future use.

Technical FM: /OPT/VIM_DETERMINE_PROC_193

information

25.81 Brazil - Wait for GR - Simple Check (PO)

If a PO is GR-IV based and the Good Receipt is not done, this exception is raised.
This rule is optimized to be maintained for a waiting process type.

• For any PO number within indexing data (header/item), the PO lines are checked
if any line has the GR-IV based flag set.
• For these lines, it is checked that at least one open invoicing line exists.

Technical FM: /OPT/VIM_DETERMINE_PROC_194

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 261

Chapter 25 Business rules for PO invoices

25.82 Brazil - Wait for GR - Enhanced Check (PO)

If a PO is GR-IV based and the Good Receipt is not done, this exception is raised.
This rule is optimized to be maintained for a waiting process type.

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

Technical FM: /OPT/VIM_DETERMINE_PROC_195

information

25.83 Russia - Wait for TORG-12/ACT - Simple Check

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

• For any PO number within indexing data (header/item), the PO lines are checked
if any line has the GR-IV based flag set.
• For these lines, it is checked that at least one open invoicing line exists.

Technical FM: /OPT/VIM_DETERMINE_PROC_196

information

25.84 Russia - Wait for TORG-12/ACT - Enhanced

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

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

Technical FM: /OPT/VIM_DETERMINE_PROC_197

information

262 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.85. Russia - Original Invoice Mismatch (PO)

25.85 Russia - Original Invoice Mismatch (PO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_198

information

25.86 Invalid Withholding Tax Code / Type (PO)

The business rule is valid for documents that are subject to withholding tax. There
are 2 possible scenarios:

Scenario 1 If the withholding tax type is not valid for the invoice vendor, the exception is
raised.

OR

Scenario 2 If the withholding tax type is not valid for the invoicing party, and the invoicing
party is maintained at PO level with the IGNORE_IP field cleared in the indexing
screen, the exception is raised.

Technical FM: /OPT/VIM_DETERMINE_PROC_401

information

25.87 Withholding Tax Base Amount Bigger than Total

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

Technical FM: /OPT/VIM_DETERMINE_PROC_402

information

25.88 Check BPF Added Data (PO)

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

Technical FM: /OPT/VIM_DETERMINE_BPF_VALID

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 263

Chapter 25 Business rules for PO invoices

25.89 Tolerance Exceeded (PO)

When this business rule is applied, the PO invoice amount and quantity are checked
whether they do not exceed the PO amount, quantity, and tolerances like in the MIRO
transaction.

Vendor Specific You can define tolerance groups for each company code using the OMRX transaction.
Tolerance You can assign tolerance groups to each supplier (vendor) in the vendor master
record, using the XK03 transaction.

Tolerance in this case means acceptance, based on the total:

If the difference is within the tolerance range, the system automatically generates a
difference line on a neutral income/expense account for small differences. This
applies to invoices with debit/credit differences when posting the invoice.

Technical FM: /OPT/VIM_DETERMINE_PROC_406

information

25.90 Missing VAT Date (PO)

This business rule checks if the VAT date is provided in the DP document. If not, the
DP processing stops with an exception. Users are required to enter the VAT date in
the DP document. To enable the check, add the respective process type for DP
document or characteristic, with the function /OPT/VIM_DETERMINE_PROC_407.

The baseline configuration of this business rule contains predefined process options.
You can adjust the process options list to suit your scenarios.

Technical FM: /OPT/VIM_DETERMINE_PROC_407

information

25.91 Check Withholding Tax Data (PO)

This business rule is valid for documents that are subject to withholding tax. If the
withholding tax checked flag is not filled, the exception is raised.

Technical FM: /OPT/VIM_DETERMINE_PROC_415

information

25.92 Down Payment Clearing (PO)

To support clearing down payments through OpenText VIM for SAP, this business
rule checks if a down payment was made against the PO or not. If yes, background
or auto posting is skipped and the invoice is routed to the AP Processor for manual
posting. The AP Processor can enter down payment data while posting the invoice.

Down payment The down payment clearing function is used to clear the down payments that are
clearing in SAP posted with reference to a PO directly in logistics invoice verification (MIRO
transaction). During posting through MIRO, the system checks if the down payment
was made earlier for the respective PO. MIRO provides a way to enter the down
payment data through the Down Payment Clearing button.

264 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.93. Missing/Invalid GST Partner (PO)

Technical FM: /OPT/VIM_DETERMINE_PROC_DWNCLR

information
Process type 416 Down Payment Clearing (PO)

25.93 Missing/Invalid GST Partner (PO)

This business rule is specific to India for PO invoices.

If the vendor on the invoice belongs to India and if the GST Partner (GST_PART)
field value is empty or not maintained in vendor master, then this exception is
raised. The invoice is automatically routed to the pre-configured agent depending
on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_IN_419

information

25.94 Missing/Invalid Vendor GST Reg. No (PO)

This business rule is specific to India for PO invoices.

If the GST Registration Number (GST_REG_NUM) field value is empty or not

matching against tax number 3 (STCD3) of the GST Partner’s vendor master, then this
exception is raised. The invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_IN_421

information

25.95 Missing/Invalid HSN/SAC code (PO)

This business rule is specific to India for PO invoices (Material based).

If one of the following conditions applies:

• HSN/SAC code is empty on PO invoice lines.

• Plant is empty on PO invoice lines.
• HSN/SAC code on PO invoice lines does not match with value of “control code”
(STEUC) on “Foreign trade export” view of material master (MARC), of given
Material on PO invoice lines.

Then this exception is raised and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_IN_423

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 265

Chapter 25 Business rules for PO invoices

25.96 Missing/Invalid Receiving Location GST

Registration No (PO)
This business rule is specific to India for PO invoices.

The field value of the Receiving Entity GST Registration Number (REC_GST_REG_NUM)
might be empty. It also might not match against the GST Registration Number
(GSTIN) of the combination of the receiving company code / business place.

In these cases, this exception is raised. The invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_IN_428

information
The function module is shared with the corresponding NPO business rule. See
“Missing/Invalid Receiving Location GST Registration No (NPO)” on page 294.

Table: J_1BBRANCH / field: GSTIN

25.97 Cannot Verify Quantity/Price Exceptions (PO)

This business rule is used for the VIM Confirm Quantity and Price Fiori app. The
business rule is activated if posting simulation cannot be performed by some reason
(missing data, locks on the PO, and so on). If activated, the work item is routed to
the AP role. The responsible agent can verify the data, process the data validation
and let the business rules run to allow for a new attempt to run the simulation.

Technical FM: /OPT/VIM_DETERMINE_PROC_425

information

25.98 Quantity/Price Mismatch (PO)

This business rule is used for the VIM Confirm Quantity and Price Fiori app. It is
activated if potential payment blocks are detected or if the invoice requires a
confirmation (non GR/IV), but the Fiori app process should not start automatically.

It is also activated after the finish of the Fiori app step to let the AP role verify the
information passed from the Fiori app and decide on the next steps.

Technical FM: /OPT/VIM_DETERMINE_PROC_418

information

266 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.99. Quantity/Price Confirmation Required (PO)

25.99 Quantity/Price Confirmation Required (PO)

This business rule is used for the VIM Confirm Quantity and Price Fiori app. It is the
actual Fiori app step. A dialog work item for this step is also visible in the SAP GUI
inbox, but the dashboard has only the Rerun Rules option configured in standard
OpenText VIM for SAP because it is supposed to be processed from the app.

Technical FM: /OPT/VIM_DETERMINE_PROC_417

information

25.100 Missing Company Code (PO)

This business rule checks if the company code (field BUKRS) has been filled. To use
this business rule, the BUKRS field must be configured as required field.

25.101 Missing Gross Amount (PO)

This business rule checks if the gross amount (field GROSS_AMOUNT) has been filled.
To use this business rule, the GROSS_AMOUNT field must be configured as required
field.

25.102 Check for Reduction Invoice (PO)

This business rule checks whether the invoice is a reduction invoice or not.

Reduction invoice
If the value of the correction ID field (KZMEK) is Vendor Error. Reduce Invoice,
the system raises this exception.
No reduction invoice
If the correction ID (KZMEK) has a value different from Vendor Error. Reduce
Invoice, the system does not raise this exception and considers this invoice as a
normal invoice.

Technical FM: /OPT/VIM_DETERMINE_PROC_428

information
Posting of this kind of invoice should be done in a different way. That is why a new
BDC ID 202 has been introduced to post a reduction invoice in background.

If you want to auto-post a reduction invoice in background, configure the BDC ID

202 against the business rule and enter Auto post as X.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 267

Chapter 25 Business rules for PO invoices

25.103 Check Vendor/Company Address (PO/NPO)

This rule is checked by random in the standard setting. The rule checks vendor and
company address against vendor and company code master data.

Technical FM: /OPT/VIM_DETERMINE_PROC_132 and /OPT/VIM_DETERMINE_PROC_122

information

25.104 Invoice subject for payment split (PO)

This business rule is specific for Poland. It checks if the Splitpayment flag is passed
from OCR and routes the invoice to a user for manual action.

Technical FM: /OPT/VIM_DET_PROC_SPLITPAYMENT

information

25.105 Missing UUID Number (PO)

If the company code is related to Mexico, the system checks whether the Mexico
UUID field is empty or not. If it is empty, the system raises the exception. If it
contains any value, the system proceeds to check the next exception.

Technical FM: /OPT/VIM_DET_PROC_MX_UUID

information

25.106 Missing lean services entry sheet (PO)

When this business rule is applied, the lean service based invoice received by the
recipient is checked for the lean service entry sheet in the SAP S/4HANA 1809
system. The following scenarios are possible:

Exists
The lean service entry sheet exists. In this case, no action is taken and the
document proceeds to the next logical step.

Does not exist

The lean service entry sheet does not exist. In this case, the exception Missing
lean services entry sheet (PO) is raised, and the invoice is automatically
routed to the preconfigured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_516

information
The PO number given in the invoice is checked using the following logic:

Check whether any PO positions of the related POs have the GR flag enabled
(indicator WEPOS) and the product type group is 2 (Service). If, for any of those
positions, no service entry sheet can be found in the current MIRO line item proposal,
the exception is raised.

268 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 25.107. Check lean services - invoice amount vs GR amount (PO)

25.107 Check lean services - invoice amount vs GR

amount (PO)
When trying to process a Lean Service PO invoice where the amount is higher than
the open amount for invoicing, the DP process should stop with an exception Check
lean services - invoice amount vs GR amount (PO).

For this scenario, a new business rule Check lean services - invoice amount vs GR
amount (PO) is introduced. If the DP line item amount is higher than the open
amount to be invoiced, the system raises the exception.

Technical FM: /OPT/VIM_DETERMINE_PROC_517

information

BDC ID supported
2200

25.108 Missing/Invalid Invoice Reference Number (PO)

This exception is raised when the invoice reference number (IRN) on the invoice for
Indian company codes is not provided or if it has a length different from 64
characters.

Technical FM: /OPT/VIM_DETERMINE_PROC_452

information

25.109 Portugal - Missing QR code/ATCUD (PO)

This exception is raised if the ATCUD is not populated.

Technical Field INV_REF_NUM is marked as a required field in the Sequence Steps under the
information Document Type Definition configuration.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 269

Chapter 26
Business rules for NPO invoices

This chapter describes the various business rules for NPO invoices. The business
rules are delivered out of the box with the product including the high level business
logic of each of these rules.

26.1 Invalid Vendor (NPO)

The supplier mentioned on the invoice should be available in the SAP S/4HANA
system. There can be two scenarios as described in the following:

Exists
The invoice supplier exists in the SAP S/4HANA system as a vendor. In this
case, no action is taken, and the document proceeds to the next logical step.
Does not exist
The invoice supplier does not exist in the SAP S/4HANA system as a vendor.
The exception Invalid Vendor (NPO) is raised, and the invoice is automatically
routed to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_201

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

26.2 Invalid Currency (NPO)

The currency provided on the invoice should exist in the SAP S/4HANA system.
There can be two scenarios as described in the following:

Exists
The currency on the supplier invoice exists in SAP S/4HANA. In this case, no
action is taken, and the document proceeds to the next logical step.
Does not exist
The currency on the supplier invoice does not exist in SAP S/4HANA. The
exception Invalid Currency (NPO) is raised and the work item is automatically
routed to the pre-configured agent depending on the role for further action.

Technical Field WAERS is checked against SAP table TCURC.

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 271

Chapter 26 Business rules for NPO invoices

26.3 Invalid Requestor ID (NPO)

This exception is raised when the requestor mentioned on the supplier invoice does
not exist in SAP S/4HANA. There can be two scenarios as described in the following:

Exists
The requestor mentioned on the supplier invoice exists in the recipient’s SAP S/
4HANA system. In this case, no action is taken, and the document proceeds to
the next logical step.
Does not exist
The requestor mentioned on the supplier invoice does not exist in the recipient’s
SAP S/4HANA system. The exception Invalid Requestor ID (NPO) is raised,
and the invoice is automatically routed to the pre-configured agent depending
on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_203

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

26.4 Suspected Duplicate (NPO)

This specific business rule checks for a duplicate invoice based on specific fields
configured in the configuration. There can be two scenarios as described in the
following:

Not a duplicate
If the invoice is not a duplicate, no action is taken, and the document proceeds to
the next logical step.
Duplicate
If the invoice is a duplicate, the exception Suspected Duplicate (NPO) is raised,
and the work item is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_DUP

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

272 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.5. Non-PO Credit Memo Processing

26.5 Non-PO Credit Memo Processing

If this Business Rule is applied, an exception is always raised for an invoice where
the indicator Credit Memo is checked. Its purpose is to indicate that the incoming
invoice is a credit memo. Such invoices will be sent to a pre-defined agent for further
processing.

Technical Field CREDIT_MEMO will be checked. If this field of a NPO invoice is checked, the
information invoice is considered as a Credit Memo.

26.6 Derivation Rule - Non-PO Expense Type

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

Technical FM: /OPT/VIM_DETERMINE_PROC_209

information
Invoices of vendors who are maintained in the table /OPT/VIM_BL_UTLV (Utility
Vendors) with flag UTLITY_VEND_FLAG set to X shall always have the Expense Type UT
- Utility.

All invoices of other vendors shall have the Expense Type ST - Standard.

26.7 Invalid Vendor VAT Number (NPO)

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

Match
The supplier VAT/Tax number provided on the invoice matches with the VAT/
Tax number mentioned in the vendor master. In this case, no action is taken, and
the document proceeds to the next logical step.
Mismatch
The supplier VAT/Tax number provided on the invoice does not match with the
VAT/Tax number mentioned in the vendor master in SAP S/4HANA. The
exception Invalid Vendor VAT Number (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_120

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 273

Chapter 26 Business rules for NPO invoices

26.8 Incomplete Credit Memo (NPO)

When this business rule is applied, the credit memo should have the original
suppliers invoice number. Also, the original invoice number mentioned on the credit
memo must be present in the SAP S/4HANA system. There can be three scenarios as
described in the following:

Present and matching

The credit memo has the original invoice number. Further, there should be an
invoice in the SAP S/4HANA system (DP document or SAP document) that has
the original suppliers invoice number as the reference number. In this case, the
exception is not raised, and the document proceeds to the next logical step.
Not present
The credit memo does not have the original invoice number. The exception
Incomplete Credit Memo (NPO) is raised, and the invoice is automatically routed
to the pre-configured agent depending on the role for further action.
Mismatch
The credit memo has the original invoice number, and there is no invoice
existing in the SAP S/4HANA system (DP document or SAP document) that has
the original suppliers invoice number as the reference number. The exception
Incomplete Credit Memo (NPO) is raised, and the invoice is automatically routed
to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_121

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

26.9 Vendor Address Mismatch (NPO)

The Remit-To-Address (suppliers address to which the billing should happen)
should match with the SAP S/4HANA Vendor Master’s address as this is a required
information on the suppliers invoice. There can be two scenarios as described in the
following:

Match
The Remit-To-Address provided on the invoice matches with the address on the
vendor master. In this case, no action is taken, and the document proceeds to the
next logical step.
Mismatch
The Remit-To-Address does not match with the address on the vendor master.
The exception Vendor Address Mismatch (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

The following SAP S/4HANA vendor address fields are matched:

• House #

274 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.10. Missing Invoice Date (NPO)

• Street
• Postal Code
• City
• Region
• Country

Technical FM: /OPT/VIM_DETERMINE_PROC_122

information

26.10 Missing Invoice Date (NPO)

When this business rule is applied, the invoice date on the DP index document
header should have been entered. There can be two scenarios as described in the
following:

Entered
The invoice date is entered on the DP index document header. In this case, no
action is taken, and the document proceeds to the next logical step.
Not entered
The invoice date is not entered on the DP index document header. The exception
Missing Invoice Date (NPO) is raised, and the invoice is automatically routed to
the pre-configured agent depending on the role for further action.

Technical If field BLDAT of the indexing data is not filled -> Exception
information

26.11 Invalid Tax Info (NPO)

The supplier’s invoice should carry the total VAT amount and (or) the VAT %
indicating the VAT payable.

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

Tax information present and matching

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

Tax information present and not matching

The tax information entered on the DP document does not have corresponding
valid SAP tax information. The exception Invalid Tax Info (NPO) is raised, and

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 275

Chapter 26 Business rules for NPO invoices

the document is automatically routed to the pre-configured agent depending on

the role for further action.

Example: The VAT % mentioned on the invoice does not have a corresponding VAT tax
code in SAP S/4HANA.

Tax information not present

The tax information is not present on the invoice. The exception Invalid Tax
Info (NPO) is raised, and the document is automatically routed to the pre-
configured agent depending on the role for further action.

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

Technical FM: /OPT/VIM_DETERMINE_PROC_126

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

26.12 Invalid Recipient VAT Number (NPO)

Every country has its typical VAT structure. You find this information in the
Company Master Data. For some countries, the recipient’s VAT number is a
mandatory information for some kind of invoices (for example for intra-community
invoices or triangulation invoices).

When this business rule is applied, the recipient VAT number provided on the
invoice must match with the company’s VAT number provided in the company
code in SAP S/4HANA. The following scenarios can apply:

Match
The recipient’s VAT number provided on the invoice matches with the VAT
number mentioned in the company code information. In this case, no action is
taken, and the document proceeds to the next logical step.

Mismatch
The recipient’s VAT number provided on the invoice does not match with the
VAT number mentioned in the company code in SAP S/4HANA. The exception
Invalid Recipient VAT Number is raised, and the invoice is automatically routed
to the pre-configured agent depending on the role for further action.

Not present
If the recipient’s VAT number is not present on the invoice, the exception
Invalid Recipient VAT Number is raised, and the invoice is automatically routed
to the pre-configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_128

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

276 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.13. ISR Number Mismatch (NPO)

26.13 ISR Number Mismatch (NPO)

This business rule is specific for Switzerland. The supplier’s invoice should have the
ISR number on the invoice as this is a required information.

When this business rule is applied, the ISR number on the DP index document
header should be present and matching with the vendor master. The following
scenarios are possible:

ISR number present and matching

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

ISR number present and not matching

The exception ISR Number Mismatch (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

ISR number not present

If the ISR number is not mentioned on the invoice but the vendor master has it,
the exception ISR Number Mismatch (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_129

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

26.14 Payment Terms Mismatch (NPO)

The payment terms mentioned on the supplier’s invoice should match with the
payment terms configured in the SAP S/4HANA system. There can be two scenarios
as described in the following:

Match
The payment terms provided on the vendor’s invoice matches with the payment
terms mentioned in the vendor master in SAP S/4HANA. In this case, no action
is taken, and the document proceeds to the next logical step.

Mismatch
The payment terms provided on the vendor’s invoice does not match with the
payment terms maintained in the vendor master in SAP S/4HANA. The
exception Payment Terms Mismatch (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_130

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 277

Chapter 26 Business rules for NPO invoices

26.15 Missing Date of Supply (NPO)

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

Date of supply present

The date of supply on the vendor’s invoice is present. In this case, no action is
taken, and the document proceeds to the next logical step.
Date of supply not present
The date of supply on the vendor’s invoice is not present. In this case, the
exception Missing Date of Supply (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

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

26.16 Invalid Siret Number (NPO) (France)

This business rule is, for example, applied for France. The SIRET number provided
on the invoice is matched against the SIRET number maintained in the vendor
master. There can be two scenarios as described in the following:

Match
The SIRET number provided on the invoice matches with the SIRET number in
the vendor master. In this case, no action is taken, and the document proceeds to
the next logical step.
Mismatch
The SIRET number provided in the invoice does not match with the SIRET
number in the vendor master. The exception Invalid SIRET Number (NPO) is
raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_229

information
For more information, see “Invalid Siret Number (PO) (France)” on page 239

278 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.17. Invalid Company Address (NPO)

26.17 Invalid Company Address (NPO)

The recipient address provided on the invoice should match with the SAP S/4HANA
company code’s address. There can be two scenarios as described in the following:

Match
The recipient address provided on the invoice matches with the company code
address. In this case, no action is taken, and the document proceeds to the next
logical step.
Mismatch
The recipient address does not match with the address of the company code.
The exception Invalid Company Address (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_132

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

26.18 Vendor Invoice Reference Missing (NPO)

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

Invoice number present

The invoice number on the vendor’s invoice is present. In this case, no action is
taken, and the document proceeds to the next logical step.
Invoice number not present
The invoice number on the vendor’s invoice is not present. In this case, the
exception Vendor Invoice Reference Number Missing (NPO) is raised, and the
invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical In the baseline, field XBLNR is set as Required field. That means the value of this field
information in the indexing data is checked. If it is empty -> exception

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 279

Chapter 26 Business rules for NPO invoices

26.19 Payment Method Mismatch (NPO)

The payment method mentioned on the supplier’s invoice should match with the
payment method configured in the SAP S/4HANA system. There can be two
scenarios as described in the following:

Match
The payment method provided on the vendor’s invoice matches with the
payment method mentioned in the vendor master in SAP S/4HANA. In this
case, no action is taken, and the document proceeds to the next logical step.
Mismatch
The payment method provided on the vendor’s invoice does not match with the
payment method maintained in the vendor master in SAP S/4HANA. The
exception Payment Method Mismatch (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_134

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

26.20 Determine Expense Type

This Business Rule is used to derive the Expense Type if this field is not delivered.
There are 3 types of Expense Types:

PA
Pre-approved. This Expense Type is delivered from OCR.
UT
Utility invoices from vendors that match the predefined Utility Vendors.
ST
Standard for other invoices.

The FM checks the vendor in the invoice against the vendors maintained in table /
OPT/VIM_BL_UTLV. If the vendor is maintained as Utility Vendor, the Expense Type is
set to UT. Otherwise the Expense Type is set to ST.

Technical FM: /OPT/VIM_DETERMINE_PROC_209

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

280 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.21. Missing/Invalid Tax Exempt Text (NPO)

26.21 Missing/Invalid Tax Exempt Text (NPO)

The exception is raised in the following cases:

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

Technical FM: /OPT/VIM_DETERMINE_PROC_135

information

26.22 Missing Import Special Text (NPO)

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

Special text present

The special text on the vendors invoice indicating tax exemption is present. In
this case, no action is taken, and the document proceeds to the next logical step.
Special text not present
The special text on the vendor’s invoice indicating tax exemption is not present.
In this case, the exception Missing Import Special Text (NPO) is raised, and the
invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_136

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

26.23 Missing Item Description (NPO)

The invoices received (for example by Switzerland companies) from suppliers
should have the item description on the invoice for each item supplied. There can be
two scenarios as described in the following:

Item description present

The item description on the vendor’s invoice is present. In this case, no action is
taken, and the document proceeds to the next logical step.
Item description not present
The item description on the vendor’s invoice is not present. In this case, the
exception Missing Item Description (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for
further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_137

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 281

Chapter 26 Business rules for NPO invoices

26.24 Missing Mandatory Information (NPO)

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

Field value entered in mandatory field

In this case, no action is taken, and the document proceeds to the next logical
step.
Field value not entered in mandatory field
In this case, the exception Missing Mandatory Information (NPO) is raised, and
the invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_138

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

26.25 Missing/Invalid Triangulation Text (NPO)

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

Triangulation text present

The special text on the vendors invoice indicating triangulation is present. In this
case, no action is taken, and the document proceeds to the next logical step.
Triangulation text not present
The special text on the vendor’s invoice indicating triangulation is not present.
In this case, the exception Missing/Invalid Triangulation Text (NPO) is raised,
and the invoice is automatically routed to the pre-configured agent depending
on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_139

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

282 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.26. Invalid Sales Tax For The Region (NPO)

26.26 Invalid Sales Tax For The Region (NPO)

When this business rule is applied, the ship-to address region, tax type, and tax rate
mentioned on the invoice are matched against the allowed tax type and the tax rates
for that region in OpenText VIM for SAP. In case of any deviations, the exception
Invalid Sales for the Region (NPO) is raised, and the invoice is routed to the pre-
configured agent depending on the role for further action. There are many scenarios
that can arise depending on the configuration. Some of the possible scenarios are
described in the following:

Information matching
The ship-to region, tax types entered on the DP document matches with the
configured SAP S/4HANA tax type for that region. The document proceeds to
the next logical step.

Example: For region Ontario, the tax type GST is supplied, and the tax type GST is
configured in SAP S/4HANA for that region.

Information not matching

The ship-to region and tax types entered on the DP document do not have a
corresponding valid configured SAP S/4HANA tax type for that region. The
exception Invalid Sales Tax for the Region (NPO) is raised, and the document
is automatically routed to the pre-configured agent depending on the role for
further action.

Example: For region Ontario, the tax type GST is supplied, and the tax type configured
in SAP S/4HANA is PST for that region.

Information not present

The ship-to region information is not present on the invoice. Depending on the
configuration option:
Default Region
Set company code address as ship-to region and proceed with the above
scenarios. You can configure this derivation of the ship-to region on
OpenText VIM for SAP side.

Blank
Keep the not present information as blank and raise exception Invalid Sales
Tax for the Region (NPO). The document is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM: /OPT/VIM_CHECK_TAX_RATE

information
For more information, see “Invalid Sales Tax for the Region (PO)” on page 244.

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 283

Chapter 26 Business rules for NPO invoices

26.27 Non PO Approval Required (NPO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_250

information
The Expense Type given in the invoice is checked against table /ORS/EXPENSE_TYP to
determine whether Approval is required for this expense type. If Approval is
required, the exception is raised. A work item is created and forwarded to the
requester given in the invoice.

Customization Run transaction /n/OPT/SPRO and navigate to OpenText Vendor Invoice

point Management Invoice Solution > Invoice Approval Configuration > Approval
Workflow > Setup Approval Chain > Maintain Expense Types.

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

26.28 Vendor Audit Required (NPO)

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

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

Technical FM: /OPT/VIM_DETERMINE_PROC_151

information
Customization point

• Run the /OPT/VIM_BL_VAUD transaction or

• run the /n/OPT/VIM transaction and navigate to OpenText VIM - Invoice
Solution > SAP menu > Customization > Vendor Audit List Configuration.

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

284 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.29. Tax Audit Required (NPO)

26.29 Tax Audit Required (NPO)

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

No tax audit required

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

Technical FM: /OPT/VIM_DETERMINE_PROC_258

information
The configuration maintained in table /OPT/VIM_BL_NPTX is checked. If the company
code, the G/L account number, and the vendor number on the invoice are
maintained in the table with the Active flag set, the exception Tax Audit Required
(NPO) is raised.

The wildcard in all columns means “All”.

Customization Run the /OPT/VIM_BL_NPTX transaction. Alternatively, run the /n/OPT/VIM

point transaction and navigate to OpenText VIM - Invoice Solution > SAP menu >
Customization > Tax Audit Configuration for PO Invoices.

26.30 Validate Bank Details (NPO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_270

information
For more information, see “Validate Bank Details (PO)” on page 255.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 285

Chapter 26 Business rules for NPO invoices

26.31 Validate Accounting Data (NPO)

When the business rule is applied, header and accounting data are validated. The
validation done here is the same as the validation done in the approval screen when
an invoice is approved. If an error occurs, error messages are added to the log table,
and the exception Validate Accounting Data (NPO) is raised. A work item is created
and routed to the pre-configured agent for further action.

To use this business rule, you must maintain and activate the new process type 271
in the document type configuration, navigating to /OPT/SPRO > OpenText Vendor
Invoice Management Invoice Solution > Document Processing Configuration >
Document Type Configuration > Maintain Document Types. For background
information, see Section 8.1.2 “Defining process types” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).

In the Baseline configuration, the process type is not characteristic specific (the
Characteristic Check check box is not set). Therefore, you do not have to maintain
the process type for characteristic.

In the document type configuration, Sequence Steps, use the function module /OPT/
VIM_DETERMINE_PROC_450 as Check Function for DP Document Type NPO_S4, Step
ID 418. For background information, see Section [Link] “Defining sequence steps” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).

In the Baseline configuration, the business rule is added to the document type
NPO_S4 but it is not activated.

Technical FM: /OPT/VIM_DETERMINE_PROC_450

information

26.32 Invalid Payment Reference (NPO)

Payment reference check is used in Norway, Sweden and Finland. The business rule
checks the payment reference using the SAP S/4HANA function module FI_PAYREF_
CHECK.

If the check fails, the exception Invalid Payment Reference (NPO) is raised, and the
invoice is automatically routed to the pre-configured agent depending on the role
for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_176

information

286 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.33. Missing Invoice Code (NPO)

26.33 Missing Invoice Code (NPO)

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

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

26.34 Invalid Invoice Code Format (NPO)

If the Invoice Code (INVOICE_CODE) field length is not equal to 10 or 12, the
exception Invalid Invoice Code Format (NPO) is raised.

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

Technical FM: /OPT/VIM_DETERMINE_PROC_112

information

26.35 Invalid Characters in Secret Code (NPO)

The Secret Code (SECRET_CODE1, SECRET_CODE2, SECRET_CODE3,
SECRET_CODE4) field value may contain only the following characters:

• Digits from 0 to 9
• Characters like +, /, <, >, -, and *

Otherwise, the exception Invalid Characters in Secret Code (NPO) is raised, and
the invoice is automatically routed to the pre-configured agent depending on the
role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_114

information

26.36 Invoice Older than Allowed (NPO)

If the difference of system date and invoice date is greater than the number of days
mentioned in the Z constant 005 / INVOICE_DAYS_OLD, the exception Invoice Older
than Allowed (NPO) is raised, and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_116

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 287

Chapter 26 Business rules for NPO invoices

26.37 Invalid Vendor Invoice Number (NPO)

The vendor reference value (XBLNR) length must be 8. If this is not the case, the
exception Invalid Vendor Invoice Number (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_117

information

26.38 Invalid Common Ordinary Invoice (VAT Exists)

(NPO)
If the invoice category is Non VAT (N) and a VAT amount (VAT_AMOUNT) exists,
the exception Invalid Common Ordinary Invoice (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_118

information

26.39 Check Hand Written (NPO)

If the gross amount is greater than 100000 and the Not hand written
(NOT_HAND_WRITTEN) check box is not selected, the exception Check Hand
Written (NPO) is raised, and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_119

information

26.40 Verification Required (NPO)

If the AFTCS_VALIDATION field is empty, the exception Verification Required (NPO)
is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_141

information

26.41 Invalid/Missing Vendor ABN Number (NPO)

If the vendor VAT number (VENDOR_VAT_NO) field is empty, or if the vendor VAT
number (VENDOR_VAT_NO) is not matching with the vendor master data, the exception
Invalid/Missing Vendor ABN Number (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_172

information

288 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.42. Invalid/Missing Recipient ABN Number (NPO)

26.42 Invalid/Missing Recipient ABN Number (NPO)

If the recipient VAT number (RECIPIENT_VAT_NO) field is empty, or if the recipient
VAT number (RECIPIENT_VAT_NO) is not matching with company code master data,
the exception Invalid/Missing Recipient ABN Number (NPO) is raised, and the
invoice is automatically routed to the pre-configured agent depending on the role
for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_173

information

26.43 Missing Vendor Name (NPO)

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

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

26.44 Missing Recipient Name (NPO)

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

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

26.45 Invalid Tax Description (NPO)

This business rule is specific to India. If the vendor belongs to India and the Tax
Description (TAX_DESC) field is empty, the exception Invalid Tax Description
(NPO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_190

information

26.46 Missing Vendor PAN Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the PAN
Number (PAN_NO) field value is empty, the exception Missing Vendor PAN Number
(NPO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_185

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 289

Chapter 26 Business rules for NPO invoices

26.47 Mismatch Vendor PAN Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the PAN
Number (PAN_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor PAN Number (NPO) is raised and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_186

information

26.48 Missing Vendor STC Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the STC
Number (STC_NO) field value is empty, the exception Missing Vendor STC Number
(NPO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_187

information

26.49 Mismatch Vendor STC Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the STC
Number (STC_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor STC Number (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_188

information

26.50 Missing Vendor CST Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the CST
Number (CST_NO) field value is empty, the exception Missing Vendor CST Number
(NPO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_179

information

290 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.51. Mismatch Vendor CST Number (NPO)

26.51 Mismatch Vendor CST Number (NPO)

This business rule is specific to India. If the vendor belongs to India, and the CST
Number (CST_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor CST Number (NPO) is raised and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_180

information

26.52 Missing Vendor TIN/TOT Number (NPO)

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

Technical FM: /OPT/VIM_DETERMINE_PROC_181

information

26.53 Mismatch Vendor TIN/TOT Number (NPO)

This business rule is specific to India. If the vendor belongs to India, and the TIN/
TOT Number (TIN_TOT) field value does not match with the vendor master data, the
exception Mismatch Vendor TIN/TOT Number (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_182

information

26.54 Missing Vendor LST Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the LST
Number (LST_NO) field value is empty, the exception Missing Vendor LST Number
(NPO) is raised, and the invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_183

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 291

Chapter 26 Business rules for NPO invoices

26.55 Mismatch Vendor LST Number (NPO)

This business rule is specific to India. If the vendor belongs to India and the LST
Number (LST_NO) field value does not match with the vendor master data, the
exception Mismatch Vendor LST Number (NPO) is raised, and the invoice is
automatically routed to the pre-configured agent depending on the role for further
action.

Technical FM: /OPT/VIM_DETERMINE_PROC_184

information

26.56 SCB Indicator / Supplying Country Missing

(NPO)
This business rule checks if the SCB Indicator (field SCB_IND) and Supplying
Country (field SUPCOUNTRY) has been entered.

Technical The rule needs to be activated for relevant countries in the Country/Characteristic-
Information specific settings for foreign vendors. There is no function module used, the check is
achieved using configuration only.

26.57 Check BPF Added Data (NPO)

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

Technical FM: /OPT/VIM_DETERMINE_BPF_VALID

information

26.58 Missing VAT Date (NPO)

This business rule checks if the VAT date is provided in the DP document. If not, the
DP processing stops with an exception. Users are required to enter the VAT date in
the DP document. To enable the check, add the respective process type for DP
document or characteristic, with the function /OPT/VIM_DETERMINE_PROC_407.

The baseline configuration of this business rule contains predefined process options.
You can adjust the process options list to suit your scenarios.

Technical FM: /OPT/VIM_DETERMINE_PROC_407

information

292 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.59. Check Withholding Tax Data (NPO)

26.59 Check Withholding Tax Data (NPO)

This business rule is valid for documents that are subject to withholding tax. If the
withholding tax checked flag is not filled, the exception is raised.

Technical FM: /OPT/VIM_DETERMINE_PROC_415

information

26.60 Missing/Invalid GST Partner (NPO)

This business rule is specific to India for NPO invoices.

If the vendor on the invoice belongs to India and if the GST Partner (GST_PART)
field value is empty or not maintained in vendor master, then this exception is
raised. The invoice is automatically routed to the pre-configured agent depending
on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_IN_420

information

26.61 Missing/Invalid Vendor GST Reg. No (NPO)

This business rule is specific to India for NPO invoices.

If the GST Registration Number (GST_REG_NUM) field value is empty or not

matching against tax number 3 (STCD3) of the GST Partner’s vendor master, then this
exception is raised. The invoice is automatically routed to the pre-configured agent
depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_IN_422

information

26.62 Missing/Invalid HSN/SAC code (NPO)

This business rule is specific to India for NPO invoices (Material based).

If one of the following conditions applies:

• HSN/SAC code is empty on NPO invoice lines.

• Plant is empty on NPO invoice lines.

• HSN/SAC code on NPO invoice lines does not match with value of “control
code” (STEUC) on “Foreign trade export” view of material master (MARC), of given
Material on NPO invoice lines.

Then this exception is raised and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_IN_424

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 293

Chapter 26 Business rules for NPO invoices

26.63 Missing/Invalid Receiving Location GST

Registration No (NPO)
This business rule is specific to India for NPO invoices.

The field value of the Receiving Entity GST Registration Number (REC_GST_REG_NUM)
might be empty. It also might not match against the GST Registration Number
(GSTIN) of the combination of the receiving company code / business place.

In these cases, this exception is raised. The invoice is automatically routed to the pre-
configured agent depending on the role for further action.

Technical FM: /OPT/VIM_DETERMINE_PROC_IN_428

information
The function module is shared with the corresponding PO business rule. See
“Missing/Invalid Receiving Location GST Registration No (PO)” on page 266.

Table: J_1BBRANCH / field: GSTIN

26.64 Missing Company Code (NPO)

This rule checks if the company code (field BUKRS) has been filled. To use this
business rule, the BUKRS field must be configured as required field.

26.65 Missing Gross Amount (NPO)

This rule checks if the gross amount (field GROSS_AMOUNT) has been filled. To use this
business rule, the GROSS_AMOUNT field must be configured as required field.

26.66 PO Data Exists (NPO)

This rule checks if there is PO data in the Non PO process to give the user a hint for
an eventual Document Type Change.

Technical FM: /OPT/VIM_DETERMINE_PROC_435

information

26.67 Invoice subject for payment split (NPO)

This business rule is specific for Poland. It checks if the Splitpayment flag is passed
from OCR and routes the invoice to a user for manual action.

Technical FM: /OPT/VIM_DET_PROC_SPLITPAYMENT

information

294 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 26.68. Missing UUID Number (NPO)

26.68 Missing UUID Number (NPO)

If the company code is related to Mexico, the system checks whether the Mexico
UUID field is empty or not. If it is empty, the system raises the exception. If it
contains any value, the system proceeds to check the next exception.

Technical FM: /OPT/VIM_DET_PROC_MX_UUID

information

26.69 Validate Changes on Advanced Tax data (NPO)

This rule checks any tax related information change during coding approval.
Configure it after the Approval Required(NPO) Business Rule. It lets you check and
confirm the advanced tax table control changes before posting the DP invoices.

Technical FM : /OPT/VIM_DETERMINE_PROC_IN_429
information

26.70 Missing/Invalid Invoice Reference Number (NPO)

This exception is raised when the invoice reference number (IRN) on the invoice for
Indian company codes is not provided or if it has a length different from 64
characters.

Technical FM: /OPT/VIM_DETERMINE_PROC_452

information

26.71 Portugal - Missing QR Code/ATCUD (NPO)

This exception is raised if the ATCUD is not populated.

Technical Field INV_REF_NUM is marked as a required field in the Sequence Steps under the
information Document Type Definition configuration.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 295

Chapter 27
Business rules for Transportation Management
invoices

27.1 General business rules for TM invoices

The baseline configuration delivers several business rules for Transportation
Management (TM) invoices. The business rules are assigned process type numbers
from 550 to 569. They are implemented in the same way as NPO and PO business
rules with matching process type text.

Additional process types are implemented with a range from 580 to 600.

27.1.1 Invalid Freight Order/Freight Booking (TM)

This business rule is triggered when the Invalid Freight Order/Freight Booking
field is filled in the indexing screen.

Technical Class: /OPT/VIM_CL_API_DET_PROC_580

information

27.1.2 Invalid House Bill of Lading (TM)

This business rule is triggered when the Invalid House Bill of Lading field is filled
in the indexing screen.

Technical Class: /OPT/VIM_CL_API_DET_PROC_581

information

27.1.3 Invalid Air Waybill (TM)

This business rule is triggered when the Invalid Air Waybill field is filled in the
indexing screen.

Technical Class: /OPT/VIM_CL_API_DET_PROC_582

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 297

Chapter 27 Business rules for Transportation Management invoices

27.1.4 Invalid Freight Settlement Document (TM)

This business rule is triggered when the Invalid Freight Settlement Document
(FSD) field is filled in the indexing screen. It is also triggered if the FSD does not
have a follow-on document (Service Entry Sheet, SES).

Technical Class: /OPT/VIM_CL_API_DET_PROC_583

information

27.1.5 FSD not Done (TM)

This business rule is triggered when the FSD is not created for the respective Freight
Order/Freight Booking.

Technical Class: /OPT/VIM_CL_API_DET_PROC_590

information

27.1.6 SES not Done (TM)

This business rule is triggered when the Service Entry Sheet (SES) is not created for
the respective FSD.

Technical Class: /OPT/VIM_CL_API_DET_PROC_591

information

27.1.7 Validate TM data (TM)

This business rule is triggered when incomplete details are provided in the indexing
screen while processing a TM invoice or a mismatch of corresponding TM
documents is filled in the indexing screen.

Technical Class: /OPT/VIM_CL_API_DET_PROC_600

information

27.2 Check for Transportation Management PO

This specific business rule checks if any of the POs provided in the DP document are
Transportation Management POs. The following scenarios are possible:

POs not relevant for Transportation Management (TM)

No exception is triggered. The invoice document proceeds to the next logical
step.
PO relevant for TM
Business rule Check for Transportation Management PO is triggered if the POs in
the DP document are found in Purchase Order Header (EKKO) with status = T.
The work item is routed to the preconfigured agent for further action.

Technical FM /OPT/VIM_DETERMINE_PROC_437
Information
When the business rule is triggered, the Transportation Management PO can be
posted using Online PO posting process option 2009 Post PO Invoice. In the current
version, only a single TM PO can be processed.

298 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 28
General business rules

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

28.1 Check Data after Restart

If the DP process was started using the process option Delete and Restart, the DP
process will run into this exception. The user can verify or add the index data of the
new DP process and can continue the DP process.

28.2 Check Inbound Interface Errors

This exception is triggered if there were recoverable errors detected in the inbound
interface for the given document. The processor is supposed to review the errors, by
clicking the Display Errors button in the DP dashboard. For the DP process to
continue, the errors must be confirmed by clicking the option button configured for
the process option 2025 (Confirm Errors).

Note: As of version 7.0 SP3, only the Ariba inbound interface triggers this.

Technical FM: /OPT/VIM_DETERMINE_PROC_IDHERR

information

28.3 Copy rule: Supply Date to VAT Date

You can enter the VAT Date field during indexing in the DP indexing screen. In
many cases, the value of the supply date, which already exists in OpenText VIM for
SAP, can be assigned to the VAT date.

This business rule copies the supply date value into the VAT date. This is not a
dialog process type: it does not trigger an exception. The same process type has to be
used for both PO and NPO invoices. You can enable it for individual document
types or using characteristics.

Technical FM: /OPT/VIM_DETERMINE_PROC_409

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 299

Chapter 28 General business rules

28.4 Invalid QR Bill data

When processing Swiss QR Bills, invoice data can be checked for consistency. This
business rule checks the following fields:

• IBAN (QR IBAN or generic)

• Partner bank type
• ISR reference
• QR Reference (ESRRE) and Payment Reference (KIDNO)
• QR Structured Information
• QR Unstructured Information

Use the same process type for both PO and Non PO invoices. You can enable the
process type for individual document types or using characteristics. In standard
configuration, the process type is enabled in the characteristic specific process types
for Switzerland only.

Technical FM: /OPT/VIM_DETERMINE_PROC_438

information

28.5 Check maximum exchange rate difference

This business rule checks for maximum exchange rate difference in PO and NPO
invoices that have currency differing from company code currency. It follows the
standard SAP check leading to the SAP message F5 212 (Exchange rate X deviates
from table rate Y by Z %). The configuration of the SAP message (transaction OBA5)
is not checked. Use the OpenText VIM for SAP document type configuration to
enable and disable the check. This business rule is included into the standard
configuration as process type 439.

Technical FM: /OPT/VIM_DETERMINE_PROC_439

information

300 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 29

Summary tables

29.1 Table: Business rules for PO invoices

Index Business rule Function Module Version[a]
100 Process PO Invoice (PO) No FM required 5.2
/OPT/
101 Invalid PO Number (PO) 5.2
VIM_DETERMINE_PROC_101
Field LIFNR will be checked
102 Invalid Vendor (PO) 5.2
against SAP table LFA1
/OPT/
103 Invalid UOM (PO) 5.2
VIM_DETERMINE_PROC_103
Field WAERS will be checked
104 Invalid Currency (PO) 5.2
against SAP table TCURC
/OPT/
105 Suspected Duplicate (PO) 5.2
VIM_DETERMINE_PROC_DUP
/OPT/
106 PO Is Not Released (PO) 5.2
VIM_DETERMINE_PROC_106
/OPT/
107 Unable to Match PO Lines (PO) 5.2
VIM_DETERMINE_PROC_107
108 Process PO Invoice (PO) OCR No FM required 5.2
Unable to Determine PO Line /OPT/
109 5.2
Number (PO) VIM_DETERMINE_PROC_POL
Manual Check Needed for
110 /OPT/VIM_LINES_DERIVE_PO 5.2
Indexing Lines (PO)
/OPT/
111 Missing invoice code (PO) 6.0
VIM_DETERMINE_PROC_111
/OPT/
112 Invalid invoice code format (PO) 6.0
VIM_DETERMINE_PROC_112
Manual Check Needed / Missing /OPT/
113 7.5
Data for Indexing Lines (PO) VIM_DETERMINE_PROC_108
Invalid characters in Secret code /OPT/
114 6.0
(PO) VIM_DETERMINE_PROC_114
Invalid PO item number (PO) /OPT/
115 VIM_DETERMINE_PROC_ITEM 7.0 SP3
S
/OPT/
116 Invoice older than allowed (PO) 6.0
VIM_DETERMINE_PROC_116

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 301

Chapter 29 Summary tables

Index Business rule Function Module Version[a]

Invalid vendor invoice number /OPT/
117 6.0
(PO) VIM_DETERMINE_PROC_117
Invalid common ordinary invoice /OPT/
118 6.0
(VAT Exists) (PO) VIM_DETERMINE_PROC_118
/OPT/
119 Check hand written invoice (PO) 6.0
VIM_DETERMINE_PROC_119
Invalid Vendor VAT Number /OPT/
120 5.2
(PO) VIM_DETERMINE_PROC_120
/OPT/
121 Incomplete Credit Memo (PO) 5.2
VIM_DETERMINE_PROC_121
/OPT/
122 Vendor Address Mismatch (PO) 5.2
VIM_DETERMINE_PROC_122
/OPT/
123 Missing Item Quantity (PO) 5.2
VIM_DETERMINE_PROC_123
125 Missing Invoice Date (PO) Field BLDAT must be filled 5.2
/OPT/
126 Invalid Tax Info (PO) 5.2
VIM_DETERMINE_PROC_126
Field SUPPLY_DATE must be
127 Missing Date of Supply (PO) 5.2
filled
Invalid Recipient VAT Number /OPT/
128 5.2
(PO) VIM_DETERMINE_PROC_128
/OPT/
129 ISR Number Mismatch (PO) 5.2
VIM_DETERMINE_PROC_129
/OPT/
130 Payment Terms Mismatch (PO) 5.2
VIM_DETERMINE_PROC_130
/OPT/
131 Invalid Siret Number (PO) 5.2
VIM_DETERMINE_PROC_229
/OPT/
132 Invalid Company Address (PO) 5.2
VIM_DETERMINE_PROC_132
Vendor Invoice Reference
133 Field XBLNR must be filled. 5.2
Missing (PO)
/OPT/
134 Payment Method Mismatch (PO) 5.2
VIM_DETERMINE_PROC_134
Missing/Invalid Tax exempt Text /OPT/
135 5.2
(PO) VIM_DETERMINE_PROC_135
/OPT/
136 Missing Import Special Text (PO) 5.2
VIM_DETERMINE_PROC_136
/OPT/
137 Missing Item Description (PO) 5.2
VIM_DETERMINE_PROC_137

302 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 29.1. Table: Business rules for PO invoices

Index Business rule Function Module Version[a]

Missing Mandatory Information /OPT/
138 5.2
(PO) VIM_DETERMINE_PROC_138
Missing/Invalid Triangulation /OPT/
139 5.2
Text (PO) VIM_DETERMINE_PROC_139
Invalid Sales Tax for the Region
140 OPT/VIM_CHECK_TAX_RATE 6.0
(PO)
/OPT/
141 Verification required (PO) 6.0
VIM_DETERMINE_PROC_141
142 Check Data After Restart No FM required 5.2
/OPT/
145 Invalid Tax Description (PO) 6.0
VIM_DETERMINE_PROC_190
Not necessary – triggered via
149 Posted Approval Required (PO) 5.2
PAS
/OPT/
150 Approval Required (PO) 5.2
VIM_DETERMINE_PROC_150
/OPT/
151 Vendor Audit Required (PO) 5.2
VIM_DETERMINE_PROC_151
/OPT/
153 Vendor Mismatch (PO) 5.2
VIM_DETERMINE_PROC_153
/OPT/
154 Service Entry Required (PO) 5.2
VIM_DETERMINE_PROC_154
/OPT/
155 Currency Mismatch (PO) 5.2
VIM_DETERMINE_PROC_155
/OPT/
156 Unit of Measure Mismatch (PO) 5.2
VIM_DETERMINE_PROC_156
/OPT/
157 Freight on Invoice (PO) 5.2
VIM_DETERMINE_PROC_157
/OPT/
158 Tax Audit Required (PO) 5.2
VIM_DETERMINE_PROC_158
/OPT/
159 Invalid Requisitioner (PO) 5.2
VIM_DETERMINE_PROC_303
Field CREDIT_MEMO will be
160 PO Credit Memo Processing (PO) 5.2
checked.
/OPT/
161 Company Code Mismatch (PO) 5.2
VIM_DETERMINE_PROC_161
Confirmation required from SRM /OPT/
162 5.2
(PO)(deprecated) VIM_DETERMINE_PROC_162
/OPT/
163 GR Not Done - Simple Check 6.0
VIM_DETERMINE_PROC_189

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 303

Chapter 29 Summary tables

Index Business rule Function Module Version[a]

/OPT/
164 Wait for GR - Simple Check (PO) 7.0
VIM_DETERMINE_PROC_164
Wait for GR - Enhanced Check /OPT/
165 7.0
(PO) VIM_DETERMINE_PROC_165
Service Entry Required (PO) - /OPT/
166 7.5 SP5
Enhanced Check VIM_DETERMINE_PROC_159
/OPT/
170 Validate Bank Details (PO) 7.0
VIM_DETERMINE_PROC_270
Invalid/Missing Vendor ABN /OPT/
172 6.0
Number (PO) VIM_DETERMINE_PROC_172
Invalid/Missing Recipients ABN /OPT/
173 6.0
Number(PO) VIM_DETERMINE_PROC_173
174 Missing Vendor Name(PO) Configuration 6.0
175 Missing Recipients Name(PO) Configuration 6.0
/OPT/
176 Invalid Payment Reference (PO) 5.2
VIM_DETERMINE_PROC_176
Missing Vendor ECC /OPT/
177 6.0
Number(PO) VIM_DETERMINE_PROC_177
Mismatch Vendor ECC /OPT/
178 6.0
Number(PO) VIM_DETERMINE_PROC_178
Missing Vendor CST /OPT/
179 6.0
Number(PO) VIM_DETERMINE_PROC_179
Mismatch Vendor CST /OPT/
180 6.0
Number(PO) VIM_DETERMINE_PROC_180
Missing Vendor TIN/TOT /OPT/
181 6.0
Number(PO) VIM_DETERMINE_PROC_181
Mismatch Vendor TIN/TOT /OPT/
182 6.0
Number(PO) VIM_DETERMINE_PROC_182
Missing Vendor LST /OPT/
183 6.0
Number(PO) VIM_DETERMINE_PROC_183
Mismatch Vendor LST /OPT/
184 6.0
Number(PO) VIM_DETERMINE_PROC_184
Missing Vendor PAN /OPT/
185 6.0
Number(PO) VIM_DETERMINE_PROC_185
Mismatch Vendor PAN /OPT/
186 6.0
Number(PO) VIM_DETERMINE_PROC_186
Missing Vendor STC /OPT/
187 6.0
Number(PO) VIM_DETERMINE_PROC_187
Mismatch Vendor STC /OPT/
188 6.0
Number(PO) VIM_DETERMINE_PROC_188

304 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 29.1. Table: Business rules for PO invoices

Index Business rule Function Module Version[a]

SCB Indicator / Supplying No function module used,
190 16.3.1
Country Missing (PO) configuration only.
/OPT/
191 Missing NF Data (PO) 7.0
VIM_DETERMINE_PROC_191
/OPT/
192 Missing NF Customizing (PO) 7.0
VIM_DETERMINE_PROC_192
/OPT/
193 NF validation check failed (PO) 7.0
VIM_DETERMINE_PROC_193
Brazil – Wait for GR – Simple /OPT/
194 7.0
Check (PO) VIM_DETERMINE_PROC_194
Brazil – Wait for GR – Enhanced /OPT/
195 7.0
Check (PO) VIM_DETERMINE_PROC_195
Russia – Wait for TORG-12/ACT /OPT/
196 7.0
– Simple Check (PO) VIM_DETERMINE_PROC_196
Russia – Wait for TORG-12/ACT /OPT/
197 7.0
– Enhanced Check (PO) VIM_DETERMINE_PROC_197
Russia – Original Invoice /OPT/
198 7.0
Mismatch (PO) VIM_DETERMINE_PROC_198
Invalid Withholding Tax Code / /OPT/
401 7.0
Type (PO) VIM_DETERMINE_PROC_401
Withholding Tax Amount Bigger /OPT/
402 7.0
than Total Net Amount VIM_DETERMINE_PROC_402
/OPT/
405 Check BPF Added Data (PO) 7.5
VIM_DETERMINE_BPF_VALID
/OPT/
406 Tolerance Exceeded (PO) 7.5
VIM_DETERMINE_PROC_406
/OPT/
408 Missing VAT Date (PO) 7.0 SP4
VIM_DETERMINE_PROC_407
Check Withholding Tax Data /OPT/
415 7.0 SP6
(PO) VIM_DETERMINE_PROC_415
/OPT/
416 Down Payment Clearing (PO) VIM_DETERMINE_PROC_DWN 7.5 SP5
CLR
Quantity/Price Confirmation /OPT/
417 7.5 SP6
Required (PO) VIM_DETERMINE_PROC_417
/OPT/
418 Quantity/Price Mismatch (PO) 7.5 SP6
VIM_DETERMINE_PROC_418
/OPT/
Missing/Invalid GST Partner
419 VIM_DETERMINE_PROC_IN_4 7.5 SP6
(PO)
19

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 305

Chapter 29 Summary tables

Index Business rule Function Module Version[a]

/OPT/
Missing/Invalid Vendor GST
421 VIM_DETERMINE_PROC_IN_4 7.5 SP6
Reg. No (PO)
21
/OPT/
Missing/Invalid HSN/SAC code
423 VIM_DETERMINE_PROC_IN_4 7.5 SP6
(PO)
23
Missing/Invalid Receiving /OPT/
428 Location GST Registration No VIM_DETERMINE_PROC_IN_4 16.3.1
(PO) 28
Cannot Verify Quantity/Price /OPT/
425 7.5 SP6
Exceptions (PO) VIM_DETERMINE_PROC_425
/OPT/
436 Check for Reduction Invoice 16.3.1
VIM_DETERMINE_PROC_428
/OPT/
430 Missing Company Code (PO) 16.3
VIM_DETERMINE_PROC_430
/OPT/
432 Missing Gross Amount (PO) 16.3
VIM_DETERMINE_PROC_432
Check Vendor/Company /OPT/
434 16.3
Address VIM_DETERMINE_PROC_434
/OPT/
437 Check for Transport Order PO 16.3.3
VIM_DETERMINE_PROC_437
Missing/Invalid Invoice /OPT/
510 20.4 SPS1
Reference Number (PO) VIM_DETERMINE_PROC_452
/OPT/
512 Missing UUID Number (PO) 20.4 SPS1
VIM_DET_PROC_MX_UUID
/OPT/
Invoice subject for payment split
514 VIM_DET_PROC_SPLITPAYME 20.4 SPS1
(PO)
NT
Missing lean services entry sheet /OPT/
516 20.4 SPS2
(PO) VIM_DETERMINE_PROC_516
Check lean services - invoice /OPT/
517 20.4 SPS2
amount vs GR amount (PO) VIM_DETERMINE_PROC_517
[a] OpenText VIM for SAP version that introduced the business rule.

306 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 29.2. Table: Business rules for NPO invoices

29.2 Table: Business rules for NPO invoices

Index Business rule Function Module Version[a]
200 Process Non-PO Invoice (NPO) Not necessary 5.2
/OPT/
201 Invalid Vendor (NPO) 5.2
VIM_DETERMINE_PROC_201
Field WAERS will be checked
202 Invalid Currency (NPO) 5.2
against SAP table TCURC
/OPT/
203 Invalid Requester ID (NPO) 5.2
VIM_DETERMINE_PROC_203
/OPT/
204 Suspected Duplicate (NPO) 5.2
VIM_DETERMINE_PROC_DUP
206 Non-PO Credit Memo Processing Check field CREDIT_MEMO 5.2
Process Non-PO Invoice (NPO)
207 Not necessary 5.2
OCR
Derivation Rule – Non PO – /OPT/
209 5.2
Expense Type VIM_DETERMINE_PROC_209
/OPT/
211 Missing invoice code (NPO) 6.0
VIM_DETERMINE_PROC_111
Invalid invoice code format /OPT/
212 6.0
(NPO) VIM_DETERMINE_PROC_112
Missing Secret Code (NPO) / /OPT/
213 6.0
Obsolete since version 7.0 VIM_DETERMINE_PROC_113
Invalid characters in Secret code /OPT/
214 6.0
(NPO) VIM_DETERMINE_PROC_114
Invoice older than allowed /OPT/
216 6.0
(NPO) VIM_DETERMINE_PROC_116
Invalid vendor invoice number /OPT/
217 6.0
(NPO) VIM_DETERMINE_PROC_117
Invalid common ordinary invoice /OPT/
218 6.0
(VAT Exists) (NPO) VIM_DETERMINE_PROC_118
Check hand written invoice /OPT/
219 6.0
(NPO) VIM_DETERMINE_PROC_119
Invalid Vendor VAT Number /OPT/
220 5.2
(NPO) VIM_DETERMINE_PROC_120
/OPT/
221 Incomplete Credit Memo (NPO) 5.2
VIM_DETERMINE_PROC_121
Vendor Address Mismatch /OPT/
222 5.2
(NPO) VIM_DETERMINE_PROC_122
223 Missing Invoice Date (NPO) Field BLDAT must be filled 5.2

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 307

Chapter 29 Summary tables

Index Business rule Function Module Version[a]

/OPT/
224 Invalid Tax Info (NPO) 5.2
VIM_DETERMINE_PROC_126
Invalid Recipient VAT Number /OPT/
225 5.2
(NPO) VIM_DETERMINE_PROC_128
Field SUPPLY_DATE must be
228 Missing Date of Supply (NPO) 5.2
filled
/OPT/
229 Invalid Siret Number (NPO) 5.2
VIM_DETERMINE_PROC_229
/OPT/
232 Invalid Company Address (NPO) 5.2
VIM_DETERMINE_PROC_132
Vendor Invoice Reference Field XBLNR is required to be
233 5.2
Missing (NPO) filled
Payment Method Mismatch /OPT/
234 5.2
(NPO) VIM_DETERMINE_PROC_134
Missing/Invalid Tax exempt Text /OPT/
235 5.2
(NPO) VIM_DETERMINE_PROC_135
Missing Import Special Text /OPT/
236 5.2
(NPO) VIM_DETERMINE_PROC_136
/OPT/
237 Missing Item description (NPO) 5.2
VIM_DETERMINE_PROC_137
Missing Mandatory Information /OPT/
238 5.2
(NPO) VIM_DETERMINE_PROC_138
Missing/Invalid Triangulation /OPT/
239 5.2
Text (NPO) VIM_DETERMINE_PROC_139
Invalid Sales Tax For the Region
240 /OPT/VIM_CHECK_TAX_RATE 5.2
(NPO)
/OPT/
241 Verification required (NPO) 6.0
VIM_DETERMINE_PROC_141
/OPT/
242 Check Data After Restart 5.2
VIM_DETERMINE_PROC_160
/OPT/
245 Invalid Tax Description (NPO) 6.0
VIM_DETERMINE_PROC_190
Posted Approval Required Not necessary – triggered via
249 5.2
(NPO) PAS
Non PO Approval Required /OPT/
250 5.2
(NPO) VIM_DETERMINE_PROC_250
/OPT/
253 Vendor Audit Required (NPO) 5.2
VIM_DETERMINE_PROC_151
/OPT/
254 Tax Audit Required (NPO) 5.2
VIM_DETERMINE_PROC_158

308 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 29.2. Table: Business rules for NPO invoices

Index Business rule Function Module Version[a]

Invalid/Missing Vendor ABN /OPT/
255 6.0
Number (NPO) VIM_DETERMINE_PROC_172
Invalid/Missing Recipients ABN /OPT/
256 6.0
Number(NPO) VIM_DETERMINE_PROC_173
257 Missing Vendor Name(NPO) Configuration 6.0
258 Missing Recipients Name(NPO) Configuration 6.0
/OPT/
270 Validate Bank Details (NPO) 7.0
VIM_DETERMINE_PROC_270
/ OPT/ VIM_ DETERMINE_ PROC_
271 Validate Accounting Data (NPO) 7.0 SP3
450

Invalid Payment Reference /OPT/

276 5.2
(NPO) VIM_DETERMINE_PROC_176
Missing Vendor PAN /OPT/
277 6.0
Number(NPO) VIM_DETERMINE_PROC_185
Mismatch Vendor PAN /OPT/
278 6.0
Number(NPO) VIM_DETERMINE_PROC_186
Missing Vendor STC /OPT/
279 6.0
Number(NPO) VIM_DETERMINE_PROC_187
Mismatch Vendor STC /OPT/
280 6.0
Number(NPO) VIM_DETERMINE_PROC_188
Missing Vendor CST /OPT/
281 6.0
Number(NPO) VIM_DETERMINE_PROC_179
Mismatch Vendor CST /OPT/
282 6.0
Number(NPO) VIM_DETERMINE_PROC_180
Missing Vendor TIN/TOT /OPT/
283 6.0
Number(NPO) VIM_DETERMINE_PROC_181
Mismatch Vendor TIN/TOT /OPT/
284 6.0
Number(NPO) VIM_DETERMINE_PROC_182
Missing Vendor LST /OPT/
285 6.0
Number(NPO) VIM_DETERMINE_PROC_183
Mismatch Vendor LST /OPT/
286 6.0
Number(NPO) VIM_DETERMINE_PROC_184
Check Withholding Tax Data /OPT/
289 7.0 SP6
(NPO) VIM_DETERMINE_PROC_415
SCB Indicator / Supplying No function module used,
290 16.3.1
Country Missing (NPO) configuration only.
/OPT/
404 Check BPF Added Data (NPO) 7.5
VIM_DETERMINE_BPF_VALID
/OPT/
407 Missing VAT Date (NPO) 7.0 SP4
VIM_DETERMINE_PROC_407

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 309

Chapter 29 Summary tables

Index Business rule Function Module Version[a]

/OPT/
Missing/Invalid GST Partner
420 VIM_DETERMINE_PROC_IN_4 7.5 SP6
(NPO)
20
/OPT/
Missing/Invalid Vendor GST
422 VIM_DETERMINE_PROC_IN_4 7.5 SP6
Reg. No (NPO)
22
/OPT/
Missing/Invalid HSN/SAC code
424 VIM_DETERMINE_PROC_IN_4 7.5 SP6
(NPO)
24
Missing/Invalid Receiving /OPT/
428 Location GST Registration No VIM_DETERMINE_PROC_IN_4 16.3.1
(NPO) 28
/OPT/
Validate Changes on Advanced
429 VIM_DETERMINE_PROC_IN_4 20.4 SPS3
Tax data (NPO)
29
/OPT/
431 Missing Company Code (NPO) 16.3
VIM_DETERMINE_PROC_431
/OPT/
433 Missing Gross Amount (NPO) 16.3
VIM_DETERMINE_PROC_433
/OPT/
435 PO Data exists (NPO) 16.3
VIM_DETERMINE_PROC_435
Missing/Invalid Invoice /OPT/
511 20.4 SP1
Reference Number (NPO) VIM_DETERMINE_PROC_452
/OPT/
513 Missing UUID Number (NPO) 20.4 SP1
VIM_DET_PROC_MX_UUID
/OPT/
Invoice subject for payment split
515 VIM_DET_PROC_SPLITPAYME 20.4 SP1
(NPO)
NT
[a] OpenText VIM for SAP version that introduced the business rule.

29.3 Table: General business rules

Index Business rule Function Module Version[a]
140 Check data after restart /OPT/ 5.2
VIM_DETERMINE_PROC_160
403 Check inbound interface errors /OPT/ 7.0 SP3
VIM_DETERMINE_PROC_IDHE
RR
409 Copy rule: Supply Date to VAT /OPT/ 7.0 SP4
Date VIM_DETERMINE_PROC_409
438 Invalid QR Bill data /OPT/ 20.4
VIM_DETERMINE_PROC_438

310 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 29.3. Table: General business rules

Index Business rule Function Module Version[a]

439 Check maximum exchange rate /OPT/ 20.4 SPS3
difference VIM_DETERMINE_PROC_439
[a] OpenText VIM for SAP version that introduced the business rule.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 311

Chapter 30
Customer library

Besides the business rules delivered along with baseline, you can create custom
business rules as well as implement custom function modules for your business
rules to meet your needs. OpenText delivers some function module templates that
you can configure or implement. The functions are example functions.

30.1 Check country consistency

This function checks whether the country assigned to the OpenText VIM for
SAP document type is equal to the corresponding country resulting from the entered
index data.

Technical FM: /OPT/VIM_DETERMINE_PROC_LIB001

information

30.2 Check balance

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

Vendor Specific You can define tolerance groups for each company code using the OMRX transaction.
Tolerance You can assign tolerance groups to each supplier (vendor) in the vendor master
record, using the XK03 transaction.

Tolerance in this case means acceptance, based on the total:

If the difference is within the tolerance range, the system automatically generates a
difference line on a neutral income/expense account for small differences. This
applies to invoices with debit/credit differences when posting the invoice.

Technical FM: /OPT/VIM_DETERMINE_PROC_LIB002

information

30.3 Check and update coding for auto coding

This function updates the coding data within the invoice item data according to the
auto coding configuration for NPO.

Technical FM: /OPT/VIM_DETERMINE_PROC_LIB003

information

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 313

Chapter 30 Customer library

30.4 General business rules template

The general business rules template contains the parameters that you can use to call
business rules.

Technical FM: /OPT/VIM_DETERMINE_PROC_TEMPLT

information
The item values stored in /OPT/VIM_1ITEM are currently not passed as a table.
Therefore, to be sure that the current field contents are checked in the simulation,
users must consider the following rules:

• They must confirm header fields, which is normally done by the ENTER key,
before they click the simulation button.
• They must save item fields, which is done by clicking SAVE or SUBMIT, before
they click the simulation button.

314 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Part 7
Logic modules
Part 7 Logic modules

The task of logic modules is to check whether data is missing for a document and to
add the data where possible. This data enrichment is mostly scheduled before the
business rules run. It can be useful to also trigger some logic modules at a later point
of time, for example if the user has entered data on the indexing screen and presses
Rerun Business Rules.

Business rule Check BPF Added Data (process types 404 and 405) has been added. It
“informs” the user that a logic module has added data to the document. Business
rules are intended to check document data whereas logic modules are intended to
also change document data.

316 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 31

General information about logic modules

The following categories of logic modules exist:

• Simple mapping (single fields)

• Mapping
• Changing data
• Deleting data

You can group logic modules into process IDs and schedule them to run at the
following points in time:

• at process start
• at rerun business rules
• at both (process start and rerun business rules)

The mapping modules are intended to run before the DP workflow is started. They
replace enhanced mapping functions.

Changing and deleting modules check data and modify if certain conditions are
fulfilled. Some of them are intended to run at process start, others during rerun
business rules.

For reasons of clarity, the modules are classified as:

• Global processing
• PO processing
• NPO processing
• Country specific

The baseline customizing contains preconfigured process IDs that you must map to
PO and NPO document types. Some global processing is active for all document
types.

Configuration Run the /OPT/SPRO transaction and navigate to OpenText Vendor Invoice
point Management Invoice Solution > Document Processing Configuration > Document
Type Configuration > Logic Module Processing.

For details, see Section 8.4 “Processing logic modules” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 317

Chapter 32
Global Processing Logic Modules

32.1 Change Vendor Group

This logic module changes the vendor group. If the vendor is changed in
background (for example, due to the partner role), the vendor group must be
changed, too.

Precondition
Vendor number and company code are filled.
Data affected
Vendor group
Class interface
/OPT/CL_D_LM_CHG_V_GRP

32.2 Determine Bank Data

This logic module fills missing bank data. In addition, it removes any present spaces
from the IBAN.

The logic module determines the partner bank type along with all corresponding
fields (for example bank name), based on the data provided in the invoice. If there is
only one entry in the vendor record that matches with the data on the invoice, this
entry is set as the result. In ambiguous cases, no data is changed.

In the most typical case, when the Capture process extracts the IBAN value from an
invoice, and that IBAN is found in the vendor record, the remaining fields like
partner bank type, bank name, SWIFT/BIC code, and so on, are determined.

Note: The Z constant 005 / REMOVE_PART_BNK_TYP controls whether the partner

bank type field is set or not. Active by default, it leaves the field blank, keeping
all other values as determined. This helps to prevent separate payments
created for each invoice during the payment run. If partner bank type is set,
SAP S/4HANA will create separate payments by default.

Category
Mapping
Precondition
Partner bank type is empty.
Data affected
All bank data is filled if available in vendor master.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 319

Chapter 32 Global Processing Logic Modules

• Partner bank type

• Bank number
• Name of bank
• Bank country key
• IBAN
• SWIFT
• Vendor permitted as payee
• Reference specification for bank details

Class interface
/OPT/CL_D_LM_DETERM_BANKDATA

32.3 Determine SAP Document Type

This logic module fills the missing SAP document type from OpenText VIM for SAP
document type customizing.

Category
Simple mapping
Precondition
SAP document type is empty.
Data affected
SAP document type is filled.
Class interface
/OPT/CL_D_LM_DETERM_BLART

32.4 Determine Invoice Category

This logic module maps the externally provided invoice category to the OpenText
VIM for SAP invoice category.

Category
Simple mapping
Precondition
Invoice category is filled in the inbound process.
Data affected
Invoice category contains an OpenText VIM for SAP specific value.
Class interface
/OPT/CL_D_LM_DETERM_INV_CAT

320 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 32.5. Determine Payment Terms

32.5 Determine Payment Terms

This logic module fills missing payment terms from the vendor (non PO) or from the
PO (vendor, company code). In baseline, this logic module is configured to run at
process start.

Category
Mapping

Precondition
Document type, vendor number and company code are filled.

Data affected
Payment terms are filled.

Class interface
/OPT/CL_D_LM_DETERM_PAY_TERM

32.6 Determine Payment Baseline Date

This logic module fills missing payment baseline date from OpenText VIM for SAP
document type customizing. In baseline, this logic module is configured to run at
process start.

Category
Mapping

Precondition
Payment baseline date is empty.

Data affected
Payment baseline date is filled.

Class interface
/OPT/CL_D_LM_DETERM_PBL_DATE

32.7 Determine Posting Date

This logic module fills the posting date from OpenText VIM for SAP country specific
customizing.

Category
Simple mapping

Precondition
Posting date or posting date determination is empty.

Data affected
Posting date is filled.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 321

Chapter 32 Global Processing Logic Modules

Class interface
/OPT/CL_D_LM_DETERM_POST_DATE

32.8 Determine Tax Code

This logic module fills the tax code using OpenText VIM for SAP document type
customizing.

Category
Simple mapping
Precondition
Tax code is empty.
Data affected
Tax code is filled.
Class interface
/OPT/CL_D_LM_DETERM_TAX_CODE

32.9 Determine New Credit Memo Flag

This logic module fills the document “transaction” field (VORGANG) depending on the
older Credit memo flag.

Category
Simple mapping
Precondition
Document “transaction” field is initial and old credit memo flag is filled.
Data affected
New credit memo flag is filled.
Class interface
/OPT/CL_D_LM_DETERM_VORGANG

32.10 Determine Vendor Address

This logic module fills the vendor address data from the vendor master.

Category
Simple mapping
Precondition
Vendor number is filled.
Data affected
Vendor address is filled.

322 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 32.11. Determine Vendor Group

Class interface
/OPT/CL_D_LM_DETERM_V_ADR

32.11 Determine Vendor Group

This logic module fills the vendor group from OpenText VIM for SAP Business Rule
Framework Customizing.

Category
Simple mapping

Precondition
Vendor number and company code are filled.

Data affected
Vendor group is filled.

Class interface
/OPT/CL_D_LM_DETERM_V_GRP

32.12 Determine Vendor Name

This logic module fills the vendor name from the vendor master.

Category
Simple mapping

Precondition
Vendor name is empty and vendor number is filled.

Data affected
Vendor name is filled.

Class interface
/OPT/CL_D_LM_DETERM_V_NAME

32.13 Determine Withholding Tax

This logic module fills the withholding tax data. Classic withholding data are read
only on the indexing screen. Extended withholding tax data can be changed
manually.

Category
Mapping

Precondition
Vendor number and company code are filled and subject to withholding tax.
The following data is required to retrieve withholding tax.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 323

Chapter 32 Global Processing Logic Modules

For PO documents

• Company code
• Vendor
• Total gross amount
• PO number
• Tax code for net or tax based withholding tax type

For Non PO documents

• Company code
• Vendor
• Total gross amount
• Currency
• Posting date
• At least one line item

Data affected
Withholding tax data is filled.
Class interface
/OPT/CL_D_LM_FILL_WHT

32.14 Synchronize Item Text

This logic module synchronizes the item text and item material text fields. If one is
initial and the other is not, the content is copied.

Category
Simple mapping
Precondition
Not applicable
Data affected
Item text fields SGTXT and MAKTX contain the same text.
Class interface
/OPT/CL_D_LM_SYNC_ITEM_TXT

324 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 32.15. Determine Purchasing Document Category

32.15 Determine Purchasing Document Category

This logic module determines the purchasing document category.

Category
Simple mapping

Precondition
Relevant for PO based documents only

Data affected
The logic module determines the purchasing document category from PO
master data.

Class interface
/OPT/CL_D_LM_DETERM_BSTYP

32.16 Copy vendor tax/VAT ID after a flexible check

You can use this logic module to copy the partially matching vendor tax/VAT ID
from the master data into the OpenText VIM for SAP document. If the flexible tax
number check is enabled with Z constant 005 / FLEXIBLE_TAXID_CHECK, the logic
module first performs an exact comparison. If that fails, but a flexible comparison
provides a match with any of the tax/VAT numbers maintained in SAP vendor
record, the value is copied from master data into the OpenText VIM for SAP
document.

Precondition
Vendor number and vendor tax/VAT number are filled.

Data affected
Vendor tax/VAT number

Class interface
/OPT/CL_D_LM_FCOPY_VEND_TAX_ID

32.17 Normalization of vendor and company code tax

IDs
This logic module provides normalization (removal of spaces) of vendor tax/VAT ID
and of recipient tax ID. The normalization must be enabled in the characteristic
specific configuration of the respective country.

Precondition
Vendor number and vendor tax/VAT number are filled, company code and
recipient tax number are filled. Tax ID normalization is enabled for the
respective country.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 325

Chapter 32 Global Processing Logic Modules

Data affected
Vendor tax/VAT number, recipient tax number
Class interface
/OPT/CL_D_LM_NORMALIZE_TAX_IDS

32.18 Tax Invoice Determination

This logic module determines the tax invoice flag.

Category
Simple mapping
Precondition
Relevant if tax description has been recognized
Data affected
The logic module maps the tax description to the tax invoice flag.
Class interface
/OPT/CL_D_LM_DETERM_TAX_INV

32.19 Create Held/Parked/Completely Parked

Document in Background
This logic module creates a document in background.

Category
Document creation
Precondition
This needs to be activated in the process type assignment in the OpenText VIM
for SAP document type. For more information, see Section 8.3.2 “Configuring
automatic parking after the start of the DP process” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Data affected
The logic module automatically tries to create a completely parked document. If
this fails, it tries to create a parked document. If this fails as well, the logic tries
to create a held document.
Class interface
/OPT/CL_D_LM_CREATE_PARKED

326 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 32.20. Create Held Document in Background

32.20 Create Held Document in Background

This logic module creates a held document in background.

Category
Document creation
Precondition
This needs to be activated in the process type assignment in the OpenText VIM
for SAP document type. For more information, see Section 8.3.2 “Configuring
automatic parking after the start of the DP process” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Data affected
The logic module automatically tries to create a held document.
Class interface
/OPT/CL_D_LM_CREATE_HOLD

32.21 Create Completely Parked Document in

Background
This logic module creates a completely parked document in background.

Category
Document creation
Precondition
This needs to be activated in the process type assignment in the OpenText VIM
for SAP document type. For more information, see Section 8.3.2 “Configuring
automatic parking after the start of the DP process” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Data affected
The logic module automatically tries to create a completely parked document.
Class interface
/OPT/CL_D_LM_CREATE_PARK_COMP

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 327

Chapter 32 Global Processing Logic Modules

32.22 Create Parked Document in Background

This logic module creates a parked document in background.

Category
Document creation
Precondition
This needs to be activated in the process type assignment in the OpenText VIM
for SAP document type. For more information, see Section 8.3.2 “Configuring
automatic parking after the start of the DP process” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Data affected
The logic module automatically tries to create a parked document.
Class interface
/OPT/CL_D_LM_CREATE_PARK

32.23 Calculation of Capture Analytics

This logic module runs the calculation of the Capture Analytics report for OpenText
Capture for SAP Solutions or OpenText Core Capture for SAP Solutions. It must be
used only once at the process start.

Category
Inbound Processing
Precondition
The document data was provided by OCR extraction process done in OpenText
Capture for SAP Solutions or OpenText Core Capture for SAP Solutions.
Data affected
Statistics about extracted and validated fields are collected and stored.
Class interface
/OTX/PS03_CL_D_LM_EXTANALYTICS

328 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 32.24. Determine Invoice Receipt Date

32.24 Determine Invoice Receipt Date

A field Invoice Receipt Date is introduced in the DP indexing screen.

Category
Mapping
Precondition
Invoice receipt date is empty when coming from inbound.
Data affected
Invoice Receipt Date field is filled with Archived Date.
Class interface
/OPT/CL_D_LM_DETERM_INVREC_DAT

32.25 Determine Payment Method Supplement

This logic module fills the Payment Method Supplement with the default value from
Vendor. OpenText recommends that you use the logic module only once at the
process start.

Category
Mapping
Precondition
Payment Method Supplement is empty when coming from inbound.
Data affected
Payment Method Supplement is filled based on the value maintained in the
Vendor details.
Class interface
/OPT/CL_D_LM_PYMNT_SUPP_MTHD

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 329

Chapter 33
PO related logic modules

33.1 Determine Currency

This logic module fills missing currency from an existing PO.

Category
Simple mapping
Precondition
Currency is empty and PO number is filled.
Data affected
Currency is filled.
Class interface
/OPT/CL_D_LM_DETERM_CURR

33.2 Determine Delivery Date

This logic module fills the missing delivery date (supply date) from an existing PO.
The value that will be assigned is the creation date of the first GR that is not
cancelled.

Note: This logical module may run when you do not have line item data yet,
because, in the baseline configuration, the logical module is placed before the
PO line item proposal module. If you will later use different, not the oldest,
GRs in the line items of the document, the assigned value might not be set as
expected. In such cases, you can rearrange the sequence in which the logical
modules run, as a project specific configuration.

Category
Simple mapping
Precondition
Delivery date is empty and PO number is filled.
Data affected
Delivery date is filled.
Class interface
/OPT/CL_D_LM_DETERM_DEL_DATE

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 331

Chapter 33 PO related logic modules

33.3 Determine PO Item Data

This logic module fills the PO data according to the OpenText VIM for SAP
document type specific PO Line Automation customizing.

Category
Mapping at process start
Precondition
PO number is filled.
Data affected
PO item data is retrieved.
Class interface
/OOPT/CL_D_LM_DETERM_PO_MAP2

33.4 Determine Matching Single Line PO Data for

Vendor
This logic module checks whether open single item POs for the vendor match
invoice data.

Category
Mapping at process start
Precondition
Single line item invoice; PO number is empty and vendor is filled. The
document must be an invoice (not a down payment or a credit memo), and the
document must have skipped validation.
Data affected
PO data is retrieved. The document type is redetermined and might be changed
from an NPO document type to an appropriate PO document type.
Class interface
/OPT/CL_D_LM_DETERM_PO_SGL1
Note: This logic module is not active by baseline. Use it only if it is very
unlikely that NPO invoices come in with amounts that would match an
open PO from the same vendor.

332 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 33.5. Determine Vendor

33.5 Determine Vendor

This logic module fills the missing vendor from the PO.

Category
Simple mapping
Precondition
Vendor number is empty and PO number is filled.
Data affected
Vendor number is filled
Class interface
/OPT/CL_D_LM_DETERM_LIFNR

33.6 Determine CPD Vendor Address Data from PO

This logic module adds additional address information of CPD vendors from the
purchase order. You can add this definition to custom logic module processes to
copy the additional CPD address from the purchase order to the OpenText VIM for
SAP tables. This module replaces business rule 413, which is used in version 7.0.

Category
Simple mapping
Precondition
Address data of CPD vendor is empty in OpenText VIM for SAP tables.
Data affected
Address data of CPD vendor is filled from purchase order.
Class interface
/OPT/CL_D_LM_DETERM_CPD

33.7 Determine Additional Costs

This logic module looks for planned costs in the PO and matches them with
additional cost lines delivered by the inbound process. Unmatched lines are treated
according to OpenText VIM for SAP unplanned costs handling determination.

Category
Mapping
Precondition
PO number(s) provided, and the inbound process delivers valid additional cost
lines.
Data affected
Depending on the OpenText VIM for SAP additional cost customizing

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 333

Chapter 33 PO related logic modules

Class interface
/OPT/CL_D_LM_MAP_ADD_COSTS

33.8 Use PO Header Data to Overwrite Line Items

This logic module discards the existing lines items and overwrites them with the
current MIRO proposal (GR) list.

Category
Mapping
Precondition
PO number and invoice header amount are filled. The PO amount is identical to
the GR amount and the invoice amount.
Data affected
Line items are overwritten.
Class interface
/OPT/CL_D_LM_MAP_HEADER_PO

33.9 Verify PO Data

This logic module checks whether the PO number belongs to company code and
vendor. Non-matching data is deleted. If no PO is left, the document type is
redetermined.

Category
Changing data
Precondition
Company code, PO number and vendor number are filled.
Data affected
PO number, PO line item data, document type
Class interface
/OPT/CL_D_LM_VERIFY_DATA

334 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 33.10. Process Line Items from OCR

33.10 Process Line Items from OCR

This logic module processes line item data delivered from OCR for PO invoices.

Category
Mapping at process start
Precondition
Channel VIM_IES. If another channel should be processed, you can configure
this in the customizing.
Data affected
Line items from OCR are deleted or not depending on the setting Ignore Items
from Ext System in the document type definition. For more information, see
Section 8.1.1 “Creating a new DP document type” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Class interface
/OPT/CL_D_LM_DETERM_PO_OCR

33.11 Determine Invoice Reference for Credit Memos

This logic module determines the invoice references for credit memos. The invoice
references can be used in FI and MM invoices when posting credit memos, to
establish links to the original invoice related to the credit memo that is being posted.

Category
Simple mapping
Precondition
CM Reference number is filled.
Data affected
Invoice reference is filled with the reference of the original invoice.
Class interface
/OPT/CL_D_LM_DETERM_CM_INV_REF

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 335

Chapter 33 PO related logic modules

33.12 Consolidate line items referring framework

orders
This logic module consolidates invoice line items if all purchase orders referred by
the invoice are framework orders (with limit items). The module can be used when
framework / limit orders must be processed at header level and line items do not
need to be distinguished. The module is delivered as module ID P_ITEM_005,
process ID P_SPEC_004. It is inactive in the standard configuration and must be
activated when required.

Category
Mapping

Precondition
Invoice has at least two line items. Line items do not contain different values in
fields like tax code, tax rate, and others that hinder the consolidation into one.

Data affected
Invoice line items are consolidated into one.

Class interface
/OPT/CL_D_LM_DETERM_FRM_PO

33.13 Populate TM object lists

This logic module copies the following line item TM document details to the TM
object list in the Basic data tab of the indexing screen:

• Freight Order (FO)

• Freight Settlement Document (FSD)
• House Bill of Lading (HBL)
• Air Waybill (AWB)

This logic module fills the /OPT/VIM_1PO_DN table where the data from the Inbound
channel is received.

Category
Simple Mapping

Precondition
Freight Order, Freight Settlement Document, House Bill of Lading, Air Waybill.

Data affected
Updates the /OPT/VIM_1PO_DN table.

Class interface
/OPT/CL_D_LM_FILL_TM_LISTS

336 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 34
NPO related logic modules

34.1 Determine Expense Type

This logic module fills a missing expense type from OpenText VIM for SAP vendor
customizing.

Category
Simple mapping
Precondition
Expense type is empty and vendor is filled.
Data affected
Expense type is filled.
Class interface
/OPT/CL_D_LM_DETERM_EXP

34.2 Determine NPO Line

This logic module fills a missing line item from header data.

Category
Mapping at process start
Precondition
NPO document type and no line item.
Data affected
One line item is created from header data.
Class interface
/OPT/CL_D_LM_DETERM_NPO_LINE

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 337

Chapter 34 NPO related logic modules

34.3 Determine NPO Auto Coding

This logic module fills coding data from the OpenText VIM for SAP NPO line auto
coding configuration.

Category
Mapping at process start
Precondition
No purchase order numbers or delivery notes are used on the invoice.
Data affected
Line item coding data is filled.
Class interface
/OPT/CL_D_LM_DETERM_NPO_COD

34.4 Process Line Items from OCR

This logic module processes line item data delivered from OCR for NPO invoices.

Category
Mapping at process start
Precondition
Channel VIM_IES. If another channel should be processed, you can configure
this in the customizing.
Data affected
Line items from OCR are deleted or not depending on the setting Ignore Items
from Ext System in the document type definition. For more information, see
Section 8.1.1 “Creating a new DP document type” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Class interface
/OPT/CL_D_LM_DETERM_NPO_OCR

34.5 Enrich NPO Line Items

This logic module enriches existing NPO line item data.

Category
Simple mapping
Precondition
Line items present
Data affected
Existing NPO line items are enriched with posting relevant information:

338 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 34.6. Enrich smart coding cost line items

• Company code, plant, business place (BUPLA), and business area (GSBER) are
copied from header data if empty.
• Fields not relevant for posting are emptied: quantity and related units.

Class interface
/OPT/CL_D_LM_DETERM_NPO_ENR

34.6 Enrich smart coding cost line items

To achieve automatic proposal of smart coding cost lines in Classic OpenText VIM
for SAP, a logic module ID is introduced and needs to be configured. By default it is
delivered inactive. If you want to use smart coding automation, you must configure
the logic module delivered for smart coding.

Category
Mapping at process start
Precondition
No purchase order numbers or delivery notes are used on the invoice
Training data for company code and vendor with cost line item confidence
above the confidence limit in Z constant SMART_CODE_MODEL
Data affected
Smart line item coding data is filled.
Class interface
/OTX/PS39_CL_D_LM_DET_NPO_SCOD

34.7 Determine Invoice Reference for Credit Memos

This logic module determines the invoice references for credit memos. The invoice
references can be used in FI and MM invoices when posting credit memos, to
establish links to the original invoice related to the credit memo that is being posted.

Category
Simple mapping
Precondition
CM Reference number is filled.
Data affected
Invoice reference is filled with the reference of the original invoice.
Class interface
/OPT/CL_D_LM_DETERM_CM_INV_REF

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 339

Chapter 35
Country specific logic modules

35.1 Determine Ship-to Region for Canada

This logic module fills the ship-to region for Canada.

Category
Simple mapping
Precondition
Country is Canada and ship-to region is empty.
Data affected
Ship-to region is filled.
Class interface
/OPT/CL_D_LM_DETERM_SHP_REGN

35.2 Determine Corrective Items for Russia

This logic module reacts to externally provided corrective invoice categories for
Russia and condenses line items for OpenText VIM for SAP.

Category
Mapping
Precondition
Country is Russia and invoice category contains either a V or a W.
Data affected
Four corrective line items are condensed to one line.
Class interface
/OPT/CL_D_LM_MAP_R_CORR_ITEMS

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 341

Chapter 35 Country specific logic modules

35.3 Determine Service PO for Russia

This logic module reacts to externally provided service invoice categories for Russia
and maps a single service PO.

Category
Mapping

Precondition
Country is Russia, the PO number is empty and the invoice category contains M.
A PO with corresponding net price and quantity exists for the vendor.

Data affected
Service PO is filled.

Class interface
/OPT/CL_D_LM_MAP_R_SERV_PO

35.4 Determine KIDNO for Denmark

This logic module checks and, if needed, corrects the payment reference field (KIDNO)
for Denmark.

Category
Mapping

Precondition
Country is Denmark. Company code is filled and payment reference is
provided.

Data affected
KIDNO is filled.

Class interface
/OPT/CL_D_LM_VERIFY_KIDNO

35.5 Enrich Country Specific Data for China

This logic module enriches country specific data for China.

Category
Simple mapping

Precondition
The country of the company code is China (CN).

Data affected
The invoice category is mapped based on the invoice code.

342 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 35.6. Enrich Country Specific Data for France

Class interface
/OPT/CL_D_LM_DETERM_COUNTRY_CN

35.6 Enrich Country Specific Data for France

This logic module enriches country specific data for France.

Category
Simple mapping
Precondition
The country of the company code is France (FR).
Data affected
The Siret Number field is mapped from the vendor tax number.
Class interface
OPT/CL_D_LM_DETERM_COUNTRY_FR

35.7 Enrich Country Specific Data for India

This logic module enriches country specific data for India.

Category
Simple mapping
Precondition
The country of the company code is India (IN).
Data affected
The logic module maps the PAN and STC number into the vendor tax number
and determines the invoice category.
Class interface
/OPT/CL_D_LM_DETERM_COUNTRY_IN

35.8 Determine Invoice Reference for Spain

This logic module splits the long reference number of incoming documents into text
and vendor reference based on the values maintained in Z-Constant SET_REF_
MAPPING_SP.

Category
Simple mapping
Precondition
Country is Spain. Long reference number is filled, and Z constant SET_REF_
MAPPING_SP has lengths in the format X16,B20 where 16 and 20 are the desired
lengths of XBLNR and BKTXT.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 343

Chapter 35 Country specific logic modules

Data affected
Long reference number is split into text and invoice reference.
Class interface
/OPT/CL_D_LM_DETERM_BKTXT_XBLN

344 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Part 8
Automated Field Enhancement
Part 8 Automated Field Enhancement

OpenText VIM for SAP provides a feature that allows you to add mapping activities
after the field mapping is done. In this Automated Field Enhancement (also called
enhanced mapping), you can refer to the values of different fields.

346 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 36
Configuring Automated Field Enhancement

You control Automated Field Enhancement in table /OPT/VIM_T107, and you

maintain it in the same maintenance view as the normal field mapping. For more
information, see Section 7.4 “Maintaining the OpenText VIM for SAP field mapping”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).

In the Automated Field Enhancement configuration, you enter a sequence of

entries, which will be processed in the order of their counter value. In each entry,
you specify a target field and the action (normally a function module), which will be
called to modify the value of the target field.

In the field mapping, the relation between source field and target field is a 1:1
relation. This is visible in the mapping table. With Automated Field Enhancement,
this is not the case. “Baseline of Automated Field Enhancement“ on page 349 shows
the relation between source fields and target fields.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 347

Chapter 37

Baseline of Automated Field Enhancement

The following tables provide an overview of Automated Field Enhancement, which

is delivered in the baseline. The overview shows only the involved values and
tables.

Mapping ID Type Sources Target field Function module

GENERAL Header LIFNR, LFA1 VEND_NAME /OPT/
VIM_EXIT_MAP_E
NH_01
GENERAL Item MAKTX SGTXT /OPT/
VIM_EXIT_MAP_E
NH_01
GENERAL Item SGTXT MAKTX /OPT/
VIM_EXIT_MAP_E
NH_01
GENERAL Header CREDIT_MEMO VORGANG /OPT/
VIM_EXIT_MAP_E
NH_03
GENERAL Header EBELN, T169F BLART /OPT/
VIM_EXIT_MAP_E
NH_03
GENERAL Header BUDAT POST_DATE_DET /OPT/
VIM_EXIT_MAP_E
NH_03
GENERAL Item /OPT/ EBELP /OPT/
SLN_VENDOR VIM_EXIT_MAP_SL
N
GENERAL Item /OPT/ EBELN /OPT/
SLN_VENDOR VIM_EXIT_MAP_SL
N

Mapping ID Type Sources Target field Function module

XML_ENFE Header BLDAT DOCDAT /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header DOCDAT BLDAT /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 349

Chapter 37 Baseline of Automated Field Enhancement

Mapping ID Type Sources Target field Function module

XML_ENFE Header RMWWR GROSS_AMOUNT /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header GROSS RMWWR /OPT/
_AMOUNT. VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header LIFNR LIFNR /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header PARID PARID /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header STCD1 VEND_NAME /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_STREET REMIT_STREET /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_PSTLZ REMIT_PSTLZ /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_AD_CITY1 REMIT_AD_CITY1 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_LAND1 REMIT_LAND1 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_REGIO REMIT_REGIO /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header BUKRS, CDC, BUKRS /OPT/
T001Z VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM XBLNR /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM9 NFNUM9 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM NFNUM /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE

350 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Mapping ID Type Sources Target field Function module
XML_ENFE Header J_1BAA NF_TYPE /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Fix: BRL WAERS
XML_ENFE Header Fix: X AUTO_CALC
XML_ENFE Header Fix: X FLAG_ENFE

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 351

 Part 9
Z constants
Part 9 Z constants

This part provides a list of the Z constants that are used in OpenText VIM for SAP.
There are individual chapters for each product code.

The following product codes are available:

002, 009
Cross component product codes
005
Document Processing (DP) based product codes
IAP
Invoice Approval product codes
IEA
Product codes for Unified Dashboard and archiving supports
IEM
Invoice Exception Monitor product codes
LIX
LIV based product codes (both for PO parking and PO blocking workflows)
VAN
VIM Analytics product codes

354 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 38
Z constants for product code 002 and 009

Product Constant Description Default Value

Code
Maximum file size
for attachment
002 ATT_MAX_FILE_SIZE upload 10485760
Currently this constant is evaluated in VIM Fiori apps that offer an attachment
upload. Default value is 10 MB.
Process option for
Online contract
002 CONTRACT_POSTING posting 5002
For more information, see Section 8.19.1 “Activating the document types
configuration” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Function Module
to calculate Due
date for Delay FM /PTGWFI/
002 DUE_DATE_FM logic 0000000002_TMP010
Function Module
to calculate Due
date for Delay FM /PTGWFI/
002 DUE_DATE_FM_PRICE logic ( Price Block) 0000000002_TMP010
Maximum Allowed
wait days for the FM:/PTGWFI/
002 MAX_WAIT_DAYS wait workflow 0000000002_TMP005
Tolerenace % limit
002 PAYASISTOLERANCE for Pay-As-Is 100
Max val Tolerance
for Pay-As-Is
( giveCurr by
placing a “;” - Eg.
002 PAYASIS_MAX_VAL_TOLE 100;USD) 1000000;USD
Function module to
be called to build
short pay
SHORTPAY_BDC_CAN_IN transactions
002 V Cancel/Create Inv

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 355

Chapter 38 Z constants for product code 002 and 009

Product Constant Description Default Value

Code
Function module to
be called to build
short pay
transactions for SC/
002 SHORTPAY_BDC_SC_DM DM
Wait data Display /PTGWFI/
002 WAIT_DATA_DISP_FM Function Module 0000000002_TMP002
Function module to /PTGWFI/
002 WAIT_DATA_GET_FM get the wait data 0000000002_TMP001
Set to X to check
authorizations for
ALV layouts in log
009 ALV_CHECK_ACTIVE display X
If set to X, ALV layout authorization is checked with the authority object J_6NIM_
ALV, in VIM Invoice Workplace, VIM Analytics and VIM Unified Dashboard. For
more information, see Section 6.7 “Restricting ALV layout for process logs” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Set to X to activate
all authorization
checks in OpenText
009 AUTH_CHECK_ACTIVE VIM for SAP
For more information, see Section 6.3.3 “Enabling OpenText VIM for SAP
authorization checks globally” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD) and Section 16.4
“Defining action authority groups for the VIM Invoice Workplace” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
EXTEND_RECIPIENT_SEL Set to X to enable <blank>
the new extended
recipient selection
dialog for DP and
invoice exceptions
009 dashboards.
For more information, see the Release Notes of version 5.2 SP9.
IMAGE_DISP_FM Function Module /OPT/CP_DISPLAY_IMAGE
to Display
009 Attachments
This constant is set to function module /OPT/CP_DISPLAY_IMAGE, used to
display the attachment list of a DP document in VIM Analytics or VIM Invoice
Workplace. Each attachment can be opened from the list.
This constant is an optional entry. You can add it if required, but it is not part of
the baseline. To avoid bugs and to display attachments, implement the latest
Correction Instruction (CI), available on OpenText My Support.

356 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
LIX_PIR_WITEXT_FM Txt maintenance /OPT/
for BIR Workflow BL_IF_DET_REASON_WI_T
009 EXT
SPROGRAM_CHECK_ACTI Set to X to activate <blank> (not delivered in
V report execution standard configuration)
authorization
checks in OpenText
009 VIM for SAP
Set this constant to X to activate additional authorization checks at the beginning
of each OpenText VIM for SAP report.
The additional authorization check is performed against the authority check
object S_PROGRAM and authorization group /OPT, action SUBMIT. You can use this
check to restrict the general execution of OpenText VIM for SAP reports.
SRFC_CHECK_ACTIV Set the value to X
to activate the
009 checks.
For more information, see Section 6.6 “Authorization checks for RFC calls” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 357

Chapter 39
Z constants for product code 005

Product Constant Description Default Value

Code
Enable/disable
Accessibility Mode.
The default is
blank. To enable
005 ACCESSIBILITY_MODE use 'X' <blank>
In VIM Analytics, VIM Invoice Workplace, and the indexing screen, the
Accessibility Mode controls the invoice display in the Detail pane:
If this Z constant is set to <blank> and the image display is configured to be
outside OpenText VIM for SAP, there is no message in the Detail pane, it is
blank.
If this Z constant is set to X and the image display is configured to be outside
OpenText VIM for SAP, a message “Image/Document opened in new window” is
displayed in the Detail pane.
ADD_COST_FM Customer specific
function module
for mapping of
005 additional cost
For more information, see Section 8.15.8 “Maintaining a function module for
customer specific cost handling” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
ADD_UNPL_COST_FM Customer specific
function module
for mapping of
005 unplanned cost
For more information, see Section 8.15.9 “Maintaining a function module for
customer specific unplanned cost matching” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Custom
configuration for
advance tax
determination
class. If you want
to build your own
custom logic for
advanced tax
determination for
the tax table
control, you can /OPT/CL_C_DETERMINE_
005 ADV_TAX_CALC use this Z-Const. ADV_TAX

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 359

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
For more information, see Section 33.4 “Maintaining Z constant 005 /
ADV_TAX_CALC” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Process Type for
005 AFTCS_PROCESS_TYPES AFTCS File 141,241
For more information, see Section 15.4 “Z constants” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Unallocated GR
Quantity (Set to X if
quantity of DP
needs to be
005 ALLOCATE_GR_TO_DP considered) X
VIM Confirm Quantity and Price Fiori app, Unallocated GR Quantity
calculation: Set this constant to X if DP Quantities calculation is needed to be
considered along with the SAP Invoices and GRs done for the PO, and the
subsequent GRs to be done using the Confirm Quantity and Price app.
To Allow
calculation for
deriving Amount/
Quantity based on
005 ALLOW_NETPR_CAL Net Price X
This constant is called in form CALCULATION1 or CALCULATION in the FM /OPT/
VIM_LINES_DERIVE_PO to calculate the line item. The FM is used in the business
rule Manual Check Needed for Indexing Lines (PO). To support tax
calculation on net amount, set the constant to X .
Option Id for
Approval
005 APPROVAL_OPTION Workflow 2015
For more information, see Section [Link] “Defining resubmit for approval action
codes” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
URL to show
Configuration
Documentation for
Document
Processing
005 APP_DOCU_URL Application [Link]
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).

360 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
If set to 'X', AR
object in
VIM_1HEAD will
be derived from
005 AR_OBJECT_FROM_DP DP doctype
For more information, see Section 8.1.8 “Mapping ArchiveLink document types”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Function module
for customer logic
to determine
005 AR_OBJECT_DETRM_FM archive doc type
Template for this function module is /OPT/VIM_GET_AR_OBJECT_TEMPLT.
For more information, see Section 8.1.8 “Mapping ArchiveLink document types”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Function module
for customer logic
to trigger
redetermination of
005 AR_OBJECT_TRIG_FM archive doc type
Template for this function module is /OPT/VIM_AR_OBJECT_TRIG_TEMPLT.
For more information, see Section 8.1.8 “Mapping ArchiveLink document types”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Ariba Inbound: set None, the constant is not
main image to PDF delivered with baseline
005 ARIBA_MAIN_IMAGE or CXML configuration.
Valid starting with OTVIMARB 7.5 SP4. Using this constant, you can determine
the main invoice image. Possible values:
CXML: make the CXML file the main invoice image.
PDF: make the invoice PDF file (generated by the Ariba Network) the main invoice
image.

Note: Setting this constant overrides the previously used setting in the
ARIBA channel.
BDC Id to be called
by Function /OPT/
VIM_PREPOPULA
005 BDC_PARKING_ONLINE TE_MIR7 16
This constant is used in the FM /OPT/VIM_PREPOPULATE_MIR7. The FM is used
in BDC 201 to support PO invoice parking online in a special case with multiple
POs existing in the invoice. The BDC maintained in this constant is used for the
online parking option maintained with BDC 201.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 361

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
BDC Id to be called
by Function /OPT/
VIM_PREPOPULA
005 BDC_POSTING_ONLINE TE_MIRO 1
For more information, see Section 8.11.3 “Enhancing MIRO for pre-population of
data during online invoice creation” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
Set to ‘X’ to use
OpenText VIM for
SAP data instead of
delivery note
number for Brazil
(in reference
document building
005 BR_NO_GR_REF enhancement).
For more information, see Section 8.11.3 “Enhancing MIRO for pre-population of
data during online invoice creation” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD). This section
describes the steps that are necessary to keep line item data during online
posting.

Usually the PO line data of the DP document is used. For Brazilian invoices, the
reference number is used to retrieve delivery note data and to fill the line items
accordingly. If this Z constant is set to X, the enhancement ignores the Brazilian
specialty and uses the PO line data.
005 BR_TAX_ON_COND
To solve the problem of incorrect tax and balance calculation in specific situations
for Brazil and Indian invoices, OpenText VIM for SAP provides a user exit that
you can use, depending on project needs. A standard implementation is provided
as the function module /OPT/VIM_GET_TAX_AMOUNT.
005 BULK_APP_IMAGE Set the value 12
This Z constant is created to decrease the calls from SAP to Windows Viewer
while accessing images in bulk mode from VIM Invoice Workplace. Maintain the
Z constant value as 12-comments or 11-history (other than 10-image). This is
considered as the default tab in the plug-in area. User settings must be
maintained as 10-image.

Note: By maintaining this Z-constant, the user default tab setting in the
plug-in area is only affected for bulk mode.
Start OpenText
VIM for SAP
process in Central
System always
(X=via RFC,
C=direct call,
005 CENTRAL_VIM_PROCESS empty=no)

362 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
This constant is related to starting a new DP process in OpenText VIM for SAP. It
indicates whether the new DP process should always be started in the central
system or not. There are two variants to start the DP workflow in the central
system:
X: start via RFC
C: start by direct function call

Checks if Update
Tasks are running
005 CHK_UPD_TSK_IS_ALIVE (when set to 'X') X
Description – When running a process option based on a call transaction (posting
or parking), the system checks if the update tasks are running. If not, a message
Update delayed. Please wait. is shown to the user.

Case 1: User is waiting for time out.

Case 2: User aborts the transaction.

--> Result in case 1 and 2: The workflow stays in the current state and can be
continued later.

Case 3: Update task continued or restarted after some time.

--> Result in case 3: The process is continuing, posting or parking is possible.

Logging – If you activate the check, an application log entry (SLG1) is written:
Object: VIM, Subobject: DP, LogPoint 94 (Update Delayed), if any update delay
that is longer than 10 seconds was discovered.

Scope – Activate this function if the system often experiences issues with update
tasks or inconsistencies between posted documents and OpenText VIM for SAP
data. The additional check improves the stability when posting invoices in dialog
in these environments. However, the check can slightly slow down processing.
MIME file type for
main invoice image
for Ariba
005 CIG_MAIN_ATTACH Integration
This constant is used in the Ariba CIG integration component. When suppliers
are sending attachments along with the Ariba invoice, typically as PDF files, you
might want to use those attachments as the main invoice image. You must set the
value to the MIME type to select the file types to be used. Example value:
application/pdf

Flag (x = manual
change of BRF-
Bypass allowed in
COMPL_ALLOW_M_BYPA Simulation/Bypass
005 SS Popup) X

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 363

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
If set to X, a manual change of activate/bypass is allowed in the DP simulation
screen. For more information, see Section 8.5.3 “Additional configuration” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Flag (x = no check
type in Simulate
COMPL_HIDE_CHECKTYP Business Rule
005 E Popup)
If set to X, check type information is hidden in the DP simulation screen. For more
information, see Section 8.5.3 “Additional configuration” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution
(VIMZ-CGD).
If random number
(0-100) is bigger
than minimum
value run rule
005 COMPL_RANDOM_MIN check 50
This central value is used as a lower limit for the Business Rule Framework. If
check type RANDOM is active for a business rule (process type), the SAP random
number generator is called. It returns a value between 0 and 100. If you want
business rules to run very rarely, you have to enter a high value (for example 90).
If you want them to run more often you have to enter a low value (for example
10). For more information, see Section 8.5.3 “Additional configuration” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Customer specific
function module
for Russian
corrective invoice
005 CORR_ITEMS_FM item handling
User Exit for
CUSTOM_FM_COMPLIAN customer specific
005 CE compliance
User Exit for customer specific Business Rule Framework matching. The template
for this function module is /OPT/VIM_DCMP_EX_MATCH. For more information,
see Section 8.5.3 “Additional configuration” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
User Exit to
manipulate data
005 CUSTOM_FM_PLUGIN for BAPI Input
For more information, see Section [Link] “User exit” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).

364 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
User Exit for
customer specific
005 CUSTOM_FM_WHHIDE wht hiding
User Exit for customer specific hiding of withholding tax from indexing screen in
combination with constant WHTAX_FROM_SAP. The template for this function
module is /OPT/VIM_WT_LIMIT_HIDE. For more information, see Section 21
“Extended withholding tax” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
Change the MIRO -
proposal data as
per the customer
005 CUSTOM_MIRO_CHANGE requirement
This constant is part of the function module /OPT/VIM_CHANGE_PROPOSAL_
MIRO. During proposal, OpenText VIM for SAP provides some baseline
information. If you want to add specific data, you can add it in this function
module. See also Section 8.11.3 “Enhancing MIRO for pre-population of data
during online invoice creation” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
Display invoice
image on display
of dash board
DASHBOARD_IMAGE_AU screen(X- Yes,
005 TO space -No)
For more information, see Section 8.1.10 “Configuring automatic image display”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Display no Logo
005 DASHBOARD_NO_LOGO (Dashboard)
For more information, see Section [Link] “Enhanced Application” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Default Archive
005 DEFAULT_AR_OBJECT Document Type
If the function module /OPT/VIM_WF_START_EXTERNAL is used to start the
OpenText VIM for SAP process externally and no valid ArchiveLink document
type is handed over, the document type maintained in this constant is used to
create the image link entry.
Populate default
tax code exit (Ex
FM:/OPT/
VIM_DEFAULT_T
005 DEFAULT_TAXCODE_NPO AXCODE_NPO)

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 365

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
This constant is used in FM /OPT/VIM_TAX_CODE_DETERMINE. In this constant,
you can maintain a custom exit function to determine the tax code if this value is
not determined in the tax code determination step. The template delivered in the
baseline is /OPT/VIM_DEFAULT_TAXCODE_NPO.
Populate default
tax code exit (Ex
FM:/OPT/
VIM_DEFAULT_T
005 DEFAULT_TAXCODE_PO AXCODE_PO)
This constant is used in FM /OPT/VIM_TAX_CODE_DETERMINE. In this constant,
you can maintain a custom exit function to determine the tax code if this value is
not determined in the tax code determination step. The template delivered in the
baseline is /OPT/VIM_DEFAULT_TAXCODE_PO.
Delay Document
Confirmation
(number entered is
multiplied by 5
005 DELAY_DOC_CONF seconds)
You can use this constant to delay the execution of the “Document confirmation”
task in the DP workflow, to let other parallel processes finish. This reduces the
probability of resource conflicts leading to data inconsistencies. The constant
value will be multiplied by 5 to get the delay duration in seconds.
Delay final
database updates
in the document
confirmation task
(number entered is
multiplied by 5
005 DELAY_DOC_CONF2 seconds)
You can use this constant in combination with the constant DELAY_DOC_CONF
to delay the execution of final database updates that run when the “Document
confirmation” task in the DP workflow finishes. In certain situations, depending
on how the events generated in the “Document confirmation” task are processed,
this reduces the probability of resource conflicts in data updates. The constant
value will be multiplied by 5 to get the delay duration in seconds.
Delay trigger
Approval
Workflow (number
entered is
multiplied by 5
005 DELAY_IAP_EVENT_CREA seconds) 3

366 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
This constant has been introduced to avoid the synchronous update issue when
the approval workflow starts. The constant is called in method Initprocess of
object type /ORS/INVAP. The approval process is delayed by the maintained
amount of time.

Synchronous update issue

There are some OpenText VIM for SAP tables that must be updated in the
process/workflow. Sometimes they are updated synchronously by several
workflows/processes, which leads to a deadlock.
Delay OpenText
VIM for SAP
update following
FIPP event
(number entered is
multiplied by 5
005 DELAY_NPO_EVENT_UPD seconds) 5
This constant is used in FM /OPT/VIM_RPT_RECEIVER to delay updating
OpenText VIM for SAP reporting data tables in response to NPO Events.
Delay in seconds to
the confirmation
coming from SAP
005 DELAY_SAP_CONFIRM S/4HANA 2
This constant is called in FM /OPT/VIM_CONFIRMATION_BINDING to delay
updating OpenText VIM for SAP tables. This helps to avoid missing data like
status.
To Determine the
Reporting
Currency from the
User Parameter
005 DETERMINE_REP_CURR FWS (Default X)

The VIM Analytics report provides a selection field Reporting Currency.

If you want to initialize the field value with the variant /OPT/VA2_L05, maintain
this constant as blank.
If you want to determine the field value as maintained in the user parameter FWS
in the user profile, maintain the constant as X.
Customer specific
function module to
determine partner
005 DET_PARTBANKTYPE_FM bank type
Derive Accounting
005 DERIVE_ACCTDATA Data X
For more information, see Section 8.3 “Derivation of accounting data” in
OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide for Invoice
Solution (VIMZ-CCS)

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 367

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
Custom function
module to /OPT/
determine invoice VIM_TEMPLATE_DET_INV
005 DETERMINE_INV_CAT category _CAT
For more information, see Section 15.4 “Z constants” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Set to X to disable
additional GR
checks in PO line
determination (BR
005 DISABLE_GR_CHECK 113) X
Set this constant value to X if you want to switch off additional GR checks in the
business rule 113, Manual Check Needed / Missing Data for Indexing Lines. This
affects only the new 7.5 business rule, the older business rule with the 7.0 process
type 110 is not affected. In the standard configuration, the business rule checks
whether the invoice quantity on each line item does not exceed the corresponding
GR quantity that is not invoiced yet. For service POs, SES is checked similarly.
Setting the constant value to X disables those checks. The business rule will then
check only if the line items are complete.
This constant has been introduced with version 7.5 SP2.
Minimum length of
a delivery note
005 DN_MIN_LEN number 5
This constant is used to exclude dummy delivery note numbers. Some customers
are using dummy delivery note numbers (for example 1) for a lot of invoices.
Such a delivery number cannot be used for line item
determination and performance optimizing, because this number is extremely
ambiguous. If all your delivery numbers, even very short ones, are significant,
you can set this value to 1.
DP Doc type for
Down Payments
005 DOCTYPE_DWN w/o DP workflow DWN_S4
Maintain the OpenText VIM for SAP document type that should be set if a Down
Payment is posted directly from the SAP transaction without going through the
regular DP workflow. This is required because no OpenText VIM for SAP
document type determination takes place in this case.
DP Doc type for
Non-PO when
document is
parked or posted
directly from SAP
005 DOCTYPE_NPO transaction NPO_S4

368 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
Maintain the OpenText VIM for SAP document type that should be set if a Non-
PO invoice or credit memo is posted or parked directly from the SAP transaction.
This can happen with or without going through the regular DP workflow, where
“with” means running the Delete(Cancel) and Re-enter process option. This
is required because no OpenText VIM for SAP document type determination
takes place in this case.
DP Doc type for
PO when
document is
parked or posted
directly from SAP
005 DOCTYPE_PO transaction PO_S4
Maintain the OpenText VIM for SAP document type that should be set if a PO
invoice or credit memo is posted or parked directly from the SAP transaction.
This can happen with or without going through the regular DP workflow, where
“with” means running the Delete(Cancel) and Re-enter process option. This
is required because no OpenText VIM for SAP document type determination
takes place in this case.
Default DP Doc
005 DP_DOC_TYPE type NPO_S4
If set to 'X', DP Doc
type will be
redetermined
DP_DOC_TYPE_REDETRM (before starting DP
005 N workflow) X
If set, a SAP
document posted
or parked outside
of OpenText VIM
for SAP will be
registered in
OpenText VIM for
005 DP_FOR_SAPDOC SAP X
This constant is introduced in version 7.5 SP6. Set the constant to X if all SAP
documents posted or parked outside of OpenText VIM for SAP should be
registered in OpenText VIM for SAP with a valid DP ID. Prerequisites are the Z
constants DOCTYPE_NPO and DOCTYPE_PO. They must be maintained with
valid document types for NPO and PO.
OpenText VIM for SAP considers only invoices of company code/document type/
plant where rollout is activated.
Exit FM to add/
change data in
BAPI structures
(EX: /OPT/
DNONPO_INVOI
005 DP_NPO_POSTING_EXIT CE_BAPI_EXIT)

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 369

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Park in MIRO/
MIR7 with DP
start: Approver
Selection while
005 DP_PARK_APPR_SELECT parking ('X' = yes)
Possible values:
X: When parking or holding a document in MIRO or MIR7, the requester can be
entered in a dialog box.
<space> (default value): Park document without entering the requester.
For more information, see Section 8.3 “Configuring parked processing” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Exit FM to add/
change data in PO
line item proposal
(EX: /OPT/
VIM_GET_PROPO
005 DP_PO_PROPOSAL_EXIT SAL_EXIT)
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Prefix added to the
comment entered
by User in DP
005 DP_PREFIX_COMMENT process >
This constant has been introduced in versions 7.0 SP8 and 7.5 SP4. The string
maintained in the constant serves as a prefix that is added to all comments
entered by end users while processing DP or blocked invoices. This prefix is not
relevant for the approval process. The constant is not included in the baseline BC
set.

Note: Only the 10 first characters of the constant are considered as prefix.

Set to X to prevent
from simulating all
rules at DP WF
005 DP_START_NO_ALLRULES start

370 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
All business rules are run at the beginning of the DP process to collect the
information for the logging infrastructure. If this is causing performance
problems, by setting this constant value to X, you can switch off the simulation of
the business rules that are placed after the first exception that triggers, that is,
after the initial process type.

Note: The setting does not mean that no rules are run at all.

DP indexing screen
005 DP_VALIDATE_EXIT - validation exit <empty>
This constant allows you to implement custom validation in the DP indexing
screen. Maintain the name of the user exit function module as the constant value.
For more information see Section 8.18.2 “Implementing custom field validation in
the DP indexing screen” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Enter lock message
005 DR_BR_LOCK_MSG for dr br wait <empty>
This constant is part of the program /OPT/DR_BR_WAIT. The default value is
empty. While running the /OPT/DR_BR_WAIT program, if any conflicting lock
occurs, find message ID and message number from the /opt/vim_1bdclog table,
and enter “<message ID>-<message number>” as value for this constant. If more
than one message exists, separate them with :

Example: M8-007:MK-534
005 EDI_CHANNEL_ID EDI Channel ID IDOC
Maintain the channel ID that is used during processing of an incoming IDOC.

Note: This is used only for the direct IDOC processing with the handler
function /OPT/START_DP_WF_FROM_IDOC and not with VIM
Foundation IDOC handler.
EDI visualization/
image archiving
exit (Template: /
OPT/
EDI_IMAGES_EXI
005 EDI_IMAGES_FM T_TEMP)
For more information, see Section 7.6.2 “Rendering IDocs to PDF” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD). This is used only for the direct IDOC processing with the
handler function /OPT/START_DP_WF_FROM_IDOC and not with VIM
Foundation IDOC handler.
Default XML
005 EINV_XML_DOC_TYPE document type

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 371

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
This is the value archive document type, for example /OPT/XML. For more
information, see Section [Link] “Displaying XML documents” in OpenText Vendor
Invoice Management for SAP Solutions - Scenario Guide for Invoice Solution (VIMZ-
CCS).
Set to X to add
functionality
bypass rule to
Apply Rules
005 ENABLE_BYPASS_POPUP process option X
For more information, see Section 8.1.3 “Defining the process type determination
sequence” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
Activate ESR
005 ESR_CHECK_REQUIRED Number Check
For more information, see “ISR Number Mismatch (PO)” on page 237.

Note: ISR processing is not relevant for Swiss invoice process anymore,
therefore OpenText recommends that you disable that process type.
FM Exit to
populate container
in custom rule for
Org Unit based /PTGWFI/
005 EXIT_RULE_RESOLUTION template COA_W_CONT_ELEMENT
You might want to use a custom rule, created in transaction PFAC, and integrate
this rule into OpenText VIM for SAP. A custom rule is always associated with the
custom rule container. To support the integration of the custom rule, you must
implement a custom function module that populates the value of the custom rule
container to OpenText VIM for SAP parameters. You must maintain this function
module in the Z constant 005 / EXIT_RULE_RESOLUTION. You can use the
function module template /PTGWFI/COA_W_CONT_ELEMENT for this purpose.
Partner Roles for
PO Vendor. Use
the values from
table view
V_TPAUM which
are not language
005 EXIT_VEND_PARTN_FUNC specific RS,WL
For more information, see “Vendor Mismatch (PO)” on page 246.
Mapping of line
items for custom FM interface: /OPT/
005 EXT_MAP_LINE_ITEM fields VIM_EXT_LINE_MAPPING
You can use this constant to map custom invoice fields or change line item data
before passing it to the tax calculation functions. The constant value must contain
a function module name. The function module interface must be the same as that
of /OPT/VIM_EXT_LINE_MAPPING.

372 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
Refresh external
tax system memory
005 EXT_TAX_REFRESH before posting <Space>
When using an external tax system, you need to call the function module
EXTERNAL_TAX_DOC_START_PRICING explicitly in OpenText VIM for SAP to
ensure that all tax data is properly updated.

Important
Only activate this constant if you have implemented the latest SAP Notes
for external tax systems, including 1434921 and 1241247.

Activate this constant with value X to ensure that the function module is called.
This updates the data properly.
Move PO number
from list / item to
header in case of
005 FAIL_PO_HEADER_SET exception for PO
This constant is called in function module /OPT/VIM_DETERMINE_PROC_161,
which is used in the business rule Company code mismatch (PO). When this
constant is set to X and when the exception occurs, the first PO with the
mismatching company code will be returned in the PO number field in the
header structure.
Enter X or exit-fm
name. Template: /
OPT/ /OPT/
VIM_COMPL_HID VIM_COMPL_HIDE_TEMP
005 FIORI_COMPLETED_FLAG E_TEMPLATE LATE
This constant is used in the indexing screen data to show or hide the Coding
Completed flag. You can maintain the following values:
• X = Flag is available.
• <space> = Flag is hidden.
• A custom exit function is used to fill the constant.
The template delivered in baseline is /OPT/VIM_COMPL_HIDE_TEMPLATE.
For more information, see Section 5.1.4 “Data pane” in OpenText Vendor Invoice
Management for SAP Solutions - User Guide for Invoice Solution (VIMZ-UGD),
heading G/L Account tab.
Semantic
Navigation: enter V
for vendor number,
005 FIORI_APPR_SEMA P for PO VP
This constant is used in the VIM Approve Invoices Fiori app to show a semantic
navigation link for vendor and/or purchase order.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 373

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
KPA First Pass
value is from
exception config if
true, and from
005 FIRSTPASS_FROMCONFIG 1HEAD if blank <blank>
This Z constant controls configuration details for the Key Process Analytics (KPA)
report. If the Z constant is set to X, the KPA First Pass value is determined from
the exception mapping configuration and workflow data (legacy logic). If it is set
to <blank>, the KPA First Pass value is determined from the header data /OPT/
VIM_1HEAD. In baseline, the default value is <blank>, so the /OPT/VIM_1HEAD
data is used to determine the KPA First Pass value.
Set to X to ignore
minor differences
and typos when
checking tax/VAT
005 FLEXIBLE_TAXID_CHECK IDs <blank>
This Z constant controls flexible tax/VAT ID checks for the process types Invalid
Vendor VAT Number and Invalid Recipient VAT Number. If the constant is set
to X, the check ignores minor differences and typos. The values provided in the
DP document and read from SAP vendor and company code records are
normalized before comparing them. Non-alphanumeric characters and spaces are
removed, a number of replacements is done, for example the check will not
distinguish between O and zero, L, 1 and I, and so on. This prevents the business
rule from returning false positives if an OCR system supplies values that do not
match completely.
Function module to /OPT/
get the Image file C_GET_ARCHIVED_FILE_E
005 FM_GET_IMG_FILE_EXT extention XT
You can use the function module /OPT/CSEND_EMAIL_NOTIFICATION to send an
email with an attachment. The attachment is an archived invoice with a certain
extension. The function module maintained in Z constant FM_GET_IMG_FILE_
EXT is used to get the file extension of the archived file. The default function
module is /OPT/C_GET_ARCHIVED_FILE_EXT.
Freight Amount
005 FREIGHT_AMOUNT tolerance 4
For more information, see
“Freight on Invoice (PO)”
on page 249.
Vendor Payment
005 GET_VEND_PAYM_BLOCK Block Indicators A,B,P
For more information, see “Invalid Vendor (PO)” on page 222.
FM Exit to verify /OPT/
005 GR_CHECK_EXIT GR is done or not VIM_BL_CHECK_GR_EXIT

374 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
GR posting -
Movement
type( actual value
or FM to
determine(ex-
005 GR_MOVEMENT_TYPE FM:xxxxxxxx) ) 101
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Exit in GR post
BDC FM (Ex FM:/
OPT/
DPPO_GR_BAPI_P
005 GR_POST_BAPI_EXIT OST_EXIT)
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
GR BDC id & PO
invoice BDC ID
005 GR_PO_POST_BDC_ID (EX: 00037:00006) 00037:00006
The value maintained in this Z constant provides the ID number of the BDC for
creating the GR and the BDC for posting PO invoices in the form GR_BDC_
ID:POST_PO_BDC_ID. The Z constant is called in function module /OPT/DPPO_
GR_INVOICE_BAPI_POST. The corresponding GR BDC is called to post the GR in
background. After the GR is posted successfully, the Post BDC is called to post
the PO invoice in background.
Default value is 00037:00006, that means BDC 37 is used for posting the GR and
BDC 6 is used for posting the PO invoice.
Enables writing
Capture Analytics
data at the process
005 IES_ANALYTICS_PR_END end. not set
This constant enables writing Capture Analytics data at the end of the OpenText
VIM for SAP process. Set to X if the call needs to be performed. This constant is
not delivered as configuration. You must configure it yourself if you want to use
Capture Analytics. For more information, see Section [Link] “Enabling the
Capture Analytics calculation” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
URL to show
Configuration
Documentation for
005 IMG_DOCU_URL IMG [Link]

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 375

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Vendor Invoice not
allowed for more
than X number of
005 INVOICE_DAYS_OLD days old 250
For more information, see “Invoice Older than Allowed (PO)” on page 254 and
“Invoice Older than Allowed (NPO)” on page 287.
KPA Report:
Thresholds for
“First Pass” - Total
005 KPA_TS_1STPASS_NO #
For more information, see Section 30.11.1 “Constant KPA_TS_1STPASS_NO” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
KPA Report:
Thresholds for
“First Pass” -
005 KPA_TS_1STPASS_PERC Percentages
For more information, see Section 30.11.2 “Constant KPA_TS_1STPASS_PERC” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
KPA Report:
Thresholds for
“Total Liability” -
Amounts for
Blocked
005 KPA_TS_LIAB_AMOUNT1 Documents
For more information, see Section 30.11.3 “Constant KPA_TS_LIAB_AMOUNT1”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
KPA Report:
Thresholds for
“Total Liability” -
Amounts for
005 KPA_TS_LIAB_AMOUNT2 Parked Documents
For more information, see Section 30.11.4 “Constant KPA_TS_LIAB_AMOUNT2”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).

376 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
KPA Report:
Thresholds for
“Total Liability” -
Amounts for Pre-
005 KPA_TS_LIAB_AMOUNT3 Process Documents
For more information, see Section 30.11.5 “Constant KPA_TS_LIAB_AMOUNT3”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
KPA Report:
Thresholds for
“Processed/In
Process
Documents” - Total
005 KPA_TS_PROCDOCS_NO #
For more information, see Section 30.11.6 “Constant KPA_TS_PROCDOCS_NO”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
KPA Report:
Thresholds for
“Processed/In
Process
Documents” -
005 KPA_TS_PROCDOCS_PERC Percentages
For more information, see Section 30.11.7 “Constant
KPA_TS_PROCDOCS_PERC” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
User Exit for KPI
Collection to fill
Customer Specific
005 KPI_COLLECT_CUST_EVT Events
The function module maintained in this Z constant is called in form get_tsp_
and_flags of KPI report /OPT/VR_KPI_COLLECTION. Based on a customer logic,
you can implement a custom mapping of all possible events to corresponding
flags and timestamps.
Fieldname to be
updated with
Leasing Contract
Number at Item
005 LEASING_REF_FLDNAME Level XREF3
This Z constant denotes the target field name in SAP document line item (table
BSEG), where the reference to leasing contract number must be written during
posting.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 377

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
Functional module
to perform custom
validations on the
line item indexing
005 LINE_FIELD_CHECK_FM screen /OPT/DP_ITEM_EXTN2
You can use the function module maintained in this Z constant to deliver
additional custom logic for validation of line item data of DP invoices in the
indexing screen.
The function module is called in form validate_fields_lines_1200 of the
include file /OPT/LVIM_IDX_UIF01.
The template for the function module is /OPT/DP_ITEM_EXTN2.
Function module to
change the field
display in the item
005 LINE_FIELD_CONFIG_FM indexing screen /OPT/DP_ITEM_EXTN1
Line item data of PO and NPO invoices can be processed before being displayed
in the indexing screen. Here, you can implement additional custom logic in an
exit to manipulate data. This Z constant is provided to support this purpose.

If the exit function module is maintained, it is called in method MODIFY_ITEM_

BY_EXIT of class /OPT/CL_C_IDX_UI_SCREEN.

Lock the related

POs before
background <empty> (for backwards
005 LOCK_PO_FOR_POSTING posting compatibility)
Several invoices that use the same purchase order might be processed
concurrently. In this case, payment block is sometimes not set when it is expected
if the invoices are posted with standard BDC ID 6. To prevent such problems,
OpenText VIM for SAP can lock the related POs before the background posting.
Set this constant to X to activate the additional locking logic.
This will replace
any original file
(normally XML)
with PDF if
attached, or with
HTM if no PDF is
005 MAIN_FILE_TYPE found. Example value: *;PDF;HTM.
This Z constant controls the file type of the main image assigned in the DP
document and the posted SAP invoice. Use the Z constant if you want to display
attached files (PDF) as main invoice image. For more information, see Section 7.3.2
“Optional configuration” in OpenText Vendor Invoice Management for SAP Solutions
- Scenario Guide for Invoice Solution (VIMZ-CCS).
Main Workflow
Template for
Document
005 MAIN_WF_TEMPLATE Processing WS00275269

378 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
TM Information is
005 MANDATORY_TM Mandatory X
If this Z constant is set to X, the system uses the Transportation Management
(TM) data for posting. That means, while posting using the BAPI, the system fills
the TM table for posting.

If the Z constant is set to <blank>, the system is passing the PO data to the BAPI.

Note: Initially, the system allows the BAPI to post the TM document using
the PO information. Later, SAP makes it mandatory to fill the TM table in
the BAPI for processing TM data.
Maximum DPs
allowed to process
005 MAX_ALLOWED_DPS in workplace 3000
If set to ‘X’, Posting
Period Warning
Message Appears
Only Once in
005 MESS_ONE_TIME_ONLY Indexing Screen <blank>
When this Z constant is set to X, the Posting period xxxx is not open
warning message appears only once when navigating to the Process tab of the
indexing screen. When set to <blank>, the warning message appears every time
the user switches to the Process tab of the indexing screen.
Error to warning in
005 MESSAGE_VALIDATE_TM indexing screen X
This Z constant is used in Transportation Management (TM) data validation in
the indexing screen at screen level. It influences the navigation between the tabs
in the indexing screen.
If set to X, the system throws a warning message during validation, so the user is
able to navigate.
If set to <blank>, the system throws an error message.
This constant is helpful if SAP S/4HANA is integrated with a standalone TM
system.
The Process Type
number for which
the save should
check for the
005 MISSING_MANDATORY mandatory fields 138;238

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 379

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
This constant has been introduced with version 7.0 SP8 / 7.5 SP4. The constant
allows to control when the check for missing mandatory fields is performed when
saving a DP document. It can be used together with the constant
REQUIRED_PROC_TYPE.
• The constant REQUIRED_PROC_TYPE sets the process types whose
activation makes fields mandatory on the screen.
• The constant MISSING_MANDATORY can activate the same check for other
process types. Users are warned that some data is still missing before the
actual Missing Mandatory Information process is triggered.
Set to X to prevent
defaulting the tax
code if it's not
present in the line
005 NO_DEF_LINE_TAXCODE (PO)
During the posting of a PO invoice, if there is no tax code present in the line, the
default value of the tax code, coming from the header or the PO, is used. Set this
constant to X to turn off this behavior.
Message: F5-231
“Terms of payment
changed; Check”-
005 NO_PAY_TERM_MESSAGE Off X
If this constant is set to X, the message “Terms of payment changed; Check” is
suppressed.
If this constant is set to <space>, this message is displayed as it is.
By default, for
Non-PO invoice
posted with LIV
routines (MIRO or
MM-LIV BAPI), the
business object
type in the table /
OPT/VIM_1HEAD
is switched to
BKPF, which may
come into conflict
NO_PO_OBJTYPE_CHANG with existing
005 E processes. <empty>
Set the constant value to X to disable the switching of the BOR type for NPO
invoices.
NO_SYNC_HEADFLDS_NP Invoice header
O field names, will
not be sync'ed with
BSEG after posted
005 (NPO) TAX_CODE,ZFBDT

380 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
In standard configuration, posted SAP document data is written back into the
original DP document. If you want to avoid this data synchronization, set this
constant value to the respective field names. In case of any other value, or if the
constant is missing in the constants table, the synchronization is performed.
The field names that should not be synced after posting are maintained in this
constant with capital letters. If you want to maintain multiple fields, separate
them by comma. Example: TAX_CODE,ZFBDT,TAX_RATE
Invoice header
field names, will
not be sync'ed with
RSEG after posted
005 NO_SYNC_HEADFLDS_PO (PO) TAX_CODE,ZFBDT
In standard configuration, posted SAP document data is written back into the
original DP document. If you want to avoid this data synchronization, set this
constant value to the respective field names. In case of any other value, or if the
constant is missing in the constants table, the synchronization is performed.
The field names that should not be synced after posting are maintained in this
constant with capital letters. If you want to maintain multiple fields, separate
them by comma. Example: TAX_CODE,ZFBDT,TAX_RATE
If set, withholding
tax changes do not
create a message
005 NO_WHT_MESSAGE on indexing screen X
Set to X to suppress the warning message “Withholding tax has changed”.
Restrict allowed
number of line
items in
NR_ALLOWED_LINEITEM background
005 S posting. 1000
This constant is introduced with version 7.5 SP3 (7.0 SP7) to restrict the number of
line items for background posting. This constant can avoid that workflows get
stuck due to background posting time outs. If the number of line items exceeds
the customized value, the workflow is sent to the processor and can be posted
manually.
Custom Number
Range Object for
Document
005 NUMBER_RANGE_OBJECT Processing
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Web Viewer
005 PLUG_IN_OBJECTDISP Customization

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 381

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
This constant provides flexibility in defining which viewer should be used to
show the scanned invoice in the image plugin of the Details pane, for example in
the DP indexing screen. Available values:

<SPACE> (default) or ON
Web Viewer is launched, based on the ArchiveLink standard viewer
configuration, if the ArchiveLink exit for viewers (TOAEX) is active.
Read TOAEX with EXIT_ID = OA_OBJECTDISPLAY_01 AND ACTIVE = X and
use the function module found there (default: /IXOS/OA_X_OA_
OBJECTDISPLAY_01).

OFF
HTML/Native viewer is launched, whether or not the ArchiveLink exit for
viewers (TOAEX) is active.
<Customer function module name>
You can have a custom implementation for the viewer to be launched for the
detail pane. The constant value is considered as the name of a function
module. It is called dynamically. In this case, only check if the function
module exists and do not check TOAEX. The template FM is /OPT/TMP_WEB_
DISP_IMG or /IXOS/OA_X_OA_OBJECTDISPLAY_01.

Note: This is an advanced setting for special requirements.

Wait constant to
handle responses
from simulate FM
in case of PO with
huge number of
005 PO_INV_SIMULATE_WAIT lines. 30 (seconds)
Class name for /OPT/
non-standard PO CL_D_LM_DETERM_PO_M
005 PO_ITEM_MATCH_CLASS item matching class AP2
/OPT/
PO item matching VIM_DBPF_FIND_PO_USE
005 PO_ITEM_MATCH_Exit PO Exit 22.4 SP6 D
Post tax entries for
an Accounting
Document, when 0
005 POST_ZERO_TAXLINES tax code is used <empty>
Set this z constant to X to post tax entries for an Accounting Document, when 0
tax code is used in a GST system. If set to <empty>, 0 tax code entries are not
posted for an Accounting Document in a GST system. By default, the constant
value is <empty>. For more information, see Section 9.3.2 “Tax components in
GST” in OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide for
Invoice Solution (VIMZ-CCS).

382 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
Document Data
Preprocess Exit
005 PREPROCESS_EXIT_FM Function Module
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
/OPT/VIM: Austria:
Check
recipient_vat_no
with limit value for
005 PROC128_CHCK_AMNT gross_amount 10000
This constant allows configuring check amount process type 128 for country AT.
Set to X to filter
proposal using the
vendor from DP
005 PROPOSAL_ONE_VENDOR document
You may want to restrict the proposal search to only those POs that were created
for the vendor specified in the header data of the DP document. Therefore, set
this constant to X. This may help to improve the performance and prevent
problems caused by limited authorizations (for example empty proposal).
Flag - Comment
necessary for
005 REFER_COM_REQ Referral
This constant controls whether comments are required when referring work items
in DP process and Approval. When the constant is set, the referring action
requires a comment. The Comments Required setting of the corresponding
process option for DP processing is ignored.
For more information, see Section 8.8 “Configuring DP process options” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD). This setting is considered if the constant is not set.
/OPT/
User exit for VIM_NOTIF_USER_EXIT_T
005 REMINDER_USER_EXIT reminder report EMP
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
To remove partner
bank type from
indexing data to
avoid it in posted
005 REMOVE_PART_BNK_TYP document X

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 383

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
To avoid separate payments creation when posting in SAP S/4HANA, the partner
bank type needs to be suppressed from OpenText VIM for SAP when posting the
invoice. To do this, set this constant to X. For more information, see “Determine
Bank Data” on page 319.
Reminder mail
005 REM_MAIL_DOCTYPE document type RAW
The format maintained in this constant is used globally for all kind of email
notification, like reminder email notification and approval email notification.
The notification emails can be sent in HTML format with readable formatting and
invoice data presented in the form of HTML tables. To enable this functionality,
you must set this constant to HTM. In the /OPT/VIM_8CX50 transaction, you must
configure the Email Type to be Internet Email.

If you maintain the email template with HTML tags present, set the constant
value to HTM1 to avoid double conversion of the HTML syntax.
Reminder mail
formatting exit
005 REM_MAIL_FORMAT_FM function
For more information, see Section 37.4 “Maintaining a notification email
formatting function module” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
The Process Type
number for which
the required fields
are shown on the
005 REQUIRED_PROC_TYPE screen 138;238
Maintain process types for which mandatory index data header and item fields
should be handled as required input fields during the index screen processing.

Note: This is a table parameter. You can define several lines by specifying
different version numbers ZVER, if one line is not long enough to store all
the values you need. Regardless of the record version number, all entries
maintained for this Z constant are considered.
Option ID to Start
005 RESTART_DP DP Workflow 2014
Maintain the process option that triggers a restart of the OpenText VIM for SAP
document processing workflow.
Split RouteID-
>RouteID1/2:
PlaceOfSplit1/
NoOfDigits1/
PlaceofSplit2/
005 ROUTE_ID_SPLIT NoOfDigits2 9/6/15/4

384 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
For more information, see Section 8.1 “Routing documents with the route ID” in
OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide for Invoice
Solution (VIMZ-CCS)
Return to Vendor:
Document Type for
Archiving the
005 RTV_AR_OBJECT Vendor mail /OPT/HTM
For more information, see Section 22.8 “Maintaining email archiving” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
User exit / function
to retrieve Email
for Return to
005 RTV_GET_EMAIL Vendor
For more information, see Section 22.6 “Maintaining the email determination user
exit” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
Default obsolete
reason for Return 01 (corresponds to the
to Vendor (RTV) baseline obsolete reason
005 RTV_OBSOLETE_REASON option Returned to vendor)

When using the Return to Vendor (RTV) option, DP documents are made
obsolete. The RTV reason and comments are stored in the DP document but the
obsolete reason is not set. With this constant, you can specify which obsolete
reason, a two-character value, will be assigned to such documents. For more
information, see Section 22 “Return to Vendor” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Return to Vendor:
Standard Text
(SO10) for the mail /OPT/
005 RTV_SIGNATURE_NAME signature VIM_SIGNATURE_RTV
For more information, see Section 22.7 “Maintaining the email signature” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Prefix for standard
texts used for
005 RTV_TEMPLATE_PREFIX Return to Vendor /OPT/VIM_RTV
For more information, see Section 22.5 “Maintaining email templates” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD)

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 385

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
Max allowed DP
lines to enable
Single Click Entry
005 SCE_MAX_ITEMS (SCE) 1000
Max allowed pages
005 SCE_MAX_PAGES to enable SCE 1000
The default values for Z constants SCE_MAX_ITEMS and SCE_MAX_PAGES are
provided primarily for backward compatibility. If you are processing large
invoices, review the settings for each invoice. You need to consider the following
factors:
• The number of fields visible in line items
• The number of line items in extreme cases that still need to be processed with
SCE
• The performance of your application servers and end user workstations
(because the data is loaded into the SCE control, running in SAP GUI)

Note: Large invoices with their corresponding data sets cause long run
time and potentially short dumps due to timeouts.
Option Id for
Sending Back to
005 SENDBACK_OPTION Central System 2013
Long Invoice
Reference Number
005 SET_REF_MAPPING_CN for China XBLNR+4(16),BKTXT
If the extracted reference number length is more than 16 characters, the last 16
characters are copied to reference number XBLNR, and the whole number is
copied to BKTXT.
For more information, see Section 7.1.2 “China - XML mapping” in OpenText
Vendor Invoice Management for SAP Solutions - Scenario Guide for Invoice Solution
(VIMZ-CCS)
This constant can be used for other header fields as well (any fields from /OPT/
VIM_1HEAD and /OPT/VIM_2HEAD).
Long Invoice
005 SET_REF_MAPPING_SP Reference Number X10,B25
For more information, see Section 9.9 “Spain” in OpenText Vendor Invoice
Management for SAP Solutions - Scenario Guide for Invoice Solution (VIMZ-CCS).
not set (Z constant entry is
not delivered in baseline
005 SET_TAX_CALC_FLAG configuration.)

386 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
You may need to have the Calculate Tax flag (SAP field BKPF-XMWST) set for
NPO invoices posted in background through baseline BDC 34. Normally this is
not advised but maybe required by your process, for example, for custom reports.
In this case, set this constant to X.

Note: Setting this flag may affect the value calculated for the field Discount
base amount in the posted document. It also may have other side effects.

This constant is introduced with version 7.0 SP7 / 7.5 SP3.

If set, always
display “Ignore IP”
field on indexing
screen for PO
005 SHOW_IGNORE_IP invoice X
Set to X to display the Ignore IP field on the indexing screen (PO based document
types).
If set to 'X', single
line PO will be
matched according
005 SINGLE_LINE_PO_MATCH to setting in BR 109
For more information, see “Unable to Determine PO Line Number (PO)”
on page 226.
If set to 'X', BAPI
posting of OTV
will be possible
without SEPA
005 SKIP_BAPICHECK_SEPA enhancement X
This constant is called when an invoice for an one time vendor (OTV) is to be
posted or parked in background.
Set to X to skip the
check of line-based
tax and the error /
005 SKIP_LINETAX_CHECK OPT/VIM_701 108
Starting recent SAP EHPs (or if corresponding OSS notes are implemented), it is
not possible to post NPO invoices in background anymore using BDC ID 34, if
line by line tax determination is used, because OpenText VIM for SAP does not
support assignment of tax line numbers. The following error is shown: “Line by
line tax determination not supported for background posting”. In case you would
like to skip this check when you are using a user exit to extend the data passed to
SAP BAPI and set tax line numbers yourself, set this constant to X.
To skip the
automatic
population on QR-
IBAN in indexing
005 SKIP_QR_IBAN_AUTO screen

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 387

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
This constant is used in Function Module /OPT/VIM_ICC_DET_PARTBANKTYPE.
Enabling this avoids the automatic population of bank data from vendor master if
the bank data has QR-IBAN.
If set to 'X', BAPI
posting of OTV
will be done
005 SKIP_SWIFT_SEPA without SWIFT X
You can use this constant to switch between two options during one time vendor
(OTV) processing. You can use setting X to avoid technical account numbers if
SAP is not configured to use them.
Skip Tax Code
Determination (A:
in approval, I:
005 SKIP_TXJCD_DETERM Indexing, X: both)
With version 7.5 SP5, this constant is introduced for customers who do not want
tax jurisdiction code (TJC) to be determined.
Possible values:
I: No TJC determination in the Indexing Screen
A: No TJC determination in Approval
X: No TJC determination at all

Set to X to allow
posting if
VATDATE is used
but cannot be
passed into
005 SKIP_VATDATE_CHECK document
This constant allows to bypass checks relevant for VAT Date in posting functions.
For more information, see Section 8.16.3 “Maintaining Z constant 005 /
SKIP_VATDATE_CHECK” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
SMART_CODE_LM_PROCI Smart coding logic
005 D module Process id N_SPEC_005
This constant is introduced for the smart coding logic module for validating field
input in the AFS ID configuration transaction. For more information, see Section
20.2 “Skipping the coder level in smart coding line automation” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Smart coding line
item proposal
005 SMART_CODE_MODEL confidence level 80

388 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
This constant is provided to maintain the confidence level of cost items and for
each DP invoice item. Only lines above this confidence level are proposed in
smart automation. The default value is 80 %. For more information, see Section
20.1.1 “Smart coding cost line items enrichment in background” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
PO posting BAPI:
'X' to split amount
SPLIT_AMOUNT_OVER_G over GR, ' ' to skip
005 R amount split
If there are multiple GRs and no delivery notes can be considered, the amount is
split over GRs. If this logic is not wanted, this Z constant is introduced to switch
the feature off.
If set to 'N', invoice
items will not be
sync'ed with BSEG
SYNC_ITEM_PARKED_NP after parking
005 O (NPO)
In standard configuration, parked SAP document line item data is written back
into the original DP document. If you want to avoid this data synchronization, set
this constant value to N. In case of any other value, or if the constant is missing in
the constants table, the synchronization will be performed.
If set to 'N', invoice
items will not be
synced with RSEG
005 SYNC_ITEM_PARKED_PO after parking (PO)
In standard configuration, parked SAP document line item data is written back
into the original DP document. If you want to avoid this data synchronization, set
this constant value to N. In case of any other value, or if the constant is missing in
the constants table, the synchronization will be performed. For more information,
see Section [Link] “OpenText VIM for SAP configuration restrictions” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
If set to 'N', invoice
items will not be
sync'ed with BSEG
after posting
005 SYNC_ITEM_POSTED_NPO (NPO)

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 389

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
In standard configuration, posted SAP document line item data is written back
into the original DP document. If you want to avoid this data synchronization, set
this constant value to N. In case of any other value, or if the constant is missing in
the constants table, the synchronization will be performed.

Note: This Z constant is not valid for BDC 2200 because for NPO
documents, after background posting is completed using BDC 2200, MM
Document GL Reference line items are written back into the original DP
document.
If set to 'N', invoice
items will not be
synced with RSEG
005 SYNC_ITEM_POSTED_PO after posting (PO)
In standard configuration, posted SAP document line item data is written back
into the original DP document. If you want to avoid this data synchronization, set
this constant value to N. In case of any other value, or if the constant is missing in
the constants table, the synchronization will be performed.
Process Type to
read the initial role
when sending back
005 SYSTEM_HANDLE_PTYPE to central system 171
When a document is being sent from a satellite back into central system, the
initial role of the workflow is set to the value that is read from the process type
settings that are maintained in the satellite. Set that process type in this constant.
Tax on vendor line
005 TAX_ON_VENDOR_LINE item in FB60 <blank>
Set the value to X if non-PO invoices posted with the BDC ID 34 must have their
tax amounts added into the vendor line item instead of accounting line items.
Set to X to enable
the logic to support
special processing
of goods invoices
between EU and
Northern Ireland.
Can be set to a
function module
name to extend the
005 UK_NI_CHARACT logic. not set
For more information, see Section 9.5 “Northern Ireland” in OpenText Vendor
Invoice Management for SAP Solutions - Scenario Guide for Invoice Solution (VIMZ-
CCS).

390 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
Do not write
change docs in fm /
OPT/
VIM_CD_IDXDAT
A ('X' = no change
005 UPDAPI_NO_CHG_DOCS docs)
Using this constant, you can disable the creation of change documents for DP
data.

Important
• The automation report depends on change document data. If this
constant is set, the automation report will cancel with an error message.
• The Ariba integration depends on change document data. If the Ariba
package is installed in the system, this constant will have no effect.

Set to X if line item

data has to be sent
into SAP tax
005 USE_ITEMDATA_FOR_TAX calculation <blank>
This constant enables the passing of item data into tax calculation functions. This
may be needed for US company codes for which an external tax system is used.

Note: Valid for BDC 34 only.

Set tax item links

according to OSS
005 USE_ITEM_COUNTER Note 1692637
Setting this constant to X enables the use of tax item counters for line-by-line tax
calculation according to SAP OSS Note 1692637.

Note: Valid for BDC 34 only.

Set to ‘X’ to
transfer indexing
screen wht amount
value to posting. If
empty the wht
amount is
calculated from
005 WHTAX_AMT_TR wht base amount.
For more information, see Section 21 “Extended withholding tax” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 391

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
Set to ‘X’ to hide
extended
withholding tax
data in indexing
screen and to use
SAP values during
005 WHTAX_FROM_SAP posting.
For more information, see Section 21 “Extended withholding tax” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Calculate
withholding tax net
base from gross
amount/tax code (X
= calculate, ' ' = use
005 WHT_CALC_NET header net amount) X
For more information, see Section 21 “Extended withholding tax” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Exit FM for wht
005 WHT_EXIT_BAPI data BAPI transfer
User Exit for customer specific determination whether withholding tax data is
transferred to background posting from OpenText VIM for SAP or from SAP. The
template for this function module is /OPT/VIM_WT_BAPI_TRANS. For more
information, see Section 21 “Extended withholding tax” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution
(VIMZ-CGD).
'X' to display WHT
Payment posting
005 WHT_PAY_AMT Tax amounts X
Payment type withholding tax: set to X to provide withholding tax amount in
indexing screen and posting. For more information, see Section 21 “Extended
withholding tax” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Set to X to post
zero WHT amount
if WHT code is not
005 WHT_POST_ZERO entered X

392 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
This constant must be set to X to enable posting some lines of withholding tax
with zero values, even if the value calculated according to customizing is not
zero. To post zero withholding tax amount for a specific withholding tax line, you
need to remove the corresponding withholding tax code in the DP indexing
screen. In this case, the line will still be posted by OpenText VIM for SAP with
withholding tax code, found using the withholding tax type entry in the
respective vendor master record. However, the tax amount value will be set to
zero and the zero flag in SAP PO BAPI will be set according to the OSS note
1803535. For more information, see Section 21 “Extended withholding tax” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
This constant has been introduced with version 7.0 SP6.
FM for Dashboard
Workitem Text: /
OPT/ /OPT/
BL_IF_DETERMIN BL_IF_DETERMINE_WI_TE
005 WI_TEXT_FM E_WI_TEXT XT
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Propose payment
terms from
alternate/permitted
005 ZTERM_FROM_PAYEE payee X
This constant is checked when payment terms are to be derived from the master
database.
Archive Object for
005 ADDL_DOCS_AR_OBJECT Other attachments /OPT/OTHER
Set to the archiving document type that must be used for attachments, for
example in inbound documents. OpenText recommends that you use an
archiving document type allowing all MIME types (*) unless you want to restrict
that to one specific file type.
Screen for selecting
the DP NPO
DPNPO_APROVER_SELEC Requester/
005 T Approver /ORS/SAPL000007_DP:8000
Screen for selecting
the DP PO
Requester/
005 DPPO_APPROVER_SELECT Approver /ORS/SAPL000007_DP:8000
FM for
manipulating the
item text in the
header - DPPO /OPT/
005 DPPO_BAPI_ITEM_TEXT (BSEG-SGTXT) VIM_BAPI_UE_ITEMTEXT

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 393

Chapter 39 Z constants for product code 005

Product Constant Description Default Value

Code
Task number of the
DP_DASHBOARD_TASK_I DP document
005 D dashboard TS00275278
Delimiter for
005 DUP_CHECK_DELIMIT duplicate check /-
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Function Module /OPT/
for changing mail C_EXT_MAIL_BODY_HAN
005 EXIT_MAIL_BODY body template DLER
For more information, see Section 10.4.10 “Configuring the email notification” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Invoice statuses
that need workflow
to be started -
005 LIST_WF_STATUSES VIM5 ABCD
For more information, see Section 8.3.3 “Parking directly in MIRO or Fiori to start
a OpenText VIM for SAP process” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
DP Non PO
posting - Default
005 NPO_DOCTYPE_DEFAULT document type KR
Default FI document type to use for posting, if not maintained in the DP
document type definition. For more information, see Section 8.1.1 “Creating a
new DP document type” in OpenText Vendor Invoice Management for SAP Solutions
- Configuration Guide for Invoice Solution (VIMZ-CGD).
OCR Currency
005 OCR_CURRENCY_FIELD Field InvoiceCurrency
This constant sets the list of mapping fields where the currency code is read from.
This must correspond to the capture extraction logic and to mappings used for
inbound documents. Field names must be listed separated with commas, without
spaces. Example: InvoiceCurrency,WAERS. For more information, see Section
7.2.2 “Configuring the Capture integration for OpenText VIM for SAP classic
mode” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
Transactions
supported in MIRO
005 TCODE_ON_BADI BADI MIRO, MIR7, MR1M
This constant enables proper creation of a DP document when an invoice is
created from a third party transaction or custom transactions. The default value is
set as MIRO,MIR7,MR1M. You can add custom transactions in the Value tab which
then creates corresponding DP documents.

394 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
Siret Number field
on the Vendor
005 VENDOR_SIRET_NO_FLD Master STCD1
For more information, see “Invalid Siret Number (PO) (France)” on page 239.
Field for Tax Code
005 VENDOR_TAX_CD_FIELD in Vendor Master STCD1
This constant is used if the DP document type is set to use the tax code from
vendor master. The field name corresponds to one of the Tax Number N fields in
the Control screen of transaction XK02.
This constant may have limited use when Business Partner functions are used to
maintain vendor data. For more information, see Section 9.1.3 “Determining the
tax code” in OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide
for Invoice Solution (VIMZ-CCS).
The plants for
which workflows
will be triggered; *
means all plants. -
005 WFTRGPLANT VIM5 *
For more information, see Section 8.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 395

Chapter 40
Z constants for product code IAP

Product Constant Description Default Value

Code
Function Module
for accounting field
IAP ACCT_CHECK_FM status group check
The custom function module maintained in this Z constant can be called in
method VALIDATEACCTDATA of class /ORS/NON_PO_INVOICE_NEW to provide
more validation checks to the accounting data.
This additional check takes place in the approval process.
Bear in mind that the additional check implemented in that way will not be
executed while posting with /OPT/DNONPO_INVOICE_BAPI_POST.
Example: Function Module /ORS/000007_VALIDATE_FSG
The constant has been introduced in version 6.0 SP8 / 7.0 SP3.
Flag: Allow passive
substitute to
IAP ALLOW_PAS_SUB approve invoices
If this constant is set to X, the passive substitute is allowed to process the
approval items. The adopting user must be maintained in the COA.
Set to X for asterisk
in COA to match
IAP AST_ALLOWS_SPACE space <empty>
With this constant, you can choose whether the asterisk will match an empty
invoice field or not.
Without the constant enabled, for lines with empty cost elements, OpenText VIM
for SAP will propose any existing coding agent to allow the coding process to
continue.
With the constant enabled, users that have COA records with asterisks are
excluded from the search. This means, the line is not empty for them anymore
because the asterisk fills the space.
For more details, see Section [Link] “COA Details View” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution
(VIMZ-CGD).
BALANCE_MESSAGE_TYP
IAP E X - Sets to Error E

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 397

Chapter 40 Z constants for product code IAP

Product Constant Description Default Value

Code
Possible values are E or W. If value is not set, E is assumed.
W - Warning: shows the balance issues and allows to continue.
E - Error: shows the balance issues and stops the process until balance is
corrected.

You can decide whether you want a balance problem to be a warning or an error.
This affects both the internal OpenText VIM for SAP check and also the optional
SAP BAPI validation check.
If you configure it to be a warning, even errors returned by SAP BAPI are
considered as warning. In this case, it does not stop the user from sending the
invoice further.
BDC Function to /ORS/
Be Called to Write 000007_NPO_SAVE_CODIN
IAP BDC_FUNCTION to Database G
For more information, see Section 20.6.4 “Changing BDC IDs” in OpenText Vendor
Invoice Management for SAP Solutions - Scenario Guide for Invoice Solution (VIMZ-
CCS).
BDC function to be
called to write to /ORS/
IAP BDC_FUNCTION_PO database 000007_PO_SAVE_CODING
This constant sets the function module that will be used to save parked PO
invoice accounting information.
Bulk approval/
reject invoice
validation (Ex
FM: /ORS/
AINV_BULK_VAL
IAP BULK_VALIDATE_EXIT IDATE_INV)
For more information, see Section 10.12.5 “Configuring the bulk approval
validation exit” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Calculate tax on
net amount option
for DP approval
IAP CALC_TAX_ON_NET ('X' or ' ' or 'D')
For more information, see Section [Link] “Configuring tax calculation on net
amount” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
Cancel DP, Appr
wfs If Inv.
cancelled in SAP
(A= Only Post
Appr workflow,
IAP CANCEL_WF_FB08 B=Both) B

398 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
After an invoice is cancelled during posted approval process, this constant
determines the cancellation behavior. Possible values:
<SPACE>: nothing cancelled
A: only approval work item cancelled
B: both work items (approval and DP work item) cancelled

Standard Text
Object to appear as
Approval Certify
Message on Web
IAP CERTIFY_MESSAGE screen ZCERTIFY
For more information, see Section 10.4.11 “Configuring the Certify message” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Check SAP user
validity in COA
IAP CHECK_SAP_USER maintenance
If this constant is not set to X in table /PTGWFI/Z_CONST (or if it does not exist in
the table), the SAP user validity in COA is not checked. To enable the checks, set
the constant value to X.
Check if the
^TXJDC is to be
validated against
IAP CHECK_TXJCD the Cost Object X
Set this constant to X if you are using the BDC 34 to post invoices and you want
OpenText VIM for SAP to compare the tax jurisdiction code entered manually in
the line item with the code retrieved from the account assignment object. If they
are not the same, the standard message F5 532 will be displayed as a warning.
Enable individual
lock logic for COA
IAP COA_INDIVIDUAL_LOCK maintenance
This constant controls the lock logic for the alternative COA maintenance
transaction /OPT/AR_COA_MAINT.
Set the value to X to enable individual locking (grouped by company code, level,
and user).
Clear the value to enable global locking if you are processing large amounts of
data that might lead to reaching the global lock limit.
For more information, see Section [Link] “Maintaining COA - alternative
transaction” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Extended COA line
check for next
approver
determination ('' =
IAP COA_LINE_CHECK_EXT off, 'X' = on)

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 399

Chapter 40 Z constants for product code IAP

Product Constant Description Default Value

Code
This constant is obsolete with version 7.5 and later because the old COA is no
longer supported.
If this constant is set to X, all approval lines are checked against the COA.
Otherwise only the first approval line is checked against the COA.
COA Maintenance:
Validation of Input
IAP COA_VAL_INPUT_FLDS fields
For more information, see Section [Link] “COA Details View” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution
(VIMZ-CGD).
Display invoice
image on display
of dashboard
DASHBOARD_IMAGE_AU screen (X- Yes,
IAP TO space -No) X
If this constant is set to X, the archived image of the invoice is automatically
displayed in a separate screen when the Approval Dashboard is called in the SAP
GUI. Make sure that there is an SAP instance available to display the image,
otherwise an error message is displayed in the status bar.

A user parameter /OPT/DISP_IMAGE_AUTO is introduced. It allows each user to

switch off the auto image displaying functionality individually. If the parameter
is set to N for the user in consideration, the image displaying functionality will be
deactivated globally, not only for the Approval Dashboard, but also for other
dashboards like Indexing or Blocked dashboard.
IAP DASHBOARD_NO_LOGO Display no Logo
If this constant is set to X, the logo is hidden in the Approval dashboard.
To check if
approver is valid /ORS/
IAP DETERMINE_VALID_USR one DETERMINE_VALID_USR
When viewing the image from Fiori or Approval Portal, there is a security logic to
check the authenticity of the user viewing the image. By default, the constant
DETERMINE_VALID_USR is set to function module /ORS/DETERMINE_VALID_
USR. You can enhance your own security logic by creating a function using
template /ORS/DETERMINE_VALID_USR.
UserExit: Display
IAP DISP_INV_IMAGE Invoice Image
This constant can be maintained with a custom FM to display the invoice image
when a user clicks the View Invoice Image button in the Approval Dashboard. If
not maintained, the baseline FM /ORS/000007_DISPLAY_FILES is called to
display the image.

400 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
DP Invoice
approval - Is
validation required
DP_APPROVAL_VALIDAT or not, when data
IAP E is saved?(X- No) X
Set this constant to X to skip the validation in the Approval Dashboard while
performing actions like Save, Forward, Reject, or Return to Inbox. If this constant
is not set, the validation will always be carried out for all actions taken in the
Approval Dashboard.
FM Exit for
calculating all.
Called in FM /ORS/
000007_CALCULA
IAP EXIT_CALCULATE_ALL TE_ALL
When maintained, the custom FM will be called in FM /ORS/000007_
CALCULATE_ALL to handle some values like balance, returned messages
according to the customer needs.
The template of the exit FM is /ORS/EXIT_CALCULATE_ALL.
FM Exit for
filtering BAPI
messages - used in
FM /ORS/
000007_FILTER_B
IAP EXIT_FILTER_APPR_MSG API_MSG
When maintained, the custom FM will be called in FM /ORS/000007_FILTER_
BAPI_MSG to filter out messages as required by customer.
The template for this user exit is FM /ORS/C_EXIT_FILTER_BAPI_MSG.
Search help user /ORS/
exit with Pre-filled SEARCH_HELP_FIELDS_PR
IAP EXIT_SEARCH_HELP_FLT values EFIL
For more information, see Section 7.7.3 “Configuring search helps with pre-filled
values” in OpenText Vendor Invoice Management for SAP Solutions - Administration
Guide (VIMZ-AGD).
Get TXJCD from
Company Code
IAP GET_TXJCD_BUKRS Table: T001 X
If this constant is set to X or does not exist in the customizing table, OpenText
VIM for SAP will retrieve the tax jurisdiction code from the company code data
and use it for line item. Set the constant to blank if you do not want the tax
jurisdiction code to be overwritten with the one from company code.
Get TXJCD from
Vendor Master
IAP GET_TXJCD_LFA1 Table: LFA1 X

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 401

Chapter 40 Z constants for product code IAP

Product Constant Description Default Value

Code
If this constant is set to X or does not exist in the customizing table, OpenText
VIM for SAP will retrieve the tax jurisdiction code from the vendor master data
and use it for line item. Set the constant to blank if you do not want the tax
jurisdiction code to be overwritten with the one from vendor master.
Override Coding
IAP GL_ACC_SCR_EXIT Fileds attributes
Evaluation Path
IAP HR_EVALUATION_PATH Maintenance
In the function module /PTGWFI/GET_USERS_OF_ORG_UNIT, the evaluation path
SAP_TAGT is passed by default into the FM HRWPC_STRUC_GET_MULTIPLE_
ROOTS. So you cannot pass your own evaluation path.
Using this constant, you can define your own evaluation path and pass it into the
FM. You can create the user-defined function module using the template /OPT/
HR_EVALUATION_PATH.

Set to X to enable
multiple account
assignment
IAP MULTI_ACCT_ASSIGN elements in COA
Setting this constant to X enables the use of multiple cost elements for a COA line
and makes the authority checks logic similar to versions 5.2 and 6.0. For more
information, see Section 4.1.4 “Maintaining Chart of Authority” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Data validation
required during
coding for parked
PARK_CODE_VALIDATIO doc(X-yes,space -
IAP N No) X
When this Z constant is set, the data validation is executed before the data of a
parked invoice is saved or approved. This constant is checked in the function
modules /ORS/000007_NPO_SAVE_CODING and /ORS/000007_NPO_SAVE_
CODING2.

PO park approval -
Accounting data
editable or not (X-
Editable, Space -
IAP POPARK_APPR_ACCTEDIT no) X
When this Z constant is set, the accounting data of PO parked invoices is editable
in the approval screen. Otherwise it is not editable.
Indicator, if set ->
Maintaining
PORTAL_NOTMAINT_SUB Substitute in Portal
IAP S is not allowed

402 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
The Substitute maintenance on OpenText Approval Portal can be disabled from
ABAP side. Therefore, you must maintain the Z constant PORTAL_NOTMAINT_
SUBS and set the constant value to X.

Enable PO Lines
IAP PO_ACC_SCR_EXIT for coding
This constant allows to enable coding for PO lines in the Invoice Approval in SAP
GUI. Implement a custom function module. Enter the name of your custom
function module in the constant value.

This Z constant is used to modify screen attributes (input/read-only) for specific

fields. The general edit (coding) mode must still be modified using the custom
approver class, as described in Section 10.12.2 “Defining the custom approver
class” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
Number of days to
wait for the
Recipient to
provide
IAP REFERRAL_WAIT_TIME information 10
For more information, see Section [Link] “Configuring the wait time for
inquiries” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
Set priority for
email notification
in Invoice
IAP SET_EMAIL_PRIORITY Approval process 2
If the priority value is set in this constant, the email notification is sent according
to the priority defined. If this constant is not set, the priority will be 1 (highest
priority).
Enable the display
of DP comments in
[Link]: D=detail
only, I=detail and
IAP SHOW_DP_COMMENTS inbox <blank>

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 403

Chapter 40 Z constants for product code IAP

Product Constant Description Default Value

Code
To enable the display of the DP comments together with the approval comments,
set the constant value to D or I.

If it is sufficient to display the DP comments of the approval history in the invoice

detail page only, set the constant value to D. OpenText recommends this value.

If it is necessary to display the DP comments also in the invoice list page

(“Inbox”), set the constant value to I.

Notes
• Setting the constant value to I may result in longer load times of the
invoice list.
• The setting I is used only on version 7.0 Approval Portal, “old” UI.
Everywhere else, it has the same effect as the setting D.
If set to 'X',
accounting data
will not be
validated in
Coding / Approval
by simulating the
IAP SKIP_BAPICHECK posting with BAPI. X
For more information, see Section [Link] “Activating and deactivating approval
validation” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
If set to 'X' skips
Message KI 339
“Profit center was
IAP SKIP_PROFIT_CTR_MSG set to xxx” X
During the approval process, on the SAP GUI approval screen, message KI 339
“Profit center was set to xxx” cannot be disabled. When GL lines have different
cost centers, users are forced to click this message several times. To avoid this
behavior, set this Z constant to X.
Subscreen Number
for Usermap
Maintenance
IAP UMUTIL_SUBDYNP Utility 100
The subscreen maintained in this Z constant is used as the initial screen when
calling the Reassignment Utility (transaction /ORS/UMREASSIGNED). See Z
constant UMUTIL_SUBPROG.
Subscreen Program
for Usermap
Maintenance /ORS/
IAP UMUTIL_SUBPROG Utility 0000007_UMUTIL_DYNP
The program maintained in this Z constant in conjunction with Z constant
UMUTIL_SUBDYNP determines which initial screen is triggered when calling
the Reassignment Utility (transaction /ORS/UMREASSIGNED).

404 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
IAP USE_ALT_APPROVERS A
For more information, see OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Substitution Profile
for OpenText VIM
IAP USE_SUBS_PROFILE for SAP
Maintain the Substitution profile for OpenText VIM for SAP workflows in the
value of this constant. For more information, see Section [Link] “Override,
delegation, substitution, and reassign” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
Approval
Workflow Task
IAP APPROVAL_TASK Number TS00275253
For this constant value, maintain the name of the dialog task in the approval
workflow. Used, for example, in the reminder program to search for open
approval tasks.
Approval
Workflow
IAP APPROVAL_WORKFLOW Template Number WS00275252
For this constant value, maintain the name of the approval workflow template.
Whenever an approval workflow instance needs to be created, OpenText VIM for
SAP will use the provided template name. The workflow container values are
populated according to the needs of standard template WS00275252.
APPROVAL_WORKFLOW_ Approval
PA Workflow
Template Number
(SubWF LBA
integration)
IAP WS00275253 WS00275253
This is an internal parameter, which is used in the approval workflow. Do not
change this parameter.
Approver Class /OPT/
IAP APPROVER_CLASS Extension CL_IAP_APPROVER_BL
This constant is obsolete in the context of NPO invoice approvals because simple
approval is no longer supported with version 7.5 and later. It is still used for PO
invoice approvals. For more information, see Section 10.12.2 “Defining the
custom approver class” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Function module to
determine if
comments are
required after
IAP APPR_COMMENT_NEED Approval/Rejection

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 405

Chapter 40 Z constants for product code IAP

Product Constant Description Default Value

Code
Name of the function module to be called to decide if comments are required on
approval. See the function /ORS/COMMENT_REQUIRED for interface and logic
example.
Exit to download
data from file
(TMP - /OPT/
COA_UPLOAD_E
IAP COA_UPLOAD_EXIT_DW XIT)
For more information, see Section [Link] “COA upload report” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Exit to upload data
from file (TMP - /
OPT/
COA_UPLOAD_E
IAP COA_UPLOAD_EXIT_UP XIT)
For more information, see Section [Link] “COA upload report” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Doc types for
Credit Memos
CREDIT_MEMO_DOC_TYP (Separated by
IAP E comma) KG
List of SAP FI document types that correspond to credit memos. This is used in
invoice data reading modules to decide on further processing logic.
Set in user
preference table. REF_DOC_NO,RECEIPT_D
Default fields to be ATE,VENDOR_NAME,ORT
shown on the 01,DUE_DATE,INVOICE_A
IAP DEFAULT_INV_LIST invoice list. MT,CURRENCY
Configure the
message to be
display when no
coding is entered
IAP EMPTY_CODING_MSG (Validateacctdata) CHECK_SP:ERROR
For more information, see Section 10.9.2 “Optional coding” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution
(VIMZ-CGD).
Exit function for
IAP EXIT_INVOICE_ACTION Invoice Action /OPT/OAP_EXIT_ACTION
For more information, see Section [Link] “Configuring exits” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).

406 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
Exit function for
IAP EXIT_INVOICE_DETAIL Invoice Detail /OPT/OAP_EXIT_DETAIL
For more information, see Section [Link] “Configuring exits” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Exit function for
IAP EXIT_INVOICE_LIST Invoice List /OPT/OAP_EXIT_LIST
For more information, see Section [Link] “Configuring exits” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Extended Ext_data
Class /ors/ext_data
IAP EXT_DATA_CLASS when not extension /ORS/EXT_DATA
You can use this constant to configure baseline class /ORS/EXT_DATA, in order to
use the rejection comment and also the rejection reason. For more information,
see Section 10.4.7 “Defining rejection reasons” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Ext IE RPT -
Loading data in
Class /ORS/
APPR_LOG_OBJE 000007_5_IE_RPT_APPR_LO
IAP EXT_IE_RPT_APPR_LOG CT G
Function module that is called during approval steps to update VIM Analytics
data tables with the information about performed actions. This constant is for
internal use. It was created for versions when VIM Analytics was an optional
component. Normally, do not change it from its standard value.
Ext IE RPT -
Loading data in
Business Object /ORS/
IAP EXT_IE_RPT_INVAP Type INVAP 000007_5_IE_RPT_INVAP
Function module that is called for each approval step to update VIM Analytics
data tables with the current approver information. This constant is for internal
use. It was created for versions when VIM Analytics was an optional component.
Normally, do not change it from its standard value.
If set to 'X', name of
substituted user is
shown on Fiori
IAP FIORI_BEHALF_NAME screen
Set to X to show the name of the substituted user in Fiori apps: Approve Invoices.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 407

Chapter 40 Z constants for product code IAP

Product Constant Description Default Value

Code
If set to 'X', will
allow reading Last
Processed User and
Comments
information for
IAP FIORI_BULK_PROCESS Bulk Fiori app
If set to X, Last Processed User and Comments information is displayed in the
Approve Invoices (bulk mode) app.
X reserves the
WorkItem, empty
unreserves and
used for only Fiori
IAP FIORI_WORKITEM_RESER Access X
“Fiori interface” in this constant refers to the following VIM Fiori apps:
• VIM Approve Invoices Fiori app
• VIM Enter Cost Assignment Advanced Fiori app
This constant is intended for customers using only the Fiori interface and
specifically the substitution case, where the unreserve feature is not available in
Fiori. This constant switches off the reservation of the work item for the
substitution user.
Many OpenText VIM for SAP customers use both SAP GUI and Fiori interfaces
for substitution. Therefore this constant’s value is set to X by default, which
means that work items are reserved.
If you use only Fiori and do not have the option to use SAP GUI, set this constant
to <empty> to unreserve the work item.
/ORS/
Image Delete URL 000007_TMP_IMAGE_DEL_
IAP IMAGE_DEL_URL_FM FM URL
/ORS/
Image Display 000007_TMP_IMAGE_DISP_
IAP IMAGE_DIS_JPG_FM JPEG generate FM JPG
For more information, see Section 10.12.1 “Configuring image display” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
/ORS/
Image Display 000007_TMP_IMAGE_DISP_
IAP IMAGE_DIS_URL_FM URL generate FM URL
For more information, see Section 10.12.1 “Configuring image display” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Supported
IAP LANGUAGE language E,D,F,S,P,N,J,I

408 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
This constant is used in different approval scenarios:
For OpenText Approval Portal, it sets the languages available for the user. For
more information, see Section [Link] “Defining supported languages” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD) and Section [Link] “Configuring additional
languages” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIMZ-AGD).
For all scenarios (SAP GUI approval, Approval Portal and Fiori apps), it also sets
alternative languages to use when reading existing comments, if the comments
are not found in the current user language.
Seconds that
invoice lock will be
valid (Called from
object /ors/
IAP LOCK_DURATION invoice_lock) 1800
Set the life time of the invoice lock, to prevent processing of the same invoice by
multiple users. Standard value is 1800 seconds. Values less than 300 seconds are
ignored, a minimum of 300 is forced in such cases.
E=email ID;
S=sequence #;
N=.NET ID and
IAP OPTUSERID_DETERMING Domain; P=EP6 ID E
When you add a new user in the User Details tab in the COA, the OpenText User
ID is determined. This constant specifies how the OpenText User ID is
determined. Possible values:
E: by Email
S: by Sequence where the sequence number should be generated from the defined
number range (/ORS/USRMP)
N: by .Net ID and Domain
P: by EP6 ID

Popup window to
display company
code selection for /ORS/
cross company 000007_POPUP_COMPANY
IAP POPUP_COMPANY_CODE invoice approve _CODE
For more information, see Section 10.4.9 “Cross company coding” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
Extended PO
Invoice Class
(Called in
Approval =>
GET_PO_INV_CL
IAP PO_INV_CLASS ASS) /ORS/PO_INVOICE_NEW

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 409

Chapter 40 Z constants for product code IAP

Product Constant Description Default Value

Code
This constant is obsolete in the context of NPO invoice approvals because simple
approval is no longer supported with version 7.5 and higher. It is still used for PO
invoice approvals. For more information, see Section 10.12.3 “Defining the
custom invoice class” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
Class /OPT/PO_INVOICE_22_4 can be used for optimizations. For more
information, see Section 10.4.4 “Configuring approval flow settings” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
/ORS/
Class: Processed By INVOICE_PROCESSED_BY
IAP PRC_BYME_CLASS ME ME
Class: Non PO
Invoice Proc for /ORS/
IAP PRC_BYME_CLASS_NPO Processed By ME NON_PO_INVOICE_PROC
Class: PO Invoice
Proc for Processed
IAP PRC_BYME_CLASS_PO By ME /ORS/PO_INVOICE_PROC
2 fields: rejection
rsn ; comments( 1 =
mandatory and 0 =
IAP REJECTION_REASON optional) 0;1
For more information, see Section 10.4.7 “Defining rejection reasons” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide for Invoice
Solution (VIMZ-CGD).
IAP SAP_PROXY_ID SAP proxy ID SAP_WFRT
This constant is multiply used. It sets the SAP user ID to which the dialog
approval task is sent if the next approver does not have an SAP user ID. It also
controls the logic used at several locations that requires identification of the
workflow background user, for example searching for log entries of the steps that
run in background.
For more information, see Section 2.1.2 “Verifying workflow background user
setting” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
/OPT/
IAP USERMAP_CLASS CL_IAP_USERMAP_BL
This constant is obsolete in the context of NPO invoice approvals because simple
approval is no longer supported. It is still used for PO invoice approvals.

410 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

Chapter 41
Z constants for product code IEM

Product Constant Description Default Value

Code
Constant for
determining due
IEM CALCULATE_DUEDATE date FM not set
Function module to call for due date calculation in Liability Report and
Notifications Report
FM for currency
IEM CURRENCY_CONVERSION conversion not set
Function module to call for currency amount conversion in Liability Report
IEM DISPLAY_LOGO Logo image name /PTGWFI/DCHENLOGO
Tran code used to
display all LIV
invoices during
drilldown
IEM INVOICE_DISPLAY_LIV reporting MIR4
Tran code used to
display parked CIV
invoice during
drilldown
IEM INVOICE_DISPLAY_PIR reporting FBV3

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 411

Chapter 42
Z constants for product code LIX

Product Constant Description Default Value

Code
If set to X, only
items with same
[Link] can be
ended on hdr level
LIX AUTH_SAME_BLKREASON decision.
Area: OpenText VIM for SAP Blocked PO invoice workflows (line item level)

You may want to apply the same “Authorize”-type action to all line level
workflows of a blocked invoice. You also may want the action to apply only to
the other workflows with the same payment block as that of the current work
item. (Previously, up to and including version 5.2 SP10, all other workflows
would be cancelled and the header workflow started if you confirmed the
corresponding dialog question.)

If you need the workflows with other payment blocks to remain active, set the
constant value to X. The default configuration delivered with OpenText VIM for
SAP will have the old logic of cancelling all line level workflows of the invoice
(the constant value is blank).
Display invoice
image on display
of dash board
DASHBOARD_IMAGE_AU screen (X- Yes,
LIX TO space -No)
Set to X if invoice image must be displayed automatically when blocked invoice
dashboard is opened.
LIX DASHBOARD_NO_LOGO Display no Logo
If this constant is set to X, the logo is hidden in the parking and blocking
dashboard for PO invoices.
Exit FM to
influence the
LIX DB_OPTION_SEQ dashboard buttons
You can set a custom function to change the sequence of process options in the
dashboard. For the interface of the function, check the Release Notes of version
7.0 SP3 or 6.0 SP8.
Use old Delete and
Re-enter sequence
(duplicate error): 1.
LIX DELETE_ENTER_OLD Delete, 2. Re-enter

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 413

Chapter 42 Z constants for product code LIX

Product Constant Description Default Value

Code
During the Delete and Reenter process, by default the document is first created
and afterwards cancelled or deleted. If this constant is activated with X, the
document is first cancelled or deleted and afterwards created, to avoid duplicate
check conflicts.
FM to select
distributed account
assignment data
LIX PO_MULTIK_FM for item
Function module to perform split account assignment instead of the standard
logic, during the posting of PO invoices with the BDC ID 6.
WF relevant
LIX WFDOCTYPE document types *
This constant is used in the receiver function modules, for example the block
receiver (/OPT/VIM_RPT_PO_INV_RECEIVER), the post receiver, or the park
receiver.
According to the configured SAP document type, it is checked against the
document type of RBKP (for example, in case of PO, in /OPT/VIM_RPT_PO_INV_
RECEIVER) if the routine to update data in VAN should be executed.
In very old OpenText VIM for SAP versions (before SAP reselling), VAN was an
extra component that customers had to pay for. Hence there was an option to
configure when VAN should be updated or used according to the SAP document
type.
Possible values are SAP document types, for example KR, RE, or KG. Baseline
always sets this value to * because there are other options to decide how
OpenText VIM for SAP should be triggered and used.
Active plants (WF
LIX WFTRGPLANT relevant) *
Workitem Text
crreation FM (Refer
FM: /OPT/
BL_IF_SET_WI_TE
LIX WI_TEXT_FM XT)
Function module
exit for processing
block reasons in
invoice verification /PTGWFI/
LIX BLK_REASON_EXIT_FM subwf LIX_F_UPD_BLK_REASONS
FM to create
invoice in case of
Delete/Cancel and /PTGWFI/
LIX CREATE_PO_BDC_FM Re-enter option VIM_CRE_PO_INV
Custom function to be used to recreate a PO invoice after cancelling

414 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
FM exit in the
Binding FM for the
DB step - at the
time of Inward
LIX DB_BIND_EXIT_FM1 binding
For more information, see Section 9.3.5 “Configuring header level dashboard
binding exits” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
FM exit in the
Binding FM for the
Dashboard step - at
the time of
LIX DB_BIND_EXIT_FM2 outward bindin
For more information, see Section 9.3.5 “Configuring header level dashboard
binding exits” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
FM exit in the LIX
DB step int he BD
method when
Sendback is done
LIX DB_SNDBACK_EXIT successfully
For more information, see Section 9.3.6 “Configuring the send back functionality
exit” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
Header Level
HEADERLEVELWORKFLO Workflow ID
LIX W WS99680014 WS00275266
Function module to /PTGWFI/
LIX IMAGE_DISP_FM display Image LIX_F_TMP_DISP_IMG
Function module to call to display invoice image (blocked PO invoices)
Inventory
INVENTORY_ACCT_ASSG Assignment
LIX M Category
This constant controls the logic of the initial actor function module /OPT/BL_Q_
INIT_ACT_FM. Role decision depends on whether the purchase order contains
inventory line items. See the function module source code if you use it.
LINEITEMLEVLWORKFLO Line Item Level
LIX W Workflow WS00275264
Invoice statuses
that need workflow
LIX LIST_WF_STATUSES to be started 5;

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 415

Chapter 42 Z constants for product code LIX

Product Constant Description Default Value

Code
FI Doctypes that
are the follow-up
docs for Logistic
Invoices (separated
LIX LIV_FI_DOC_TYPES by '; ) RE
LIV Line Item
LIX LIV_LINE_WF Workflow Task ID WS00275264
LIX Header Level
Dash Board Task
LIX LIXDASHBOARD_TASKID ID TS00275267
Subscreen program /PTGWFI/
LIX LIXDBPROG for LIV Dashboard M_LIXDB_SUBSCREEN02
For more information, see Section [Link] “Header level” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution
(VIMZ-CGD).
Subscreen for LIV
LIX LIXDBSCREEN Dashboard 9902
For more information, see Section [Link] “Header level” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Invoice Solution
(VIMZ-CGD).
Subscreen program
for Logistic Invoice /PTGWFI/
LIX LIXPROG Resolution M_LIX_SUBSCREEN02
For more information, see Section [Link] “Line level” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Subscreen for
Logistic Invoice
LIX LIXSCREEN Resolution 9902
For more information, see Section [Link] “Line level” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).
Currency
conversion(I=Invoi
ce, P=PO , L=Local,
N=None)
(1=button, 0=no
LIX LIXSCREEN_CURR_CONV button) N0
For more information, see Section [Link] “Line level” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIMZ-
CGD).

416 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
FM:/ORS/
Subscreen screen LIX_T_GET_EXIT_SUBSCR
LIX LIX_B_PSS_EXIT_S_NO number for PSS N
Subscreen screen number for PSS if the function module is not used with the
constant LIX_B_PSS_EXIT_S_PRG
Returns subscreen
program name and
screen number in FM:/ORS/
PSS ( FM: indicates LIX_T_GET_EXIT_SUBSCR
LIX LIX_B_PSS_EXIT_S_PRG FM) N
Line Item Execute
Transaction Task
LIX LN_EXECTCODE_TASKID ID TS98600016
Function module to
determine the
options to be
displayed in
LIX OPTION_DET_FM Process Selection /PTGWFI/0000000002_F002
FM exit for F4 help
from override
LIX OVERRIDE_F4_EXIT screen 9207
Post LIV blk pss /PTGWFI/
LIX POST_PSS_METHOD_EXIT screen user ext LIX_BK_TMP_PST_PSS_EXT
For more information, see Section 9.3.4 “Configuring the post dashboard method
exit” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Invoice Solution (VIMZ-CGD).
PO Invoice Archive
LIX PO_INV_ARCHIVE_OBJ Object
Pre PSS screen
LIX PRE_PSS_METHOD_EXIT method exit
Name of the
Function module
which does the /PTGWFI/
LIX PRICE_BLOCK_FM price check LIX_F_CHECK_P_BLK
This function module is used whenever it is required to check if the price block
for an invoice item is still valid. For example, the function module is used in
OpenText VIM for SAP workflows to decide on the further processing steps.
Process Selection
Screen - Task ID
LIX PROC_SELECT_TASKID TS99691001 TS00275265

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 417

Chapter 42 Z constants for product code LIX

Product Constant Description Default Value

Code
FM exit in the
Binding FM for the
PSS step - at the
time of Inward
LIX PSS_BIND_EXIT_FM1 Binding
For more information, see Section 9.3.3 “Configuring binding function exits
(dashboard)” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
FM exit in the
Binding FM for the
PSS step - at the
time of Outward
LIX PSS_BIND_EXIT_FM2 Binding
For more information, see Section 9.3.3 “Configuring binding function exits
(dashboard)” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Invoice Solution (VIMZ-CGD).
User exit at the
PBO of PSS Log /PTGWFI/
LIX PSS_LOG_SCREEN_EXIT Subscreen PIR_TMP_PSS_LOG_EXIT
PSS screen: Option
type display
sequence ( A=
Action T=
Authorize
LIX PSS_OPTYP_DIS_SEQ R=Referral) 10ATR
For more information, see Section 9.3.2 “Configuring the option order” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Option key for the
LIX RESUBMIT_OPTION re-submit Option R9998
Function module to
be executed before
the TCode
Execution step is
LIX TCODE_BIND_EXIT_FM1 created
Function module to
be executed at the /ORS/
end of the Tcode 000007_LIX_TCODE_BIND_
LIX TCODE_BIND_EXIT_FM2 Execution step O
TCODE_CHANGE_LIV_IN Transaction code to
LIX V change LIV invoice MIR4
Transaction code to
LIX TCODE_DISP_LIV_INV display LIV invoice MIR4

418 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
FM to be called in
the User Exit to /OPT/
collect data during VIM_BAPI_MM_GET_PARK
LIX USR_EXIT_GET_DATA_FM Document Parking _DATA
For more information, see Section 8.3.3 “Parking directly in MIRO or Fiori to start
a OpenText VIM for SAP process” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Invoice Solution (VIMZ-CGD).
FM to be called in
the User Exit to /PTGWFI/
collect data after PRK_M_GET_PARK_DATA
LIX USR_EXIT_GET_DATA_S Document Parking _S

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 419

Chapter 43

Z constants for product code VAN

Product Constant Description Default Value

Code
Function to use to
calculate the due
date (used
throughout
OpenText VIM for
SAP, not only for /OPT/
VAN CALC_DUEDATE_FOR_DP reporting). VIM_DP_CALC_DUEDATE
Enhancing Liability
Report with
custom fields for
DP line view and
VAN LIABILITY_OBJ_PROC SAP lines view <newly created class>
For more information, see Section 14.7 “Extending the Current Liability Report”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Invoice Solution (VIMZ-CGD).
Group reminders
by user ID, One
email per USER/
Email type/Text-
VAN NOTIF_GROUP_BY_USER Reminder Report
This constant enables you to switch between the following scenarios:

Scenario 1: constant is activated (set to X)

The reminder report is run and there are multiple work items that need to be
sent to a single user. All items are sent to the user in a single email unless
separate reminder texts have been maintained in the reminder configuration.
In this case, multiple emails are sent grouped, based on each type of
reminder text.
Scenario 2: constant is deactivated (set to <blank>)
The reminder report is run and there are multiple work items that need to be
sent to a single user. The items are grouped, based on User, Reminder Text,
Notif Type, Notif. SubType, Curr Role, as maintained in the reminder
configuration.

Constant for
determining due
date FM (for
notifications
VAN CALCULATE_DUEDATE report)
FM for currency
VAN CURRENCY_CONVERSION conversion

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 421

Chapter 43 Z constants for product code VAN

Product Constant Description Default Value

Code
This function module is used to convert the total amount/the line amount of DP
documents from the document currency to the local currency throughout the VIM
Analytics report.

If there is no function module provided, the function module CONVERT_TO_

LOCAL_CURRENCY is used as a fallback.

Detailed workitem
logging active ( X =
Active; Space =
VAN DETAILED_LOG_ACTIVE inactive) X
VAN DISPLAY_LOGO logo image name /OPT/VIM_OTLOGO
Use document date
when convert
VAN DOC_DATE_IN_CONVERT currency X
DOCUMENT
TYPE FOR CREDIT
VAN DOC_TYPE_CREDITMEMO MEMO KG;RA
Tran code used to
display all LIV
invoices during
drilldown
VAN INVOICE_DISPLAY_LIV reporting MIR4
In some OpenText VIM for SAP reports (for example VIM Analytics), it is
possible to use a link to go from the SAP invoice number (BELNR) to the display of
the corresponding SAP invoice. This is the transaction code that is used for
displaying PO invoices.
Tran code used to
display parked CIV
invoice during
drilldown
VAN INVOICE_DISPLAY_PIR reporting FBV3
In some OpenText VIM for SAP reports (for example VIM Analytics), it is
possible to use a link to go from the SAP invoice number (BELNR) to the display of
the corresponding SAP invoice. This is the transaction code that is used for
displaying Non-PO invoices.
INVOICE
DOCUMENT
TYPE FOR NON-
VAN INV_DOC_TYPES_NPO PO INVOICE KR;KG
INVOICE
DOCUMENT
TYPE FOR PO
VAN INV_DOC_TYPES_PO INVOICE RE;RG

422 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Product Constant Description Default Value
Code
Default language
REMNDER_DEFAULT_LA for sending
VAN NG Reminders EN

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 423

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.

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
Web interface for approving invoices.

Archive system
Computer system that enables storage, management and retrieval of archived
data and documents

ArchiveLink document types

Document types that need to be customized for ArchiveLink

ArchiveLink
Service integrated in the SAP NetWeaver Application Server ABAP for linking
archived documents and the application documents entered in the SAP ERP
system.

Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can perform in the SAP system. These authorizations are stored in
Authorization profiles.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 425

Glossary

Automation Report
Tool that provides data about automated and manual processing steps of
documents

BAdI

See: Business Add-Ins (BAdI)

BAPI®
SAP programming interface: Business Application Programming Interface

Baseline
Set of functionality with predefined configuration and the starting point to
implement OpenText VIM for SAP.

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

BSP

See: Business Server Page (BSP)

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

426 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Glossary

Business Server Page (BSP)

SAP term: An HTML-coded user interface of an Internet application of
Application Server ABAP.

Business Transaction Event (BTE)

Event used for extending a Non PO invoice functionality to call a custom program

Capture
Common technical term for both of the following products: OpenText Core
Capture for SAP Solutions and OpenText Capture for SAP Solutions.

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 documents and their work items, in order to optimize
working with OpenText VIM for SAP. 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.

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

Data View (View)

Dynamic part of a perspective. A set of views is shown in the template at specific
locations at runtime. For each perspective, you can define which view appears at
which location in its template. You can insert each view only once in each
perspective.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 427

Glossary

DataSource
Set of fields in SAP NetWeaver BW that provide the data for a business unit for
data transfer to the SAP NetWeaver BW system; technically, it contains an extract
structure and an extraction function module.

DataStore Object (DSO)

Storage location for consolidated and cleansed data in SAP NetWeaver BW

DocuLink
OpenText™ DocuLink for SAP Solutions enables the archiving, management and
retrieval of SAP CRM or SAP S/4HANA documents from within the SAP
infrastructure.

Document Processing (DP)

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)

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. OpenText VIM for SAP 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.

428 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Glossary

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.

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

Fiori Task App

Light-weight web application following the design principles of SAP Fiori. It
provides an inbox showing the items that have been assigned to the logged-in
user. The user then is able to complete items by performing dedicated actions,
entering comments, and editing the data.

IAP

See: Invoice Approval (IAP)

IDoc

See: Intermediate Document (IDoc)

IE

See: Invoice Exception (IE)

Inbound Configuration
Connection to various inbound channels, for example scanned paper documents,
fax, email, or IDoc, and the corresponding configuration.

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

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 429

Glossary

InfoCube
Self-contained dataset in SAP NetWeaver BW, for example, of a business-oriented
area; an InfoCube is a quantity of relational tables arranged according to the
enhanced star schema: A large fact table in the middle surrounded by several
dimension tables

InfoObject Catalog
Folder structure in SAP NetWeaver BW to organize InfoObjects

InfoObject
Smallest information unit in SAP NetWeaver BW. Key figures and Characteristics
are collectively called InfoObjects.

InfoPackages
Object in SAP NetWeaver BW that specifies when and how to load data from a
given source system to the SAP NetWeaver BW system

InfoProvider
Object in SAP NetWeaver BW for which queries can be created or executed.
InfoProviders are the objects or views that are relevant for reporting.

Intermediate Document (IDoc)

Standard SAP message document format for the EDI interface.

Invoice Approval (IAP)

Component that enables users to perform coding, approving and rejecting
invoices

Invoice characteristic
A value specific to each invoice (for example country) that allows flexible
processing. 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)

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.

430 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 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 process: It shows the
accumulated amounts of all documents in the DP workflow, in parked state and
in posted state.

LIV

See: Logistic invoice (LIV)

Logistic invoice (LIV)

purchase order invoice

Materials Management (MM)

Materials management module of the SAP S/4HANA software package. Materials
management is used for procurement and inventory management.

MM

See: Materials Management (MM)

Mobile Approval Portal

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

Invoice based on a Non purchase order (Non PO)

Number range
Array of numbers that can be used for an object in the SAP S/4HANA system

OCR

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 431

Glossary

See: Optical character recognition (OCR)

OpenText VIM for SAP

Packaged business solution that solves a business problem – paying correct
amount to vendors on-time and with the lowest cost. OpenText VIM for SAP
delivers not technology but best-practice business processes. OpenText VIM for
SAP provides values to customers in process efficiency, visibility and compliance.

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.

Perspective
Web Services element that defines which item related data is displayed in the
Fiori Task App and where. A perspective defines the content and visual
appearance of items for a specific area of the screen in the Fiori Task App. The
Fiori Task App displays only one perspective at the same time.

PO

See: Purchase order (PO)

Posted invoice document

Invoice that has already been posted in SAP S/4HANA. 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.

432 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Glossary

Process Configuration
Easy and technically simplified configuration of complex business scenario
aspects. Process Configuration covers profile configuration, profile assignment,
and authorizations.

Process Foundation
Flexible framework to configure and run processes. It utilizes generic workflow
definitions, which are processed by the SAP Business Workflow engine.

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

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.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 433

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.

Scan operator
Person who scans the invoices into images (may not have a SAP ID)

Summary Report
Part of the Central Reporting infrastructure. The Summary Report provides a
summary of all documents processed through OpenText VIM for SAP.

Technical catalog
SAP term: Repository for creating role-specific business catalogs

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)

VIM Analytics (VAN)

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
OpenText VIM for SAP.

VIM Central Workplace

Central tool to process work objects. It provides an inbox with personal and
shared work item lists to the user. It also provides access to different business
objects and status information for all objects in process. The user can switch
between work centers and navigate in a process-dependent tree.

VIM Invoice Workplace

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

434 OpenText™ Vendor Invoice Management for SAP® Solutions VIMZ230402-RGD-EN-01

 Glossary

Web Services
Underlying technical concept of the Fiori Task App interface. You configure the
complete content of the Fiori Task App either by customizing or by implementing
an interface for the Web Services.

Work object type

Processing object in the VIM Central Workplace. It can represent a process object,
a SAP business object, or information from any SAP tables.

Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP S/4HANA system.

VIMZ230402-RGD-EN-01 Reference Guide for Invoice Solution 435