Professional Documents
Culture Documents
Reference Guide
VIM160304-RGD-EN-01
OpenText™ Vendor Invoice Management for SAP® Solutions
Reference Guide
VIM160304-RGD-EN-01
Rev.: 2019-Oct-29
This documentation has been created for software version 16.3.4.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com
One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
Disclaimer
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
Part 1 About Vendor Invoice Management 13
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide iii
VIM160304-RGD-EN-01
Table of Contents
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide vii
VIM160304-RGD-EN-01
Table of Contents
viii OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Table of Contents
Vendor Invoice Management does not replace SAP invoice transactions and SAP
core logic of logistic invoice verification – Many categories of invoices can be
automated or treated by manual intervention through VIM screens. For other
invoice categories, navigation from VIM into the SAP invoice transaction (typically
MIRO) is required to fully post the invoice. Not all MIRO fields are provided in the
VIM baseline configuration.
VIM builds on top of the SAP core invoice verification. Tolerances are defined in
core SAP customizing. This logic will apply blocking reasons to line items when
invoices are posted. Most prominent blocking reasons are price and quantity. VIM
catches the events created by blocked invoices in core SAP and triggers workflows
for block resolution.
“Classic Mode” versus “Simple Mode” – Starting with version 16.3 and only
available for SAP S/4HANA 1610 and later, Vendor Invoice Management provides
two implementation options.
Classic Mode and Simple Mode are generally independent of each other.
Classic Mode Classic Mode is to a large extent compatible with previous VIM versions 7.0 and 7.5.
It offers proven architecture and a framework and many options to configure and
Classic mode is the choice for organizations upgrading from SAP ECC and older
VIM versions who want to gradually adopt to new SAP S/4HANA concepts and
maintain their approach to invoice processing.
Classic mode provides powerful SAP GUI/Webgui based tools like VIM Workplace
and the VIM Analytics report, a web portal for invoice coding and approval, which
can be integrated with SAP NetWeaver® Portal and SAP Fiori apps for different
tasks like simple coding, approval, and confirming price and quantity on PO related
invoices.
Simple Mode Simple Mode provides a new invoice process designed embracing SAP S/4HANA
concepts like simplification, principle-of-one, digitalization, cloud-first, and new
user experience from the start. The SAP S/4HANA environment is the basis for a
next-generation invoice automation solution that focuses on streamlined and
simplified invoice processing.
While the Classic Mode provides different options, the Simple Mode philosophy is
about a uniform best practice approach based on different invoice scenarios:
• Invoices that can be processed through automation by their nature and structure
• Invoices that can be processed through automation with limited manual
intervention
• Invoices that need manual processing and may use specific features of SAP’s
Fiori app Manage Supplier Invoices
• Invoice automation build around SAP’s Fiori App Manage Supplier Invoices
• End-to-end Fiori user experience
• Capture of scanned paper invoices and PDF invoices through OCR cloud service
with automated optimization through constant feedback, other invoices are
received from networks like Ariba or classic IDocs or other channels.
• Cloud OCR as default option - on premise OCR will also be supported.
• Advanced machine learning features to optimize data capture (feedback from
SAP process and SAP posting to the data extraction service)
• Leverage SAP invoice drafts as container to store preliminary invoice data
(instead of separate business object and header and line items tables of classic
mode)
• Background logic for initial classification of incoming invoice data to control
process and flow (happens in background) - separate into invoices going through
automation and invoices that need manual intervention
Limitations Vendor Invoice Management 16.3 provides a basic version of the new Simple Mode
covering invoices and credit memos. A number of features are not yet released and
there are further limitations. Future versions will provide new features to fully
support the scope of the Simple Mode as explained above.
This document collects reference information that is helpful when configuring and
administering VIM.
Release Notes The Release Notes describe the following aspects in detail:
The Release Notes are continually updated. The latest version of the VIM Release
Notes is available on OpenText My Support (https://support.opentext.com).
A third party interface is one channel to import an invoice to VIM. Third party
vendors provide the routing of invoices from the vendor to the customer.
“Middlemen” handle the responsibility of sending the invoice from vendor to
customer. These middlemen may also communicate back to the vendor regarding
the progress of the invoice processing on customer side. Third party vendors can use
any middleware technology like EDI, and so on.
Figure 3 depicts the suggested data and process flow for a third party service
provider scenario.
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.
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).
• Ensure that the original invoice sent by the vendor is transmitted unaltered to the
customer.
• Ensure that a Digital Signature infrastructure is agreed on and implemented
according to the customer and partner needs.
• Ensure that the VIM APIs are implemented so that correct data is passed to VIM.
Note: VIM 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 Business Center Workplace. As soon as the workflow is started,
the document is visible in VIM Analytics and other reports.
The third party service provider scenario includes 3 Interface Remote Functions.
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.
Export parameters
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.
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
2. Channel info:
Structure/OPT/VIM_1REXTDATA:
For each invoice field passed, the External Partner must specify field name
(EXTFIELD) and value (EXTVALUE).
4. Other optional parameters:
Export parameters
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.
Additional notes
The document class (TIF, PDF, and so on) is determined the following way:
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
1. Channel info:
Export parameters
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.
DOC_STATUS-LOGICAL_SYSTEM
This export parameter shows the logical system where the information of the
table entry was taken from.
• 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.
VIM Analytics provides you with a clear data report on your documents with
exceptions as well as the Invoice Exception workflows. It allows you to track the
documents routed through SAP workflows by VIM or even without any VIM
process. You can use VIM Analytics to check the current document status of a
particular invoice. You can also check the current workflow status, current agent
and exception reason of a particular invoice. VIM Analytics presents the data report
results in the SAP List Viewer (ALV). ALV is used in the result list and in the detail
pane, Processes, Line Items and History tab.
VIM Analytics has been completely reworked for VIM 7.5. Here are some of the new
features:
• The new VIM Analytics provides more detail information to selected invoices:
There are several detail views available, showing, for example, workflows, line
items, and comments. In the process view of the detail pane, the user gets
information about all running VIM processes, including parallel approval and
referral processes, which are not available in the old VIM Analytics report.
• The new VIM Analytics provides a completely reworked selection screen: The
new selection screen was designed for the following purposes:
For documentation of the “old” VIM Analytics, see the VIM 7.0 documentation.
/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 VIM
exceptions.
Tip: You can switch between the different report variants with Get Variant .
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 VIM 7.5 SP4, the following new reports are introduced for
this:
/OPT/ This transaction launches VAN to read DP data from one remote system.
VIM_VA25
To start remote enabled VAN for a single remote system:
/OPT/ This transaction launches VAN to read DP data from two or more remote systems.
VIM_VA26
To start remote enabled VAN for multiple remote systems:
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 (VIM160304-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.
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.
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.
• 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.
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
Invoice Data
Transaction/Event
Categorization of invoice documents into invoices, credit memos, subsequent
debits, subsequent credits and down payments
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
Note: Both the actual purchasing document in line items and potential
purchasing documents from header level and purchase order list (PO list)
are taken into account.
Plant
Plant from the invoice line items
Process Data
• Invoices of all Process Types. This means invoices with and without VIM
processes
• Invoices with DP Process. Technically, this means that a DP workflow was
started.
• Parked/Blocked Inv., w/o DP. This means invoices with at least one VIM
process (parking, blocking, approval) but without a DP process.
• Invoices without VIM Process. This means invoices without any VIM
process
Invoice Type
Type of invoice, indicating whether the invoice is purchase order based or not
Overall Process Status
The Overall Process Status enables you to select for invoices in a specific
processing status. You can select for predefined status scenarios and for a SAP
invoice status or a VIM processing status.
Specific Scenario
Specific Scenario provides predefined scenarios, for example All
Invoices, Open Invoices, and Completed Invoices.
An open invoice in this context is defined as an invoice that has an open
VIM process (if existing) or where the SAP invoice (if existing) is not
deleted, not cancelled, or not yet ready for payment (this means not yet
posted without any fiscal and logistic payment block).
A completed invoice in this context is defined as an invoice where both all
VIM processes (if existing) are completed and the SAP invoice is deleted, or
cancelled, or ready for payment (this means posted without any fiscal and
logistic payment block).
You can also select for invoices in different approval scenarios supported by
VIM: approval of posted documents, or approval of parked or DP based
documents.
With the Fiscal Year Changed scenario, you can select all invoice
documents that ran through the year end program of VIM. In other words,
you can select all invoice documents whose SAP invoice documents were
deleted due to a change in the year end posting period.
Selected Status
Selected Status enables you to select for the status of the SAP invoice or for
the VIM processing status. The value help offers a big range of different
status values. SAP statuses start with the prefix SAP_. They represent
different states of the SAP invoice, for example Parked, Posted, or Blocked.
Statuses without prefix SAP_ represent DP statuses.
Note: An invoice is not in status Posted but Blocked as long as any
payment block exists. For PO based invoices, both the fiscal payment
block and the logistic payment block are taken into account.
Accounting Data
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.
Workflow Type
Type of the VIM workflow that is or was active for processing an invoice.
Example:
• The work item could be created but the condition for the step Create
Work Item is not yet fulfilled (SAP work item status: CHECKED).
• The work item cannot be executed yet and therefore cannot be seen in
the Business Workplace or the VIM Workplace yet (SAP work item
status: WAITING).
51 - In Process
These are workflows with a current work item that has one of the following
statuses:
52 - Completed
These are workflows with the following statuses:
54 - Error in Workflow
These are workflows with a current work item that has the following status:
Document Dates
Start Date
Date when the invoice entered the SAP system
DP Start Date
Date when the DP workflow started
Parking Date
Date when the parked SAP invoice was created or when the SAP invoice was
parked
Update Date
Date of the last change of the invoice.
Note: Even doing an approval step is defined as a change in this context.
Process Flow
The following sections explain the general layout and the various areas of the report
results.
1. In the selection screen, enter the criteria you want to run a report for.
1
Menu toolbar
2
Application toolbar
3
Result list
4
Detail pane
Personal layout You can change the layout of the report results screen, according to your needs:
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.
Refresh
Get the newest data for the displayed report results.
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™ Extended ECM for SAP®
Solutions) for the work item in a separate window. Extended ECM for SAP
Solutions allows you to access related OpenText™ Content Server items in the
business workspace without leaving the SAP system.
For a comprehensive description, see Section 5 “Working in SAP ERP with the
Business Content window ” in OpenText Extended ECM 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 49.
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)
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 2
Amount of cash discount for the second payment period in document currency
Document Status
Status ID of DP document
DP ID before restart
ID of a previous DP document that was deleted and for which a new DP process
was started
Due Date
Due date of the invoice
End at
Time at which the last VIM process was finished
End on
Date when the last VIM process was finished
Enter at
Time at which the invoice entered the SAP system
Enter on
Date when the invoice entered the SAP system
Exception Reason
Current exception of the invoice, for example the current process type of a DP
document or the parking reason of a parked invoice
Invoice Type
Type of invoice, indicating whether the invoice is purchase order based or not
Net Amount
Net Amount, as calculated in the DP indexing screen
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
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
• Processes
• Image
• Line Items
• History
• Comments
• Vendor Workspace
If you change the selection in the result list, the detail pane automatically switches to
the newly selected document.
Processes
This tab shows the VIM workflows of the document that is selected in the result list.
The ALV grid control of the Processes tab provides some action buttons.
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 48.
The Process State column displays one of the following icons, indicating the status
of the workflow:
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 48.
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 48.
Comments
This tab displays the comments of the document that is selected in the result list. It
displays Process Comments and Approval Comments.
Vendor Workspace
This tab displays the Extended ECM for SAP Solutions plug-in for the work item.
Extended ECM for SAP Solutions allows you to access related OpenText Content
Server items in the business workspace without leaving the SAP system.
For a comprehensive description, see Section 5 “Working in SAP ERP with the
Business Content window ” in OpenText Extended ECM for SAP Solutions - User Guide
(ERLK-UGD)
Note: This field is populated only for VIM processes that are related to a
SAP FI invoice, for example at the parking workflow of a SAP FI invoice.
Approval Path
Approval path in case of parallel approval processes
Block Reason
Block reason in case of a blocked workflow
Company Code
Company Code of the SAP invoice document
Note: This field is populated only for VIM processes that are related to a
SAP FI invoice, for example at the parking workflow of a SAP FI invoice.
Current Agent
Agent that is currently assigned for processing the VIM process
If multiple different agents are assigned, * is displayed.
Current Role
Role that is currently assigned for processing the VIM process
Current Task
Technical ID of the current workflow task
Current Workitem ID
Work item ID of the current workflow task
Cycle Time
Duration of the VIM process from the point in time when the workflow was
started to the point in time when the workflow was finished
Dialog Flag
Indicator whether the current task is a dialog task or not (background task)
Document ID
DP Document ID
End at
Time at which the VIM workflow was finished
End on
Date when the VIM workflow was finished
Exception Reason
Current exception of the VIM process, for example the current DP process type,
the parking reason or the block reason
Fiscal Year
Fiscal year of the SAP invoice document
Note: This field is populated only for VIM 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 VIM workflow
Note: This field is populated only for the block workflow on SAP MM
invoice line items
MM Invoice Document No.
SAP MM invoice number
Note: This field is populated only for VIM 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 VIM workflow
Process State
For a description of this field, see “Processes” on page 54.
Process Type
DP process type
Start at
Time at which the VIM workflow was started
Start on
Date when the VIM workflow was started
Update Date
Date when the VIM workflow was processed the last time
Update Time
Time at which the VIM workflow was processed the last time
WF Type Text
Text for the VIM workflow type
Example:
WI Status
Current status of the VIM workflow. The following values are available:
50 - Waiting
These are workflows with a current work item that is not yet visible in the
VIM Workplace. This can have one of the following reasons:
• The work item could be created but the condition for the step Create
Work Item is not yet fulfilled (SAP work item status: CHECKED).
• The work item cannot be executed yet and therefore cannot be seen in
the Business Workplace or the VIM Workplace yet (SAP work item
status: WAITING).
51 - In Process
These are workflows with a current work item that has one of the following
statuses:
52 - Completed
These are workflows with the following statuses:
54 - Error in Workflow
These are workflows with a current work item that has the following status:
WI Status Text
Text for the current status of the VIM workflow
Workflow
Work item ID of the workflow instance
Workflow Definition
Technical ID of the workflow template
Workflow Type
ID of VIM workflow type
Example:
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
If multiple different G/L accounts, cost centers, and so on exist, * is displayed.
• 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.
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.
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.
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.
11. In the Determine drilldown totals level dialog box, select Level 1 Current
Role.
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.
16. In the Determine drilldown totals level dialog box, select Level 0 Non-total
lines.
Note: You can save your preferred layout with the Save Layout option of
the Choose Layout button.
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.
2. Click the small arrow on the right side of the Choose Layout button.
4. In the Change Layout dialog box, select the Vendor column and use the arrow
buttons to set this column at the first position of the Displayed Columns pane.
5. Select the Processing Time (in Sec) column and use the arrow buttons to set
this column at the second position of the Displayed Columns pane.
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.
12. In the Determine drilldown totals level dialog box, select Level 1 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.
17. In the Determine drilldown totals level dialog box, select Level 0 Non-total
lines.
Note: You can save your preferred layout with the Save Layout option of
the Choose Layout button.
3.4.9.3 Example 3: Getting the total invoice amount per company code,
separated in PO and Non PO invoices
You want to see the total invoice amount per company code. For every company
code, you want to have a subtotal for PO based and for Non PO based invoices.
Getting the total invoice amount per company code, separated in PO and NPO
invoices:
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.
2. Click the small arrow on the right side of the Choose Layout button.
4. In the Change Layout dialog box, select the Company Code column and use the
arrow buttons to set this column at the first position of the Displayed Columns
pane.
5. Select the Invoice Type Text column and use the arrow buttons to set this
column at the second position of the Displayed Columns pane.
6. Select the Total Amount in Rep. Crcy column and Reporting Currency, and
use the arrow buttons to set theses columns at the third and fourth position of
the Displayed Columns pane.
7. Select the Aggregation check box for the Total Amount in Rep. Crcy column.
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.
Note: You can save your preferred layout with the Save Layout option of
the Choose Layout button.
• When working without ABAP Core Data Services views (ABAP CDS
views), the selection fields Overall Process Status and Maximum
Number of Records are not working as restrictive selection criteria. Find
more details in Selection fields for the Overall Process Status
on page 68 and Selection field Maximum Number of Records
on page 69.
• In case you use very restrictive selection criteria but experience very
slow performance nevertheless, ask your VIM consultant or system
administrator to check if a database index might help.
Limit the number of output fields in the result list
The result list provides about 100 columns. The more records you want to be
displayed in the result list, the more important becomes the number of columns
in the result list. Adjust the existing layout variants or create a new layout
variant for the result list. So you restrict the number of output columns to those
columns you need for your daily business. For more details about layout
variants, see Section 16.3 “Layout variants” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-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.
blocked. When running VIM Analytics with these selection criteria, first,
all one million invoices with channel ICC are selected and read into the
memory. Then, those 5,000 blocked invoices are filtered out. This means
that 995,000 invoices were read into the memory without need.
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.
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.
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
Include Documents
In this panel, enter search criteria regarding which documents should be included.
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.
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.
Views
Groupings
Header Groups
Allows you to group the result based on the header level; see “Document header
grouping” on page 81.
Line Groups
Allows you to group the result based on the line level; see “Document lines
grouping” on page 83.
You can select views and groupings in the Report View Group By field of the
selection screen, see “General Information” on page 73. But also in the report views
screen, you can toggle between views and groupings in the menu bar and the
application toolbar.
Executing a search in the selection screen displays the report views screen, based on
the search criteria entered in the selection field panel.
The 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:
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.
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.
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
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
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
• 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.
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
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:
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
The Automation Report is a tool that provides data about automated and manual
processing steps of VIM 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 (VIM160304-CGD).
The VIM program “Automation Report” allows to view and export the table
contents. The current version of the Automation Report does not do any counting or
calculation.
2. In the Automation Report selection field screen, configure parameters for the
report.
Invoice Information
Report Options
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 91.
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.
• Invoice data
• Automation data
Invoice data
Note: Fields that are marked with an asterisk in the tables are not visible in the
screenshot.
Automation data
Note: Fields that are marked with an asterisk in the table are not visible in the
screenshot.
The Invoice Life Cycle Report (ILC) is a tool that provides data about the complete
life cycle of a VIM document. All VIM 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 5.2 “Scheduling batch jobs for
Invoice Life Cycle” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM160304-AGD).
2. In the Life Cycle Report selection screen, configure the following parameters
for the report:
Process Data
Document ID
Enter the DP ID of the document in VIM.
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
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.
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.
• 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.
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.
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.
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/
VEND_NAME Vendor name
VIM_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/
STATUS_TEXT Document status text
VIM_T101T
Fiscal year of the DP from /
GJAHR Fiscal year
OPT/VIM_1HEAD
PROCESS_DURATION Cycle time Calculated
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
Description (column
Technical Field Name Meaning - Usage - Notes
name)
OpenText user mapping The responsible agent for the
ACTUAL_AGENT
object ID individual work item
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
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 114.
The selection screen opens. It comprises the application toolbar and the selection
field panel.
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.
Tips
Layout
Enter the layout for the report if you have saved a personal layout using the
ALV grid control, before.
100 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
7.2. Using the report screen
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.
Details Screen
The details screen differs for the particular reports. The following button in the
ALV grid control of the details screen is common for all reports that have a
details screen (except the Aging Report):
Image
You can display the scanned image of the original invoice of a VIM
document in the Image Viewer that is installed and configured on your
desktop: Select a line in the table and click Image.
For individual settings of the details screens, see the respective Details Screen
sections of the particular reports.
Notes
• The Key Process Analytics Report does not display the results in a report
screen but in individual report panels; see “Using the individual report
panels” on page 114.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 101
VIM160304-RGD-EN-01
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.
102 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 8
Using the Summary Report
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 103
VIM160304-RGD-EN-01
Chapter 8 Using the Summary Report
104 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
8.2. Using the 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 101.
In process
• Approval
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 105
VIM160304-RGD-EN-01
Chapter 8 Using the Summary Report
Pre Processed
Processed
• Posted
Others
• Cancelled
• Deleted
• Confirmed Duplicate
• Obsolete
• Rescan Complete
Tip: The selected line in the ALV Grid must contain data. Otherwise, the
Summary Report drill down list cannot be displayed.
106 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 107
VIM160304-RGD-EN-01
Chapter 9 Using the Central Audit Report
108 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
9.2. Using the report screen
Workflow Log
Select a document's line in the ALV Grid and click this button to display
detailed workflow information.
Image
Select a document's line in the ALV Grid and click this button to display the
scanned image of the original invoice in the Image Viewer installed and
configured on your desktop.
Dashboard
Select a document's line in the ALV Grid and click this button to access the
OpenText unified dashboard.
Link to VAN
Select a document's line in the ALV Grid and click Link to VAN to open VAN
for the selected document, see “VIM Analytics: Getting data reports“ on page 35.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 109
VIM160304-RGD-EN-01
Chapter 9 Using the Central Audit Report
In a multiple backend scenario, VAN is opened directly on the system where the
document resides. You do not have to log on to the system, when using trusted
RFC connections.
Note: Ask your administrator whether trusted RFC connections are used.
The administrator can configure RFC connections, using the System
Landscape Directory (SLD).
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.
110 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-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 VIM process: It shows the accumulated amounts of all documents in the DP
workflow, in parked state and in posted state.
The individual report panels of the Key Process Analytics Report highlight the
following aspects:
Total Liability
This panel provides an overview of the total liability.
Amounts that are exceeding certain thresholds are highlighted in orange or red.
Your administrator can customize these thresholds.
Processed / In Process Documents
This panel provides an overview of VIM invoices, processed and currently in
process.
If the number or percentage of processed or in process documents exceeds
certain thresholds, the respective cells are highlighted in orange or red. Your
administrator can customize these thresholds.
Channel Analysis
This panel provides an overview of VIM invoices per channel.
First Pass
This panel provides an overview of first pass VIM invoices, that means VIM
invoices that could be posted without any exceptions.
If the number or percentage of first pass VIM invoices goes below certain
thresholds, the respective cells are highlighted in orange or red. Your
administrator can customize these thresholds.
Top Exceptions by Count
This panel provides an overview of the most frequent exceptions during the
VIM process. You can select the number of exceptions to be listed.
Top Vendors by Amount
This panel provides an overview of the vendors with the highest purchase
amount, based on the gross amount of all VIM invoices. You can select the
number of vendors to be listed.
The Key Process Analytics Report supports the conversion of amount fields to
different currencies.
You can display report data as graphics, using standard SAP ALV grid functionality.
You can choose between different chart types, for example bar chart or pie chart.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 111
VIM160304-RGD-EN-01
Chapter 10 Using the Key Process Analytics Report
The main screen comprises the application toolbar, the Frame Selection panel
and the individual report panels.
For a description of the elements that are common for all reports, see “Using the
selection screen” on page 99.
112 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
10.1. Using the Frame Selection panel
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.
• 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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 113
VIM160304-RGD-EN-01
Chapter 10 Using the Key Process Analytics Report
The individual report panels in the main screen get populated with data.
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.
114 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
10.2. Using the individual report panels
Category
The following states of documents are listed:
• Blocked Documents
• Parked Documents
• Pre-Process Documents (all documents that are still in process and did not
yet result in an SAP invoice)
Total Amount
Total Amount of all documents
Crcy
Reporting Currency, as selected in the Frame Selection panel
Details To show details for a specific cell in the Total Amount column, double-click the cell
in the ALV grid. The Document List opens, showing detailed information on the
VIM documents of the Category referred to in the selected cell.
Tips
• The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.
• For the columns Category and Crcy, no document lists are available.
Threshold func- In the Total Liability panel, the threshold functionality is available. Your
tionality administrator can define threshold values for an attention status and a critical status.
If the attention value is exceeded in a cell, the cell is highlighted in orange. If the
critical value is exceeded in a cell, the cell is highlighted in red.
Invoice Type
• PO Invoices
• NPO Invoices
• Unclassified
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 115
VIM160304-RGD-EN-01
Chapter 10 Using the Key Process Analytics Report
Total # Processed
Total number of invoices that are already processed, that means with status
Posted.
You can add the following columns using the ALV grid control:
PO Based
Indicator if the invoice is PO based or not. Possible values: Y for Yes, N for No, U
for Unclassified.
This column can be useful if you export the data, for example to Microsoft Excel.
Processed (%)
Percentage of invoices that are already processed, that means with status
Posted.
In Process (%)
Percentage of invoices that are currently in process
Details To show details for a specific cell, double-click the cell in the ALV grid. The
Document List opens, showing detailed information on the VIM documents
according to Invoice Type and Document Status referred to in the selected cell.
Tip: The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.
The ALV grid control in the Document List contains the following button:
Image
You can display the scanned image of the original invoice of a VIM document in
the Image Viewer installed and configured on your desktop: Select a line in the
table and click Image.
Threshold func- In the Processed / In Process Documents panel, the threshold functionality is
tionality available. Your administrator can define threshold values for an attention status and
a critical status. If the attention value is exceeded in a cell, the cell is highlighted in
orange. If the critical value is exceeded in a cell, the cell is highlighted in red.
116 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
10.2. Using the individual report panels
The Channel Analysis panel provides an overview of VIM invoices by Channel ID.
The channel indicates the input mode of invoices into VIM, for example OCR. The
Channel Analysis panel comprises the following columns:
Note: The following list only covers columns whose meaning is not obvious.
Channel ID
Channel ID, for example IDOC for invoices imported using Electronic Data
Interchange
Channel Text
Description of the channel
Total # Unclassified
Total number of unclassified invoices (not yet classified as PO or NPO invoices)
You can add the following columns using the ALV grid control:
PO Invoices (%)
Percentage of PO invoices
NPO Invoices (%)
Percentage of NPO invoices
Unclassified (%)
Percentage of unclassified invoices
Details To show details for a specific cell, double-click the cell in the ALV grid. The
Document List opens, showing detailed information on the VIM documents,
according to Invoice Type and Channel ID referred to in the selected cell.
Tip: The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.
The First Pass panel provides an overview of first pass VIM invoices, that means
VIM invoices that could be posted without any exceptions. The following types of
exceptions can happen:
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 117
VIM160304-RGD-EN-01
Chapter 10 Using the Key Process Analytics Report
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 (VIM160304-CGD),
especially “To maintain exceptions for Central Reporting” and “To map exceptions
for several back end systems”.
Note: The following list only covers columns whose meaning is not obvious.
You can add the following columns using the ALV grid control:
PO Based
Indicator if the invoice is PO based or not. Possible values: Y for Yes, N for No.
This column can be useful if you export the data, for example to Microsoft Excel.
Details To show details for a specific cell, double-click the cell in the ALV grid. The
Document List opens, showing detailed information on the VIM documents,
according to the Invoice Type referred to in the selected cell.
Tips
• The selected cell in the ALV grid must contain data. Otherwise, the
Document List cannot be displayed.
• There is no Document List available for the column Total # Documents.
Threshold func- In the First Pass panel, the threshold functionality is available. Your administrator
tionality can define threshold values for an attention status and a critical status. If the value in
a cell falls below the attention value, the cell is highlighted in orange. If the value in
a cell falls below the critical value, the cell is highlighted in red.
118 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
10.2. Using the individual report panels
The Top Exceptions by Count panel provides an overview of the most frequent
exceptions during the VIM process.
You can select the number of exceptions to be listed in the panel. Therefore, the ALV
grid control of the Top Exceptions by Count panel provides the Top button:
Top
Click this button to select the number of exceptions that are listed. Possible
values: 3, 5, 10, or 20
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.
The Top Vendors by Amount panel provides an overview of the vendors with the
highest purchase amount, based on the gross amount of all VIM invoices.
You can select the number of vendors to be listed in the panel. Therefore, the ALV
grid control of the Top Vendors by Amount panel provides the Top button.
Top
Click this button to select the number of exceptions that are listed. Possible
values: 3, 5, 10, or 20
Note: The following list only covers columns whose meaning is not obvious.
Name 1
Vendor name
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 119
VIM160304-RGD-EN-01
Chapter 10 Using the Key Process Analytics Report
Total Amount
Total amount for the vendor
Currency
Reporting Currency, as selected in the Frame Selection panel
You can add the following column using the ALV grid control:
Name 2
Only useful if this field is maintained for the vendors in the system
Details To show details for a specific line, double-click the line in the ALV grid. The
Document List opens, showing detailed information on the VIM documents,
according to the Logical System and the Vendor referred to in the selected line.
120 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 121
VIM160304-RGD-EN-01
Chapter 11 Using the Exception Analysis Report
122 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
11.2. Using the report screen
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 123
VIM160304-RGD-EN-01
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 101.
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.
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 – Reference Guide
VIM160304-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 VIM document before all the work items related to
this VIM document have been touched by a user for the first time.
One VIM document can comprise several work items. Every work item has a
wait time before it is touched for the first time. The report sums up these wait
times and averages them.
Note: The columns containing time data display the time in <xx>d <xx>h
<xx>m <xx>s format. You can add corresponding columns that display the
time in seconds as a numeric value. This is useful, for example, if you want
to export data to an Excel spreadsheet.
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
Tip: The selected line in the ALV Grid must contain data. Otherwise, the Work
Items with Exception List cannot be displayed.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 125
VIM160304-RGD-EN-01
Chapter 12
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 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:
Note: The time stamps that are used for the Productivity Report are based on
the time information in the SAP work item tables and are not directly related to
the time stamps in the VIM process history.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 127
VIM160304-RGD-EN-01
Chapter 12 Using the Productivity Report
128 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
12.2. Using the report screen
Doc Characteristics
Click PO Invoices, Non-PO Invoices, or All Invoices (All Invoices includes
PO, Non PO and unclassified invoices).
Note: Unclassified invoices are not yet classified as PO or NPO
invoices.
Time Characteristics
Date Range
Enter the date range you want to run the report for. The date refers to
the Created at date of work items related to the VIM document, 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
VIM document.
Grouping
Select the parameter to group the report by. Click Agent or Role.
For a description of the elements that are common for all reports, see “Using the
report screen” on page 101.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 129
VIM160304-RGD-EN-01
Chapter 12 Using 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.
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 VIM documents that have been worked on in the report period.
Work is not necessarily completed; that means, the invoice may be already
posted or not.
Reserved
Number of VIM documents that are reserved at the moment; that means, at least
one work item belonging to the VIM document is reserved. The moment of time
is determined by the last update of the data.
The value in the Reserved column is a subset of the value in the In Process
column.
In Process
Number of VIM documents that have at least one work item in the following
states at the moment:
130 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
12.2. Using the report screen
Note: The columns containing time data display the time in <xx>h <xx>m
<xx>s format. You can add corresponding columns that display the time in
seconds as a numeric value. This is useful, for example, if you want to
export data to an Excel spreadsheet.
Avg. # of Touches
Average number of how often a VIM document has been touched
Avg. # of Referrals
Average number of how often a VIM document has been referred to another
agent
Comparison To the right of the report period columns, the following columns are displayed for
period results the comparison period (indicated by Prev. in the column title):
Note: The columns containing time data display the time in <xx>h <xx>m
<xx>s format. You can add corresponding columns that display the time in
seconds as a numeric value. This is useful, for example, if you want to
export data to an Excel spreadsheet.
Prev. Avg. # of Touches
Average number of how often a VIM document has been touched
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 131
VIM160304-RGD-EN-01
Chapter 12 Using the Productivity Report
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 – Reference Guide
VIM160304-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:
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 133
VIM160304-RGD-EN-01
Chapter 13 Using the Aging Report
Doc Characteristics
Click PO Invoices, Non-PO Invoices, or All Invoices (All Invoices includes
PO, Non PO and unclassified invoices).
Vendor
Enter the vendor number, depending on the logical system.
134 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 135
VIM160304-RGD-EN-01
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 101.
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 – Reference Guide
VIM160304-RGD-EN-01
13.2. Using the report screen
With Doc Type grouping, the data cells contain information about VIM documents.
With Role grouping, the data cells contain information about work items.
Report results Next to the right, the following columns are displayed:
Note: You can change the layout of the report results; for example, you can
shift, remove or add columns. So, your actual table might differ from the
following description.
Description
Description of the document type if you have grouped by Doc Type.
Description of the role if you have grouped by Role.
0 to 30 Days
This is the default setting. You can change the setting, using the Buckets (in
Days) parameter in the selection field panel. See Buckets (in Days) on page 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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 137
VIM160304-RGD-EN-01
Chapter 13 Using the Aging Report
With Doc Type grouping, the Document List opens, showing detailed information
on the VIM documents referred to in the selected cell. The Document List shows
documents with a specific Logical System and Document Type.
With Role grouping, the Work Items with Exception List opens, showing detailed
information on the work items referred to in the selected cell. The Work Items with
Exception List shows work items with a specific Role.
Tips
• The selected cell in the ALV Grid must contain data. Otherwise, the
Document List or Work Items with Exception List cannot be displayed.
• Displaying the Document List or Work Items with Exception List for a cell
is possible in all columns with numeric values, except the cells containing
the Total.
• The layout of the Document List or Work Items with Exception List
depends on the selected column.
138 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Part 4
Comparison Approval Portal to VIM Fiori
apps
Part 4 Comparison Approval Portal to VIM Fiori apps
Legend
x
Available
-
Not available
(x)
Functionality in the Fiori app is not as comprehensive as in the Approval Portal.
140 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 14
Comparison Approval Portal to Approve Invoices
app
Table 14-1: Approval Portal features compared to the Approve Invoices app
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 141
VIM160304-RGD-EN-01
Chapter 14 Comparison Approval Portal to Approve Invoices app
142 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Area Feature Fiori app -
Portal Fiori app
comment
Invoice history x x
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
Brava! View
x x
(desktop)
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 143
VIM160304-RGD-EN-01
Chapter 14 Comparison Approval Portal to Approve Invoices app
144 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 145
VIM160304-RGD-EN-01
Chapter 15
Comparison Approval Portal to Enter Cost
Assignment Simple app
Table 15-1: Approval Portal features compared to the Enter Cost Assignment
Simple app
Note: Parked
documents x x
are supported
in the context
of DP process
only.
Held documents
(PO and Non PO)
Note: Held
documents x x
are supported
in the context
of DP process
only.
Posted documents
x x
(PO and Non PO)
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 147
VIM160304-RGD-EN-01
Chapter 15 Comparison Approval Portal to Enter Cost Assignment Simple app
148 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Area Feature Fiori app -
Portal Fiori app
comment
Custom field x -
Re-use of coding Coding templates x -
If there is more than
User can insert/ one GL account, GL
x -
change GL accounts accounts are not
GL accounts (more than one) shown on screen.
Invoice actions Forward x -
Inquire x -
Confirm x x
Decline x x
Custom x -
Select next approver Maximum 100 users
x (x)
from COA in list
Line item actions Add row, copy row,
x -
delete row
Search helps Cost assignment
x x
fields
Invoice header
x -
custom fields
Attachments Upload attachments x x
Delete attachments x x
History Display my
x -
processed invoices
View invoice
x -
history
Display invoices
from multiple
x (x)
systems in one
Multiple backend inbox
Status display
x x
Status (inquiry/on behalf)
A complex invoice
x x
Balance Calculate balance cannot be handled.
Coding data Export to Excel x -
handling
Import from Excel x -
Comments View comments x -
Add comment x x
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 149
VIM160304-RGD-EN-01
Chapter 15 Comparison Approval Portal to Enter Cost Assignment Simple app
150 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
[c] Can be included as tile but technically not a UI5 app
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 151
VIM160304-RGD-EN-01
Chapter 16
Comparison Approval Portal to Enter Cost
Assignment Advanced app
Table 16-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
coder/ coder/
VIM 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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 153
VIM160304-RGD-EN-01
Chapter 16 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
154 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 155
VIM160304-RGD-EN-01
Chapter 16 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
Cloud deployment - x the cloud based on
SAP Cloud Platform
Requires SAP user
User management - x
(SU01)
[a] Can be included as tile but technically not a UI5 app
156 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Part 5
SAP NetWeaver Business Warehouse
details
Part 5 SAP NetWeaver Business Warehouse details
This part covers details about the following objects that are part of the VIM 7.0 BW
content for SAP NetWeaver Business Warehouse (SAP NetWeaver BW):
• InfoObjects
• DataSources
• DataStore Objects (DSOs)
• MultiProviders
For more information, see Section 26 “SAP NetWeaver Business Warehouse content”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
158 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 17
InfoObjects
• Key Figures
• Characteristics (including time characteristics and technical characteristics)
• Units
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 159
VIM160304-RGD-EN-01
Chapter 17 InfoObjects
The key figure shows the amount of the SAP FI document (financial accounting
document) that was created from the VIM invoice in local currency
(0LOC_CURRCY), which means the currency of the company code.
Technical data
Technical data
160 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
17.1. Key figures
Restriction No
Technical data
Technical data
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 161
VIM160304-RGD-EN-01
Chapter 17 InfoObjects
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No
Technical data
Available as of VIM 7.0
Release
Data element /B7999/OIKAPDURS
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No
Technical data
Available as of VIM 7.0
Release
Data element /B7999/OIKTODURD
Aggregation Summation
Exception Summation
Aggregation
Calculation Cumulative value
Restriction No
162 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
17.2. Characteristics
Technical data
17.2 Characteristics
Accounting Characteristic: 0AC_DOC_NO
document
number This characteristic shows the document number of the SAP invoice that was created
from the VIM invoice.
This characteristic classifies VIM invoices into different categories according to their
invoice amount. An example for an amount class from the VIM baseline is “Small
amounts” for invoices below 10,000 EUR. The amount classes and their ranges are
maintained in the KPI Dashboard customizing in the leading SAP S/4HANA system.
Technical data
This characteristic shows the input channel of the VIM invoice. The channels are
maintained in the VIM customizing of the leading SAP S/4HANA system.
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 163
VIM160304-RGD-EN-01
Chapter 17 InfoObjects
IMG activity: Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice
Management > Cross Component Configuration > Central Reporting > KPI
Dashboard > Company Code Groups > Company Code Groups Mapping (BW).
Technical data
Technical data
Technical data
164 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
17.2. Characteristics
Reference 0DATE
characteristic
Technical data
Created at Characteristic:/OPT/CCREATE
(UTC Time
Stamp in Short This characteristic shows the time stamp in UTC time (Coordinated Universal Time)
Form
(YYYYMMDDh
when the VIM invoice was created.
hmmss))
Technical data
Technical data
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 165
VIM160304-RGD-EN-01
Chapter 17 InfoObjects
Technical data
Technical data
This characteristic shows the VIM document type of the VIM invoice. The VIM
document types are maintained in the VIM customizing of the SAP S/4HANA
system.
Technical data
Technical data
166 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
17.2. Characteristics
Invoice exceptions that occur during the VIM process are grouped in exception
classes. This characteristic shows the exception class of an exception. Examples for
exception classes from the VIM baseline are “Compliance issue” and “Authorization
mismatch”. The exception class is determined from the exception class mapping in
the KPI Dashboard customizing of the leading SAP S/4HANA system.
Technical data
This characteristic shows the exception ID of an exception that occurred during the
VIM process. The exception IDs are maintained in the Central Reporting
customizing in the leading SAP 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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 167
VIM160304-RGD-EN-01
Chapter 17 InfoObjects
Technical data
Available as of VIM 7.0
Release
Data element /B7999/OICFINIDT
Reference 0DATE
characteristic
Technical data
Available as of VIM 7.0
Release
Data element /B7999/OICFINITM
Reference 0TIME
characteristic
Technical data
Available as of VIM 7.0
Release
Data element /B7999/OICFINISH
This characteristic shows the fiscal year of the SAP invoice that was created from the
VIM invoice.
168 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
17.2. Characteristics
Technical data
Technical data
Technical data
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 169
VIM160304-RGD-EN-01
Chapter 17 InfoObjects
Technical data
Technical data
Technical data
Technical data
170 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
17.2. Characteristics
Technical data
Technical data
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 171
VIM160304-RGD-EN-01
Chapter 17 InfoObjects
This characteristic shows the name of the logical system of the OLTP source system
(SAP S/4HANA system).
172 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
17.2. Characteristics
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
This characteristic shows the time type of a duration value. The time type classifies
durations within the VIM process. An example for a time type from the VIM
baseline is “On time” for VIM invoices that have been processed in 0 to 5 days. The
time types are maintained in the KPI Dashboard customizing in the leading SAP S/
4HANA system. The compounded characteristic Time Group determines whether
the time type refers to the processing time or the approval time.
Technical data
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 173
VIM160304-RGD-EN-01
Chapter 17 InfoObjects
Technical data
Technical data
This characteristic shows the vendor the VIM invoice was sent from.
This characteristic shows the vendor group, the VIM invoice is assigned to. The
vendor group classifies vendors into different groups regarding their total invoice
volume. An example for a vendor group from the VIM baseline is “Vendor Group A
(high volumes)”. You maintain the vendor groups in the KPI Dashboard
customizing of the leading SAP S/4HANA system. You maintain the mapping of
vendors to vendor groups in the local SAP S/4HANA system of the VIM invoice. If
the vendor of the VIM invoice is not assigned to a vendor group, the ABC indicator
from the purchasing organization data of the vendor master data is taken.
Technical data
174 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
17.3. Units
17.3 Units
Currency of Unit: 0INV_CURR
Invoice
This unit shows the document currency of the VIM invoice.
Technical data
This unit shows the local currency (this means the currency of the company code) of
the SAP FI document (financial accounting document) that was created from the
VIM invoice.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 175
VIM160304-RGD-EN-01
Chapter 18
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:
Technical data
This structure serves to consistently extract exception data to VIM invoices from
VIM to a SAP NetWeaver BW system. Only exceptions of finished invoices (= DP
workflow is finished) that are not obsolete or canceled are extracted.
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 177
VIM160304-RGD-EN-01
Chapter 18 DataSources
Technical data
178 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
18.2. DataSources for master data
Technical data
Technical data
This structure serves to consistently extract the texts of input channels from VIM to a
SAP NetWeaver BW system. The channels and their texts are maintained in the VIM
customizing of the leading SAP S/4HANA system.
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 179
VIM160304-RGD-EN-01
Chapter 18 DataSources
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/VIM_CHNL_T
Extraction /OPT/ESVIM_CHANNEL_TE0001
Structure
Technical data
Technical data
180 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
18.2. DataSources for master data
Technical data
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 181
VIM160304-RGD-EN-01
Chapter 18 DataSources
Technical data
Technical data
Technical data
182 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
18.2. DataSources for master data
Delta-Capable No
Extraction from No
Archives
Extraction by DB view/table /OPT/VT_EXC_T
Extraction /OPT/ESVIM_EXCEPT_TEX0001
Structure
Technical data
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 183
VIM160304-RGD-EN-01
Chapter 18 DataSources
Technical data
Technical data
184 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
18.2. DataSources for master data
Technical data
Technical data
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 185
VIM160304-RGD-EN-01
Chapter 19
DataStore objects (DSOs)
A DataStore object (DSO) serves as a storage location for consolidated and cleansed
transaction data or master data on a document (atomic) level. When being used as a
storage location for history reasons, the DSO may also store raw data.
The VIM BW content has been designed following the OpenText VIM Layered
Scalable Architecture (LSA), which groups the SAP NetWeaver BW objects into
different logical layers. The OpenText VIM LSA is based on the SAP LSA. For
details, see Section 26.1 “OpenText VIM Layered Scalable Architecture (LSA)” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD). The VIM BW content uses DSOs in the Data Propagation Layer
and in the Corporate Memory Layer.
This DSO contains VIM 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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 187
VIM160304-RGD-EN-01
Chapter 19 DataStore objects (DSOs)
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.
This DataStore object contains exceptions to VIM 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.
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.
188 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
19.1. DSOs of the Data Propagation Layer
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.
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.
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 VIM
customizing of the leading SAP S/4HANA system.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 189
VIM160304-RGD-EN-01
Chapter 19 DataStore objects (DSOs)
(/OPT/DCCHA) from the Corporate Memory Layer can be used for recovery purposes.
For both sources, all fields are updated in a 1:1 mapping into the DSO.
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.
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.
190 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
19.2. DSOs of the Corporate Memory Layer
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.
This DataStore object contains the VIM invoice headers as raw data as extracted by
the corresponding DataSource.
This DataStore object contains exceptions to VIM invoices as raw data as extracted
by the corresponding DataSource.
As a target of the DSO, the DSO Exceptions (/OPT/DPEXC) of the Data Propagation
Layer is supplied.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 191
VIM160304-RGD-EN-01
Chapter 19 DataStore objects (DSOs)
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.
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.
This DataStore object contains the possible input channels of VIM invoices as raw
data as extracted by the corresponding DataSource.
As a target of the DSO, the DSO Channel (/OPT/DPCHA) of the Data Propagation
Layer is supplied.
This DataStore object contains the texts of the possible input channels of VIM
invoices as raw data as extracted by the corresponding DataSource.
Data Sources/Data Targets – As a source of the DSO, the Channel Text DataSource
(/OPT/VIM_CHANNEL_TEXT) is used. All fields are updated in a 1:1 mapping into the
DSO.
192 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
19.2. DSOs of the Corporate Memory Layer
This DataStore object contains the texts of the possible types of input channels of
VIM invoices as raw data as extracted by the corresponding DataSource.
Data Sources/Data Targets – As a source of the DSO, the Channel Type Text
DataSource (/OPT/VIM_CHATY_TEXT) is used. All fields are updated in a 1:1 mapping
into the DSO.
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.
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.
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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 193
VIM160304-RGD-EN-01
Chapter 19 DataStore objects (DSOs)
As a target of the DSO, the DSO Exception Class Mapping for Exception (/OPT/
DPEID) of the Data Propagation Layer is supplied.
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.
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 Time Group Text
DataSource (/OPT/VIM_TIMEGR_TEXT) is used. All fields are updated in a 1:1
mapping into the DSO.
This DataStore object contains the possible time types as raw data as extracted by the
corresponding DataSource.
194 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
19.2. DSOs of the Corporate Memory Layer
Data Sources/Data Targets – As a source of the DSO, the Time Type DataSource (/
OPT/VIM_TIMETY_ATTR) is used. All fields are updated in a 1:1 mapping into the
DSO.
As a target of the DSO, the DSO Time Type (/OPT/DPTTY) of the Data Propagation
Layer is supplied.
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.
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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 195
VIM160304-RGD-EN-01
Chapter 20
MultiProviders
This chapter focuses on the final data targets in the Virtualization Layer: the
MultiProviders.
SAP recommends to create reports, for example BEx Queries, on MultiProviders and
not on InfoCubes directly. Therefore the VIM 7.0 BW content delivers
MultiProviders for all its InfoCubes. Technically, the MultiProviders are assigned to
the Virtualization Layer and can be found below the InfoArea with the same name
(OpenText Vendor Invoice Management > Reporting Layer > Virtualization Layer).
The VIM 7.0 BW content provides the following MultiProviders based on InfoCubes:
Note: A finished invoice in this context is an invoice that has finished the VIM
process. Cancelled and obsolete invoices are excluded (they are not loaded into
the SAP NetWeaver BW system).
• How many finished invoices have been processed with delay/on time?
• How many finished invoices have been approved with delay/on time?
• 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?
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 197
VIM160304-RGD-EN-01
Chapter 20 MultiProviders
• What is the exception free rate, which is the rate of “no real exceptions”, to
all finished invoices?
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.
Example: List of all DP documents with document type NPO_75 and channel ICC to
vendor 1000
Example: List of all DP documents with document type NPO_75 and channel ICC to
vendor 1000 that had at least one exception to exception class Auth. mismatch.
Example: List of all DP documents with document type NPO_75 and channel ICC to
vendor 1000 that had the exception Missing Item Quantity (PO).
198 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Part 6
Transactions and roles
Part 6 Transactions and roles
This part provides information about the transaction codes that various roles have
access to.
200 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 21
Transaction profiles for various roles
The following table shows domains, transactions, and the roles that have access to
the transactions.
Note: For roles ICC User and BCC User, see Section 5.1.2 “ERP users” in
OpenText Business Center Capture for SAP Solutions - Administration Guide
(CPBC-AGD). You might have to adjust the authorizations for ICC users after
you have installed the packages for Business Center Inbound Configuration in
addition to an existing VIM package. For more information, see Section 9
“Incoming document processing” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide (VIM160304-CGD).
Table headings
1 Indexer
2 AP Processor
3 AP Supervisor
4 Buyer
5 Receiver
6 Requester
7 Coder
8 Approver
9 WF Admin
Transaction Description 1 2 3 4 5 6 7 8 9
VIM
Notifications
VIM /OPT/REMINDER program X X
VIM Analytics
/OPT/ Current
VIM VAN_LIABILITY Liability Report X X
VIM /OPT/VIM_WP VIM Workplace X X X X X
SAP Business
SAP SBWP Workplace X X X X X
VIM /OPT/VIM_AGING Aging Report X X
Summary
VIM /OPT/VIM_SUMM Report X X
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 201
VIM160304-RGD-EN-01
Chapter 21 Transaction profiles for various roles
Transaction Description 1 2 3 4 5 6 7 8 9
Central Audit
VIM /OPT/VIM_AUDIT Report X X
Exception
VIM /OPT/VIM_EXCP1 Analysis Report X X
Key Process
Analytics
VIM /OPT/VIM_KPA1 Report X X
Productivity
VIM /OPT/VIM_PROD1 Report X X
Automation
VIM /OPT/VIM_ATM Report X
VIM /OPT/VIM_7AX8 Admin Tool X X X
Change
VIM /OPT/VIM_1AX1 document type X X X
Display
IDocument
VIM /OPT/VIM_1AX13 (indexed) X X X X X X X X
Change process
VIM /OPT/VIM_1AX2 type X X X
VIM /OPT/VIM_1AX3 Send for rescan X X X
Display BDC
VIM /OPT/VIM_1AX4 log X X X
Approval
baseline COA
VIM /OPT/AR_COA maintenance X X
Maintain
notification
VIM /OPT/VIM_8AX50 settings for me
VIM /OPT/VIM_VA2 VIM Analytics X X X X X X X X
VIM Analytics -
VIM /OPT/VIM_VA21 AP Basic X
VIM Analytics –
VIM /OPT/VIM_VA22 AP Advanced X
VIM Analytics -
VIM /OPT/VIM_VA23 Procurement X
VIM Analytics -
VIM /OPT/VIM_VA24 Monitor X
Display special
handling
VIM /ORS/DISP_SH instructions X X X X X
202 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Transaction Description 1 2 3 4 5 6 7 8 9
Resubmit Non-
/ORS/ PO invoice for
VIM RESUB_NPO_INV approval X X X
Resubmit PO
invoice for
VIM /ORS/RESUB_PO_INV approval X X X
Submit Non-PO
/ORS/ invoice for
VIM SUBMIT_NPO_INV approval X X X
Submit PO
/ORS/ invoice for
VIM SUBMIT_PO_INV approval X X X
Cancel PO
/PTGWFI/ invoice, re-enter
VIM CANC_INV_05 PO X X
Cancel PO
/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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 203
VIM160304-RGD-EN-01
Chapter 21 Transaction profiles for various roles
Transaction Description 1 2 3 4 5 6 7 8 9
/PTGWFI/
VIM M_CHG_CONTR Change contract X
Change logistic
VIM /PTGWFI/M_CHGLIV invoice X X
Goods receipt
for purchase
VIM /PTGWFI/M_CR_GR order X
Display
VIM /PTGWFI/M_DIS_REQ requisition X X X
Purchasing
documents for
VIM /PTGWFI/M_LIST_PO material X X X X
Release LIV
VIM /PTGWFI/M_LIX_REL blocked invoice X X
/PTGWFI/ Short pay LIX
VIM M_LIX_SHORTP invoice X X
Reverse goods
VIM /PTGWFI/M_REV_GR receipt for PO X
/PTGWFI/ Short pay:
VIM M_SPAY_2_CM credit memo X X
Short pay:
/PTGWFI/ subsequent
VIM M_SPAY_4_SC credit X X
Short pay:
/PTGWFI/ delete invoice/
VIM M_SPAY_INV create invoice X X
/PTGWFI/ Change parking
VIM PIR_CHG_PKRS reason X X X
All VIM
VIM /OPT* transactions X
All VIM
VIM /ORS* transactions X
All VIM
VIM /PTGWFI* transactions X
Workflow
SAP SW* transactions X
Development
SAP SE* transactions X
System
SAP SM13, SM50, SM12 monitoring X
SAP ST22, ST05, Dump analysis X
204 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Transaction Description 1 2 3 4 5 6 7 8 9
SAP SQ* SAP query X
SAP SCATT Test procedures X
SAP SHDB, SM35, SM35P BDC analysis X
OAWS, OAWD,
OAC2, OAC3, OAC0, SAP
OAA3, SOA0, OAM1, ArchiveLink
SAP OANR transactions X
Post NPO
SAP FB60 invoice X X
Display NPO
SAP FB03 invoice X X X X X X X X X
SAP MIRO Post PO invoice X X
Display PO
SAP MIR4 invoice X X X X X X X X X
SAP ME23N Create new PO X
SAP ME22N Change PO X
Change vendor
SAP XK02 master X
Create new
SAP XK01 vendor X
Create new
SAP ME51N requisition X
Change
SAP ME52N requisition X
List PO by
SAP ME2L vendor X X X X
SAP MIGO Post/reverse GR X
Unblock PO
SAP MRBR invoice X X X
Cancel PO
SAP MR8M invoice X X X
SAP ME31K Create contract X
SAP ME32k Change contract X
Update info
SAP ME12 record X
List PO by
SAP ME2M material X
Display change
SAP RSSCD100 documents X
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 205
VIM160304-RGD-EN-01
Chapter 21 Transaction profiles for various roles
Authorization objects
206 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Part 7
Business rules
Part 7 Business rules
This part provides an overview of all business rules applied in VIM. This part also
provides some technical insight to ease the using of the business rules. If needed the
related configuration aspect is mentioned.
208 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 22
General information about business rules
At the beginning of each business rule, a check is performed whether the business
rule is relevant for this specific document based on the customizing stored in table /
OPT/VIM_T005A (Characteristic Specific Process Types Configuration). The following
check is done:
• Invoice Characteristics
• Invoice type: A for All, N for NPO and P for PO. For example: If the coming
invoice is of type NPO but the rule is applicable for PO, the rule is not executed.
• Simplified Invoice (ignored or not): If this indicator is set, a FM is called to check
whether the invoice is a simplified one.
The check is executed based on the customizing in table /OPT/VIM_T005
(Characteristic Specific Process Types Configuration). If the fixed amount limit is
maintained, the amount of the invoice will be compared with this limit.
Otherwise if the Simplified Invoice Check FM is maintained, the FM is called.
When the invoice is determined as simplified, the rule is not applied for
simplified invoices.
• Invoice category: The invoice category maintained for the business rule (all
categories, intra-community, domestic, import, ...) is compared with the invoice
category of the indexing data. If it does not match, the rule is not executed.
Configuration Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > Document Type Configuration >
Characteristic Specific Document Type Configuration.
Double click the document type. The Characteristic Specific Attributes view opens.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 209
VIM160304-RGD-EN-01
Chapter 23
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.
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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 211
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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.
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.
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.
212 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.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.
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.
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 Vendor Invoice Management >
point Document Processing Configuration > General Configuration > Maintain
Duplicate Check Procedures
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 213
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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.
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.
214 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.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).
When this business rule is applied, the PO invoice is checked if all data - header and
item lines - is fully provided.
In contrast to the pre-7.5 business rule, this new version additionally checks if the
invoiced quantity on each line does not exceed the GR quantity (that has not been
invoiced yet). This can be switched off if needed, to achieve that the 7.5 business rule
performs only completeness checks. The corresponding configuration is described in
this section.
If line item data is complete, that means all mandatory fields are fully supplied, the
business rule is completed without any exception and the document proceeds to the
next logical step.
A line is considered incomplete if one or more mandatory fields are not fully
supplied.
Technical FM /OPT/VIM_DETERMINE_PROC_108
information
In this FM, all mandatory fields of item indexing data are checked.
• PO number
• PO item
• Quantity
• Amount
• UOM
• PO number
• PO item
• GR reference document
• Delivery note number (if available)
• Quantity
• Amount
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 215
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
• UOM
The exception is raised if at least one line is incomplete or missing (empty). The
missing fields are then determined by the settings of the document type
configuration, PO line determination maintenance.
As mentioned above, this business rule additionally checks whether the invoice
quantity on each line item does not exceed the corresponding GR quantity that is not
invoiced yet. For service POs, SES is checked similarly. This check is made by
default in VIM 7.5, but can be switched off if needed, to make this business rule
behave similarly to the 7.0 business rule and make only completeness checks. To
switch the additional checks off, create a new entry in the table /PTGWFI/Z_CONST,
using the SM30 transaction:
Determined
The corresponding PO line number is determined based on the supplier’s
invoice information. In this case, no action is taken and the document proceeds
to the next logical step.
Unable to Determine
The corresponding PO line number is not determined based on the supplier’s
invoice information. The exception Unable to Determine PO Line Number (PO)
is raised, and the work item is automatically routed to the pre-configured agent
depending on the role for further action.
Technical FM /OPT/VIM_DETERMINE_PROC_POL
information
Item data of the PO is read from table /OPT/VIM_1ITEM.
The item number is determined based on the PO Line Determination logic group ID
(POL_GROUPID). This POL Group ID is maintained for each document type in the
Document Type configuration.
216 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.9. Unable to Determine PO Line Number (PO)
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.
If field ALL_MATCH is set, all fields must be matched. Otherwise the number of
matched fields is given in field NOF_FIELDSMATCH.
If field INVOICED_LINES is checked, only item lines marked as Final Invoice (field
EREKZ is marked – meaning that the item is already invoiced and no further invoice
is expected) will be considered.
After the matching, each pair PO number and determined Item Number are checked
against table EKPO. If there is no match -> Exception.
Configuration Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > General Configuration > Automated Line
Processing > PO Line Determination > Maintain PO Line Determination
Procedures.
Notes
• The field entered in the POL configuration shall be a valid field. A field that
exists in /OPT/VIM_1ITEM can be entered in the configuration, but it will be
ignored in the POL logic if it does not exist in SAP table EKPO. Except the
following fields which are internally re-mapped from VIM fields to SAP
fields:
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 217
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
When this business rule is applied, the PO invoice is checked if all data – header and
item lines – is fully provided. The difference between this business rule and the
business rule Unable to Determine PO Line Number is listed in the following:
• This business rule not only checks the PO line number, it checks also other
mandatory fields of the PO.
• Not only the PO line number, but also other mandatory fields, which are not
supplied in the document, will be derived in background.
Complete
If line items data is complete, that means all mandatory fields are fully supplied,
the business rule is completed without any exception and the document
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
• PO number
• PO item
• Delivery Note/GR Reference Document
• Quantity
218 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.11. Invalid PO Item Number (PO)
• 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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 219
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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.
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
220 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.13. Incomplete Credit Memo (PO)
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).
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:
If CM Ref No is required for CM but the field CM REF NUMBER in the indexing is
left blank -> Exception
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 221
VIM160304-RGD-EN-01
Chapter 23 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 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:
CM Ref No Req.
CM reference number is required.
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.
222 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.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.
• House #
• Street
• Postal Code
• City
• Region
• Country
Technical FM /OPT/VIM_DETERMINE_PROC_122
information
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 223
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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.
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
When this business rule is applied, the tax information provided on the vendor
invoice is analyzed and mapped to standard SAP tax values (tax codes) and passed
onto the DP document. Depending on the VIM specific tax configuration settings
(with auto calculate tax or without auto calculate tax), the tax information is
validated and, in case of any deviations, the exception Invalid Tax Info (PO) is
raised and the invoice is routed to the pre-configured agent depending on the role
for further action. There are many scenarios that can arise depending on the
configuration. In the following, some of the possible scenarios are described:
Example: The VAT % mentioned on the invoice has a corresponding VAT tax code.
224 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.18. Invalid Tax Info (PO)
Example: The VAT % mentioned on the invoice does not have a corresponding VAT tax
code in SAP S/4HANA.
Example: The payable VAT % or VAT amount is not present on the vendor’s invoice.
• 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:
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).
– 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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 225
VIM160304-RGD-EN-01
Chapter 23 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 tax_amount # 0 but tax_code in header or in all line items is not given ->
Exception
If auto_calc is checked:
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.
226 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.19. Missing Date of Supply (PO)
For all Canada-specific customizing, run the /n/OPT/SPRO transaction and navigate
to Vendor Invoice Management > Document Processing Configuration >
Document Type Configuration > Specific Country Settings > Canada.
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:
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 227
VIM160304-RGD-EN-01
Chapter 23 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.
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:
228 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.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).
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.
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 229
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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.
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.
230 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.25. Vendor Invoice Reference Missing (PO)
Technical If field XBLNR of the indexing data is not filled with the reference number ->
information Exception
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).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 231
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
• 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.
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.
232 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.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.
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.
Configuration Fields on the DP document can be maintained in /OPT/SPRO on the following levels:
point
On header level
Vendor Invoice Management > Document Processing Configuration >
Document Type Configuration > Maintain Document Types.
Select the DP Document Type. In Dialog Structure, double-click Index Header
Configuration.
On item level
Vendor Invoice Management > Document Processing Configuration >
Document Type Configuration > Maintain Document Types.
Select the DP Document Type. In Dialog Structure, double-click Index Item
Configuration.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 233
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
Technical FM /OPT/VIM_DETERMINE_PROC_139
information
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.
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.
234 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.32. Invalid Sales Tax for the Region (PO)
Default Region
Company code address/PO address are used as ship-to region. The business
rule proceeds with the above scenarios. You can configure this derivation of
the ship-to region on VIM side.
Blank
Keep the not present information as blank and raise exception Invalid
Sales Tax for the Region (NPO). The document is automatically routed to
the pre-configured agent depending on the role for further action.
Notes
• If VIM is used in combination with ICC, the ship-to region is not supplied by
ICC.
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.
Company Code
The ship-to region is determined based on the company code and read from
table T001.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 235
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
Fixed Value
The region maintained in table /OPT/VIM_STR_DET is used as ship-to region.
Function Module
The FM maintained in table /OPT/VIM_STR_DET is used to determine the
ship-to region.
Second step
After all tax rates (in header as well as on line items) are determined, they will
be checked against table /OPT/VIM_TAX_PRO. If some tax rates are required
according to the customizing table, but not given in the invoice or cannot be
determined in the first step, the exception is raised.
Customization Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > Document Type Configuration > Specific
Country Settings > Canada.
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”.
236 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.34. Vendor Maintenance (PO)
Customization point
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 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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 237
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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 VIM 7.0 SP3 and later, the two Z constants SERVICE_ENTRY_BSTYP and
SERVICE_ENTRY_BSART (product code 005) are not used any more.
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.
238 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.38. Unit of Measure Mismatch (PO)
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
different, the MIRO proposal is calculated and the UOM is compared to the MIRO
proposal.
Additional change in VIM 7.0 and higher: Line items with qualifiers (additional
costs) are not considered for UOM matching because they are line items that
transport costs only.
Technical FM /OPT/VIM_DETERMINE_PROC_150
information
Customization Run the /n/OPT/VIM transaction and navigate to OpenText Vendor Invoice
point Management > SAP menu > Customization > PO Invoice Approval Configuration.
Note: If the exception is triggered, a work item is created and forwarded to the
requisitioner of the PO if this requisitioner is maintained in COA (Chart of
Authority). If not, no agent can be found for the current work item.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 239
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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.
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.
240 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.42. Invalid Requisitioner (PO)
Customization point
• Transaction /OPT/VIM_BL_PTX, or
• run the /n/OPT/VIM transaction and navigate to OpenText Vendor Invoice
Management > SAP menu > Customization > Tax Audit Configuration for PO
Invoices.
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
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 239. Only if the invoice is going through
the approval process, the system will perform the following checks.
3. If the PO number is given in the PO document, the system checks whether it is
SRM-related or not.
To perform this check, the status of the PO is compared with the status
maintained in the Z table under the Z constant SRM_PO_STATUS. If it matches, the
PO is considered as SRM-related.
4. For an SRM-related PO, no further check is done. For a non-SRM-related PO, the
system performs the checks in the following order.
5. 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.
6. 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,
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 241
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
the system checks the user map table. If the user is not available there, the
exception is raised.
7. 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.
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
242 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.45. Confirmation Required from SRM (PO)
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.
Technical FM /OPT/VIM_DETERMINE_PROC_162
information
• All POs on the invoice are checked whether they are SRM-related or not. If there
is a FM maintained in the constant LIX / SRM_PO_CHECK, this FM is called for the
checking. If there is no FM maintained, the status of the PO is compared with all
statuses maintained in the Z constant LIX / SRM_PO_STATUS. If the status matches,
the PO is considered as SRM-related.
• If the PO is SRM-related, a line item has a GRIV flag, and no GR or multiple GRs
exist for this item -> exception
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 243
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
Technical To use this business rule, the INVOICE_CODE field must be configured as required
information field.
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.
244 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.51. Invalid Vendor Invoice Number (PO)
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 245
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
• 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.
Technical To use this business rule, the VEND_NAME field must be configured as required field.
information
246 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.59. Missing Recipient Name (PO)
Technical To use this business rule, the RECIPIENT_NAME field must be configured as required
information field.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 247
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
248 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.68. Missing Vendor LST Number (PO)
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 249
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
• 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.
• 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.
250 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.76. Service Entry Required (PO) - Enhanced Check
For this, a new business rule 166 Service Entry Required (PO) - Enhanced Check
has been introduced in VIM 7.5 SP5. If the DP line item amount is higher than the
open amount to be invoiced, the system raises the exception.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 251
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
• 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.
• 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.
• 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.
252 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.84. Russia - Wait for TORG-12/ACT - Enhanced Check (PO)
• For any PO item within indexing data (header/item), the delivered PO lines are
checked if any line has the GR-IV based flag set.
• For these lines, it is checked that all lines are open for invoicing with the correct
amount.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 253
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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.
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.
The baseline configuration of this business rule contains predefined process options.
You can adjust the process options list to suit your scenarios.
254 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.92. Down Payment Clearing (PO)
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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 255
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
Then this exception is raised and the invoice is automatically routed to the pre-
configured agent depending on the role for further action.
In these cases, this exception is raised. The invoice is automatically routed to the pre-
configured agent depending on the role for further action.
256 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.97. Cannot Verify Quantity/Price Exceptions (PO)
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 257
VIM160304-RGD-EN-01
Chapter 23 Business rules for PO invoices
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_437
Information
When the business rule is triggered, the Transport Order 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.
258 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
23.104. Check Vendor/Company Address (PO/NPO)
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 259
VIM160304-RGD-EN-01
Chapter 24
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.
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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 261
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
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.
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.
262 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.5. Non-PO Credit Memo 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.
All invoices of other vendors shall have the Expense Type ST - Standard.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 263
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
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.
• House #
264 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.10. Missing Invoice Date (NPO)
• Street
• Postal Code
• City
• Region
• Country
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
When this business rule is applied, the tax information provided on the vendor
invoice is analyzed and mapped to standard SAP tax values (tax codes) and passed
onto the DP document. Depending on the VIM specific tax configuration settings
(with auto calculate tax or without auto calculate tax), the tax information is
validated. In case of any deviations, the exception Invalid Tax Info (NPO) is
raised, and the invoice is routed to the pre-configured agent depending on the role
for further action. There are many scenarios that can arise depending on the
configuration. In the following, some of the possible scenarios are described:
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 265
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
Example: The VAT % mentioned on the invoice does not have a corresponding VAT tax
code in SAP S/4HANA.
Example: The payable VAT % or VAT amount is not present on the vendor’s invoice.
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.
266 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.13. ISR Number Mismatch (NPO)
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:
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 267
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
Technical The field SUPPLY_DATE must be filled. If it is not, the exception is raised.
information
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.
268 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.17. Invalid Company Address (NPO)
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 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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 269
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
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.
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.
270 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.21. Missing/Invalid Tax Exempt Text (NPO)
• 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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 271
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
272 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.26. Invalid Sales Tax For The Region (NPO)
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.
Blank
Keep the not present information as blank and raise exception Invalid
Sales Tax for the Region (NPO). The document is automatically routed to
the pre-configured agent depending on the role for further action.
Notes
• If VIM is used in combination with ICC, the ship-to region is not supplied by
ICC.
• VIM uses company code/PO (based on the configuration option chosen) to
derive the ship-to region when ICC is used as OCR. For cases where
company code cannot be used to derive the ship-to region, you must apply
either a custom function or a manual entry.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 273
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
Customization Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > Document Type Configuration > Specific
Country Settings > Canada.
Customization Run transaction /n/OPT/SPRO and navigate to Vendor Invoice Management >
point 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.
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.
274 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.29. Tax Audit Required (NPO)
For more information, see “Vendor Audit Required (PO)” on page 236.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 275
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
To use this business rule, you must maintain and activate the new process type 271
in the document type configuration, navigating to /OPT/SPRO > Vendor Invoice
Management > Document Processing Configuration > Document Type
Configuration > Maintain Document Types. For background information, see
Section 11.1.2 “Defining process types” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide (VIM160304-CGD).
In the Baseline configuration, the process type is not characteristic specific (the
Characteristic Check check box is not set). Therefore, you do not have to maintain
the process type for characteristic.
In the document type configuration, Sequence Steps, use the function module /
OPT/VIM_DETERMINE_PROC_LIB004 as Check Function for DP Document Type
NPO_75, Step ID 418. For background information, see Section 11.1.3.1 “Defining
sequence steps” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM160304-CGD).
In the Baseline configuration, the business rule is added to the document type
NPO_75 but it is not activated.
276 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.32. Invalid Payment Reference (NPO)
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 To use this business rule, the INVOICE_CODE field must be configured as required
information field.
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.
• Digits from 0 to 9
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 277
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
278 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.40. Verification Required (NPO)
Technical To use this business rule, the VEND_NAME field must be configured as required field.
information
Technical To use this business rule, the RECIPIENT_NAME field must be configured as required
information field.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 279
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
280 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.50. Missing Vendor CST Number (NPO)
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 281
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
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.
The baseline configuration of this business rule contains predefined process options.
You can adjust the process options list to suit your scenarios.
282 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
24.59. Check Withholding Tax Data (NPO)
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.
• 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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 283
VIM160304-RGD-EN-01
Chapter 24 Business rules for NPO invoices
In these cases, this exception is raised. The invoice is automatically routed to the pre-
configured agent depending on the role for further action.
284 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 25
This section describes general business rules that are independent from NPO or PO.
To leave the exception, you must choose one of the following options:
• Activate bypass
• Send to rescan
• Obsolete document
You cannot leave the exception by changing data, by clicking Apply Business Rules,
or by referring the document to another user.
Note: As of VIM 7.0 SP3, only the Ariba inbound interface triggers this.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 285
VIM160304-RGD-EN-01
Chapter 25 General business rules
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.
286 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 26
Summary tables
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 287
VIM160304-RGD-EN-01
Chapter 26 Summary tables
288 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
26.1. Table: Business rules for PO invoices
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 289
VIM160304-RGD-EN-01
Chapter 26 Summary tables
290 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
26.1. Table: Business rules for PO invoices
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 291
VIM160304-RGD-EN-01
Chapter 26 Summary tables
292 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
26.2. Table: Business rules for NPO invoices
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 293
VIM160304-RGD-EN-01
Chapter 26 Summary tables
294 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
26.2. Table: Business rules for NPO invoices
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 295
VIM160304-RGD-EN-01
Chapter 26 Summary tables
296 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 27
Customer library
Besides the business rules delivered along with VIM Baseline, you can create custom
business rules as well as implement custom function modules for your business
rules to meet your needs. OpenText delivers some function module templates that
you can configure or implement. The functions are example functions.
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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 297
VIM160304-RGD-EN-01
Chapter 27 Customer library
• 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.
298 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Part 8
Logic modules
Part 8 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.
300 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 28
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.
• Global processing
• PO processing
• NPO processing
• Country specific
The VIM baseline customizing contains preconfigured process IDs that you must
map to PO and NPO document types. Some global processing is active for all
document types.
Configuration Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
point Document Processing Configuration > Document Type Configuration > Logic
Module Processing.
For details, see Section 11.4 “Processing logic modules” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 301
VIM160304-RGD-EN-01
Chapter 29
Global Processing Logic Modules
Precondition
Vendor number and company code are filled.
Data affected
Vendor group
Class interface
/OPT/CL_D_LM_CHG_V_GRP
Category
Mapping
Precondition
Partner bank type is empty.
Data affected
All bank data is filled if available in vendor master.
Class interface
/OPT/CL_D_LM_DETERM_BANKDATA
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 303
VIM160304-RGD-EN-01
Chapter 29 Global Processing Logic Modules
Category
Simple mapping
Precondition
SAP document type is empty.
Data affected
SAP document type is filled.
Class interface
/OPT/CL_D_LM_DETERM_BLART
Category
Simple mapping
Precondition
Invoice category is filled from ICC.
Data affected
Invoice category contains a VIM specific value.
Class interface
/OPT/CL_D_LM_DETERM_INV_CAT
Category
Mapping
Precondition
Document type, vendor number and company code are filled.
Data affected
Payment terms are filled.
304 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
29.6. Determine Payment Baseline Date
Class interface
/OPT/CL_D_LM_DETERM_PAY_TERM
Category
Mapping
Precondition
Payment baseline date is empty.
Data affected
Payment baseline date is filled.
Class interface
/OPT/CL_D_LM_DETERM_PBL_DATE
Category
Simple mapping
Precondition
Posting date or posting date determination is empty.
Data affected
Posting date is filled.
Class interface
/OPT/CL_D_LM_DETERM_POST_DATE
Category
Simple mapping
Precondition
Tax code is empty.
Data affected
Tax code is filled.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 305
VIM160304-RGD-EN-01
Chapter 29 Global Processing Logic Modules
Class interface
/OPT/CL_D_LM_DETERM_TAX_CODE
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
Category
Simple mapping
Precondition
Vendor number is filled.
Data affected
Vendor address is filled.
Class interface
/OPT/CL_D_LM_DETERM_V_ADR
Category
Simple mapping
Precondition
Vendor number and company code are filled.
Data affected
Vendor group is filled.
306 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
29.12. Determine Vendor Name
Class interface
/OPT/CL_D_LM_DETERM_V_GRP
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
Category
Mapping
Precondition
Vendor number and company code are filled and subject to withholding tax.
The following data is required to retrieve withholding tax.
For PO documents
• Company code
• Vendor
• Total gross amount
• PO number
• Tax code for net or tax based withholding tax type
• Company code
• Vendor
• Total gross amount
• Currency
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 307
VIM160304-RGD-EN-01
Chapter 29 Global Processing Logic Modules
• Posting date
• At least one line item
Data affected
Withholding tax data is filled.
Class interface
/OPT/CL_D_LM_FILL_WHT
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
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
308 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
29.16. Tax Invoice Determination
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
Category
Document creation
Precondition
This needs to be activated in the process type assignment in the VIM document
type. For more information, see Section 11.3.2 “Configuring automatic parking
after the start of the DP process” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM160304-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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 309
VIM160304-RGD-EN-01
Chapter 29 Global Processing Logic Modules
Category
Document creation
Precondition
This needs to be activated in the process type assignment in the VIM document
type. For more information, see Section 11.3.2 “Configuring automatic parking
after the start of the DP process” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM160304-CGD).
Data affected
The logic module automatically tries to create a held document.
Class interface
/OPT/CL_D_LM_CREATE_HOLD
Category
Document creation
Precondition
This needs to be activated in the process type assignment in the VIM document
type. For more information, see Section 11.3.2 “Configuring automatic parking
after the start of the DP process” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM160304-CGD).
Data affected
The logic module automatically tries to create a completely parked document.
Class interface
/OPT/CL_D_LM_CREATE_PARK_COMP
310 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
29.20. Create Parked Document in Background
Category
Document creation
Precondition
This needs to be activated in the process type assignment in the VIM document
type. For more information, see Section 11.3.2 “Configuring automatic parking
after the start of the DP process” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM160304-CGD).
Data affected
The logic module automatically tries to create a parked document.
Class interface
/OPT/CL_D_LM_CREATE_PARK
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 311
VIM160304-RGD-EN-01
Chapter 30
PO related logic modules
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
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 313
VIM160304-RGD-EN-01
Chapter 30 PO related logic modules
Category
Mapping at process start
Precondition
PO number is filled.
Data affected
PO item data is retrieved.
Class interface
/OPT/CL_D_LM_DETERM_PO_MAP
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 ICC 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.
314 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
30.5. Determine Vendor
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
Category
Simple mapping
Precondition
Address data of CPD vendor is empty in VIM tables.
Data affected
Address data of CPD vendor is filled from purchase order.
Class interface
/OPT/CL_D_LM_DETERM_CPD
Category
Mapping
Precondition
PO number(s) provided, and ICC delivers valid additional cost lines.
Data affected
Depending on the VIM additional cost customizing
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 315
VIM160304-RGD-EN-01
Chapter 30 PO related logic modules
Class interface
/OPT/CL_D_LM_MAP_ADD_COSTS
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
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
316 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
30.10. Process Line Items from OCR
Category
Mapping at process start
Precondition
Channel ICC. 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 11.1.1 “Creating a new DP document type” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
Class interface
/OPT/CL_D_LM_DETERM_PO_OCR
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 317
VIM160304-RGD-EN-01
Chapter 31
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
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
Category
Mapping at process start
Precondition
No purchase order numbers or delivery notes are used on the invoice.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 319
VIM160304-RGD-EN-01
Chapter 31 NPO related logic modules
Data affected
Line item coding data is filled.
Class interface
/OPT/CL_D_LM_DETERM_NPO_COD
Category
Mapping at process start
Precondition
Channel ICC. 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 11.1.1 “Creating a new DP document type” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
Class interface
/OPT/CL_D_LM_DETERM_NPO_OCR
Category
Simple mapping
Precondition
Line items present
Data affected
Existing NPO line items are enriched with posting relevant information:
• 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
320 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 32
Country specific logic modules
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
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 321
VIM160304-RGD-EN-01
Chapter 32 Country specific logic modules
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
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
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.
322 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
32.6. Enrich Country Specific Data for France
Class interface
/OPT/CL_D_LM_DETERM_COUNTRY_CN
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
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 323
VIM160304-RGD-EN-01
Part 9
Automated Field Enhancement
Part 9 Automated Field Enhancement
VIM provides a feature that allows you to add mapping activities after the field
mapping is done. In this Automated Field Enhancement (also called enhanced
mapping), you can refer to the values of different fields.
326 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 33
Configuring Automated Field Enhancement
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 329 shows
the relation between source fields and target fields.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 327
VIM160304-RGD-EN-01
Chapter 34
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 329
VIM160304-RGD-EN-01
Chapter 34 Baseline of Automated Field Enhancement
330 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Mapping ID Type Sources Target field Function module
ICC Header PAN_NO, LIFNR, VENDOR_VAT_N /OPT/
LFA1 O VIM_EXIT_MAP_E
NH_07
ICC Header STC_NO, LIFNR, VENDOR_TAX_N /OPT/
LFA1 O VIM_EXIT_MAP_E
NH_07
ICC Header VENDOR_TAX_N SIRET_NO /OPT/
O VIM_EXIT_MAP_E
NH_07
ICC Header LIFNR, LFA1, REMIT_STREET /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_HSNM1 /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_PSTLZ /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_LAND1 /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_AD_CITY1 /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header LIFNR, LFA1, REMIT_REGIO /OPT/
ADRC VIM_EXIT_MAP_E
NH_02
ICC Header BNKA SWIFT /OPT/
VIM_EXIT_MAP_E
NH_08
ICC Header IBAN, SWIFT, BANKS /OPT/
BNKA VIM_EXIT_MAP_E
NH_08
ICC Header BUDAT POST_DATE_DET /OPT/
VIM_EXIT_MAP_E
NH_03
ICC Header BUKRS, T001, SHIPTO_PO_BOX /OPT/
ADRC VIM_EXIT_MAP_E
NH_09
ICC Header BUKRS, T001, SHIPTO_LAND1 /OPT/
ADRC VIM_EXIT_MAP_E
NH_09
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 331
VIM160304-RGD-EN-01
Chapter 34 Baseline of Automated Field Enhancement
332 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Mapping ID Type Sources Target field Function module
XML_ENFE Header Rx_PSTLZ REMIT_PSTLZ /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_AD_CITY1 REMIT_AD_CITY1 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_LAND1 REMIT_LAND1 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Rx_REGIO REMIT_REGIO /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header BUKRS, CDC, BUKRS /OPT/
T001Z VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM XBLNR /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM9 NFNUM9 /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header NFNUM NFNUM /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header J_1BAA NF_TYPE /OPT/
VIM_EXIT_MAP_E
NH_IDH_NFE
XML_ENFE Header Fix: BRL WAERS
XML_ENFE Header Fix: X AUTO_CALC
XML_ENFE Header Fix: X FLAG_ENFE
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 333
VIM160304-RGD-EN-01
Part 10
Z constants
Part 10 Z constants
This part provides a list of the Z constants that are used in VIM. There are individual
chapters for each product code.
002, 009
Cross component product codes
005
Document Processing (DP) based product codes
IAP
Invoice Approval product codes
IEA
Product codes for Unified Dashboard and archiving supports
IEM
Invoice Exception Monitor product codes
KPI
KPI Dashboard product codes
LIX
LIV based product codes (both for PO parking and PO blocking workflows)
PIR
Product codes for Non-PO parking workflows
VAN
VIM Analytics product codes
336 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 35
Z constants for product code 002 and 009
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 337
VIM160304-RGD-EN-01
Chapter 35 Z constants for product code 002 and 009
338 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Tolerenace % limit
002 PAYASISTOLERANCE for Pay-As-Is 100
Max val Tolerance
for Pay-As-Is
( giveCurr by
placing a “;” - Eg.
002 PAYASIS_MAX_VAL_TOLE 100;USD) 1000000;USD
Search help for
002 SHLP_ON_APPROVER Initial Approver /PTGWFI/SH_APB
Function module to
be called to build
short pay
SHORTPAY_BDC_CAN_IN transactions
002 V Cancel/Create Inv
Function module to
be called to build
short pay
transactions for SC/
002 SHORTPAY_BDC_SC_DM DM
Supress -
“Continue with out
workflow” Button
002 SUP_CONT_WO_WF_BUTT on parking screen
Supress “Return to
invoice” Button on
002 SUP_RETN_TO_INV_BUTT parking screen
Wait data Display /PTGWFI/
002 WAIT_DATA_DISP_FM Function Module 0000000002_TMP002
Function module to /PTGWFI/
002 WAIT_DATA_GET_FM get the wait data 0000000002_TMP001
Set to X to 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 Workplace, VIM Analytics and VIM Unified Dashboard.
For more information, see Section 8.6 “Restricting ALV layout for process logs” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
Set to X to activate
all authorization
009 AUTH_CHECK_ACTIVE checks in VIM
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 339
VIM160304-RGD-EN-01
Chapter 35 Z constants for product code 002 and 009
340 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 36
Z constants for product code 005
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 341
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
342 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
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.
Use Business
Center for SAP
Solutions Inbound
Configuration (X-
005 BC_INBOUND Yes, space -No)
Use OpenText™ Business Center for SAP® Solutions Inbound Configuration to
register and pre-process documents.
X = Use Business Center Inbound Configuration.
For VIM 16.3, setting the X is mandatory.
Values: X = active, <space> = not active
For more information, see Section 10 “ICC integration” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-CGD) and Section
24.1.1 “Configuring inbound processing (InvoiceDetailRequest)” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
BDC Id to be called
by Function /OPT/
VIM_PREPOPULA
005 BDC_PARKING_ONLINE TE_MIR7 16
This constant is used in the FM /OPT/VIM_PREPOPULATE_MIR7. The FM is
used in BDC 201 to support PO invoice parking online in a special case with
multiple POs existing in the invoice. The BDC maintained in this constant is used
for the online parking option maintained with BDC 201.
BDC Id to be called
by the function /
OPT/
VIM_PREPOPULA
005 BDC_PARK_ONLINE TE_MIR7 16
This constant is not used.
BDC Id to be called
by Function /OPT/
VIM_PREPOPULA
005 BDC_POSTING_ONLINE TE_MIRO 1
For more information, see Section 11.11.3 “Enhancing MIRO for pre-population of
data during online invoice creation” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide (VIM160304-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 343
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
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 ZVIM_GET_TAX_AMOUNT
To solve the problem of incorrect tax and balance calculation in specific situations
for Brazil and Indian invoices, VIM 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.
Start VIM process
in Central System
always (X=via RFC,
C=direct call,
005 CENTRAL_VIM_PROCESS empty=no)
This constant is related to starting a new DP process in VIM. It indicates whether
the new DP process should always be started in the central system or not. There
are two variants to start the DP workflow in the central system:
X: start via RFC
C: start by direct function call
Check Rules
005 CHECKRULES_OPTION Option 2737
This constant is obsolete.
Checks if Update
Tasks are running
005 CHK_UPD_TSK_IS_ALIVE (when set to 'X') X
344 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Description – When running a process option based on a call transaction (posting
or parking), the system checks if the update tasks are running. If not, a message
Update delayed. Please wait. is shown to the user.
--> Result in case 1 and 2: The workflow stays in the current state and can be
continued later.
Logging – If you activate the check, an application log entry (SLG1) is written:
Object: VIM, Subobject: DP, LogPoint 94 (Update Delayed), if any update delay
that is longer than 10 seconds was discovered.
Scope – Activate this function if the system often experiences issues with update
tasks or inconsistencies between posted documents and VIM data. The additional
check improves the stability when posting invoices in dialog in these
environments. However, the check can slightly slow down processing.
Flag (x = manual
change of BRF-
Bypass allowed in
COMPL_ALLOW_M_BYPA Simulation/Bypass
005 SS Popup) X
If set to X, a manual change of activate/bypass is allowed in the DP simulation
screen. For more information, see Section 11.5.3 “Additional configuration” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-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 11.5.3 “Additional configuration” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
If random number
(0-100) is bigger
than minimum
value run rule
005 COMPL_RANDOM_MIN check 50
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 345
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
346 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
User exit for
customer RFC
function for PO
CUSTOM_ICC_PO_DOWNL download from
005 D ICC
For more information, see Section 10.1 “Defining frequently used default values”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-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, VIM provides some baseline
information. If you want to add specific data, you can add it in this function
module. See also Section 11.11.3 “Enhancing MIRO for pre-population of data
during online invoice creation” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM160304-CGD).
Display invoice
image on display
of dash board
DASHBOARD_IMAGE_AU screen(X- Yes,
005 TO space -No)
For more information, see Section 11.1.10 “Configuring automatic image display”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
Display no Logo
005 DASHBOARD_NO_LOGO (Dashboard)
For more information, see Section 18.3.2.2 “Enhanced Application” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
Exit FM to
influence the
dashboard buttons
005 DB_OPTION_SEQ (old index screen)
You can set a custom function to change the sequence of process options in the
dashboard. For the interface of the function, check the Release Notes of VIM 7.0
SP3 or VIM 6.0 SP8.
As this Z constant refers to the old index screen, it is only valid for VIM versions
7.0 and earlier.
Default Archive
005 DEFAULT_AR_OBJECT Document Type /OPT/ICC
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 347
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
348 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Delay trigger
Approval
Workflow (number
entered is
multiplied by 5
005 DELAY_IAP_EVENT_CREA seconds) 3
This constant has been introduced 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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 349
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
350 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Maintain the VIM document type that should be set if a Down Payment is posted
directly from the SAP transaction without going through the regular VIM DP
workflow. This is required because no VIM document type determination takes
place in this case.
DP Doc type for
Non-PO when
document is
parked or posted
directly from SAP
005 DOCTYPE_NPO transaction NPO_75
Maintain the VIM 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 VIM DP workflow, where “with”
means running the Delete(Cancel) and Re-enter process option. This is
required because no VIM 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_75
Maintain the VIM 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 VIM DP workflow, where “with”
means running the Delete(Cancel) and Re-enter process option. This is
required because no VIM document type determination takes place in this case.
Default DP Doc
005 DP_DOC_TYPE type NPO_75
For more information, see Section 10.1 “Defining frequently used default values”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD) and Section 10.4 “Document type determination rules engine”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
If set to 'X', DP Doc
type will be
redetermined
DP_DOC_TYPE_REDETRM (before starting DP
005 N workflow) X
For more information, see Section 10.4 “Document type determination rules
engine” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM160304-CGD).
If set, a SAP
document posted
or parked outside
of VIM will be
005 DP_FOR_SAPDOC registered in VIM X
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 351
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
352 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
This constant has been introduced in VIM 7.0 SP8 and VIM 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, parked, 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
All business rules are run at the beginning of the DP process to collect the
information for the logging infrastructure. If this is causing performance
problems, to switch off the simulation of all business rules, set this constant value
to X.
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 11.18.2 “Implementing custom field validation
in the DP indexing screen” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM160304-CGD).
005 EDI_CHANNEL_ID EDI Channel ID IDOC
Maintain the channel ID that is used during processing of an incoming IDOC.
EDI visualization/
image archiving
exit (Template: /
OPT/
EDI_IMAGES_EXI
005 EDI_IMAGES_FM T_TEMP)
This Z constant is obsolete.
Extended IIC:
Function module to
determine object
005 EIIC_DET_OBJ_KEY key
This constant is obsolete since VIM 7.5 because Integrated Invoice Cockpit is
discontinued.
Extended IIC:
Function module to
update customer
005 EIIC_UPD_CUSTFIELDS fields
This constant is obsolete since VIM 7.5 because Integrated Invoice Cockpit is
discontinued.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 353
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
354 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-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 VIM 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 (VIM160304-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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 355
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
356 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
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.
Customer specific
function module
for adding
metadata for ICC
005 ICC_METADATA_ADD extraction
For more information, see Section 17.1 “Overview” in OpenText Vendor Invoice
Management for SAP Solutions - Scenario Guide (VIM160304-CCS).
Archive
DocumentType
Substring to be
watched - for
breakpoints and
005 ICC_WATCHTYPE logs
Specify a string with maximum 10 characters to be found among the first 4
document types of a query. If the string is found, the logs will be written with log
point 96 instead of 95.
URL to show
Configuration
Documentation for
005 IMG_DOCU_URL IMG http://www.opentext.com
For more information, see Section 11.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-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 244 and
“Invoice Older than Allowed (NPO)” on page 278.
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
(VIM160304-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 357
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
358 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
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 (VIM160304-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.
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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 359
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
360 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
NO_SYNC_HEADFLDS_NP Invoice header
O field names, will
not be sync'ed with
BSEG after posted
005 (NPO) 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
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 VIM 7.5 SP3 (VIM 7.0 SP7) to restrict the number
of line items for background posting. This constant can avoid that workflows get
stuck due to background posting time outs. If the number of line items exceeds
the customized value, the workflow is sent to the processor and can be posted
manually.
Custom Number
Range Object for
Document
005 NUMBER_RANGE_OBJECT Processing
For more information, see Section 11.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 361
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
<SPACE> (default) or ON
Web Viewer/Brava! View 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.
362 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
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 11.8 “Configuring DP process options” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-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 11.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
Reminder mail
005 REM_MAIL_DOCTYPE document type RAW
The format maintained in this constant is used globally for all kind of email
notification, like reminder email notification, approval email notification, and
SRM email notification.
The notification emails can be sent in HTML format with readable formatting and
invoice data presented in the form of HTML tables. To enable this functionality,
you must set this constant to HTM. In the /OPT/VIM_8CX50 transaction, you
must configure the Email Type to be Internet Email.
Reminder mail
formatting exit
005 REM_MAIL_FORMAT_FM function
For more information, see Section 36.4 “Maintaining a notification email
formatting function module” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM160304-CGD).
The Process Type
number for which
the required fields
are shown on the
005 REQUIRED_PROC_TYPE screen 138;238
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 363
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
Note: This is a table parameter. You can define several lines by specifying
different version numbers ZVER, if one line is not long enough to store all
the values you need.
Option ID to Start
005 RESTART_DP DP Workflow 2014
Maintain the process option that triggers a restart of the VIM document
processing workflow.
Process Type used
in case of RFC
failures when
calling Central
005 RFC_PTYPE_NPO System(NPO) 270
Process Type used
in case of RFC
failures when
calling Central
005 RFC_PTYPE_PO System(PO) 170
Return to Vendor:
Document Type for
Archiving the
005 RTV_AR_OBJECT Vendor mail /OPT/HTM
For more information, see Section 21.7 “Maintaining email archiving” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
User exit / function
to retrieve Email
for Return to
005 RTV_GET_EMAIL Vendor
For more information, see Section 21.5 “Maintaining the email determination user
exit” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM160304-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 21 “Return to Vendor” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
364 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Return to Vendor:
Standard Text
(SO10) for the mail /OPT/
005 RTV_SIGNATURE_NAME signature VIM_SIGNATURE_RTV
For more information, see Section 21.6 “Maintaining the email signature” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
Prefix for standard
texts used for
005 RTV_TEMPLATE_PREFIX Return to Vendor /OPT/VIM_RTV
For more information, see Section 21.4 “Maintaining email templates” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD)
Option Id for
Sending Back to
005 SENDBACK_OPTION Central System 2013
Service Entry
005 SERVICE_ENTRY_BSART Document Type
This constant is obsolete since VIM 7.0 SP3.
Purchase
Document
Category for
005 SERVICE_ENTRY_BSTYP service entry
This constant is obsolete since VIM 7.0 SP3.
Long Invoice
005 SET_REF_MAPPING_SP Reference Number X10,B25
For more information, see Section 11.19 “Implementing long invoice numbers” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
not set (Z constant entry is
not delivered in baseline
005 SET_TAX_CALC_FLAG configuration.)
You may need to have the Calculate Tax flag (SAP field BKPF-XMWST) set for
NPO invoices posted in background through baseline BDC 34. Normally this is
not advised but maybe required by your process, for example, for custom reports.
In this case, set this constant to X.
Note: Setting this flag may affect the value calculated for the field Discount
base amount in the posted document. It also may have other side effects.
This constant is introduced with VIM 7.0 SP7 / VIM 7.5 SP3.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 365
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
366 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
With VIM 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 11.16.3 “Maintaining Z constant 005 /
SKIP_VATDATE_CHECK” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide (VIM160304-CGD).
PO posting BAPI:
'X' to split amount
SPLIT_AMOUNT_OVER_G over GR, ' ' to skip
005 R amount split
VIM provides the following old feature: If there are multiple GRs and no delivery
notes can be considered, the amount is split over GRs. As it seems that most
customers do not like the feature, 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 33.1.4.1 “VIM configuration restrictions” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 367
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
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.
368 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
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.
Package Size for
005 VEND_REC Vendor Download 50000
For more information, see Section 10.1 “Defining frequently used default values”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
Set to ‘X’ to
transfer indexing
screen wht amount
value to posting. If
empty the wht
amount is
calculated from
WHTAX_AMT_TR wht base amount.
For more information, see Section 20 “Extended withholding tax” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
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 20 “Extended withholding tax” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
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 20 “Extended withholding tax” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
Exit FM for wht
005 WHT_EXIT_BAPI data BAPI transfer
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 369
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
370 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Screen for selecting
the DP NPO
DPNPO_APROVER_SELEC Requester/
005 T Approver /ORS/SAPL000007_DP:8000
Screen for selecting
the DP PO
Requester/
005 DPPO_APPROVER_SELECT Approver /ORS/SAPL000007_DP:8000
FM for
manipulating the
item text in the
header - DPPO /OPT/
005 DPPO_BAPI_ITEM_TEXT (BSEG-SGTXT) VIM_BAPI_UE_ITEMTEXT
Standard task for
DP dashboard
005 DP_DASHBOARD_TASKID TS95780003 TS00275257
For more information, see Section 11.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
Task number of the
DP_DASHBOARD_TASK_I DP document
005 D dashboard TS00275278
Delimiter for
005 DUP_CHECK_DELIMIT duplicate check /-
For more information, see Section 11.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
Function Module
for ESRNR
Number
005 ESR_CHECK_FUNCTION Determination
Starting Position
for finding POR
subscriber number
in ESR Reference
005 ESR_NO_BEGIN_POS Number
Ending Position for
finding POR
subscriber number
in ESR Reference
005 ESR_NO_END_POS Number
Function Module /OPT/
for changing mail C_EXT_MAIL_BODY_HAN
005 EXIT_MAIL_BODY body template DLER
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 371
VIM160304-RGD-EN-01
Chapter 36 Z constants for product code 005
372 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
For more information, see Section 11.13 “Configuring global parameters” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 373
VIM160304-RGD-EN-01
Chapter 37
Z constants for product code IAP
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 375
VIM160304-RGD-EN-01
Chapter 37 Z constants for product code IAP
376 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
For more information, see Section 13.4.10 “Configuring the Certify message” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-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 want VIM to compare the tax jurisdiction code
entered manually in the line item with the code retrieved from the account
assignment object. If they are not the same, the standard message F5 532 will be
displayed as a warning.
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 6.5.9 “Maintaining COA - alternative
transaction” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM160304-CGD).
Extended COA line
check for next
approver
determination ('' =
IAP COA_LINE_CHECK_EXT off, 'X' = on)
This constant is obsolete with VIM 7.5 and higher because the old COA is no
longer supported.
If this constant is set to X, all approval lines are checked against the COA.
Otherwise only the first approval line is checked against the COA.
COA Maintenance:
Validation of Input
IAP COA_VAL_INPUT_FLDS fields
For more information, see Section 6.5.3 “COA Details View” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 377
VIM160304-RGD-EN-01
Chapter 37 Z constants for product code IAP
378 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
FM Exit for
filtering BAPI
messages - used in
FM /ORS/
000007_FILTER_B
IAP EXIT_FILTER_APPR_MSG API_MSG
When maintained, the custom FM will be called in FM /ORS/
000007_FILTER_BAPI_MSG to filter out messages as required by customer.
The template for this user exit is FM /ORS/C_EXIT_FILTER_BAPI_MSG.
Search help user /ORS/
exit with Pre-filled SEARCH_HELP_FIELDS_PR
IAP EXIT_SEARCH_HELP_FLT values EFIL
For more information, see Section 12.3 “Configuring search helps with pre-filled
values” in OpenText Vendor Invoice Management for SAP Solutions - Administration
Guide (VIM160304-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, VIM will
retrieve the tax jurisdiction code from the company code data and use it for line
item. Set the constant to blank if you do not want the tax jurisdiction code to be
overwritten with the one from company code.
Get TXJCD from
Vendor Master
IAP GET_TXJCD_LFA1 Table: LFA1 X
If this constant is set to X or does not exist in the customizing table, VIM will
retrieve the tax jurisdiction code from the vendor master data and use it for line
item. Set the constant to blank if you do not want the tax jurisdiction code to be
overwritten with the one from vendor master.
Override Coding
IAP GL_ACC_SCR_EXIT Fileds attributes
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 379
VIM160304-RGD-EN-01
Chapter 37 Z constants for product code IAP
380 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
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
appr.log: D=detail
only, I=detail and
IAP SHOW_DP_COMMENTS inbox <blank>
To enable the display of the DP comments together with the approval comments,
set the constant value to D or 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 VIM 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 13.9.3.1 “Activating and deactivating approval
validation” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM160304-CGD).
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).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 381
VIM160304-RGD-EN-01
Chapter 37 Z constants for product code IAP
382 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
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 6.5.7 “COA upload report” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
Exit to upload data
from file (TMP - /
OPT/
COA_UPLOAD_E
IAP COA_UPLOAD_EXIT_UP XIT)
For more information, see Section 6.5.7 “COA upload report” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
IAP CODER_DEFAULT Coder default XXX X
This constant is not used anymore.
R=by requester ID;
C=by company
code; B=by both R
and C; S=use
IAP CODER_DETERMING requester R
This constant is obsolete because simple approval is no longer supported with
VIM 7.5 and higher.
Doc types for
Credit Memos
CREDIT_MEMO_DOC_TYP (Separated by
IAP E comma) KG
List of SAP FI document types that correspond to credit memos. This is used in
invoice data reading modules to decide on further processing logic.
Set in user
preference table. REF_DOC_NO,RECEIPT_D
Default fields to be ATE,VENDOR_NAME,ORT
shown on the 01,DUE_DATE,INVOICE_A
IAP DEFAULT_INV_LIST invoice list. MT,CURRENCY
Configure the
message to be
display when no
coding is entered
IAP EMPTY_CODING_MSG (Validateacctdata) CHECK_SP:ERROR
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 383
VIM160304-RGD-EN-01
Chapter 37 Z constants for product code IAP
384 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Ext IE RPT -
Loading data in /ORS/
Prog. 000007_5_IE_RPT_LIX_BIND
IAP EXT_IE_RPT_LIX_BIND LIX_PSS_BIND_O 1
Function module that is called at the end of the PO approval workflow to update
VIM Analytics data tables. This constant is for internal use. It was created for VIM
versions when VIM Analytics was an optional component. Normally, do not
change it from its standard value.
Ext IE RPT -
Loading data in /ORS/
Prog. 000007_5_IE_RPT_PIR_BIND
IAP EXT_IE_RPT_PIR_BIND PIR_PSS_BIND_O 1
Function module that is called at the end of the Non-PO approval workflow to
update VIM Analytics data tables. This constant is for internal use. It was created
for VIM versions when VIM Analytics was an optional component. Normally, do
not change it from its standard value.
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
and Enter Cost Assignment Simple.
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.
/ORS/
Image Delete URL 000007_TMP_IMAGE_DEL_
IAP IMAGE_DEL_URL_FM FM URL
/ORS/
Image Display 000007_TMP_IMAGE_DISP_
IAP IMAGE_DIS_JPG_FM JPEG generate FM JPG
For more information, see Section 13.12.1 “Configuring image display” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM160304-CGD).
/ORS/
Image Display 000007_TMP_IMAGE_DISP_
IAP IMAGE_DIS_URL_FM URL generate FM URL
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 385
VIM160304-RGD-EN-01
Chapter 37 Z constants for product code IAP
386 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Popup window to
display company
code selection for /ORS/
cross company 000007_POPUP_COMPANY
IAP POPUP_COMPANY_CODE invoice approve _CODE
For more information, see Section 13.4.8 “Cross company coding” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
Extended PO
Invoice Class
(Called in
Approval =>
GET_PO_INV_CL
IAP PO_INV_CLASS ASS) /ORS/PO_INVOICE_NEW
This constant is obsolete in the context of NPO invoice approvals because simple
approval is no longer supported with VIM 7.5 and higher. It is still used for PO
invoice approvals. For more information, see Section 13.12.3 “Defining the
custom invoice class” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM160304-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 13.4.6 “Defining rejection reasons” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
IAP SAP_PROXY_ID SAP proxy ID WF-BATCH
This constant sets the SAP user ID to which the dialog approval task is sent if the
next approver does not have an SAP user ID.
Actions for Submit
for Approval (used
in TCode binding 8701,8601,8602,8603,8604;202
IAP SUBMIT_ACTION_CODE function exit) 7;2028;
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 387
VIM160304-RGD-EN-01
Chapter 37 Z constants for product code IAP
388 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 38
Z constants for product code IEA
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 389
VIM160304-RGD-EN-01
Chapter 38 Z constants for product code IEA
390 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 39
Z constants for product code IEM
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 391
VIM160304-RGD-EN-01
Chapter 39 Z constants for product code IEM
392 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 40
Z constants for product code KPI
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 393
VIM160304-RGD-EN-01
Chapter 40 Z constants for product code KPI
394 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 41
Z constants for product code LIX
You may want to apply the same “Authorize”-type action to all line level
workflows of a blocked invoice. You also may want the action to apply only to
the other workflows with the same payment block as that of the current work
item. (Previously, up to and including VIM 5.2 SP10, all other workflows would
be cancelled and the header workflow started if you confirmed the corresponding
dialog question.)
If you need the workflows with other payment blocks to remain active, set the
constant value to X. The default configuration delivered with VIM will have the
old logic of cancelling all line level workflows of the invoice (the constant value is
blank).
Display invoice
image on display
of dash board
DASHBOARD_IMAGE_AU screen(X- Yes,
LIX TO space -No)
This Z constant is obsolete.
LIX DASHBOARD_NO_LOGO Display no Logo
If this constant is set to X, the logo is hidden in the parking and blocking
dashboard for PO invoices.
Exit FM to
influence the
LIX DB_OPTION_SEQ dashboard buttons
You can set a custom function to change the sequence of process options in the
dashboard. For the interface of the function, check the Release Notes of VIM 7.0
SP3 or VIM 6.0 SP8.
Use old Delete and
Re-enter sequence
(duplicate error): 1.
LIX DELETE_ENTER_OLD Delete, 2. Re-enter
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 395
VIM160304-RGD-EN-01
Chapter 41 Z constants for product code LIX
396 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Function module
exit for processing
block reasons in
invoice verification /PTGWFI/
LIX BLK_REASON_EXIT_FM subwf LIX_F_UPD_BLK_REASONS
Function module
exit or fixed rule
for moving cash
LIX CHECK_CASH_DISC_RULE discount date
Option for
changing Parking
LIX CHG_PARK_RSN_OPTION reason 2025
FM to create
invoice in case of
Delete/Cancel and /PTGWFI/
LIX CREATE_PO_BDC_FM Re-enter option VIM_CRE_PO_INV
This Z constant is obsolete.
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 12.3.5 “Configuring header level dashboard
binding exits” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM160304-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 12.3.5 “Configuring header level dashboard
binding exits” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide (VIM160304-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 12.3.6 “Configuring the send back functionality
exit” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide (VIM160304-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 397
VIM160304-RGD-EN-01
Chapter 41 Z constants for product code LIX
398 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Subscreen program
for Logistic Invoice /PTGWFI/
LIX LIXPROG Resolution M_LIX_SUBSCREEN02
For more information, see Section 12.3.1.1 “Line level” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
Subscreen for
Logistic Invoice
LIX LIXSCREEN Resolution 9902
For more information, see Section 12.3.1.1 “Line level” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-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 12.3.1.1 “Line level” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM160304-CGD).
Returns subscreen
screen number for
PSS ( FM:) for FM FM:/ORS/
or can be direct LIX_T_GET_EXIT_SUBSCR
LIX LIX_B_PSS_EXIT_S_NO value N
Returns subscreen
program name and
screen number in FM:/ORS/
PSS ( FM: indicates LIX_T_GET_EXIT_SUBSCR
LIX LIX_B_PSS_EXIT_S_PRG FM) N
Returns subscreen
screen number for
PSS ( FM:) for FM FM:/ORS/
or can be direct LIX_T_GET_EXIT_SUBSCR
LIX LIX_P_PSS_EXIT_S_NO value N
Returns subscreen
program name and
screen number in FM:/ORS/
PSS ( FM: indicates LIX_T_GET_EXIT_SUBSCR
LIX LIX_P_PSS_EXIT_S_PRG FM) N
Line Item Execute
Transaction Task
LIX LN_EXECTCODE_TASKID ID TS98600016
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 399
VIM160304-RGD-EN-01
Chapter 41 Z constants for product code LIX
400 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Subscreen for
Parked Invoice
LIX PRKSCREEN Resolution 9901
This Z constant is obsolete.
Function Module
Exit to be executed
before the start of
LIX PRK_AUTOPOST_EXIT Auto-Posting (LIV)
This Z constant is obsolete.
Function Module
Exit to be executed
at the end of
Parked Document
LIX PRK_POSTING_EXIT_FM Posting Step
This Z constant is obsolete.
Post Process Sub
Workflow for
Parked Document
LIX PRK_POST_PROCESS_WF WF
This Z constant is obsolete.
Pre Process Sub
Workflow for
Parked Document
LIX PRK_PRE_PROCESS_WF Workflow
This Z constant is obsolete.
FM exit in the
Binding FM for the
PSS step - at the
time of Inward /PTGWFI/
LIX PRK_PSS_BIND_FM1 Binding PRK_TMP_BIND_EXT_FM
This Z constant is obsolete.
FM exit in the
Binding FM for the
PSS step - at the
time of Outward /ORS/
LIX PRK_PSS_BIND_FM2 Binding 000007_LIX_PSS_BIND_O
This Z constant is obsolete.
Parallel Exit
workflow for PSS
Step in LIV Parked
LIX PRK_PSS_EXIT_WF Doc workflow
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 401
VIM160304-RGD-EN-01
Chapter 41 Z constants for product code LIX
402 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
This Z constant is obsolete.
Option key for the
LIX RESUBMIT_OPTION re-submit Option R9998
Parking Reasons
with Single Level
LIX SINGL_APPRVL_PRKRSN Approval 03;
SRM Block process
LIX SRM_BLK_PROCTYPE type 162
LIX SRM_PO_STATUS SRM PO Status K;
For more information, see “Invalid Requisitioner (PO)” on page 241,
“Confirmation Required from SRM (PO)” on page 243, and Section 31.1
“Determining purchase order types” in OpenText Vendor Invoice Management for
SAP Solutions - Configuration Guide (VIM160304-CGD).
SRM- Mail
configuration ID
LIX SRM_PRC_BLK_MAIL_CID for Price Block 3
For more information, see Section 31.2.3 “Price discrepancy scenario” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
Proxy Role for
LIX SRM_PRC_BLK_PXY_ROLE Price Block AP_PROCESSOR
For more information, see Section 31.2.3 “Price discrepancy scenario” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
Delay in minutes
for SRM Price
LIX SRM_P_BLK_DELAY Block 1
For more information, see Section 31.2.3 “Price discrepancy scenario” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
SRM- Recipient /OPT/
Email ID FM for S_GET_SRM_USER_EMAIL_
LIX SRM_P_BLK_RCV_EML_FM price block ID
For more information, see Section 31.2.3 “Price discrepancy scenario” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM160304-
CGD).
SRM Quantity
Block process type
(obsolate, replaced
by
SRM_BLK_PROCT
LIX SRM_QTY_BLK_PROCTYPE YPE) 162
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 403
VIM160304-RGD-EN-01
Chapter 41 Z constants for product code LIX
404 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Chapter 42
Z constants for product code PIR
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 405
VIM160304-RGD-EN-01
Chapter 42 Z constants for product code PIR
406 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
Transactions to
create Non-PO FV60;FB60;/PTGWFI/
based Parked LIV_CHG_PKRS;
PIR NONPO_INV_TCODE Invoices /PTGWFI/PIR_CHG_PKRS;
This Z constant is obsolete.
NPO Invoice
PIR NPO_INV_ARCHIVE_OBJ Archive Object
Function module to
determine the
options to be
PIR OPTION_DET_FM displayed in Proc /PTGWFI/0000000002_F001
Parked Invoice
PIR PARKREASON Blocking Reason V
Subscreen program
for Parked Invoice /PTGWFI/
PIR PIRPROG Resolution PIR_SUBSCREEN01
This Z constant is obsolete.
Subscreen for
Parked Invoice
PIR PIRSCREEN Resolution 9901
This Z constant is obsolete.
Returns subscreen
program name and
also screen number FM:/ORS/
for PSS ( FM:) for BIR_T_GET_EXIT_SUBSCR
PIR PIR_PSS_EXIT_SUBSCRN FM N
Returns subscreen
screen number for
PSS ( FM:) for FM FM:/ORS/
or can be direct BIR_T_GET_EXIT_SUBSCR
PIR PIR_PSS_EXIT_SUBS_NO value N
PIR Process
Selection Screen
Task ID
PIR PIR_PSS_TASK_ID TS98691004 TS00275260
PIR Execute
Transaction Code
PIR PIR_TCODE_TASK_ID Task ID TS78600019
Function Module
Exit to be executed
at the end of
Parked Document
PIR POSTING_STEP_EXIT_FM Posting Step
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 407
VIM160304-RGD-EN-01
Chapter 42 Z constants for product code PIR
408 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
This Z constant is obsolete.
Option key for the
PIR RESUBMIT_OPTION re-submit Option R9998
FM for sending /PTGWFI/
PIR SEND_MAIL Document PIR_F_TMP_SEND_MAIL
Parking Reasons
with Single Level
PIR SINGL_APPRVL_PRKRSN Approval 03;
Function module to
be executed before
the TCode
Execution step is
PIR TCODE_BIND_EXIT_FM1 created
Function module to
be executed at the /ORS/
end of the Tcode 000007_PIR_TCODE_BIND_
PIR TCODE_BIND_EXIT_FM2 Execution step O
FM to be called in
the User Exit to /PTGWFI/
collect data during PIR_F_GET_PARK_DATA_
PIR USR_EXIT_GET_DATA_FM Document Parking N
This Z constant is obsolete.
FM to be called in
the User Exit to
collect data after /PTGWFI/
PIR USR_EXIT_GET_DATA_S Document Parking PIR_F_GET_PARK_DATA_S
Main Workflow
Template ID
WS98600055/
PIR WORKFLOWTEMPLATE WS99680011 WS00275254
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 409
VIM160304-RGD-EN-01
Chapter 43
Z constants for product code VAN
Display result of
SYNC run in SYNC
VAN SYNCH_DIAG_INFO INFO button X
This constant is obsolete with VIM 7.5 SP1 and higher because the old VIM
Analytics is no longer supported.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 411
VIM160304-RGD-EN-01
Chapter 43 Z constants for product code VAN
412 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
FM for currency
VAN CURRENCY_CONVERSION conversion
This function module is used to convert the total amount/the line amount of DP
documents from the document currency to the local currency throughout the VIM
Analytics report.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 413
VIM160304-RGD-EN-01
Chapter 43 Z constants for product code VAN
414 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Product Constant Description Default Value
Code
This constant is obsolete with VIM 7.5 SP1 and higher because the old VIM
Analytics is no longer supported.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 415
VIM160304-RGD-EN-01
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.
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
Archive system
ArchiveLink
Service integrated in the SAP NetWeaver Application Server ABAP for linking
archived documents and the application documents entered in the SAP 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.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 417
VIM160304-RGD-EN-01
Glossary
Automation Report
Tool that provides data about automated and manual processing steps of VIM
documents
BAdI
See Business Add-Ins (BAdI).
BAPI®
Baseline
BasisCube
See InfoCube.
BDC ID
Business Data Communication ID. The BDC ID is used by the system to process
an SAP transaction to create an SAP Document in user context.
Block
Situation where an invoice has a price or quantity variance that prevents invoice
from posting
BTE
See Business Transaction Event (BTE).
Business Center
OpenText Business Center for SAP Solutions. OpenText product that helps
receiving incoming documents, capturing processes, and filing them within a SAP
system. VIM is tightly integrated with Business Center.
418 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Glossary
Business rules
Rules that describe the operations, definitions and constraints that apply to an
organization
Event used for extending a Non PO invoice functionality to call a custom program
Central Reporting
Reporting infrastructure that provides several reports that enable you to measure
certain properties of VIM documents and their work items, in order to optimize
working with VIM. Central Reporting comprises the following individual reports:
Aging Report, Central Audit Report, Exception Analysis Report, Key Process Analytics
Report, Productivity Report, and Summary Report.
Characteristic
COA
See Approval chart of authority (COA).
Coding
Dashboard
User interface that organizes and presents information in a way that is easy to
read. Users can also perform actions from the dashboard.
Object in SAP NetWeaver BW to transfer data from source objects to target objects
DataSource
Set of fields in SAP NetWeaver BW that provide the data for a business unit for
data transfer to the SAP NetWeaver BW system; technically, it contains an extract
structure and an extraction function module.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 419
VIM160304-RGD-EN-01
Glossary
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.
VIM component that captures invoice metadata including line items for PO and
performs preconfigured business rules
Document type
DP
See Document Processing (DP).
DSO
See DataStore Object (DSO).
DTP
See Data Transfer Process (DTP).
EDI
See Electronic Data Interchange (EDI).
Method for transferring data between different application systems in the form of
messages. SAP applications support EDI with messages sent in an SAP
Intermediate Document (IDoc) format. VIM supports the creation of vendor
invoices through the EDI/IDoc interface.
Error handling method. Event Type Linkage determines what the application
should do in case an error could not be handled.
Exception
FI
See Financial Accounting (FI).
420 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Glossary
IAP
See Invoice Approval (IAP).
IDoc
See Intermediate Document (IDoc).
IE
See Invoice Exception (IE).
Indexing
InfoArea
InfoCube
InfoObject Catalog
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
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 421
VIM160304-RGD-EN-01
Glossary
VIM 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 in VIM. An invoice characteristic is determined during runtime and
depends on the corresponding index data of the document.
Invoice coder
Person who enters the accounting info on invoices to allocate the cost
VIM component that handles the exceptions that arise after an SAP invoice is
created
Invoice requester
Key Figure
Part of the Central Reporting infrastructure. The Key Process Analytics Report
reports about a variety of key figures regarding the VIM process: It shows the
accumulated amounts of all documents in the DP workflow, in parked state and
in posted state.
KPI Dashboard
Tool for managers showing VIM related process data at a glance in graphical
charts.
LIV
See Logistic invoice (LIV).
422 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Glossary
MM
See Materials Management (MM).
MultiProvider
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
Number range
Array of numbers that can be used for an object in the SAP S/4HANA system
OCR
See Optical character recognition (OCR).
Park
Situation where an invoice is not posted and is waiting for further processing
Temporary document that the AP processor can change and post. SAP assigned
document number becomes real number when posted.
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 423
VIM160304-RGD-EN-01
Glossary
PIR
See Non purchase order (Non PO) invoice (PIR).
PO
See Purchase order (PO).
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
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
PSA
See Persistent Staging Area (PSA).
424 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01
Glossary
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
SAP application that provides software for ticket systems, for example in the
Accounts Payable department.
SAP software that contains a rich set of tools to improve and automate Shared
Service Center operations.
Scan operator
Person who scans the invoices into images (may not have a SAP ID)
Summary Report
Transformation (TRF)
OpenText Vendor Invoice Management for SAP Solutions – Reference Guide 425
VIM160304-RGD-EN-01
Glossary
TRF
See Transformation (TRF).
VAN
See VIM Analytics (VAN).
VIM component that gives users a clear data report on their invoices in progress.
VIM Analytics allows to track the documents routed through SAP workflows via
VIM.
VIM Workplace
Tool for VIM super users, which allows users to display lists of their work items
that meet a selection they have entered before. Users also can display work items
of other users and of their team as a whole.
Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP S/4HANA system.
426 OpenText Vendor Invoice Management for SAP Solutions – Reference Guide
VIM160304-RGD-EN-01