Professional Documents
Culture Documents
Configuration Guide
VIM070500-08-CGD-EN-01
OpenText™ Vendor Invoice Management for SAP® Solutions
Configuration Guide
VIM070500-08-CGD-EN-01
Rev.: 12. Dec. 2018
This documentation has been created for software version 7.5 SP8.
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 11
5 Roles ......................................................................................... 35
5.1 Defining roles .................................................................................. 36
5.2 Defining role templates .................................................................... 38
5.3 Assigning templates to roles ............................................................ 42
5.4 Maintaining role determination settings ............................................. 44
5.5 Maintaining Chart of Authority .......................................................... 47
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide iii
VIM070500-08-CGD-EN-01
Table of Contents
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide vii
VIM070500-08-CGD-EN-01
Table of Contents
30.4 Creating variants of the Aggregation Report for each group ............. 810
30.5 Activating Central Reporting Baseline and maintaining reporting
tables ........................................................................................... 811
30.6 Scheduling the Collection Report ................................................... 815
30.7 Scheduling the User Master Report ................................................ 819
30.8 Scheduling the Text Master Report ................................................ 820
30.9 Scheduling the Aggregation Report ................................................ 821
30.10 Troubleshooting: Cleaning up Central Reporting tables .................... 821
30.11 Maintaining thresholds for the Key Process Analytics Report ........... 823
30.12 Configuring the Summary Report ................................................... 833
viii OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Table of Contents
• VIM solves a business problem - paying correct amount to vendors on time and
with the lowest cost.
• VIM delivers not technology but best-practice business processes.
• VIM provides values to customers in process efficiency, visibility and
compliance.
• VIM is tightly integrated with OpenText™ Business Center for SAP® Solutions.
• VIM is an add-on to your SAP ERP system, the majority of the functions and
processes run inside your SAP ERP system.
• VIM deals only with invoices that will be posted to SAP ERP.
• VIM uses SAP technology: ABAP®, Workflow, SAP Fiori®, and SAP NetWeaver®
Portal.
• VIM integrates with standard SAP functions: Invoice Verification, Financial
Processing, etc.
• Automate the capture of paper invoices by using OCR to extract invoice data.
BC (Business Center)
Business Center provides the following components that are integrated in VIM.
Document Processing
Approval Portal
Mobile Approval
• VIM Reporting: Use various reports to analyze the status of invoices in your
system.
• VIM Analytics with CDS view: Overlook the invoices in progress in a unified
dashboard.
• VIM Invoice Analysis Fiori app: Overlook invoices in progress in a
lightweight web application, based on SAP Fiori®. The Invoice Analysis app
is a simple version of the VIM Analytics SAP GUI report. The Invoice
Analysis app is included into VIM to show how, for example, cost center
owners or similar roles can access VIM Analytics from Fiori. Currently it is
only included as an example or template but not fully supported for use in
production.
• Provide a web interface that enables suppliers to keep track of the status of
their invoices.
• Connect VIM with Ariba Network Integration for SAP Business Suite.
Suppliers create invoices in the Ariba Network. The invoices are sent to the
SAP ERP system of the buyer. The buyer processes all incoming invoices in
VIM.
SAP NetWeaver BW
Processing From a technical and functional perspective, the overall processing comprises the
blocks following processing blocks:
This document describes the configuration of each of the processing blocks (see
“Processing blocks” on page 15). It also describes the various implementation
aspects of configuring VIM to suit the specific business requirements for any
organization. VIM is designed to be highly configurable to accommodate varied
business scenarios.
“Mandatory configuration”
These configuration steps describe the basic mandatory customizing. This
customizing must be done with every VIM installation, independent of changes
to the VIM baseline; for example the configuration of roles for the VIM process.
For further information about the VIM baseline, see “Delivery model”
on page 19.
“Advanced configuration”
These configuration steps describe the advanced customizing. This customizing
changes the VIM baseline and partly includes extensions and customer exits. An
example is the DP process configuration.
“Optional configuration”
These configuration steps describe the basic, but optional customizing. This
customizing must be done for optional VIM features, such as the integration of
SAP Shared Service Framework.
“Special topics”
These configuration steps describe special topics of the VIM customizing, for
example VIM Notifications.
For information about all OpenText products resold by SAP (including VIM
and ICC), check SAP Marketplace Note 1791874: SAP Products by OpenText -
Software and Support Lifecycle. This note provides detailed information about
software life cycle, access to Support Packages, access to latest documentation,
language packages, and other patches, as well as Support ticket handling.
Process steps The Vendor Invoice Management (VIM) business process typically includes the
following main steps:
Note: Only end user screens are translated in additional languages other than
English. Customizing screens are provided in English language only.
Validate metadata
The metadata or index data are validated against the SAP database. If validation
fails, an exception is triggered.
Check duplicates
The validated metadata is used to check whether the new invoice has been
entered already. If the new invoice is suspected to be a duplicate of any existing
invoice, an exception is triggered.
Apply business rules
Invoice pre-processing: Business rules are applied to detect additional
exceptions before posting.
Post for payment
The invoice is posted and released for payment.
Process Description
The description in the headline represents the process scenario.
Roles
Each lane represents a business role, a unique grouping of people required to
collaborate to complete the process.
Dashboard
The dashboard is the user interface for the actors in the process. The dashboard
type identifies the VIM component that is used to realize a specific functionality.
The following dashboard types are available:
DP dashboard
The DP dashboard represents a process as implemented in the Document
Processing component of VIM.
See section 4 “Working with the DP Dashboard” in OpenText Vendor Invoice
Management for SAP Solutions - User Guide (VIM070500-08-UGD).
VIM dashboard
The VIM dashboard represents a process as implemented in the Invoice
Exception component of VIM for parked invoices.
See section 6 “Working with the Invoice Exception dashboards” in OpenText
Vendor Invoice Management for SAP Solutions - User Guide (VIM070500-08-
UGD).
Options
Various options are available to the actors during the processing of invoices.
These are represented as individual items next to the dashboard block.
This section describes the activities that need to be done prior to implementing VIM.
For detailed installation steps, refer to OpenText Vendor Invoice Management for SAP
Solutions - Installation Guide (VIM070500-08-IGD).
• Install and configure an archiving system that supports SAP HTTP Content
Server interface.
• Complete business process blueprint sessions: Final process design swimlane
diagrams are available.
• Create User IDs with appropriate developer and configuration authorizations.
Authorizations need to include developer as well as workflow administrator
authorizations.
• Create ArchiveLink document types or at least finalize the list of the document
types etc.
• Check for any existing BAdI implementations for definition INVOICE_UPDATE.
Check to see if there is any conflicting code that could prevent parking reasons in
PO/Non PO invoices from showing up.
• Complete appropriate FI and MM-Purchasing customizations, so FI and logistics
invoices can be created in the system.
This part describes mandatory configuration steps for VIM. These configuration
steps describe the basic mandatory customizing. This customizing must be done
with every VIM installation, independent of changes to the VIM baseline; for
example the configuration of roles for the VIM process.
This chapter describes the steps needed to configure SAP ArchiveLink document
types. ArchiveLink is responsible for the collaboration between the SAP ERP system
and the Archive Center, for example to save documents from a VIM workflow to the
Archive Center, or to retrieve documents from Archive Center for a VIM process.
You need to do this configuration when the content repository (Archive Center) is
installed and the basic ArchiveLink settings are completed. Depending on the
customer requirements, the number and attributes of the ArchiveLink settings might
be different.
Note: For further details about ArchiveLink refer to the SAP documentation.
Check if the following archive document types are defined because they are
frequently used as default values in the VIM configuration:
• /OPT/HTM with description Archived HTML Email and document class HTM
• /OPT/ICC with description ICC Scanned Image (or other) and document class
PDF or TIF
• /OPT/NFE with description XML document NF-e brazil invoice and document
class XML
• /OPT/OTHER with description Additional documents and document class
<empty>
• /OPT/PDF with description Workflow History and document class PDF
To know where to store the incoming invoice (in which Content Repository, in
which link table), you must maintain the links, as described in this section.
To link the Archive Document Type and the VIM Business Object:
2. In the Links for Content Repositories Overview screen, click New Entries.
Object Type
Enter /OPT/V1001
Document type
Enter /OPT/ICC
Link Status
Enter X
Storage system
Enter the Content Repository ID.
Link
Enter TOA01
Notes
4. Click .
2. Create new entries, as shown in the following screenshots. The first one is BKPF
for Non-PO invoices and the second one is BUS2081 for PO invoices.
Additionally, you have to define a profile for the PDF history log and assign it to a
VIM process step. For more information, see “PDF history log” on page 910.
To know where to store the PDF history log (in which Content Repository ID, in
which link table), you must maintain the links, as described in this section.
To link the archive document type and the VIM business object:
2. In the Links for Content Repositories Overview screen, click the New Entries
button in the application tool bar.
Object Type
Enter /OPT/V1001.
Document type
Enter /OPT/PDF.
Link Status
Enter X.
Storage system
Enter the Content Repository ID.
Link
Enter TOA01.
2. Create new entries as shown in the following screenshots. The first one is BKPF
for Non-PO invoices and the second one is BUS2081 for PO invoices.
Roles refer to the grouping of various business users according to their business
activity. In the swimlane diagrams, roles represent the title for each of the lanes.
Vendor Invoice Management (VIM) has a comprehensive framework for realizing
various requirements in the area of role definition. You can define roles as granular
as needed.
Role
In VIM terminology, role stands for a Process Agent. Role is not the same as the
SAP workflow technical role.
Note: The workflows are delivered by OpenText and hence cannot be
changed at client side.
Template
Any role bases on a template.
Template fields
Templates can have fields that determine the granular logic used in determining
the final set of users. For example, the grouping of roles can base on the
company code or the purchasing organization.
This chapter describes the steps required to create and configure roles needed for
implementing VIM business scenarios.
005
Document Processing (DP) based product codes
LIX
LIV based product codes (both for PO parking and PO blocking workflows)
PIR
Product codes for Non-PO parking workflows
Every role assignment bases on the product code/role combination. For example, to
create a role called BUYER in a PO parking process, create a role BUYER with product
code LIX.
OpenText delivers standard roles used in most process scenarios. You can define
your own roles if needed.
To maintain roles:
Product Code
Enter the product code such as 005, LIX, PIR. Refer to OpenText product
codes for applicable product code.
Responsible Party
Enter the responsible party (role).
Description
Enter the description of the role.
Role Function Module
Enter a function module for the role. For the interface, see function module
template /PTGWFI/COA_W_ADKY_GET.
Key Determination
Select the check box, if the role is defined by object information – the context
in which the role is used.
Deactivate the check box, if the role is fixed and defined by organization
data, for example: if you want to determine the role by company code, scan
location, or plant.
Object Type
Maintain the object type, based on the workflow.
• Combination of columns
Example: Company code, scan location and plant define the AP Processor role.
Example: Buyer is the PO creator that the function module extracts from the PO.
Template Id
Enter meaningful character value that identifies the template.
Description
Enter the template description.
Type
Select the template type. The following template types are available:
Org Unit
If you select Org Unit, the agents for the role are determined from a
fixed org unit (User, Position, Work Center, and so on)
Allow Org
For Key Determination Based templates, only: If the Allow Org flag is set,
you can set an Org Unit instead of a fixed SAP User ID while maintaining
agents for role template in the role determination transaction.
Object Type
For Org Unit based templates only: Select the default value for Agent Type
(User, Position, and Work Center etc.).
Agent Id
For Org Unit based templates only: Select the agent ID.
Function Module
For Function Module Based based templates only: Select the function
module that is used to determine agents for this template. The interface
value for the function module can be found in the OpenText delivered
function /OPT/BL_ROLE_SELF_DIRECTED.
1. In the Template Definition Overview screen, select a template from the list and
double-click Template Fields in the navigation pane.
Field Id
Enter a freely defined field Id which describes the usage of the field.
Ref. Table/Ref. Field
Select reference table and reference field. When maintaining values for the
field, the system can check the values and provide F4 help for the field
using reference table and reference field.
Search Help
Select the search help. When maintaining values for the field in the role
determination transaction, the system uses this value to provide F4 help for
the field.
Allow Range
Select this check box to allow ranges. The values can have a range from
“Low Value” to “High Value”. The system checks the runtime data for the
product code in which the template is used to validate if it can resolve the
field.
Wild Card
Select this check box to allow the wild card character *. Users can define a
wild card for values in the role determination transaction for the product
code in which the template is used.
Example: A field combination of Company Code and Plant could be used to resolve BUYER
in the PO parking process, BUYER in the PO blocking process and PO_BUYER in the Document
Processing process.
2. In the Template Fields Details Overview screen, maintain the Template Field
Details, using the following parameters:
Product Code
Select the OpenText product code in which the template is used.
Object Type
Select the object type. Object types are defined for each OpenText product
code. You can however create a subtype for the OpenText Object Type to
define your own attributes. At runtime, the system instantiates the object
with the object key. The type should be compatible to the OpenText object
type for the given product code.
Attribute
Select the attribute the system uses for the given OpenText product code for
getting the runtime value for the given field Id.
Product Code
OpenText product code
Responsible Party
OpenText role
Key Determination Template Id
Template Id defined
Active check box
Select the Active check box to assign the template defined to the product
role combination. The template will be used in determining agents for the
role in OpenText processes. You can only have one active template for a
given product role.
Func. Module
Enter the custom function module. The interface for the function
module is defined in the /OPT/BL_ROLE_SELF_DIRECTED function
module.
Agent Type
Select the agent type (US for user ID, S for position, and so on).
Agent Id
Depending on the agent type, select the agent Id (SAP user ID, position
etc.).
Level-based This approval method has been introduced with VIM 7.0. Level-based approval is
approval considered only for Non PO document types. For PO document types, a one-step
approval is provided by default.
For more information, see “Configuring approval flow settings” on page 365.
Note: The simple approval flow, which was used in versions of VIM prior to
7.0, was based on Manager’s information provided in the “old” Chart of
Authority (COA). For information about the “old” COA, see section 9.6
“Maintaining Chart of Authority” in OpenText Vendor Invoice Management -
Configuration Guide (VIM060000-CGD). This is the documentation for VIM 6.0.
COA configura- In level-based approval, COA details are checked when the user opens the work
tion item. That means that changes in the COA details are automatically reflected in the
Invoice Approval screen. When a task is performed, the next approval steps are
automatically determined according to the actual setting. Therefore, changes to user-
specific COA details are not critical. Changing or renaming a User ID might be
critical. For more information, see “To activate or deactivate a user:“ on page 51.
This section provides details on how to configure the COA for level-based Invoice
Approval. For a comprehensive description of the level-based Invoice Approval
component, see “Invoice Approval“ on page 347.
Purpose COA is required in the Invoice Approval process to allow users to approve Non PO
invoices. The data combination maintained in the COA helps to determine the
correct approver for a certain invoice in the approval process.
Note: The PO Invoice Approval process does not consider the COA when
determining the next approver. For PO invoices, Baseline implementation
identifies the requester of the PO as the first and only approver.
Prerequisites
• The Cost Objects allowed in the Invoice Approval process are maintained. You
can maintain the Cost Objects in the SM30 transaction for the /OPT/BL_T401V
table/view.
Note: The fields Inv. Table and Inv. Field in /OPT/BL_T401V were used in
the old simple approval, but are ignored in level-based approval.
• The fields required for approval user data in the User Details tab are maintained.
You can maintain the fields in the SM30 transaction for the /OPT/BL_T402V table/
view.
Independently from the /OPT/BL_T402V table/view, the following fields are
always displayed in the User Details tab:
– OPT_USERID
– DELETED
– EMAIL
– MANAGER_ID
– BULKAPPROVAL
– BTEXT
– USER_TYPE
– UTEXT
For all other fields, you must maintain them in the /OPT/BL_T402V table/view to
have them displayed in the User Details tab.
• The levels required for approval limit and approval authorities are maintained.
You can maintain the levels in the SM30 transaction for the /OPT/AT_LEVEL table/
view.
Note: Level 0 is always reserved for Coder Level. Level 1 always represents
Requester Level. All other subsequent levels from 2 to x can be used for
Approval Levels.
Expense type It is possible to build the line-based approval logic on the values of expense type and
and additional other fields that are available in the invoice line items. The expense type is treated as
fields
an item level field. Other fields must already be present in the line item structures of
the invoice. See the /OPT/A_INVOICE_ACCT_ST structure for reference.
Important
You can configure the requester determination using the same COA logic as
used to determine coders (except the first coder) and approvers. However, this
is only supported if you work with real coders, that means, if you have two
steps, first coding and then requester. If you have configured that “coder =
requester”, VIM uses the requester field from the invoice.
1. Add new fields (except the expense type) to the /OPT/A_COA_FIELDS_ST and /
OPT/BL_4RCOA_DATA structures. To do this, use append structures.
2. Add new fields to the COA field list in the /OPT/BL_T401V view as line item
fields. You must add the expense type field as a line item field. Make sure the
Header field check box is cleared.
3. Provide a mapping between the invoice fields and the COA fields. You do this
in the VIM customizing for the respective AFS IDs, under Maintain Invoice
Detail Fields and Maintain Coding Fields Mapping. For more information, see
“Configuring fields for the invoice detail page” on page 388.
Access You can access the COA maintenance using transaction code /OPT/AR_COA.
The default access to COA is in display mode. Use the Display/Change button to
switch to maintenance mode.
OpenText User Id
User Id (generated automatically)
Note: If the OpenText Approval Portal is connected to multiple SAP ERP
backend systems, the OpenText User Id for a particular user must be the
same in all SAP ERP systems.
Deleted
Check box indicating if the user is deleted from COA.
Manager ID
Direct superior of the user. In the level based approval flow, the manager is only
used for the notification escalation processing but not for any approval
processing logic. For more information, see “Configuring notification and email
options” on page 937.
• A-Approval
• R-Reject
• B-Approval and Reject
• N-None
Last Name
User’s last name
First Name
User’s first name
Middle Name
User’s middle name (optional)
Department
User's department (optional)
Windows Domain
If implementing optional Approval Portal with WAS authentication scenario:
Windows domain. Required if Approval Portal is used with WAS authentication
scenario and users are authenticated using Windows domain.
Windows_ID
If implementing optional Approval Portal with WAS authentication scenario:
Windows ID or the login ID. Required if Approval Portal is used with WAS
authentication scenario and users are authenticated using Windows domain.
Personnel number
Personnel number of the user
SAP User ID
SAP User ID of the user
SAP Portal User ID
If implementing optional Approval Portal with Portal authentication scenario,
this will be the login ID for the user in the portal.
Email Address
User's email address. Identifying field for all COA users (approvers). This field
cannot be duplicated with existing users.
Name and address
Name, other form of user's address (optional)
Telephone number
User's telephone number
In the User Details View screen, you can perform the following actions:
Notes
• You cannot delete users in COA but only deactivate them. Before you
deactivate a user, check if the user has open invoices to approve. If yes,
reassign open invoices to another user using the Reassign utility. For
more information, see “Override, delegation, substitution, and reassign”
on page 408.
• Renaming an OpenText User ID is not possible directly. You must create
a new user and deactivate the old user.
• If you are deactivating a user, the COA will issue a warning if there are
any active approval tasks. However, this is only a warning, you can still
proceed.
The settings here are the same as in the Personalization screen in the Approval
Portal. See section 8.15 “Personalizing your views of the Approval Portal” in
OpenText Vendor Invoice Management for SAP Solutions - User Guide (VIM070500-08-
UGD). Some parameters apply to the Mobile Integration, as well.
Show Details
Select this check box to automatically open the Invoice Detail section in the
Approve Invoice screen.
Clear this check box to display only the Details link in the Approve Invoice
screen.
Show History
Select this check box to automatically open the History section in the
Approve Invoice screen.
Clear this check box to display only the History link in the Approve Invoice
screen.
Default Coder
Starting with VIM 7.5, this parameter is no longer used.
E Notify Active
Select this check box to receive an email notification regarding any new
invoice in your inbox.
Language
Enter the default language.
Note: Using this setting can override the language used by some
screen elements in browser-based Invoice Approval applications. This
can result in a mixed display, meaning different languages in the same
screen. Do not use this setting if you experience conflicts of this setting
with default settings on the client side, like browser default settings or
the Fiori Launchpad sign-in language.
Date format
Also relevant for Mobile Integration: Enter the date format. Click for a
list of possible formats.
Dec.pt.format
Also relevant for Mobile Integration: Enter the format of the decimal
notation. Click for a list of possible formats.
Currency
Enter the default currency.
Show Attachment
This check box is not relevant. Users can always use the attachment
function, regardless of the Show Attachment check box.
Display Type
Determine where the invoice image should be displayed when opening the
detail page. Click for a selection.
Logical system
Enter the SAP ERP system that you want to use as the user preference for
your Invoice List page.
Time Zone
Also relevant for Mobile Integration (as the time zone in Approval log):
Enter the default time zone for the user. Click for a selection.
Note: In header based approval, the flow will remain the same as the line
based approval in coder and requester level. The lines have to be coded and
approved, and each line is checked against the COA details of the user in the
corresponding level.
Enter the following parameters for the combination of Company Code and
Approval Level:
Company Code
Company Code for which the approval level should apply
Approval Level
Basic value of the level based COA. Select one of the following values from the
list:
0
Coder level (no limit possible)
1
Requester level
2, 3, ...
Approval levels
Amount Limit
Enter an amount. This amount will be considered as the approval limit. The user
can approve the invoice if the amount of a certain pack in the invoice is less than
or equals to the amount mentioned in this column. If the amount exceeds this
limit, the invoice needs next level approval.
Notes
Invoice information
Invoice 1000€
Amount
Line 1 Cost Center: 1000; Amount 100€
Line 2 Cost Center: 1001; Amount 300€
User A Allowed for Cost Center 1000 and Cost Center 1001
User B Allowed for Cost Center 1001
User C Allowed for Cost Center 1002
As User C has the highest pack amount, he will receive the workitem.
(In this case, you must distinguish between the Highest pack only and the
All pack scenarios.)
For coder and requester (approval level 0 and 1), the cost objects are checked if the
user can code or approve the corresponding cost objects. All lines must be approved
by a legitimated coder or requester. The invoice is forwarded to the next coder or
requester until all lines are coded or approved. Within level based approval, this
process is performed in the same way for header and line based approval scenarios.
For approvers, the COA is used to determine the next approver and also to create
the pack when the approver opens the work item. If more than one approver exists
in the COA for the corresponding cost objects of the invoice line, the first user in the
COA will be determined. For this, the entries will be sorted alphanumerically with
the approver ID and counter.
Note: To change the logic of handling the cases when more than one approver
can be determined, you can redefine the user map class and implement your
own logic of sorting the entries and prioritizing the approvers.
Cost object values can be entered using ranges and wildcards (asterisk). Only full
wildcards (*) are allowed, no partial wildcards (n*).
Note: You can choose whether the asterisk will match an empty invoice field
or not. You control this by the constant IAP / AST_ALLOWS_SPACE. When
changing the constant value, be aware that having it enabled may affect the
process of finding the next coding agent for the lines where all COA-relevant
fields are empty.
Without the constant enabled, for lines with empty cost elements, VIM will
propose any existing coding agent to allow the coding process to continue.
With the constant enabled, users that have COA records with asterisks will be
excluded from the search. This means, the line is not empty for them anymore
because the asterisk will fill the space.
If an invoice line has one cost object assigned, this cost object is checked against the
COA.
If an invoice line has more than one cost object assigned, all cost objects are checked
against the COA. There is no precedence of one cost object over the other. All cost
objects that are listed in OPT/BL_T401V are checked.
Cost objects which are not available in the COA (according to configuration of OPT/
BL_T401V) are not checked.
If an invoice line does not have any cost object that can be assigned to a COA cost
object, the line cannot be approved.
The COA Details View lists approvers, depending on the Company Code and the
Approval Level.
The user types Coder / Requester and Approver are shown on separate sub-tabs.
Company Code
The company code that the user is authorized to approve. For line based
approval, the company code of the invoice line is used to check against the
COA. For header based approval, the header company code is relevant.
Important
In VIM baseline, level based approval does not support cross-company-
code invoices.
Approval Level
Approval level. See “Approval Limit/Level View” on page 53.
UserObjID
OpenText User Id, maintained in the User Details tab
Counter
This column is not editable. It is filled automatically by the system. The counter
is used to indicate the number of times the same user with same level and
company code is assigned to different cost elements. See the lines in the
screenshot at the beginning of this section: Company Code 1000, Approval
Level 000-Coder, and UserObjID CODER1
However, using this way, you cannot limit the approval rights at some
selected levels only to a combination of GL account 1234 and cost center
1010. The solution is to enable multiple cost elements in COA and
maintain the COA like this:
Parallel editing
The following might be a requirement: Multiple users in different company codes
should be able to change data in the COA Details tab in parallel. You can use the /
OPT/AR_COA_S transaction for this purpose.
The following conditions apply for parallel editing of the COA Details tab.
Notes
Technical implications
Locking
To ensure data integrity between standard COA maintenance, COA Detail
maintenance and COA Upload, the following locking scenarios are in place:
Data handling
The behavior of the delete line icon in the /OPT/AR_COA_S transaction needed to
be changed. In this transaction, the delete line action is directly performed on the
database, in contrast to the main transaction where the deletion is performed
only after saving.
The company code will only be shown for determination by requester and
company code. If the determination is configured to use requester, there will be
no maintenance view available for this AFS ID.
Requester ID
Person who the invoice belongs to (initial approver). For more information,
see “Driving the approval flow for DP invoices” on page 363 and “Defining
approval hierarchy and approval level” on page 364.
Company Code
The company code the coder is authorized to perform coding accounting
information for.
Default
Select the check box to set the coder as the default coder for this company
code.
Counter
Counter, cannot be modified.
Coder
User ID of the coder for this combination.
In the Coder Settings view, you can perform the following action:
You as the VIM workflow administrator can set up Anne as Andrew’s substitute so that she
can approve the invoices.
Notes
• When a substitute approves an invoice, the audit trail shows that “XXXX
approves on behalf of YYYY”.
• In the Approval Portal (new interface), you can set up substitutes (delegates)
using the User menu in the header. For more information, see section 8.16
“Specifying settings for delegation” in OpenText Vendor Invoice Management
for SAP Solutions - User Guide (VIM070500-08-UGD).
2. In the User Substitutes Management Utility screen, click the Search User
button to indicate the user to be substituted.
3. In the Search User dialog box, enter search criteria for the substituted user and
click to search for the user ID.
4. To select the user from the list, double-click the corresponding entry in the
Search User dialog box.
5. In the User Substitutes Management Utility screen, click the Substitutes tab,
and then click Select a substitute.
6. In the Search User dialog box, enter search criteria for the substitute and click
to search.
7. To select the user from the list, double-click the corresponding entry in the
Search User dialog box.
To view the change documents, select the records to be analyzed and click the
Display changes button in the mentioned tabs.
You might want to use standard SAP transactions to view change documents or to
write change documents from your custom programs. In this case, see the following
list. It describes the corresponding change document classes and function modules
that are provided with VIM.
User Details
Change document class /ORS/USERMAP
Function module /OPT/VIM_BL_CHNG_USRMAP
Approval Limit/Level
Change document class /OPT/VIM_APPLMT
Function module /OPT/VIM_APPLMT_WRITE_DOCUMENT
COA Details
Change document class /OPT/VIM_LBACOA
Function module /OPT/VIM_LBACOA_WRITE_DOCUMENT
Processing modes
Delta mode
In this mode, you update the existing record with information provided in
the upload file (*.CSV file).
Inserts a new record if the user does not exist yet.
Note: To mark a user as deleted, set the deletion flag in the *.CSV file.
The field DELETED for table /ORS/USERMAP must be enabled in the
upload configuration, and the *.CSV file must contain X at the
corresponding position.
Full mode
In this mode, all data from the COA tables is deleted in the database, and is
updated with the data provided in the *.CSV file.
Important
Handle the full mode with care because all existing users are deleted
in the system if you upload the data in full mode.
Test mode
Select this check box to run the report for testing purposes. Test mode does
not perform table updates.
Note: The processing modes are only applicable to upload (data transfer).
For download, the processing modes are not used.
Update modes
Presentation server
The *.CSV file to be uploaded is selected from the PC (presentation layer).
File path
Path to the *.CSV file that is used to either upload or download the data.
Application server
The *.CSV file to be uploaded is selected from the application layer.
Notes
Upload
The data provided in the *.CSV file is uploaded to the COA tables.
Use SAP internal format
Clear this check box to upload the cost objects that are defined in the *.CSV
file with conversion (conversion exits, for example adding leading zeros).
Select this check box to upload the cost objects that are defined in the *.CSV
file without conversion, in the SAP internal format.
Notes
• The upload report does not perform all input checks as done in the /
OPT/AR_COA maintenance transaction. Manual rework might be
necessary after the upload.
• If the Use SAP internal format parameter is not set, Z constant
COA_VAL_INPUT_FLDS will be considered. For more information, see
Input validation for cost objects on page 59.
Download
The data related to the COA tables is downloaded into the *.CSV file.
Use Configuration
Clear this check box to download the table using the structure of the
database table.
Select this check box to download the table using the structure defined in
the COA upload configuration.
Exits You can overwrite the entire logic using the exits provided in the /OPT/
COA_UPLOAD_REPORT program, using the following Z constants of the IAP product
code in the /PTGWFI/Z_CONST table:
COA_UPLOAD_EXIT_UP
Z constant for upload. The reference FM template for the exit is /OPT/
COA_UPLOAD_EXIT.
COA_UPLOAD_EXIT_DW
Z constant for download. The reference FM template for the exit is /OPT/
COA_UPLOAD_EXIT.
Customization You can configure the fields and the field sequence for the COA upload, according
to the tabs in the new COA. The configuration for the COA upload supports only
three of the four tabs. For details, see the following table.
1. To specify the tab type for the COA upload, run the /OPT/VIM_UPLCFG
transaction.
Alternatively, run the /n/OPT/SPRO transaction and navigate to Vendor Invoice
Management > Invoice Approval Configuration > Technical General > COA
Upload Configuration Details.
2. In the Tab Configuration for COA Upload screen, in the COA Tab selection
field, specify the tab type that you want to configure, and click .
Field entries are inserted into the /opt/coa_uplcfg table.
Tab type
COA upload tab type
Table name
Name of the table related to the specified COA upload tab type
Fields
Fields available in this table
Active
Select this check box for the fields that you want to change or update the
information for in the respective tab of the new COA.
Sequence
Specify the order of the fields. This can be flexible, you can determine your
own order or template. Do not duplicate order numbers.
Notes
The proposal for the COA upload configuration entries is created when you
open the corresponding node in /OPT/SPRO. All the field information related to
the COA tab is read. Already existing records are not overwritten. The data is
inserted or modified in the COA upload configuration table /opt/coa_uplcfg.
You must activate the fields in the proposed list of COA upload configuration
entries according to your process.
When using the Use Configuration option for the COA download, this
configuration is also considered when downloading COA data.
Deletion of records in the COA Details tab – For data in the COA Details tab
(key COA for table /OPT/APPR_COA), you can maintain a DELETE_FLAG in the
upload configuration for the COA details table. All entries that are marked with
DELETE_FLAG are deleted from the database.
Important
• OpenText strongly recommends that you fully specify the key of the /
OPT/APPR_COA table in the *.CSV upload. If the key is not specified
completely and you perform a delta upload, existing data that is not
considered in the *.CSV file might be overwritten. Therefore, if you run
a delta upload without fully specified keys, you do so at your own risk.
• When deleting entries in the COA details with the DELETE_FLAG, you
must completely specify the key.
Entries in the *.CSV file that cannot be matched to an existing database entry
are ignored and mentioned in the output protocol of the report.
The virtual field DELETE_FLAG is not reflected in the database table /OPT/
APPR_COA. The virtual field is only used to mark fields for deletion in the upload
report.
Notes
• Always maintain the first column of the *.CSV file with the COA upload tab
type, for example USR. Then follow the sequence for the corresponding table,
mentioned in Sequence on page 69.
• The SAP_USER_IDs must already exist as SAP users.
• Cleaning the personal data from the usermap for records marked as inactive,
selected by user. No records are deleted, but the following fields are set to blank:
last, first, and middle name; department; email; phone number.
• Deleting the usermap records, COA and coder records, for records marked as
inactive, selected by user.
Notes
• The program does not check whether there are approval workflows that are
still open. Such a check is being performed in the COA maintenance
transaction when a user is being deactivated.
• The approver name can be eventually stored in approval process comments.
The comments are stored as SAPScript objects and are not deleted by the
program.
• When personal data is cleared, corresponding change documents are
written. The existing values will then be visible in the change documents
created in the process. The change documents can be deleted later using
standard SAP tools.
1. To open the selection screen, run the SE38 transaction, enter the program
name /OPT/VIM_USERMAP_CLEANUP, and click Execute.
2. On the COA Usermap Cleanup screen, configure the cleanup program, using
the following parameters:
The transaction supports only updating of COA Details, which is the third tab in the
COA maintenance transaction from earlier versions. You can use the alternative
transaction to maintain larger amounts of data, compared to the earlier one.
Note: Performance optimization implies the restriction that any custom COA
columns are not supported. Use the earlier transaction /OPT/AR_COA in this
case.
To access specific COA records with the alternative maintenance transaction, restrict
the selection on User Mapping Object ID, Approval Level, or Expense Type for
Invoices. The selection of the Company Code is mandatory. You can select only one
company code.
Note: The data in the Limits and Users tabs cannot be changed, even in
maintenance mode.
Product code
IAP
Constant name
COA_INDIVIDUAL_LOCK
Run the SM30 transaction for table /PTGWFI/Z_CONST, and set the value to X
to enable the individual locking.
Clear the value to enable global locking if you are processing large amounts
of data that might lead to reaching the global lock limit.
To determine when parking and blocking processes need to be triggered, you must
define the rollout criteria, for example the company code, for these processes.
Note: The rollout criteria are used for two additional functions:
• for the posted approval process. For more information, see “Configuring
event linkage for posted approval” on page 358.
• for the creation of accompanying DP documents for documents that are
posted or parked directly in the SAP system, in connection with a
corresponding setting of the Z constants 005 DOCTYPE_NPO and 005
DOCTYPE_PO.
Note: Company codes, document types, and plants are part of the rollout
criteria for the PO parking process and the PO blocking process. For the Non
PO parking process, company codes and document types are part of the rollout
criteria.
• Rollout company codes, plants, and document types are maintained in the
respective tables by using the OpenText Customization:
Company codes
/OPT/VIM_CCODE_A
Plants
/OPT/VIM_PLANT_A
Document types
/OPT/VIM_DTYPE_A
1. To define the rollout criteria, run the /n/OPT/SPRO transaction and navigate to
Vendor Invoice Management > PO Based Invoice Configuration > Parked
Invoice Processing Configuration > Rollout Criteria (Workflow Start
Conditions) > Allowed Company Codes, Plants, Document Types.
2. In the Allowed Company Codes screen, select either both PO Invoice Process
and Non PO Invoice Process or only one of the check boxes for the respective
Company Code.
3. Click New entries to add a company code.
Save your settings when finished.
4. Double-click Allowed Plants and Allowed Document Types in the navigation
panel to switch to the respective screens and define the rollout criteria for plants
and document types, as described for company codes.
The respective receiver function module triggers the workflow based on the
data in the tables. The workflow is triggered when there is no data maintained
in the table(s) or the data meets all the conditions such as company code,
document type and plant (only for PO invoices).
Caution
If you change the configuration in this section, the PO parking process
might not trigger at all.
Company codes, document types, and plants are part of the rollout criteria for
the PO parking process and the PO blocking process. For details, see “Defining
rollout criteria for the PO parking process” on page 77.
1. To define the rollout criteria, run the /n/OPT/SPRO transaction and navigate to
Vendor Invoice Management > PO Based Invoice Configuration > Blocked
Process Configuration > Rollout Criteria (Workflow Start Conditions) >
Allowed Company Codes, Plants, Document Types.
2. In the Allowed Company Codes screen, select either both PO Invoice Process
and Non PO Invoice Process or only one of the check boxes for the respective
Company Code.
3. Click New entries to add a company code.
Save your settings when finished.
Caution
If you change the configuration in this section, the PO blocking process
might not trigger at all.
Notes
• You must activate this linkage if you want to use posted approval for
PO invoices, because the event to trigger posted approval is generated
in the receiver function module /OPT/BL_PO_BLK_RECEIVER. Make sure
that your setting of rollout criteria does not prevent the execution of the
receiver function module.
• The recommended event linkage is with receiver TS00275264. You can
use the /OPT/VIM_IMG311 transaction for the following purposes:
Note: For a description of the configuration necessary for the Non PO parking
process, see “Non PO parking process configuration“ on page 325.
To completely disallow the Non PO parking process, deactivate the event linkage as
described in “Event linkages” on page 83.
Note: Company codes, document types, and plants are part of the rollout
criteria for the PO parking process and the PO blocking process. For the Non
PO parking process, company codes and document types are part of the rollout
criteria.
Rollout company codes and document types are maintained in the respective tables
by using the OpenText Customization:
Company codes
/OPT/VIM_CCODE_A
Document types
/OPT/VIM_DTYPE_A
1. To define the rollout criteria, run the /n/OPT/SPRO transaction and navigate to
Vendor Invoice Management > Non PO Based Invoice Configuration >
Parked Invoice Processing Configuration > Rollout Criteria (Workflow Start
Conditions) > Allowed Company Codes, Plants, Document Types.
2. In the Allowed Company Codes screen, select either both PO Invoice Process
and Non PO Invoice Process or only one of the check boxes for the respective
Company Code.
Caution
If you change the configuration in this section, the Non PO parking process
might not trigger at all.
This part describes the advanced customizing. This customizing changes the VIM
baseline and partly includes extensions and customer exits. An example is the DP
process configuration.
Important
If you create new elements from baseline elements in the advanced
configuration, do not change the baseline configuration but only copy it. Use
element names that begin with Z and numeric elements with 800 or 900. If you
need to enhance the VIM document status, use alphanumeric values (for
example Z1). VIM has already occupied the whole range between 00 and 99.
VIM implements authorization checks in several reports, for the COA maintenance
transaction /OPT/AR_COA, for the indexing screen, and for VIM Workplace.
In the reports, in the indexing screen, and in VIM Workplace, the authorization
checks ensure that SAP users working with VIM are able to see and process only the
information that they are authorized for. In the COA maintenance, the authorization
checks make sure that the user is allowed to display or maintain the entries.
For backward compatibility reasons, the authorization checks are disabled in the
standard configuration. You can enable them on demand as described in “Enabling
VIM authorization checks globally” on page 96.
If you run VIM in a multiple backend landscape, the data for the Central Reporting
module is normally collected from more than one system. It may be important to
distinguish between documents arriving from different systems even if they have
the same company code. Because of this, OpenText provides the new authorization
object J_6NIM_BUK, which has the following check fields: activity, logical system,
and company code. The activity checked currently in the reports is 03 - Display.
The logical system and the company code correspond to the document source.
In case of VIM Analytics and Current Liability Report, the data that is displayed
comes from the current (local) system only. Therefore, these reports use a blank
logical system value when checking the authorizations.
Restrict the visibility of the data regarding company code authorizations of the users
for the following reports:
All reports perform the checks for the blank value of the company code whenever it
is relevant for DP documents. If the authorization checks are active, the documents
with a blank company code are not shown to all users, but are checked as are all
other documents. Therefore, unless you are granting “all values” access with an
asterisk (*), it is important to allow the display by adding the empty company code
value in the authorization profile. The value to enter is ' ', that is a space
surrounded by single quotes. For the OpenText authorization object J_6NIM_BUK,
the authorization profiles in the central system must include entries with blank
company code for the central and satellite systems as needed.
Similarly, to grant access to local documents in VIM Analytics and Current Liability
Report, you must maintain the entries with blank logical system in the authorization
profiles. You must do this even if at the same time, for the multiple backend
scenario, the exact logical system name of the local system is already added into the
authorization profiles.
All authorization checks examine the SAP user group of corresponding SAP user in
the user map, or a blank user group of non-SAP users is entered. The following
screenshot from the SU01 transaction shows the field being checked.
The checks of the approval limits and coder assignments will also check the
company code of the record. All three objects support the following activities for the
authorization checks: 01- Create, 02 - Change, and 03 - Display.
Table 7-3 summarizes the authorization checks available in the COA maintenance.
If you do not use the user group field in the SAP user master of the corresponding
SAP user, enter a <blank> value for the user group in the authorization profile. Also
enter a <blank> value for the user group in the authorization profile if the SAP user is
not maintained (for example for pure portal users). The blank company code will be
used whenever the company code is not entered or is entered as “*” in COA Details
or Coder Settings.
If Coder Settings is set to “Use Requester” mode so that the company code is not
used, empty company code values must be used in the authorization profiles. When
switching the setup from “Use Requester” to other modes, all company code values
in the Coder Settings have to be properly populated. If needed, this must be
performed by a user who has the coder maintenance authorization for all company
codes.
Whenever the data is saved, in all four screens, the maintenance transaction
performs consistency checks on the changed data. This also includes the entries that
are not shown to the user because of missing authorization. This means, both the
displayed list and the hidden list are checked together. An inconsistency could be
reported because of the hidden entries. In case of Coder Settings checks, the
consistency errors for hidden entries will be reported as any that have the row index
99999. When such problems occur, the COA consistency has to be checked by a user
who has maximum authorizations for all four screens, for example by a Basis
administrator.
Table 7-4 shows the authorization object used in the indexing screen (DP
dashboard).
Note: With VIM Workplace, you can run work items that are not in your own
inbox, such as Work Views Other, Team, or All. If you want to restrict this
possibility, you must protect it against the authorization objects J_6NIM_WP8
or J_6NIM_WP9.
Note: If your VIM system does not run in a multiple backend environment, all
authorization checks are performed on the same local system. In this case, a
transaction assignment in SU24 is possible for all authorization checks, using
The authorization checks use the authorization object J_6NIM_BC1. Any “Display”
or “Change” authorizations allow the user to execute work items.
Table 7-6 shows the authorization object used in the exception dashboards.
Transaction Description
/OPT/DP_POST_DT_UPD Mass update of posting date in DP documents
/OPT/VIM_INV_REVERSE Reverse invoice posted with VIM
/OPT/VIM_RPT_DATA_LD Initial data load for VIM Analytics (VIM 7.0 only)
/ORS/UMREASSIGNED Approval reassignment
The installation packages provide only the standard entries for “SAP” assignments,
which means those visible in SU22. Copying of the standard VIM assignments into
the “customer” tables (SU24) must be performed through the standard SAP
download / upload programs RSU22DOWN and RSU22UPLD in the following way.
3. Run the upload program RSU22UPLD, and enter the same list of VIM
transactions.
4. Make sure you set the check boxes as shown in the following screenshot:
Note: You can perform a test run first (select Test Mode) and also use the
option to create a transport file if needed (select Enter Data in Transport).
5. When asked for the file to use, select the same file created by the download
program.
6. When you have successfully completed the previous steps, adjust the
transaction assignments, if needed, in SU24. Then, you can use them in the
profile generation tool.
• /OPT/VIM_VA2
• /OPT/VIM_VA21
• /OPT/VIM_VA22
• /OPT/VIM_VA23
• /OPT/VIM_VA24
• /OPT/VAN_LIABILITY
• /OPT/VIM_AGING
• /OPT/VIM_AUDIT
• /OPT/VIM_EXCP1
• /OPT/VIM_KPA1
• /OPT/VIM_PROD1
• /OPT/VIM_SUMM
• /OPT/AR_COA
• /OPT/VIM_WP
Some VIM tables are being delivered without this authorization group. To set this
authorization group on customer’s site, a report is available. The report is called /
OPT/VIM_AUTHGROUP_TABLE_CHNG. You can use it to update:
If you run the report in test mode, the names and the number of tables with default
authorization group are displayed.
If you run the report in normal mode, the report prompts for a transport request
after successfully updating the data. This transport must be transported to quality
and production clients.
The new authorization checks are implemented to comply with SAP security
requirements. You cannot switch them off like it is possible with VIM specific
authorization checks (see “Configuring the authorization checks” on page 94). Most
of the time, VIM users already have the necessary authorizations in their profiles
because they likely use the same transactions outside of the VIM context. For
reference purposes, the list of transaction codes is provided in “Authorization
checks with fixed transaction codes, VIM transactions” on page 97 and
“Authorization checks with fixed transaction codes, standard SAP transactions”
on page 98. If needed, authorization profiles of VIM users can be extended
according to their specific tasks.
Note: Make sure the background user (normally WF-BATCH) has all
necessary authorizations
Table 7-8: Authorization checks with fixed transaction codes, VIM transactions
Table 7-9: Authorization checks with fixed transaction codes, standard SAP
transactions
100 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
7.4. Authorization checks when performing transaction calls
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 101
VIM070500-08-CGD-EN-01
Chapter 7 Authorization checks
• Function modules that belong to core VIM (namespaces /PTGWFI, /ORS and /
OPT)
• Function modules that belong to VIM solutions based on Business Center, used
for Business Center Inbound and Fiori apps (namespace /OTX)
In core VIM, you can additionally secure remote function calls (RFC) by activating
dedicated authorization checks. These checks are optional and are not active in the
baseline configuration for backwards compatibility.
Product code
009
Constant name
SRFC_CHECK_ACTIV
102 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
7.6. Restricting ALV layout for process logs
• The users authorized for activity = 02 are allowed to maintain ALV layouts for
the mentioned screens.
• Unauthorized users do not have any layout options active in ALV toolbars of the
mentioned screens. The default global variant is used all the time.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 103
VIM070500-08-CGD-EN-01
Chapter 7 Authorization checks
2. The authorized users create a global default variant in each ALV screen.
3. All user specific ALV layouts for the following programs are deleted.
• /OPT/CL_C_UI_PLUGIN_DEF_LOG===CP
• /OPT/CIDX_OUTPUT_LOG_ST
• /OPT/SAPLVIM_RPT_FG_005
Note: The ALV layout deletion can be performed as described in SAP Note
933916.
4. Activate the authorization check for ALV layout (table /PTGWFI/Z_CONST).
104 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 8
Incoming document processing
With OpenText™ Business Center for SAP® Solutions (Business Center) 10.0 SP1 or
later and Business Center Solution Integration for Vendor Invoice Management 10.0
SP2 or later, you can use Business Center Inbound Configuration to handle incoming
document processing. For more information, see section 4 “Inbound Configuration”
in OpenText Business Center for SAP Solutions - Configuration Guide (BOCP160302-
CGD).
For documentation about the old IDH and ICC Dispatcher frameworks, see
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide
(VIM070500-03-CGD) (Configuration Guide VIM 7.5 SP3).
If you use Business Center Inbound Configuration, only the following customizing
steps are relevant for VIM:
Each document runs through defined workflow steps indicated by the framework
process. Workflow steps consist of an ordered number of Service Modules. These
Service Modules are integrated components of the framework. You can enhance the
Service Modules by adding new entries in the customizing.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 105
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
OTBCSL03 For the integration of Business Center Inbound Configuration, the OTBCSL03 addOn
addOn (with the corresponding BC set) delivers most settings to process incoming invoices
in VIM. Besides specific Business Center Configuration, also general configuration is
required according to the used inbound scenario.
106 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.1. Business Center Inbound Configuration
Note: Make sure that the channel you use in Business Center Inbound
Configuration is also configured in VIM.
Scenario classification
Entry PS03_VIM_INVC is delivered in BC set. It is required to trigger VIM. You
must assign it in your registration configuration. For details, see section 4.3
“Creating scenario classifications” in OpenText Business Center for SAP Solutions -
Configuration Guide (BOCP160302-CGD).
Document handler - status
All necessary status entries are delivered in BC sets. For details, see section
4.4.1.1 “Configuring the document handler status” in OpenText Business Center
for SAP Solutions - Configuration Guide (BOCP160302-CGD).
Document handler - modules
The following document handlers are delivered in BC sets. Assign the document
handlers in your registration configuration. For details see section 4.4.1.3
“Configuring modules for the required processing steps” in OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD):
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 107
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
8.1.3 Administration
All incoming documents can be monitored and administered in the Business Center
Workplace in the Inbound Administration work center. For details, see section 4
“Business Center Workplace: Inbound Administration work center” in OpenText
Business Center for SAP Solutions - User Guide (BOCP160302-UGD).
1. Run the /n/OPT/SPRO transaction and navigate to the menu path Vendor
Invoice Management > Document Processing Configuration > General
Configuration > Incoming Document Processing > Maintain Channels.
The Channel Setup Overview shows a list of all existing Channel IDs.
108 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.2. Maintaining channels
2. Make sure that all relevant VIM import channels are included in the table.
Important
The Web Dynpro application of the KPI Dashboard can display a maximum of
10 channels.
To create a channel:
Channel Type
Select the channel type from the list.
Short Description, Text
Enter the channel description. It is language dependent.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 109
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
Mapping ID
Enter the Mapping ID.
You maintain mapping IDs for each channel, for example IDOC. The
mapping ID is used to determine whether the mapping is done through a
custom function module or field to field.
Sys Det. ID
If you want to link a System Determination ID to the channel, enter the
System Determination ID. If no System Determination ID is linked here, the
Default Company Code Look up system determination can be used in a
multiple system scenario.
Process ID
Enter the process ID.
You can maintain process IDs for the channel. The process ID is used to
determine which process handling the incoming document is linked to.
Notes
You can create a Mapping ID to logically group a mapping set for a particular
channel. A Mapping ID is tied to a channel so that proper mapping is performed for
an incoming invoice for that channel.
110 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.3. Maintaining the VIM field mapping
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 111
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
Ignore
Enter characters that are deleted in an extra step before the mapping
continues. This is useful, for example, if there are apostrophes in the
Reference Number. Enter the apostrophe in the Ignore Chars field in the
XBLNR line, to avoid a short dump in duplicate check.
The field can contain up to 6 characters.
Condense
To remove blank characters in the input string, enter X in this field.
Notes
112 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.3. Maintaining the VIM field mapping
the PO number list and the DN number list must be presented to VIM with
the fixed external names ListPO and ListDN. These are hard-coded
keywords for VIM. VIM parses the strings and enters the numbers into the /
OPT/VIM_1PO_DN table. The mapping is activated, as soon as the keyword is
present in the mapping table.
• With VIM 7.5 SP6, the OCR interface to ICC has been extended to accept an
unlimited count of PO numbers and DN numbers from ICC. A new docpart
List is used to transport an additional line for every number. For this
interface, field names are not configurable and have the fixed values
TablePONumber and TableDNNumber. You can switch the mapping on
and off by adding or removing fields POList and DNList in the mapping
table /OPT/VIM_T109_N. These fields are already used to switch the mapping
for the string base list fields.
This feature requires ICC 7.5 SP6 as minimum ICC support package level.
In addition to the standard field mapping, automated field enhancement offers the
possibility to set or change field values statically or dynamically.
Counter
To specify a call order of the field enhancement, enter a number up to 4
digits.
Field Type
Select field level Header or Item.
Field Value
If selected in Field Processing Type, enter a fixed value or a system
variable.
Satellite
If the exit function module must be executed on a satellite system, select this
check box. The check box is only available on the central instance in a
multiple backend system.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 113
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
Note: If you are using Subsequent Debit/Credit, for the field name BSART
(E1EDK01 segment, object name INVOIC02), maintain the Document Field
name VORGANG instead of CREDIT_MEMO.
Additionally, in the IDoc Field Mapping, maintain, for the field name
BSART, the Document Field Name VORGANG instead of CREDIT_MEMO. For
more information, see “Configuring IDoc field mapping” on page 121.
3. Save your settings.
Starting with Business Center 10.0 SP1 and Business Center Solution Integration for
Vendor Invoice Management 10.0 SP2, you can use Business Center Inbound
Configuration to handle incoming document processing. For more information
about how to configure document registration for Document Pipeline and document
handler, see section 4.4.2.4 “Customizing the Document Pipeline registration type”
in OpenText Business Center for SAP Solutions - Configuration Guide (BOCP160302-
CGD).
Starting with Business Center 10.0 SP1 and Business Center Solution Integration for
Vendor Invoice Management 10.0 SP2, you can use Business Center Inbound
Configuration to handle incoming document processing. For more information
114 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
about how to configure document registration for IDoc and document handler, see
section 4.4.2.2 “Customizing the Inbound IDoc registration type” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
To activate the IDoc processing for Business Center Inbound Configuration, you
must assign the corresponding processing function delivered with Business Center
in the Inbound Function Module configuration in the BD51 transaction. For more
information, see “Defining settings for the inbound function module” on page 115.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 115
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
Input type
Enter 0 (for Mass processing).
Dialog allowed
If you want to process IDocs in dialog mode, select this check box. With
baseline implementation, the check box is cleared.
4. Click Save .
8.5.1.2 Linking the inbound function module to IDoc type and message
type
In this step, you establish the link between the inbound function module, the basic
IDoc type, and the message type.
To link the inbound function module to IDoc type and message type:
Function module
/OPT/DB_INBOUND_IDOC_PROC
Function type
Select Function Module.
116 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
Basic type
Enter the basic type, for example INVOIC02.
Message Type
Enter the message type, for example INVOIC.
Object Type
Enter /OPT/V1001.
Direction
Select Inbound.
Description
Enter a meaningful description.
5. Click Save .
The process code is a logical name for the processing function module. The process
code is used to uniquely determine a function module that processes the received
IDoc data and converts an IDoc to an SAP document.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 117
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
Process code
Enter the process code name.
Tip: You can choose a name for the process code that suits your needs.
Description
Enter a meaningful description.
Identification
Enter the inbound function module /OPT/DB_INBOUND_IDOC_PROC.
Option ALE
Click Processing with ALE service.
Processing type
Click Processing by function module.
5. Click .
6. Double-click Logical message in the Dialog Structure.
7. Assign the new process code to the logical message using the following
parameters:
118 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
Process code
Process code name as defined in Step 4.
Message type
Enter the message type, for example INVOIC.
8. Click Save .
In this step, you assign the new process code to the IDoc partner profile. You must
specify partner and partner type. You must also specify whether you define a profile
for inbound or outbound data exchange. You can use an existing partner profile. The
partner type must be Logical system (LS).
Tip: If you want to create a new partner profile, you must first create a new
logical system. See the SAP documentation for details.
2. Select the partner profile under Partner Profiles > Partner Type LS.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 119
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
Partner No.
ID of the partner profile
Partn. Type
Partner Type: Enter LS for logical system.
Message type
Enter the message type, for example INVOIC.
5. On the Inbound options tab, enter the Process code that you created in
“Creating a new process code” on page 117.
6. Click Save .
120 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
• The first level of mapping maps the IDoc data to Intermediate fields.
• The second level of mapping maps Intermediate fields to VIM fields (index
fields). The second level of mapping is maintained at the channel level.
Every type of incoming document, for example IDoc, is assigned to a channel.
Based on the mapping ID which is assigned to the channel, each type of
incoming document is mapped differently. The mapping ID determines the set of
mappings from the Intermediate Fields to the VIM fields. For VIM, the channel
for the EDI scenario is IDOC. The Channel IDOC is assigned to the mapping ID
IDOC.
In multiple backend systems, the incoming IDocs are received and preprocessed in
the central system. After that, they are sent to the satellite system for further
processing. The satellite system is determined based on the company code. Each
system in the multiple backend system is identified by a logical system name. See
“Determining system by company code for multiple backend systems” on page 126.
1. Run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Invoice Management > Document Processing Configuration > General
Configuration > Incoming Document Processing > Idoc Data Mapping.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 121
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
Obj. name
Development Object name: the IDoc type INVOIC02
Segm.type
Segment type in IDoc type
Field name
Segment field
IDOC Qualf(Fld/VAl)
Qualifier of the Segment
Qualifier Value
Value of Segment Qualifier
Field Type
Select either Header or Item type from the list.
Value
If you selected Constant (fixed value), System variable, or Function
Module as the field mapping type, enter the corresponding value.
122 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
If you selected Function Module, you can use the /OPT/GET_YEAR or /OPT/
IDOC_UOM_ISO_TO_SAP function modules as a template.
Notes
Value
POLIST or DNLIST
• If you are using Subsequent Debit/Credit, for the field name BSART (E1EDK01
segment, object name INVOIC02), maintain the Document Field name
VORGANG instead of CREDIT_MEMO.
Additionally, when maintaining the VIM field mapping, maintain, for the
IDoc Mapping ID, the CREDIT_MEMO Document Field name instead of
VORGANG in Automated Field Enhancement. For more information, see
“Maintaining the VIM field mapping” on page 110.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 123
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
From Business Center 10.0 SP1 and Business Center Solution Integration for Vendor
Invoice Management 10.0 SP2, you can use Business Center Inbound Configuration
to handle incoming document processing. For more information about how to
configure document registration for IDoc and document handler, see section 4.4.2.2
“Customizing the Inbound IDoc registration type” in OpenText Business Center for
SAP Solutions - Configuration Guide (BOCP160302-CGD).
Z constant To enable the PDF rendition, you must maintain the Z constant EDI_IMAGES_FM
(product code 005) in table /PTGWFI/Z_CONST. In the Constant Value field, enter a
function module using the template /OPT/EDI_IMAGES_EXIT_TEMP. You can use the
baseline function module /OPT/EDI_IDOC_PDF_IMAGE.
2. For the fields in the Define Profiles area, see the following screenshot and
“Defining profiles for the PDF log” on page 907. The field description is similar
to the general PDF log.
124 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
The IDoc rendition to PDF shows the following differences from the general
PDF log:
• The fields PDF Timezone and Time Zone do not apply for the IDOC
rendition.
• The Document type must be the same as the IDOC channel archive object
document type.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 125
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
For the EDI scenario, you configure the system determination using Company Code
only in the central system.
For a description of the configuration, see section 4.8 “Maintaining the system
determination” in OpenText Vendor Invoice Management for SAP Solutions - Scenario
Guide (VIM070500-08-CCS).
In the following screenshot, Company code 2000 is mapped to the Logical system
T90CLNT090.
To test an IDoc:
1. To start the Test tool for IDoc processing, run the WE19 transaction.
126 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
3. Click the Inbound function module button in the application tool bar. The Test
inbound IDoc via a function module dialog box opens.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 127
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
5. To check the status of the new IDoc, run the WE02 transaction.
128 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
6. Enter the new IDoc number into the IDoc number field and click .
The IDoc with status information is displayed. Successfully processed IDocs
have the status 53.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 129
VIM070500-08-CGD-EN-01
Chapter 8 Incoming document processing
1. To access the Data Browser: Initial Screen, run the SE16 transaction.
3. Enter the IDoc number in the EDI_DOCNUM field of the selection screen and
click in the application tool bar.
130 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
8.5. EDI configuration
Important
Changes of the global configuration parameters as described in this section
may affect the functionality of the process.
3. In the WebFlow Constant Table, under Product Code 005, double-click the
Constant EDI_IMAGES_FM.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 131
VIM070500-08-CGD-EN-01
Chapter 9
Document Processing process configuration
Document types
• Highest level attribute, effect the processing, process flow and user interface.
A more detailed configuration according to the process and screen layouts is
done at the invoice characteristic level; see “Characteristic specific
configuration“ on page 547. Therefore it is not necessary to create many
different document types for individual process settings. Use a document
type as a global invoice processing template.
• Determine the SAP transaction to be called during document creation.
• Determine the metadata (index) collection screen layout and fields.
• Can be derived from OCR data using the document type determination rules
engine.
• Require no one-to-one relation to SAP ArchiveLink document types.
Process types
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 133
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Business rules
– process type
– document type (in case of OCR or external data input)
• Use configuration to apply logical conditions.
• Allow defining of multiple criteria.
• Can be specified regarding order and exclusivity.
• Can be used for validating data from external systems (OCR).
• Can be automatically applied to the metadata to effect the process flow.
• Can be configured to be called at multiple stages in the process flow.
Roles
– Actions
Actions can be based on transactions or class method or workflow tasks.
– Referrals (for collaboration)
• Can effect the processing logic.
• Can effect the user experience.
• Can trigger the workflow engine to re-run the rules on the most current
metadata to effect the process flow.
• Can be configured to change the document status.
BDC IDs
134 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
• Are optimized for both dialog processing and background processing.
• Allow to set dynamic parameter IDs.
• Can be used to configure new user collaboration actions.
• Eliminate the need to code parameterized transactions.
• Allow to configure BDC success messages.
Main steps Implementing process scenarios in the DP workflow component of VIM comprises
the following main steps:
The starting point for any configuration is a set of process flow swimlanes.
Figure 9-1 shows an example for a process swimlane as implemented by the DP
workflow:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 135
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
NPO_75
for Non PO processing
PO_75
for PO processing
DWN_75
for Down Payment processing
The NPO_75 and PO_75 document types contain a huge amount of business rules,
which are relevant to process Non PO or PO invoices in different countries. Because
136 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
The customizing allows specifying if a business rule should be executed for each
characteristic or executed only depending on the characteristic setting. For more
information, see “Characteristic specific configuration“ on page 547.
The baseline also contains only a few business rules which are mandatory for further
processing. The intention is to avoid dialog steps to increase efficiency.
With VIM 7.5 and above, baseline document types PO_75, NPO_75 and DWN_75
can be posted automatically. For more information, see “Configuring automatic
posting” on page 182.
The DWN_75 document type allows processing of Down Payments (both Non PO
related and PO related) based on a specific set of business rules. After processing the
defined business rules and running through the corresponding approval process (if
required), posting of Down Payment Requests using the F-47 transaction is possible
in dialog or background.
Note: The document types described in this section are the DP document types
in the baseline configuration of VIM.
Of course, you are free to create new DP document types, and, in upgrade
projects, to keep the DP document types that you are used to.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 137
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Description
Enter the document type description.
138 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
Number Range
Enter the number range for the number range object. If a custom number
range object is not defined in global configuration, you can maintain the
number range for object /OPT/DOCID in the Maintain Number Ranges step;
see “Configuring global parameters” on page 250.
Classifier
Select the classifier from the list. The classifier represents a further detailed
classification of special invoice types (for example Down Payments).
Document Index Type
Select the type of indexing to determine how the system determines the
origin of data. The following values are available:
Indexing using OCR
Use this option if the document is scanned and the OCR interface
passes the data to SAP ERP for creating an OpenText document.
Online Indexing
Use this option if archiving a document using the SAP ArchiveLink
Early Archiving process. Indexing is manual and the person responsible
maintains the data and submits for further processing.
In case of online indexing, the first process type that is determined will
be the default process type (see Default Process Type on page 141),
regardless of the list and the sequence of process types configured for
the document type.
No Indexing
Use this option if there is no indexing required and the document is
directly processed. Use this option if there is no scanned image and the
process is triggered using an API provided by OpenText.
Indexing using Idoc
This is not supported at the moment.
Invoice Type
Decide whether the document generates a Non PO Invoice or a PO Invoice.
Default Archive Doc. Type
The following logic applies:
ArchiveLink document type is set for external data
Document types will be checked for the ArchiveLink document type;
not only the field in the global customizing but also the new Archive
Link Mapping table; see “Mapping ArchiveLink document types”
on page 156.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 139
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Example: If the value in the field is AA,BB, the system will set the FI document type
AA for invoice and BB for credit memos.
140 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
• ATTRIBUTE1
• ATTRIBUTE2
• ATTRIBUTE3
• ATTRIBUTE4
• CUSTOM_FIELD4
• CUSTOM_FIELD5
• CUSTOM_FIELD6
• CUSTOM_FIELD7
• CUSTOM_FIELD8
• CUSTOM_FIELD9
• CUSTOM_FIELD0
Process Configuration
Document Posting Configuration group
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 141
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Example: If a document has no errors and should directly be created in SAP ERP,
you select a default process type for creating the document.
Rescan Role
Select the role that receives the work item if the document data is not legible
or if the user decides to send the document for rescanning.
Note: A valid role must be already defined, see “Defining roles”
on page 36.
Posting Role
Select the role that is responsible for posting the document finally. If the
posting of the document fails in background, this role gets the work item to
post the document in dialog.
Note: A valid role must be already defined, see “Defining roles”
on page 36.
Display Index Data
Select this check box to display the index document in a separate session
while document posting so the user is able to reference back the index data.
Note: At least one session must be available for display.
Skip Dashboard
Select this check box to skip the dashboard step. The system creates the SAP
document directly during the document posting process for the posting
user.
Example: If the document is all okay, the user might want to post it directly,
without displaying the document data.
Display Image
Select this check box to display the archived image linked to the document
in a separate session when the user processes the work item.
Note: Archiving must be active in the system.
142 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
3. In the Document Processes Overview screen, select a process type and click the
button in the application bar.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 143
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
4. In the Document Processes Details screen, define the process type, using the
following parameters.
Process Type
Select the process type that is valid for the document type.
Active check box
Select this check box to achieve that the process type is considered for the
document type, for example if you want to delimit a specific process type
delivered by OpenText or defined in the system but no longer used.
BDC Transaction Id
Select the BDC Id that the system uses to process an SAP transaction to
create an SAP document in user context.
Background Tran Id
Select the BDC Id that the system uses to process an SAP transaction to
create an SAP document in the background. This is relevant if the user does
not want to see the index data (dashboard) during document posting.
Autopost Flag
The following settings are possible:
144 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
ParkReason
Enter the parking reason the system uses to park the document.
Prerequisites
• The BDC Id defined for Document Create is used for parking the
document.
• A valid parking reason is defined in the Maintain Parking Reasons step
for Non PO or PO documents; see “Configuring parking reasons”
on page 282 and “Configuring parking reasons (Non PO parking
process)” on page 327.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 145
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Step Id
Define a step Id.
Process Type
Define the process type for the step Id.
Exclusive Indicator
Select this check box if the system should stop checking for next process
type even though the current step resolves a process type.
Bypass possible
Select this check box to enable the Bypass icon on the Bypass/Simulate
Business Rules screen for the user.
Run in Central
This column appears in satellite systems, only.
Select this check box for any business rule to have it run in the central
system by an RFC call from the satellite system. Some business rules are
centralized. Satellite systems can use such centralized rules by this option.
146 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
1. In the Proc. Type. Det. Sequence Overview screen, select a step and double-
click Sequence Steps.
Step Seq.
Enter a numeric value identifying the step sequence.
Field name
Select the field name in document data that is considered for validation.
Check Type
Select the type of check to be performed:
• If Table Field is selected, the system validates that the value of the
document field at runtime exists in the check table mentioned in the
Table field. If the value does not exist, the step is considered to be
successful and the system will determine the process type.
You have to maintain the Table field.
• If Check Function is selected, you can define your own check against
the document field. If the function raises an exception the step is
considered to be successful and the system will determine the process
type.
You have to maintain the Check Function field.
• If Constant Value is selected, you can define a constant value against
which the runtime data of the document is compared. If the runtime
value matches the configured value, the step is considered to be
successful and the system will determine the process type.
You have to maintain the value of the constant in the Check Val field.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 147
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Note: The business rule check function library offers additional check
function modules that are not directly delivered as pre-customized
business rules. You can use the function modules as new business rules
depending on your needs. The new library is located in function group /
OPT/VIM_PROC_TYPE_LIBRARY, which has been created to collect such
function modules.
If you want to activate one of the library function modules as a new
business rule for any VIM document type, perform the following
customizing steps:
148 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
3. In the Index Screen Options Overview screen, click the New entries button in
the application tool bar to create a new index screen option.
Process Type
Select a valid process type, as defined in “Defining process types”
on page 143.
Description
Description of the selected process type
Current role
Role which processes the work item
Allow Changes
Select this check box for a given role to allow all users in the role defined to
change the index data.
Prerequisite – The document should not have been submitted, yet.
Show Duplicates
Select this check box to achieve that the duplicates identified by the system
are displayed below the index data screen for the role that is processing the
work item.
Example: It might be relevant for the DUP_CHECKER role to look at the duplicates to
decide whether the document is actually a duplicate. For the AP_PROCESSOR role,
showing duplicates might not be that important as the document might have
already completed the duplicate check process and might be ready to be posted or
parked.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 149
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Initial Tab
With the indexing screen delivered with VIM 7.0 and higher, you can
configure each tabstrip of the indexing screen for the tab that is shown
initially:
Basic Data
Shows the basic indexing information which is also available on the
invoice document
Line Item Data
Shows the relevant line items
Accounting Data
Shows additional SAP specific data for the accountant to post the
document
Tax Data
Shows relevant tax information
Process Data
Shows relevant process information and also provides access to the
duplicated invoices
Enable Simulate
Select this check box to simulate skipping certain business rules. The
Simulate process will check the relevant business rules.
Enable Bypass
Select this check box to bypass the business rules.
Dis.Obsolete
Select this check box to hide the Obsolete button in the DP Dashboard for
the selected DP document type and the current role.
Dis.Rescan
Select this check box to hide the Rescan button in the DP Dashboard for the
selected DP document type and the current role.
150 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
Show Match
Select this check box to display the matching area within the item data
subscreen for PO invoices to the user. This is relevant to execute the
matching for PO related documents based on the SAP proposal.
Disable GL Tab
Select this check box to hide the GL tab on the index screen for the selected
PO document type and the current role.
Code Check Enable
You can configure the check box in the following places:
Document type configuration
/OPT/SPRO > Document Processing Configuration > Document Type
Configuration > Maintain Document Types, option: Index Screen
Options (described in this section)
Configuration in Characteristic
/OPT/SPRO > Document Processing Configuration > Document Type
Configuration > Characteristic Specific Document Type
Configuration, option: Characteristic Specific Screen Configuration
(see “Characteristic specific screen configuration” on page 568)
Select the check box for a certain process type and a certain role to show the
Validate Coding button in the DP Dashboard, Line Items tab, G/L Account
tab of the given role and the given process type. This button enables the
agent to validate the coding entered in the indexing screen.
Notes
• To use the Validate Coding button, you must select the Code Check
Enable check box in both places (document type configuration and
configuration in Characteristic) if the Characteristic Check check
box of the process type is selected (see “Defining the process type”
on page 230). In baseline, this check box is cleared.
The configuration in Characteristic will overwrite the document
type configuration.
• Coding validation is available for Non PO based DP documents.
Enable Code Upload
You can configure the check box in the following places:
Document type configuration
/OPT/SPRO > Document Processing Configuration > Document Type
Configuration > Maintain Document Types, option: Index Screen
Options (described in this section)
Configuration in Characteristic
/OPT/SPRO > Document Processing Configuration > Document Type
Configuration > Characteristic Specific Document Type
Configuration, option: Characteristic Specific Screen Configuration
(see “Characteristic specific screen configuration” on page 568)
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 151
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Select the check box for a certain process type and a certain role to show the
Upload Coding button in the DP Dashboard, Line Items tab, G/L Account
tab of the given role and the given process type. This button enables the
agent to upload coding from an Excel sheet.
Notes
• To use the Upload Coding button, you must select the Enable Code
Upload check box in both places (document type configuration and
configuration in Characteristic) if the Characteristic Check check
box of the process type is selected (see “Defining the process type”
on page 230). In baseline, this check box is cleared.
The configuration in Characteristic will overwrite the document
type configuration.
• Upload coding is available for Non PO based DP documents.
152 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
Field Stat
Required
Make the field mandatory at runtime.
Input
Define the field as an input field for users.
Display Only
Only display the field.
Hide
Hide the field on the screen.
Note: The attributes Input, Display Only, and Hide are independent
from the processing state. Unlike those, the attribute Required works as
follows: If the processing state is configured in Z constant 005 /
REQUIRED_PROC_TYPE, the field is required and the field will show the
Input Required icon. In all other processing states, the field is a normal
input field. Thus, the field input can be skipped in the early processing
steps.
There are some special fields that are not in the database but can be displayed in the
index screen. To use them, you must configure the Field Stat column for the
following parameters:
VORGANG
To display Subsequent Debit and Subsequent Credit for PO in the index
screen, under Invoice Data, Transaction field, set the parameter VORGANG to
Input.
DIFFERENZ
To display the Balance traffic light in the index screen, under Invoice Data, set
the parameter DIFFERENZ to Display Only.
DN_LIST, PO_LIST, SES_LIST
To display the DN List, PO List, and SES List buttons in the index screen, under
Invoice Data, set the parameters DN_LIST, PO_LIST, and SES_LIST to Input.
IGNORE_IP
If the purchase order contains an invoicing party, this field appears (if it is not
set as Hide). The invoicing party is used as reference for bank data and
withholding tax.
Check the field IGNORE_IP, if you want to ignore the invoicing party and pay to
the vendor directly.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 153
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
3. In the Index Item Configuration Overview screen, configure the index item
fields, using the following parameters:
Field Stat
Every line represents one line item field of the selected DP document type,
indicated by the Field Name.
Required
Make the field mandatory at runtime.
Input
Define the field as an input field for users.
Display Only
Only display the field.
Hide
Hide the field on the screen.
Note: The attributes Input, Display Only, and Hide are independent
from the processing state. Unlike those, the attribute Required works as
follows: If the processing state is configured in Z constant 005 /
REQUIRED_PROC_TYPE, the field is required and the field will show the
Input Required icon. In all other processing states, the field is a normal
input field. Thus, the field input can be skipped in the early processing
steps.
154 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
3. In the Field Selection dialog box, select one or more filters: Field Name,
Language Key, Data element, Label and click .
4. In the Determine Work Area: Entry dialog box, enter filter values and click .
5. In the Maintain index screen header field labels or the Maintain index screen
line item field labels screen, customize the field labels, using the following
parameters:
Field Name
Field in the index data table. The table is either /OPT/VIM_1HEAD (header
fields) or /OPT/VIM_1ITEM (line item fields).
Language
Language, for example EN.
Data element
Enter the data element.
For line item labels, baseline configuration determines that the labels are
fetched based on the data element that is mapped to the field. If a data
element is available, the medium size label is fetched automatically. If an
input is provided in the text field, the label from the data element is
ignored. This means the field is cleared.
Label
Enter the language-specific label, which represents the heading of the field.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 155
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
You can migrate for multiple languages at the same time for bulk update of the line
item labels. The migration program updates the line item labels only. You cannot
use it to update header field labels.
After running the migration program, you must add the table entries to a
customizing request manually. This enables you to transport the table entries when
using the migration program.
Note: If you add entries using the OPT/SPRO node Translations/Labels for
Index Screen Fields, no customizing transport request is necessary to move the
table entries to the target system.
2. In the Upload labels for line item fields screen, enter the Language Key
(range).
Country
Enter a country code to which the ArchiveLink document type is associated.
Doc. Type
Enter an ArchiveLink document type to map it to the selected DP document
type.
156 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
Description
Enter a description of the ArchiveLink document type.
You can define country specific archive document types in the document type
configuration. You can also define an archive document type that is not country
specific. This means, it is used for the rest of the countries. If you have only one
archive document type that is not country specific, you can use the default archive
document type in the document type configuration. If you have more of these
document types, leave the default archive document type empty and make archive
document type entries with empty value in the Country column.
Prerequisites
The DP document type, the company code, or the Country field might be changed
during DP processing. In this case, VIM checks if the archive document type has to
be adjusted, and if so, performs the adjustment. If the new archive document type is
linked to a different logical archive, the images are copied between the archives.
The application log shows messages for object /OPT/VIM, subobject DP, and
document number as external ID. Messages are of the following types:
Information
if there was a copy to a new archive
Warning
if there is no image linked
Error
if there was an exception in one of the called function modules
You can have country specific document types and you can maintain the relation in
the ArchiveLink mapping table. Whenever a company or a country is changed in the
indexing screen, the relation is checked and, if necessary, the archive document type
is adjusted. There are two user exits to change this, controlled by two Z constants:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 157
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
You can define the logic to determine the archive document type and you can define
the logic when a redetermination should be triggered.
To enable custom solutions for attachments, VIM 7.5 SP3 introduces the /OPT/
ES_VIM_R1AX1 enhancement spot in the /OPT/VIM_R1AX1 program. When changing
the DP document type, this enhancement spot allows implementing a custom logic
to reassign ArchiveLink document types of documents and attachments to other
logical archives.
Further filters For the /OPT/VIM_CHANGE_DOCUMENT_TYPE function module, VIM 7.5 SP4
introduces an enhancement spot /OPT/ES_VIM_FG1A3. You can use the enhancement
spot to apply further filters for the new document types available in the Change
Document Type option, for example authorization checks.
The DP Dashboard provides the possibility to show the image in the Detail pane.
The configuration described in this section is only relevant if you want to deactivate
the image plug-in, or to display the image in a separate window.
3. In the WebFlow Constant Table, under Product Code 005, double-click the
Constant DASHBOARD_IMAGE_AUTO.
158 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
With version 7.5 and higher, VIM provides some options in the logic module
processing to match and derive data even if no 1:1 relation is available.
• Ignoring the line item data coming from ICC and deriving the line item data
from the PO(s).
• Ignoring the line item data coming from ICC and deriving the line item data
from the MIRO proposal.
• Matching the PO and GR data against the data provided manually or from
external sources, and, based on the PO and GR data, completing the data in the
line item fields where it is missing.
With VIM 7.5 and higher, the determination of line item data is implemented in logic
module /OPT/CL_D_LM_DETERM_PO_MAP, which is included in logic module
processing Line based processing / enrichment / matching (PO).
Old In VIM versions prior to 7.5, the following DP business rules were used to process
the PO matching and exception handling:
• Manual Check Needed for Indexing Lines (PO), DP process type 110
• Unable to Determine PO Line Number (PO), DP process type 109
New These two business rules are replaced by the combination of a logic module and a
business rule:
Note: In this section, the “OCR” term, which is used to denote the source of the
data, applies equally to the data entered manually or received from external
sources like IDoc.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 159
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
> Automated Line Processing > PO Line Determination > Maintain PO Line
Determination Procedures.
PO Line Det. ID
The ID must be numeric.
You must assign the PO Line Determination ID to the DP document type;
see Step 8 on page 162.
Description
Enter an appropriate description.
Check Function
Optionally, use a custom function module here to determine the PO line
number. By default, the field is blank. An OpenText standard function
module is used.
No of Fields to Match (shown if Match All Fields is cleared)
Specify how many fields should be matched before claiming the PO line
number found. The number of fields you specify here should be less than or
equal to the number of fields you maintain for this Determination ID.
Match All Fields
Select this check box to use all fields maintained in the PO line
determination fields for the Determination ID to find a PO line match.
Match Conditional (used in logic module Line based processing /
enrichment / matching (PO))
Select this check box to configure a condition in the fields configuration
between each field within one field group. See Relation on page 162.
Match against Proposal (used in logic module Line based processing /
enrichment / matching (PO))
Select this check box to match not only against PO information but also
against the MIRO proposal. If a unique match is found, also relevant key
fields (GR or SES) are retrieved.
160 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
Match within MIRO Tolerance (used in logic module Line based processing
/ enrichment / matching (PO))
Select this check box to achieve that matching is also possible within the
tolerances configured in MIRO.
Exclude Invoiced Lines
Select this check box to exclude the lines in the PO that have been marked
as Final Invoice when trying to find the PO line match. This narrows
down the search for the PO line determination.
The new matching process is used in logic module Line based processing /
enrichment / matching (PO)). To find the PO line number, the matching
process first tries to match all fields within step ID 1 (MENGE / NETPR / WRBTR) for
each index line against the PO and the GR. If no unique match is found, step ID
2 is processed. Now, the process takes also the field MAKTX into account. If again
no unique match is found, the process takes step ID 3 with field LFSNR into
account. So it is possible to define various steps with different detail levels to
find a unique match.
4. Maintain the fields you want to use for the PO line determination. Baseline
configuration uses the following fields for the matching:
Step ID
Define the sequence for the matching. The step ID is also the grouping
indicator for the fields to find a unique match.
Field Name
Enter the field used for matching.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 161
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
• Baseline:
/OPT/VIM_DBPF_MATCH_QUANTITY to convert quantity fields from
invoice unit into PO unit
• Baseline:
/OPT/VIM_DBPF_MATCH_TEXT to normalize the invoice material text to
match it against PO material text
Relation
Optional: Enter AND or OR.
The relation is taken into account if conditional matching is enabled. The
relation is used within one step ID.
8. Maintain the Determination Logic ID (PO Line Determination ID) you have
just configured.
9. Select the PO Line Determination Setting:
OK (default value)
Use OCR lines as basis without deletion of incomplete lines.
162 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
OCR lines are evaluated line by line. All lines based on reference documents
are read from the MIRO proposal. All OCR lines for which matches are
found in the MIRO proposal are overwritten with MIRO Amount/Quantity if
the OCR Amount/Quantity is missing.
• While matching, PO/PO item will be used as a key for Non GR IV case.
• PO/PO item or delivery note will be used as a key for GR IV case.
All lines that could not be matched with MIRO lines stay as they are. Finally,
the modified OCR lines are updated in the indexing item table.
OD
Use OCR lines as basis with deletion of incomplete lines.
OCR lines are evaluated line by line. All lines that are based on reference
documents are read from the MIRO proposal. All OCR lines for which
matches are found in the MIRO proposal are overwritten with MIRO Amount/
Quantity if the OCR Amount/Quantity is missing.
• While matching, PO/PO item will be used as a key for Non GR IV case.
• PO/PO item or delivery note will be used as a key for GR IV case.
All lines that could not be matched against MIRO lines and that are
incomplete are deleted. Finally, the modified OCR lines are updated in the
indexing item table.
MO
Use MIRO proposal as basis for indexing lines.
All lines that are based on reference documents are read from the MIRO
proposal. All MIRO lines for which matches are found in OCR line items are
overwritten with OCR Amount/Quantity.
• While matching, PO/PO item will be used as a key for Non GR IV case.
• PO/PO item or delivery note will be used as a key for GR IV case.
All lines that could not be matched against OCR lines stay unchanged.
Finally, the modified MIRO lines are updated in the indexing item table.
M2
Use MIRO proposal as basis, change only open lines.
This option has the same logic as MO but it prevents the data in non-open
lines of the MIRO proposal from being overwritten.
Background: Option MO results in overwriting the MIRO proposal lines that
are not open anymore because the data has been manually entered in the
DP document or received from ICC. Although this logic may be wanted in
some situations, VIM is now offering the alternative option M2.
PO (Default for PO Automation)
Use only MIRO proposal as indexing lines.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 163
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Important
Level Preference is used in conjunction with Ref Doc Preference. These two
values indicate the starting point for selecting reference documents, in order to
propose lines for invoicing: either purchase orders or delivery notes that
appear either at line item level or at header level.
Example: If Level Preference is L and Ref Doc Preference is PO, the system uses
purchase orders at line item level as the basis for getting proposals.
If no purchase order exists at line item level, the system uses delivery notes at line item
level.
If no documents exist at line level, the system uses the header level and starts with
purchase orders, there.
If no purchase order is supplied, the system uses delivery notes at header level.
Note: If the PO line determination does not find the PO line item number
while running the Business Rules, you will get an exception Unable to
determine PO line number (PO). You will also get this exception if the PO
line item number is blank or if it is invalid.
164 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
The tax code determination works whenever there is a supplied tax rate. See “Tax
calculation group” on page 165 for details.
In the Tax Code Determination group, the following options are available:
Note: Select the Tax Code from Vendor Master check box to retrieve the
tax code from Vendor Master in case any of the other options fails to
retrieve the tax code.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 165
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Note: This option only works if Auto Calculate Tax is not selected.
• Select the Calculate Tax on Net check box to define that G/L account
amounts are to be entered net.
• Clear the Calculate Tax on Net check box to define that G/L account
amounts are to be entered gross.
SAP ERP has two different tax flags that control the line amount and balance on
the Non PO parking screen and VIM Non PO parked approval:
In the past, VIM had only the auto-calc tax flag for Non PO DP approval. The
calculate-on-net-amount tax flag, known from Non PO processing, was not
available for DP documents. VIM interpreted the missing second flag as being
empty. If the auto-calc flag was selected, the gross amount was expected in the
Non PO DP line items.
The following combinations are possible with the two tax flags:
166 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
1. If a PO line exists, the system tries to retrieve the jurisdiction code from the PO
line item.
2. If the PO line item does not contain a jurisdiction code, the system checks for a
jurisdiction code based on the plant for the PO line item.
3. If still no jurisdiction code is found or if the invoice is a Non PO invoice, the
system picks up the jurisdiction code from the vendor master.
Note: If no jurisdiction code is found for tax procedures with jurisdiction code,
the tax code determination fails.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 167
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
• The PO line item tax code does not match the tax rate supplied.
• There are multiple tax codes belonging to the same tax rate supplied.
• A tax rate may match with one tax code but the tax code contains multiple rates.
• The tax jurisdiction code has not been determined, in case a tax procedure with
jurisdiction code is used.
For example, the United States have the TAXUSJ tax procedure with jurisdiction
code.
If the tax code determination fails, an Invalid Tax Info exception is raised in the
VIM Analytics report. In this case, the workflow is routed to the Tax Expert for
further actions.
1. The system reads the tax code from the PO line and checks if the tax rate
supplied by the external system matches uniquely. If the tax code exists in the
PO line item and no match is found, the tax code is considered to not determine
and the system stops checking further.
2. If the tax code does not exist in the PO line or the invoice is not a PO invoice, the
system proceeds as follows:
a. The system checks all tax codes of input tax type for the country and checks
if the tax rate supplied matches uniquely with only one tax code. If no match
is found, the system proceeds further.
b. The system selects the tax code from the OpenText table based on the tax
rate (Simple Maintenance). See “Tax Determination using OpenText Tax
Table (Simple maintenance)” on page 169.
c. If the above step does not result in a tax code match, the system retrieves the
tax code from Vendor Master if the Tax Code from Vendor Master check
box is selected in the DP configuration. The system checks if the vendor tax
code contains only one tax rate and if that tax rate matches with the tax rate
supplied. If it matches, the tax code is determined.
Note: If the tax procedure with tax jurisdiction is used, the jurisdiction code is
determined first and this code is used in conjunction with tax code to retrieve
the match. For details on the jurisdiction code determination, see “Tax
jurisdiction code determination” on page 167.
168 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
1. The system reads the tax code from the PO line and checks if the tax rate
supplied by the external system matches uniquely. If the tax code exists in the
PO line item and no match is found, the tax code is considered to not determine
and the system stops checking further.
2. If the tax code does not exist in the PO line or the invoice is not a PO invoice, the
system proceeds as follows:
a. The system selects the tax code from the OpenText tax table based on the tax
rate (Simple Maintenance).
2. For a given Country key and Vendor ranges, maintain Tax Rate versus
Tax Code.
For tax procedures with jurisdiction code, additionally use the
Jurisdiction code field to maintain Tax Rate versus Tax Code entries.
b. If the above step does not result in a tax code match, the system retrieves the
tax code from Vendor Master if the Tax Code from Vendor Master check
box is selected in the DP configuration. The system checks if the vendor tax
code contains only one tax rate and if that tax rate matches with the tax rate
supplied. If it matches, the tax code is determined.
Note: If the tax procedure with tax jurisdiction is used, the jurisdiction code is
determined first and this code is used in conjunction with tax code to retrieve
the match. For details on the jurisdiction code determination, see “Tax
jurisdiction code determination” on page 167.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 169
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
1. The system reads the tax code from the PO line and checks if the tax rate
supplied by the external system matches uniquely. If the tax code exists in the
PO line item and no match is found, the tax code is considered to not determine
and the system stops checking further.
2. If the tax code does not exist in the PO line or the invoice is not a PO invoice, the
system proceeds as follows:
a. The system checks all tax codes of input tax type for the country and checks
if the tax rate supplied matches uniquely with only one tax code. If no match
is found, the system proceeds further.
b. If the above step does not result in a tax code match, the system retrieves the
tax code from Vendor Master if the Tax Code from Vendor Master check
box is selected in the DP configuration. The system checks if the vendor tax
code contains only one tax rate and if that tax rate matches with the tax rate
supplied. If it matches, the tax code is determined.
Note: If the tax procedure with tax jurisdiction is used, the jurisdiction code is
determined first and this code is used in conjunction with tax code to retrieve
the match. For details on the jurisdiction code determination, see “Tax
jurisdiction code determination” on page 167.
*"--------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" REFERENCE(LOCATION) TYPE CHAR1 OPTIONAL
*" TABLES
*" INDEX_ITEM STRUCTURE /OPT/VIM_1ITEM
*" CHANGING
*" REFERENCE(INDEX_DATA) TYPE /OPT/VIM_1HEAD OPTIONAL
*"--------------------------------------------------------
170 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
VIM duplicate VIM extends the idea of standard duplicate checks available in SAP ERP or SAP S/
check 4HANA in FI and MM-IV modules. VIM allows flexible configuration of the checks
and offers many different options, which are described in this section.
Basic configura- In VIM, you implement duplicate check as a DP process type (exception) that is
tion active for DP document types and is executed on each run of business rules. The
configuration of duplicate check in VIM does not depend on the standard
configuration in SAP FI or MM-IV modules, including field selection or vendor
specific activation of the checks. Therefore, when implementing VIM, OpenText
recommends that you make the standard SAP FI and MM-IV duplicate check less
strict, disabling the corresponding messages in transactions OBA5 / OMRM for
background posting. This will let the documents post when invoice data is really the
same as that of an earlier posted invoice, and a DP document was explicitly declared
as non-duplicate.
Groups, steps, To implement VIM duplicate check, first decide on duplicate check groups. Each DP
and fields document type must have a duplicate check group assigned. Depending on the
duplicate check type maintained in the group, each group can have several steps of
fields checks, or it can have a function module that will be called by VIM. Steps are
an additional layer to control the check. On each step, several different combinations
of fields are checked to match against existing documents. In the most simple case, a
duplicate check group has only one step and list several fields to be checked. A
duplicate will be detected as soon as the first combination of fields defined by a step
deliver a match.
Baseline In a baseline configuration, VIM duplicate check checks both DP documents (not
posted or parked) and SAP documents (posted or parked). Checks of SAP
documents are optional but active in a baseline configuration.
In the baseline, the fields invoice date, invoice reference, and vendor number
are used to identify potential duplicates.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 171
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Note: This does not apply if the check type is set to Function module and a
custom function module is entered in the above mentioned field, assuming all
responsibility over the check.
Relevant For all combinations of checks, whether DP or SAP documents, only relevant
invoices invoices are checked. Obsolete, cancelled, or deleted documents, as well as those
confirmed as duplicate, are ignored.
Performance Take care when deciding on the fields to be used for duplicate checks with regards
to check performance. For most common field combinations, it is very likely that
database indexes will exist for VIM DP and SAP FI and MM tables. If you use less
common fields, it is advised to consider creating additional database indexes.
When VIM performs a duplicate check during the business rules run, the process
typically stops, opening a dialog box to decide the following:
Buttons The list of found documents whose data match the current document will be
displayed in the DP indexing screen. If invoice data is considered to be wrong and is
corrected, use Submit or Rerun business rules options to continue the processing.
The Non duplicate button lets the invoice proceed and post even if identical data is
detected. The button Declare as Duplicate ends the DP process.
9.1.13.2 Configuration
Configuring duplicate check comprises the following steps:
172 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
2. To add a duplicate check group, click the New entries button in the application
toolbar.
3. Define the new duplicate check group, using the following parameters:
FUNCTION <FUNCTION>.
IMPORTING
REFERENCE(I_INDEX_DATA) TYPE /OPT/VIM_1HEAD
EXPORTING
REFERENCE(O_DUPLICATES) TYPE /OPT/VIM_1HEAD_T
REFERENCE(O_DUPLICATES_EXT) TYPE /OPT/VIM_DUPL_H_T
TABLES
INDEX_ITEM STRUCTURE /OPT/VIM_1ITEM OPTIONAL
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 173
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
In multiple systems scenario, select this check box in any satellite system to
scan for duplicates through all DP documents of all systems in the
landscape, central as well as satellite systems.
The configuration data for Run Duplicate Check in Central System does
not have to be centralized. Local configuration can work without the need
of centralizing configuration data.
Note: The Aggregation Report batch job for the OTH_VMHEAD group
runs periodically and synchronizes the data of SAP IM documents to
the central system. The frequency of the batch job can be adjusted as
needed. Run Duplicate Check in Central System yields desired
results only after the batch job synchronized data with up to date
information. See “Scheduling the Aggregation Report” on page 821
for details.
In this step, you define the fields that need to be considered to define a duplicate
check. You can define multiple groups by maintaining them in the same step id.
2. Define duplicate check fields for the selected group, using the following
parameter:
174 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
Currency field In versions before VIM 7.5 SP2 (and VIM 7.0 SP6), the duplicate check automatically
included the Currency field when an amount was configured in the duplicate check
customizing.
Since VIM 7.5 SP2 (and VIM 7.0 SP6), this automatism is removed. The Currency
field is not automatically checked during duplicate check, you have to customize it
explicitly.
This change was done to avoid duplicate postings which occurred if a wrong or
empty currency was delivered, for example, during OCR recognition or other input
channels. In these cases, it could happen that a duplicate was not found due to the
wrong currency check.
The new default delivery is a duplicate check without currency. It can lead to a
higher amount of possible candidates for duplicate check. For upgrade customers,
OpenText recommends that you review the current duplicate check settings and
include the currency field (WAERS) to the customizing, if necessary.
The table /OPT/VT_DOC_DET stores the vendors that send PO based invoices. In
China it is possible to send PO based invoices without providing the PO numbers on
it. Using this table, you can configure certain vendors that do this practice, thereby
determining the DP document type correctly.
The system first checks the entries in table /OPT/VT_DOC_DET. If the vendor is found,
the DP document is considered as a PO based invoice. If no vendor entry is found,
the system checks for the existence of any PO numbers on the invoice.
You can maintain vendors per company code and also ranges of company code and
vendor combinations.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 175
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
3. In the document type determination procedure, add the step details with the
custom function module copied in Step 2. See “Document type determination
and characteristic customizing” on page 552.
Configuration The whole configuration for auto coding is integrated in the OpenText
aspects Configuration tree: Navigate to Vendor Invoice Management > Document
Processing Configuration > General Configuration > Automated Line Processing >
NPO Line Auto Coding.
1. Define dynamic determination for auto coding. In this step, you configure the
data loading for auto coding:
• With VIM 7.5 and later, you can use logic modules for auto coding.
Therefore, the Logic Module Process ID N_SPEC_001 must be mapped to the
Non PO based DP Document Types that are used. In VIM Baseline, this
mapping is available for DP Document Type NPO_75. For more information,
see “Mapping the processing” on page 193.
• Without logic modules: Integrate a process type for the document type to
execute auto coding in the DP processing.
176 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
Determination Type
Enter ACO (Auto Coding Configuration)
The determination type is defined in table /OPT/AT_DETTYPE. The type ACO
is delivered within the posted approval baseline configuration.
Note: You can perform some customizing on the production system,
where clients are normally set to “No changes allowed”. For this
customizing activity, no transport request is created.
As a prerequisite, you must select the Edit Allowed check box in the /
OPT/AT_DETTYPE table for the corresponding transaction codes.
Field Type
Available values are Header or Item. For the determination, only header
fields are relevant.
Field Name
Select the corresponding field of the /OPT/VIM_1HEAD or /OPT/VIM_1ITEM
table.
Sequence
Define the processing sequence of the determination.
Search Help Name
Configure the search help that will be used in the data determination
configuration.
Allow Ranges
Select this check box to allow ranges in the data determination
configuration. For item fields, ranges are not allowed.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 177
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
C
Skip the coding step (most common setting).
R
Skip the coding step and the requester step.
178 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
S
Skip the requester step. However, in case of rejection, the document is still
sent to the requester in the approval process.
To execute the auto coding, you must integrate a process type in the document
processing for the following reasons:
To integrate a process type, follow the customizing steps in “Defining the process
type” on page 230.
• No exception
• No user process options
• Autopost flag activated
• Bypass and simulate deactivated
• Process type determination sequence before Approval Required process option
• Sequence step function module /OPT/VIM_DETERMINE_PROC_LIB003
Process Type Definition (no other settings relevant); see also “Defining the process
type” on page 230:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 179
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Index Screen Options (no other settings relevant): see also “Configuring index screen
options” on page 148:
Process Type Determination Sequence (no other settings relevant); see also
“Defining the process type determination sequence” on page 145
180 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.1. Configuring DP document types
The corresponding Upload Coding button is added to the indexing screen. You can
configure the button to be shown or hidden. For more information about
configuring the button, see “Configuring index screen options” on page 148.
In this step, you configure the mapping between VIM fields and columns in the
Excel sheet for coding upload in the indexing screen.
Application Area
IDX_CODING is specific for coding upload in Indexing.
Table Name
/OPT/CIDX_ITEMS is also specific for coding upload in Indexing.
Note: The Application Area and Table Name fields are not editable.
They will be added to the entries during the configuration.
Fields
Field name in the indexing screen.
Active
Select this check box to specify that the field is considered in the uploading
process.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 181
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Sequence
Enter digits that indicate the sequence of Excel sheet columns that will be
mapped. This sequence number must be unique.
Example: The first column of the Excel sheet is mapped to the field with the lowest
sequence number. The second column of the Excel sheet is mapped to the field with
the second lowest sequence number, and so on.
With VIM 7.5 and above, the baseline document types PO_75, NPO_75 and DWN_75
will no longer get posted automatically. You must activate them to get posted
automatically.
To activate the automatic posting configuration, you must configure the document
type accordingly: In the process type definition, you must configure the baseline
function module /OPT/VIM_DETERMINE_AUTOPOST for the default process type or the
relevant process types for automatic posting.
Automatic posting might fail, for example, if the scenario is not supported or if the
necessary configuration has not been implemented. In this case, the DP document is
re-routed to the posting role, which is defined in the DP Document Type; see
Posting Role on page 142.
182 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.2. Configuring automatic posting
2. Configure the fields for automatic posting, using the following parameters:
Determination Type
The determination type for automatic posting is APO. It is defined in table /
OPT/AT_DETTYPE. The determination type APO is delivered in the baseline
configuration.
Field Type
You can configure Header or Item fields. For the determination, only
header fields are relevant.
Field Name
Select the corresponding field of table /OPT/VIM_1HEAD or /OPT/
VIM_1ITEM.
Sequence
Define the processing sequence of the determination.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 183
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Allow Ranges
Select this check box to allow configuring ranges in the data determination
configuration.
In this example, all documents of the company codes 1000 to 2000 and vendors
1000 to 9000 will be posted automatically.
184 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.2. Configuring automatic posting
• NPO - Cross company posting is not supported if the company codes have
different currencies.
• NPO - Specific currency translation for tax
• PO - Mixed Services and Goods in combination with multi account assignment
• NPO - Fields that are not supported by standard SAP BAPI: LNRZE (Head office
account number)
• PO - Fields that are not supported by standard SAP BAPI: LNRZE (Head office
account number), SECCO (Section Code)
• Distribution logic “by amount” is not supported if it is used in multiple account
assignment of a PO position.
Note: Starting with VIM 7.0 SP7 and VIM 7.5 SP3, this scenario is
supported.
• Posting of material lines for PO invoices is not supported in the same way as the
MIRO transaction does it.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 185
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
• Net vendor invoices, which typically have SAP document type KN, cannot be
posted with BDC ID 34. VIM does not calculate the discount and does not create
automatic lines for discount posting. OpenText recommends that you use BDC
ID 41 (batch input with the FB60 transaction) or BDC ID 42 (starting with VIM 7.0
SP7 and VIM 7.5 SP3) to post discounts correctly.
• When posting in background with BDC ID 41, pay attention to the way how line
item amounts in the DP document (gross or net) are entered. It must be in sync
with the gross or net setting flag of the user that is used to post the documents,
typically WF-BATCH.
• VIM provides a limited logic of assigning the default values to cost elements and
other invoice fields. VIM supports determining the tax jurisdiction code from
cost center, WBS element, network or activity, internal order, and vendor master.
Example: FI validation rules that you define for FB60 are not called by VIM and SAP
BAPIs to determine default field values.
Therefore, the current logic of assigning the default values may not satisfy your
implementation requirements. In this case, extend the logic with the provided
extension mechanisms or disable automatic posting of such invoices.
• Tax reporting date (VAT date) is posted if the corresponding field exists in the
SAP BAPI structure, which depends on your SAP SP level. Moreover, the
company code must be set up to use VAT date. However, if the company code is
set up for VAT date but the BAPI structure does not allow this, the background
posting stops. The invoice must be posted in dialog. For more information, see
“Maintaining the VAT date” on page 267.
Note: You can disable the VAT date and BAPI structure check by setting
the Z constant SKIP_VATDATE_CHECK.
• You might want to post an invoice with CPD vendor. If there is no IBAN field in
the BAPI structure, the posting will stop. To avoid this, set the Z constant
SKIP_BAPICHECK_SEPA.
To activate the Document Creation field on the indexing screen (AUTO_POST field),
see “Configuring the index header” on page 152.
Using the Document Creation field, the user can decide whether the document
should be posted automatically in background (A), online in dialog (M), or posted as
configured.
The decision of the user has the highest priority, that means, no matter what is
configured for the document type,
186 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.3. Processing 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 scheduled before the business
rules run. It might be useful to also trigger some logic modules at a later point of
time, for example if the user has entered data on the indexing screen and presses
Rerun Business Rules. A new business rule has been introduced that “informs” the
user that a logic module has added data to the document. Business rules are
intended to check document data whereas logic modules are intended to also change
document data.
Logic module customizing comprises modules, process IDs and the mapping of
document types to process IDs. The smallest unit is a logic module. It consists of a
class method (including an user exit) running its own checks and its own data
retrieval. The logic modules are clustered together to process IDs obtaining a certain
sequence. There are process IDs for PO documents and Non PO documents.
Some logic modules replace existing mapping function modules, others are
completely new.
“Best Practice” in VIM 7.5 means that OpenText delivers a set of logic modules/
process IDs that you can use by assigning them to your document types, according
to your processes.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 187
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
Document Processing Configuration > Document Type Configuration > Logic
Module Processing.
To configure the logic module processing, the following steps are necessary:
188 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.3. Processing logic modules
Module ID
Unique ID of the module
Class Name
Enter the processing class of the logic module. The class must have super
class /OPT/CL_D_LM_SUPER. Method /OPT/IF_D_BP_MODULE~PROCESSING
must be redefined to integrate own processing logic.
Process Type Activation
Select how the process type is activated. A process type or exception gets
triggered according to the activation type:
Activate on field change
The process type gets triggered by a field change. See “Configuring
field change for exception” on page 189.
Activate on custom logic
The process type gets triggered by custom logic implemented in Exit
FM.
Process Type
Enter the process type.
Process type 405 is a template for the one time business rule trigger. The
rule gets triggered when a field is changed within the module or by custom
logic (see Process Type Activation on page 189)
Note: If you use a process type here, locate it near the beginning of the
sequence of process types.
Exit FM
Enter the exit function for process type activation on custom logic. Use
template function /OPT/VIM_DBPF_TEMPLATE_PROC_TR to create your own
function module.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 189
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
3. In the Field Change for Exception screen, configure the fields, using the
following parameters:
Field Type
Select Header or Item.
Field Name
Enter the name of the field in the index data table. The table is either /OPT/
VIM_1HEAD or /OPT/VIM_1ITEM.
1. In the Module Definition Overview screen, select a Module ID that has Process
Type Activation Activate on field change, and double-click Messages for
Exception in the Dialog Structure.
2. In the Messages for Exception screen, configure the messages, using the
following parameters:
Application Area
Enter the message class of the message.
MsgNo
Enter the message number.
Fld.Change
Select this check box to show a message for each field that gets changed
with relevant information:
/OPT/VIM_BPF - 001
Message for item field changes
/OPT/VIM_BPF - 002
Message for header field change
Field Type
Select if the message is shown for Header or Item fields.
190 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.3. Processing logic modules
• a processing sequence
• different processing for PO / NPO document types
• easier configuration: basic enrichment is separate from special handling
(additional costs)
2. In the Processing Definition screen, define the processing, using the following
parameters:
Process ID
Enter the unique Process ID of the processing steps.
Description
Enter the description of the processing steps.
2. In the Module Processing Steps screen, assign the logic modules to the
processing definition, using the following parameters:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 191
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Counter
Enter the sequence of the modules.
Module ID
Enter the unique ID of the module (see “Defining logic modules”
on page 188).
Active
Select this check box to activate each module in the process.
Process Mode
Define when to trigger the module: at Process Start, at Rerun Rules
(rerun business rules), or at both times (Start + Rerun).
Note: Be careful when you use the rerun option. Many of the
enrichments only make sense when they are done at the start of
processing. During rerun, they might overwrite values entered by the
user.
Relation
Select the relation between the modules: AND or OR
You can define if the module has run successfully or not within the
processing class (see “Defining logic modules” on page 188).
• If you define an AND relation between two modules and the first module
does not run successfully, the next modules will not be processed at all.
• If you define an OR relation, the next modules in the OR relation will be
skipped if the previous module ran successfully.
Notes
192 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.3. Processing logic modules
Counter
Define the sequence of processing.
Channel ID
Only relevant for activation type Activate by Constant.
Enter the input channel that is used for the process definition. If it is empty,
all channels are valid.
DP Document Type
Only relevant for activation type Activate by Constant.
Enter the document type that is used for the process definition. If it is
empty, all document types are valid.
Note: When upgrading from older VIM releases, you might like to
have some document types using logic modules and some others run
without logic modules. In this case, you need to remove the standard
entries in the processing mapping with empty document types. This
will prevent the logic modules to be called for all documents. The
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 193
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Important
If there are entries in the logic module processing mapping that have activation
type Activate by Determination, you must define the relevant fields and the
data. Otherwise, you can skip sections “Configuring logic module processing
determination - fields” on page 194 and “Configuring logic module processing
determination - data” on page 196.
This section describes the configuration of fields that are used for the determination.
The process ID (PROC_ID) field (see screenshot below) is required to assign the
correct process.
194 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.3. Processing logic modules
2. In the Maintenance View for Logic Module Processing, configure fields for
logic module processing, using the following parameters:
Determination Type
BPF (mandatory)
The determination type for Best Practice Framework Configuration is
BPF. It is defined in table /OPT/AT_DETTYPE. The determination type BPF is
delivered in the baseline configuration.
Note: You can perform some customizing on the production system,
where clients are normally set to “No changes allowed”. For this
customizing activity, no transport request is created.
As a prerequisite, you must select the Edit Allowed check box in the /
OPT/AT_DETTYPE table for the corresponding transaction codes.
Field Type
You can configure Header or Item fields. For the determination, only
header fields are relevant.
Field Name
Select the corresponding field of table /OPT/VIM_1HEAD.
Sequence
Define the processing sequence of the determination.
Search Help Name
You can configure a search help, which will be used in the data
determination configuration.
Allow Ranges
Select this check box to allow configuring ranges in the data determination
configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 195
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Important
This is only relevant if there are entries in the logic module processing
mapping that have activation type Activate by Determination. Otherwise,
you can skip sections “Configuring logic module processing determination -
fields” on page 194 and “Configuring logic module processing determination -
data” on page 196.
In this example, the Logic Module Process ID N_SPEC_001 is used for all
documents of the company code 7000 and vendors 1000 to 3000 + for the
company code 7500 and vendors 4000 to 7000.
196 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.4. Business Rule Framework
With VIM 7.5, the settings are more refined with respect to check status, check
conditions, vendor grouping, and assignment.
The new check status does not only mean that a business rule run is either on or off.
The check status also considers counter based, random, periodic, or once as possible
triggers for a business rule run.
The new check condition definition allows you to limit business rule runs to either
exceeding a minimum amount or receiving a flag from a custom function.
• Random
The business rule might or might not run.
• Condition based (function module)
The business rule runs only if a custom function module delivers a success flag.
• Counter based
If the counter is reached, the business rule runs. The counter can be customized.
• Blind
The business rule runs without stopping in case of an exception.
• Off
The business rule does not run (inactive).
• Check
The business rule runs (active).
• Periodic
The business rule runs every x month for a vendor. The x can be customized.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 197
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
• Amount based
A minimum amount is configured. If the document exceeds this amount, the
business rule is run.
• Function module based
A custom function can be implemented. If it returns a success flag, the business
rule is run.
198 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.4. Business Rule Framework
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
Document Processing Configuration > Process Configuration > Business Rule
Framework (BRF).
• Defining check IDs if you want to use amount limits or custom function modules
• Defining which check types are valid for which process types and which
documents (document type, company code, vendor group)
Vendor Group
Unique name for the vendor group (black, grey, white)
Description
Description of the vendor group
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 199
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
200 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.4. Business Rule Framework
• RANDOM
• CONDITION
• COUNT
• BLIND
• OFF
• CHECK
• PERIODIC
• ONCE
For more information, see “Check type / check status” on page 197.
2. In the BRF - Check Type ID Overview screen, fill the check type descriptions
(especially in additional languages), using the following parameters:
• Chck. Type ID
• Check Type name
• Check Type Description
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 201
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Check ID
Enter the unique ID of the check condition.
Description
Enter the check condition description.
Check Base
Select which check base you want to use. Possible options:
Amount based
If you select this option, you must enter values in the following fields:
Amount, Currency, Amount Base, and Conversion Date.
Function Module
If you select this option, you must enter a custom check function in the
Check Function field.
Check Function
Enter the exit function for the function module check base. You can use
the /OPT/VIM_DCMP_EX_CONDITION function module as a template.
Amount
Enter a minimum amount for a business rule run.
Currency
Enter the currency for the minimum amount.
Amount Base
Select Gross amount or Net amount.
Conversion Date
Define a currency conversion date. You can select one of the following
options:
Conversion Function
Optionally, enter a custom function for the currency conversion. If you
leave this field empty, the SAP function module
CONVERT_TO_LOCAL_CURRENCY is used.
202 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.4. Business Rule Framework
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 203
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Counter X
If you use Counter Based check type: Enter a numeric value for the counter.
When the counter is reached, the business rule runs.
COMPL_RANDOM_MIN
Valid for check type RANDOM. You can increase or decrease the probability of
exceeding the minimum random value.
This central value is used as a lower limit for the Business Rule Framework. If
check type RANDOM is active for a business rule (process type), the SAP random
number generator is called. It returns a value between 0 and 100. If you want
business rules to run very rarely, you have to enter a high value (for example
90). If you want them to run more often you have to enter a low value (for
example 10).
CUSTOM_FM_COMPLIANCE
You can create a customer specific function module for the BRF matching. Use
template /OPT/VIM_DCMP_EX_MATCH.
COMPL_ALLOW_M_BYPASS
The DP indexing simulation screen shows activate/bypass icons that are set by
the BRF or manually. If a BRF check type exists and this Z constant is empty, the
icon cannot be changed. If no check type exists or this Z constant is set to X,
manual changes are possible.
COMPL_HIDE_CHECKTYPE
If this Z constant is set to X, the DP indexing simulation screen does not show
the check type column. If it is empty, it shows the column.
• to show the processing steps for a group of documents that is defined by:
– DP document type
– Company Code
– Vendor
• to show the processing steps of a DP document.
204 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.4. Business Rule Framework
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 205
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
• DP Document Type
• Characteristic (country)
• Vendor Group
Step data
Step ID
Technical information: processing sequence
Process Type
Technical information: process type ID
Business Rule
Name of the process type (business rule)
206 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.4. Business Rule Framework
Activate/Bypass
A business rule can take one of the following statuses:
<empty>
Active (no manual bypass possible)
Active
Inactive / bypassed
Check Type
If a check type has been assigned in the BRF schemata assignment, it is
shown.
Initial Role
Role that is assigned to the business rule.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 207
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Header data
• Document ID
• DP Document Type
• Characteristics (country)
• Invoice Category
• Vendor Group
208 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.5. Customizing profiles for the indexing screen
Step data is identical to the group result list; see Step data on page 206.
4. To return to the selection screen, click .
You can assign a specific user profile, using the user parameter /OPT/
CIDX_CUST_PROF.
2. In the Profiles Details screen, define the profile, using the following
parameters:
Customizing profile
Unique ID of the profile
Customizing Profile Description
Description of the profile
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 209
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
The general default profile (DEFAULT) included in the baseline delivery assumes a
minimum screen resolution of 1600 x 900 for all UI related settings.
2. Define the profile settings using the following parameters. The corresponding
settings are called during runtime.
Customizing Profile
Unique ID of the profile
Application Class
Enter the application class.
The complete logic of the indexing screen is combined in the application
class of the indexing screen. All relevant attributes and methods of the
global application class are delivered in a baseline indexing screen
application. You can enhance the class by redefining components of the
class within a custom class, which can be maintained instead of the baseline
class.
Default value: /OPT/CL_C_IDX_APPLICATION
UI Class
Enter the UI class.
210 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.5. Customizing profiles for the indexing screen
All relevant screen logic is combined within the UI class of the indexing
screen. Like for the application class, the baseline class delivers the
complete screen logic, which you can redefine.
Default value: /OPT/CL_C_IDX_UI_CONTROLLER
Process Options
Enter the process options class.
This class includes the process options to be executed within the indexing
screen.
Default value: /OPT/CL_C_IDX_PROCESS_OPTIONS
User Class
Enter the user class.
This class includes necessary user settings and configuration of the indexing
screen.
Default value: /OPT/CL_C_IDX_USER
The plug-in options of the profile are used when the user calls the indexing
screen the first time. Changes done during screen processing are stored when
the indexing screen is left and the screen is opened in the same way the next
time. For details about plug-ins, see “Customizing plug-in controls for end-user
screens“ on page 615.
Plug-In Type
Enter the plug-in type that is used within the indexing screen by default.
Default value: VIM_IDX
Plug-In ID
Enter the default plug-in ID that is used in the indexing screen.
Default value: 10 (Image plug-in)
Plug-In Side
Select the default plug-in side where the plug-in is displayed on the screen.
Default value: Right justified
Cont. Pane % Vt.
Content pane size ratio vertical in %: Enter the default plug-in size in
percent of the indexing screen, a % value between 5 and 90.
Default value: 42
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 211
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Alternatively, navigate to OpenText Vendor Invoice Management > SAP menu >
Roles > Role Maintenance.
To create a new role, follow the process described in “Defining roles” on page 36,
with product code 005.
212 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.7. Configuring DP process options
Option Id
Enter a 4 digit number identifying the process option.
Option Button Text
Enter the text that appears on the button for this option in the users’
dashboard.
Option Button Icon
Enter the icon that appears on the button for this option in the users’
dashboard. If you maintain an icon, the Option Button Text is not used.
Option Text
Enter a description that describes the option in detail.
Option Type
Select the type of option:
BDC Action
A BDC ID is executed if the user chooses this option.
Note: If you select BDC Action, you must maintain the BDC
Configuration Id.
Referral
User can refer the work item to a target role for further processing.
Note: If the Override Res. Actor check box is selected, the user
has an option to send the work item to users other than the ones
determined by the system for the target role.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 213
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Class Method
The system calls the class method that you define in the Option Class
Name field.
Note: If you select Class Method, you must maintain the Option
Class Name field.
Call Transaction
The system calls the transaction that is defined in the Transaction Code
field.
Workflow Task
The system calls a (sub) workflow or task before continuing the process.
Select Workflow Task to define any custom post processing steps for a
given option.
Confirm Execute
Select this check box to let the system get a confirmation from the user to
execute the option.
Confirm Completion
Select this check box to let the system get a confirmation from the user that
the option is successfully executed.
214 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.7. Configuring DP process options
Comments Required
Select this check box if a comment is required for the action executed. The
comment will be shown in the process log.
Note: For referring process options, this setting is ignored if the Z
constant REFER_COM_REQ (product code 005) is set.
Document Status
Select the status set for the document if the option is executed successfully.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 215
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Description
Enter a meaningful description for the action.
Transaction Code
Enter the related SAP transaction code.
Data Area
Enter Indexing for DP
Processing Mode
Select settings for processing:
Display errors
BDC mode E: Stops at Error screen.
Background processing
BDC Mode N: Use this option for background processes.
216 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.7. Configuring DP process options
Update
Select the Update mode to call transaction. Possible values: Local,
Synchronous, or Asynchronous.
CATT Mode
Select the CATT mode. The following values are possible:
No CATT
’ ’ No CATT active
Default Size
Select this check box to use the default window size.
Continue after Commit
Select this check box to specify that the transaction does not end at COMMIT
WORK.
Not a BI Session
Select this check box to specify no batch input mode, that is, SY-BINPT =
SPACE.
End: No BI
Select this check box to specify no batch input mode after the end of BDC
data.
Custom BDC Function
Maintain the custom BDC function, and the system will ignore all settings
in the BDC Definition Details screen. Figure 9-2 on page 218 shows the
function module interface.
Exceptions
• You must specify the processing mode that you are using in your
customer function.
• You must specify the transaction FV60 as Transaction code, if you are
calling a transaction to park Non PO invoices in your custom module,
and if you want the parking workflow for the Non PO invoices dialog to
be triggered.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 217
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
To define parameters:
SPA/GPA
Parameter Id (Check definition with SAP Documentation)
218 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.7. Configuring DP process options
Function module
Figure 9-3 on page 219 shows example and interface.
As the data head is structure, it is not specified. Use field symbol to pass
it on to the respective structure.
You can use the function module parameter ID also as exit before
calling BDC transaction.
Create a dummy parameter ID and use the custom function module for
any processing that needs to be done before BDC call.
Application Variable
Application Variable is used to reference index field values.
System Field
System Field is used to reference system fields.
Default Value
Default Value is used to set default values as parameters.
Class Method
Currently not implemented.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 219
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Index ID
Sequence step number for the BDC data table
Program
Enter the name of the program.
Screen number
Enter the screen number.
Start Screen
Select the check box to indicate a new screen.
Line Number for Item
Enter the line number for the table control line item. Normally blank.
BDC Field Name
Enter the BDC field name.
220 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.7. Configuring DP process options
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 221
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Application Variable
The value of the table field from table /opt/vim_1head can be used in
the application variable. If you choose Application Variable, enter
the field name from table /opt/vim_1head into the BDC field value
table.
Class Method
Currently not implemented.
BDC Extension Function Module
You can use this option to add a screen field to BDC Data structure
based on special logic, for example country specific screen fields. When
you use this option, enter the following values and leave the remaining
fields empty. See the following screenshot.
222 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.7. Configuring DP process options
Program
EXTENSION
If success messages are maintained, the system checks for the messages at the end of
the transaction, and if they match any other messages returned from BDC, the
system treats it as transaction completed.
Index
Sequential line item number
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 223
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Application Area
Select the message class.
Message ID
Select the message number.
The success message is not required for all transactions. In a few cases, like MIRO and
FV60 transactions, the transaction itself exports a Process_key-complete flag to
memory ID name as work item ID, and then the system also treats the transaction as
completed.
The following is the example code for exporting a document creation flag in case of
MIRO and FV60 transactions.
CHECK sy-subrc EQ 0.
l_prockey-bus_objtype = 'BUS2081'.
l_prockey-bus_objkey = l_rbkp+3(14).
l_prockey-complete = 'X'.
224 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.7. Configuring DP process options
3. Replace the existing BAPI with custom BAPI compatible to interface /OPT/
VIM_52_BAPI_DOCLINES_PO.
5. Replace the existing BAPI with custom BAPI compatible to interface /OPT/
VIM_52_BAPI_PO_PARK.
You might not want to entirely overwrite the BAPIs with custom BAPIs as described
above. The other way to allow some custom modifications is to use a custom plug-in
function module.
2. Double-click CUSTOM_FM_PLUGIN.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 225
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
This Z constant allows you to plug in your own function module, in order to
enhance the functionality lines for posting or parking via BAPI. This plug-in
custom function is called within /OPT/VIM_52_BAPI_DOCLINES_PO and /OPT/
VIM_52_BAPI_PO_PARK, just before creating the SAP documents.
EXPORTING
index_header = index_header
TABLES
index_item = index_item
itemdata = lt_bitem
accountingdata = lt_accountingdata
glaccountdata = lt_glaccountdata
materialdata = lt_materialdata
taxdata = l_tax
withtaxdata = lt_withtax "Witholding Tax
vendoritemsplitdata = lt_vendoritemsplit
CHANGING
headerdata = l_bhead
addressdata = ls_addressdata.
226 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.8. Invoice processing plug-ins
In this step, you need to verify that the BAdI used for PO based invoice processing is
active. This is important to successfully terminate the document processing
workflow and start PO parked/blocked workflow (if required).
Usage:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 227
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Make sure that only one implementation for this BAdI is called. Therefore use the
SE19 transaction to check that the runtime behavior of BAdI /OPT/
VIM_ENH_SPOT_MIRO is Implementation is not called. To prevent activation of
this second BAdi, leave the Planned Status for Business Function /OPT/
VIM_SFW_MIRO empty (in the SFW5 transaction).
2. Use the SFW5 transaction to set the planned status of business function /OPT/
VIM_SFW_MIRO to “active” and activate the change.
You can check if the activation was successful in SFW5 (bulb is lit) or in
SFW_BROWSER (“Switch position” of business function /OPT/VIM_SFW_MIRO is
green.)
3. Use the SE19 transaction to make sure that runtime behavior of BadI /OPT/
VIM_ENH_SPOT_MIRO is Implementation is called.
228 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.8. Invoice processing plug-ins
New BTE processing for document parking – The parked processing within BTE
2213 has been enhanced and supports the following scenarios:
• NPO parking using enjoy transactions: uses BTE 2213 and BTE 1140
• NPO parking using classic transactions: uses BTE 1020 and BTE 2213
• NPO BDC scenario: uses BTE 2213 and modification in function module /OPT/
VIM_CALL_IDX_TRANSACTION
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 229
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
230 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.9. Configuring the process type
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 231
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
To rerun process types correctly in background, you must plan a batch job for a
report; see section 5.1 “Scheduling batch jobs for workflows” in OpenText Vendor
Invoice Management for SAP Solutions - Administration Guide (VIM070500-08-
AGD). You can also rerun the waiting process types in dialog using the /OPT/
DR_BR_WAIT report or the /OPT/VIM_RULERUN transaction. See also “Rerunning
waiting process types“ on page 957.
Wait / Rerun
With this option, it is possible to send any exception of a business rule into a
wait state. Depending on the selected option, it is possible or not possible to
process the work item:
Background processing only
The work item is sent to the background user (WF-BATCH).
Workitem processing possible
The work item is in a wait state but it can be processed by the user
specified in Wait Role.
Interval (hours)
The interval defines the time in hours after which the business rule is
skipped or placed in the initial actor's inbox if no other action happened.
You can control this using the exclusive indicator; see “Defining the process
type determination sequence” on page 145). The rule will be skipped if the
exclusive indicator is not set, or the process will stop and the initial actor
has to resolve the process type manually.
Wait Role
Only necessary if the Wait / Rerun option is set to Workitem processing
possible. The specified role gets the work item that is sent into the wait
state. The specified role is able to process the work item.
Workflow Settings
Workflow Type
Select Opentext Approval Workflow from the drop down list to start the
DP based approval workflow. With Opentext Approval Workflow selected,
it is possible to select or clear the Auto Start check box, as the case may be.
Select External Workflow from the drop down list to run any external
workflow (based on SAP technology) outside SAP IM workflows as a part
of any business rule. With External Workflow selected, the Auto Start
option is always enabled.
232 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.9. Configuring the process type
Select SRM System Integration from the drop down list for SRM scenarios
or any other external systems where an email will be sent and the workflow
will be in wait status. See “SRM integration“ on page 889.
Auto Start
Relevant for DP based approval workflow. If the process type
corresponding to the approval workflow is determined, the system checks
whether the Auto Start check box is enabled. If yes, the system starts the
approval workflow if it is enabled. If Auto Start is not enabled, processing
continues with the initial actor assigned to the current process type. The
initial actor will manually start the approval workflow.
Task
Enter the workflow template to be triggered. The workflow template
container can be of any interface as the binding is controlled by a custom
binding function module.
Binding Function
Enter the Workflow Binding function module.
It must be implemented in the system where the SAP IM workflow is
running, to pass appropriate data to the external workflow. The function
module should have an interface as /OPT/VIM_DASHBOARD_BINDING. Inside
the custom function, in this case, implement Dataflow = E (Inward
Binding). You can access the complete container elements of the DP
workflow from the table parameter CALLING_CONTAINER. Regarding how
actual to implement the binding function, you can refer /OPT/
VIM_DASHBOARD_BINDING.
As a simple implementation, element INDEXDOCUMENT can be accessed from
the container CALLING_CONTAINER. DP (Document Processing number) can
be retrieved and other indexing information can be extracted and passed to
the elements of the CALLED_CONTAINER container, which is the container of
the external workflow. The external workflow must also raise the event /
OPT/V1001.PSS_COMPLETED at the end in the system where the SAP IM
workflow runs so that the SAP IM workflow proceeds further.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 233
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
SWC_CONTAINER_TO_RUNTIME called_container.
SWC_CONTAINER_TO_PERSISTENT called_container.
ENDIF.
ENDFUNCTION.
Logical System
Enter the name of the system where the external workflow is supposed to
run. The external workflow should be based on SAP technology.
SRM Settings
Max Retry Counter, Retry Time (Minutes), Mail Config ID, Receiver Mail
Function, Send Mail Function
These fields are only relevant for the SRM integration. See “Missing goods
receipt scenario” on page 894.
234 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.9. Configuring the process type
1. In the Process Type Definition Overview screen, select a process type and
double-click User Process Option in the navigation pane.
Option Id
Process option identifier
Description
Description of the option
From Actor
Select the source role that gets the work item.
To Actor
Select the target role that receives the work item if the action is performed.
This is only available if the option is a referral.
Check FM
Enter a check function module to restrict the option for a role. You find the
interface for the check function module using /OPT/
VIM_BL_CHECK_FM_2012.
Sequence
Optional setting: Enter the sequence of the process options shown in the
dashboard.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 235
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Old VIM With VIM 7.0 and lower, the business rule Unable to Determine PO Line number
approach was used to derive PO item numbers for the indexing lines. As an extension for the
feature of line determination for invoicing, VIM provides a business rule Manual
Check Needed for indexing lines. The former rule Unable to Determine PO Line
number stays valid as it complements the line determination.
New VIM In VIM 7.5 and higher, the old approach is replaced with a combination of a logic
approach module and a business rule.
OCR lines
• If no OCR lines are supplied, the entire proposal that is based on reference
documents is used to form indexing lines, based either on PO orders in the
documents or on Delivery Notes, but not on both.
• If OCR lines are supplied, and all lines’ mandatory fields are filled, no business
exception occurs.
• If OCR lines are supplied, but some lines have empty mandatory fields, these
lines are considered as incomplete.
Incomplete OCR lines are checked if certain fields are filled. According to the
configuration, either the lines proposed by the MIRO transaction or the OCR
236 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.10. Configuring indexing line matching
supplied lines can then form the basis for indexing lines. See “Setting up the
derivation infrastructure” on page 237.
Business exception
• PO Number
• PO Item
• Quantity
• Amount
• UOM
Once the system has determined that indexing lines are incomplete, the system
derives the missing mandatory fields based on the configuration described in
“Setting up the derivation infrastructure” on page 237.
The old derivation infrastructure using business rules is still working but you
should not use it any more.
Process Type 110, business rule Manual Check Needed for Indexing Lines, used in
VIM versions prior to 7.5, is replaced with process type 113, business rule Manual
Check Needed / Missing Data for Indexing Lines (PO) with VIM 7.5 and higher.
This business rule has been created for PO data checking.
2. Process definition and related logic module must be available and active.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 237
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
3. The process definition must be mapped and activated for the related document
type.
238 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.10. Configuring indexing line matching
2. At DP Document Type level, configure process type 113 Manual Check Needed
/ Missing Data for Indexing Lines (PO).
3. Open the Sequence Steps screen for process type 113. See also “Defining
sequence steps” on page 147.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 239
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
240 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.10. Configuring indexing line matching
2. Double-click BDC_POSTING_ONLINE.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 241
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Process option BDC Configuration Id 200 is a special BDC Configuration Id. It, therefore, needs to
be attached to a user process option, which in turn is called from the DP Dashboard.
Either create a new process option or change the existing process option for PO
invoice posting, as shown in the following procedure.
User process You need to configure the user process option 2009 Post PO Invoice for process
option type 110 Manual Check Needed for Indexing Lines.
242 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.10. Configuring indexing line matching
2. In the Process Type Definition Overview screen, select process type 110 Manual
Check Needed for Indexing Lines and double-click User Process Option in
the navigation pane. See also “Defining user process options” on page 235.
3. Maintain process option 2009 Post PO Invoice for appropriate roles under
process type 110, as shown in the screenshot.
4. For VIM version 7.5, repeat this procedure for process type 113.
/OPT/VIM_BUILD_REFERENCE_DOCS
This function is used for passing the reference documents (include LMR1MF3S).
Call this function inside the subroutine ZUORDNUNGSKRITERIEN_AUFBAUEN.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 243
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
/OPT/VIM_CHANGE_PROPOSAL_MIRO
This function is used to manipulate the lines from proposal (include LMR1MF3U).
Call this function inside the subroutine ZUORDNUNG_DURCHFUEHREN.
.
***********BEGIN OF ADDITIONAL MIRO CHECKS*******************
if VIM = 'X'.
loop at ydrseg.
244 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.11. Additional process configurations
space
CHANGING ydrseg.
modify ydrseg.
endloop.
endif.
***********END OF ADDITIONAL MIRO CHECKS***********************
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 245
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Code
Rescan reason code.
Description
Description of the rescan reason.
Comm Required
If you select this check box, the user must maintain the comments to
proceed.
Code
Obsolete reason code
Description
Description of the obsolete reason
Comm Required
If you select this check box, the user must maintain the comments to
proceed.
Comm visible
Comments visible externally. If you select this check box, comments entered
when obsoleting a document may be sent outside your organization. For
246 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.11. Additional process configurations
Scan Location
Scan location for archiving
Description
Scan location description
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
Document Processing Configuration > Process Configuration > Maintain
Document Priorities.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 247
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Priority
Enter the priority number.
Description
Enter a description of the priority.
248 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.11. Additional process configurations
Column Header
Enter text to appear as column header in user's inbox.
Dynamic Col. Type
Define how the dynamic column value is determined. The following values
are possible:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 249
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Table Field
Data will be populated from the /OPT/VIM_1HEAD table.
Container Expression
Data will be populated from container data from task TS9578003.
Custom Function
Data is derived using a custom function module. A sample interface can
be found from function module /OPT/BL_IF_SET_DYNAMIC_COLUMN.
Note: The change of the settings for dynamic columns in the DP workflow
results in automatic entry of the workflow container elements DYNAMICCOLUMNx
for the task TS00275278 in the table SWLVCUSTOM. All six columns are plain text
fields, and this can result into incorrect sorting for values containing numbers,
for example Invoice Amount. If you need VIM users to see and sort work items
using the Invoice Amount field, you must maintain one dynamic column
directly in the table SWLVCUSTOM (transaction SM30) with the container element
expression &_WI_OBJECT_ID.GROSSAMOUNT& (instead of automatically entered
&DYNAMICCOLUMNx&).
Important
Take care when you change the global configuration parameters. Changes can
affect the functionality of the process.
GR_CHECK_EXIT
Usage
This constant defines the function that is called to check if the Goods
Receipt (GR) for the PO is already done.
This constant is only applicable for Brazil.
Default value
/OPT/VIM_BL_CHECK_GR_EXIT
250 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.12. Configuring global parameters
GR_MOVEMENT_TYPE
Usage
This constant defines the movement type to be used when posting the
goods receipt (GR) document in background. It can either be a fixed
value or a function module name.
This constant is only applicable for Brazil.
Default value
For a fixed value, just mention the movement type in the constant
value, for example: 101.
For a function module, use the format FM: <function_name>.
GR_POST_BAPI_EXIT
Usage
This user exit bases on a function module. The function module defined
in this constant is called by the standard program before the SAP BAPI
is called while posting the goods receipt (GR). You can use this user exit
to change values being passed to the BAPI.
This constant is only applicable for Brazil.
Default value
None
The interface of the custom function module must be the same as /OPT/
DPPO_GR_BAPI_POST_EXIT.
DP_NPO_POSTING_EXIT
Usage
This user exit bases on a function module. The function module is called
before calling the non PO invoice posting BAPI
BAPI_ACC_DOCUMENT_POST in function module /OPT/
DNONPO_INVOICE_BAPI. You can use this user exit to modify the
baseline data in BAPI structures.
This constant is applicable for all countries.
Default value
None
The interface of the custom function module must be the same as /OPT/
DNONPO_INVOICE_BAPI_EXIT.
DP_PO_PROPOSAL_EXIT
Usage
This user exit is called at the end of the proposal function. You can
modify the proposals and create additional error messages.
Note: Under certain conditions, for example with closed posting
periods, the user exit is not called.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 251
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Default value
None
APP_DOCU_URL
Usage
The custom help URL for the DP dashboard. You can provide custom
help for users to look up processing steps they need to take when they
are processing the DP dashboard.
Default value
www.opentext.com
IMG_DOCU_URL
Usage
The custom help URL for OpenText IMG. Do not change this constant.
Default value
www.opentext.com
MAIN_WF_TEMPLATE
Usage
The default workflow template that will be triggered for DP. Do not
change this value.
Default value
WS00275269
NUMBER_RANGE_OBJECT
Usage
The default number range object for DP is /OPT/DOCID. If you want to
define a custom number range object for document number ranges,
define the value of the number range object here.
Default value
None
Note: If you change this value, you will have to maintain the number
ranges for the documents separately. The OpenText delivered /OPT/
VIM_1CX6 transaction will not work in this case for maintaining
number ranges.
PREPROCESS_EXIT_FM
Usage
A custom function module can be used as a value for this constant to
change the document values (Index Data etc.) before the workflow
starts.
Default value
None
252 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.12. Configuring global parameters
Interface
CALL FUNCTION <CONSTANT>
CHANGING
INDEXER = LCL_INDEXER TYPE REF TO /OPT/CL_VIM_DOC_PROCESSOR
REMINDER_USER_EXIT
Usage
This configuration value is used to maintain a custom function allowing
to format e-mail content when sending reminders to users holding
work items.
Default value
/OPT/VIM_NOTIF_USER_EXIT_TEMP
Interface
REM_MAIL_DOCTYPE
Usage
This configuration value determines the global format of email sent
from Reminder Notification, Approval Notification and SRM
Notification.
The notification emails can be sent in HTML format with readable
formatting and invoice data presented in the form of HTML tables. To
enable this functionality, you must set the constant 005 /
REM_MAIL_DOCTYPE to HTM. In the /OPT/VIM_8CX50 transaction, you
must configure the Email Type to be Internet Email.
Default value
RAW
REM_MAIL_FORMAT_FM
Usage
This configuration value determines the exit function module where the
customer can manipulate the email content before sending it out.
Default value
empty
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 253
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
SERVICE_ENTRY_BSART (obsolete)
Usage
The service entry document type. This configuration value was
formerly used in business rule 154 Service entry required.
SERVICE_ENTRY_BSTYP (obsolete)
Usage
Purchase document category for service entry. This configuration value
was formerly used in business rule 154 Service entry required.
WI_TEXT_FM
Usage
This configuration value is used to maintain a custom function that
allows formatting the work item text.
Prerequisite
Knowledge about work item data
Default value
/OPT/BL_IF_DETERMINE_WI_TEXT
Interface
DP_DASHBOARD_TASKID
Usage
This configuration value is used to determine the dashboard task in DP.
The task should be compatible to task TS00275257.
Prerequisite
Knowledge about workflow tasks
Default value
TS00275257
Note: Do not change this value as a change affects the behavior of the
application.
DUP_CHECK_DELIMIT
Usage
This configuration value is used to determine which characters in the
document reference number are considered as delimiter to determine a
document as a duplicate.
254 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.12. Configuring global parameters
Default value
/-
Example
If a document with reference number REF-1 should be considered as a
duplicate for REF, the delimiter that should be maintained is -.
LIST_WF_STATUSES
Usage
This configuration value is used to determine at which document
statuses the PO parked workflow should be triggered. The document
status in question is the SAP document status.
Possible values:
A: Parked workflow triggered by MIR7 function Save parked document
B: Parked workflow triggered by MIR7 function Save as completed
AB: Parked workflow triggered by MIR7 function Save as completed
and Save parked document
Default value
A
Usage
This configuration value is used to determine for which SAP document
types the PO/Non PO workflow is triggered. This eliminates the
triggering of the workflow for unwanted document types. Separate the
values by comma.
Default value
KR,RE,KG
Example
If you want to trigger the workflow for GL documents (document type
AB) maintain value AB here.
WFTRGPLANT
Usage
This configuration value is used to determine for which plants the PO /
Non PO workflow is triggered. This eliminates the triggering of the
workflow for unwanted plants. If you want to consider all plants,
maintain the value * here.
Default value
*
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 255
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Example
If you want to stop triggering the workflow for plant 0001, maintain all
plants different from 0001 here.
2. Maintain company codes that should be excluded from process types, using the
following parameters:
Process Type
Enter the process type from which the company code should be excluded
Company Code From, Company Code To
Enter a company code or a company code range that should not execute the
mentioned process type.
Exclude
To activate the exclusion, select this check box.
256 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.14. Maintaining additional cost handling
Delivery costs are costs that are invoiced for a delivery over and above the value of
the delivery itself. This includes freight charges, customs duty, packaging, material
surcharges, or other costs.
Delivery costs can accrue as line item related costs and as header related costs. There
is also a distinction between planned delivery costs and unplanned delivery costs.
• Freight charges
• Customs charges
Costs calculation
ICC extracts and classifies additional costs from the invoice based on customer
specific keywords. It delivers a separate line for each cost object found. The cost
type, for example freight or packaging, that is delivered within the line is called
“qualifier”.
You can customize VIM to use ICC line item data by setting the PO line
determination setting to OK; see “Maintaining the PO line determination”
on page 159. VIM checks whether planned costs of this cost type(s) exist for the
purchase order(s) involved and tries to match the cost amount(s) to the planned cost
amount(s). If the PO line determination setting is not OK, additional cost handling
will not work.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 257
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
A successfully matched line will be shown with PO details and condition type.
Mismatched cost lines will be handled according to the customizing. For the
available alternatives, see “Maintaining the handling of unplanned costs”
on page 263.
Planned delivery costs are shown on the PO Reference tab of the indexing screen
line item section. They can be recognized by the filled Condition Type. Unplanned
delivery costs are either shown on header level or on the G/L account tab of the
indexing screen line item section. If they are on item level they will show the
qualifier name and the alternative A4 or A5.
2. In the Customizing table qualifier texts screen, maintain the qualifiers, for
example FREIGHT or PACKAGING, using the following parameters:
• Description
• Short Description
2. In the Maintenance View for Qualifier Discount Flag, specify the qualifiers
that are discount, using the following parameters:
• Discount Flag
• Additional Costs
258 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.14. Maintaining additional cost handling
A SAP condition type represents some aspect of a company's daily pricing activities.
A different condition type can be defined for each kind of price, discount, or
surcharge that occurs in business transactions.
Example: ZOB1 represents value based customs surcharges.
Easymatch is a flag for the comparison of extracted line item data with planned
delivery cost in the purchase order. If Easymatch is set, only the cost amount is
compared. If it is not set, the amount is compared in addition with purchase order
number and item.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 259
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
2. In the Maintenance View for Additional Cost Handling, maintain the fields,
using the following parameters:
Determination Type
Enter the determination type. For additional planned cost handling, enter
ACP.
The determination type ACP is defined in the /OPT/AT_DETTYPE table.
Note: You can perform some customizing on the production system,
where clients are normally set to “No changes allowed”. For this
customizing activity, no transport request is created.
As a prerequisite, you must select the Edit Allowed check box in the /
OPT/AT_DETTYPE table for the corresponding transaction codes.
Field Type
Select Header from the list.
Field Name
Enter the field name. Click for a list of available fields.
Sequence
Define the sequence for the header.
Easymatch should have the highest number in the list.
260 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.14. Maintaining additional cost handling
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 261
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
2. In the Maintenance View for Additional Cost Handling screen, maintain the
fields, using the following parameters:
Determination Type
Enter the determination type. For additional cost handling, enter ACS.
The determination type ACS is defined in the /OPT/AT_DETTYPE table.
Note: You can perform some customizing on the production system,
where clients are normally set to “No changes allowed”. For this
customizing activity, no transport request is created.
As a prerequisite, you must select the Edit Allowed check box in the /
OPT/AT_DETTYPE table for the corresponding transaction codes.
Field Type
Select Header or Item from the list.
Item fields are used for auto coding of alternative 4 and alternative 5 G/L
lines.
The following item fields are allowed:
• HKONT
• KOSTL
• KSTRG
• PRCTR
• PROJK
• AUFNR
• NPLNR
• GSBER
• LSTAR
• VORNR
262 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.14. Maintaining additional cost handling
• ZUONR
• VBELN
• VBELP
• PAOBJNR
• GEBER
• FISTL
Field Name
Enter the field name. You can select the field from the available field list.
If you want to use auto coding for GL lines (alternative 4 and 5), you must
enter item coding fields like HKONT or KOSTL.
Sequence
Define the sequence for header and item fields.
ALTERNATIVE must be the first header field with sequence 1.
QUALIFIER must be sequence 2.
DISTR_TYPE must be sequence 3.
HEADER fields must be sequence 4 to x.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 263
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Alternative
The following alternatives are available:
Additional Costs
Enter qualifiers, for example FREIGHT.
264 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.14. Maintaining additional cost handling
Example:
• A1: For company code 3000 and vendors 0 to 3000, the cost will be added to the
Unplanned Cost header field.
• A6: Vendor 1002 claims handling charges, which will always be discarded.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 265
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
266 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.15. Maintaining the VAT date
2. In the Customizing Table G/L line flag for Handling Alternative screen,
specify whether the customer specific handling alternative is G/L line relevant
or not.
For general information, see the SAP Note 1232484 - How to use the VAT due date,
tax reporting date VATDATE (http://service.sap.com/sap/support/notes/1232484)
The VAT date functions in VIM work in conjunction with the global setting of
company codes Tax Reporting Date active. If this setting is activated, VIM checks
if the VAT date is provided in the DP document at the time of posting.
You can enter the VAT Date field during indexing in the DP indexing screen. In
many cases, the value of the supply date, which already exists in VIM, can be
assigned to the VAT date. VIM does not automatically populate the VAT date from
the supply date, but VIM provides the business rule 409 - Copy rule: Supply Date
to VAT Date (NPO / PO) to copy the value. You can activate this business rule when
needed. VIM provides the business rules 407 - Missing VAT Date (NPO) and 408 -
Missing VAT Date (PO) to check if the VAT date is entered in the DP document.
These business rules stop the process with a DP exception before posting.
In the standard configuration, none of the related functions are active. To be able to
use the VAT date, additional configuration is required, as described in the following
sections.
Alternatively, you can add the VATDATE field into the list based on characteristics, as
described in “Characteristic specific screen fields” on page 565. For example, you
can enable the field for Eastern European countries where the VAT date is
mandatory.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 267
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
The process types 407 and 408 check if the VAT date is provided in the DP
document. If not, the DP processing stops with an exception. Users are required to
enter the VAT date in the DP document. To enable the check, add the respective
process type for DP document or characteristic, with the function /OPT/
VIM_DETERMINE_PROC_407 (same function for 408).
The baseline configuration of the process types 407 and 408 contains predefined
process options. You can adjust the process options list to suit your scenarios.
The process type 409 copies the supply date value into the VAT date. This is not a
dialog process type: it does not trigger an exception. You must use the same process
type for both PO and NPO. You can enable the process type for individual
document types or using characteristics. The process type must be checked with the
function /OPT/VIM_DETERMINE_PROC_409.
• For PO invoices
With SAP BAPI (standard VIM BDC ID 1): When PO invoices are set up to be
posted.
268 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.16. Activating the profitability segment in the indexing screen
VIM 7.0 SP8 / VIM 7.5 SP4 and earlier do not support background posting of
VAT date. But if you want the posting to go through or you are using a user exit
to pass the date in some other way, you can set the constant to X.
3. On the Maintain Profitability Sement Fields screen, select the Active check box
at least for one row.
4. Enter a value 1 in the corresponding field of the Seq. Num column, and save.
5. If you use the Approval Portal for Invoice Approval, perform the necessary
configuration as described in “Activating the profitability segment”
on page 426.
6. Activate the PSEG field in Index Item Configuration in the document type
configuration. For more information, see “Configuring the index item fields”
on page 154.
Limitations
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 269
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
/OPT/VIM_1RDOC_DATA
This structure is used to capture data that is document specific and not process
specific. If a field is applicable for both POs and Non POs, maintain the field
here. An example for that field is the company code which can be for POs and
also for Non POs.
/OPT/VIM_4RAPP_DATA
This structure is used to capture data that is specific for Non PO approvals. If a
field is applicable to Non PO approvals, maintain the field here.
/OPT/VIM_BL_1RIDX_DATA
This structure is used to capture index data which may or may not be used in
subsequent processes. If you want to create a field that is specific to index
documents, extend this structure.
• Developer authorization
• Knowledge of SAP database tables and structures
270 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.17. Extensions in Document Processing
The validation is called in change mode for all DP dashboard actions with the
exception of the exit type functions located in the DP dashboard toolbar. These exit
type functions are used for special processing that does not allow reading the
current screen data.
Notes
• Actions performed in the plug-in toolbar, typically in the right panel, result
in the validation call. However, you cannot stop the corresponding actions
by passing the error message type back from the user exit, because of
technical limitations.
• If you would like to skip validation on plug-in toolbar actions, or on any
other actions, you can implement a check of the OK code in your user exit.
The example source code at the end of this section shows how to do this.
To activate and perform the data validation, you must first create a function module
with the following interface:
*" IMPORTING
*" VALUE(INDEX_DATA) TYPE /OPT/VIM_1HEAD
*" VALUE(INDEX_DATA2) TYPE /OPT/VIM_2HEAD
*" VALUE(OK_CODE) TYPE SY-UCOMM
*" VALUE(PROC_OPT) TYPE /OPT/VIM_1RACTION
*" TABLES
*" INDEX_ITEMS STRUCTURE /OPT/CIDX_ITEMS
*" INDEX_WTAX STRUCTURE /OPT/CIDX_EWHTAX
*" RETURN STRUCTURE BAPIRET2
The function module logic receives, in addition to the document data, the active OK
code and the selected process option (if there are any). It is supposed to return an
internal table with messages. All messages are shown in a dialog box. If any error
messages of type A, E, or X are returned, the screen processing is stopped when the
dialog box is closed.
To activate the user exit, you must create the following Z-constant entry with the
value equal to the function module name, in the /PTGWFI/Z_CONST table:
Product code
005
Constant
DP_VALIDATE_EXIT
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 271
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
Description
DP indexing screen - validation exit
Value
User exit function module name
DATA:
ls_return TYPE bapiret2,
lv_mesg TYPE sy-msgv2.
lv_mesg = ok_code.
CALL FUNCTION 'BALW_BAPIRETURN_GET2'
EXPORTING
type = 'W'
cl = '00'
number = '398'
par1 = lv_mesg
IMPORTING
return = ls_return.
APPEND ls_return TO return.
ENDFUNCTION.
272 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
9.17. Extensions in Document Processing
3. Configure the fields RBWWR, RBMNG, and KZMEK as input fields at item level for the
PO Reference tab only.
4. Configure the business rule Check for Reduction Invoice and BDC IDs 200
and 202 for auto posting or background posting of the reduction invoice.
1. Select the correction ID (KZMEK) as Vendor Error. Reduce Invoice from the list
in the line item column Correctn ID (Correction ID).
2. Press ENTER.
The original amount and quantity is copied into the fields Invoice Amount FC
(RBWWR) and Inv.doc.qty (Invoice document quantity; RBMNG).
3. Change the amount and quantity in the original amounts and quantity fields.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 273
VIM070500-08-CGD-EN-01
Chapter 9 Document Processing process configuration
In this context, VIM provides the LXBLNR field to hold the complete/entire long
invoice number in VIM. During DP processing/posting, VIM supports the following
options, aligned with SAP’s proposal, this means based on XBLNR and BKTXT in BKPF.
• Option 1
Prefix part goes to XBLNR. Sequence Number part goes to BKTXT.
• Option 2
Prefix part goes to BKTXT. Sequence Number part goes to XBLNR.
• Option 3
Based on Custom field in BKPF.
If you choose this option, this means a custom field in BKPF, to store either part or
complete invoice number. For this option, no out-of-the-box support is available.
You must customize BDC/BAPIs to save the invoice number into the custom field
while posting invoices.
Options 1 and 2 You configure two parts of the long invoice number, Prefix and Sequence Number,
using Z constant SET_REF_MAPPING_SP,to split into the fields XBLNR and BKTXT and
to post invoices accordingly.
The Z-constant SET_REF_MAPPING_SP allows configuring offset length for Prefix part
and Sequence Number part.
• Option 1
Example value: X10,B25. 10 characters (Prefix) of the long invoice
number are mapped into XBLNR and the next 25 characters (Sequence
Number) are mapped into BKTXT.
• Option 2
Example value: B20,X16. 20 characters (Prefix) of the long invoice
number are mapped into BKTXT and the next 16 characters are mapped
into XBLNR.
274 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 10
PO parking process configuration
Primarily, invoices can be parked for some further processing. This includes, for
example, waiting for approval, or changing some customizing like vendor data, or
tax data. The invoice will be posted in a later step.
Main concepts
Parking reasons
Roles
– Actions
– Referrals (for collaboration)
• Actions can base on transactions or class methods or workflow tasks.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 275
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
BDC IDs
• BDC IDs build a powerful infrastructure for prepopulating data into SAP
transactions without programming.
• BDC IDs are optimized for both dialog processing and background
processing.
• BDC IDs can be used to set dynamic Parameter IDs.
• BDC IDs can be used to configure new user collaboration actions.
• BDC IDs eliminate the need to code parameterized transactions.
• BDC IDs can be used to configure BDC success messages.
Main steps The following are the main steps involved in implementing process scenarios in the
PO parking process:
1. Identify the various parking reasons that are required for the realization of the
process scenarios.
2. Identify the subscreen to be called during the document parking process.
3. Identify the roll out criteria.
4. Identify the various roles and configure the roles in the appropriate process
types.
5. Identify and configure the process options according to the swimlanes.
6. Configure global customization setting as per customer requirements.
The starting point for any configuration is a set of process flow swimlanes. The
following swimlane is an example of such a process as implemented by the PO
invoice parking workflow:
276 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.1. Configuring process options
The following sections describe the main steps of the PO parking process
configuration:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 277
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
PO Based Invoice Configuration > Parked Invoice Processing Configuration >
Park Reason Maintenance > Process Option Definition
Option Type
Select the option type:
Action
The system executes an SAP transaction code defined against this
action.
Authorization
This option type is relevant only if the option selected is a PO blocked
scenario. It allows the user to complete the line level workflow and the
target role to run the transaction code defined against the authorization
option.
278 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.1. Configuring process options
Referral
The work item is forwarded to the target role defined in the user
process options configuration.
Approve/Reject
The Approve/Reject option type has more relevance in the Invoice
Approval process as these are predefined options.
BDC Action
Similar to the Action option type, but the transaction/execution has
more flexibility to be configured in the BDC ID defined here.
Workflow Task
Triggers a custom (sub) workflow when the user selects the option.
Note: Some of the following parameters are only available for certain
option types.
Option ID
Enter a 5 digit numeric ID that represents the option.
Description
Enter a description.
Option Short Text
Enter the description that is shown on the button in the user dashboard for
this option.
BDC Configuration Id
Select the BDC ID that will be called when the user selects the option for
execution. This field is applicable only if the option type is BDC Action.
Task
Enter the (sub) workflow/task to be triggered when the user selects the
option. The task must be compatible to OpenText workflow task.
Transaction Code
Define a transaction code to be called when the user executes the option.
This is only relevant if the option type is Action or Authorization.
Check Autopost
Define if the system shall try to post a parked document in background
after successful execution of the option:
Comments Required
Select this check box to force the user to maintain comments once this
option is executed.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 279
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Example: If an option deletes the SAP document, a confirmation from the user to
really perform the action makes sense.
Confirm Completion
Select this check box to achieve that the user will be prompted to confirm
successful completion of the option.
Override
Select this check box to achieve that the user will be able to select any SAP
user in the system as the user(s) that will receive the work item when it is
referred, and not just the users the system proposes after running the role
resolution process. This parameter is applicable only in the Referral
option type.
Validate Override User
Select a function module that is used to validate the users that the current
user overrides.
280 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.1. Configuring process options
Tip: The standard SAP authorizations for transactions are checked for the
underlying transactions in a user process option.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
PO Based Invoice Configuration > Parked Invoice Processing Configuration >
Technical Configuration > Advanced Process Option Configuration > PSS
User Process Options - OST
Block Reason
Select block reason. 9 is the system defined block reason for PO parked
invoices.
From Actor
Select the role that sent the work item.
To Actor
Select the role that receives the work item after successfully processing the
option.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 281
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Option Type
Select the type of process option (Action, Referral, BDC Action, Approve,
Reject, etc., see “Configuring process options” on page 277)
Option ID
Select the ID of the process option.
Condition FM
Example: If you would like to show the option “Change Purchase Info Record”
only if the Purchase Order has a Purchase Info Record (PIR), you can define a
custom function to verify the existence of the PIR and issue an error if there is no
PIR.
• If an error is issued in the function module, the option will not be
available to the user.
• For the interface of the condition function module, see function
module /OPT/BL_CONDFM_INFOPROVIDER.
282 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.2. Configuring parking reasons
In this step, you configure the valid parking reasons. Each parking reason represents
a process scenario as represented in a swimlane diagram.
• Define the roles that are responsible for receiving the first work item in the
process, for posting the PO invoice, and the initial approver.
• Delimit the available options for the role that is responsible for receiving the first
work item.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
PO Based Invoice Configuration > Parked Invoice Processing Configuration >
Park Reason Maintenance > Parking Reason Definition Maintenance
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 283
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Description
Enter a description for the parking reason.
Active Indicator
Select this check box to achieve that the user can select the parking reason
during parking of a PO invoice.
Approval Required
Select this check box to achieve that the parking reason will be considered
for the Invoice Approval process. For details on the Invoice Approval
process in VIM, see “Invoice Approval“ on page 347.
Subscreen Program/Screen Number
Select a subscreen that can be configured to capture additional information
from the user when the user chooses a particular parking reason.
284 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.2. Configuring parking reasons
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 285
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Autopost
Select this check box to achieve that the system tries to post the parked
invoice after the routing is complete.
Posting Actor
Define the role responsible for posting the invoice and also responsible for
handling errors if the posting in background fails.
Initial Actor
Define the role who receives the first work item in the process when the
current parking reason is selected.
Example: If a PO invoice is parked for “Currency Mismatch”, the initial role that
needs to look at the invoice is the BUYER to correct the PO. Maintain BUYER as initial
actor.
Initial Actor FM
You can define a custom function module to determine the initial actor.
Available Options
Define the options that are available for the role on the dashboard during
PO parked invoice process for the current parking reason. Separate the
options by semicolon. The option format is AXXXX where A is the option type
and XXXX is the 4 digit value representing the option ID.
The system uses these values in conjunction with the user process options
defined in “Configuring user process options” on page 281 to determine
which options show up for the role’s dashboard.
Initial Approver
Define the role of the initial approver if the invoice document is sent for
approval.
Delay Function
• Define the custom function module that can be used to restrict the
immediate triggering of the PO parking process even if the user selected
the current parking reason when the invoice is parked.
Example: The PO is parked for “Credit Memo Required” and you know that
Credit Memo is on its way and will not show up for the next two days. You
might then want to send the work item to the AP's inbox not before two days.
For this purpose, you can define a custom function to restrict the triggering of
the work item for the user for the next two days.
286 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.3. Configuring global parameters
• For the interface of the delay function module, see function module /
OPT/BL_P_DELAYFM_SRM.
Important
Take care when you change the global configuration parameters. Changes can
affect the functionality of the process.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 287
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
3. In the WebFlow Constant Table, under Product Code PIR, double-click the
Constant PO_BASED_INV_TCODE.
Example: After you have selected a particular parking reason, you want a particular
subscreen to appear as shown in the following screenshot.
288 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.3. Configuring global parameters
Note: We strongly recommend that you copy the program and subscreen
because the common part /PTGWFI/WLIX_COMMON_PART is required to
communicate to the main program.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 289
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
2. To access the configuration for PRKPROG and PRKSCREEN, run the /OPT/
VIM_IMG207 transaction.
Constant: PRKPROG
Usage
Subscreen program for parked invoice dashboard header subscreen. To
provide additional data on the invoice dashboard, you can define your
custom screen here.
290 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.3. Configuring global parameters
Default Value
/PTGWFI/PRK_SUBSCREEN01
Constant: PRKSCREEN
Usage
Subscreen number for parked invoice dashboard header subscreen. To
provide additional data on the invoice dashboard, you can define your
custom screen here.
Default Value
9901
2. Configure the order in which the options will appear in the user’s dashboard,
using the following parameters:
Description
Enter a description of the option order.
Constant Value
Value for the option order. Default value: 10ATR
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 291
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Individual values
1
Approvals
0
Rejects
A
Actions
T
Authorizations
R
Referrals
Example: If you want all actions to show up first, maintain A10TR. The options will
be shown in order actions, approvals, rejections, authorizations and referrals.
This custom (sub)workflow can do some actions that are not delivered in the VIM
standard process. For example, it can notify an agent that a PO invoice is parked and
waiting to be further processed. The (sub)workflow can also update some
monitoring custom tables.
292 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.3. Configuring global parameters
Constant PRK_PSS_BIND_FM1
Usage
This function module is used to manipulate the workflow container
during inward binding (task container to workflow container). This
manipulation facilitates many features such as populating Analytics
with custom data etc.
Default value
/PTGWFI/PRK_TMP_BIND_EXT_FM
Constant PRK_PSS_BIND_FM2
Usage
This function module is used to manipulate the workflow container
during outward binding (workflow container to task container). This
manipulation facilitates the user to capture process information and
populate with additional information.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 293
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Default value
/ORS/000007_LIX_PSS_BIND_O
Example: If the custom data is added to VIM tables and it should be displayed in the
Dashboard in some way, the data must be managed (manipulated) in such method exits.
Constant Value
This value is used to manage document data before calling the dashboard.
Default value – None
294 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.3. Configuring global parameters
Constant Value
This value is used to manage document data after calling the dashboard.
Default value – None
This custom (sub)workflow can do some additional action that is not delivered in
the VIM standard process, for example to notify an agent that the process is
completed, or to update some VIM/custom tables with corresponding data.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 295
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Constant Value
If you want to call a custom subworkflow after completing the PO Parked
Invoice Document process, you can define a workflow template/task here.
Default value – None
296 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.3. Configuring global parameters
Constant Value
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 297
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Constant Value
298 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.3. Configuring global parameters
Constant Value
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 299
VIM070500-08-CGD-EN-01
Chapter 10 PO parking process configuration
Constant Value
Enter a function module to be used to activate the parking of PO invoice
documents.
Default value:
Blank.
Baseline does not offer parking.
Optional value:
/PTGWFI/PRK_M_GET_PARK_DATA_N
This is the standard parking implementation function module.
• Company code
• Document date
• Vendor reference number
• Currency
• Vendor number
You can insert the function module in the corresponding Z constants or you can
create an own logic on basis of this function module.
For the creation of a PO invoice, maintain table /PTGWFI/Z_CONST, using the SM30
transaction. In Product Code LIX, Constant CREATE_PO_BDC_FM, enter Constant
Value /PTGWFI/VIM_CRE_PO_INV_PREF.
300 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
10.3. Configuring global parameters
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 301
VIM070500-08-CGD-EN-01
Chapter 11
PO blocking process configuration
Main concepts
Blocking reasons
Roles
– Actions
– Referrals (for collaboration)
• Actions can base on transactions or class methods or workflow tasks.
• Options and option types can effect the processing logic.
• Options and option types can also effect the user experience.
• Options and option types can make the workflow engine rerun the rules on
the most current metadata to effect the process flow.
• Options and option types can be configured to change the document status.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 303
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
BDC IDs
• BDC IDs build a powerful infrastructure for pre-populating data into SAP
transactions without programming.
• BDC IDs are optimized for both dialog processing and background
processing.
• BDC IDs can be used to set dynamic Parameter IDs.
• BDC IDs can be used to configure new user collaboration actions.
• BDC IDs eliminate the need to code parameterized transactions.
• BDC IDs can be used to configure BDC success messages.
Main steps The following are the main steps involved in implementing process scenarios in the
blocked PO invoice process configuration:
1. Identify the various blocking reasons that are required for the realization of the
process scenarios.
2. Identify the roll out criteria.
3. Identify the various roles and configure the roles in the appropriate process
types.
4. Identify and configure the process options according to the swimlanes.
5. Configure global customization setting as per customer requirements.
The starting point for any configuration is a set of process flow swimlanes. The
following swimlane is an example of such a process swimlane, as implemented by
the blocked PO invoice processing workflow:
304 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
The following sections describe the main steps of the PO blocking process
configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 305
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
• Define user process options for all the roles in the process.
• Delimit available options for the role that is responsible for the first work item
created by each blocking reason. This is done in an individual blocking reason
definition.
Tip: The standard SAP authorizations for transactions are checked for the
underlying transactions in a user process option.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
PO Based Invoice Configuration > Blocked Process Configuration > Technical
Configuration > Advanced Process Option Configuration > PSS User Process
Options - OST
306 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.2. Configuring blocking reasons
BlockReason
Select the blocking reason. If the invoice is blocked, the SAP invoice sets this
blocking reason.
From Actor
Select the role that sent the work item. Only this role will have the process
option on it's dashboard.
To Actor
Select the role who receives the work item after successfully processing the
option.
Option Type
Select the type of process option (Action, Referral, BDC Action, Approve,
Reject, etc., see “Configuring process options” on page 277)
Option ID
Select the ID of the process option.
Condition FM
Example: If you would like to show the option “Change Purchase Info Record”
only if the Purchase Order has a Purchase Info Record (PIR), you can define a
custom function to verify the existence of the PIR and raise an error if there is no
PIR.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
PO Based Invoice Configuration > Blocked Process Configuration > Block
Reason Maintenance > Block Reason Definition
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 307
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
Block Reason
Click and select the blocking reason from the list.
Description
Enter a description defining the blocking reason.
Delay FM
• Define the custom function module that can be used to restrict the
immediate triggering of the PO blocking process even if the user
selected the current blocking reason when the invoice is blocked.
Example: The PO is blocked for “Quantity Discrepancy” and you know that
additional quantities required to remove the blocking reason automatically are
on their way and will not show up for the next two days. You might then want
to send the work item to the AP's inbox not before two days. For this purpose,
you can define a custom function to restrict the triggering of the work item for
the user for the next two days.
• For the interface of the delay function module, see function module /
OPT/BL_P_DELAYFM_SRM.
308 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.3. Configuring global parameters
Initial Actor
Define the role who receives the first work item in the process when the
current blocking reason is selected.
Example: If a PO invoice is blocked for “Price discrepancies”, the initial role that
needs to look at the invoice is the BUYER to correct the PO. Maintain BUYER as initial
actor.
Initial Actor FM
• You can define a custom function module to determine the initial actor.
Object Type
This parameter is obsolete.
Event
This parameter is obsolete.
Reference table
This parameter is obsolete.
Reference field
This parameter is obsolete.
Important
Take care when you change the global configuration parameters. Changes can
affect the functionality of the process.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 309
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
310 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.3. Configuring global parameters
Note: We strongly recommend that you copy the program and sub screen
because the common part /PTGWFI/WLIX_COMMON_PART is required to
communicate to the main program.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 311
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
2. To access the configuration for LIXPROG and LIXSCREEN, run the /OPT/
VIM_IMG301 transaction.
Alternatively, navigate to Vendor Invoice Management > PO Based Invoice
Configuration > Blocked Process Configuration > Technical Configuration >
Dashboard Screen Customization > Line Level Dashboard Screen > Screen
Exit.
312 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.3. Configuring global parameters
Constant: LIXPROG
Usage
Subscreen program for blocked invoice dashboard header subscreen. To
provide additional data on the invoice dashboard, you can define your
custom screen here.
Default Value
/PTGWFI/M_LIX_SUBSCREEN02
Constant: LIXSCREEN
Usage
Subscreen number for blocked invoice dashboard header subscreen. To
provide additional data on the invoice dashboard, you can define your
custom screen here.
Default Value
9902
Currency A purchase order and the corresponding blocked invoice might have been created or
conversion posted using different currency keys. Therefore, it was often difficult to compare the
amounts displayed in the header section of the blocked line item dashboard due to
the different currency keys. VIM provides a solution that allows different settings
regarding the initial and also a completely flexible currency conversion: the constant
LIXSCREEN_CURR_CONV, available for the product code LIX in table /PTGWFI/
Z_CONST (transaction SM30).
• The first character controls which initial default currency conversion method is
used when the blocked line item dashboard is executed.
• The second character controls whether a currency conversion button is displayed
on the screen. Such a button allows flexibly changing the displayed currency at
any time.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 313
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
I
Use the invoice currency for initial currency conversion. The posting date of the
invoice is taken as conversion date.
P
Use the purchase order currency for initial currency conversion. The creation
date of the purchase order is taken as conversion date.
L
Use the local currency (based on the invoice) for initial currency conversion. The
current system date is taken as conversion date.
N
No initial currency conversion takes place.
1
Display the currency conversion button on the screen. The current system date is
always taken as conversion date.
0
Do not display the currency conversion button on the screen.
The default configuration is N0. This means, no initial currency conversion takes
place, and the button for flexible currency conversion is not displayed.
The constant allows different flexible combinations, for example P1: Initial currency
conversion uses the purchase order currency; and additionally the flexible
conversion button is activated. This approach should offer maximum flexibility
when using the blocked line item dashboard.
314 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.3. Configuring global parameters
Note: We strongly recommend that you copy the program and sub screen
because the common part /PTGWFI/WLIXDB_COMMON_PART is required to
communicate to the main program.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 315
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
2. To access the configuration for LIXDBPROG and LIXDBSCREEN, run the /OPT/
VIM_IMG303 transaction.
316 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.3. Configuring global parameters
Constant: LIXDBPROG
Usage
Sub screen program for blocked invoice dashboard header sub screen.
To provide additional data on the invoice dashboard, you can define
your custom screen here.
Default Value
/PTGWFI/M_LIXDB_SUBSCREEN02
Constant: LIXDBSCREEN
Usage
Sub screen number for blocked invoice dashboard header sub screen.
To provide additional data on the invoice dashboard, you can define
your custom screen here.
Default Value
9902
2. Configure the order in which the options will appear in the user’s dashboard,
using the following parameters:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 317
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
Description
Enter a description of the option order.
Constant Value
Value for the option order. Default value: 10ATR
Individual values
1
Approvals
0
Rejects
A
Actions
T
Authorizations
R
Referrals
Example: If you want all actions to show up first, maintain A10TR. The options will
be shown in order actions, approvals, rejections, authorizations and referrals.
Using such exits, you can manipulate the workflow container of the process or
populate VIM tables with custom data. The function modules maintained here are
called in the function module /PTGWFI/BIR_F_PSS_BINDING.
318 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.3. Configuring global parameters
Constant PSS_BIND_EXIT_FM1
Usage
This function module is used to manipulate the workflow container
during inward binding (task container to workflow container). This
manipulation facilitates many features such as populating analytics
with custom data etc.
Default value
None
Constant PSS_BIND_EXIT_FM2
Usage
This function module is used to manipulate the workflow container
during outward binding (workflow container to task container). This
manipulation facilitates the user to capture process information and
populate with additional information.
Default value
None
Example: Some custom data is added to VIM tables and should be displayed in the
dashboard. Therefore, this data must be managed (manipulated) in such method exits. These
exits are called in method SELECTPROCESSBIRV2 of the object type /OPT/VIM_BIR.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 319
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
2. Configure the post dashboard method exit, using the following parameters:
Constant Value
This value is used to manage document data after calling the dashboard.
Default value
/PTGWFI/LIX_BK_TMP_PST_EXT
Using such exits, you can manipulate the workflow container during inward and
outward binding. If maintained, the custom functions are called in the function
module /PTGWFI/LIX_F_DB_BINDING.
320 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.3. Configuring global parameters
Constant DB_BIND_EXIT_FM1
Usage
This function module is used to manipulate the workflow container
during inward binding (task container to workflow container). This
manipulation facilitates many features such as populating analytics
with custom data etc.
Default value
None
Constant DB_BIND_EXIT_FM2
Usage
This function module is used to manipulate the workflow container
during outward binding (workflow container to task container). This
manipulation facilitates the user to capture process information and
populate with additional information.
Default value
None
2. Configure the send back functionality exit, using the following parameters:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 321
VIM070500-08-CGD-EN-01
Chapter 11 PO blocking process configuration
Constant DB_SNDBACK_EXIT
Usage
This function module is used to capture option information from the
dashboard step when the work item is sent back successfully in the
header level dashboard.
Default value
None
Interface
The interface of the function module is found in function module /
PTGWFI/LIX_TMP_DB_SBK_EXIT.
Constant IMAGE_DISP_FM
Constant Value
Enter a function module. This function module can be used to display
an SAP ArchiveLink image associated to the PO invoice document.
Default value
/PTGWFI/LIX_F_TMP_DISP_IMG
322 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
11.3. Configuring global parameters
Interface
For the interface of the image display function module, see function
module /PTGWFI/LIX_F_TMP_DISP_IMG.
3. In the WebFlow Constant Table, under Product Code LIX, double-click the
Constant DASHBOARD_IMAGE_AUTO.
VIM provides a function module for this scenario. See “Configuring populating
screens for re-enter options” on page 300 for details.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 323
VIM070500-08-CGD-EN-01
Chapter 12
Non PO parking process configuration
Vendor Invoice Management (VIM) provides functionality for managing parked Non
PO FI invoices (FV60 transaction) and exceptions therein.
The main processing concept involved in managing parked Non PO invoices is the
concept of “parking reasons”. Parking reasons define the overall processing of the
invoice as required by the process swimlane.
Main concepts
Parking reasons
Roles
– Actions
– Referrals (for collaboration)
• Actions can base on transactions or class methods or workflow tasks.
• Options and option types can effect the processing logic.
• Options and option types can also effect the user experience.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 325
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
• Options and option types can make the workflow engine rerun the rules on
the most current metadata to effect the process flow.
• Options and option types can be configured to change the document status.
BDC IDs
• BDC IDs build a powerful infrastructure for pre-populating data into SAP
transactions without programming.
• BDC IDs are optimized for both dialog processing and background
processing.
• BDC IDs can be used to set dynamic parameter IDs.
• BDC IDs can be used to configure new user collaboration actions.
• BDC IDs eliminate the need to code parameterized transactions.
• BDC IDs can be used to configure BDC success messages.
Main steps The following are the main steps involved in implementing process scenarios in the
Non PO parking process:
1. Identify the various parking reasons that are required for the realization of the
process scenarios.
2. Identify the sub screen to be called during the document parking process.
3. Identify the roll out criteria.
4. Identify the various roles and configure the roles in the appropriate process
types.
5. Identify and configure the process options according to the swimlanes.
6. Configure global customization setting as per customer requirements.
The starting point for any configuration is a set of process flow swimlanes. The
following swimlane is an example of such a process as implemented by the Non PO
invoice parking workflow:
326 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.1. Configuring parking reasons (Non PO parking process)
The following sections describe the main steps of the Non PO parking process
configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 327
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
In this step, you define the valid parking reasons in the VIM Non PO parking
process. Each parking reason represents a process scenario as represented in a
swimlane diagram.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
Non PO Based Invoice Configuration > Parked Invoice Processing
Configuration > Park Reason Maintenance > Parking Reason Maintenance
328 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.1. Configuring parking reasons (Non PO parking process)
Description
Enter a description for the parking reason.
Active Indicator
Select this check box to achieve that the user can select the parking reason
during parking of a Non PO invoice.
Subscreen Program/Screen Number
Select a sub screen that can be configured to capture additional information
from the user when the user chooses a particular parking reason.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 329
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
Approval Required
Select this check box to achieve that the parking reason is flagged for
approval and that the Invoice Approval process is triggered.
Autopost
Select this check box to achieve that the system automatically posts the
invoice after Invoice Approval is completed.
Initial Actor
Define the role who receives the first work item once this document is
parked for the current parking reason.
Example: If a Non PO invoice is parked for “Approval Required”, the initial role
that needs to look at the invoice is the APPROVER. If the Approval Required check
box is selected, the initial role will be CODER.
Initial Actor FM
You can define a custom function module to determine the initial actor.
For the interface of the function module, see function module /OPT/
BL_Q_INIT_ACT_FM.
Delay Function
• Define the custom function module that can be used to restrict the
immediate triggering of the Non PO parking process even if the user
selected the current parking reason when the invoice is parked.
• Example: The Non PO invoice is parked for “Approval Required” and you
want to delay the approval for 2 days. You might then want to send the work
item to the AP's inbox not before two days. For this purpose, you can define a
custom function to restrict the triggering of the work item for the user for the
next two days.
330 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.1. Configuring parking reasons (Non PO parking process)
• For the interface of the delay function module, see function module /
OPT/BL_P_DELAYFM_SRM.
Initial Approver
Define the role of the initial approver if the invoice document is sent for
approval.
Posting Actor
Define the role responsible for posting the invoice and also responsible for
handling errors if the posting in background fails.
Available Options
Define the options that are available for the role on the dashboard during
Non PO parking process for the current parking reason. Separate the
options by semicolon. The option format is AXXXX where A is the option type
and XXXX is the 4 digit value representing the option ID.
The system uses these values in conjunction with the user process options
defined in “Configuring user process options” on page 331 to determine
which options show up for the role’s dashboard.
Tip: The standard SAP authorizations for transactions are checked for the
underlying transactions in a user process option.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
Non PO Based Invoice Configuration > Parked Invoice Processing
Configuration > Technical Configuration > Advanced Process Option
Configuration > PSS User Process Options - OST
2. Click New Entries in the application toolbar.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 331
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
BlockReason
Select block reason. V is the system defined block reason for Non PO parked
invoices.
From Actor
Select the role that sent the work item.
To Actor
Select the role who receives the work item after successfully processing the
option.
Option Type
Select the type of process option (Action, Referral, BDC Action, Approve,
Reject, etc., see “Configuring process options” on page 277)
Option ID
Select the ID of the process option.
Condition FM
Important
Take care when you change the global configuration parameters. Changes can
affect the functionality of the process.
332 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.2. Configuring global parameters
3. In the WebFlow Constant Table, under Product Code PIR, double-click the
Constant NONPO_INV_TCODE.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 333
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
Example: After you have selected a particular parking reason, you want a particular
subscreen to appear as shown in the following screenshot.
Note: We strongly recommend that you copy the program and subscreen
because the common part /PTGWFI/WLIX_COMMON_PART is required to
communicate to the main program.
334 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.2. Configuring global parameters
2. To access the configuration for PIRPROG and PIRSCREEN, run the /OPT/
VIM_IMG224 transaction.
Alternatively, navigate to Vendor Invoice Management > Non PO Based
Invoice Configuration > Parked Invoice Processing Configuration > Technical
Configuration > Dashboard Screen Customization > Dashboard Screen Exits.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 335
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
Constant: PIRPROG
Usage
Subscreen program for Non PO parked invoice dashboard header
subscreen. To provide additional data on the invoice dashboard, you
can define your custom screen here.
Default Value
/PTGWFI/PIR_SUBSCREEN01
Constant: PIRSCREEN
Usage
Subscreen number for Non PO parked invoice dashboard header
subscreen. To provide additional data on the invoice dashboard, you
can define your custom screen here.
Default Value
9901
This custom (sub)workflow can do some actions that are not delivered in the VIM
standard process. For example, it can notify an agent that a Non PO invoice is
parked and waiting to be further processed. The (sub)workflow can also update
some monitoring custom tables.
336 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.2. Configuring global parameters
Constant PSS_BIND_EXIT_FM1
Usage
This function module is used to manipulate the workflow container
during inward binding (task container to workflow container). This
manipulation facilitates many features such as populating analytics
with custom data etc.
Default value
None
Constant PSS_BIND_EXIT_FM2
Usage
This function module is used to manipulate the workflow container
during outward binding (workflow container to task container). This
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 337
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
Example: If the custom data is added to VIM tables and it should be displayed in the
Dashboard in some way, the data must be managed (manipulated) in such method exits.
2. Configure the pre PSS method exit, using the following parameters:
Constant Value
This value is used to manage document data before calling the dashboard.
Default value
None
338 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.2. Configuring global parameters
Example: Custom data is added to VIM tables and it is displayed in the dashboard. This
custom data can be changed in the dashboard. After the dashboard is quit, the data must be
saved. This can be done in the post PSS method exit.
2. Configure the post PSS method exit, using the following parameters:
Constant Value
This value is used to manage document data after calling the dashboard.
Default value
None
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 339
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
This custom (sub)workflow can do some additional action that is not delivered in
the VIM standard process, for example to notify an agent that the process is
completed, or to update some VIM/custom tables with corresponding data.
Constant Value
If you want to call a custom subworkflow after completing the Non PO
parking process, you can define a workflow template / task here.
Default value
None
340 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.2. Configuring global parameters
Constant Value
Enter a function module. This function module can be used to post a
document automatically using a custom function. If the function module
configured here raises an exception, the document will not be posted.
Default value
None
Interface
For the interface of the function module, see function module /PTGWFI/
PIR_F_TMP_PRE_AUTOPOST.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 341
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
Constant Value
Enter a function module. This function module can be used to post process
data after an invoice document is posted.
Default value
None
Interface
For the interface of the function module, see function module /PTGWFI/
PIR_F_TMP_POST_EXIT_FM.
342 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.2. Configuring global parameters
Constant Value
Enter a function module. This function module can be used to display an
SAP ArchiveLink image associated to the Non PO invoice document.
Default value
/PTGWFI/BIR_F_TMP_DISP_IMG
Interface
For the interface of the function module, see function module /PTGWFI/
BIR_F_TMP_DISP_IMG.
The copy function module should be remote enabled.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 343
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
Constant Value
You can use this value to call any workflow parallel to the Non PO parking
workflow.
Default value
None
344 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
12.2. Configuring global parameters
3. Look for Product Code PIR and Constant USR_EXIT_GET_DATA_FM and double-
click the line.
Constant Value
Enter a function module to be used to activate the parking of PO invoice
documents.
Default value:
Blank.
Baseline does not offer parking.
Optional value:
/PTGWFI/PIR_F_GET_PARK_DATA_N
This is the standard parking implementation function module.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 345
VIM070500-08-CGD-EN-01
Chapter 12 Non PO parking process configuration
• Company code
• Document date
• Vendor reference number
• Currency
• Vendor number
You can insert the function module in the corresponding Z constants or you can
create an own logic on basis of this function module.
For the creation of a Non PO invoice, maintain table /PTGWFI/Z_CONST, using the
SM30 transaction. In Product Code PIR, Constant CREATE_BDC_FM, enter Constant
Value /PTGWFI/VIM_CRE_NPO_INV_PREF.
346 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 13
Invoice Approval
Invoice Approval (IAP) is the component of VIM that handles the approval
processes for both Non-PO based and PO based invoices.
13.1 Overview
Level-based approvals can be done as line-based (sequential or parallel flow) and
header-based approvals. For details about level-based approval, see “Configuring
approval flow settings” on page 365.
• Sequential approval
• Parallel approval
• Approval buffer
Supported Approvals can be handled at the DP processing stage, after the DP invoice is
invoice types converted in to an SAP parked document, or after the invoice is posted.
DP approval
For DP-document-based approval, the process type for DP approval needs to be
configured in the system. For more information, see “Configuring the process
type” on page 350.
Parked approval
In case of parked document approval, the invoice has to be parked with an
appropriate parking reason before an approval process can start. Depending on
the parking reason configuration, an approval workflow starts. For more
information, see “Configuring the parking reason” on page 350.
Posted approval
For posted approval, depending on the configuration for this type of approval,
the approval process will be started after the document is posted either in
background or manually with some payment block. For more information, see
“Configuring posted approval” on page 353.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 347
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Approval in The approval workflow supports approvals inside SAP GUI, and outside of SAP
SAP GUI, web, GUI, if the optional OpenText Approval Portal or Mobile Approval Portal is
and mobile
implemented.
Approving invoices in the Approval Portal or in the Mobile Approval Portal does
not require an SAP user ID. Users can be authenticated through the SAP NetWeaver
Portal or the Windows domain instead. However, you must ensure, like with any
other solution, that the indirect usage of SAP data is properly licensed.
The Approval Portal provides a concise and user-friendly web interface for
approving invoices. The interface is designed to deliver the right amount of
information to enable approvers to make a quick decision.
With the Mobile Approval Portal, you can use mobile devices like an iPad, an
iPhone, an Android smartphone, or a Blackberry device for approval purposes. In
the Mobile Approval Portal, coding is not available.
People involved There are several people (roles) that are involved in the IAP process. The actual
in the IAP names might be different, but the activities are the same.
process
Coder
The person who is responsible for entering accounting data. The coder can be
both an SAP user and/or a web user if Approval Portal is implemented.
Goods or Service Requester (Requisitioner)
The person who requested the goods or the service.
Approver
The person who is responsible for approving the invoices. The approver can be
an SAP user or a web user if Approval Portal or Mobile Approval Portal is
implemented.
AP Processor
A member of the Accounts Payable (AP) department who deals with invoices.
The roles that are part of this process are different from the standard roles described
in “Roles“ on page 35. Because the functional requirements are different for IAP
roles compared to other exception processes, a separate role infrastructure is
required. For more information, see “Roles in the IAP process” on page 404.
Workflow
348 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.1. Overview
Trigger for the The way the IAP process is triggered depends on the kind of invoice document.
IAP process
End of the IAP There are several activities that mark the end of the IAP process:
process
• The invoice is finally approved and posted.
• The invoice is deleted or posted (only for parked invoices).
• The invoice is completely rejected.
• Approval is recalled. The process goes back to DP or parking workflow.
Configuration This section outlines all the aspects of implementation and configuration of the IAP
outline of the component of VIM.
IAP process
Note: You can perform most of the configurations using the VIM Customizing
IMG with the /OPT/SPRO transaction code.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 349
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
The following screenshot shows the standard process type configuration delivered
for the DP IAP process.
To configure the parking reason for PO invoices, run the /n/OPT/SPRO transaction
and navigate to Vendor Invoice Management > PO Based Invoice Configuration >
Parked Invoice Processing Configuration > Park Reason Maintenance > Parking
350 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.3. Configuring the parking reason
To configure the parking reason for Non PO invoices, run the /n/OPT/SPRO
transaction and navigate to Vendor Invoice Management > Non PO Based Invoice
Configuration > Parked Invoice Processing Configuration > Park Reason
Maintenance > Parking Reason Maintenance.
For the Non PO IAP process, the following dialog box serves to capture the
requester information:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 351
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
If you need to capture custom logic or customer data during the parking process to
initiate the approval workflow, you have to replace the above screen with a custom
screen. For details, refer to “Configuring parking reasons (Non PO parking process)”
on page 327.
2. Configure the trigger points for the approval workflow, using the following
parameters:
352 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.4. Configuring posted approval
BLOCKRSN
Benefit Besides the PO blocking scenarios, the VIM process ends with the creation of a
posted document. The posted approval processing enables you to post a Non PO or
PO invoice as fast as possible with an individual blocking reason. Then you can
approve the document with the approval workflow after the document creation.
Invoices do not need to go into a long approval process and then are posted finally.
With posted approval, they are posted before any approval process is started.
Workflow The posted approval subworkflow is available for blocked posted documents that
are processed within the DP process. Stand-alone parked or posted documents are
not supported. You can trigger the subworkflow in one of the following ways:
For the posted PO approval scenario, either the existing blocking workflows are
triggered or the approval process is started depending on the posted approval
configuration.
With the final approval of the posted document, the individual payment block is
removed.
Automated In combination with the automatic processing of the posted approval, the coding
coding step can be completely skipped.
Configuration The whole configuration for the posted approval is integrated in the OpenText
aspects Configuration tree: Navigate to Vendor Invoice Management > Invoice Approval
Configuration > Approval Workflow.
To configure the posted approval process, the following steps are necessary:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 353
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
2. Configure event linkage for posted approval trigger and configure the event
queue processing job using transaction SWEQADM (mandatory)
3. Define dynamic determination for the auto processing:
Note: This step is optional: If you configure to use the determination for
the automatic posted approval activation type, then you have to process
this step. If you activate it always or by custom function module, you do
not need to process this customizing.
354 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.4. Configuring posted approval
3. Configure the Posted Approval Settings (PAS), using the following parameters:
Process Type
Baseline delivers the process type 149 for PO documents and the process
type 249 for Non PO documents. A posted document that is rejected in the
approval process will be processed within the DP workflow with this
process type. For this process type, baseline delivers the following process
options:
2020
Re-Submit for Approval
2021
Submit for one step Approval
2022
Remove payment block and complete DP
2023
Keep payment block and complete DP
Automatic processing
For Non PO documents
In the DP process, a document can be submitted for approval (manually
or automatically with exception “Approval required”). In this case, the
automatic processing defines that the DP or parked approval process
terminates after the requester step, for the time being. The document is
posted with the configured payment block. After posting, the approval
process is resumed, starting with the first approver step.
When the coding happens in background with auto coding (see
“Configuring auto coding” on page 176), also the coding step can be
skipped and the document will be posted directly.
For PO documents
The automatic processing defines that the document is posted
automatically with the configured payment block.
Activation type
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 355
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Payment Block
This field is available if posted approval is activated.
Enter the payment block that is used to post the document in the
automatic processing.
Posted Approval Finder
Enter the exit function to activate the automatic processing (interface
check function /OPT/AAFS_DETERMINE_PAS).
Manual processing
For Non PO and PO documents, the configuration of the manual processing
defines that the posted approval process is triggered for manually posted
documents with the configured payment blocks.
Activation type
Constant Value
Enter Constant Values for payment blocks: Possible payment blocks for
which the posted approval is relevant to be triggered. Maintain the
standard Payment blocks of table T008. Separate them by comma.
Reject processing
Approval restart options
Rejected invoices are processed within DP processing with the
configured process type. This refers to the baseline process options
Submit for one step Approval and Resubmit for Approval for the
356 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.4. Configuring posted approval
Comments Required
Select this check box to determine that a comment is required
within the Resubmit for Approval screen. This comment is used in
the approval process. It is not logged for the process option, which
can also be activated in the process option configuration.
Reject by Requester
An automatic processed DP document for posted approval is directly
sent to the assigned approver of the COA during the approval process.
In this scenario, the coding and requester step is already executed.
When the approver rejects the document, it is sent to the previous
approver. With posted approval, the requester is not always the first
approver. It may happen that the requester does not receive the rejected
document.
Select this check box to determine that the document is finally sent to
the requester when the approver rejects the document before the
approval workflow ends.
Processing Exits
You might want to individually trigger the posted approval process and to
keep the DP workflow alive for the posted document. Therefore, you can
maintain custom functions. The payment block, which will be removed in
the final approval step, can be processed individually, as well.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 357
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Exit confirmation
Integrate an own logic for the posted approval to keep the DP process
alive according to your start conditions. All other configurations to keep
the process alive according to the manual or automatic blocking are not
taken into account (maintained within /OPT/AT_PAS). Only the own
logic within the exit function is used. The interface of the exit function
has to be compatible with the function /OPT/
AAFS_SAMPLE_EXIT_CONFIRM.
Run the SWETYPV transaction and activate the event linkage for the posted approval.
358 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.4. Configuring posted approval
Object Type
/ORS/INVAP
Event
POSTED
Linkage Activated
Selected
Enable Event Queue
Selected.
You must maintain the event queuing and configure a job (transaction SWEQADM).
Non PO For Non PO documents, the event is raised in the BTE exit 1050 and exit 1030 within
exit function /OPT/BTE_IF_00001050 and /OPT/BTE_IF_00001030. The
corresponding BTE has to be activated. Check transaction FIBF > Settings > P/S
Modules -> …of a partner.
PO For PO documents, the event is raised in the event receiver of function /OPT/
BL_PO_BLK_RECEIVER, which is triggered in the event linkage for object BUS2081
and event POSTED. Check transaction SWETYPV and see “Event linkages” on page 81.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 359
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Note: This step is optional: If you configure to use the determination for the
automatic posted approval activation type, then you have to process this step.
If you activate it always or by custom function module, you do not need to
process this customizing.
Determination Type
Enter PAS (Posted Approval Settings)
The determination type is defined in table /OPT/AT_DETTYPE. The type PAS
is delivered within the posted approval baseline configuration.
Field Type
Available values are Header or Item. For the determination, only header
fields are relevant.
360 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.4. Configuring posted approval
Field Name
Select the corresponding field of the /OPT/VIM_1HEAD or /OPT/VIM_1ITEM
table.
Sequence
Define the processing sequence of the determination.
Search Help Name
Configure the search help that will be used in the data determination
configuration.
Allow Ranges
Select this check box to allow ranges in the data determination
configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 361
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
To define a multi level approval process, you have to consider the following aspects:
362 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
The subsequent approvers (only for Non PO invoices) are determined when the
current approver approves the invoice. The system determines the next approver
according to the settings in the COA. In the level based approval, the approver is
determined by:
If the current approver rejects the invoice, the invoice is sent to the previous
approver or to the initial coder, or the complete approval flow is cancelled. This
depends on the configuration of the rejecting process.
All approvers who approve the invoice are stored in the approval stack. So, in case
the current approver rejects the invoice, the system knows the last approver. If the
first approver rejects the invoice, the invoice is sent back to the AP department.
Notes
• Implementation note
When you enter the first approver at the parking reason screen or indexing
screen, and you are using search help, OpenText recommends using the
combination of last name, first name and email address. If the combination
fails to identify one user, the system may suggest a list of matching users.
• Technical note
The initial approver is usually stored in the parking monitor table (/PTGWFI/
F_PIRMTR) and retrieved by the /ORS/APPROVER-> NEW method.
The subsequent approvers (only for Non PO invoices) are determined when the
current approver approves the invoice. The system determines the next approver
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 363
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
according to the settings in the COA. In the level based approval, the approver is
determined by:
If the current approver rejects the invoice, the invoice is sent to the previous
approver or to the initial coder, or the complete approval flow is cancelled. This
depends on the configuration of the rejecting process.
All approvers who approved the invoice are stored in the approval stack so that in
case the current approver rejects the invoice, the system knows who the last
approver was. If the first approver rejects the invoice, the invoice is sent back to the
AP department.
Technical Notes
• You can configure who receives the work item after the first approver rejects
the invoice. You perform this configuration in the parking reason table /
PTGWFI/F_PRKRSN for a non-PO invoice or /PTGWFI/M_PRKRSN for a PO
invoice. See “Configuring the parking reason” on page 350.
• The approval is considered completed if the current approver has sufficient
authorization for the invoice amount and cost elements.
• You can redefine determination conditions using an extension.
364 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
against the COA. As long as there still are invoice lines that have not been
approved yet, and that cannot be approved by the current coder, the
document must be forwarded to the next coder until the document is
completely coded and approved. When the document is completely coded
on the coding level (level 0), the document must be processed in the
requester level because there is no limit assigned to the coder level.
Requester level
Coding has been processed. This can also happen on requester level, see
Coder Processing on page 369. Now the invoice is processed on requester
level. If there has been a coder step before, the requester cannot change the
data. If there has been no coder step, the requester can change the data.
Similar to the coder level, all invoice lines are checked against the COA and
the document is forwarded until all lines are approved. Compared to the
coder level, there is the following difference: According to the approval
scenario (header or line based), the invoice or invoice lines can already be
finally approved in the requester level (level 1) if the approval limit of the
requester is sufficient.
Approval level
The approval level is processed according to the approval scenario (header
or line based). The invoice or the invoice lines are processed on one level. It
is checked if additional approval levels have to be processed after one level
has been finished. On the approval level, the invoice cannot be changed any
longer by the approver.
Technical note
Important
For PO document types, level-based approval cannot be used. Still, only the
“old” simple approval is supported.
To configure an approval with more than one step for PO document types, a custom
extension is required.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 365
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Level based approvals can be done header based or line based (sequential or parallel
flow). Levels are defined against approval limits. A pack is defined as a group of
lines that are assigned to an approver and that this approver can approve; this
means, the approver has the corresponding authorizations of the cost elements.
To use the level based approval, you must configure approval flow settings (AFS).
These settings are divided into the following parts:
366 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Note: This action is optional: If you configure to use the determination for
the mapping activation type, you must perform this action. If you activate it
always or by custom function module, you do not need to perform this
customizing.
Important
OpenText recommends that you do not change the settings of the AFS ID if
there are still open approval processes that were started with this AFS ID.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
Invoice Approval Configuration > Approval Workflow > Setup Approval
Chain > Approval Flow Settings.
Note: You can access the field configuration for the invoice detail page for
a selected AFS ID, from here: Select an AFS ID, and, in the Dialog
Structure, double-click Maintain Invoice Detail Fields or Maintain
Coding Fields Mapping. For more information, see “Configuring fields
for the invoice detail page” on page 388.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 367
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
The AFS ID represents a template for an approval flow. To use an AFS ID, it
must be mapped against a VIM document type. For more information, see
“Maintaining the approval flow settings mapping” on page 371.
AFS ID
Unique ID for the global approval settings
Important
To keep your system manageable, do not create too many AFS IDs.
Preferably, use the detail configuration to set up the AFS settings.
Approval Flow
Explanation
Detail description of the AFS
AFS Type
Select one of the following AFS types:
H - Header Based Approval
Header based approval is based on the gross amount of the invoice.
S - Line Based - Sequential
Line based approval is based on the line items amount. Sequential
approval sends the invoice to one approver after the other.
P - Line Based - Parallel
Parallel approval allows to send the invoice to more than one approver
at the same time.
Process Classes
368 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Approval Limit
Amount Base
Select Gross Amount or Net Amount. If the AFS Type is Header, approvals
are always based on gross amount.
COA Currency
Select Fixed Currency (Define the currency in the Currency field.) or
Company Code Default Currency.
Conversion Date
Select the conversion date for currency conversion. Possible values: Current
System Date, Date on the Vendor Invoice, Date per Function Module.
Conversion FM
If you have selected Date per Function Module in the Conversion Date
field, enter the function module to determine the currency conversion date.
Template: /OPT/DETERMINE_CONVERSION_DATE
Automation Processing
Fallback User FM
Enter a function module to determine a fallback user. A fall back user will
always be available in the user search dialogs (next coder, next requester, or
next approver) if no user can be found in the COA. The purpose of the fall
back user is to send the invoice to a user who takes care to correct the COA
settings. Therefore, you must set up the fallback user with the user details in
the COA.
Template: /OPT/FALLBACK_USER_TEMPLATE
Automatic Forward
Select this check box to let the system automatically choose the next user
within one approval level. It is not possible to change this user.
Note: Automatic Forward is not considered for the Approval Portal.
Coder Processing
Coder Determination
Coders can be defined for each document type. Select one of the following
options:
By Requester
Each requester has an associated coder.
By Company Code
Each company code has an associated coder.
Both Requester and Company Code
The coder is determined by both requester and company code.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 369
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Use Requester
The coder is the requester.
Coder Determination FM
You can customize the coding functionality by defining your own function
module. See “Approval flow settings function modules” on page 374.
Template: /OPT/DETERMINE_CODER_TEMPLATE
Use SAP field seq.
Select this check box to use the customized Approval Portal item field
sequence also for the SAP GUI approval screens.
Requester Determ.
Determine the first requester after the coding step. Select one of the
following values from the list:
Determine Requester by COA
The first requester is determined by the maintained data from the COA.
Use Requester from Invoice
The first requester is determined by the email address on the invoice.
Important
You can configure the requester determination using the same COA
logic as used to determine coders (except the first coder) and
approvers. However, this is only supported if you work with real
coders, that means, if you have two steps, first coding and then
requester. If you have configured that “coder = requester”, VIM uses
the requester field from the invoice.
Rejection Processing
Rejection FM
Enter a custom function module to customize rejection. See “Approval flow
settings function modules” on page 374.
Template: /OPT/OPTION_REJECT_TEMPLATE
370 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Additional Settings
In this area you maintain additional settings that affect the approval logic.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
Invoice Approval Configuration > Approval Workflow > Setup Approval
Chain > Mapping for Approval Flow Settings.
2. In the Mapping for Level Based Approval Settings screen, perform the
mapping, using the following parameters:
DP Document Type
Enter a specific DP document type. Alternatively, leave the field empty to
use the AFS ID maintained in this line for all DP document types that are
not configured in the Mapping for Level Based Approval Settings screen.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 371
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Activation Type
Select one of the following values from the list:
Inactive
Level based approval is inactive.
Activate by Constant
Level based approval is activated with corresponding AFS ID. You
must maintain the AFS ID field.
Activate by Determination
Level based approval is active, based on the Level Based Approval
Flow Determination Procedure. For more information, see “Maintaining
the level based approval flow determination” on page 372.
Activate by Custom Function
Level based approval is active, based on a custom function module. You
must maintain the FM to determine AFS field.
Template: /OPT/DETERMINE_AFS_TEMPLATE
Fields Determination
You can use the fields determination to filter the determination based on the
fields defined in the field determination. With baseline, the following fields are
supported for the AFS determination type: Company Code (BUKRS) and Vendor
(LIFNR)
To access the fields determination, run the /OPT/SPRO transaction and navigate
to Vendor Invoice Management > Invoice Approval Configuration > Approval
Workflow > Setup Approval Chain > Approval Flow Strategy Determination
Procedure > Determination - Fields.
Determination Type
Enter AFS (Approval Flow Settings).
The determination type AFS is defined in the /OPT/AT_DETTYPE table.
372 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Field Type
Available values are Header or Item. For the determination, only header
fields are relevant.
Field Name
Select the corresponding field of the /OPT/VIM_1HEAD or /OPT/VIM_1ITEM
table.
Sequence
Define the processing sequence of the determination.
Search Help Name
Configure the search help that will be used in the data determination
configuration.
Allow Ranges
Select this check box to allow ranges in the data determination
configuration.
Data Determination
You can use this interface to enter data for the fields you determined in the
fields determination.
To access the data determination, run the /OPT/SPRO transaction and navigate to
Vendor Invoice Management > Invoice Approval Configuration > Approval
Workflow > Setup Approval Chain > Approval Flow Strategy Determination
Procedure > Approval Flow Strategy Determination - Data.
For each combination of index fields (Company Code and Vendor), you must
configure the corresponding AFS ID.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 373
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Currency This function module returns the date for currency conversion. Based on the invoice
Conversion details, you can define a date that will be used for conversion.
Function
Module For the Currency Conversion Function Module, you can use template /OPT/
DETERMINE_CONVERSION_DATE.
Reject Function This function module returns the rejection option. Possible values are 1, 2, 3, 4.
Module These values are the only affected.
For the Reject Function Module, you can use template /OPT/
OPTION_REJECT_TEMPLATE.
Coder Determi- This function module returns coder or requester. Based on the coder details, it will
nation Function find the initial coder. If coder is equal to requester, it will consider the requester as
Module
the initial coder.
For the Coder Determination Function Module, you can use template /OPT/
DETERMINE_CODER_TEMPLATE.
374 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
ExpType
Select a unique identifier (two characters).
Description
Enter a description of the expense type.
Approval Req
Activate by typing X if the expense type requires an Invoice Approval
process.
Technical note
Table /ORS/EXPENSE_DEC stores the description and the language and table /
ORS/EXPENSE_TYP stores Approval Req and ExpType.
Value
This value determines how the rejection reason reacts when taking action in
the coding/approval process. The first value denotes the rejection reason,
the second value denotes the rejection comments. Value 1 is mandatory and
value 0 is not mandatory. Possible values:
1;0
Rejection reason is mandatory.
0;1
Rejection comments are mandatory.
1;1
Both rejection reason and rejection comments are mandatory.
The default value is 0;1.
3. In the Buttons Configuration, perform the following setting (to update the /
OPT/BUTTON table): For Function code Reject, select the Comments Required
check box. For more information about the buttons configuration, see
“Configuring buttons” on page 397.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 375
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
1. Run the SM30 transaction to maintain table /PTGWFI/Z_CONST, and locate the
record with Product Code IAP and Constant EXT_DATA_CLASS.
2. Use the constant to configure baseline class /ORS/EXT_DATA. If you want to use
the rejection reason to select from a drop-down on the rejection confirmation
screen, you must implement a custom logic within a method in class /ORS/
EXT_DATA.
Important
Take care when you change the global customization parameters. Changes can
affect the functionality of the process.
376 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
2. Define the resubmit for approval action codes, using the following parameter:
Constant Value
Maintain action codes, separated by comma.
If you want to enable the functionality to submit for approval again after a DP based
approval has been rejected, perform the following steps:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 377
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
3. Configure the DP process option, as shown in the screenshot above. For further
information, see “Configuring DP process options” on page 212.
4. Make sure the same DP process option (as above) is maintained also in the Z
constant Entries table, see screenshot below.
378 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
The DP process option should be configured as user option for the Approval
related Process Type.
2. Define the supported currency and language, using the following parameters:
Constant LANGUAGE
Determines which languages are supported in the Approval Portal. You can
maintain multiple languages by using a comma as separator.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 379
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Determines which currencies are supported in the Approval Portal. You can
maintain multiple currencies by using a comma as separator.
Default Value: USD,DEM
The “sender” is the user who has sent the inquiry to another user (recipient).
The “recipient” is the user who provides additional information on the approval
invoice.
Note: When introducing the Forward feature, Refer was renamed to Inquiry
to avoid confusion on end user side.
3. Enter the Constant Value. It indicates the number of days to wait for the
recipient to provide information.
After that period, the work item is rerouted to the sender's inbox from the
Resubmission folder of the sender's SAP Business Workplace.
1. To add a new global CALC_TAX_ON_NET constant for product IAP, run the /n/
OPT/VIM_IMG424 transaction.
380 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Value Description
X Central setting (for all document types)
G/L account amounts are to be entered net.
<blank> Central setting (for all document types)
G/L account amounts are to be entered gross.
D Individual setting for document types
Each document type can be set individually.
Technical note
The OpenText delivered code includes a popup to suggest the correct company
code for the line if the cross company coding is active and the cost center or
internal order entered in the line item does not match the company code in the
header. This feature is supported in the Approval Portal and the SAP GUI.
If the coding is done in the SAP GUI, the popup window to suggest the correct
company code is generated by a function module defined in the Z constant
POPUP_COMPANY_CODE. The OpenText default delivered function module for
this constant is /ORS/000007_POPUP_COMPANY_CODE.
2. Enter table /ORS/APPR_GL_CFG. Locate the field BUKRS and double-click. If the
field BUKRS is not displayed, add a new field.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 381
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
You can configure the notification email to include some invoice information, such
as vendor name, invoice reference number, or invoice amount. The following is an
example of a notification email:
The approval email notification depends on the user configuration. You configure
users in the COA or in the Approval Portal, on the Personalization page. For more
information, see “User Details View” on page 49 (COA) and section 8.15
“Personalizing your views of the Approval Portal” in OpenText Vendor Invoice
Management for SAP Solutions - User Guide (VIM070500-08-UGD).
Note: To send email notification, you can also use VIM Notifications. In this
case, the email is sent without the configuration in the COA or on the
Personalization page. For more information, see “Using VIM Notifications“
on page 931.
382 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
The Business object method Get_Approver_List calls the ABAP class method
sendemail of the ABAP class that implements the user mapping class. The name of
this ABAP class is configured in table /PTGWFI/Z_CONST under the entry IAP, 0,
USERMAP_CLASS. Baseline VIM uses class /OPT/CL_IAP_USERMAP_BL.
Call Sequence:
/ORS/INVAP-> Get_Approver_List
/OPT/CL_IAP_USERMAP_BL-> sendemail
/PTGWFI/CP_SENDMAIL
3. Change the configuration in table /PTGWFI/Z_CONST: Insert the new ABAP class
instead of /OPT/CL_IAP_USERMAP_BL.
7. Make sure that at least one additional SAP GUI session is available.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 383
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
&/ORS/INVAP.InvoiceAmount&
• ApprovalStatus
• CompanyCode
• Currency
• DocumentNumber
• DueDate
• FiscalYear
• GrossInvoiceAmount
• InvoiceAmount
• InvoiceDate
• InvoiceObjectKey
• InvoiceObjectType
• ObjectType
• StatusPosted
• Vendor
• VendorInvocieNumber
• VendorName
384 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Other option
Overwrite the sendemail method. See “To overwrite email sending with a
customer specific email function:“ on page 383.
Important
If no text can be found for the current value of sy-langu, then no email is
sent.
Therefore the text should be maintained in all languages that are typically used
for logon. The text is retrieved in function module /PTGWFI/CP_SENDMAIL in the
following way:
CALL FUNCTION 'READ_TEXT'
EXPORTING
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 385
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
CLIENT = SY-MANDT
ID = TEXT_ID
LANGUAGE = SY-LANGU
NAME = TEXT_NAME
OBJECT = 'TEXT'
IMPORTING
HEADER = HEADER
TABLES
LINES = TEXT_LINES
EXCEPTIONS
2. Enter the Text name, select Text ID ST (Standard text) and click Create.
386 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Depending on the application and the scenario (PO / NPO and DP / PARKED /
POSTED), fields can be configured to be changed on the screen if the user has the
corresponding authority (coding).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 387
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
List of coding You find a list of all fields that are provided for coding in structure /ORS/
fields INVOICE_ACCT_DATA. From baseline, only a subset of the fields is supported to be
posted in background using BAPI or in dialog using BDC IDs. If you want to use an
unsupported field, you must extend the relevant BDC IDs or implement the BAPI
exit.
For use in Invoice Approval, you can configure extended fields that are no baseline
fields. For more information, see section 12.6.4 “Changing BDC IDs” in OpenText
Vendor Invoice Management for SAP Solutions - Scenario Guide (VIM070500-08-CCS).
The following sections describe the configuration you need to perform for the fields.
The configuration is necessary to show the invoice detail fields when an invoice is
processed from the invoice inbox list and also when an invoice is selected from the
Process by me list.
For the coding fields, you must also configure all fields separately. This
configuration separates display functionality and the functionality to read and store
data back in the invoice line items, independent of the field status on the screen.
To configure fields for approval, you must perform both configurations, for the
invoice detail page as well as for the coding fields.
Notes
• All configuration for item fields is available for SAP GUI Approval,
Approval Portal, Mobile Approval Portal, and VIM Approve Invoices Fiori
app (Approve Invoices app) (device specific).
• For the Approval Portal, the INVOICE_DOC_ITEM field is mandatory for line
items in the Cost Assignment section of any invoice (both PO and Non PO).
• All configuration for header fields is available for Approval Portal, Mobile
Approval Portal, and Approve Invoices app (device specific). Status for
coding fields, custom fields (CUSTOM_FIELD*) and special fields like
expense type and VAT amount can be changed to be editable.
388 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
3. Configure the relevant header and item attributes field, using the following
parameters:
Field name
Unique name of the field
Page
Select the page where the field is displayed: Invoice Detail Page
Field Type
Select Header Field or Item Field.
Invoice Type
Select All Invoices, PO based invoices, or Non PO based invoices.
Device name
Select SAP GUI, Web Approval Portal, Mobile Approval Portal, Fiori
Approval Desktop, Fiori Approval Tablet, or Fiori Approval
Smartphone.
AFS ID
Select the relevant AFS ID.
Reference Field
Enter a standard data element and press the ENTER key. For example, the
ShortFieldLabel and the Long Field Label are populated. The Label fields
are visible in the Portal.
Field Status
Select the status of the field: Display, Input, Hide, or Required (not
available for line item fields).
Most of the settings will be available for Approval Portal, Mobile Approval
Portal, and the Approve Invoices app (device specific).
The Mobile Approval Portal and the Approve Invoices app provide only
display functionality. Also, header fields on all other devices will be
displayed only.
SAP GUI provides the possibility to change the status for coding fields.
Header fields are always shown on the SAP GUI screen and cannot be
hidden.
On the Approve Invoices app, header and item fields are only displayed if
the corresponding values are set (not empty). This can also be a single
value.
List Sequence
Configure the sequence of the field in the page, only for Approval Portal,
Mobile Approval Portal, and the Approve Invoices app (device specific), for
header and item fields.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 389
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Note: This is only relevant for Approval Portal and for SAP GUI. It is
not relevant for Mobile Approval Portal and for approval-related Fiori
apps (VIM Approve Invoices Fiori app and VIM Enter Cost
Assignment Fiori app).
Search Help Parameter
Enter the search help parameter for the field. For details, see “Configuring
search help for web and SAP GUI approval screen fields” on page 401.
Note: This is only relevant for Approval Portal and for SAP GUI. It is
not relevant for Mobile Approval Portal and for approval-related Fiori
apps (VIM Approve Invoices Fiori app and VIM Enter Cost
Assignment Fiori app).
Configuring You may want to read and store coding information that is not shown on the screen.
coding Therefore, you must configure all coding fields. This configuration also determines
which SAP field (DP and parked line item field) is mapped to each coding field
(used in the approval screen).
390 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Note: Fields that are not configured or that are not active will not be saved in
the line items.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 391
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Approval Portal: Web Approval Portal supports the following types of custom fields.
Supported
custom fields • Static custom fields
• Dynamic custom fields
You define the following static custom fields in the /OPT/FIELDS_V table.
392 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
You define the following dynamic custom fields in the /OPT/FIELDS_V table.
To configure the fields that must appear in the node list for Approval Portal
and Approve Invoices Fiori app:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 393
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
For the Approval Portal, users can personalize the list fields according to their
needs. This is possible on the Approval Portal Personalize page. The personalized
fields are then used in the inbox and the Processed by me list.
If no personalized preferences exist, the global default invoice list fields are
configured at the following location: Run the /n/OPT/SPRO transaction and
navigate to Vendor Invoice Management > Invoice Approval Configuration > User
Experience > Invoice List Configuration > Default Invoice List.
Note: All configuration for list fields is available for the Approval Portal, the
Mobile Approval Portal, and the VIM Approve Invoices Fiori app (Approve
Invoices app). All fields can only be display fields.
394 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
3. Configure the relevant header and item attributes field using the following
parameters:
Field name
Unique name of the field
Page
Select the page where the field is displayed: Invoice List Pages
Field Type
Select Header Field.
Invoice Type
Select All Invoices, PO based invoices, or Non PO based invoices.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 395
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Device name
Select Web Approval Portal, Mobile Approval Portal, Fiori Approval
Desktop, Fiori Approval Tablet, or Fiori Approval Smartphone (not
supported for SAP GUI).
Reference Field
Enter a standard data element and press the ENTER key. For example, the
ShortFieldLabel and the Long Field Label are populated. The Label fields
are visible in the Portal.
Field Status
Select the status of the field: Display
List Sequence
Configure the sequence of the field in the list
List Display Length
Configure the display length of the field.
No. of Characters
Configure the number of characters for the value in the field.
Data Type
Configure the data type of the field (string, char, or int). Select a data type
from the list.
3. In the WebFlow Constant Table, under Product Code IAP, navigate to the
following constants:
• EXIT_INVOICE_ACTION
• EXIT_INVOICE_DETAIL
• EXIT_INVOICE_LIST
4. If you want to configure exit function modules for invoice action, invoice detail,
invoice list, and Processed By Me list, maintain your function module in the
respective Constant Value.
The default template function modules are:
• /OPT/OAP_EXIT_ACTION
396 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
• /OPT/OAP_EXIT_DETAIL
• /OPT/OAP_EXIT_LIST
Note: Custom buttons are not supported in the Mobile Approval Portal.
If you add buttons to the Invoice List page of the Approval Portal, you must select
Button Type List.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 397
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Notes
Function code
Function code that is used to process the invoice
Page
Select the page where the button is displayed: Invoice List or Invoice
Detail Page
Invoice Type
Select All Invoices, PO based invoices, or Non PO based invoices.
Button Type
Select where the buttons are considered on the page: Header level, Item
level, or List level.
Device name
Select Web Approval Portal or Mobile Approval Portal.
SAP GUI, Fiori Approval Desktop, Fiori Approval Tablet, and Fiori
Approval Smartphone are not supported for invoice list buttons. However,
they are supported for detail page buttons.
Text
Enter the text for the button to be displayed in the portal.
Quick Info
Enter the tool tip for the button.
Button Code
Select Standard Button or Custom Button.
Standard Button
Baseline buttons are covered in this category.
Custom Button
You can define own buttons and achieve custom functionality.
User Type
Select the user to which this button is applicable: Approver, Coder, or
Everyone.
398 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
Reason Required
Select this check box to require a reason on the confirmation screen from the
user when they click the button.
Comments Required
Select this check box to require a comment on the confirmation screen from
the user when they click the button.
Log Activation
See “Custom button logging” on page 400.
Log Act. Txt.
Log Activation Text, see “Custom button logging” on page 400.
Handling Function
The Handling Function determines the RFC function that is called when
the user clicks the button in the approval screen or the Approval Portal.
Enter the function module to handle the button. Create a custom function
module by copying the sample function module /OPT/BUTTON_FM.
For buttons on the invoice list page of the Approval Portal (Button Type
List), use the sample function module /OPT/BUTTON_FM_LIST. You can use
the handling function module to call a dynamic URL.
URL
Enter the static URL to be displayed after the button is clicked.
URL Function
Enter the function module to get the URL dynamically. Create a custom
function module by copying the sample function module /OPT/
BUTTON_URL_FM.
Notes
• This field is not relevant for buttons on the invoice list page (Button
Type List).
• Either Handling Function or URL and URL Function will work;
you must decide for one of them, you cannot use both.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 399
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Modifying data VIM provides a feature to change the accounting data and header data for custom
for custom buttons. The feature can save the changed header data and item data.
buttons
The feature only works if the following conditions apply:
• Change header data or item data or both and also delete the line items.
• Copy the selected line and add as the last line item.
To maintain custom buttons, you must maintain the data in the view /OPT/BUTTONV
or use the transactions /n/OPT/OAP_DETL_BUTTON or /n/OPT/OAP_LIST_BUTTON.
Custom button VIM supports logging for custom buttons in the SAP GUI approval screen and on
logging the Approval Portal. You can customize the log comments.
To activate the custom button logging and to customize the log comments, run the /
n/OPT/OAP_DETL_BUTTON transaction for the detail screen, or run /n/OPT/
OAP_LIST_BUTTON for the list screen.
For a detailed description of all parameters in these two transactions, see “To
configure buttons for the Invoice List:“ on page 397.
The relevant parameters for the custom button logging are the following:
Log Activation
To activate the custom button logging, select this check box.
By default, the custom button logging is inactive when you install VIM. You
must activate it for all the custom buttons as needed.
For the Approval Portal, the custom button logic is there but the Approval
Portal still needs to write the logic to display the customized custom button log.
Note: In the Approval Portal, custom buttons are not handled except the
URL functionality.
400 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
13.5.13 Configuring search help for web and SAP GUI approval
screen fields
You can configure search help for web and SAP GUI approval screen fields to give
users input help for these fields.
1. Run the /OPT/SPRO transaction and navigate to Vendor Invoice Management >
Invoice Approval Configuration > User Experience > Invoice Detail
Configuration > Maintain Invoice Detail Fields.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 401
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
3. Configure the search help, using the following parameters (at the bottom of the
screen):
Notes
402 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.5. Implementing Invoice Approval
• Call the SE11 transaction to find the search help and also to display the
attributes of the search help.
• You can maintain different search helps for different devices. SAP GUI
approval screens are not limited to elementary search helps.
GL_ACCOUNT
Search help name = SAKO_CORE
SearchHelpParam = SAKNR
COST_CENTER
Search help name = TRAC_KOSTL
SearchHelpParam = KOSTL
COMPANY_CODE
Search help name = H_T001
SearchHelpParam = BUKRS
MATERIAL
Search help name = H_WERKS_MATNR_E
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 403
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
SearchHelpParam = MATNR
INTERNAL_ORDER
Search help name = ORDEA
SearchHelpParam = AUFNR
TAX_CODE
Search help name = SH_T007A
SearchHelpParam = MWSKZ
NETWORK_NO
Search help name = AUKOB
SearchHelpParam = AUFNR
WBS_ELEMENT
Search help name = PRPMA
SearchHelpParam = POSID
When the invoice is parked for approval, it is sent to the coder first. The following
coder definitions are possible:
By requester
Each requester has an associated coder.
By company
Each company code has an associated coder.
Both
The coder is determined by both requester and company code.
Use requester
The coder is the requester.
404 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.6. Roles in the IAP process
Configuration The configuration for level based approval is done in the approval flow settings
(AFS). For more information, see “Configuring approval flow settings” on page 365.
The following sections describe user map maintenance and Chart of Authority
(COA) maintenance. For a detailed description, see “Maintaining Chart of
Authority” on page 47.
The definition table for approver persona attributes is /OPT/BL_AP_CONF, which can
be maintained by the SM30 transaction.
Alternatively navigate to OpenText Vendor Invoice Management > SAP menu >
Roles > Coder/Approver Options Configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 405
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
The following check boxes for the approver persona are available:
Approval Flag
Select this check box always.
Approver access rights – Approve or reject an invoice; enter comments.
Coding Flag
Select this check box to achieve that the approver is able to enter accounting
data.
In level based approval, the accounting information can only be entered either in
the coding level (level 0) or in the requester level (level 1). If the requester is
maintained as coder, the requester is able to enter and change the accounting
information. In this case, there is no coding level.
Note: In the approval levels (level 2 and higher), coding is not supported.
You might want to remove the following buttons from the Approve Invoice
screen, both in the SAP GUI and in the Approval Portal:
406 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.6. Roles in the IAP process
Coding Display
Select this check box to achieve that the coding block is displayed.
If Coding Flag is selected, the coding block is always displayed in change mode.
If Coding Flag is cleared, you can use the Coding Display check box to display
or hide the complete coding block.
Note: The Coding Display check box only takes effect in the SAP GUI
approval.
Coding Delegate
Select this check box to achieve that the approver is able to delegate the coding
to others.
In level based approval, the Coding Delegate check box enables or disables the
forward button in the coding level.
If Coding Delegate is selected and, additionally, Coding Flag or Coding
Display is selected, the buttons I will enter accounting information and I want
someone else to enter accounting information are displayed.
If only Coding Delegate is selected (and no Coding Flag or Coding Display
check box), the buttons are not displayed. In the approval screen, you can
delegate the coding. The Please Specify the Coder field is displayed directly.
Approver access rights – Specify a Coder, which means a specialist to enter the
accounting information.
Configuration
Select this check box to achieve that the approver can set the persona for the next
approver.
Approver access rights – Determine next approver’s access options.
Override
Select this check box to achieve that the approver can override the system
generated next approver.
Approver access rights – Override the system-proposed next approver.
Look Ahead
Select this check box to achieve that the approver is able to retrieve all the
approvers.
Approver access rights – View the entire approval chain or pre-determine all
the approvers.
In level based approval, the look ahead option is obsolete.
Custom Flag 1
Select this check box to indicate the expense type as read only.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 407
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Custom Flag 2
Select this check box to indicate the approver as a delegated coder.
Custom Flag 3
Not used
The log event is written to the approval log file /ORS/APPL_LOG, whenever the
invoice is approved and an override approver has been entered.
The event is shown in the approval log:
408 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.6. Roles in the IAP process
The entry does not show directly who executed the override action. To find this
out, look at the corresponding action entry, which has the same time stamp.
Coding delegation
If the current coder/approver does not have all the knowledge to provide the
correct coding, the current coder/approver may delegate to another coder. To do
so, the approver persona needs to have the CODING_DELEGATE check box
selected.
Substitution
The approver or coder can set up personal substitutes to temporarily take over
their responsibility. The substitute can be defined by one of the following ways:
• If the optional Web IAP is implemented: From the approval web page, open
the User Preference page and open the Substitution section.
• From the SAP inbox, add substitute from the SAP menu.
Substitution features
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 409
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
You can control these options using the Substitutes inherit COA check box
in the Approval Flow Settings for the respective AFS ID; see “Configuring
approval flow settings” on page 365.
• The invoices belonging to the original approver will be added to the
substitute's invoice list.
• When the substitute approves an invoice that is not originally sent to the
substitute, the action will be logged as XXX approves the invoice on behalf
of YYY.
• The original approver can place limitations when setting up the substitute.
Normally, the names are searched by the Name Search method /ORS/
000007_NAME_SEARCH of the usermap class. The method can be customized
to include a logic that restricts the list of legible substitutes to those with
equal or higher authority of the original approver.
• To restrict the substitution to only VIM workflow tasks, currently only one
substitution profile can be maintained for all VIM workflows. The
substitution profile can be created using a standard SAP method and
assigned to VIM workflow tasks.
Reassign
When an employee is not supposed to approve invoices anymore, the
administrator can use the Reassign utility to reassign the work item to others.
The Reassign utility may “recall” the invoice back to the AP department. Once
recalled, the approval workflow is terminated. The AP department may
resubmit the invoice for approval. For more details, see section 14 “Reassigning
work items belonging to another user” in OpenText Vendor Invoice Management
for SAP Solutions - Administration Guide (VIM070500-08-AGD).
410 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.7. Configuring header based approval
To do this, you can implement a custom logic in the method NEXT_ALT, which is
introduced in VIM 7.5 SP6 (VIM 7.0 SP10).
1. To access the Approval Flow Settings screen, run the /OPT/SPRO transaction
and navigate to Vendor Invoice Management > Invoice Approval
Configuration > Approval Workflow > Setup Approval Chain > Approval
Flow Settings.
5. To access the Mapping for Approval Flow Settings screen, run the /OPT/SPRO
transaction and navigate to Vendor Invoice Management > Invoice Approval
Configuration > Approval Workflow > Setup Approval Chain > Mapping for
Approval Flow Settings.
6. To map your customized AFS ID to the wanted VIM Document Type, add the
AFS ID in the mapping configuration.
For more information, see “Maintaining the approval flow settings mapping”
on page 371.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 411
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
7. To determine the user that gets assigned the approval work item, configure the
COA, Approval Category column. For more information, see Approval
Category on page 55.
If an invoice can be sent to multiple approvers, the found approvers are displayed as
a list on the approval confirmation screen. This is possible only when transitioning
to the next level. Therefore only the last approver (or coder) in each level is shown
the list with multiple approvers.
Note: The approvers cannot be overridden in this case, unlike in the case of
sequential approval.
At the Approval level, you can forward an invoice only to an approver that can
approve at least all the line items assigned to the current approver, according to the
COA settings.
If an invoice is rejected at the Approval level, all other parallel work items are
cancelled. The invoice is routed according to the AFS settings, for example One Step
Back. For details, see Rejection Processing on page 370.
In case of the option One Step Back, the invoice returns to the previous approval
level.
VIM Analytics In the Processes tab of the VIM Analytics report, the invoices that are currently sent
to multiple parallel approvers are displayed with one line for each agent.
In the Unified Dashboard approval log dialog box, the text Multiple approvers
exist is displayed instead of the approver name. A button to display the approvers
list is placed next to this text.
412 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.8. Configuring level based approval features
An invoice gets approved at levels 1 (requester) and 2 (approver), and then gets
rejected at the approver level 3, going back to the requester level.
VIM provides the approval buffer. If the approval buffer is active and the line items
have not been changed, the following approval at requester level leads to the invoice
being sent to the approver at level 3, bypassing level 2.
You can enable the approval buffer for individual AFS IDs. For more information,
see “Configuring approval flow settings” on page 365.
Conditions With the approval buffer enabled, approval of a specific line item is skipped in the
level if the following conditions apply:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 413
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Final approval The final approval is not considered. Final approval steps must be repeated.
Approval flow The approval buffer functionality is implemented only for approver levels (2 and
higher). Both sequential and parallel line-based approval flows are supported.
Header-based approval flow is not supported.
Line item All accounting information fields are considered when comparing line items against
information their earlier state.
Substitution When using substitution during the approval, some line items might be approved
not by their originally assigned approvers but by their substitutes. The check,
whether the last approver of the line item is still allowed to approve it, is done with
the actual approver, that means with the substitute.
Logging The approval steps simulated through the approval buffer are shown in the
extended approval log for the last dialog approval step that is executed. In the
extended approval log, the name of the approver who approved the lines earlier are
shown for simulated steps. The simulated steps are not shown in the standard
approval log.
You can enable the skipping logic for individual AFS IDs. For more information, see
“Configuring approval flow settings” on page 365.
The following diagram illustrates how skipping of COA levels works. In the
example, there are no approvers maintained in the COA at level 2, but there are
approvers maintained at level 3. The invoice skips level 2 and is directly sent to the
approver at level 3.
414 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.9. Down payment approval
Restrictions The functionality of skipping the COA levels is implemented only for approver
levels (2 and higher). Both sequential and parallel line-based approval flows are
supported. Header-based approval flow is not supported.
Logging The approval steps simulated by skipping the COA levels are shown in the extended
approval log for the last dialog approval step that is executed. In the extended
approval log, no approver is shown for simulated steps. The simulated steps are not
shown in the standard approval log.
The skipping logic is only active when an invoice proceeds from one approval level
to the next one. Only at this point, the system decides whether skipping is possible.
If COA is changed after that and some approvers are removed, so that no approvers
can be found for some lines at the current level, skipping to the next level will not be
attempted. In this case, the last valid approver gets an error message that the next
approver cannot be found.
The decision to skip is taken one level below the first level where the COA is not
maintained completely. Therefore, it is important to ensure that, at the level where
the approval workflow begins, no skips are required. It is no problem if invoices are
going through coder or requester step. But you might use posted approvals or
autocoding, which is followed by an approval workflow starting directly at the
approval level, that is level 2. In this case, make sure that the first approver level has
the COA completely maintained because there is no “previous level” where the skip
decision can be made. If the level approvers cannot be found for all lines, an error
message will be displayed even when skips are active.
Note: The same invoice might be rejected and might pass through the
approvals once again. In this case, the skipping logic is active at the level
before the last one, and the error does not happen.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 415
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Within baseline delivery, down payment approval follows header based approval.
Coding and coding delegation is not possible, irrespective of the coder configuration
in the AFS settings.
1. Down payment approval starts at approval level 2 directly. The requester who is
maintained in the invoice is considered as first approver.
2. After the requester approves at level two, the invoice moves on to higher levels
based on the invoice amount. The next approvers are determined based on COA.
3. If the requester is not authorized to approve at level 2 due to COA, the invoice is
forwarded to the next approver at level 2 based on COA. From there, it moves
on to higher levels based on the invoice amount.
Note: Approval data in COA must be maintained for expense type DW (Down
Payment). Approval limits for level 0 and 1 must as well be maintained with
nominal amounts in COA.
416 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.10. Coding validation
1. Run the SM30 transaction to maintain table /PTGWFI/Z_CONST, and locate the
record with Product Code IAP and Constant NPO_INV_CLASS. Enter Constant
Value /ORS/NON_PO_INVOICE_NEW.
2. Run the SM30 transaction with table /ORS/APPR_GL_CFV.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 417
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
a new BAdI object and activate it (see “To modify the validation code for
Company_Code:“ on page 419).
7. Test /ORS/COMPANY_CODE.
418 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.10. Coding validation
1. If you want to modify the validation code for Company_Code, create your object
and implement it:
Run the SM30 transaction and change the BAdI name from Company_Code to
ZCompany_Code (for example).
2. Click the BADI Implement button and create a new BAdI, called
Z_COMPANY_CODE (for example).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 419
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
5. In Defined filters, select ZCOMPANY_CODE from the drop down list and save.
420 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.10. Coding validation
8. Test Z_COMPANY_CODE.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 421
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
422 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.10. Coding validation
Field
BAdI
G/L Account
/ORS/CL_IM_GL_ACCOUNT
Internal Order
/ORS/CL_IM_INTERNAL_ORDER
Item Text
/ORS/CL_IM_ITEM_TEXT
Material
/ORS/CL_IM_MATERIAL
Plant
/ORS/CL_IM_PLANT
Profit center
/ORS/CL_IM_PROFIT_CENTER
Tax Code
/ORS/CL_IM_TAX_CODE
Trading Partner
/ORS/CL_IM_TRADING_PARTNER
Unit
/ORS/CL_IM_UNIT
Valuation Type
/ORS/CL_IM_VALUATION_TYPE
WBS Element
/ORS/CL_IM_WBS_ELEMENT
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 423
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
You can enable or disable this check with a specific Z constant, product code IAP,
constant SKIP_BAPICHECK, description If set to 'X', BAPI check will not be
processed in Coding / Approval.
424 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.11. Configuring the profitability segment feature
Message Class
Enter the name of the message class that contains the message to be
excluded.
Message ID
Enter the number of the message to be excluded.
Active
Select this check box to activate the exclusion of the message in the approval
validation.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 425
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
2. In the Maintain Profitability Segment Fields screen, enter the Company Code
and click Get Fields.
3. To activate the profitability segment functionality for the given Company Code,
perform the following settings:
426 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.11. Configuring the profitability segment feature
Limitations
EXIT_ADD_FIELDS
While displaying the fields in the portal: can add or delete extra fields to or from
the existing list of fields based on any conditions
EXIT_BDC_BG
If any issue occurs during posting the data in the background mode with the
profitability segment data, the user can modify the profitability segment data
according to their needs.
EXIT_DATA_CHG
Can overwrite the data of the profitability segment before displaying the pop up
EXIT_DEL_VALID
Can add custom validations for portal before deleting profitability segment data
EXIT_MSG_CHG
Can add custom validations on the profitability segment number. Or can modify
or delete the existing messages according to your needs.
EXIT_READ_VALID
Can add custom validations for portal before displaying the pop up
EXIT_STOR_VALID
Can add custom validations for portal before saving the profitability segment
data
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 427
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
428 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.11. Configuring the profitability segment feature
IM_CALL_SYS
Importing parameter. It provides information from which system the error
message is coming. The value should be either SAP or WEB (Portal).
IM_MSG_AREA
Importing parameter. It provides the exact location from where the message is
coming. Possible values are 1, 2, 3, or 4.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 429
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
1
The message is coming from the portal when validating the existing
profitability segment number. This validation has been performed in the
function module /ORS/000007_PROFIT_SEGMENT.
2
The message is coming from SAP when validating the existing profitability
segment. The validation has been performed in the function module /ORS/
VIM_SAVE_PSEG.
3
The message is coming either from SAP or WEB (Portal) when validating the
newly created profitability segment number. The validation has been
performed in the function module /ORS/VIM_SAVE_PSEG.
4
The message is coming from SAP during posting time when validating the
existing profitability segment number.
EX_EXIT
Exporting parameter. Use this parameter if the user wants to exit without
further processing. The values should be either <blank> or X. X means exit
without further processing.
CH_MESSAGE
Changing parameter. It imports the actual message into the function module.
According to your requirements, you can modify or delete the existing messages
and you can add your own custom messages.
CH_PAOBJNR
Changing parameter. It imports the problematic profitability segment number.
According to your requirements, you can modify the profitability segment
number.
430 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.12. Logging and monitoring in Invoice Approval
Each step in the approval flow leaves log records, which can be viewed later, for
example for audit purposes. Basic information, for example who approved or
rejected an invoice and when, is being logged for the approval flow.
VIM supports advanced logging for level based approvals, allowing you to see the
accounting data at each step. This can help in reconstructing the accounting data
change history and explaining why the invoice was sent to a particular approver and
was (or was not) approved.
The advanced logging is available from the display of basic logging, for the steps or
actions that can affect the approval flow. The changes of accounting data, approvals
and rejections are recorded; entering the comments is not. For more information, see
“Using the extended approval log” on page 433.
Basic log The basic approval log can be shown from the following locations:
locations
• VIM Workplace, DP dashboard, and DP document display: History pane,
Approval History
• Approval dashboard:
Extended log The extended log can be shown only in SAP GUI screens, wherever basic log is
locations shown. An additional column Display item details shows the Display item details
button for steps where the extended log is available.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 431
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
• PDF History Log. For more information, see “Using the PDF history log for
Invoice Approval” on page 434.
To display the Invoice Processed By <Username> table, enter the Approver and
optional additional search criteria, and click in the application toolbar.
The columns displayed in the result list are retrieved from the fields that are
maintained in the user preferences for the corresponding user. See “User Details
View” on page 49. The invoice list fields are reused.
3. Select the Add to screen check box for the search field name. All other fields are
currently not in use.
432 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.12. Logging and monitoring in Invoice Approval
In the following example, three invoice lines were approved by the user at level 1
(requester level).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 433
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
If implementing the optional Approval Portal, the Approval Portal uses the
following infrastructure for displaying the images from the web browser during the
IAP process.
1. Clicking the View Invoice Image link in the Approval Portal will call SAP ERP
with the following function module:
FUNCTION /ORS/000007_IMAGE_DISP_URL or /ORS/000007_IMAGE_DISP_JPEG
2. This function module will in turn call a configurable function module that is
defined in the OpenText /PTGWFI/Z_CONST table, Product Code IAP. The
constant for Image Display JPEG is IMAGE_DIS_JPG_FM. The constant for Image
Display URL is IMAGE_DIS_URL_FM.
3. The data that is passed to this pluggable module is:
434 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.13. Enhancing Invoice Approval using extensions
Example: By modifying/extending the method NEXT, you can implement your own logic to
determine the approvers in the approval process.
With the new level based approval flow, you must configure the class on document
type level in Approval Flow Settings (AFS); see “Configuring approval flow
settings” on page 365.
Constant Value
Maintain the custom approval class. This class should conform to the /ORS/
APPROVER class (sub type).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 435
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
With the new level based approval flow, you must configure the class on document
type level in Approval Flow Settings (AFS); see “Configuring approval flow
settings” on page 365.
The Z constants mentioned in this section are used when no AFS ID is found for the
respective DP document type in the approval AFS ID mapping. A typical example
for this in a baseline configuration is a PO invoice.
2. Define the custom invoice class (exit), using the following parameter:
Constant Value
Define the custom invoice class. This class must be a subtype of /ORS/
NON_PO_INVOICE.
You can use this class to extend the following methods:
VALIDATEACCTDATA
Validates the accounting data of invoices.
PROCESS_RETURN_MSG
Formats the return message from SAP ERP to something meaningful
that can be displayed on the web.
436 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.13. Enhancing Invoice Approval using extensions
GET_NO_CODING_MSG
Returns a message if there is no coding information on the invoice.
CHECK_COBL
Is used to validate the coding block data on the invoice.
CONVERT_STD_FIELD
Converts the value of a field from input format to output format.
GET_FIELD_STATUS_GRP
Sets the display parameters (Optional, Required, Hidden) for invoice
fields while coding.
3. Define the custom invoice class (exit), using the following parameter:
Constant Value
Define the custom invoice class. This class must be a subtype of /ORS/
PO_INVOICE_NEW.
VALIDATEACCTDATA
Validates the accounting data of invoices.
CONVERT_TO_RSEG_FORMAT
Converts the value of a field from input format to output format.
With the new level based approval flow, you must configure the class on document
type level in Approval Flow Settings (AFS); see “Configuring approval flow
settings” on page 365.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 437
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
Constant Value
You can use this custom class to modify or extend the standard usermap
functionality. Methods of class /OPT/CL_IAP_USERMAP_BL can be extended.
2. Locate the record with Product Code IAP and Constant BULK_VALIDATE_EXIT.
Note: Simple Email Approval is not a product feature that will be extended in
the future but it is an example implementation. OpenText recommends using
OpenText Approval Portal or the VIM Approve Invoices Fiori app. Simple
Email Approval is not supported by OpenText Customer Support, and
OpenText does not plan to further develop this.
Name
Simple Email Approval
438 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
13.14. Simple Email Approval
Roles
Manager - Procurement
VIM roles
Typical users are managers in an organization. Managers in this understanding
are, for example, cost center owners, project managers, managers of
organizational units.
Overview
Simple Email Approval adds an interface to the user to approve or reject
invoices using their email inbox. It gives instant notifications about the approve
or reject actions when the user clicks the Approve or Reject links provided in
the email. Simple Email Approval is an example version of the REST API
component, deployed along with Approval Portal.
Prerequisites
The following components are required to run Simple Email Approval:
• VIM package
• Approval Portal package deployed and running
You can configure the application settings within the VIM Invoice Approval
configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 439
VIM070500-08-CGD-EN-01
Chapter 13 Invoice Approval
2. Click New Entries and configure the Approval Portal link using the following
parameters:
Application Type
Simple Email Approval OAP
Application URL
Web Approval Portal URL (for both NetWeaver and standalone portal
servers):
http://<host name>:<port number>/vimportal/api/v1/approvals/
html/
Example: http://mucr3d9e.opentext.net:50000/vimportal/api/v1/
approvals/html/
Note: All Simple Email Approval functionality details are tracked using the
staging table /OPT/EMAIL_APPR.
Security You can handle Approval Portal URL security using reverse proxy or web
dispatcher (mobile security in guides).
440 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 14
VIM provides the following apps that are based on Business Center Fiori Task App,
which is based on SAP Fiori®:
• VIM Confirm Quantity and Price Fiori app (Confirm Quantity and Price app)
• VIM Resolve Invoice Exceptions Fiori app (Resolve Invoice Exceptions app)
• VIM Enter Cost Assignment Fiori app (Enter Cost Assignment app)
• VIM Approve Invoices Fiori app (Approve Invoices app)
This chapter provides a general overview on these apps and describes the necessary
configuration to use each of them.
• Name
• SAP Fiori roles
Note: For the VIM Fiori apps, the following sections provide information to
which roles of the SAP Fiori App Library (https://
fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer) these apps
fit. The VIM Fiori apps are not part of the core SAP Fiori App Library. They
are delivered only as part of VIM.
• App details and VIM roles: explanation with reference to VIM roles and use cases
• Key features: most important features. Details how to use the app and app
features are described in OpenText Vendor Invoice Management for SAP Solutions -
User Guide (VIM070500-08-UGD).
• Limitations (if relevant)
Note: For information about semantic object navigation, see section 8.2.1
“Semantic object navigation with the Fiori Task App” in OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD). For the link
type Semantic object navigation, the following prerequisites apply:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 441
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
• Employee – Requisitioner
• Display only the items that require confirmation (no GR/IV), have potential
payment blocks (GR/IV) or are posted with price or quantity payment blocks
(posted PO invoices)
• Post a good receipt for selected line items
• Provide suggestions on further processing for each line item with drop down
selection and additional comments
• Display history data and invoice image
• Confirm the step by sending the invoice for further processing by AP
department
Limitations
442 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.1. General overview
Note: This app requires simulation support of SAP MM-LIV BAPI provided
with the SAP note 1694508 or corresponding SAP support package.
• Employee - Procurement
• Purchaser
• Warehouse Clerk
• Other roles depending on configuration and requirements
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 443
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
Notes
Key features
Name
444 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.1. General overview
Limitations
Complex invoices are not supported. This includes the following:
• credit memo
• mix of credit/debit lines
• more than one cost object type
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 445
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
• balance issue
Complex invoices are routed to the Approve Invoices app. You can distinguish
them by the remark Approve coding completed by <user>. See comments in
History. above the headline.
Alternatively, the remark can read: Coding cannot be completed in Fiori.
Please continue in SAP GUI.
• Employee - Procurement
• Manager - Procurement
446 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.1. General overview
Key features
Limitations
• The Certify message (see “Configuring the Certify message” on page 386) is
not automatically displayed in the Approve Invoices app.
• Custom buttons (see “Configuring buttons” on page 397) are not
automatically displayed in the Approve Invoices app.
• Search helps (see “Configuring search help for web and SAP GUI approval
screen fields” on page 401) are not automatically displayed in the Approve
Invoices app.
• Manager - Procurement
• Click the Multi Select button to select multiple invoices for approval that are
ready for only approval and that are assigned to your inbox by the
VIM approval workflow logic.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 447
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
• You can also perform Approve or Reject actions on the invoices from the
Invoice List using Direct Approve and Direct Reject icons that are assigned to
your inbox by the VIM approval workflow logic.
• You can also perform Approve, Reject and other actions on the invoice by
navigating to the detail perspective shown in the Approve Invoices app.
Typical users are higher level managers in an organization, for example cost
center owners, project managers, managers of organizational units, and
Enterprise VP.
This role is called approver in VIM. Approval is mostly relevant for Non-PO
invoices. In case of PO invoices, the approval has been done for the
PO. Approvers check the details of a Non-PO invoice and approve or reject
according to company spending rules (approval level compared to invoice
amount). Rejection can be necessary in cases where the invoice is not correct or
the account assignment needs to be changed (for example incorrect cost center).
Key features
• The full screen pattern displays the Invoice List with Direct Approve and
Reject.
• The following new filters are added: Invoice Status (Approved Invoices
(multi-select) and Rejected and other invoices) and Last Processed By.
• The following new columns are added: Last Processed by and Comments
(last processed comments).
Supplier (Vendor)
https://fioriappslibrary.hana.ondemand.com/sap/fix/
externalViewer/index.html#/detail/Apps('F1861')/S9OP
Odata Service
C_SUPPLIER_FS_SRV
448 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.1. General overview
Limitations
• Invoices that are not eligible for Approve or Reject are shown with a
clickable Information icon. The Information dialog is shown with a relevant
message. You can perform relevant actions by navigating to the Invoice
Detail page by clicking the field Reference Number.
• Consider performance issues when selecting more invoices for bulk
approval.
• The Approve Invoices (bulk mode) app is supported only in the desktop
version, not for tablet and mobile phone.
• The Comments Mandatory check is not applied to Bulk Approve. By default,
comments are optional.
• Only the Bulk Approve action is supported. Make sure that the Approval
COA configuration for approvers is enabled with Bulk Approval Category
“A - Approval” or “B - Approval and Reject”.
• Employee - Procurement
• Manager - Procurement
• Invoice approved
• Financial information entered
• Sent for reference
• Data entered and invoice approved
• Attachment deleted
• Invoice rejected
• Invoice sent to approver
• New attachment
• Invoice forwarded
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 449
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
• Comment entered
The My Approved Invoices app can be used for all roles involved in the
approval process, like requester, coder, and approver.
Key features
• Search, sort or filter invoices with own interaction within the approval
process
• Display the image of the invoice and its attachments
• Access invoice information and history of the invoice
• Employee - Procurement
• Manager - Procurement
• Accounts Payable Manager
450 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.2. Integrating VIM Fiori apps into Fiori launchpad
Note: The current version of the Invoice Analysis app is an example Fiori
app to demonstrate how VAN information can be provided as an
analytical Fiori App. This app is included into the product to demonstrate
this option but it is currently not fully supported for use in production:
Selection fields and result columns are hard-coded. The app can only be
adjusted to other requirements by copying the app into the customer name
space. Any change to the app requires Fiori/UI 5 development and changes
to the ODATA service. Based on these considerations, OpenText does not
guarantee to fix issues related to the app: From a support point of view, the
app is not part of the fully supported product scope but should only serve
as an example.
Technical hints
Unlike the other VIM Fiori apps, the Invoice Analysis app is not based on
OpenText Business Center for SAP Solutions.
For more information about the Invoice Analysis app, see section 4 “Invoice
Analysis app: Simple VAN on mobile or web devices” in OpenText Vendor
Invoice Management for SAP Solutions - Reference Guide (VIM070500-08-RGD) and
part XVI “Vendor Invoice Management ABAP Invoice Analysis app components
installation” in OpenText Vendor Invoice Management for SAP Solutions -
Installation Guide (VIM070500-08-IGD).
The general setup is described in section 9.1.1 “Integrating Fiori Task App into Fiori
Launchpad” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD). Import the mentioned transport or configure the tiles.
The tiles are also delivered with transports, which are stored in the file
VendorInvoiceManagement-LaunchpadContent.zip for On premises. You can
download this file from My Support: https://knowledge.opentext.com/knowledge/
llisapi.dll/Open/71941132.
Note: The zip file has been created for VIM 16.3 but it is also compatible for
VIM 7.5 SP7 and later.
Several additional packages are delivered along with this SP that are required for
VIM Fiori apps. The following table lists the delivered files, specifying the related
deployment scenario. All files are to be found in the same directory where the
components packages for the VIM Business Center solution are located.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 451
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
The following Fiori tile catalogs are delivered. You can assign them to the related
role used in the corresponding business scenario.
/OTBCWUI/PS30_VIM
Vendor Invoice Management
/OTBCWUI/PS34_VIM
Vendor Invoice Management - Supplier Self Service
/OTBCWUI/PS34_VIM_ACC
Vendor Invoice Management - Supplier Accountant Perspective
Parameters for When setting up tiles for VIM, you need to know specific parameters for each Fiori
manual configu- Task App. They are listed in the following table.
ration
452 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.3. Configuring the Confirm Quantity and Price app
Note: To support PO invoice simulation used by this app, implement the SAP
Note 1694508 in the SAP ERP system, unless already present.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 453
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
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.
417 - Quantity/Price Confirmation Required (PO)
The actual Fiori app step. A dialog work item for this step is also visible in
the SAP GUI inbox, but the dashboard has only the Rerun rules option
configured in standard VIM, because it is supposed to be processed from the
app. The process type has a special workflow type, which is the criteria for
work item selection by the app:
Use the process types in the following sequence: 425, 418, 417, 418. OpenText
recommends that you keep the group as close to the approval and posting as
possible, to ensure that the DP document has validated and complete data and
the posting simulation can be performed.
DP process options
The standard process option 2051, Send to FIORI app Confirm invoice
quantity and price, is used in the process type 418 to send the document to the
Fiori app if automatic start is not used. This process option is delivered in a BC
set.
454 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.3. Configuring the Confirm Quantity and Price app
You must maintain the settings separately for price discrepancies (Payment in the
column ID) and quantity discrepancies (Delivery in the column ID). It is possible to
maintain settings depending on the company code (ranges are allowed).
Note: The app does not perform checks of the configuration. If you choose to
use company code based configuration, you must make sure that there are no
overlapping settings.
If blocked workflow is active and will be processed with the app, the dropdown
entries must have process option type and ID maintained but this is not required or
used by DP process.
CC from / CC to
Company code from/to. Maintain the required company code(s). This field is
optional.
ID
Click Payment for price discrepancy option or Delivery for quantity
discrepancy option.
Counter
Provide a counter for the option.
Note: The value must be greater than one (1). Within the ID (Delivery or
Payment) the counter has to be unique.
Active
Select this check box to activate the dropdown option value.
Add. value
Additional value. Select true if selection of the dropdown has to enable the
additional quantity field. In the standard configuration, this is used for the
option Wrong quantity, when the GR quantity to be posted needs to be
provided. Currently this functionality is limited to the quantity field.
Description
Option text shown on the Fiori screen.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 455
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
Note: On the menu, click Goto > Translation to provide translations for
selected options.
Long field label
Enter text for the optional quantity field. For more information, see Add. value
on page 455.
GR options
Selecting specific dropdown values for quantity discrepancy can result in
posting of a goods receipt. The quantity of the GR is calculated depending on
the data (“delta value”) and the selected GR option:
Comment mandatory
Select this check box to make a comment in the confirmation dialog box
mandatory.
Option Type
Enter the option type of the standard process option of the blocked workflow.
Currently, only Authorization must be entered for the dropdown entries used
in the blocked workflow for quantity discrepancy.
Option ID
Enter the option ID of the standard process option of the blocked workflow. This
must be one of the Authorization options. The option ID associated with the
dropdown will be shown in the process log of the blocked invoice workflow.
If an item is accessed from the inbox, a staging entry is created and after that the
dropdown values are created. You need to clean drafts using the /OTX/
PS35_DROP_ALL_DRAFTS program to reflect the changes.
2. Select the check boxes Drop all existing drafts and Do you really want to
delete?
4. Access the Fiori app and check whether delivery dropdown values are
displayed.
456 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.3. Configuring the Confirm Quantity and Price app
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 457
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
4. In the node Web Services > Workplace > Nodes, perform the configuration of
the initial sort order:
Select the node ID PS35_VIM_MPOEX_INV and perform the required changes in
the subnodes for Search fields, Sort fields, and Filter fields:
2. Select the work object type PS35_VIM_MPOEX and double-click Master List -
Data Binding in the Dialog Structure.
458 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.3. Configuring the Confirm Quantity and Price app
3. Perform the required changes. The following screenshot shows the standard
configuration:
1. Run the SM30 transaction (table maintenance) and enter the view /OTX/
PF62_V_OH.
2. In the dialog box that opens, enter the work object type PS35_VIM_MPOEX.
3. Configure the header fields. The following screenshot shows the vendor
number added to the standard display of the vendor name:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 459
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
2. In the customizing nodes that are shown, navigate to Business Center - Web
Services - Deprecated Activities > Items > Item Header Details.
3. Add or modify the records with the work object type PS35_VIM_MPOEX. The
following screenshot shows the vendor name added to the standard display:
460 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.3. Configuring the Confirm Quantity and Price app
You can configure, based on the document company code, whether the document
will be sent into the app immediately.
To do this, run the /n/OPT/SPRO transaction and navigate to Fiori Configuration >
Confirm Quantity and Price > Confirm Quantity and Price Customizing for Start.
In the standard configuration, no settings for automatic start of the Fiori app step are
delivered. An example entry for company code 1000 is shown in the following
screenshot:
The frequency of the job runs depends on the business needs. It must be run more
frequently to make the header level work items start faster after finishing the line
level steps in the SAP GUI dashboard or with the Fiori app.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 461
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
Prerequisites
Process step handling with the Resolve Invoice Exceptions app supports the
following:
• Displaying header and line item information, history and comments, attached
documents
• Entering comments
You also may perform the following project-specific implementations. But be aware
that OpenText Customer Support will not support them beyond regular product
support.
Known issues Generic refer to any user is not possible, refer is based on role assignment.
and restrictions
Authorizations When accessing the work list, the following authority objects are checked.
Vendor Check
Check of Authority Object F_LFA1_BEK (Authorization Group in LFA1)
462 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.4. Configuring exception handling with the Resolve Invoice Exceptions app
Note: Example customizing for a sample set of process types and the role Info
Provider is delivered in the BC set of the VIM Foundation (/OTX/
PS03_VIM_003). You can add other process types to the customizing if needed.
For more information, see “Assigning process options” on page 470.
The following example takes up the info provider scenario. This means, the AP
processor needs additional information to process an invoice.
5. As the selected user, check the comments and the invoice data.
6. To send the invoice back to AP, click Send to AP and provide a comment.
14.4.2 Architecture
The Resolve Invoice Exceptions app is implemented as a solution for Business
Center. It offers the VIM Fiori integration framework to handle VIM exceptions in
the Resolve Invoice Exceptions app. The VIM Fiori integration framework supports
custom scenarios based on Fiori.
You configure the interface to the Resolve Invoice Exceptions app by a solution-
specific web handler implementation. The web handler class calls RFC modules to
support multiple backend scenarios. Within the RFC modules, a process controller
class is called to provide data, solution specific customizing and control action
handling.
Actions in Fiori are based on the VIM process options. For each process option, you
must implement a class to provide the needed functionality. In the delivered process
option classes, an interface is called. This interface controls the actual VIM
workflows.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 463
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
To define work object types for the Resolve Invoice Exceptions app:
464 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.4. Configuring exception handling with the Resolve Invoice Exceptions app
3. Configure the work object type details, especially the ones in the following list.
Note: For general information about work object type definitions, see
section 7.1.1 “Defining work object types” in OpenText Business Center for
SAP Solutions - Configuration Guide (BOCP160302-CGD).
Handler class
/OTX/PF03_CL_DATA_HANDLER_DYN
The generic selection of the Business Center framework is used to get the
work list for the current user. In the dynamic data selection, the View /OTX/
PS31_V_RG01 is used to retrieve the user specific work item list.
Selection Exit
/OTX/PS31_CL_CHANGE_SELECT
You can use the selection exit to change the selection of the work list. In the
delivered solution, it restricts the work list according to authorizations and
to the configured process options and roles.
Display Structure
/OTX/PS31_S_DISP
The display structure defines the available field in the work list.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 465
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
To configure the web handler for the Resolve Invoice Exceptions app:
2. In the Work Object Type Overview screen, assign the PS31_VIM_WEB work
object type to the /OTX/PS31_CL_VIM_WEB_HANDLER class.
Note: For custom projects, you can redefine the delivered /OTX/
PS31_CL_VIM_WEB_HANDLER class.
For details about Web Services customizing and defining a web handler class,
see section 8.5 “Work object type” in OpenText Business Center for SAP Solutions -
Configuration Guide (BOCP160302-CGD).
2. On the Nodes Overview screen, mark a node and double-click Master List -
Data Binding in the Dialog Structure.
466 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.4. Configuring exception handling with the Resolve Invoice Exceptions app
3. Define the display options for the work item list. For more information, see
section 8.6.2.3 “Configuring the data binding for the master list” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 467
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
Workflow Type
Determine the type of the workflow.
Currently, the delivered solution supports only the DP workflow (Document
Process Workflow). For other workflow types, you must perform customer
specific project implementations.
Process options You must define a process option in the standard VIM customizing to have it
in standard VIM available in this customizing. The following settings are taken from the VIM
definition:
Comments required
Set comments as mandatory.
For details about defining process options, see “Configuring DP process options”
on page 212.
468 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.4. Configuring exception handling with the Resolve Invoice Exceptions app
Additional Additional settings that are relevant for the Fiori UI are defined in the solution
settings for Fiori specific /OTX/PS31_V_OD01 customizing view.
2. In the VIM Fiori - DP Process Option Definition Overview screen, define Fiori
process options, using the following parameters.
Option ID
Enter the Fiori enabled option ID.
Web Icon
Enter the icon of the button that is shown in the Fiori screen.
UI 5 Button Type
Select the style of the button from the list.
Process Option Class
Define the actual actions that are taken after performing an action.
The following process option classes are delivered:
/OTX/PS31_CL_OPTION_SUBMIT_DP
This class provides Submit functionality. After submitting, the VIM
business rules are evaluated. You can use the class in custom scenarios
that provide Edit functionality.
/OTX/PS31_CL_OPTION_FORWARD
This class provides Forward functionality. Forwarding sends the
current work item to another VIM role or user. You can use this class
for process options of type Refer.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 469
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
Process Type
VIM process type
Responsible Party
VIM role
Note: You can define general settings by leaving Responsible Party
empty. For performance reasons, OpenText recommends this only on
test environments. For productive use, OpenText recommends a full
specification of relevant combinations of roles and process types.
Option ID
Process option ID
Sequence
Display sequence of the process options
470 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.4. Configuring exception handling with the Resolve Invoice Exceptions app
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 471
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
2. Maintain the field settings for the header and item view, using the following
parameters.
Process Type
VIM process type
Note: To simplify the configuration, it is possible to define general
settings by leaving Process Type empty. This setting is then used for
all process types that do not have specific settings.
Responsible Party
VIM role
Note: To simplify the configuration, you can define general settings
by leaving Responsible Party empty. This setting is then used for all
roles that do not have specific settings.
Field Type
Select Header Field or Item Field from the list.
Field Name
Enter the field name in the item or header table.
472 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.5. Configuring the Enter Cost Assignment app
This section describes the customizing of the Enter Cost Assignment app. Handling
coding processes with the Enter Cost Assignment app is also referred to as Simple
Coding.
To prevent processing of the same invoice by multiple users, VIM provides the Z
constant IAP / LOCK_DURATION in the /PTGWFI/Z_CONST table. This constant sets the
life time of the invoice lock. Standard value is 1800 seconds.
In Business Center, the life time of the lock is defined in General Settings. For more
information, see section 3.1.1 “Configuring locking” in OpenText Business Center for
SAP Solutions - Configuration Guide (BOCP160302-CGD). If you use the Enter Cost
Assignment app, you must adjust the lock setting in Business Center to the same
value as in VIM.
Important
The Enter Cost Assignment app does not support multiple backend or multiple
system setups. Only one backend system can be used in the context of one
launchpad tile or app inbox. To provide users with access to several systems,
you must create a separate launchpad tile for each system and specify the
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 473
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
Important
If you have not installed Web Viewer or Brava! View, OpenText recommends,
as a general advice, that you create PDF files from scanning and use the PDF
viewer that is installed on your computer for displaying invoice images.
For more information, see section 8.4.1 “Configuring basic settings” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
Note: You can customize the settings described in this section in the Business
Center Configuration.
You can change the initial sort order of the invoices that appear on the inbox list.
Default value is set to invoice due date in ascending sort order. If you want to
change the initial sort order, perform the following steps.
474 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.5. Configuring the Enter Cost Assignment app
3. In the Order by screen, remove the existing entry and/or add another entry with
a different priority, using the following parameters:
Priority
Enter the priority of the initial sort order, starting with 1 (highest priority).
Table Name
Optional: Enter name of the invoice structure.
Field Name
Enter the field name that should be used for initial sort order. The field
must be part of the display structure that has been customized in work
object type PS32_PRC_VIM_SCO.
Asc./Desc.
Select Ascending or Descending sort order.
For more information, see section 7.3.1.2 “Defining the order” in OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
You can sort inbox items also within the Enter Cost Assignment app. If a user selects
a field from the sorting list, a new sort will be performed. The selected field entry is
added to the fields that have been customized for initial sort order. In this case, the
newly added field is set to the highest sorting priority.
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 475
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
476 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.5. Configuring the Enter Cost Assignment app
1
Document header data
2
Cost assignment data
Header data is defined in the Business Center customizing. Avoid changing the
customizing.
Cost assignment data cannot be customized. It depends on the selected template and
the split switch.
1. Run the SM30 transaction (table maintenance) and enter the view /OTX/
PF62_V_OH.
2. In the dialog box that opens, enter the work object type PS32_PRC_VIM_SCO.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 477
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
3. Configure the header fields. The following screenshot shows the vendor
number added to the standard display of the vendor name:
Note: Title, 1st Attribute, 2nd Attribute, and 2nd Status are usable. 1st
status is overwritten in code.
2. In the customizing nodes that are shown, navigate to Business Center - Web
Services - Deprecated Activities > Items > Item Header Details.
3. Add or modify the records with the work object type PS32_PRC_VIM_SCO. The
following screenshot shows the vendor name added to the standard display:
478 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.5. Configuring the Enter Cost Assignment app
The SAP user account that is used on the SAP FIORI UI / Gateway system requires
the following:
The SAP user account which is used on the SAP ERP system requires the following:
Note: The SAP user must have the identical user name on both systems.
• You can configure the app to prohibit confirming the invoice if coding data is
incomplete.
• You can set the G/L Account field to read-only.
CC from, CC to
Enter the company code or company code range.
GL read only
• Select this check box to set the G/L Account field to read-only in case of
a non-multiple GL.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 479
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
• If you clear the check box, the G/L Account field is editable in case of a
non-multiple GL.
Error if incomplete
• Select this check box to achieve the following behavior if the coding is
incomplete:
An error message Coding not complete is displayed with just an OK
button. The user must complete the coding before the Confirm button is
available.
• Clear this check box to achieve the following behavior if the coding is
incomplete:
A warning is displayed in the CONFIRM dialog box.
Active Indicator
To set the customizing to active, select this check box.
Custom<n>-Name
Enter COMMENT_AT_REJECT if a comment is mandatory for the Decline
action.
Selected?
Select true for COMMENT_AT_REJECT if a comment is mandatory for the
Decline action.
• Cost Center
• Internal Order
• Profit Center
• WBS Element
480 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.5. Configuring the Enter Cost Assignment app
Template ID
Enter a unique template ID. Do not use blanks in the template ID.
Sequence
Enter 1. For multiline templates, increase the number for each line of the
template.
Active Indicator
To set the template to active, select this check box.
Flag gen.
Generic flag (SAP cost object type). Clear this check box. Select it for the
generic cost objects.
Pref. Set
Preferred setting. For multiline templates: select either Amount or Percent.
Percent
For multiline templates: enter percentage for cost object.
Cost Center, Order, Profit Center, WBS element, Function name, Cost Obj.
Define the cost object by filling one of these fields. Select a value.
Function name is meant for future use: name of Z function. The function
module must use the same interface parameters as function module /OTX/
PS32_SCO_EXIT_TMPL_EXMP.
Cost Obj.: Cost Object. Select a type; for example COST_CENTER.
Additionally, configure Cost Obj. Value: Cost Object Value. Enter a value,
for example 1000.
No change
For future use
Hide val.
For future use
3. After creating an Enter Cost Assignment template, assign it to users. For more
information, see “Assigning Enter Cost Assignment templates to users”
on page 482.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 481
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
2. In the Settings for Enter Cost Assignment Coding Check screen, configure
check settings, using the If set to X, clear all supported coding fields
before saving parameter with one of the following values:
X
Clear all supported coding fields before saving.
<Empty>
Clear only the fields used by the previous template before saving.
Note: The current version supports only assignments to the object type User.
482 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.5. Configuring the Enter Cost Assignment app
CC from
Company Code from. If yo want to set a restriction, enter the lower value of
the range.
CC to
Company Code to. If you want to set a restriction, enter the upper value of
the range.
Template ID
Select a template ID from the list.
Obj. Type
Object type. Select User from the list or leave empty for all users.
Agent ID
Enter the SAP user ID or leave empty for all users.
Template Name
Enter the template name. It is displayed on the Fiori Task App screen.
Templ. Prio
Template Priority. If a user has assigned more than one template, define the
priority.
Active Indicator
To set the assignment to active, select this check box.
Template Short Text
Template short text entered in the template definition. For more
information, see “Customizing templates for the Enter Cost Assignment
app” on page 480.
For user SCODER1, the templates are displayed on the Fiori Task App screen
with descending priority:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 483
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
• Cost Center
• Internal Order
• Profit Center
• WBS Element
2. In the Settings for Enter Cost Assignment Coding Check screen, configure
check settings, using the following parameters.
Check handling
484 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.6. Configuring the Approve Invoices app
• S: stronger check
• <FM>: Function module name
Important
If coding values are missing or wrong, the next approver most probably
cannot be determined. The next approver is determined by the COA.
You can configure application settings within the Business Center Configuration and
also the VIM Approval Configuration. The specific baseline customizing is delivered
separately for both components.
The Approve Invoices app is based on the processes and handling described in
“Invoice Approval“ on page 347.
For more information on the Business Center Configuration, see OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
For more information on the Business Center Solution Integration for Vendor
Invoice Management, see “Incoming document processing“ on page 105 and “Apps
based on the Fiori Task App“ on page 441.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 485
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
You can change the initial sort order of the invoices that appear on the inbox list.
Default value is set to invoice due date in ascending sort order. If you want to
change the initial sort order, perform the following steps.
3. In the Order by screen, remove the existing entry and add another entry (or
entries) with a different priority, using the following parameters:
Priority
Enter the priority of the initial sort order, starting with 1 (highest priority).
Table Name
Optional: Enter name of the invoice structure.
Field Name
Enter the field name that should be used for initial sort order. The field
must be part of the display structure that has been customized in work
object type PS03_PRC_VIM_APR.
Asc./Desc.
Select Ascending or Descending sort order.
For more information, see section 7.3.1.2 “Defining the order” in OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
486 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.6. Configuring the Approve Invoices app
You can sort inbox items also within the Approve Invoices app. If a user selects a
field from the sorting list, a new sort will be performed. The selected field entry is
added to the fields that have been customized for initial sort order. In this case, the
newly added field is set to the highest sorting priority.
If a Default sort is triggered, a sorting on the initial order entries will be performed.
If the sort direction Ascending or Descending differs from the customized entry, the
sort direction of the field entry with the highest priority gets overwritten by the
chosen sort direction.
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
Important
If you have not installed Web Viewer or Brava! View, OpenText recommends,
as a general advice, that you create PDF files from scanning and use the PDF
viewer that is installed on your computer for displaying invoice images.
For more information, see section 8.4.1 “Configuring basic settings” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 487
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
You can start the application process on a specific target system when using one
central system for document registration.
As a prerequisite, the central system running Business Center must have at least one
entry customized as logical system (default entry is set to LOCAL).
Multiple-system With special regard to this setup, you can also enable the Approve Invoices app for
access multiple-system access.
All VIM systems that you want to enable for multiple-system access must have a
valid logical systems entry customized on the central system running Business
Center.
Also a valid ABAP connection must be set up using trusted RFC. You must add new
entries having logical system and RFC destination to the logical systems table within
the general customizing of Business Center.
Notes
• All VIM systems that will be enabled for multiple-system access must have
at least installed VIM 7.0 SP9 or VIM 7.5 SP5 in combination with the
appropriate Support Packages of Business Center components. For more
information, see section 10 “Business Center compatibility and support
package information” in OpenText Vendor Invoice Management for SAP
Solutions - Installation Guide (VIM070500-08-IGD).
• The customizing of the fields that are displayed in the Inbox and Header
section are taken from the first valid system entry which is maintained in the
logical systems list.
All fields that can be displayed in the Approve Invoices app can be customized
within VIM customizing tables and views. Default settings are delivered within the
baseline of the Approve Invoices app and can be changed as described in “Invoice
Approval“ on page 347. The Approve Invoices app is using the settings stored with
device name “Fiori Approval Desktop” for customizing of Desktop, and “Fiori
Approval Tablet” for customizing of Tablet, and “Fiori Approval Smartphone” for
customizing of Smartphone devices.
488 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.6. Configuring the Approve Invoices app
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
Invoice Approval Configuration > User Experience > Invoice List Configuration >
Maintain Invoice List Fields.
For more information, see “Configuring invoice list fields” on page 394.
The following fields are initially set on inbox list items and cannot be changed by
customizing:
• INVOICE_AMT
• CURRENCY
• INV_STATUS
The first entry within the sequence sort order will be shown as highlighted title field
in each list item. The title field cannot be one of the fields mentioned above.
Other fields will be shown underneath the title field. These fields cannot be one of
the fields mentioned above. A maximum of two other fields are supported to be
shown together with the title field, depending on the sort order of the sequence
settings. All fields in the inbox list are shown without any leading description text
by default.
• Header fields
• Header detail fields
• Item fields
On the Header fields section, the fields that are customized for the Invoice List are
displayed with leading description text (except for the title field). You can also
customize the description text in the VIM Invoice List Fields maintenance view; see
“Customizing inbox list fields” on page 489.
For the header fields Vendor and Purchase order, semantic navigation can be
activated using Z constant 005 / FIORI_APPR_SEMA. For more information,
see section 35 “Z constants for product code 005” in OpenText Vendor Invoice
Management for SAP Solutions - Reference Guide (VIM070500-08-RGD).
Header detail fields and Item fields are customized in the VIM Invoice Detail Fields
maintenance view:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 489
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
Invoice Approval Configuration > User Experience > Invoice Detail Configuration
> Maintain Invoice Detail Fields.
Header detail fields are customized with Field Type set to Header Field. If no field
description has been customized, the data is not shown on the UI.
Item fields are customized with Field Type set to Item Field. If no field description
has been customized, the default field name is shown on the UI.
Notes
• The number of Item fields that can be shown in the specific item table is
limited to 10 maximum.
• Any field that does not contain a valid value is not displayed on the UI.
By default, bulk processing is activated for the Approve Invoices app and is
available for the Approval action only. If bulk processing is set to active, a specific
button is available in the inbox header. When a user clicks the button, the view
switches to bulk processing. The user can then mark all invoices for bulk processing,
except invoices with status Inquiry.
490 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.6. Configuring the Approve Invoices app
3. Select the Bulk actions active check box at the bottom of the screen.
Note: If the setting is activated, invoices that are already sent for inquiry
are shown in the Inbox with status Pending.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 491
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
You can activate special node handling by setting the Exit for node entry in the
customizing of the Node ID. This is part of the PS03_PRC_VIM_APR work object type.
Field validation
To be shown on the UI, fields must be part of the header display structure
that has been customized in the PS03_PRC_VIM_APR work object type.
Field description
The description text of the fields that are shown on the UI are taken from
the customized list of VIM Invoice Approval fields. If the specific field is
part of the Invoice Header field configuration, the text is taken from the
table parameter Long Field Label. If no customizing exists for the specific
field entry, the component field name of the display structure is set by
default. For more information, see “Configuring invoice list fields”
on page 394.
The SAP user account that is used on the SAP FIORI UI / Gateway system requires
the following:
The SAP user account which is used on the SAP ERP system requires the following:
492 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.7. Configuring the Approve Invoices (bulk mode) app
Notes
• The SAP user must have the identical user name on both systems.
• Within the COA, each user using the Approve Invoices app must have
assigned a corresponding SAP user.
It is also possible to launch the Approve Invoices app directly. To do this, browse
the following relative URL:
/sap/bc/ui5_ui5/otbcwui/pf07_bc_ui_02/index.html?
nodeId=PS03_VIM_APR_INV&wobjType=PS03_PRC_VIM_APR&workplaceId=WP_INBO
X&system=<SID>
For more information, see section 9.1.1 “Integrating Fiori Task App into Fiori
Launchpad” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
You can configure application settings within the Business Center Configuration and
also the VIM Approval Configuration. The specific baseline customizing is delivered
separately for both components.
The Approve Invoices (bulk mode) app is based on the processes and handling
described in “Invoice Approval“ on page 347.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 493
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
For more information on the Business Center Configuration, see OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
For more information on the Business Center Solution Integration for Vendor
Invoice Management, see “Incoming document processing“ on page 105 and “Apps
based on the Fiori Task App“ on page 441.
You can change the initial sort order of the invoices that appear on the inbox list.
Default value is set to invoice due date in ascending sort order. If you want to
change the initial sort order, perform the following steps.
3. In the Order by screen, remove the existing entry and add another entry (or
entries) with a different priority, using the following parameters:
Priority
Enter the priority of the initial sort order, starting with 1 (highest priority).
Table Name
Optional: Enter name of the invoice structure.
Field Name
Enter the field name that should be used for initial sort order. The field
must be part of the display structure that has been customized in work
object type PS03_PRC_VIM_APR.
494 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.7. Configuring the Approve Invoices (bulk mode) app
Asc./Desc.
Select Ascending or Descending sort order.
For more information, see section 7.3.1.2 “Defining the order” in OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
You can sort inbox items also within the Approve Invoices (bulk mode) app. If a
user selects a field from the sorting list, a new sort will be performed. The selected
field entry is added to the fields that have been customized for initial sort order. In
this case, the newly added field is set to the highest sorting priority.
If a Default sort is triggered, a sorting on the initial order entries will be performed.
If the sort direction Ascending or Descending differs from the customized entry, the
sort direction of the field entry with the highest priority gets overwritten by the
chosen sort direction.
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
Important
If you have not installed Web Viewer or Brava! View, OpenText recommends,
as a general advice, that you create PDF files from scanning and use the PDF
viewer that is installed on your computer for displaying invoice images.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 495
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
For more information, see section 8.4.1 “Configuring basic settings” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
You can start the application process on a specific target system when using one
central system for document registration.
As a prerequisite, the central system running Business Center must have at least one
entry customized as logical system (default entry is set to LOCAL).
Multiple-system With special regard to this setup, you can also enable the Approve Invoices (bulk
access mode) app for multiple-system access.
All VIM systems that you want to enable for multiple-system access must have a
valid logical systems entry customized on the central system running Business
Center.
Also a valid ABAP connection must be set up using trusted RFC. You must add new
entries having logical system and RFC destination to the logical systems table within
the general customizing of Business Center.
Notes
• All VIM systems that will be enabled for multiple-system access must have
at least installed VIM 7.0 SP9 or VIM 7.5 SP5 in combination with the
appropriate support packages of Business Center components. For more
information, see section 9 “Selecting required components and downloading
the packages” in OpenText Vendor Invoice Management for SAP Solutions -
Installation Guide (VIM070500-08-IGD).
• The customizing of the fields that are displayed in the Inbox and Header
section are taken from the first valid system entry which is maintained in the
logical systems list.
496 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.7. Configuring the Approve Invoices (bulk mode) app
All fields that can be displayed in the Approve Invoices (bulk mode) app can be
customized within VIM customizing tables and views. Default settings are delivered
within the baseline of the Approve Invoices (bulk mode) app and can be changed as
described in “Invoice Approval“ on page 347. The Approve Invoices (bulk mode)
app is using the settings stored with device name “Fiori Approval Desktop” for
customizing of Desktop.
3. All fields in the screenshot are delivered as baseline. Do not delete or reorder
the fields at column ID 9 and 10.
The char field CUSTFIELD1 has been reused twice at column ID 9 and 10 to
display the Approve and Reject icons.
For more information, see “Configuring invoice list fields” on page 394.
The following fields are initially set on inbox list items and cannot be changed by
customizing:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 497
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
• INVOICE_AMT
• CURRENCY
• INV_STATUS
The first entry within the sequence sort order will be shown as highlighted title field
in each list item. The title field cannot be one of the fields mentioned above.
Other fields will be shown underneath the title field. These fields cannot be one of
the fields mentioned above. A maximum of two other fields are supported to be
shown together with the title field, depending on the sort order of the sequence
settings. All fields in the inbox list are shown without any leading description text
by default.
• Header fields
• Header detail fields
• Item fields
On the Header fields section, the fields that are customized for the Invoice List are
displayed with leading description text (except for the title field). You can also
customize the description text in the VIM Invoice List Fields maintenance view; see
“Customizing invoice list fields - full screen list” on page 497.
For the header fields Vendor and Purchase order, semantic navigation can be
activated using Z constant 005 / FIORI_APPR_SEMA. For more information,
see section 35 “Z constants for product code 005” in OpenText Vendor Invoice
Management for SAP Solutions - Reference Guide (VIM070500-08-RGD).
Header detail fields and Item fields are customized in the VIM Invoice Detail Fields
maintenance view:
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
Invoice Approval Configuration > User Experience > Invoice Detail Configuration
> Maintain Invoice Detail Fields.
Header detail fields are customized with Field Type set to Header Field. If no field
description has been customized, the data is not shown on the UI.
Item fields are customized with Field Type set to Item Field. If no field description
has been customized, the default field name is shown on the UI.
Notes
• The number of Item fields that can be shown in the specific item table is
limited to 10 maximum.
498 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.7. Configuring the Approve Invoices (bulk mode) app
• Any field that does not contain a valid value is not displayed on the UI.
By default, bulk processing is activated for the Approve Invoices app and is
available for the Approval action only. If bulk processing is set to active, a specific
button is available in the inbox header. When a user clicks the button, the view
switches to bulk processing. The user can then mark all invoices for bulk processing,
except invoices with status Inquiry.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 499
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
Note: If the setting is activated, invoices that are already sent for inquiry
are shown in the Inbox with status Pending.
You can activate special node handling by setting the Exit for node entry in the
customizing of the Node ID. This is part of the PS03_PRC_VIM_APR work object type.
Field validation
To be shown on the UI, fields must be part of the header display structure
that has been customized in the PS03_PRC_VIM_APR work object type.
Field description
The description text of the fields that are shown on the UI are taken from
the customized list of VIM Invoice Approval fields. If the specific field is
part of the Invoice Header field configuration, the text is taken from the
500 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.7. Configuring the Approve Invoices (bulk mode) app
table parameter Long Field Label. If no customizing exists for the specific
field entry, the component field name of the display structure is set by
default. For more information, see “Configuring invoice list fields”
on page 394.
The SAP user account that is used on the SAP FIORI UI / Gateway system requires
the following:
The SAP user account which is used on the SAP S/4HANA system requires the
following:
Notes
• The SAP user must have the identical user name on both systems.
• Within the COA, each user using the Approve Invoices app must have
assigned a corresponding SAP user.
It is also possible to launch the Approve Invoices (bulk mode) app directly. To do
this, browse the following relative URL:
/sap/bc/ui5_ui5/otbcwui/pf07_bc_ui_03/index.html?
nodeId=PS03_VIM_APR_INV&wobjType=PS03_PRC_VIM_APR&workplaceId=WP_INBO
X&letterBox=false&appMode=FS&system=<SID>
For more information, see section 9.1.1 “Integrating Fiori Task App into Fiori
Launchpad” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 501
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
For more information on the Business Center configuration, see OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
You can change the initial sort order of the invoices that appear on the result list. By
default, the list is sorted descending by document date. If you want to change the
initial sort order, perform the following steps.
3. In the Order by screen, add a new entry and enter the following parameters:
Priority
Enter the priority of the initial sort order, starting with 1 (highest priority).
Table Name
Optional: Enter name of the invoice structure.
502 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.8. Configuring the My Approved Invoices app
Field Name
Enter the field name that should be used for initial sort order. The field
must be part of the display structure /OTX/PS03_S_VIM_MY_HEAD_DIS.
Asc. /Desc.
Select Ascending or Descending sort order.
For more information, see section 7.3.1.2 “Defining the order” in OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
You can sort the result list also within the My Approved Invoices app. When a user
selects a field from the sorting list, a new sort is performed. The selected field entry
is added to the fields that have been customized for initial sort order. In this case, the
newly added field is set to the highest sorting priority.
Important
If you have not installed Web Viewer or Brava! View, OpenText recommends,
as a general advice, that you create PDF files from scanning and use the PDF
viewer that is installed on your computer for displaying invoice images.
For more information, see section 8.4.1 “Configuring basic settings” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
Default settings for displayed fields are delivered with a BC set. If you change the
default settings, consider that these changes will be overwritten if you activate the
relevant BC set after a manual change.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 503
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
3. Double-click Full Screen List – Data Binding in the dialog structure and adjust
the configuration to your needs.
504 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.8. Configuring the My Approved Invoices app
Area 1 is the invoice header, area 2 contains invoice attributes and area 3 contains
invoice line items.
3. Dependent on the area you want to change, proceed with the following steps.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 505
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
506 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.8. Configuring the My Approved Invoices app
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 507
VIM070500-08-CGD-EN-01
Chapter 14 Apps based on the Fiori Task App
The SAP user account that is used on the SAP FIORI UI / Gateway system requires
the following:
The SAP user account which is used on the SAP S/4HANA system requires the
following:
Notes
• The SAP user must have the identical user name on both systems.
• Within the COA, each user using the My Approved Invoices app must have
assigned a corresponding SAP user.
How long does it take to install and configure one of the VIM Fiori apps?
It is like every other SAP AddOn: Install it, activate the BC sets, and activate the
services as described in OpenText Vendor Invoice Management for SAP Solutions -
Installation Guide (VIM070500-08-IGD). For more information, see OpenText
Business Center for SAP Solutions - Installation Guide (BOCP160302-IGD).
508 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
14.9. Frequently asked questions
If I am using Business Center for inbound channels email and paper, do I need to
use BCC instead of ICC? Or can I still use ICC with Business Center Inbound
Configuration?
You can use ICC with Business Center Inbound Configuration to process
invoices.
For a new customer, you need to use Business Center Inbound Configuration for
email and paper. You also need to use Business Center as basis for VIM Fiori
apps.
BCC or ICC depends on what the customer buys. They do not get BCC for free,
unlike you do get Business Center when used for vendor invoices.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 509
VIM070500-08-CGD-EN-01
Chapter 15
VIM Analytics (new)
The new VIM Analytics (VAN) replaces the “old” VAN, which was in use in VIM
prior to version 7.5.
For documentation of the “old” VAN, see the VIM 7.0 documentation.
Important
The new VAN is not designed and supported for processing in background.
VAN gives users a clear data report on their open and completed invoices as well as
the VIM workflows. VAN also includes DP documents and workflows. VAN allows
you to track the documents routed through SAP workflows by VIM or even without
any VIM process.
Note: If you want to track documents without any VIM process in the new
VAN, you must maintain the constants DOCTYPE_NPO and DOCTYPE_PO, product
code 005, of the WebFlow Constant Table /PTGWFI/Z_CONST.
VAN has been completely reworked for VIM 7.5. Here are some of the new features:
• The new VAN is highly optimized for SAP® HANA database systems to support
queries on mass data very quickly.
• The new VAN is based on a completely redesigned data base schema to ensure
high data quality and improved performance.
• The new VAN comes with a central place of configuration in the VIM
configuration tree. The baseline is delivered with default settings for the new
VIM Analytics.
• With VIM 7.5 SP4 and later, the new VAN is enabled to extract data from
multiple backend systems.
Note: VAN does not read data of work items that are treated with data
archiving.
VAN presents the data report results in the SAP List Viewer (ALV).
You can use VAN to check the current document status, the current agent and
exception reason of a particular invoice. Besides the result list, there are further
views available that provide detail information about a selected invoice:
• Process View
This view displays open and completed VIM processes together with the current
workflow status, the current agent and exception reason of this particular
process.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 511
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
• Image View
This view displays the scanned, linked images.
• Line Item View
This view displays the invoice line items.
• History View
This view displays the VIM process history.
• Comments View
This view displays the comments that have been added during the VIM process
and during the approval process.
The new VAN supports all kind of database systems. On a SAP system with SAP
NetWeaver Application Server ABAP 7.40 SP05 or higher, you have the choice
between the following types of data selection:
For more details to the role-specific transaction codes, see section 3 “VIM Analytics:
Getting data reports” in OpenText Vendor Invoice Management for SAP Solutions -
Reference Guide (VIM070500-08-RGD).
Starting with VIM 7.5 SP6 (VIM 7.0 SP10), Net Amount and Tax Code fields are
displayed in the VAN result list.
Net Amount
In the DP indexing screen, the Net Amount field is updated with the following
formula:
Net amount = gross amount – tax amount
For any changes in gross or tax amount, the net amount is recalculated with this
formula and updated in the Net Amount field. After the correct net amount has
been updated in the DP document, the same amount is pulled in the new VAN
for reporting purposes.
512 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.1. Reports for one-time data upload and for consistency check of documents
Tax Code
The tax code is displayed in the VAN result list. The tax code on output is based
on the following rule:
If the tax code exists in the header, the tax code is considered. Otherwise, the tax
code from the line items is considered. If line items have multiple tax codes, an
asterisk (*) is displayed.
As the administrator, you may also run this report for chosen documents in case of
any data inconsistency in the database tables that the new VAN is working with.
/OPT/VR_ANA- After upgrading from VIM 6.0, the due date fields in /OPT/VIM_1HEAD are filled for
LYT- old (pre-upgrade) work items during the normal work process. If you want to
ICS_750_UPD_
1H
automatically fill these fields during the upgrade process, you can use the migration
report /OPT/VR_ANALYTICS_750_UPD_1H.
These tables are filled consistently during the runtime of the work item.
Initialization mode
When upgrading from a lower VIM version (6.0), the mentioned tables need to
be filled initially for old instances. The new VIM Analytics will not show any
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 513
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
values if the /OPT/VIM_2HEAD table is not filled. You must run this migration
report mode accordingly.
Update mode
As the administrator, run this report mode for chosen document IDs to correct
data in the mentioned tables.
Running in dialog
For more information, see “Using the selection screen” on page 515.
Running in background
514 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.1. Reports for one-time data upload and for consistency check of documents
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 515
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
Document selection
Document-ID
Mandatory field: enter the Document IDs.
Select Charge
The processing in the report is done by charges. You can maintain the number of
processed documents before committing (COMMIT). In normal cases, leave this
number on the standard setting. For optimization, you can set this parameter
differently.
Update properties
Test run
Select this check box to achieve that the report will not update any values in the
database tables. You can use this mode for runtime measurement before
planning the actual productive run or to check what updates would be done in
detail.
15.1.2.3 Output
The /OPT/VR_ANALYTICS_750_INIT report output differs if Display calculation
results is selected or not.
Display The report shows a protocol about successful or unsuccessful execution. You can
calculation access the protocol in the Job Spool when running in the background.
results not
selected
Display The report calculates all values within the selection range and displays them in
calculation intervals according to the Select Charge setting. On the main screen, you can
results selected analyze the tables for these intervals by pressing the respective buttons. Click Go to
next interval to start the calculation of the next interval.
516 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.1. Reports for one-time data upload and for consistency check of documents
Table view The table view shows a list of all values already present in the database and
compares them to the calculated value. The first line is representing the current
value in the database, the second line the calculated value.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 517
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
You can assign a specific user profile using the /OPT/VVA2_CUST_PROF user
parameter.
Profile
Define the profile with a unique ID.
Customizing Profile Description
Enter a description for the profile.
518 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.2. Customizing profiles for the new VAN
All UI-related settings are taken into account if you run the new VAN for the first
time or if you decide to reset the UI layout to the general default settings.
4. Configure the general profile settings, using the parameters described in the
following subsections.
Customizing Profile
Predefined customizing profile, for which the settings are valid.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 519
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
15.2.2.1 Application
Logo Name
Enter the object name of any corporate branding logo image. If you leave the
field empty, no logo image is displayed in the new VAN.
Default value: /OPT/VIM_LLECMLOGOFS
Note: VIM provides the global feature to control whether logo images
should be displayed using the DASHBOARD_NO_LOGO constant, product code
005 of the WebFlow Constant Table /PTGWFI/Z_CONST. If you want to use
this feature, do not change the Logo Name parameter.
Application Class
Enter the application ABAP class that contains the VAN application logic.
Default value: /OPT/CL_V_VA2_APPLICATION
Factory Class
Enter the factory ABAP class that creates the object instances for the new VAN,
for example the object instances for the data providers.
Default value: /OPT/CL_V_VA2_OBJECT_FACTORY
UI Class
Enter the UI controller ABAP class that contains the VAN UI specific logic.
Default value: /OPT/CL_V_VA2_UI_CONTROLLER
Data Class
Enter the data provider ABAP class that contains the VAN data load logic.
Default value: /OPT/CL_V_VA2_DATA_PROVIDER
User Class
Enter the VAN user ABAP class that contains the logic to read and save user-
specific profile settings.
Default value: /OPT/CL_V_VA2_USER
Selection Mode
On a SAP system with SAP NetWeaver AS ABAP 7.40 SP 05 or higher, you can
decide whether you want to run VAN with ABAP CDS views or without. ABAP
CDS views are database independent, with some exceptions if the databases do
not yet cover all the functionalities, for example views with parameters. On SAP
NetWeaver AS ABAP versions lower than 7.40 SP 05, VAN will always run
without ABAP CDS views.
Select Selection Mode Use ABAP CDS Views to specify that the data selection is
using ABAP CDS views.
Select Selection Mode Use no views to specify that the data selection is not
using ABAP CDS views, but using standard DDIC tables and DDIC views
instead.
520 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.2. Customizing profiles for the new VAN
• On other database systems, start with Use no views and check whether
the runtime is sufficient. If it is not, you can switch to Use ABAP CDS
Views and the other way round seamlessly.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 521
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
Reuse Buttons
The old VAN provides the feature to add function buttons to the ALV toolbar.
Table /OPT/VIM_FCODE contains all function buttons available in the document
view of the old VAN report.
The new VAN provides the feature to add action buttons to the result list, to the
process view, and to the line item view. Regarding the result list, you can decide
whether you want to reuse all the action buttons already defined for the old
VAN or whether you want to configure the action buttons independent from the
old VAN.
The parameter Reuse Buttons allows to configure whether the action buttons
already defined for the old VAN shall be reused for the result list of the new
VAN.
Select this check box to specify that the custom buttons configured for the old
VAN shall be reused for the new VAN.
Clear this check box to specify that the custom buttons assigned to the VAN
customizing profile shall be used instead of reusing the custom buttons of the
old VAN.
Default value: <cleared>
Classical ALV
In the context of SAP HANA, SAP has provided a new version of the SAP List
Viewer, the SAP List Viewer with Integrated Data Access (IDA ALV). The IDA ALV
introduces some major database feature improvements compared to the classical
ALV.
Example:
• Database paging: The result will be selected from the database in pages - there is no
need to transfer the full result set to the application server any more.
• Operations like aggregation, sorting and filtering in the ALV grid will be pushed
down to the database layer.
The IDA ALV can be used not only on a SAP HANA database system but on all
other database systems as well.
With the Classical ALV check box, you configure which version of the SAP List
Viewer you want to use for the result list.
Select this check box to specify that the classical ALV is used for the result list.
Not yet supported:Clear this check box to specify that the IDA ALV is used for the
result list.
Note: This setting influences the result list only. For all details views, the
classical ALV is used.
522 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.2. Customizing profiles for the new VAN
Size Ratio %
Enter the size of the result list in percent of the detail pane. If you do not enter a
value, the system automatically uses a standard value of 50%.
Example: A value of 60 means that 60% of the width of the window are reserved for the
result list and 40% of the width are reserved for the detail pane.
Default value: 50
Plug-In Type
Enter a predefined plug-in type to get all mapped plug-in definitions that are
available as buttons in the detail pane toolbar.
Default value: VIM_VA2 - VIM Analytics
Plug-In ID
Enter the plug-in that is initially loaded in the detail pane. If you do not enter a
value, the system automatically uses a standard value of 21 (Display Workflow
Processes).
Default value: 21 - Display Workflow Processes
• The input parameters of the ABAP CDS views: Fields of the VAN selection
screen are assigned to input parameters of the ABAP CDS views, restricting the
data to be selected.
• The output parameters of the ABAP CDS views: Fields of the ABAP CDS views
are assigned to fields of the ABAP table containing the selection result.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 523
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
Selection Mode
Select Use ABAP CDS Views if the field mapping is relevant for the data
selection with ABAP CDS views.
Not yet supported: Select Use no views if the field mapping is relevant for the
data selection without ABAP CDS views, that means for the selection with
standard DDIC tables and views.
View
Enter the type of view that the field mapping is related to.
Not supported for ABAP CDS views:Line Item View and Process View.
Note: Header View corresponds to the result list.
524 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.2. Customizing profiles for the new VAN
Select Output Field if you want to define the mapping for an ABAP CDS
view field to a field of the ABAP table containing the selection results. This
means that the selected value is assigned to the respective field in the result
table.
Application Field Name
For an input field, enter the name of the parameter or select-option on the
VAN selection screen. Cut off the first two letters, for example cut of the P_
of parameters and S_ of select-options.
Example: For selection-option S_LIFNR, enter LIFNR.
For an output field, enter the name of the field in the ABAP result table.
This means a field name of structure /OPT/VVA2_CDS_DOC_HDR_ST.
The user selects vendors on the VAN selection screen to get all invoices of
these vendors. The select-option for vendors is S_LIFNR. The ABAP CDS
view for the result list has an input parameter LIFNR_I to limit the selection
of document headers regarding vendors.
The user chooses to display the vendor of an invoice in the result list. The
ABAP CDS view for document headers selects the vendor into the output
field LIFNR_O. The ABAP table containing the selection results is based on
the /OPT/VVA2_CDS_DOC_HDR_ST structure. The LIFNR field of this structure
represents the vendor.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 525
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
If you want to integrate OpenText™ Extended ECM for SAP® Solutions into VAN as
a custom button that opens a separate window, see the respective Notes in the
following sections.
View
Select the type of view that the button is relevant for.
Note: Header View corresponds to the result list.
Button ID
Enter a unique numeric button ID that defines the action button.
Button Type
Select the button type used to generate the button during runtime. Select
one of the following button types:
Single action
All buttons defined as single actions are generated as separate buttons
in the button toolbar.
Separator
This setting allows you to insert standard SAP separator lines to group
the generated buttons from a visual point of view.
526 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.2. Customizing profiles for the new VAN
Button Text
Enter the button text, which is displayed as text label for the generated
button during runtime.
Quickinfo
Enter quick info text, which is displayed for the button during runtime.
Icon name
Assign an icon to the generated button or use the button exit to assign the
icon dynamically.
Button Exit
Enter an exit function module that dynamically performs the following
actions:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 527
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
Note: You can configure whether custom buttons configured for the old VAN
shall be reused for the new VAN (see “Action Buttons” on page 522). If the
custom buttons of the old VAN are reused, the assignment of action buttons
described in this section is ignored during runtime.
Customizing Profile
Predefined customizing profile for which the button assignment settings are
valid.
View
Select the type of view that the action button shall be assigned to.
Button ID
Enter the ID of the button that shall perform a button action.
Button Text
Button text, which is displayed as text label for the generated button during
runtime.
528 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.3. Layout variants
With layout variants, you define the fields to be read in the result list, the process
view and the line item view. By ensuring that your layout variants contain only
those fields that are needed by your users, you can positively influence the runtime
of VAN.
Besides hiding or displaying columns, layout variants allow you to change the
sequence of the displayed columns or to change the sort order.
VAN delivers some preconfigured layout variants for the ALV grid of the result list,
the process view and the line item view to ensure that only a limited set of fields is
selected:
Result List
Process View
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 529
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
list, the process view and the line item view. Of course it is always possible for the
user to define user-specific layout variants.
• Use the standard SAP function Change layout in the ALV grid control.
To open the layout context menu, click the right portion of the Select layout
button .
For detailed information about the layout features, see the SAP Help: http://
help.sap.com/erp2005_ehp_06/helpdata/EN/8d/
e994374c9cd355e10000009b38f8cf/frameset.htm.
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:
• Maintain the SLD in all satellite systems, with a logical system entry for each
remaining satellite system besides central and own systems. Assign a proper
RFC for Dialog Comm for all other satellite systems and central system. For
more information, see section 4.4.1 “Maintaining the SLD” in OpenText Vendor
Invoice Management for SAP Solutions - Scenario Guide (VIM070500-08-CCS).
• To use the remote enabled VAN, OpenText recommends trusted RFCs for Dialog
Comm.
• For further information, see section 4.4 “Working with the System Landscape
Directory (SLD)” in OpenText Vendor Invoice Management for SAP Solutions -
Scenario Guide (VIM070500-08-CCS).
For a description how to start VAN for single and multiple remote systems, see
section 3.1 “Starting remote enabled VAN” in OpenText Vendor Invoice Management
for SAP Solutions - Reference Guide (VIM070500-08-RGD).
Notes
530 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.5. Additional configuration options for the new VAN
• If you have custom settings for buttons and plugins that the local database
reads, it must be adjusted to read from the selected satellite system (with an
RFC).
Ensure that select-options start with S_ and parameters start with P_.
Example implementation:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 531
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
Note: Always read the instructions mentioned in the coding of the classes very
carefully before implementing enhancement points.
3. Add a new class attribute similar to the existing attributes starting with MR_ as
implicit enhancement. This new class attribute represents a range table for the
new selection criteria. Use type RSELOPTION or any range type appropriate to
your selection criteria.
532 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.5. Additional configuration options for the new VAN
Note: Always read the instructions mentioned in the coding of the classes very
carefully before implementing enhancement points.
To enhance the data selection when not using ABAP CDS views:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 533
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
enhancement. This new class attribute represents a range table for the new
selection criteria. Use type RSELOPTION or any range type appropriate to your
selection criteria.
Note: There are three enhancement points available at different points of time
in the process to filter for custom selection ranges. It may have negative effects
on the runtime when using an inappropriate enhancement point for filtering.
The more restrictive selection criteria is, the more you should use it for filtering
at the beginning of the filter process.
The other way round, if you have to select all VIM documents (technically, all
records of /OPT/VIM_1HEAD) before you can judge whether a document fulfills
the selection criteria or not, you should use the enhancement point at the end
of the filter process.
15.5.1.3 Defining field mapping (only when using ABAP CDS views)
The input of the additional selection field needs to be passed to the appropriate
input parameter of the ABAP CDS views. Define an additional field mapping from
the selection field to the ABAP CDS views field in VIM customizing:
For more details, see “Defining field mapping (only when using ABAP CDS views)”
on page 523.
534 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.5. Additional configuration options for the new VAN
In addition, the VAN selection screen offers more than 80 selection fields. Not all of
these selection fields may be required for all user groups. To keep the selection
screen as clearly as possible, you can use variant-specific attributes. Variant-specific
attributes enable you to hide individual fields, for example, or to write-protect data.
Furthermore, you can store the selection values defined for a selection option as a
separate selection variable. Changes made to the variable then affect all of the
variants in which it is used.
For detailed information about variants on the selection screen, see the SAP help.
4. Add the customer fields that you want to add into the structure fields and
provide related data elements. The data element will provide the field label, for
example the column heading.
5. Save and activate the append structure and put it into a transport request.
6. By default, the new custom fields are not yet displayed in the result list. To get
the custom fields displayed, launch VIM Analytics and change the layout
variant for the result list. For details, see “Layout variants” on page 529.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 535
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
1. Repeat the steps in “To add fields to the output structure of the result list:“
on page 535 for structure /OPT/VVA2_OUT_LINE_ITEM_ST.
2. By default, the new custom fields are not yet displayed in the line item view. To
get the custom fields displayed, launch VIM Analytics and change the layout
variant for the line item view. For details, see “Layout variants” on page 529.
1. Repeat the steps in “To add fields to the output structure of the result list:“
on page 535 for structure /OPT/VVA2_OUT_WORK_ITEM_ST.
2. By default the new custom fields are not yet displayed in the process view. To
get the custom fields displayed, launch VIM Analytics and change the layout
variant for the process view. For details, see “Layout variants” on page 529.
How to populate custom fields in the result list depends on whether you use ABAP
CDS views or not. In contrast to this, for the line item view and the process view,
there is no difference how to populate custom fields no matter if ABAP CDS views
are used or not.
Populating or changing field content in the result list with ABAP CDS views –
You may need to read additional fields from the database to populate the field
content in the result list. Depending on the database tables that are concerned, there
are two alternatives how to select these additional fields:
• The ABAP CDS views read data from several database tables already. You want
to read an additional field.
Example: The CDS views select data from database table /OPT/VIM_1HEAD already. You
want to select an additional field from database table /OPT/VIM_1HEAD.
536 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.5. Additional configuration options for the new VAN
See “To select additional fields by enhancing the ABAP CDS views:“
on page 537
• You need to read data from database tables that are not included in the ABAP
CDS views.
Example: You want to get an additional descriptive text from a text table.
See “To select additional fields by selecting data from additional database tables:
“ on page 538
1. Enhance the appropriate ABAP CDS views by the additional output fields you
need to read.
The data records selected by the ABAP CDS views are read into a local table
lt_result of structure /OPT/VVA2_CDS_DOC_HDR_ST.
3. Pass the additional fields that are read from the ABAP CDS views to the local
table lt_result of structure /OPT/VVA2_CDS_DOC_HDR_ST. In Step 1, you have
added fields to the structure of local table lt_result. Now define the field
mapping between the ABAP CDS view fields and the fields of the result table:
For more details, see “Defining field mapping (only when using ABAP CDS
views)” on page 523.
4. In some cases, it may not be enough to just select one field from the ABAP CDS
views per output field but it may be required to select some more fields from
the ABAP CDS views. In this case, you may need to implement enhancement
point /OPT/EP_VIM_VA2_DATA_PROV_ADDF of enhancement spot /OPT/
ES_VIM_VA2_DATA_PROV_BE_C to add some more fields to be selected.
Repeat Step 1 to Step 3 for these additional fields.
Now you have done everything to get data read from the ABAP CDS views into
the local table lt_result. This local table is used to populate the custom output
fields in the result table rt_out_doc_hdr of structure /OPT/
VVA2_OUT_DOC_HDR_ST in a next step. By default all data records of local table
lt_result are moved to the final result table rt_out_doc_hdr by using the
move-corresponding statement. Sometimes this may not be sufficient and you
may need to implement some custom logic.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 537
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
To populate or change field content in the result list without ABAP CDS views:
538 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.5. Additional configuration options for the new VAN
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 539
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
VIM Analytics allows you to add hot spots to additional fields in the following
output tables: result list, process view, line item view. This includes fields of the
VIM standard as well as custom fields. In a first step, you enable the hot spot for the
field. In a second step, you implement the function behind this hot spot.
540 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.5. Additional configuration options for the new VAN
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 541
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
Several fields in the result list and in the process view of the VIM Analytics provide
hot spot functionality to jump to detail information related to the field.
VIM Analytics allows you to change the logic behind hot spots for fields in the result
list, the line item view and the process view. You can not only change the program
logic but you can also add program logic to fields for which you have added a new
hot spot (see “Enabling hot spot functionality for fields in output tables”
on page 540).
To add custom logic to a hot spot for a field in the result list:
542 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.5. Additional configuration options for the new VAN
To add custom logic to a hot spot for a field in the line item view:
To add custom logic to a hot spot for a field in the process view:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 543
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
• Number of days before the due date for cash discount 1 to set a yellow discount
light.
• Number of days before the due date for cash discount 1 to set a red discount
light.
The settings for the discount light apply for the discount light that is integrated in
the process output list of VIM Workplace. The settings also apply for the discount
light icon that is integrated in the result list of VAN.
For more details and all the steps needed to specify the discount light settings, see
“Specifying discount light settings” on page 612.
The selection screen comes with more than 80 different selection fields. The selection
criteria that are used in companies most frequently vary very much. So there cannot
be a general recommendation which database indexes would be the best in your
company.
Analyze the most frequent and time critical queries, for example by using the ST05
transaction. Then create extension indexes on /OPT/VIM_1HEAD and further tables
depending on your company’s most common selection requirements.
In section 3.5 “VIM Analytics and mass data” in OpenText Vendor Invoice Management
for SAP Solutions - Reference Guide (VIM070500-08-RGD), you find further
recommendations for the end user how to ensure a fast data selection in VIM
Analytics.
Additionally, adjust the layout variants for the result list of VIM Analytics to restrict
the number of output columns to those columns that are needed for the daily
business. For more details, see “Layout variants” on page 529.
Note: If your SAP system is on SAP NetWeaver AS ABAP 7.40 SP05 or higher,
you have the choice to use the new VIM Analytics report with ABAP CDS
Views or without. This configuration of the Selection Mode may have a high
impact on the run time of the new VIM Analytics report. It varies from system
to system which configuration is the best. But based on extensive mass data
544 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
15.7. Extending the Current Liability Report
For more details about the configuration of the Selection Mode, see “Data
Selection” on page 520.
However, these are general recommendations only. Your system might react
differently from OpenText's test systems. This is why OpenText strongly
recommends that you test the setting for the Selection Mode on your system
and set it accordingly. You can switch the setting whenever needed.
Limitation
During PO proposal, the system does not populate both GL account and cost
center for multiple account assignments. Therefore, they are not reported in the
DP line view of the Current Liability Report. However, for single account
assignment, both GL account and cost center will appear in the DP line view.
To get a meaningful output list of the Current Liability Report, with additional fields
on DP line view and SAP lines view, you can perform the following customization.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 545
VIM070500-08-CGD-EN-01
Chapter 15 VIM Analytics (new)
5. Redefine the EXTEND_LINE_VIEW method of the newly created subclass with the
logic to read data for additional fields and fill the report using changing
parameter OUTTABLE.
In this method, you can set custom field attributes by field catalog using the
changing parameter FIELDCAT.
6. Finally run the SM30 transaction and add the new entry to the Z constant table /
PTGWFI/Z_CONST with the following values:
546 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 16
16.1 Introduction
Within companies, the processing of invoices varies according to legal or specific
company-based settings. VIM supports flexible processing by defining individual
invoice characteristics.
With respect to invoice processing, there are various business and regulatory rules
that need to be applied. These rules differ from region to region. VIM provides a
flexible infrastructure for implementing these rules. This empowers customers to
fine tune these rules to be in line with their interpretation of legal rules and for
optimizing their business processes.
Tax related
Specific pieces of information relating to Value Added Tax (VAT) and other
taxation rules that need to be followed. SAP ERP implements the various tax
rules in the standard software and has a flexible infrastructure to link with tax
software like Vortex and Taxware. VIM by itself does not duplicate any of these
pieces of functionality. VIM provides a way to implement certain metadata-
based business rules that can be implemented before the invoice data is entered
in to the SAP ERP transactions.
Core infrastructure
Infrastructure that supports the ability to model and realize different business
process flows depending on the characteristic specific rules.
Baseline content
Out-of-box content that includes common implementation of business rules
specific to the various regions. VIM provides a baseline that is based on country
as a characteristic. However, you can customize this if required.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 547
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
You can use a document type to combine all global settings to process an invoice
within a company. Therefore a document type is a global invoice processing
template. You can configure detailed settings according to specific invoice attributes
within invoice characteristic settings. You can also maintain settings in different
determination procedures, for example approval determination or additional cost
determination.
Obsolete The document types have an attribute to configure a “country code”. The “country
setting code” provides a mechanism for an implementer to configure country-specific
processes. This is obsolete with VIM 7.0 and higher because the country-specific
settings have been replaced by the characteristic-specific settings, which are
specified by the document type determination.
If you still use a fixed country in the document type, and the characteristic is also
configured, the country of the document type is used for the characteristic
processing. Therefore no other characteristic like the country is allowed.
548 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.1. Introduction
Domestic
Invoices raised by vendors in the same country.
Intra-Community
Invoices raised by vendors in the European Union (EU) to companies in the EU.
Applicable only to EU countries.
Triangulation
Invoices raised by vendors in the EU to companies in the EU for a delivery of
goods or services originating in another EU country. In this case, both the
vendor and the company are in different EU countries. Applicable only to EU
countries.
Import
Invoice raised by vendors outside the company’s country.
Domestic Material
Invoices raised by vendors in India where the Purchase Order is a Material PO.
Applicable only to India.
Domestic Service
Invoices raised by vendors in India where the Purchase Order is a Service PO.
Applicable only to India.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 549
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
Import Material
Invoices raised by vendors outside India where the Purchase Order is a
Standard PO. Applicable only to India.
Import Service
Invoices raised by vendors outside India where the Purchase Order is a Service
PO. Applicable only to India.
Non VAT
Invoices without VAT amount. Applicable only to China.
VAT Common
Invoices with VAT provided but the VAT amount is not deductible. Applicable
only to China.
VAT Special
Invoices with VAT provided and the VAT amount is deductible. Applicable
only to China.
These global templates cover the basic configuration, and in combination with the
country-specific invoice characteristic enable global companies to process invoices.
The following table lists the document types that are delivered as a part of VIM
baseline version.
550 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.1. Introduction
Each document type has a defined set of business rules. These business rules
determine the DP Exception to be raised in case of missing or invalid data on the DP
indexing screen.
The DP indexing screen is different for each document type. Based on the document
type, the respective Indexing screen is displayed. The screen configuration for each
document type is a part of the document type configuration.
Besides the global configuration of the document types, the detailed characteristic
configuration provides, in the baseline delivery, settings for all countries. Specific
countries and a global country template are delivered to support all requirements
from the process point of view.
You should copy the baseline document types to “own” document types.
The business rule run can be configured to run different for customer specific
groups. There is no preconfiguration. Some vendors could be grouped as white list
vendors. For this group, the business rules would not all be carried out.
2. Decide which checks (business rules) shall be carried out in which sequence:
Adjust the document processes in the Document Type Definition. For more
information, see “Defining the process type determination sequence”
on page 145.
3. Decide which groups shall be used to have a strict or relaxed business rule run.
For more information, see “Business Rule Framework” on page 197.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 551
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
Besides the global document type, the invoice characteristic is determined and
defined in the determination engine. Within the baseline, VIM delivers the country
for characteristic. This section describes how to define an own invoice characteristic
and how to use the determination based on the invoice characteristic.
Note: You must only change the settings in this section, if you want to enhance
the baseline implementation by using an own characteristic.
552 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.1. Introduction
You can change the sequence of the procedures, and you can introduce
additional procedures. Because the procedures are performed in alphabetical
order according to their procedure name, you must insert new procedures in
their correct position. The maintained procedures are checked from top to
bottom, and the first matching document type will be chosen.
5. Characteristic customizing
To maintain the characteristic settings, double-click Characteristics Field.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 553
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
Field Name
Specify the characteristic field. Each characteristic setting depends on that
field. In the baseline, LAND1 is delivered to replicate countries for all
characteristics. If this value changes, all characteristic settings have to be
checked and changed.
Search Help Name
Enter a search help to simplify the characteristics mapping.
Text table, Short tx fld n (Short text field name)
Enter the field name of the short text in the configured text table. The short
text is used in the characteristics customizing.
Exit FM
Enter a function module to determine the specified characteristic. In the
baseline, the country is read from the delivered company code.
Note: You must only change the settings in this section if you want to enhance
the baseline implementation.
You can use category groups to restrict the number of invoice categories per
characteristic. Category groups are a bundle of different categories.
When defining the business rules for a particular characteristic, you can configure
them by category group. You can define a business rule for all the categories in that
group in one line of configuration.
For a list of invoice categories that are supported for VIM, see “Invoice categories”
on page 549.
554 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.2. Invoice categories, category groups, and mapping
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 555
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
Prerequisites
556 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.2. Invoice categories, category groups, and mapping
2. Maintain the invoice categories for each invoice category group. One invoice
category can be assigned to multiple category groups.
Prerequisites
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 557
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
2. Map your invoice category groups to the characteristics that are supported in
your system.
1. To configure or to see what is configured for the baseline version for the
characteristic specific settings for document types, run the /N/OPT/SPRO
transaction to access OpenText Configuration and navigate to Vendor Invoice
Management > Document Processing Configuration > Document Type
Configuration > Characteristic Specific Document Type Configuration.
558 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.3. Characteristic specific settings for document types
Posting date
This attribute determines the date to be used as the Posting date when
creating a SAP Invoice Document from a DP document. This configuration
will be applicable to all the invoices posted to SAP ERP for the
characteristic.
Select one of the following values:
Conversion Date
This attribute determines the date to be used while converting the invoice
amount from foreign currency to company code or local currency.
Select one of the following values:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 559
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
• Posting Date
Simplified Inv FM
You can write your own function module to determine if an invoice can be
classified as a Simple Invoice. Add the name of the function module in this
field. Copy the interface of the /OPT/VIM_CHECK_SIMPLE_INVOICE standard
function module to create a custom function module.
The following check boxes are indicators for credit memo check:
CM Data Validate
Select this check box to determine that the credit memo reference number
and the credit memo reference date must match the existing invoice in the
SAP ERP system.
Trg.sp.G/L ind.
This attribute sets the target special G/L indicator when creating an SAP
Down Payment Request from a DP document. This configuration is only
applicable to Down Payment Requests posted to SAP ERP for the
characteristic. For more information, see “Posting of down payment
requests” on page 924.
560 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.3. Characteristic specific settings for document types
Note: For a description of possible scenarios for the baseline date, see
“Baseline date determination scenarios” on page 561.
Baseline Date FM
To apply custom logic for the baseline date determination, you can write
your own function module. If you enter a custom function module in this
field, the value for Det. Baseline Date is not considered anymore. However,
you can use the value in the custom function module.
Exit FM
Enter an exit function module to modify the indexing screen fields, for
example /OPT/VIM_SCREEN_EXIT_FM.
Cat. from external
This check box is only relevant for Russia and Brazil, where the invoice
category should not be changed when starting VIM.
Select this check box to indicate that the invoice category comes from a
channel and is not changed when starting VIM.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 561
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
The Det. Baseline Date is set to Document Date in the customizing. In the indexing
screen, the baseline date is automatically populated as document date. See the
following screenshot.
All other options, such as Manual Entry, Current System Date, SAP Logic and so
on, are overwritten by Document Date.
Note: Manual Entry is not compatible with this option because baseline date
becomes non-editable.
The selected Det. Baseline Date option is overwritten by SAP logic. However, in the
indexing screen, manual entry is allowed to be selected.
SAP logic includes the possibility to set a baseline date according to the payment
terms. If the payment terms are configured to use the Entry date (in the OBB8
transaction), this is interpreted as the document creation date in VIM.
562 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.3. Characteristic specific settings for document types
If there are no payment terms maintained in the vendor master for the vendor, then
the baseline date is blank, and the user can select any of the baseline determination
options. See the following screenshot:
Note: In case of auto posting of PO invoices ensure that the payment term is
maintained for the vendor.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 563
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
564 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.3. Characteristic specific settings for document types
As a part of the baseline version, each document type has a different screen attached
with it. Screen configuration is a part of the document type configuration. Based on
the business requirements for each characteristic, respective header and item screens
are attached to the document type.
The baseline document types contain a standard subset of screen fields. These
settings are specified in more detail for each characteristic. For example, the ISR
field for Switzerland is only specified for baseline characteristic CH.
Globally, you configure fields for one document type. For more information, see
“Configuring the index header” on page 152. For country level, you configure the
fields on characteristic level, as described in detail in “To configure characteristic
specific screen fields:“ on page 565.
The indexing screen displayed is generated at runtime, based on the document type
and characteristic being processed.
1. To configure or to see what is configured for the baseline version for the screen
fields, run the /N/OPT/SPRO transaction to access OpenText Configuration and
navigate to Vendor Invoice Management > Document Processing
Configuration > Document Type Configuration > Characteristic Specific
Document Type Configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 565
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
The screenshot displays the various attributes that can be modified for a screen
field. The configuration also allows you to configure screens per role or per
invoice type.
3. Input
Select this option to show the field as an input field.
Required
Select this option to make the field mandatory at runtime.
Display Only
Select this option to only display the field.
Hide
Select this option to hide the field on the screen.
4. To configure the attributes for the item screen, double-click Index Item
Configuration in the Dialog Structure.
The attributes are the same as for the index header.
566 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.3. Characteristic specific settings for document types
2. Configure the process types for the characteristic, using the following
parameters:
Process Type
Process type number.
Description
Description of the process type.
InvoiceTyp
Select the invoice type that is applicable to the process type in this country.
The following values are available:
• All invoices
• PO based invoices
• Non PO based invoices
• Not applicable
Ignore Sim
Select this check box to specify that the process type will be ignored for
Simple Invoices.
Cat. Group
Select the invoice category group to which the process type is applicable.
For information about categories, see “Invoice categories” on page 549.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 567
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
You can configure a process type that is used globally in document types to be
processed on characteristic base. Therefore, follow the description in “Defining the
process type” on page 230. In the Process Type Definition Details screen, select the
Characteristic Check check box.
16.4 Z constants
For some characteristic-specific configurations, you need to maintain Z constants. To
access Z constants, run the SM30 transaction with the /PTGWFI/Z_CONST table.
AFTCS_PROCESS_TYPES
Usage
This Z constant defines the process types that are relevant for the Anti Forge Tax
Control System (AFTCS) file upload/download program. The /OPT/
VR_AFTCS_FILE program only downloads the data of those invoices that are in
process types defined in this Z constant.
You can maintain multiple process types (as in baseline) with each process type
separated by a comma.
Product code
005
Baseline
141, 241
568 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.5. Configuration for Canada
DETERMINE_INV_CAT
Usage
VIM baseline provides several invoice categories. You can also create your own
invoice categories. However, the system will not determine the custom invoice
category. You must write your own function module to determine the custom
invoice category. You must define this custom function module in this Z
constant.
Product code
005
Baseline implementation
/OPT/VIM_TEMPLATE_DET_INV_CAT
Before tax code derivation, the system validates whether the supplied tax rate fields
are applicable for the region. Therefore, it uses the Invalid Sales Tax for the
Region business rule. However, to move past the Invalid Sales Tax for the
Region business rule check, the system must know the ship-to-region for the
incoming vendor invoice. The external system (for example OCR or IDOC) might
not supply a ship-to-region. The region can be derived automatically, based on
certain settings. For more information, see “Determining the ship-to region”
on page 570.
When the ship-to-region is known and the Invalid Sales Tax for The Region
business exception does not occur, the system proceeds further to determine the tax
code, based on the multiple tax rate fields supplied. For more information, see
“Determining the tax code” on page 573.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 569
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
Company Code
The system will determine the region from the address maintained in the
company code address for the range of vendors and company codes.
You do not have to maintain an entry in the Region and Custom FM fields.
Fixed Value
You must maintain the region explicitly in the Region field.
570 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.5. Configuration for Canada
Custom Function
You can define a custom logic to find the region by defining the Z function
module explicitly in the Custom FM field.
The following is an example interface of the custom function:
FUNCTION ZXXXXXXXXXXX
*"------------------------------------------------------------
*"*"Local Interface:
*" EXPORTING
*" REFERENCE(REGION) TYPE REGIO
*" TABLES
*" INDEX_ITEM STRUCTURE /OPT/VIM_1ITEM OPTIONAL
*" CHANGING
*" REFERENCE(INDEX_DATA) TYPE /OPT/VIM_1HEAD OPTIONAL
*"------------------------------------------------------------
ICC If ICC is used as OCR, ICC does not explicitly supply the ship-to region. In this case,
VIM uses the Company Code/PO (based on the selected configuration option) to
derive the ship-to region. There might be cases where you cannot use a Company
Code/PO to derive the ship-to region. In these cases, you must use custom functions
or manual entries, for example, if one of the following cases applies:
• The Company Code address cannot be treated as the ship-to address. In this case,
do not use the Company Code option to derive the ship-to region. Use the custom
function option.
• A PO or a combination of multiple POs has any line items with varying ship-to
regions for various PO line items (based on different receiving plants at PO line
item level). In this case, do not use the PO as an option to derive the ship-to
region. Use the custom function option.
• Without the ship-to region determined automatically or supplied, new business
rules for validation of tax rate fields/tax code determination fail on VIM side.
Manual user input is needed.
• ICC does not supply taxes at line item level. ICC should supply taxes only at
header level. The same tax rate at the header is applicable for each line item if no
lines are supplied with a tax rate. Different line items in the vendor invoice might
have different tax rates. For example, if a combination of free goods line (tax-free)
and lines with a tax rate exists in the vendor invoice, use the custom function
option.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 571
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
• The tax rate fields supplied in the incoming invoice do not match with the
allowed fields maintained.
• The ship-to region is empty. The ship-to region must be determined to
proceed.
572 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.5. Configuration for Canada
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 573
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
except the Tax Code field. If key fields overlap, the system will pick the tax
code corresponding to the first match.
Note: The Find Text for Field at Header and Line Item Level table with its
entries is provided by default. Therefore, you do not have to maintain or
change anything, unless some exceptional cases occur.
574 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
16.5. Configuration for Canada
• TAXRATE_1: Maintain GST, if this field is supposed to store the GST tax
rate.
• TAXRATE_2
• TAXRATE_3
• TAXRATE_4
The following fields at line level should be maintained for the tax line keyword:
• TAXRATE1_1
• TAXRATE2_2
• TAXRATE3_3
• TAXRATE4_4
Labels – Besides maintaining keywords, the Find Text for Field at Header and
Line Item Level table is used for maintaining labels for tax rate fields and tax
amount fields at line item level.
Note: For header level fields, you maintain texts in view /OPT/VIM_IDX_T.
Use the SM30 transaction or run the /OPT/SPRO transaction and navigate to
Vendor Invoice Management > Document Processing Configuration >
General Configuration > Translations/Labels for Index Screen Fields. For
more information, see “Customizing field labels in the index screen”
on page 155.
For the line item level, the following fields should be maintained for texts:
• TAXAMT_1
• TAXAMT_2
• TAXAMT_3
• TAXAMT_4
• TAXRATE1_1
• TAXRATE2_2
• TAXRATE3_3
• TAXRATE4_4
*FUNCTION ZXXXXXXXXX
*" TABLES
*" INDEX_ITEM STRUCTURE /OPT/VIM_1ITEM
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 575
VIM070500-08-CGD-EN-01
Chapter 16 Characteristic specific configuration
*" CHANGING
*" REFERENCE(INDEX_DATA) TYPE /OPT/VIM_1HEAD OPTIONAL
576 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 17
ICC Integration
The OCR solution OpenText Invoice Capture Center (ICC) can be integrated into
VIM. ICC automates the capture of paper invoices by using OCR to extract the
invoice data. ICC uses SAP ERP as backend to store and retrieve invoice image
information through the ICC Dispatcher.
Starting with Business Center 10.0 SP1 and Business Center Solution Integration for
Vendor Invoice Management 10.0 SP2, you can use Business Center Inbound
Configuration to handle incoming document processing. For more information
about how to configure document registration for early archiving and document
handler, see section 4.4.2.1 “Customizing the early archiving registration type” in
OpenText Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
To activate the ICC processing for Business Center Inbound Configuration, you
must activate the BC_INBOUND Z constant.
Note: After you have switched your system to BC_INBOUND, ICC and
OpenText™ Business Center Capture for SAP® Solutions (BCC) cannot access
the ICC application store in your VIM system anymore. This means, that you
must perform a new export of all your ICC/BCC applications. For more
information, see section 2.2.3 “Exporting an application to SAP ERP” in
OpenText Business Center Capture for SAP Solutions - Customization Guide (CPBC-
CGD) and section 2.2.6 “Exporting an application to file” in OpenText Business
Center Capture for SAP Solutions - Customization Guide (CPBC-CGD).
If you use Business Center Inbound Configuration, only the following customizing
steps are relevant for VIM.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 577
VIM070500-08-CGD-EN-01
Chapter 17 ICC Integration
• CUSTOM_ICC_PO_DOWNLD
• DP_DOC_TYPE
• PO_REC
• VEND_REC
1. Run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Invoice Management > Document Processing Configuration > General
Configuration > Incoming Document Processing > ICC Configuration >
Advanced Configuration.
Product Code 005 determines Document Processing.
Value is the default value or expected value in the process.
2. Define the default values, according to the following table:
Constant Meaning
CUSTOM_ICC_PO_DOWNLD Customer function module to perform the PO
download.
The signature is the same as standard function
module /OPT/DOWNLOAD_PURCHASE_DATA
Using this user exit, a customer specific function can
be performed to load the items from the staging tables
to the ICC.
DP_DOC_TYPE Default DP document type
PO_REC Maximum batch size for Purchase Order download
data
VEND_REC Maximum batch size for Vendor download data
578 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
17.2. Maintaining the Mark for Training function
Prerequisite The DOC_ARC_DOC_ID field (XML data from ICC) must be filled for the work item.
1. Open the index header configuration (see “Configuring the index header”
on page 152)
The Training button is visible but inactive if one of the following conditions applies:
1. Run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Invoice Management > Document Processing Configuration > General
Configuration > Incoming Document Processing > ICC Configuration >
Maintain Workflow Template Constants.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 579
VIM070500-08-CGD-EN-01
Chapter 17 ICC Integration
1. Run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Invoice Management > Document Processing Configuration > General
Configuration > Incoming Document Processing > ICC Configuration >
Maintain Preprocess Exit constants.
The engine works if the DP document type assigned to the archive document type is
one of the following:
• the default document type; that means the value configured in Z-constant 005
DP_DOC_TYPE
If a different DP document type is assigned to the archive document type, the engine
is skipped. In this case, the assigned DP document type is used for the DP workflow.
580 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
17.4. Document type determination rules engine
If you have a 1:1 relation between the DP document type and an ArchiveLink
document type, select the ArchiveLink document type defined in the SAP
ArchiveLink process. If you do not have a fixed relation, you can leave the field
empty or you can use a dummy archive document type which is used for all DP
document types without fixed relationship. The current baseline is delivered with
dummy document type /OPT/ICC.
Up to VIM 6.0 SP3, the archive document type in table /OPT/VIM_1HEAD was derived
from the DP document type by the configuration setup using the /OPT/VIM_1CX1
transaction. This determination was changed in VIM 6.0 SP3 to the determination
that is described in this section.
However you can switch to the old determination behavior (as it was before VIM 6.0
SP3), using transaction /OPT/VIM_1CX12: For constant 005 / AR_OBJECT_FROM_DP,
enter Constant Value X.
17.4.1 Methods
The rules engine consists of a sequence of procedures. Each procedure is responsible
for one DP document type. If one procedure says NEXT, the next procedure is
performed. If a procedure says TRUE, the document type of this procedure is applied
to the document. The last procedure should be responsible for the DP document
type NPO_75. This last procedure should always return TRUE.
17.4.2 Configuration
You configure the rules engine in the OpenText Configuration (/OPT/SPRO):
Vendor Invoice Management > Document Processing Configuration > Document
Type Configuration > Maintain Document Type Determination Procedure
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 581
VIM070500-08-CGD-EN-01
Chapter 17 ICC Integration
You can use the Exclusive check box to deactivate a procedure. If the check box
is not selected, the procedure will never return TRUE but always return NEXT.
You can change the sequence of the procedures, and you can introduce
additional procedures. As the procedures are executed in alphabetical order
according to their procedure name, you must insert new procedures in their
correct position. The maintained procedures will be checked top down and the
first matching document type will be chosen.
17.4.4 Steps
The procedures consist of steps, which can be modified. You can use the following
check types:
A
Missing value of an OCR field
B
Constant value of an OCR field
C
Custom function
D
Invalid value of an OCR field (value cannot be found in a check table)
E
Characteristic value of the characteristic customizing criteria
F
PO related invoice type check
You can configure the processing relation between the different steps with the
indicators AND or OR.
582 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
17.5. Download of recipient data for ICC usage
Note: The report is available with UI languages English, German, French, and
Spanish.
The report generates database lines for every company code in the selection,
respecting all house banks and bank accounts. The address information related to
the company code is the same in all lines.
Note: In most cases, you must edit the text file or the database itself because
the address information generated by the download program will not be
sufficient for a good identification of company codes.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 583
VIM070500-08-CGD-EN-01
Chapter 17 ICC Integration
Character The processing option With character check checks the address for TAB characters
check inside the strings. These characters would disturb the output format and must be
eliminated.
Processing option With character check will not work in an EBCDIC environment, so
it can be switched off.
Logical system You can set the value for the logical system to be used in the data to a defined value.
So, it is possible to generate databases which are not designated for the logical
system where the download data is taken from.
Output to If you use the option Additional output to screen, the data will be displayed on the
screen screen in an ALV grid. Note that the field sequence is rearranged for optimized
readability. The field sequence does not correspond to the field sequence in the
download file.
You can maintain these keywords in table /OPT/VIM_T001I, using the SE16 or SE16N
transaction.
1. Run the SM30 transaction to maintain the trusted vendor list /OPT/
SLN_VENDORV.
If the list does not contain any entries at all, each vendor is considered as
active.
584 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
17.6. Maintaining the trusted vendor list
If the list contains entries, but none of them is flagged as active, each vendor is
considered as inactive.
Note: To avoid risks, add at least one vendor in this list, before you use an ICC
application with option Deliver line item number.
To find out which vendors can be added to the trusted vendor list:
1. Switch on the ICC option Deliver line item number and process the
documents as usual. For more information about the option, see section 3.4.6
“Specifying line item processing” in OpenText Business Center Capture for SAP
Solutions - Customization Guide (CPBC-CGD).
2. After a while, look at the entries in table /OPT/VIM_1ITEM. Look for items that
have the same value in columns EBELP and EBELP_N and find out the vendors
for these purchase orders.
3. If you have found suitable vendors, find out the purchase orders of these
vendors. Double-check the items.
If you find purchase orders with different values for EBELP and EBELP_N, the
vendor is not a candidate for the trusted vendor list.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 585
VIM070500-08-CGD-EN-01
Chapter 18
Configuring the VIM Workplace
VIM Workplace is intended as a tool for VIM super users, for example the AP
processor. However, also occasional users can work with it. VIM Workplace allows
you to display lists of your work items based on criteria that you have specified. You
also can display work items of other users and of your team as a whole.
The registration tables need to be filled for existing items so the tabs Inbox, Pending
and Closed are filled correctly. Therefore, a migration report is available with VIM
7.5 SP2.
/OPT/CT_PMC_RG00
Contains information about work items in the inbox
/OPT/CT_PMC_RG01
Contains information about work items in the inbox
/OPT/CT_PMC_RG02
Contains information about work items in My Pending
/OPT/CT_PMC_RG03
Contains information about work items in finished items
These tables are filled consistently during the runtime of the work item.
Initialization mode
When upgrading from a lower VIM version (6.0), the mentioned tables need to
be filled initially for old instances. The VIM Workplace will not show any work
items if these tables are not filled. You must run the migration report
accordingly.
Update mode
As the administrator, run this report mode for chosen document IDs to correct
data in the mentioned tables.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 587
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
Prerequisite The report is based on data contained in /OPT/VIM_1PROC. This table is initially
filled by the VIM Analytics migration report, which is documented in “Reports for
one-time data upload and for consistency check of documents” on page 513.
Document selection
Document-ID
Mandatory field: enter the Document IDs.
Select Charge
The processing in the report is done by charges. You can maintain the number of
processed documents before committing (COMMIT). In normal cases, leave this
number on the standard setting. For optimization, you can set this parameter
differently.
Update properties
Test Run
Select this check box to achieve that the report will not update any values in the
database tables. You can use this mode for runtime measurement before
planning the actual productive run.
588 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.1. Migration report for the VIM Workplace
18.1.2.2 Output
The report output differs if Display calculation results is selected or not.
Display The report shows a protocol about successful or unsuccessful execution. You can
calculation access the protocol in the Job Spool when running in the background.
results not
selected
Display
The report calculates all values within the selection range and displays them in
calculation intervals according to the Select Charge setting. On the main screen, you can
results selected analyze the tables for these intervals by pressing the respective buttons. Click Go to
next interval to start the calculation of the next interval.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 589
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
Table view The table view shows a list of all values already present in the database and
compares them to the calculated value. The first line is representing the current
value in the database, the second line the calculated value.
590 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.2. Configuring the System Landscape Directory (SLD) for the VIM Workplace
Note: As long as you do not configure the SLD, an error message is displayed
when starting or refreshing the VIM Workplace.
You can assign a specific user profile using the /OPT/CPMC_CUST_PROF user
parameter.
To define a profile:
Customizing Profile
Define the profile with a unique ID.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 591
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
All UI-related settings are taken into account if you run the VIM Workplace for the
first time or if you decide to reset the UI layout to the general default settings. The
general default profile (DEFAULT) included within the baseline delivery assumes a
minimum screen resolution of 1600 x 900 for all UI-related settings.
3. Configure the general profile settings using the parameters described in the
following sections:
592 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.3. Customizing profiles for the VIM Workplace
Customizing Profile
Predefined customizing profile for which the settings are valid.
Work View
Select the work view that is initially loaded when starting the VIM Workplace. If
you do not provide a value, the system automatically starts the personal work
view.
Discount Function
Enter the exit function module to determine the discount light indicator
behavior within the process output list of the VIM Workplace.
Default value: /OPT/C_PMC_DATA_SET_DISC_LIGHT
Exit template function: /OPT/C_PMC_EXIT_TEMPL_DISCOUNT
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 593
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
Plug-In Type
Enter a predefined plug-in type in order to get all mapped plug-in definitions,
which are available as buttons in the detail pane toolbar.
Plug-In ID
Enter the plug-in that is initially loaded in the detail pane.
594 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.3. Customizing profiles for the VIM Workplace
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 595
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
selection subscreen area values because the screen does not offer any subscreen
area separation.
Field selection subscreens for vertical selection tabs
The Tab<x> Vertical fields allow replacing the vertical field selection subscreens
for each selection tab.
Reset Selection Criteria Function Module
Enter a function module to reset the selection criteria on the currently active
selection pane tab.
Default value: /OPT/C_PMC_SEL_OPTIONS_RESET
Synchronize Selection Criteria Function Module
Enter a function module to synchronize the selection criteria between the
horizontal and vertical selection pane subscreens.
Default value: /OPT/C_PMC_SEL_OPTIONS_SYNC
Lock Selection Screen Function Module
Enter a function module to lock the selection screen input for an active selection
screen tab.
Default value: /OPT/C_PMC_SEL_PANE_LOCK_GET
596 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.3. Customizing profiles for the VIM Workplace
Include Substitution
Select this check box to achieve that the output process list also shows work
items for active or adopted substitutions in the personal inbox view, and that the
field Substitution for: contains the original work item receiver.
Note: The output sequence of the list fields delivered by the DEFAULT baseline
customizing profile is used as a standard configuration. Each individual user
can change the configuration using the ALV layout variant functionality.
3. Configure the output list field settings using the following parameters:
Profile
Predefined customizing profile for which the output list field settings are
valid.
Sel. Tab
Selection tab for which the corresponding output list field settings are valid.
Possible values: Inbox, Pending, Completed.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 597
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
Component name
Field name of the output list field: Select any field that is available in the
output list field reference structure /OPT/CPMC_OUTPUT_PROCESS_ST, using
the input search help.
You can select several standard fields and additionally custom fields and
manual classification:
Custom fields
• CUSTOM_FIELD4
• CUSTOM_FIELD5
• CUSTOM_FIELD6
• CUSTOM_FIELD7
• CUSTOM_FIELD8
• CUSTOM_FIELD9
• CUSTOM_FIELD0
MAN_CLASSIFICATION
Manual classification.
Only for custom development: You can use this field to add customer
specific classifications. You can implement a custom logic to fill this
field during runtime.
Out. Key
Output key: Select this check box to mark the output list field as ALV
output key column. All fields marked as output key fields are fixed when
using the horizontal scroll bar in the process output list.
Out. Seq.
Output sequence: Define the sequence of the field within the output list.
Out. Stat.
Output status: To define the status of the output field, select Display or
Hide.
Col. width
Output width: Enter the fixed column width for an output field. If you do
not enter a value, the system activates the automatic ALV grid control
column optimization for the output field.
Out. Style
Output style: Define the output style of an output field, for example, if it is
displayed as an Icon or as a Hyperlink.
598 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.3. Customizing profiles for the VIM Workplace
Out. Icon
Output icon: Enter the icon symbol that is displayed if you selected the
Icon or Executable Icon field output style.
Icon Info
Icon quick info: Select this check box to display an icon quick info for the
output icon.
Icon Exit Function Module
Enter an exit function module to dynamically set the output icon symbol
and the corresponding icon quick info during runtime. Exit template
function: /OPT/C_PMC_EXIT_TEMPL_ICON.
Before Action Execute Function
Enter an exit function module that allows performing the following special
functionality:
Auth. Grp.
Action authority group: Assign a predefined action authority group to an
output list field action. The action authority group is used to check whether
the corresponding user is allowed to perform the action or not.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 599
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
Profile
Predefined customizing profile for which the button assignment settings are
valid.
Button ID
Predefined button ID to perform a button action.
But. Seq.
Button Sequence: Define the sequence in which the assigned action buttons
are generated within the VIM Workplace process output list toolbar.
Auth. Grp.
Action authority group: Assign a predefined action authority group to an
action button. The action authority group is used to check whether the
corresponding user is allowed to perform the action or not.
600 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.4. Defining action buttons for the VIM Workplace
Button ID
Unique numeric button ID that defines an action button.
Button Text
Enter the button text, which is displayed as text label for the generated
button during runtime.
Quickinfo
Enter quickinfo text, which is displayed for the button during runtime.
Butt. Type
Enter the button type used to generate the button during runtime. Select
one of the following button types:
Bulk action
All buttons defined as bulk actions are generated within a special
toolbar button menu called Choose Bulk Action.
Single action
All buttons defined as single actions are generated as separate buttons
in the VIM Workplace process output list button toolbar.
Separator
This setting allows you to insert standard SAP separator lines to group
the generated buttons from a visual point of view.
Notes
• Buttons that are defined as single actions can only be performed for
exactly one marked line in the VIM Workplace process output list. A
bulk action can be performed for one or multiple lines marked by
the Bulk Action check box.
• The Forward bulk action has been introduced for administrators.
Regular end users should use the Refer action instead. The function
is set to inactive by default. You must activate it if required.
OpenText recommends that you protect this function against special
authority checks because the function should only be available to
administrators.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 601
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
• Starting with VIM 7.5 SP7, the Forward action in the VIM
Workplace, both single and bulk, writes an entry into the process
history log for all non-approval work items.
Icon name
Assign an icon to the generated button or use the button exit to assign the
icon dynamically.
Button Exit
Enter an exit function module that dynamically skips the creation of a
button during runtime. Exit function template: /OPT/
C_PMC_EXIT_TEMPL_BUTTON
Active
Select this check box to set the button definition to active.
Button actions
These actions are defined as single or bulk action buttons within the process
output list button toolbar.
Output Field actions
These actions are defined as executable icons or hotspots within the process
output list itself.
All action-related authority checks are performed based on action authority groups.
An action authority group allows grouping of multiple similar actions for the
602 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.6. Configuring scanning in VIM Workplace
authority check instead of performing the authority check based on each defined
action separately. This concept simplifies the maintenance of the corresponding
authorizations. If you want to perform an authority check directly for each action,
you must set up a 1:1 relationship between action authority groups and defined
actions.
If you do not want to perform an authority check for a selected action, do not assign
an authority group to the action in the action button assignment or the output field
action setting.
If you have set the global VIM authorization check to inactive using the
AUTH_CHECK_ACTIVE constant for product code 009 of the web flow constant table /
PTGWFI/Z_CONST, the authority check field is not considered. Therefore, all entered
values do not have any effect.
Auth. Grp.
Action Authority Group: Unique technical name that defines an action
authority group.
Action Authority Group Description
Enter a description for the defined action authority group.
Prerequisites To use the scanning function, the following prerequisites must be fulfilled.
• VIM-related document types (document types assigned to the VIM object /OPT/
V1001) are configured according to OAWD customizing.
• The available document types are filtered by the VIM object in SOA0.
• Using an authorization check of the S_WFAR_OBJ authorization object, you can
further restrict available document types.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 603
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
To scan an invoice:
The Scan Document dialog box displays the following fields in the upper right
area.
Doc. type
Document Type. Long text for the ArchiveLink document type
Scan User
Current user
2. In the Scan Document dialog box, double-click the document type in the tree.
On the right, the following objects are displayed. Their functionality is like in
SAP standard.
• Archive Document and Mass Archiving buttons for single and mass
archiving
• Drag & Drop area
3. To archive, click one of the archiving buttons.
The behavior (scan using Enterprise Scan, upload from file system) is
determined by the ArchiveLink customizing of the respective document type.
604 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.6. Configuring scanning in VIM Workplace
OpenText recommends Mass Archiving only for document types that are
configured for scanning.
Below the Drag & Drop area, the scan results are displayed.
4. Click Show details for more information on workitem IDs and docIDs.
• Document types
• Number of subtrees
3. Navigate to package /OPT/VIM_PMC_SCAN and class /OPT/CL_C_SDP_TREE.
Methods GET_ROOT_NODES and GET_CHILD_NODES in class /OPT/CL_C_SDP_TREE
offer an enhancement point that is defined in enhancement spot /OPT/
ES_CL_C_SDP_TREE.
• Nodes
• Tree settings
5. Navigate to package /OPT/VIM_PMC_SCAN and class /OPT/CL_C_SDP_VIM.
Method OPEN_SCAN_POPUP in class /OPT/CL_C_SDP_VIM offer an enhancement
section that is defined in enhancement spot /OPT/ES_CL_C_SDP_VIM.
6. Perform changes, as needed:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 605
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
• Object types
• Display logo
• Call of popup
Example implementation
Example coding provided in method ON_BUTTON_CUST1_CLICK: refresh
automatic batch ID to open a new batch of scanned invoices.
Example coding provided in method ON_BUTTON_CUST2_CLICK: user enters a
note manually (to use as batch ID or handling advice).
606 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.6. Configuring scanning in VIM Workplace
INITIALIZE_NOTE
This method is called when opening the scanning dialog box and when
changing the document type selection.
SET_NOTE
Set the note to custom value (can be called in custom implementations).
GET_NOTE
This method is called when archiving is started to retrieve a value for the note.
The defined ArchiveLink note can be retrieved in the NOTE field of table /OTX/
PF01_T_1REG. As a prerequisite, Business Center Inbound must be used.
You can replace the existing example implementation by custom coding. The NOTE
field is not used in the product baseline.
Processing hint
Add a manually entered processing hint during scanning. For information how
to add custom information, see “Adding custom fields in the selection screen”
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 607
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
Note: If you use the VIM Workplace smart selection in a multiple backend
environment, make sure to keep the smart selection definition identical on all
involved systems.
Selection Criteria
Enter a unique alphanumeric ID or any other 10 character string that
technically defines a set of selection criteria.
608 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.7. Defining smart selections
Description
Enter a meaningful text that describes the selection criteria. The text is
available in the VIM Workplace selection criteria list of the smart selection
pane.
Criteria Type
This setting controls the way how the corresponding selection criteria logic
is executed in order to determine the check result.
Select one of the following criteria types:
Static check
Selection criteria checks are based on index data and executed every
time the index data is changed during runtime.
Time based check
Selection criteria checks are based on dynamic time bound dimensions
and therefore can only be executed by the additional criteria check
program /OPT/CR_PMC_BS_CHECK.
Note: For more information regarding the functionality and run
frequency of program /OPT/CR_PMC_BS_CHECK, see section 5.4
“Scheduling batch jobs for VIM Workplace” in OpenText Vendor
Invoice Management for SAP Solutions - Administration Guide
(VIM070500-08-AGD).
Criteria Class
Enter the ABAP class that contains the check logic for the defined selection
criteria. To redefine the available check methods, every entered class must
be inherited from the abstract class definition /OPT/CL_C_PMC_BS.
Note: For more information how to implement additional custom
selection criteria and restriction checks based on the abstract class /
OPT/CL_C_PMC_BS, see section 12.3.2.1 “Creating a custom smart
selection class implementation” in OpenText Vendor Invoice
Management for SAP Solutions - Scenario Guide (VIM070500-08-CCS).
Active
Select this check box to activate the defined selection criteria and its
dependent restrictions.
If the Active check box is not selected, the selection criteria is not considered
during the selection criteria check and also not available in the VIM
Workplace smart selection pane.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 609
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
Restriction
Enter a unique alphanumeric ID or any other 10 character string that
technically defines a selection restriction.
Description
Enter a meaningful text that describes a selection restriction. The text is
available in the VIM Workplace selection restriction list of the smart
selection pane.
Constant Value
Enter any additional information that can be helpful during the selection
criteria and restriction check. You can freely choose the additional
information, independent from any data format.
610 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.8. Maintaining general teams for the VIM Workplace
Work View
Select the work view for which a selection criteria should be available.
Possible values: Personal, Team, Other user, All.
Selection Tab
Select the selection pane for which a selection criteria should be available.
Possible values: Inbox, Pending, Completed.
Preview Active
Select this check box to achieve that a special selected hits preview of the
potential selection result is displayed for each selection criteria and
restriction. If no dependent restrictions are defined for a selection criteria,
the preview counter is shown on criteria level only. If there are dependent
restrictions, the selected hits preview is shown on restriction level.
Note: The determination of the selected hits preview counter values
consumes a lot of performance. Use it carefully. Therefore, no selected
hits preview is activated in the baseline delivery for the VIM
Workplace All work view mode.
Personal Team
Maintained by each user directly in the VIM Workplace team configuration
dialog.
General Team
Generally maintained by an administrator. Users cannot change the general
team in the VIM Workplace team configuration dialog box.
The general team definition describes the team with a unique ID and the
corresponding description.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 611
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
Team ID
Unique ID for the general team definition.
Description
Enter a description for the defined general team.
2. In the General Team Definition Overview screen, select a line and double-click
Team Member Assignment.
Team ID
Unique ID for the general team definition.
OT
Organizational Object Type: This field contains a one or two character code
that represents different types of objects, for example US for user or S for
position.
Agent ID
Corresponding organizational object ID, depending on the selected
organizational object type.
Active
Select this check box to set the member assignment to active.
• Number of days before the due date for cash discount 1 to set a yellow discount
indicator light.
• Number of days before the due date for cash discount 1 to set a red discount
indicator light.
Note: If you do not want to set up the discount indicator light settings for each
company code separately, enter an asterisk (*) in the company code field.
If the number of days before the due date for cash discount 1 is higher than the
specified number of days for the yellow discount indicator light, a green light is
shown. If the corresponding due date for cash discount 1 is reached or is already
overdue, the discount indicator light switches to red.
612 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
18.10. Displaying returning invoices in VIM Workplace
Note: If you do not want to use the described generic configuration settings
based on the number of days before cash discount 1, do not maintain any
number of days. The following fixed logic for the discount indicator light will
apply automatically:
• Cash discount 1 possible (due date for cash discount 1 >= current date): green
discount indicator light
• Cash discount 2 possible (due date for cash discount 2 >= current date):
yellow discount indicator light
• All possible discounts missed: red discount indicator light
Note: The discount light settings depend on the corresponding SAP ERP
system and therefore no transport of the setting is available.
2. In the VIM Workplace Disc. light settings Details screen, enter your company
code dependent settings.
Note: If you do not want to specify company code specific settings, enter
an asterisk (*) in the Company Code field.
You can configure the new display column Returning invoice in the VIM
Workplace profile settings. For more information, see “Customizing profiles for the
VIM Workplace” on page 591. The configuration must look like in the following
screenshot:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 613
VIM070500-08-CGD-EN-01
Chapter 18 Configuring the VIM Workplace
With this configuration, the Returning invoice column is available in the ALV
layout settings in the inbox tab of VIM Workplace. With the column enabled in the
layout, the returning invoices are displayed with an icon in the Returning invoice
column.
614 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 19
Customizing plug-in controls for end-user screens
Different end-user screens, for example the VIM Workplace or the indexing screen
(DP Dashboard) are enabled to use integrated plug-in views to display detail
information for a process.
You can also use plug-in controls in the Invoice Approval Dashboard, the Parked
Dashboard, and the Blocked Dashboard.
2. In the Plug-In Type Definition Overview screen, define the plug-in type, using
the following parameters:
Plug-In Type
Unique ID of a plug-in type to be used within an end-user screen.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 615
VIM070500-08-CGD-EN-01
Chapter 19 Customizing plug-in controls for end-user screens
Plug-In ID
Unique ID of the plug-in.
Plug-In title
Enter the title of the plug-in, which is displayed on the button in the plug-in
toolbar.
Plug-In description
Enter the tooltip of the plug-in, which is displayed on the button in the
plug-in toolbar.
Plug-In Sequence
Define the order of the buttons for the plug-in.
Plug-In class
To process the corresponding logic for the plug-in, enter the class to be
called during runtime. To integrate custom logic to retrieve data for existing
616 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
19.3. Assigning the plug-in IDs to plug-in types
Note: To create a new plug-in, you must create your own plug-in class
with superclass /OPT/CL_C_PMC_UI_PLUGIN.
Plug-In Icon
Enter the icon of the plug-in, which is displayed on the button in the plug-in
toolbar.
PI Active
Select this check box to activate the plug-in on the screen.
Plug-In Type
Unique ID of the plug-in type definition.
Plug-In ID
Unique ID of the plug-in definition.
• Indexing screen
• VIM Workplace
• VIM Analytics
You can also integrate Extended ECM for SAP Solutions into VIM Analytics as a
custom button that opens a separate window. For more information, see “Defining
and assigning action buttons” on page 526.
Extended ECM for SAP Solutions allows displaying content that is stored in the
OpenText™ Content Server in the SAP GUI. You also can upload content from the
SAP GUI to the Content Server.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 617
VIM070500-08-CGD-EN-01
Chapter 19 Customizing plug-in controls for end-user screens
Extended ECM for SAP Solutions can be configured for several business objects.
That means, the solution is open for custom solutions. An example integration for
vendor workspaces is delivered with baseline. You can include custom scenarios
based on other business objects. For more information, see “Implementing custom
solutions for the plug-in framework” on page 619.
Prerequisites
• Extended ECM for SAP Solutions is installed, at least version 10.5 Service Pack 1.
• Extended ECM for SAP Solutions is customized, as described in OpenText
Extended ECM for SAP Solutions - Customizing Guide (ERLK-CGD).
• Workspaces can be created for business objects using the standard Extended
ECM for SAP Solutions GOS menu integration.
1. Define the plug-in ID. See the description in “Defining the plug-in ID”
on page 616.
In Plug-In class, enter the class for the respective VIM tool:
Indexing screen
/OPT/CL_C_IDX_UI_PLUGIN_XECM or your own custom class
VIM Workplace
/OPT/CL_C_PMC_UI_PLUGIN_XECM or your own custom class
VIM Analytics
/OPT/CL_C_VA2_UI_PLUGIN_XECM or your own custom class
2. Assign plug-in IDs to plug-in types. See the description in “Assigning the plug-
in IDs to plug-in types” on page 617.
The plug-in types for the respective VIM tools are the following:
Indexing screen
VIM_IDX
VIM Workplace
VIM_WP
VIM Analytics
VIM_VA2
618 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
19.4. Customizing the integration of Extended ECM for SAP Solutions
4. Create a new entry to assign the plug-in ID to an extended ECM business object.
Plug-In ID
Enter the ID created in Step 1 on page 618.
Object Type
Enter the business object that should be shown in this plug-in. This business
object must be configured in Extended ECM for SAP Solutions. In the
example screnshot: LFA1 for vendor workspace.
H/L
Define the origin of the object key: Header (/OPT/VIM_1HEAD) or Line (first
line of /OPT/VIM_1ITEM).
Reference field
Specify the field in the header or line item table that contains the object key
for the business object. In the example screenshot: /OPT/VIM_1HEAD-LIFNR
contains the object key for the vendor.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 619
VIM070500-08-CGD-EN-01
Chapter 19 Customizing plug-in controls for end-user screens
These classes can handle all Object Types whose object key is directly available in
tables /OPT/VIM_1HEAD or in the first selected line in /OPT/VIM_1ITEM. By using
customizing table /OPT/CT_XECM_PMC, the relevant fields can be customized directly.
Please see the customizing for vendor workspaces in “Customizing the integration
of Extended ECM for SAP Solutions” on page 617 as a reference.
For more complex scenarios, where additional selects are necessary, you can define
custom classes. For each workspace type, a new implementation is needed. The
following procedure describes the implementation of a subclass of /OPT/
CL_C_IDX_UI_PLUGIN_XECM as a reference. You can implement the other classes
accordingly. Custom implementations for indexing screen and VIM Analytics (new)
can be created accordingly, as well.
620 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
19.4. Customizing the integration of Extended ECM for SAP Solutions
3. Implement custom coding to get the relevant object key. Return the object key in
the RV_OBJ_ID parameter.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 621
VIM070500-08-CGD-EN-01
Chapter 19 Customizing plug-in controls for end-user screens
5. Return the SAP Object type for the Extended ECM for SAP Solutions scenario in
the RV_SAP_OBJECT parameter.
622 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
19.4. Customizing the integration of Extended ECM for SAP Solutions
You can copy this module to a custom implementation. Select the respective Object
Key and SAP Object for the actual scenario. The customizing to activate the button is
described in “Defining and assigning action buttons” on page 526.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 623
VIM070500-08-CGD-EN-01
Chapter 19 Customizing plug-in controls for end-user screens
You can copy this module to a custom implementation to define criteria when the
workspace button is displayed or not.
624 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 20
Configuring VIM dashboards for plug-ins
You can use plug-in controls in the Invoice Approval Dashboard, the Parked
Dashboard, and the Blocked Dashboard. You must perform the following
configuration of the dashboards’ customizing profiles.
• Customizing Profile
• Customizing Profile Description
3. Double-click Profile Settings in Dialog Structure.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 625
VIM070500-08-CGD-EN-01
Chapter 20 Configuring VIM dashboards for plug-ins
4. In the Profile Settings: Details screen, maintain the settings of the customizing
profile, using the following parameters:
Customizing Profile
Customizing profile defined in Step 2.
Application Class
Enter the application class.
The logic of the plug-in integration is located in the dashboard application
class. All relevant attributes and methods of the global application class are
delivered in a baseline dashboard application. You can enhance the class by
redefining components of the class within a custom class, which can be
maintained instead of the baseline class.
Default value: /OPT/CL_C_DBP_APPLICATION
User Class
Enter the user class.
Enter the dashboard user ABAP class, which contains logic to read and save
user-specific profile settings.
Default value: /OPT/CL_C_DBP_USER
Plug-In Type
Enter the plug-in type, defined in “Defining the plug-in type” on page 615.
Default value: VIM_DBP
Plug-In ID
Enter the plug-in ID, defined in “Defining the plug-in ID” on page 616.
Plug-In Side
Select the location where the plug-in is displayed, right side or left side.
Default value: Right justified
Cont. Pane % Vt.
Content pane size ratio vertical in %: Enter the default plug-in size, in
percentage form, of the dashboard screen.
Show Plug-In
Select this check box to display the plug-in.
626 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
20.2. Assigning default profiles to product code
For the dashboard plug-in, the following product codes are relevant:
BIR
PO parking
IAP
Invoice Approval
LIX
PO blocking, both for header and item dashboard
PIR
Non PO parking
The user parameters, synchronous to the product codes, are the following:
• /OPT/CBIR_CUST_PROF
• /OPT/CIAP_CUST_PROF
• /OPT/CLIX_CUST_PROF
• /OPT/CPIR_CUST_PROF
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 627
VIM070500-08-CGD-EN-01
Chapter 20 Configuring VIM dashboards for plug-ins
628 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Part 4
Optional configuration
Part 4 Optional configuration
This part describes the basic, but optional customizing. This customizing must be
done for optional VIM features, such as the integration of SAP Shared Service
Framework.
630 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 21
Standard VIM configuration includes extended withholding tax in the tax folder of
the indexing screen. This applies to company codes and vendors that are relevant to
extended withholding tax.
Indexing screen users can change extended withholding tax code, base amount, and
amount. The data is transmitted to posting.
You can configure that the extended withholding tax data is no longer available on
the indexing screen and posting retrieves the withholding tax data from the vendor
master.
The following configuration actions are available for extended withholding tax.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 631
VIM070500-08-CGD-EN-01
Chapter 21 Extended withholding tax
If you do not want to hide withholding tax for all vendors, you can create a custom
function module that limits the hiding and put it into another constant.
Note: You can use the following VIM custom function module example as
a base for copying: /OPT/VIM_WT_LIMIT_HIDE.
3. Enter Constant Value <your custom function module name> and save.
Note: You can use the following VIM custom function module example as
a base for copying: /OPT/VIM_WT_BAPI_TRANS.
To configure that the withholding tax net amount is calculated from gross and
tax instead of using the header net amount:
2. Do not enter a Constant Value (which means “do not transfer”) but save.
632 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
To configure manual check of extended withholding tax data as a business
rule:
1. Check for existing process type 289 (NPO) / 415 (PO) in the document type
processing. If it does not exist, create it.
3. Select a country.
• The withholding tax base amount flags Inherit base and Base amount reduction
are not supported.
• Accumulation is not supported.
• Minimum or maximum amounts are not supported.
• Cash discount is not supported.
• Control data is not supported.
• Central invoice is not supported.
Limitation of exemption
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 633
VIM070500-08-CGD-EN-01
Chapter 22
Return to Vendor
The Return to Vendor (RTV) function allows you to inform the vendor by email that
the invoice is being returned. It also terminates the DP workflow. The vendor is
informed by an email, which is generated based on a template that the VIM user
selects. The email lists the reasons for the return. It may contain additional
comments and a signature. It may have the invoice image or additional images
attached. VIM users may select several different return reasons that are maintained
in VIM customizing. You may change the content of the email by implementing
your custom coding in new enhancement spots.
When the user clicks the Return to Vendor process option in the DP dashboard, a
new screen opens where all RTV-related information must be entered.
When the RTV function is performed successfully, the generated email is sent using
standard SAP functionality (SAPConnect). The DP document status is set to
obsolete, the DP workflow is finished, and the email is archived. Return reasons are
stored along with the DP step comments. Comments are mandatory.
Whereas the return reason and comments are stored in the DP document, and the
document status is changed to obsolete, the obsolete reason is not provided for the
document, which could be confusing later. Therefore, VIM 7.5 SP6 introduces the Z
constant RTV_OBSOLETE_REASON (product code 005). With this Z constant, you can
specify which obsolete reason, a two-character value, is assigned to such documents.
The following sections describe the activities that are necessary to configure the RTV
function.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 635
VIM070500-08-CGD-EN-01
Chapter 22 Return to Vendor
Starting with VIM 7.5 SP6, the system client role is checked before sending the email.
Only in productive clients, the send request is processed “immediately”. In other
client roles, the send request is processed with the SAP standard asynchronous send
procedure.
Note: Do not use the Comments required setting with RTV. The comments are
mandatory for RTV regardless of this setting, and they must be entered on the
RTV screen and not in the DP dashboard. If you select the Comments required
check box in the process option customizing, you will introduce an
unnecessary processing step.
Run the n/OPT/SPRO transaction, and navigate to Vendor Invoice Management >
Cross Component Configuration > Return to Vendor > Maintain return reasons.
If multiple languages will be used with RTV, each return reason description has to
be translated into the required languages. To translate, select GoTo > Translation in
the table maintenance dialog box.
Product Code
005
636 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
22.5. Maintaining the email determination user exit
Constant
RTV_TEMPLATE_PREFIX
Description
Prefix for standard texts used for Return to Vendor
Constant Value
/OPT/VIM_RTV
Standard texts used in the RTV process option can contain variables for fields of
the /OPT/VIM_1HEAD table. You must define the variables in the text as <1HEAD-
<FIELDNAME>>.
Product Code
005
Constant
RTV_GET_EMAIL
Description
User exit / function to retrieve email for Return to Vendor
Constant Value
<Name of the function module>
• Importing
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 637
VIM070500-08-CGD-EN-01
Chapter 22 Return to Vendor
Note: OpenText delivers a sample standard text for the vendor signature in
English: /OPT/VIM_SIGNATURE_RTV
In the standard text, you can insert variables. They will be enriched from the SAP
user address data at runtime. The following variables are available:
638 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
22.7. Maintaining email archiving
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 639
VIM070500-08-CGD-EN-01
Chapter 22 Return to Vendor
PAI-Module: USER_COMMAND_0001
In the USER_COMMAND_0001 PAI-Module, you may want to implement your own
email processing within the /OPT/ES_VIM_RTV_PROCESS_BFD enhancement
section.
640 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 23
Supplier Self Service
• The VIM Supplier Self Service Fiori app allows user based access. The Supplier
Registration app provides an automated process for suppliers to register into the
Supplier Invoices app, where suppliers can keep track of their invoices’ status.
The Supplier Accountant app provides an interface to the Supplier Care
Executives to view the status of all supplier’s invoices.
• The lean variant provides anonymous access to the Supplier Self Service – no
user account required. The user can only search for a single invoice by entering
required search criteria. If mandatory search criteria matches the invoice data in
the backend system, specific invoice status information is shown on the web
page.
Note: You should have the lean variant or the Fiori app on your system. You
cannot use both on the same installation.
Supplier Self Service lean variant is enabled for multiple deployment options:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 641
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
Most of the customization is common for both deployments. So, the customization is
differentiated wherever it is applicable. If you plan to use the On-Premise
deployment, skip “Customizing the HANA Cloud Server (option)” on page 653.
This chapter describes the customization that is necessary to use Supplier Self
Service.
You must configure your SAP NetWeaver Gateway system to allow the server
applications to retrieve the data requested by the web client. You must perform
additional configuration steps as described in this chapter. As a prerequisite, the
SAP NetWeaver Gateway 2.0 add-ons must be installed on top of an existing SAP
Business Suite or an application platform, as described in part X “Vendor Invoice
Management component for SAP NetWeaver Gateway installation” in OpenText
Vendor Invoice Management for SAP Solutions - Installation Guide (VIM070500-08-IGD).
You find more detailed information in the SAP NetWeaver Online Configuration
Guide: http://help.sap.com/saphelp_gateway20sp09/helpdata/en/4c/
a670b0e36c4c01ae2b9a042056f9dc/frameset.htm.
642 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.1. Customizing the OData Channel on the SAP NetWeaver Gateway system
Note: You can use only RFC destinations of connection type 3 (Connection
to ABAP System).
3. On the Technical Settings tab, add Target Host and System Number of the
SAP business system.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 643
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
4. Force remote logon on the target system: Therefore, on the Logon & Security
tab, manage specific Client, User, and Password information. This setting is
mandatory.
644 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.1. Customizing the OData Channel on the SAP NetWeaver Gateway system
Note: Only a user administrator can create and assign roles to users. Details
about different SAP user administrator types are available in the SAP
NetWeaver Library documentation at http://help.sap.com/nw70.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 645
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
2. In the Role Maintenance screen, enter the role already set up in the system and
assigned to the existing user. (For a new role, set up the role first.)
3. Specify the required SAP NetWeaver Gateway authorizations for this new role.
On the Authorizations tab, click Change Authorization Data.
4. From the list of template roles, select /IWFND/RT_GW_USER and click Adopt
reference. If the list of templates does not appear, click Edit > Insert
Authorization(s) > From template.
• Full authorization
b. Add authorization object S_USER_GRP
• Activity: Display
• User group in user master maintenance: Full authorization
6. Generate the profile and save your settings for the role.
646 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.1. Customizing the OData Channel on the SAP NetWeaver Gateway system
1. To directly include user IDs in the Change Roles screen, on the User tab, add
the user ID in the User ID field and press ENTER.
Alternatively, run the SU01 transaction and add the role explicitly to the user on
the Display Users screen. Therefore you have to enter or select the role name on
the Roles tab.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 647
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
• /OPT/VIM_3S_CONFIGURE
• /OPT/VIM_3S_DATA_LEAN
For every service entry, you must select the ICF Node OData and click Activate
ICF Node.
The traffic light in front of the service switches to green.
2. In the Assign SAP System Aliases to OData Service screen, configure a new
entry for every OData service, using the following parameters:
User Role
Enter or select the user role you want to assign to the system alias. Leave
this field blank to assign the system alias independent from roles.
Default System
Select this check box to set the system as default system.
648 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.1. Customizing the OData Channel on the SAP NetWeaver Gateway system
2. In the Assign Data Provider to Data Model screen, configure a new entry for
every OData service, using the following parameters:
Model Identifier
Enter or select the ID of the model the data provider is used for.
Type
Select (Adaption) Data Provider (default setting).
Software Version
Enter or select software version DEFAULT (because there is only one data
provider set to a model).
Class/Interface
Enter or select ABAP class /IWFND/CL_ODC_COE_RT_MANAGER.
Description
Optional: Enter explanatory text.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 649
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
Note: If the activation of services fails, use the SICF transaction to activate
services manually.
2. Navigate to the following path: default_host > sap > bc > ui5_ui5.
650 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.1. Customizing the OData Channel on the SAP NetWeaver Gateway system
5. When opt is created, right-click the opt service and create a new sub-element
VIM_3S_PREM.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 651
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
To bypass authorization issues for the service path, provide logon data to the
following service paths with authorized user.
1. Run the SICF transaction, and navigate to the following path: /default_host/
sap/opu/odata/.
652 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.2. Customizing the HANA Cloud Server (option)
1. Run the SICF transaction, and navigate to the following path: /default_host/
sap/bc/bsp/.
1. Run the SICF transaction, and navigate to the following path: /default_host/
sap/bc/ui5_ui5/.
Note: You need an SAP account for accessing the HANA Cloud. For more
information, see https://help.hana.ondemand.com/help/frameset.htm?
8ed4a705efa0431b910056c0acdbf377.html.
To customize the application settings, log on to the HANA Cloud Platform Cockpit
with your credentials. The cockpit is the central point for managing all activities
associated with your account and for accessing key information about your
applications. It allows you to manage all applications deployed in your account from
a single dedicated web-based user interface. You can log on to the cockpit at the
following URLs. Use the relevant URL for your account type and, in case of
customer and partner accounts, the associated region:
Europe
https://account.hana.ondemand.com/cockpit
United States
https://account.us1.hana.ondemand.com/cockpit
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 653
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
To get an overview of the current status of the application, select Dashboard in the
Content pane. This provides key information in a summarized form and allows you
initiating actions, such as starting, stopping, and undeploying applications.
Use the Destinations editor in the SAP HANA Cloud Platform Cockpit to configure
HTTP destinations. They connect the Supplier Self Service web application to the
Internet or make it consume an on-premise backend system via HTTP(S).
2. Click Create New and set up a new destination as described in the following:
654 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.2. Customizing the HANA Cloud Server (option)
Name
Enter destination name vimodataservice. This name is used by the
Supplier Self Service application to refer to remote connections.
Description
Optional: Enter a description.
Type
Select HTTP. The HTTP protocol is used for both Internet and on-premise
connections. Additionally, you must specify the destination URL, select the
ProxyType, and then the Authentication type.
URL
Enter the URL of the virtual host for connecting the Cloud connector. Make
sure that you specify the URL exactly as it is specified in the System
Mapping of the Cloud connector.
ProxyType
Select the Proxy Type of the Cloud connector. Default setting: OnPremise
CloudConnectorVersion
Select the version of your Cloud connector from the list.
Note: To use the Connectivity service 2.x and the Cloud connector 2.x
version, you must specify the property for HTTP destinations to 2.
Authentication
Select BasicAuthentication. You must enter User ID and Password.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 655
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
If you need more information about the SAP HANA Cloud Platform configuration,
see the online documentation: https://help.hana.ondemand.com/help/frameset.htm?
e47748b5bb571014afedc70595804f3e.html.
2. Login to the Cloud connector, for User Name and Password, enter
Administrator and manage (case sensitive).
Note: When you log in for the first time, you must change the password
before you continue.
656 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.2. Customizing the HANA Cloud Server (option)
1. Make sure the Landscape Host field specifies the SAP HANA Cloud Platform
landscape that you should use.
2. For Account Name and User Name (user/password), enter the values you
obtained when you registered your account on the SAP HANA Cloud Platform.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 657
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
The green icon next to Landscape Host and HTTPS Proxy indicates that they both
are valid and work properly. In case of a time-out or a connectivity issue, the icon is
respectively yellow (warning) or red (error), and a tooltip displays the cause of the
problem.
2. Configure the Cloud connector for HTTP, using the following parameters:
Virtual Host
Specify the host name exactly as it is specified as the URL property in the
HTTP destination configuration in SAP HANA Cloud.
The virtual host can be a fake name. If you leave the Internal Host
parameters blank, the Cloud connector will try to forward the request to the
658 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.2. Customizing the HANA Cloud Server (option)
network address specified by the virtual host and port. In this case, this
address needs to be real.
Virtual Port
Specify the virtual port.
This basically allows you to distinguish between different entry points of
your backend system, for example, HTTP/80 and HTTPS/443, and have
different sets of access control settings for them. For example, some non-
critical resources may be accessed by HTTP, while some other critical
resources are to be called using HTTPS only.
Internal Host
Specify the actual host under which the target system can be reached within
the intranet. The internal host must be an existing network address that can
be resolved on the intranet.
Internal Port
Specify the actual port under which the target system can be reached within
the intranet.
Protocol
Specify the protocol.
The Cloud connector can use HTTP or HTTPS for the connection to the
backend system.
This means, even if the HTTP destination on SAP HANA Cloud side
specifies http:// in its URL, you can select HTTPS. Therefore, you are
ensured that the entire connection from the on-demand application to the
actual backend system (provided through the SSL tunnel) is SSL-encrypted.
The only prerequisite is that the backend system supports HTTPS on that
port.
If you specify HTTPS and there is a “system certificate” imported in the
Cloud connector, the latter attempts to use that certificate for performing a
client-certificate-based login to the backend system. If there is no system
certificate imported, the Cloud connector opens an HTTPS connection
without client certificate.
For more information, see the online documentation about “Installation of a
System Certificate for Mutual Authentication”: https://
help.hana.ondemand.com/help/frameset.htm?
3f974eae3cba4dafa274ec59f69daba6.html
Back-end Type
Select SAP NetWeaver Gateway.
This is important mainly for metering information: tunnel connections to
any kind of SAP system are free of charge, while using the tunnel for
connecting to a non-SAP system costs a fee.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 659
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
3. After saving the hostname mapping, use the Check button to trigger a ping
from the Cloud connector to the Internal host. This option allows you to make
sure that the Cloud connector can access the Internal system. It also allows you
to catch basic issues like spelling mistakes or firewall problems between the
Cloud connector and the Internal host. In case the ping to the Internal host fails,
the Cloud connector displays a red exclamation mark icon.
1. In the Resources tab of the Access Control, select the line corresponding to the
backend system.
2. In the Add Resource dialog box, in URL Path, enter the specific URL path that
you want to allow to be invoked: /sap/opu/odate/opt.
3. Select the Enabled check box to specify that the resource shall initially be
enabled.
The Cloud connector checks that the path part of the URL is exactly as specified in
the configuration. If it is not, the request is denied.
Note: The URL check does not include a possible question mark (?) that may
denote the start of optional CGI-style query parameters.
660 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.3. Customizing Supplier Self Service
For more information about the SAP HANA Cloud connector configuration, see the
online documentation: https://help.hana.ondemand.com/help/frameset.htm?
e7d4927dbb571014af7ef6ebd6cc3511.html.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 661
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
Baseline: /OPT/VIM_3S_GET_DATA_LEAN
b. Click Display.
The invoice details are displayed, including Invoice Status, Payment
Details, and PO / DN Reference.
In the upper right corner, the processing status of the invoice is
displayed: In Process, Paid, Partially Paid, Received, or Rejected.
Fallback Language
Enter the default language. If a user has no language customized or if there
is no translation for the specified language, the default language is taken.
Network
Enter the external supplier network ID to process the status mapping.
Baseline: 3S
The following additional settings can be used for the full variant to integrate a
notification option in the user self registration process for vendors. In baseline
delivery, the notification sends an SAP mail to the administrator who is
responsible for the onboarding process of the users. The email contains the
corresponding information of the user who registers for the application.
662 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.4. Configuring the status
Notification Text
Enter a text object for the notification email context. You can maintain text
objects using the SO10 transaction. The first line of the text stored in SO10 is
used as the subject line of the email.
Language
Enter the language for the notification mail.
2. In the Define Supplier Networks screen, maintain an entry for the Supplier Self
Service, using the following parameters:
Netw
Enter a two-digit identifier for the external supplier network.
Default value: 3S
Supplier Network
Enter the name of the external supplier network.
Default value: Supplier Self Service
Class Name
Enter the name of the class containing the processing logic for the external
supplier network.
Default value: /OPT/CL_E_SUPPLIER_NETW_3S
Notes
3. To define the status known in Supplier Self Service, select the entry for Supplier
Self Service and double-click Define External Status in the Dialog Structure.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 663
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
4. In the Define External Status screen, maintain entries for all status codes
known in Supplier Self Service, using the following parameters:
ExtStatID
External Invoice Status
Enter a two-digit, artificial key for the status of the external supplier
network.
External Status
External Invoice Status as known by the Network
Enter the invoice status as known by the external supplier network.
Example: inprocess
Note: Ensure that the status code in the field External Status is exactly
the status code that is delivered by Supplier Self Service. Pay attention
to lower and upper case.
External Status Description Long
Enter a description for the invoice status of the external supplier network.
Example: In process
5. To map the process status of a VIM invoice to the status codes that are known in
Supplier Self Service, double-click Assign External Status to VIM Document
Status in the Dialog Structure.
The process status of a VIM invoice is a combination of the VIM document
status, the SAP document status and the previous status determined by the
external supplier network. A combination of these three status codes determines
the new external status code.
6. In the Assign External Status to VIM Document Status screen, maintain status
mappings for Supplier Self Service, using the following parameters:
Document Status
Enter the VIM document status.
Example: 00 (Created)
664 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.5. Configuring the layout
SAP Status
The status of the SAP invoice is not relevant for the Supplier Self Service
component.
PrevStat
Previous External Invoice Status
Enter the artificial key for this previous external invoice status.
Supplier Self Service determines an invoice status for posted invoices: PA for
paid, PP for partially paid.
ExtStatID
External Invoice Status
Enter the artificial key for the new status that should be given to Supplier
Self Service.
Table
Source table for the displayed field
Field name
Name of the displayed field. The name cannot be extended dynamically.
Field Description
Enter text that is shown on the user interface.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 665
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
Output Length
Enter the length of the field on the user interface.
2. In the Supplier Self Service - Field Configuration per User screen, define fields
that are shown in the user interface dependent on the user, using the following
parameters:
UserID
User for whom the settings are applied
Table
Source table for the displayed field. As defined in the field definition; see
“Defining fields” on page 665.
Field name
Name of the displayed field. The name cannot be extended dynamically. As
defined in the field definition; see “Defining fields” on page 665.
Field Status
Specify the status of the field in the user interface: Click Display or Hide in
the list.
2. In the Supplier Self Service - Output Texts screen, define texts for headers,
using the following parameters:
666 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.6. Configuring company code settings
Property
User interface related value. It cannot be changed or extended.
Description
Enter text that will be shown in user dependent language.
Logical System
On the satellite system, configure your logical system. On a central system
within a multiple backend scenario for the Supplier Self Service application,
you must configure all mappings of all relevant systems where data is
collected, or the corresponding aggregation group of Central Reporting
needs to create related entries. For more information, see section 5.6
“Scheduling batch jobs for Supplier Self Service” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM070500-08-AGD).
Company Code ID
Unique company code ID
Company Code Text
Enter text that is shown on the user interface for this company code.
Additional Information
Enter additional text that is shown on the user interface for this company
code, for example the address.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 667
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
2. In the Supplier Self Service - Company Codes Mapping screen, map company
codes, using the following parameters.
Logical System
On the satellite system, configure your logical system. On a central system
within a multiple backend scenario for the Supplier Self Service application,
you must configure all mappings of all relevant systems where data is
collected, or the corresponding aggregation group of Central Reporting
needs to create related entries. For more information, see section 5.6
“Scheduling batch jobs for Supplier Self Service” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM070500-08-AGD).
Company Code
Company code from the master data
Company Code ID
Your defined company code ID
668 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.7. Configuring the supplier settings
• Supplier definition
• Supplier mapping
Logical System
On the satellite system, configure your logical system. On a central system
within a multiple backend scenario for the Supplier Self Service application,
you must configure all mappings of all relevant systems where data is
collected, or the corresponding aggregation group of Central Reporting
needs to create related entries. For more information, see section 5.6
“Scheduling batch jobs for Supplier Self Service” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM070500-08-AGD).
Supplier ID
Unique supplier ID
Name
Enter text that is shown on the user interface for this supplier.
Email Address
Enter the email address of the supplier.
Active
Select this check box to activate the supplier for the Supplier Self Service
component.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 669
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
2. In the Supplier Self Service - Supplier Mapping screen, map suppliers, using
the following parameters.
Logical System
On the satellite system, configure your logical system. On a central system
within a multiple backend scenario for the Supplier Self Service application,
you must configure all mappings of all relevant systems where data is
collected, or the corresponding aggregation group of Central Reporting
needs to create related entries. For more information, see section 5.6
“Scheduling batch jobs for Supplier Self Service” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM070500-08-AGD).
Vendor
Vendor from the master data
Supplier ID
Your defined supplier ID
You must configure all the allowed Gateway-related and application parameters to
run the Supplier Self Service On-Premise solution smoothly on supported browsers.
670 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.8. Configuring Gateway host and application parameters
APPNAME
Application Name in read-only-mode. You cannot modify it. This is an
optional field, meant for future usage of the product.
PROTOCOL
SAP NetWeaver Gateway Hosted Server Protocol. Enter HTTP or HTTPS.
HOST
SAP NetWeaver Gateway host. Enter a valid host with domain.
PORT
SAP NetWeaver Gateway port. Enter a valid port.
LEANACTIVE
Enter default value TRUE.
HEADERIMGPATH
Enter default value RESOURCES/
HEADERBAR_VENDOR_INVOICE_MANAGEMENT.PNG.
Note: You can customize this header image. Replace it with a valid
PNG file under the MIMES > resources path of the BSP application,
which is available in the SAP Gateway server.
SHOWHEADER
Enter default value TRUE.
SHOWFOOTER
Enter default value TRUE.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 671
VIM070500-08-CGD-EN-01
Chapter 23 Supplier Self Service
You choose the vendor for deletion and click Delete in the application menu.
The deletion of the vendor implies the deletion of vendor data that is used in the
Supplier Self Service configuration, customization, and the invoice data stored in
Supplier Self Service tables.
The following tables are cleaned when the program is run for a vendor:
• /OPT/WT_3S_SLREG
• /OPT/WT_3S_SUPPL
• /OPT/WT_3S_SUPPM
• /OPT/WT_3S_USER
• /OPT/WT_3S_MAP
• /OPT/WT_3S
• /OPT/WT_3S_PYMNT
• /OPT/WT_3S_VALUE
The program provides built-in checks to ensure that only VIM specific data is
modified or deleted. The program also provides a specific authorization check. The
authorization object is J_6NIM_CA6.
672 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
23.9. Vendor cleanup program for Supplier Self Service
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 673
VIM070500-08-CGD-EN-01
Chapter 24
VIM provides the following Fiori apps as part of Supplier Self Service Fiori apps:
Prerequisites The following components are required to run the Supplier Self Service apps:
• VIM package
Starting with VIM 7.5 SP8 and VIM 16.3.2, Supplier Self Service Fiori apps are
supported both on premises and on cloud.
Fiori Launchpad content transports are delivered for preconfigured tiles. For more
information, see “Integrating VIM Fiori apps into Fiori launchpad” on page 451.
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/72179700
/OTBCWUI/PS30_VIM
Solution for Approval Management, Enter Cost Assignment, Confirm Quantity
and Price, Exceptions, and My Approved Invoices
/OTBCWUI/PS30_VIM_BULKAPPR
Solution for Approve Invoices (bulk mode)
/OTBCWUI/PS34_VIM_ACC
Solution for Supplier Self Service accountant perspective
/OTBCWUI/PS34_VIM
Solution for Supplier Self Service supplier perspective
For more details, see section 6.5 “Fiori launchpad content” in OpenText Business
Center for SAP Solutions - Installation Guide (BOCP160302-IGD).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 675
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
You can configure application settings in the Business Center Configuration and also
in the VIM Invoice Approval Configuration. The specific baseline customizing is
delivered separately for both components.
For more details and further information about the Fiori Launchpad, see http://
scn.sap.com/docs/DOC-53178.
When creating tiles for the Launchpad, there are three different ways how you can
link an application. For a UI5 application that is delivered as component, only the
“Target Mapping SAP UI5 Fiori App” mechanism is recommended.
Direct Link
The tile is directly referring to a relative or absolute URL.
676 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.1. Fiori Launchpad integration
Because the Fiori Task App is delivered as a UI5 component, the tile creation
description is referring to “Target Mapping SAP UI5 Fiori App”.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 677
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
Note: For Supplier Self Service apps, two catalogs are necessary. Create a
catalog for the Supplier Invoices app. And create another catalog for the
Supplier Accountant app. You can assign any appropriate Title and ID.
Make sure that the ID is unique.
If you plan to enroll the Fiori Launchpad configuration to another Fiori
server, ensure that a customizing request is specified, using the Settings
button.
678 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.1. Fiori Launchpad integration
Note: Create a catalog for the Supplier Invoices app. Create another
catalog for the Supplier Accountant app. You can assign any appropriate
Title and ID. Make sure that the ID is unique.
3. Create a Supplier Invoices app target mapping.
In the Launchpad Designer, you must create one target mapping to the Fiori
Task App.
a. In the Intent area, choose the Semantic Object you have created in Step 1
on page 677 and specify an Action.
You can freely define the action. You must remember it when creating the
tiles. For that string, no value help is provided.
b. In the Target area, click SAP UI5 Fiori App for the Source of Navigation
Target.
c. Enter the parameters exactly as follows.
Title
<A title of your choice>
URL
/sap/bc/ui5_ui5/otbcwui/pf07_bc_ui_03
Component
ot.approve.requests03
Note: You must use the semantic object created in Step 1 on page 677
whereas the rest of the configuration will remain same for both
Supplier Invoices app and Supplier Accountant app.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 679
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
4. Create tiles.
After you have defined the target mapping, you can create the required tiles.
Create a tile for the Supplier Invoices app in its respective catalog. Create
another tile for the Supplier Accountant app in its respective catalog.
General
Title
<A title of your choice>
Subtitle
<A subtitle of your choice>
Icon
<An icon of your choice>
Example: sap-icon://Fiori2/F0021
Dynamic data
Service URL
There is no need to maintain a Service URL.
Navigation
680 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.1. Fiori Launchpad integration
Action
Enter the action that you have defined in Step 3 on page 679.
Parameters
Example: If the system alias of the backend system for the Supplier
Invoices app is TWRCLNT800, then parameters are the following:
workplaceId=SUP_INBOX&system=TWRCLNT800&appMode=FS
Example: If the system alias of the backend system for the Supplier
Accountant app is TWRCLNT800, then parameters are the following:
workplaceId=ACC_INBOX&system=TWRCLNT800&appMode=FS
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 681
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
682 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.1. Fiori Launchpad integration
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 683
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
On the menu on the right, users must click Personalize Homepage. Then, they
can search for the created Supplier Self Service catalog and add the required
tiles from it to the Home Page.
Notes
• Business Center OData service version 3 is required for the Supplier Self
Service apps to work.
The SAP user account that is used on the SAP Fiori UI / Gateway system requires the
following:
The SAP user account that is used on the SAP ERP system requires the following:
• The role that is created for the SAP Fiori catalog (see To assign a catalog to a role:
on page 681) should be assigned to the Template User, which is maintained in
SAP Front End and Gateway systems.
• Additionally, the User Authorizations mentioned in this section should be
maintained in a role and that role should be assigned to Template User of SAP
Front End and SAP ERP systems.
Note: For details about the Template User, see “User Self Service roles and
authorizations” on page 703.
684 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
• The role that is created for the Supplier Accountant app should be assigned to
the user.
• Additionally, the User Authorizations mentioned in this section should be
maintained in a role and that role should be assigned to the user.
Note: The SAP user must have the identical user name on the SAP ERP and the
SAP Gateway system.
3. If the supplier is not yet registered into the Supplier Invoices app, a
registration mail is triggered.
4. Through this registration mail the supplier can register into the Supplier
Invoices app.
Key features
Limitations
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 685
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
3. For Process Type 426, select the Active check box, and save your changes.
686 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
Users, Roles, and Authorizations for User Self Service – Create the following types
of users:
• Service User
• Admin User
• Reference User
Service User
The Service User is used by anonymous users to create requests to create users,
or to reset the password for the users created.
The Service User is an Internet user created both in the SAP Gateway hub, and
in the SAP Business Suite System with the IWBEP add-on.
1. Create a user of type Service, for example gwusssrv, with the /IWFND/
RT_GW_USR role template.
2. To your newly created Service User, assign roles for creating, and unlocking
users, as well as changing passwords for users, in SAP NetWeaver AS
ABAP.
To set up the Service User in the SAP Business Suite with IW_BEP add-on:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 687
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
Admin User
The Admin User is required in the SAP Gateway with the IW_BEP add-on for the
following actions:
To setup the Admin User in the SAP Business Suite system with IW_BEP
add-on:
Reference User
Create Reference Users in both SAP Gateway hub and SAP Business Suite
System with IW_BEP add-on.
Reference Users are used as a reference to create named users in SAP
NetWeaver AS ABAP.
3. Maintain the user profile, using the roles tab in the User Management tool
(SU01) in SAP NetWeaver AS ABAP.
4. Assign the set of roles that are required for the users to be created out of the
Reference User.
5. Enable changing the password, using the roles in the User Management tool
in SAP NetWeaver AS ABAP.
688 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
To set up the Reference User in the SAP Business Suite system with
IW_BEP add-on:
3. Maintain the user profile, using the roles tab in the User Management tool
(SU01) in SAP NetWeaver AS ABAP.
24.3.2.2 Configuring the SAP Business Suite system for User Self Service
This section describes the settings on the SAP Business Suite system that are
required for User Self Service.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 689
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
6. On the Technical Settings tab, Load Balancing Status area, click the relevant
option according to your system’s settings.
7. In the Target Host field, enter the (message) server name of the SAP system.
8. In the System Number field, enter the SAP NetWeaver system number, for
example 00.
690 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
9. On the Logon & Security tab, Logon area, enter the SAP system’s Client
number.
11. Click Yes for Trusted System and save your settings.
1. Run the SPRO transaction, open the SAP Reference IMG and navigate to SAP
NetWeaver > SAP Gateway Service Enablement > Backend OData
Channel > User Self Service Setup > Maintain RFC Destinations for User
Replication.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 691
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
Note: The implementation type must be IWBEPUM if you want to use the
default User Self Service solution from SAP Gateway.
Create a type 3 RFC destination with the name IWBEP_UM_BGRFC for the
inbound queue:
692 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
6. Click the Special Options tab and click Classic with bgRFC in the Transfer
Protocol list.
The following inbound destination configuration is required for executing the user
creation and user maintenance process in asynchronous mode.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 693
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
694 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 695
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
4. In the RFC Destination field, enter a name, for example <XX>_TRUST, where
<XX> refers to the SAP Business Suite system.
7. On the Technical Settings tab, in Load Balancing, click the relevant option
according to your system’s settings.
8. In the Target Host field, enter the (message) server name of the SAP Business
Suite system.
9. In the Instance No. field, enter the SAP NetWeaver system number, for example
00.
4. Click Continue.
5. On the log-on screen that is displayed, log on with the User with the
authorization object S_RFCACL.
696 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
4. In the RFC Destination field, enter a name, for example <XX>_TRUST, where
<XX> refers to the SAP Gateway system.
5. In the Connection Type field, enter 3.
6. In the Description 1 field, enter an explanatory text and click Save.
7. On the Technical Settings tab, in Load Balancing, click the relevant option
according to your system’s settings.
8. In the Target Host field, enter the (message) server name of the SAP Business
Suite system.
9. In the System Number field, enter the SAP NetWeaver system number, for
example 00.
10. Save your settings.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 697
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
4. In the RFC Destination field, enter a name, for example <XX>CLNT800, where
<XX> refers to the SAP Business Suite system.
7. On the Technical Settings tab, in Load Balancing, click the relevant option
according to your system’s settings.
8. In the Target Host field, enter the (message) server name of the SAP Business
Suite system.
9. In the System Number field, enter the SAP NetWeaver system number, for
example 00.
10. On the Logon & Security tab, enter the SAP system’s client number.
11. On the Logon & Security tab, activate the current user.
12. For the Trust Relationship, activate Yes and save your settings.
24.3.2.4 Configuring the SAP Gateway system for User Self Service
The following procedures refer to the SAP NetWeaver system, where the SAP
Gateway component is installed, for User Self Service.
698 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
f. Enter the Service User name in the User field and a password in the
Password field. For more information, see “Security aspects of User Self
Service” on page 687. This ensures that the service /IWBEP/
USERREQUESTMANAGEMENT is always executed in the service user context.
h. Click the Service Data tab and then click GUI Configuration.
3. Add the System Alias with the destination (<XX>CLNT800) created in “To create
the destination for the trusted connection for communication between SAP
Gateway system and SAP Business Suite system:“ on page 698.
f. Enter the Service User name in the User field and a password in the
Password field. For more information, see “Security aspects of User Self
Service” on page 687.
6. Add the System Alias with the destination (<XX>CLNT800) created in “To create
the destination for the trusted connection for communication between SAP
Gateway system and SAP Business Suite system:“ on page 698.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 699
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
24.3.2.5 Performing User Self Service IMG activities in the SAP Business
Suite System
User Self Service specific configuration tasks are included in the SAP Gateway
Implementation Guide (IMG), which is available in the system.
To access these IMG activities, run the SPRO transaction, open the SAP Reference
IMG and navigate to: SAP NetWeaver > SAP Gateway Service
Enablement > Backend OData Channel > User Self Service Setup.
2. Maintain Number Range Interval for User Self Service (mandatory): Use this
activity to maintain the number range for generating the users in the SAP
system.
700 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
Note: No. must be 01 and the interval From number must be greater than
0.
4. Maintain User Category (mandatory): Maintain the list of user categories for
your application using this activity.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 701
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
Version
Enter the version. By default, enter 1.
Namespace
Enter /OTX/ for PS33_USREGSRV_SRV and /IWBEP/ for
USERREQUESTMANAGEMENT.
User Category
Enter 1.
Reference User Name
Enter the Reference User created in “Security aspects of User Self Service”
on page 687.
5. Define Handler for User Management Notification: This is an activity for the
BAdI /IWBEP/BD_MGW_UM_NOTIFICATION to notify about the user creation.
702 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
3. To resend the email report, enter the company code in the COMPCODE field or
specific vendors in the VENDOR field.
Template User roles and authorizations are copied to supplier users created during
the Registration process.
For required roles and authorizations that need to be applied for the Template User,
see “User authorization” on page 684.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 703
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
5. Enter the User ID of the Template User in this constant, Value field.
Notes
• The Template User must be available in both SAP Gateway and SAP
ERP / SAP Business Suite systems.
• The Template User must have all the roles and authorizations required
for the Supplier Invoices app.
Application Name
Enter /OTBCWUI/PS31_3S_USREG.
Protocol
Enter HTTP or HTTPS.
Gateway Host
Enter the fully qualified name of the Gateway Host.
Gateway Port
Enter the port number.
Active
Enter TRUE.
Show Hdr
Show Header. Enter TRUE.
Show Fo...
Show Footer. Enter TRUE.
704 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.3. Configuring the Supplier Registration app
Note: The configuration for Company Codes, Suppliers, and Users is filled
automatically during the User Registration process.
To configure log in to Fiori Launchpad with alias name (SAP Gateway system):
3. On the Define Services screen, in Hierarchy Type, enter SERVICE and click .
4. Navigate to /default_host/sap/bc/ui2/flp.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 705
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
8. Navigate to /default_host/sap/bc/ui5_ui5/ui2/ushell.
706 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.4. Configuring the Supplier Invoices app
Key features
Business The VIM Supplier Invoices Fiori app, based on SAP Fiori, runs on top of the
Center configu- OpenText Business Center for SAP Solutions product. It is an optional component. It
ration
provides a Fiori Task App that enables suppliers to keep track of their invoices’
status. It also shows additional information like payment status and SAP documents
linked to the invoice, for example Purchase Order number and Delivery Note
number.
You can configure application settings within the Business Center Configuration and
also in the VIM Invoice Approval Configuration. The specific baseline customizing
is delivered separately for both components.
For more information on the Business Center Configuration, see OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
For more information on the Business Center Solution Integration for Vendor
Invoice Management, see “Apps based on the Fiori Task App“ on page 441.
You can customize the settings described in this section in the Business Center
Configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 707
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
PS34_VIM_S3_INV_O
Node for the All tab (fetch all supplier invoices)
PS34_VIM_S3_INV_M
Node for the This Month tab (fetch invoices prior to 30 days)
PS34_VIM_S3_INV_Q
Node for the This Quarter tab (fetch invoices prior to 120 days)
PS34_VIM_S3_INV_Y
Node for the This Year tab (fetch invoices prior to 365 days)
3. To customize the order of the nodes, edit the values in the Node pos. (Node
position) column.
For more information, see section 8.6.3 “Assigning nodes to work centers” in
OpenText Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
708 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.4. Configuring the Supplier Invoices app
2. Mark the Node ID of the tab for which you want to configure the sort field.
Example: Mark Node ID PS34_VIM_S3_INV_O to configure sorting for the All tab.
3. Add the sort field from the list of supported sort fields, using the following
parameters:
Field Name
Enter the technical name of the field.
Position
Enter a numeral. The display order of the sort fields is based on this field.
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 709
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
2. Mark the Node ID of the tab for which you want to configure the search field.
Example: Mark the PS34_VIM_S3_INV_O Node ID to configure searching for the All
tab.
3. Add the search field from the list of supported search fields using the following
parameters:
Field Name
Enter the technical name of the field.
Position
Enter a numeral. The display order of the search fields is based on this field.
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
710 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.4. Configuring the Supplier Invoices app
2. Mark the Node ID of the tab for which you want to configure the filter field.
Example: Mark the PS34_VIM_S3_INV_O Node ID to configure filtering for the All tab.
3. Add the filter field from the list of supported filter fields using the following
parameters:
Field Name
Enter the technical name of the field.
Position
Enter a numeral. The display order of the filter fields is based on this field.
No multi
This check box is not used in this version.
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 711
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
Then double-click Full Screen List - Data Binding in the Dialog Structure.
Field Name
Enter the technical name of the field.
Note: The following fields are supported:
• XBLNR
• STATUS_TXT
• BLDAT
• PYMNT_TERMS
• DOCID
• GROSS_AMOUNT
• WAERS
• NAVLINK.
Other fields are not supported to configure the full screen list - data
binding.
712 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.4. Configuring the Supplier Invoices app
Width (CSS)
Enter the width of the field in percent.
For more information about these settings, see “Configuring company code settings”
on page 667.
For more information about these settings, see “Configuring the supplier settings”
on page 669.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 713
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
6. Delete the entries of this user from this table and save your changes.
After deletion of entries in the Supplier Self Service tables, remove the role created
for the Supplier Invoices app from the roles of the user for which you want to
deactivate the Supplier Invoices app.
Remove all the roles given to this user in the context of the Supplier Invoices app
from this user.
• Supplier
• Supplier Care Executive
714 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.5. Configuring the Supplier Accountant app
You can configure application settings within the Business Center Configuration and
also in the VIM Invoice Approval Configuration. The specific baseline customizing
is delivered separately for both components.
For more information on the Business Center Configuration, see OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
For more information on the Business Center Solution Integration for Vendor
Invoice Management, see “Apps based on the Fiori Task App“ on page 441.
You can customize the following settings in the Business Center Configuration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 715
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
3. Add the sort field from the list of supported sort fields, using the following
parameters:
Field Name
Enter the technical name of the field.
Note: Only the BLDAT field is supported for the sorting.
Position
Enter a numeral. The display order of the sort fields is based on this field.
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
3. Add the search field from the list of supported search fields using the following
parameters:
Field Name
Enter the technical name of the field.
Note: Supported search fields are BUKRS, DOCID, GROSS_AMOUNT, and
XBLNR. For other fields, search is not supported.
716 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.5. Configuring the Supplier Accountant app
Position
Enter a numeral. The display order of the search fields is based on this field.
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
2. Mark the PS34_VIM_S3_INV Node ID, and double-click Filter fields in the
Dialog Structure.
3. Add the filter field from the list of supported filter fields using the following
parameters:
Field Name
Enter the technical name of the field.
Note: Supported filter fields are BLDAT, LIFNR, and STATUS_TXT. For
other fields, filtering is not supported. Multi-selection within filters is
not supported.
Position
Enter a numeral. The display order of the filter fields is based on this field.
No multi
This check box is not used in this version.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 717
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
For more information, see section 8.6.2.1 “Adding fields for searching, sorting, and
filtering to a node” in OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD).
2. Mark the PS34_VIM_S3_INV Node ID and double-click Full Screen List - Data
Binding in the Dialog Structure.
Field Name
Enter the technical name of the field.
• XBLNR
• STATUS_TXT
• BLDAT
• PYMNT_TERMS
• DOCID
• GROSS_AMOUNT
• WAERS
• NAVLINK.
Other fields are not supported to configure the full screen list - data
binding.
718 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.5. Configuring the Supplier Accountant app
Width (CSS)
Enter the width of the field in percent.
3. Delete entries that are not mentioned in the screenshot. Otherwise the
document date filter does not work as expected.
For more information about these settings, see “Configuring company code settings”
on page 667.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 719
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
For more information about these settings, see “Configuring the supplier settings”
on page 669.
User ID
Enter the user ID.
E-Mail Address
Enter the email address of the user.
Language
Enter EN.
Note: Other languages are not supported.
LogSystem
Enter SAP logical system details
720 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.5. Configuring the Supplier Accountant app
Supplier ID
Enter the Supplier ID of the supplier that you want to link to this user.
Name
Enter the name of the supplier that you want to link to this user.
UserID
Enter the user ID of the accountant.
CompCodeID
Enter the Company Code ID of the company code that you want to link to
this user.
Department
No need to fill this information.
After deletion of entries in the Supplier Self Service tables, remove the role created
for the Supplier Accountant app from the roles of the user for which you want to
deactivate the Supplier Accountant app.
Remove all the roles given to this user in the context of the Supplier Accountant app
from this user.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 721
VIM070500-08-CGD-EN-01
Chapter 24 Supplier Self Service Fiori apps
2. On the 3S Fiori Registration App URLs screen, configure the application, using
the following parameters:
Application Type
Two application types are available. Select from the list:
• 3S Registration On-Cloud
• 3S Confirmation On-Cloud
Application URL
722 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
24.6. Configuring the Supplier Self Service app on the cloud
Example: HTTPS://OTUSRREGUIV5-A9E96CFA0.DISPATCHER.HANA.
ONDEMAND.COM
• For the 3S Confirmation On-Cloud URL, configure the URL that is
derived from the Portal Service of the Fiori Launchpad site. For more
information, see “Integrating VIM Fiori apps into Fiori launchpad”
on page 451.
Example: HTTPS://FLPNWC-A9E96CFA0.DISPATCHER.HANA.
ONDEMAND.COM/SITES?SITEID=5CE0A2AA-2B38-4667-
BA93-4E5FC23AF02B
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 723
VIM070500-08-CGD-EN-01
Chapter 25
Integration with Information Extraction Service
Starting with VIM 7.5 SP8 and VIM 16.3 SP2, OpenText™ Information Extraction
Service for SAP® Solutions (IES) can be used in scenarios that require OCR. The
support of IES is built on using the new features delivered with Business Center
16.3.2. It requires this support package of Business Center, as well as the Business
Center-based VIM solution, which is delivered for VIM 7.5 SP8 with the component
OTBCSL03. In VIM 16.3.2, it is built into the core VIM delivery.
This chapter describes configuration required for IES and VIM integration, which is
specific for VIM. General Business Center configuration that is required for IES
integration is documented in section 4.5 “Customizing capture” in OpenText Business
Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
Notes
The following settings are provided with the BC sets. Do not change them:
Note: The VIM channel is using the standard VIM mapping GENERAL.
The following procedure shows the additional required steps to enable the IES
integration. The OpenText Business Center for SAP Solutions - Configuration Guide
(BOCP160302-CGD) provides more details on some of the configuration tasks.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 725
VIM070500-08-CGD-EN-01
Chapter 25 Integration with Information Extraction Service
1. Customize ArchiveLink:
726 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
b. On the Profile Overview screen, mark an profile ID and double-click
Document Type Assignment in the Dialog Structure.
c. Assign the extraction profile to the archiving document type.
6. Activate the created extraction profile in the system that will be actually
integrated with the IES service.
Note: It can take some minutes until the profile will be completely
activated and ready to be used for extraction.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 727
VIM070500-08-CGD-EN-01
Chapter 26
Integration with the Ariba Network
VIM can be integrated with the Ariba Network on the buyer side. In this scenario,
suppliers create invoices within the Ariba Network. The invoices are sent to the SAP
ERP system of the buyer. The buyer processes all incoming invoices within VIM.
Besides local invoice channels (email, or scan, or OCR), the buyer is connected with
the Ariba Network and receives invoices of his suppliers from this channel.
Ariba can be integrated in different ways within the SAP Business Suite.
• On the one hand, an integration with the SAP NetWeaver Process Integration
(PI) in combination with the Ariba PI adapter is possible. Technically, the
invoices are then sent in IDoc format (INVOIC02) to the SAP ERP system of the
buyer.
PI integration is supported with the Ariba Network Adapter 11s2 and 12s2 as
well as with the newer Ariba Cloud Integration components from Ariba. For the
latter, VIM supports the version CI-8 and later versions.
For a list of supported support packages of VIM, VIM Ariba Integration
component, Ariba Network Integration for SAP Business Suite, and PI
integration components, see the Knowledge Base article 58540435 (https://
knowledge.opentext.com/go/58540435).
• On the other hand, it is possible to connect Ariba with the new SAP add-on Ariba
Network Integration for SAP Business Suite. The add-on is built based on web
service technology and can be connected to Ariba Network either direct or
mediated via PI or other middleware. Technically, the invoices are sent in cXML
format. For technical details, see the SAP Service Marketplace.
VIM integration The standard business application (IDOC integration or Ariba SAP add-on
integration) posts or parks the invoices automatically on the SAP ERP backend
system without the possibility to handle exceptions within a workflow. With the
integration of VIM, the DP workflow starts and VIM is the single point of access for
all invoices. VIM processes exceptions, both for invoices received electronically or by
paper. VIM controls the process for the automated reconciliation and posting.
Invoice status During the invoice process, the Ariba Network retrieves status information of the
invoice process in the SAP ERP system. The Ariba Network updates the invoice
status on the network. This enables vendors to see the processing status of their
invoices on the Ariba Network. For details of updating the invoice status on the
Ariba Network for VIM, see “Outbound processing (StatusUpdate)” on page 741.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 729
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
– Transfer of invoices posted directly in SAP ERP for vendors integrated into
the Ariba Network. OpenText provides a BADI implementation to prevent
duplicates when using standard SAP CC invoice integration.
You find details about installation and configuration of the SAP add-on Ariba
Network Integration for SAP Business Suite 1.0 on the SAP Service Marketplace. For
relevant prerequisites, see part XII “Vendor Invoice Management ARIBA Integration
730 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.1. Integrating Ariba SAP Business Suite Adapter
Starting with Business Center 10.0 SP1 and Business Center Solution Integration for
Vendor Invoice Management 10.0 SP2, you can use Business Center Inbound
Configuration to handle incoming document processing. For more information
about how to configure document registration for custom registration and document
handler, see section 4.4.2.5 “Customizing a custom registration type” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP160302-CGD).
To activate the Ariba processing for Business Center Inbound Configuration, you
must activate the BC_INBOUND Z constant.
1. Run the SPRO transaction and navigate to Integration with Other mySAP.com
Components > SAP Business Suite Integration Component for Ariba >
Application Specific Settings > SAP ERP Integration Component for Ariba >
Business Add-Ins (BAdIs) > BAdI: Inbound Mapping.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 731
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
3. To maintain the inbound processing for the corresponding network, run the /
OPT/SPRO transaction and navigate to Document Processing Configuration >
General Configuration > Incoming Document Processing > Maintain
Processing for Supplier Network.
1. Processing of inbound cXML messages and storing them in form of key and
value according to the Ariba specific mapping. For more information, see
“Mapping fields (Ariba specific mapping)” on page 733).
2. Business Center Inbound processing with Ariba specific mapping. At this step,
invoice attachments are archived, and a VIM DP document and corresponding
DP workflow is created. See also “Mapping VIM fields” on page 735.
To process the inbound cXML messages in case of direct connectivity, the program
ARBFND_FETCH_CXML_MESSAGES must be scheduled to run periodically
(ARBFND_FETCH_CXML_MESSAGES_NEW for SAP components ARBERP SP2 and higher).
In case of mediated connectivity, the interface will be called automatically by PI. You
can monitor errors on this step with standard SAP tools like Application log
(transaction SLG1, to be started with the object ARIBA_INTEGRATION.
732 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.1. Integrating Ariba SAP Business Suite Adapter
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management >
Document Processing Configuration > General Configuration > Incoming
Document Processing > Ariba Data Mapping.
The mapping is conceptually similar to the IDoc mapping. It points to the specific
fields in the input structure, allowing to choose the starting point in the structure
and, in case a list of values is provided, search for specific lines of internal tables by
the use of qualifiers.
Not all cXML fields can be mapped by creating new configuration entries, only.
Unlike IDocs, which have a table-like two-dimensional structure, cXML is
transformed internally into an ABAP structure with many levels of nesting. If the
nesting involves internal tables, OpenText mapping allows to perform table lookups
using qualifiers.
However, only one level of such lookups is possible. It is not possible to handle
tables inside of tables. The standard mapping logic will simply extract the first line
of each table when traversing a path that is not specified by a qualifier. For such
cases, you can use a function module mapping.
In the baseline configuration, OpenText delivers several function modules. You can
use them as an example of how to implement logic for any project specific fields.
Path Type
Select the path type:
Header
The mapping path to the field begins at request-invoice_detail_request
of the structure ARBERP_XINVC_S_CXML.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 733
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
Service item
The mapping path to the field begins at request-
invoice_detail_request-invoice_detail_order-
invoice_detail_service_item.
Field path
Enter the field path. This setting denotes the further path to the field, starting
where the shortcut set in path type ends. The path is traversed step by step to
find the fields. If there is any internal table used in the path, either its first line is
read, or the qualifier is used to find the line. You can use qualifiers only if the
table is the last element of the path.
Qualifier Field Name
Enter the field name that is used to search lines of internal tables. If the value # is
entered, the qualifier value must be numeric, containing the index of the table
line to read.
Qualifier Field Value
Enter the value that will be searched for in the field set in the Qualifier Field
Name to find the needed table line. It can contain a line index if # is used instead
of the qualifier field name.
Field Name
Enter the name of the source field to map.
Document Field Name
Enter the name of the target field to map.
Note: This is not yet the name of DP document fields but the field name to
be used as a source field in the second (VIM fields) mapping.
Field Mapping Type
Select V for the value to be assigned without any conversions. Alternatively, you
can use a function module (mapping type = M).
Value
Enter the name of the function module to be called for field value conversion.
For header fields, the function module /OPT/VIM_ARB_TEMPLATE_2 provides an
interface template.
For item fields, the function module /OPT/VIM_ARB_TEMPLATE_3 provides the
interface template.
Store Original Value
This check box is no longer in use. It was used in earlier versions of VIM with
the Incoming Document Handling (IDH) module.
734 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.1. Integrating Ariba SAP Business Suite Adapter
The selection of the main invoice document is controlled by the external profile
settings in the channel settings for the ARIBA channel. There must be exactly one
entry provided in the external profiles list. If this entry has set the PDF document
class, the PDF file is chosen as the main document. If the XML document class is set,
the cXML message itself is saved as an XML file and is used as the main document.
The archiving document type for the main document is set according to the value in
the external profile.
The archiving document type for other documents is read from the VIM constant
table, the constant 005/ADDL_DOCS_AR_OBJECT.
Notes
• Make sure that you maintain appropriate archiving settings for both
archiving document types. Links must normally be set in the OAC3
transaction for BOR types /OPT/V1001 and SAP document object types.
In the following example, the invoice PDF file is set as the main invoice document.
This setting is delivered as standard configuration:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 735
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
Application log The first (ARIBA specific) mapping is run by the program
ARBFND_FETCH_CXML_MESSAGES / ARBFND_FETCH_CXML_MESSAGES_NEW (for direct
connectivity, or by the PI in case of mediated connectivity) . You can verify the
results of the processing in the application log, transaction SLG1, to be started with
object ARIBA_INTEGRATION.
Error types In case of non-recoverable errors, like missing configuration, the processing aborts at
this step. If you are using custom mapping functions, return a message of type A in
the messages return table to abort the processing. Messages of type E (error) do not
stop the processing but allow the errors to be verified on later DP processing steps.
In case of non-fatal errors happening during the data mapping, the processing will
continue. The error messages are stored for later review in the DP process.
Process type To be able to review the messages, enable the new DP process type 403. This process
403 type should be normally configured to be one of the first processes checked for
relevant DP document types. For process type determination, use the function
module /OPT/VIM_DETERMINE_PROC_IDHERR.
When using the process type 403, you must add the process option 2025 (Confirm
errors) to the options list for relevant roles. This new option allows to confirm the
errors in the document mapping and lets the DP processing continue to run. For
details about process type and process option configuration, see “Defining the
process type determination sequence” on page 145 and “Configuring DP process
options” on page 212.
When the DP workflow stops on the process type 403, you can use the Display
Errors button in the DP dashboard to review the errors happened during the data
mapping.
Note: The program will process only the invoices that are already in the DP
process.
736 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.1. Integrating Ariba SAP Business Suite Adapter
Payload ID
Enter the payload ID of the original invoice cXML message
Document ID
Enter the DP document ID
Registration ID
Enter the IDH document ID / Business Center registration ID
Reversal Reason
Enter the default reversal reason to use when cancelling SAP documents.
If you do not provide a value, the program uses the reversal reason 01
(Reversal in current period). If 01 is not maintained in the SAP ERP
system, it will try to use reversal reason 03 (Actual reversal in current
period).
The cancellation program tries to cancel documents and stop workflows regardless
whether other steps succeed. If any step fails while other steps succeed (for example
document is obsolete but workflow could not be stopped by some reason), the failed
steps will be retried on the next program run.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 737
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
2. Decide which condition types will be used for shipping and handling.
Configure this accordingly for qualifiers FREIGHT and HANDLING in the
customizing for additional cost mapping.
The customizing area for this configuration is: Vendor Invoice Management >
Document Processing Configuration > General Configuration > Incoming
Document Processing > Maintain Handling of Additional Costs > Planned
Costs - Mapping of Qualifiers to Condition Types
For more information, see “Maintaining additional cost handling” on page 257.
26.1.1.9 Alternatively mapping tax codes and tax jurisdiction codes for
PO invoices
The initial release of the Ariba Network integration component provided tax code
mapping that uses standard SAP Ariba mapping of tax categories to tax codes. As an
alternative, you can use VIM’s own tax code determination using the tax rate sent
from Ariba Network.
To complement these mappings, VIM now provides an alternative mapping with the
mapping function module /OPT/VIM_ARB_MWSKZ_PO. This function module delivers
the tax code from the corresponding purchase order item. This mapping change
needs to be performed manually, it is not delivered in a BC set.
In addition, VIM provides a new mapping for tax jurisdiction codes, with the
function module /OPT/VIM_ARB_TXJCD. This function module delivers the tax
jurisdiction code from the corresponding purchase order item. You also need to add
the respective mapping in the VIM fields mapping for Ariba. You can activate these
mapping changes with a BC set or perform them manually.
Note: The Ariba mapping for tax jurisdiction codes uses the CXML source field
tax description. If you need to map the real value of tax description for your
purposes, use another field for tax jurisdiction code.
738 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.1. Integrating Ariba SAP Business Suite Adapter
1. Run the SPRO transaction and navigate to Integration with Other mySAP.com
Components > SAP Business Suite Integration Component for Ariba >
Application Specific Settings > SAP ERP Integration Component for Ariba >
Business Add-Ins (BAdIs) > BAdI: Outbound Mapping.
2. In the BAdI Implementations dialog box, make sure that the BAdI
implementation /OPT/EH_E_ARB_BADI_OUTB_MAP is activated.
3. To maintain the outbound processing for the corresponding network, run the /
OPT/SPRO transaction and navigate to Document Processing Configuration >
General Configuration > Incoming Document Processing > Maintain
Processing for Supplier Network.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 739
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
4. In the Define Supplier Networks screen, make sure that the outbound
processing default class /OPT/CL_E_ARB_OUTBOUND is configured correctly for
network AN.
Notes
740 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.2. Integrating the Ariba SAP NetWeaver Process Integration adapter
For the PI adapter, VIM provides an integration white paper which describes the
different integration options. The white paper is available for integration partners on
My Support: https://knowledge.opentext.com/knowledge/cs.dll/Overview/38761889.
Processing
Invoice in process
Reconciled
Invoice posted successfully
Paid
Invoice partially/fully paid
Canceled
Invoice canceled
Rejected
Invoice not posted from IDoc
The standard function of the Ariba Network Adapter only tracks the status of
invoices after posting. With the integration of VIM, tracking must also cover
documents that have not yet been posted but are processed inside DP or a parking
workflow. Therefore, VIM delivers functionality to add VIM specific status
information to the status retrieval of the Ariba Network or Ariba CI Adapter. This
includes a configuration to map the process status of a VIM invoice to the status
codes that are known in the Ariba Network. It also includes a program include to be
called in a customer exit of the Ariba Network Adapter. For Ariba CI Adapter,
OpenText provides a BAdI implementation that is called by the status update
program to add VIM based status information.
Note: Currently only versions 12s2 and 11s2 of the Ariba Network Adapter are
supported. For integration based on Ariba CI adapter, version CI-8 and later is
supported.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 741
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
2. In the Define Supplier Networks screen, maintain an entry for the Ariba
Network, using the following parameters:
Netw
Enter a two-digit identifier for the external supplier network.
Default value: AN
Supplier Network
Enter the name of the external supplier network.
Default value: Ariba Network
Class Name
Enter the name of the class containing the processing logic for the external
supplier network.
Default value: /OPT/CL_E_SUPPLIER_NETW_ARIBA
Notes
742 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.2. Integrating the Ariba SAP NetWeaver Process Integration adapter
3. To define the status known in the Ariba Network, select the entry for the Ariba
Network and double-click Define External Status in the Dialog Structure.
4. In the Define External Status screen, maintain entries for all status codes
known in the Ariba Network, using the following parameters:
ExtStatID
External Invoice Status
Enter a two-digit, artificial key for the status of the external supplier
network.
External Status
External Invoice Status as known by the Network
Enter the invoice status as known by the external supplier network.
Example: canceled
Note: Ensure that the status code in the field External Status is exactly
the status code that is delivered by the Ariba Network. Pay attention
to lower and upper case.
External Status Description Long
Enter a description for the invoice status of the external supplier network.
5. To map the process status of a VIM invoice to the status codes that are known in
the Ariba Network, double-click Assign External Status to VIM Document
Status in the Dialog Structure.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 743
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
can define default settings by using the empty value for the fields
Document Status, SAP Status and PrevStat (see the examples in this
section).
The most specific mapping is chosen first. If no exact match is found, the
next less specific mapping is taken and so on.
6. In the Assign External Status to VIM Document Status screen, maintain status
mappings for the Ariba Network, using the following parameters:
Document Status
Enter the VIM document status.
SAP Status
Enter the status of the SAP invoice (if already existing).
PrevStat
Previous External Invoice Status
Enter the artificial key for this previous external invoice status.
The Ariba Network determines an invoice status for posted invoices.
ExtStatID
External Invoice Status
Enter the artificial key for the new status that should be given to the Ariba
Network.
The Ariba Network has sent an invoice to the SAP ERP system. The invoice
was posted with a payment block and is now waiting for approval in the
VIM process (Posted Approval). The Ariba Network Adapter determines the
external status processing (PR) for this invoice. What mapping record will
be taken?
744 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.2. Integrating the Ariba SAP NetWeaver Process Integration adapter
For a posted, paid invoice, the Ariba Network Adapter determines the status
paid. As VIM does not deliver any additional value regarding the status
information, the status should be kept as it is.
Document Status
<empty> (all VIM document statuses)
SAP Status
<empty> (all SAP document statuses)
PrevStat (Previous External Invoice Status)
PD (paid)
The VIM invoice has the status Obsolete. An SAP invoice was not created.
The VIM invoice should be treated as a rejected invoice, that is an invoice
that was not “accepted” by the buyer or the buyer's system.
Document Status
08 (Obsolete)
SAP Status
<empty> (all SAP document statuses)
PrevStat (Previous External Invoice Status)
<empty> (Because the invoice is not yet posted, the Ariba Network
Adapter will not provide a status.)
ExtStatID (External Invoice Status)
RJ (rejected)
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 745
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
VIM knows a big variety of different document statuses. Invoices with status
Obsolete or Confirmed Duplicate should get the Ariba status rejected.
All others should get the Ariba status processing. It is possible to maintain
a default mapping for invoices:
Document Status
<empty> (all VIM document statuses)
SAP Status
<empty> (all SAP document statuses)
PrevStat (Previous External Invoice Status)
<empty> (all Ariba network statuses)
ExtStatID (External Invoice Status)
PR (processing)
Note: Currently only the Ariba Network Adapter with Version 11s2 or 12s2 is
supported.
(for Ariba Network Adapter Version 11s2 on SAP NetWeaver 7.0 and higher)
746 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.2. Integrating the Ariba SAP NetWeaver Process Integration adapter
5. Navigate to the enhancement option at the end of the function module, that is
the enhancement option directly before the ENDFUNCTION instruction.
INCLUDE /OPT/EI_ARIBA_INV_STATUS_11S2.
SORT invoice_status_info BY doc_date doc_time.
INCLUDE /OPT/EI_ARIBA_INV_STATUS_12S2.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 747
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
Because of dependencies on the Ariba CI-8 adapter, OpenText delivers the necessary
ABAP workbench objects as a separate set of transport files. You find the transport
files on My Support: https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
64801445
1. EW3K901050
2. EW3K901080
3. EW3K901083
The delivery of the transports is provided with VIM 7.5 SP5. This scenario is
supported by VIM 7.0 SP3 and VIM 7.5 SP1 and later VIM versions. You can use the
provided transports with the mentioned older VIM versions and SPs.
This BAdI implementation uses the same IDoc mapping configuration as used for
the Network Adapter (11s2 and 12s2). The key difference is the class used in the
configuration:
748 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.3. Integrating Ariba Network using Cloud Integration Gateway
The minimum VIM release and SP levels are VIM 7.5 SP5 with Business Center
16.0.1, and VIM 16.3 with Business Center 16.3.
Note: Support of freight and handling costs with delivered mapping requires a
minimum of VIM 7.5 SP8 or VIM 16.3.2 with Business Center 16.3.2. You can
still implement this on older versions by using a custom mapping function.
• Inbound Invoice. This includes standard invoice, credit memo and non-PO
invoices.
• Both SAP ERP and SAP S/4HANA are supported. SAP Ariba CIG component
ARBCI1 is required. For details on specific SAP Basis, SAP_APPL or S4CORE
versions, see OpenText Vendor Invoice Management for SAP Solutions - Installation
Guide (VIM070500-08-IGD), OpenText Business Center for SAP Solutions -
Installation Guide (BOCP160302-IGD), and the respective Release Notes.
Comments and attachments are currently not supported. For more information on
current limitations, see “Known issues” on page 752.
Note: SAP provides reports integrated into the SPRO transaction, which create
necessary entries in SAP IDoc configuration tables. To connect CIG and VIM,
change the IDoc configuration created by the reports. If the configuration
reports are run again by some reason, you must redo the necessary
configuration for VIM.
The following sections assume that the standard integration is configured to work
without VIM, and they describe the additional steps to perform.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 749
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
2. In the WE42 transaction, enter the Business Center Inbound handler function
module /OTX/PF01_UTIL_IDOC_INPUT for the process code.
3. In the WE57 transaction, enable the processing of the CIG IDoc type
ARBCIG_INVOIC by the Business Center Inbound handler function module.
To support CIG integration, a new IDoc mapping is needed. The IDoc mappings are
maintained in the Business Center customizing.
OpenText provides a new IDoc mapping for CIG, delivered with a transport. If you
were following the CIG configuration guide provided by SAP, you likely have
created a new IDoc partner with the name that corresponds to your SAP system
logical system name.
Note: If using your logical system name as the IDoc partner name, you will
normally have to create production and test system mapping entries already in
your development or customizing system and then transport your settings.
The new standard mapping provided by OpenText does not refer to any specific
partner and therefore it needs to be copied to reflect your specific settings.
3. Copy the entries that provide your correct target IDoc partner:
750 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
26.3. Integrating Ariba Network using Cloud Integration Gateway
4. If needed, adjust the existing entries or create new ones for other fields.
Note: You can enter the 4-character qualifier values for freight and handling
only if you use Business Center 16.3.2 or a later support package.
For further details about configuration and running of the Business Center inbound,
refer to section 4 “Inbound Configuration” in OpenText Business Center for SAP
Solutions - Configuration Guide (BOCP160302-CGD).
The status updates are not sent for incoming invoices that are still being processed in
Business Center inbound. This means, from the time of the IDoc creation until the
start of the DP workflow. Typically, it is a short time period defined by the
frequency of the background job that runs Business Center inbound handler, unless
the Business Center inbound processing stops with an error by some reason.
The status updates are sent by the standard program provided with the CIG
package: ARBCIG_INVOICESTATUS_EXPORT. OpenText provides an implementation
of a BAdI called by that program to add VIM DP documents into the output. Make
sure that the BAdI implementation /OPT/VIM_ARB_CIG_ISU is active in CIG
customizing. Normally it is active after you install the VIM CIG integration
component.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 751
VIM070500-08-CGD-EN-01
Chapter 26 Integration with the Ariba Network
Normally, you do not need to adjust the VIM to Ariba status mapping (contents
of other customizing nodes in the screenshot). If you need to do the changes in
the status mapping, see “Integrating the Ariba SAP NetWeaver Process
Integration adapter” on page 740 for more details.
Non PO invoices
For Non PO invoices, the company code cannot be mapped correctly. You can
implement your own company code mapping as extension if you can define a
project specific mapping. For example, if each vendor supplies to exactly one
company code.
PO credit memos
Currently, the PO number is not being mapped into IDoc.
752 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 27
Reporting, analysis and interpretation of business data are crucial to preserve and
enhance the competitive edge of companies. They optimize processes and enable
companies to react quickly and in line with market needs. SAP NetWeaver Business
Warehouse (SAP NetWeaver BW) provides tools and functions that enable
companies to attain these goals. In SAP NetWeaver BW, you can integrate,
transform, and consolidate relevant business information from productive SAP
applications and external data sources. SAP NetWeaver BW provides you with a
high-performance infrastructure that helps you evaluate and interpret data. Decision
makers can make well-founded decisions and identify target-orientated activities on
the basis of the analyzed data.
With VIM 7.0 BW content, OpenText delivers preconfigured reporting and analysis
scenarios for SAP NetWeaver BW that are based on consistent metadata.
The VIM BW content provides the relevant BW objects from extraction to analysis, in
an understandable, consistent model. The VIM BW content therefore provides you
with an efficient and cost-effective way to implement SAP NetWeaver BW for VIM
in your company.
The VIM 7.0 BW content focuses on VIM related process data. The key figures that
are available in the KPI Dashboard are either directly available or can be calculated
in the VIM 7.0 BW content also. This comprises the following key figures:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 753
VIM070500-08-CGD-EN-01
Chapter 27 SAP NetWeaver Business Warehouse content
With VIM 7.0, BW content is delivered for SAP NetWeaver BW 7.0, SAP NetWeaver
BW 7.3, and OLTP systems with ECC 6.0. Technically, the VIM BW content
comprises DataSources together with the following components:
• Extractors
• InfoObjects
• DataStore Objects (DSO)
• InfoCubes
• MultiProviders
• BEx Query Variables
• Transformations
• InfoPackages
• DataTransfer Processes (DTP)
• Process Chains
• InfoObjects
• DataSources
• DataStore Objects (DSOs)
• MultiProviders
The main topic of the LSA is a model with different layers. The model describes the
way of data from the data source to the final data target. You see the data flow in a
tiered way where the data is passing several layers, in which it is transformed,
harmonized, validated and corrected.
The VIM BW content is structured according to the LSA. That means, separate
folders (so called InfoAreas) have been created for VIM to logically group the BW
objects for all layers with physical data storage.
754 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
27.1. OpenText VIM Layered Scalable Architecture (LSA)
Corporate Memory
The purpose of the Corporate Memory is to save raw data permanently for
history reasons to help recovery if needed.
The VIM 7.0 BW content provides a Write Optimized DataStore Object (DSO) for
every DataSource (master data and transaction data).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 755
VIM070500-08-CGD-EN-01
Chapter 27 SAP NetWeaver Business Warehouse content
The VIM 7.0 BW content provides both a meta process chain that supplies data
to DSOs of the Corporate Memory and a meta process chain that does not
supply data to the Corporate Memory.
• from the Data Acquisition Layer to the Data Propagation Layer and to the
Corporate Memory
756 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
27.1. OpenText VIM Layered Scalable Architecture (LSA)
Reporting Layer
Data in this layer is provided to serve the requirements of the reports best.
The VIM 7.0 BW content provides standard InfoCubes.
Virtualization Layer
The Virtualization Layer is part of the Reporting Layer. The Virtualization Layer
makes it possible to exchange the physical data models (for example the
InfoCubes) on which the reports are based.
The VIM 7.0 BW content provides MultiProviders based on InfoCubes and on
DataStoreObjects. For more information, see part V “SAP NetWeaver Business
Warehouse details” in OpenText Vendor Invoice Management for SAP Solutions -
Reference Guide (VIM070500-08-RGD).
Figure 27-3 provides an example for the BW objects and their transformations for
master data with the help of the master data amount class.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 757
VIM070500-08-CGD-EN-01
Chapter 27 SAP NetWeaver Business Warehouse content
1. OLTP system(s): Ensure that the following IMG activities of Central Reporting
are maintained properly:
a. On each OLTP VIM system (central and satellite), the VIM exception IDs
have been customized in the OpenText Configuration (/OPT/SPRO): Vendor
Invoice Management > Cross Component Configuration > Central
Reporting > Report Table Maintenance > Exception Definition and
Mapping > Exception Definition Maintenance and Exception Mapping
Maintenance. See “Activating Central Reporting Baseline and maintaining
reporting tables” on page 811.
b. Create company code groups. See “Creating company code groups”
on page 780.
758 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
27.2. Installing VIM BW content
Note: Time groups and time group ranges can be loaded from a
single OLTP system only. If there are multiple OLTP systems
connected to the SAP NetWeaver BW system, ensure that there is a
leading OLTP system that provides a complete list of all time groups
and time group ranges. This leading OLTP system may correspond to
the central system but this is not mandatory.
e. Check vendor groups and map them to vendors. See “Vendor groups”
on page 783.
Note: Vendor groups can be loaded from a single OLTP system only.
If there are multiple OLTP systems connected to the SAP NetWeaver
BW system, ensure that there is a leading OLTP system that provides
a complete list of all possible vendor groups. This leading OLTP
system may correspond to the central system but this is not
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 759
VIM070500-08-CGD-EN-01
Chapter 27 SAP NetWeaver Business Warehouse content
Note: Amount classes and amount class ranges can be loaded from a
single OLTP system only. If there are multiple OLTP systems
connected to the SAP NetWeaver BW system, ensure that there is a
leading OLTP system that provides a complete list of all possible
amount classes and amount class ranges. This leading OLTP system
may correspond to the central system but this is not mandatory.
g. Check exception classes and map all existing exception IDs to them. See
“Exception classes” on page 786.
Note: The texts of DP document types and the texts of channels can be
loaded from every OLTP system that is connected to the SAP NetWeaver
BW system.
2. SAP NetWeaver BW system: Ensure that the OLTP source systems have been
assigned to source system IDs in the Data Warehousing Workbench. If this is
not yet the case, maintain source system IDS for the OLTP systems:
760 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
27.2. Installing VIM BW content
Click Replicate Metadata in the context menu of the above VIM application
components in the DataSource tree of the Data Warehousing Workbench.
f. Click Replicate Metadata in the context menu of the VIM DataSources in
the DataSource tree of the Data Warehousing Workbench. Replicate
metadata only for those VIM DataSources that are needed for your
purposes.
Important
OpenText strongly recommends to launch the replication of
DataSources from the lowest level of application components (for
example from the application component /OPT/VIM_MD for VIM
Master Data). Otherwise the replication and activation of DataSources
may take a lot of time.
Notes
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 761
VIM070500-08-CGD-EN-01
Chapter 27 SAP NetWeaver Business Warehouse content
– Exception (/OPT/VIM_EXC_TRAN)
• If you are asked in which format the DataSources should be created
in the BW system, ensure that the DataSources are created as RSDS
DataSources.
Note: The given steps for replicating the metadata describe one possible
way only. Other ways are possible and valid.
For alternative ways and further details about the replication of metadata,
see the SAP documentation regarding the replication of DataSources in
SAP NetWeaver 7.x.
a. Gather the objects for the In Data Flow Before grouping and activate these
objects.
b. Then gather the objects for the In Data Flow Afterwards grouping and
activate these objects.
c. Using the buttons in the right screen area, make the following settings for
gathering dependent objects:
Button Value
Collection Start Manual Collection
Mode
Grouping In Data Flow Before
d. To select the VIM 7.0 Content objects that you want to activate, choose
InfoObjects by InfoAreas or InfoProviders by InfoAreas and then the
OpenText Vendor Invoice Management InfoArea.
e. Select the InfoObjects or InfoProviders that you want to activate from the
VIM scenarios and drag them to the right screen area.
f. Click with the quick info text Gather Dependent Objects. The first
group of objects is listed in the right screen area.
3. Start activation.
In the Active Version Available column, the icon is displayed for any objects
that are already activated and that you do not need to activate again.
762 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
27.2. Installing VIM BW content
a. In the Install column, select all objects that you want to activate. Any
objects for which the active and delivered versions differ can be identified
by the selection mark in the Match (X) or Copy column.
b. In the Match (X) or Copy column, select the objects that you want to
compare.
c. Click Apply > Install.
The Activation begins. As soon as the activation is complete, the data is
loaded automatically.
d. Repeat this procedure from Step 2 on page 762 (Gather Objects for
Activation in Data Flow) using the In Data Flow Afterwards grouping.
1. Select InfoObjects.
The characteristics and key figures of the VIM 7.0 BW content are organized in
InfoObject catalogs assigned to InfoAreas representing the different layers of
the LSA.
Select the InfoObject catalogs of the different LSA layers (Corporate Memory,
Data Propagation Layer, Reporting Layer) with the In Data Flow Before
option.
2. Install DataSources and data flow from source systems to Data Acquisition
Layer:
a. Select the leading OLTP source system and install the DataSources that are
needed for your purposes first with the In Data Flow Before option and
then with the In Data Flow After option. The object name of all VIM
DataSources starts with /OPT/.
First select with the In Data Flow Before option and then with the In Data
Flow After option.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 763
VIM070500-08-CGD-EN-01
Chapter 27 SAP NetWeaver Business Warehouse content
Note: The InfoProviders and the data flow between the InfoProviders are
installed with this step as well.
4. Select the Meta Process Chains that are needed for your purposes with the In
Data Flow Before option. The object names of all the VIM process chains start
with /OPT/. You can use a filter on the object name to search for the VIM
process chains. The VIM BW content provides the following meta process
chains to be used directly or as a template to be adapted to customer needs:
Meta Process Chain for Delta Load of VIM Data w/o Corp. Mem. (technical
name: /OPT/VIM_ALL_01)
This meta process chain is used to upload master data and transaction data
from the leading OLTP system without storing data records in the
Corporate Memory and to further upload the data to the Reporting Layer,
that means to the InfoCubes.
Meta Process Chain for Delta Load of VIM Data with Corp. Mem. (technical
name: /OPT/VIM_ALL_02)
This meta process chain is used to upload master data and transaction data
from the leading OLTP system with additionally storing the data records in
the Corporate Memory and to further upload the data to the Reporting
Layer, that means to the InfoCubes.
Note: Both meta process chains are designed for a single OLTP system
only. If there are multiple OLTP systems connected to the SAP NetWeaver
BW system, the process chains need to be adapted for the non-leading
OLTP systems. In case of a non-leading OLTP system, the process chain
should restrict the master data to be loaded to the following:
764 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
27.2. Installing VIM BW content
3. SAP NetWeaver BW system: Schedule a meta process chain to upload VIM data
to the BW periodically.
5. SAP NetWeaver BW system: The VIM BW content reuses InfoObjects of the SAP
standard content, for example:
Ensure that all BW objects needed for the dataflow from the DataSources to
these InfoObjects are installed from the SAP NetWeaver BW content.
Additionally, ensure that the data for these InfoObjects is loaded. This includes
loading the data for the attributes of the above InfoObjects, for example the
country of a vendor.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 765
VIM070500-08-CGD-EN-01
Chapter 28
KPI Dashboard
The “Key Performance Indicator” Dashboard (KPI Dashboard) is a tool for managers
showing VIM related process data at a glance in graphical charts.
KPI KPIs are used for performance management. Organizations use KPIs to measure
their overall success or the success of a particular activity. For the KPI Dashboard,
the following KPIs have been implemented with several filters:
For information about the user interface of the KPI Dashboard, see “Viewing data in
graphical charts” in OpenText Vendor Invoice Management for SAP Solutions - User
Guide (VIM070500-08-UGD).
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 767
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
768 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.2. Periodic jobs - collection and aggregation
Note: Before running periodic jobs, you must complete all customizing steps
for the KPI Dashboard. See “Customizing settings” on page 778.
The KPI Dashboard architecture overview shows that different levels of data
preparation are necessary to provide correct KPI data.
Level 1a
The VIM logging continuously writes data to special Log Tables and Index Data
Tables in the Central System and the Satellite Systems (if involved). The
activation of the KPI Dashboard BC set starts the logging mechanism.
Level 1b
The KPI Data Collection assembles document and exception data from the
logging and saves them in the KPI Source Tables. A periodic collection job is
required on each involved system to fill the KPI Source Tables.
Level 2
The KPI Aggregation selects data from the KPI Source Tables (in different logical
systems if required), aggregates the data, transforms it and saves the data in the
KPI Target Tables. A periodic aggregation job is required only in the Central
System (or Single System) to fill the KPI Target Tables.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 769
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
Level 3
The Web Dynpro uses the KPI Target Tables for visualization in the Web
Frontend.
KPI Source Tables and KPI Target Tables can always be refilled from the logging
tables.
Manual run
Run frequency
Ad hoc / on demand
Business background
Ad hoc reporting / short term KPI analysis for a certain period of time
Execution
Manually in dialog or background
Parameter settings
770 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.2. Periodic jobs - collection and aggregation
If you want to load just a special period of time for the KPI Dashboard, you can use
the KPI collection report on demand manually. All processes which have been
started and also finished within the chosen process start interval are included in the
resulting collection output and stored to the KPI source data tables. From there, the
KPI aggregation report picks up the data and writes it to the KPI target data tables
as data basis for the Web Frontend.
To run the KPI collection report in test mode, select Test mode. This setting will
display the collected data in an ALV grid before saving the result to the database.
Important
When using this ad hoc type of KPI data supply, you must completely clear the
KPI source and target data tables before. Otherwise, reloading just a special
period of time could probably result in inconsistent overall results and
interrupt the regular delta collection runs in a significant way.
Therefore, the following steps are required to fulfill short term ad hoc KPI
reporting requirements whenever needed:
3. Collect KPI source data for the required special time period using the KPI
collection report /OPT/VR_KPI_COLLECTION
4. Aggregate the collected KPI source data and write it to the KPI target data
tables using the report /OPT/VR_A_AGGREGATION using aggregation group
KPI.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 771
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
The “Start From” date is the timestamp of the last run. The “Start To” date is
the current timestamp.
Test mode
Same processing, but the data is not written to the database, but shown in an
ALV Grid.
Configure the collection program as a job with a variant for the processing option
Delta mode.
When running the KPI collection in the regular delta mode, the report picks up all
processes which have been started and also finished after the last delta run. The
report stores the result to the KPI source data tables. From there, the KPI
aggregation report picks up the data that has been collected after the last
aggregation run and writes it to the KPI target data tables as data basis for the Web
Frontend.
The following steps are required to fulfill ongoing KPI reporting requirements:
772 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.2. Periodic jobs - collection and aggregation
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 773
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
774 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.2. Periodic jobs - collection and aggregation
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 775
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
Note: For best performance, OpenText recommends that you select only
the Init source table check box for all KPI entries.
The check boxes may not be combined!
Maintain KPI Settings
Make the KPI related sub function modules available in Maintain KPI Settings.
Run the /n/OPT/SPRO transaction and navigate to Vendor Invoice Management
> Cross Component Configuration > Central Reporting >KPI Dashboard >
Maintain KPI Settings.
776 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.3. Authorizations
28.3 Authorizations
The access to the KPI Dashboard is limited to users that have a SAP user on the
central SAP ERP system.
The OpenText standard delivery restricts the user to see only the company code data
that he is authorized to access. The filter Company Code Group displays only
groups that contain at least one authorized company code. So, the ALL filter in
Company Code Group contains only the company code groups that the user is
authorized to access.
You can abolish this restriction and change the setting to: All users can see all
company code data. Therefore, change the value for constant DO_NOT_CHECK_BUKRS
to X. For details, see “Company code authority check” on page 793.
Important
If the company code check for authorization is running, and different users
have different company code authorizations, they will see different KPI
Dashboard filters and data.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 777
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
778 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
Grouping A lot of customizing has to do with the grouping of data. The KPI Dashboard is not
the right tool to display a large range of values; for example, to show 20 different
company codes. The KPI Dashboard rather shows grouped data like company code
groups or vendor groups.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 779
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
Important
You must define at least one company code group. Otherwise, the Web
Frontend of the KPI Dashboard cannot be viewed.
2. Create groups with a 4 character grouping ID and two descriptive fields (long,
short). Fill both description fields.
If you have between 1 and 20 different company codes that are relevant for the
KPI Dashboard, enter each company code as a company code group and fill the
description fields.
It is also possible to mix new company code groups with company code groups
that are identical with existing company codes.
The Flg: Disp. check box is for future use. It is not relevant now.
780 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
Important
If one company code is mapped to different company code groups, the
data displayed on the dashboard is not disjoint.
Important
Do not change the time groups.
In the OpenText Configuration (see “Customizing menu” on page 779), open Time
Group Definition.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 781
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
• On time
• Delayed
Note: The text symbols &1 and &2 in the Short Description will be replaced
during runtime with the Days from and Days to values.
782 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
Enter the maximum number of days for time group 1 and time type On time
(representing the invoices processed on time). In the example, all invoices with a
processing time less or equal 5 days are considered to be on time.
Enter the maximum number of days for time group 1 and time type Acceptable
(representing the invoices processed almost on time). In the example, all invoices
with a processing time more than 6 and less or equal 15 days are considered to be
almost on time.
Enter the minimum number of days for time group 1 and time type Delayed
(representing the invoices with delayed processing). In the example, all invoices
with a processing time more than or equal 16 days are considered to be delayed.
Enter the maximum number of days for time group 2 and time type On time
(representing the invoices approved on time). In the example, all invoices with an
approval time less or equal 2 days are considered to be on time.
Enter the maximum number of days for time group 2 and time type Acceptable
(representing the invoices approved almost on time). In the example, all invoices
with an approval time more than 2 and less or equal 4 days are considered to be
almost on time.
Enter the minimum number of days for time group 2 and time type Delayed
(representing the invoices with delayed approval). In the example, all invoices with
an approval time more than or equal 5 days are considered to be delayed.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 783
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
<Empty>
Use SAP standard LFM1 mapping (continue with next section)
X
Use KPI Dashboard specific mapping
If you want to use a KPI specific vendor grouping, set the constant value to X,
and fill the vendor mapping table, as shown in the following.
784 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
The text symbols &1 and &2 will be replaced during runtime with the From amount
and To amount values for the amount classes.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 785
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
The currency must be identical with the favorite currency in the KPI constants.
786 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
Note: If you change the texts, do not use special characters for the Short
Description.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 787
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
788 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
Check whether the following entries with Aggregation Group ID KPI and KPI
Group 1 are available:
• /OPT/KAGR_SUB_KPI1
• /OPT/KAGR_SUB_KPI2
• /OPT/KAGR_SUB_KPI3_TO_4
• /OPT/KAGR_SUB_KPI5_TO_6
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 789
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
T
Use the current system date.
P
Use the posting date of the document.
F
Use a fix date for the current year.
If you enter F, it is necessary to enter a value for the constant
CURR_CONVERSION_DAY.
790 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
The constant DASHBOARD_HELP_URL contains the link to the KPI Dashboard Help
page. Store the help file in the SAP mime repository and use the whole directory
structure in the URL link.
If the field is empty, the help link is not shown on the web page.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 791
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
<Empty>
The default help link stored in constant DASHBOARD_HELP_URL is used.
X
The help link URL is changed to language specific setting:
<default help link without file extension> + “_” + sy-langu + <file extension>
Example: /SAP/PUBLIC/BC/UR/DOC/Help_E.html
Keep in mind to store all the language specific help files to the same repository
with restriction of the above naming convention.
792 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
Example: http://op60vimd89.optura.local:8000/sap/bc/webdynpro/opt/
vim_kpi_main
This functionality applies for URLs that are up to 80 characters. For URLs with more
than 80 characters, you must maintain the constant value as FM:<CUSTOM FM>, where
FM: indicates that a function module is used, and <CUSTOM FM> indicates your
function module name. As a function module template, use /OPT/
DETERMINE_KPIURL_TEMPLATE.
If the application uses secure http (https) for communication, apply changes as
described in section 14.2 “Setting the connection for the SAP Web Dynpro service”
in OpenText Vendor Invoice Management for SAP Solutions - Installation Guide
(VIM070500-08-IGD).
<Empty>
Check for company code authorization.
X
Do not check for company code authorization. Show all data for all users.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 793
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
Enter the currency in which the amount of all invoices should be displayed. This is a
central constant also used during aggregation.
Important
It is absolutely necessary to enter the value with the YYYYMM notation.
Example: If the year is 2011, and the month is October; enter 201110
794 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
<Empty>
The standard SAP vendor grouping of table LFM1 is used.
X
You have to fill the KPI specific customizing vendor mapping. See “Mapping
vendor groups” on page 784.
SAP-CLIENT
Enter the client number of the SAP ERP system where the KPI Dashboard has
been installed and activated.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 795
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
SAP-EP-THEMEROOT
Enter the path from where the theme of the Web Dynpro application is taken (to
use MIME objects, such as pictures and style sheets for visualization). You can
change the parameter for using custom CI-style guides. Default value: OpenText
SAP-LANGUAGE
Only EN, DE, and FR are allowed at the moment.
SAP-SYSTEM-LOGIN-BASIC_AUTH
If you have sap-system-login-basic_auth=X in the URL, a session cookie is
created. That is the reason why you can still load the application without re-
authentication. If you have the IE Developer Toolbar, you can clear session
cookies and try again. It will ask for credentials then.
SHOW_BANNER
Enter Y to show banner images (default setting). To deactivate banners, set the
value to N.
796 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.4. Customizing settings
Time Range TO
Current month/year
Company Code Group
All
Channel
All
With the user parameter /OPT/VIM_KPI_MONTHS, you can set the KPI Dashboard
Time Range filter From. The value entered represents the number of months that
the KPI Dashboard goes into the past to collect data. The value must be a number
between 1 and 12. Other values are not allowed.
For users without this user parameter, the default value of 8 months is used.
Note: The KPI constant FILTER_START_PERIOD can be set to date that is higher
than the time range calculated as current month/year minus user specific
number of months. In this case, the value FILTER_START_PERIOD is used for
the initial display.
Example: FILTER_START_PERIOD is 201106 and the calculated Time Range FROM value
would be 201103. In this case, the initial display uses 201106.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 797
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
Make sure that all relevant VIM import channels that you want to see in the KPI
Dashboard are included in the table.
Important
The Web Dynpro application of the KPI Dashboard can display a maximum of
10 channels.
28.5 Troubleshooting
28.5.1 Problems with Excel download
Users might have problems downloading the KPI data from the Dashboard to Excel.
In this case, change the browser’s internet security settings in the Downloads sub
tree as shown in the following screenshot:
798 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
28.5. Troubleshooting
In this case, check the settings of the RFC destination IGS_RFC_DEST (TCP/IP
connection) on the backend system. Set the Program ID to IGS.<SID>; where SID is
the System ID of the SAP ERP system.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 799
VIM070500-08-CGD-EN-01
Chapter 28 KPI Dashboard
If the connection is successful, users should be able to access the KPI Dashboard
using the Web Dynpro page.
800 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 29
Automation report
29.1 Overview
The automation report is a tool that provides data about automated and manual
processing steps of VIM documents. For more information, see section 6 “Using the
Automation Report” in OpenText Vendor Invoice Management for SAP Solutions -
Reference Guide (VIM070500-08-RGD).
Important
Data for the automation report is based on change documents for object class /
OPT/VIM_IDXDAT, which is a completely new feature with VIM 7.0 SP2.
Therefore, it is not possible to show automation data for documents that have
been processed in older VIM versions.
The VIM program “automation report” allows you to view and export the table
contents.
Run frequency
OpenText recommends that you run this report daily, in delta mode, in the
background.
Processing options
Delta mode
To run the ATM collection report in delta mode, select this check box.
This is the default setting.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 801
VIM070500-08-CGD-EN-01
Chapter 29 Automation report
To run the ATM collection report in full mode, clear the check box. You
need the full mode only if the data structures have been changed. This
may be the case when a new VIM SP is installed.
Note: Review the Release Notes of the SP to confirm if a full mode
run is necessary.
Test mode
To run the ATM collection report in test mode, select this check box.
This setting will display the collected data in an ALV grid before saving
the result to the database.
802 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 30
Central Reporting infrastructure
• Summary Report (see section 8 “Using the Summary Report” in OpenText Vendor
Invoice Management for SAP Solutions - Reference Guide (VIM070500-08-RGD))
• Central Audit Report (see section 9 “Using the Central Audit Report” in
OpenText Vendor Invoice Management for SAP Solutions - Reference Guide
(VIM070500-08-RGD))
• Key Process Analytics Report (see section 10 “Using the Key Process Analytics
Report” in OpenText Vendor Invoice Management for SAP Solutions - Reference Guide
(VIM070500-08-RGD))
• Exception Analysis Report (see section 11 “Using the Exception Analysis Report”
in OpenText Vendor Invoice Management for SAP Solutions - Reference Guide
(VIM070500-08-RGD))
• Productivity Report (see section 12 “Using the Productivity Report” in OpenText
Vendor Invoice Management for SAP Solutions - Reference Guide (VIM070500-08-
RGD))
• Aging Report (see section 13 “Using the Aging Report” in OpenText Vendor
Invoice Management for SAP Solutions - Reference Guide (VIM070500-08-RGD))
Aggregation To ensure good performance for the reports in Central Reporting, the data used for
the reports must be aggregated and saved in Reporting Data Tables. To achieve this
goal, the data is prepared in several different activities:
1. The Collection Report, the User Master Report and the Text Master Report get master
data and transaction data from their original tables and save the data in the
Source Data Tables. See “Scheduling the Collection Report” on page 815 for
details.
2. The Aggregation Report selects data from the Source Data Tables (in different
logical systems, if required), aggregates, transforms and saves the data in the
Reporting Data Tables of the current system. See “Scheduling the Aggregation
Report” on page 821.
3. The reports in Central Reporting are end user reports based on the content of the
Reporting Data Tables.
Configuration To configure Central Reporting, you have to perform the following steps:
steps
1. Maintaining logical systems and System Landscape Directory (SLD)
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 803
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
• Collection Report
• User Master Report
• Text Master Report
• Aggregation Report with variants for each aggregation group
Groups Data in Source Data Tables changes during the use of VIM. Therefore, the
aggregation of data to the Reporting Data Tables must run regularly. OpenText
strongly recommends scheduling batch jobs for this purpose. For different tables, the
necessary frequency to update will differ considerably. For example, the SAP
Vendors Table will change much less frequently than the Workitem Agents Table.
For this reason, several default groups, comprising specific tables, are set up for the
aggregation:
Groups beginning with OTH* are used by the Central Audit Report only. The other
groups are used by the other central reports.
CUST_PREFL
Comprises Roles and Exception Mapping. This group is used to prefill the
customizing tables for roles and exceptions (see “Activating Central Reporting
Baseline and maintaining reporting tables” on page 811) to ease customizing.
TRANSACT
Comprises Document Header, Workitem, Workitem Activities, and Workitem
Agents. This group will have to be executed most frequently because its content
is changed most frequently.
MASTER
Comprises Company Codes, Vendors, and Document Types.
USER
Comprises Users and the assignment of users to organizational objects within
SAP Organizational Management.
KPI
Builds up the KPIs which are offered by the KPI Dashboard.
Scheduling the Aggregation Report for the KPI group is only required if you
want to use the KPI Dashboard. See “KPI Dashboard“ on page 767.
Scheduling the Aggregation Report for the following groups is only necessary in a
multiple backend system.
804 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
OTH_MASTER
Recommended to run once. Depending on how frequently Parking Reasons,
Process Type Definitions and Blocking Reasons are maintained, schedule the job
accordingly.
OTH_DCHEAD
Recommended to run twice a day. The frequency can vary depending on
business needs. Group ID OTH_DCHEAD replicates the data from table /OPT/
VT_DOC_HEAD to the Central System. This table is useful for Central Audit Report
output.
OTH_VMHEAD
Recommended to run twice a day. The frequency can vary depending on
business needs. Group ID OTH_VMHEAD replicates the data from table /OPT/
VIM_1HEAD to the Central System. This data replication is useful for system wide
duplicate check for an incoming invoice.
OTH_AGENT
Recommended to run twice a day. The frequency can vary depending on
business needs. Group ID OTH_AGENT replicates the data from table /OPT/
VT_WI_AGENT to the Central System. This data replication is useful for current
agent display in the Central Audit Report.
Baseline To display the groups that are delivered with Baseline, run the /n/OPT/SPRO
groups transaction and navigate to Vendor Invoice Management > Cross Component
Configuration > Central Reporting > Aggregation Infrastructure > Aggregation
report groups.
Note: OpenText strongly recommends that you do not change the Baseline
groups.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 805
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
Target data To display the Baseline target data tables that will be filled by the Aggregation
tables Report, run the /n/OPT/SPRO transaction and navigate to Vendor Invoice
Management > Cross Component Configuration > Central Reporting >
Aggregation Infrastructure > Aggregation report target tables.
Target and source tables are displayed, depending on the Aggregation Group ID.
Note: OpenText strongly recommends that you do not change the Baseline
target data tables.
806 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.1. Configuring the System Landscape Directory (SLD)
For details, see section 4.4 “Working with the System Landscape Directory (SLD)” in
OpenText Vendor Invoice Management for SAP Solutions - Scenario Guide
(VIM070500-08-CCS).
1. Central system – All satellite systems are maintained with proper RFCs and
classifications. The own logical system for the Central system itself is configured
with classification Central and with RFC destination NONE for system
communication.
2. Satellite system – The Central System logical system name is maintained with
proper RFC and classification. The own logical system for the Satellite system
itself is configured with classification Satellite and with RFC destination NONE
for system communication.
Note: Collection Report, User Master Report, and Text Master Report always
run in all systems involved. The Aggregation Report runs only in the central
system.
Note: Collection Report, User Master Report, Text Master Report, and
Aggregation Report all run in the concerned system.
1. To display the Aggregation report: Back end systems screen, run the /OPT/
VIM_ABE transaction.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 807
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
Notes
Note: The wrapper function on the logical system returns the source table
content as an XML stream to the central system, because it is not possible
to hand over internal tables as generic types in RFC. If the fields Character
set and Byte order remain blank, the system default will be used. In case
of XML conversion problems during execution of the Aggregation Report,
you can specify the encoding to be used in these fields.
Character set
Enter the character set, for example UTF-8.
Byte order
Enter the byte order, for example 1 if the character set uses big endian byte
ordering.
Note: For character sets and byte orders supported by SAP, see the
SAP documentation.
If you are not sure about the correct settings for your system, try the following:
808 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.3. Running the Aggregation Report for the CUST_PREFL group
a. In the related back end system, call the SE37 transaction and execute
function module SYSTEM_CODEPAGE.
The codepage of the system is displayed.
b. Call the SE16 transaction and enter table name TCP00.
c. Use the codepage number returned by the previous function module call
(for example 4103) as selection value for field CPCODEPAGE.
In the selected dataset, the field CPCOMMENT contains most often a
description of the character set it contains (for example ISO-8859-1 or
UTF-16BE).
d. Try this character set first in back end system settings.
Important
If you don’t want to use the default mapping from OpenText supplied baseline
content, use the CUST_PREFL group and run the report. Running the
Aggregation Report for the CUST_PREFL group prefills the customizing for
roles and exceptions.
You must manually map roles and exceptions in Central Reporting; see “Activating
Central Reporting Baseline and maintaining reporting tables” on page 811.
Group ID
Enter the group ID, in this case CUST_PREFL.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 809
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
Asynchronous selection
Select this check box to have a new task opened for every call of the
selection function. If there are more than 35 Reporting Data Tables, this is
required to avoid overflow of buffer when creating generic subroutines
(used to define structures of internal tables dynamically).
1. Invoke the Aggregation Report screen, see “To run the Aggregation Report for
the CUST_PREFL group:“ on page 809.
2. Enter the Group ID and configure the report for this group, according to your
needs. See Step 3 on page 809.
4. In the ABAP: Save as Variant screen, enter Variant name and Description and
save.
810 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.5. Activating Central Reporting Baseline and maintaining reporting tables
Central VIM Baseline delivers exception mapping and role mapping as part of the BC set
Reporting activation. To access these mappings, run the /n/OPT/SPRO transaction and navigate
Baseline
to Vendor Invoice Management > Cross Component Configuration > Central
Reporting > Report Table Maintenance. The mappings have one key field Logical
System that remains empty as the logical system key is not supplied in the Baseline
implementation.
If you want to configure custom user roles, add your settings before activating
Central Reporting Baseline. Maintain the roles manually in the Role Mapping
Maintenance without providing the logical system name as the key.
If you want to configure exceptions of your own, add your settings before activating
Central Reporting Baseline. Maintain exceptions in the Exception Mapping
Maintenance without providing the logical system name as the key.
To associate the mappings with the logical systems in the landscape, activate Central
Reporting Baseline by running the /n/OPT/VIM_SYS_ACTIV transaction. It is a one
time activity on each system involved. Perform it as a part of post installation
activity. If you activate Central Reporting Baseline, it provides default mapping of
role IDs and exception IDs from Baseline.
Maintaining If the baseline mapping of roles and/or exceptions does not suit your needs or if you
reporting tables want to enhance the mapping, some maintenance is required, before you can use the
reports in Central Reporting.
• Role Maintenance: Define the roles to be used in the reports. See “To maintain
roles for Central Reporting:“ on page 812.
• Exception Definition Maintenance: Define the exceptions to be reported. See “To
maintain exceptions for Central Reporting:“ on page 812
• Role Mapping Maintenance: Map roles from all the logical systems that have
been maintained for usage in the Aggregation Report. See “To map roles from
several back end systems:“ on page 813.
• Exception Mapping Maintenance: Map exceptions from all the logical systems
that have been maintained for usage in the Aggregation Report. See “To map
exceptions for several back end systems:“ on page 814.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 811
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
812 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.5. Activating Central Reporting Baseline and maintaining reporting tables
Once you have run the Aggregation Report for the CUST_PREFL group, the
customizing tables for Role Mapping Maintenance and Exception Mapping
Maintenance are prefilled. To map roles/exceptions from several back end systems,
perform the following steps:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 813
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
The columns Product Code and Responsible Party have been prefilled
automatically.
2. Assign the Role ID (as defined in “To maintain roles for Central Reporting:“
on page 812) to each responsible party (role) for specific product code.
814 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.6. Scheduling the Collection Report
The columns Exc. Type and Exc.typeID (Exception Type ID) have been prefilled
automatically.
2. Assign the Exc. ID (as defined in “To maintain exceptions for Central Reporting:
“ on page 812) to each Exception Type ID for specific exception type.
Note: For a description of the KPI Collection Report that is needed for the KPI
Dashboard, see “Collection job” on page 770.
The Collection Report collects data from VIM transactional tables and SAP workflow
tables and populates the Source Data tables. The Source Data tables are later
aggregated by the Aggregation Report into Reporting Data tables.
Scheduling You can schedule the Collection Report by running the /OPT/
VR_COLLECTION_REPORT program with appropriate start date and time in all the
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 815
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
systems involved. OpenText recommends running this report twice a day. However,
depending on how frequently data is needed, you can schedule it accordingly.
Cut-off date The only mandatory selection criterion is Creation Date From. You must set this
date. It refers to the cut-off date, the work item creation date. Any invoices that have
been created before this date are not considered in reporting. The (Creation Date) to
field is relevant only for partial load, see “Partial load” on page 816. You can
combine the Creation Date From field with the Creation Time From field. If you
also provide Creation Time From, date and time together decide the cut-off time
period.
With a new installation, use the installation or go-live date for the Creation Date
From. With an upgrade, use the date of upgrading.
Do not maintain selection parameters other than Creation Date From and Creation
Time From (and to for partial load).
Note: However, you can use the parameters Task and ID for testing purposes.
The parameters refer to the workflow dialog task and the work item ID.
Delta and full Once scheduled, this report always runs in delta mode. Only those work items and
mode documents are considered that have changed since the last run. Delta mode is
default and fixed. To change to full mode, you must clean table /OPT/VT_JOB; see
“Troubleshooting: Cleaning up Central Reporting tables” on page 821.
Partial load VIM provides the “partial load” feature for the Collection Report. Without partial
load, the Collection Report only supported full and delta loads, therefore it was not
possible to collect process information only for a special period of time, which can be
816 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.6. Scheduling the Collection Report
done using partial load. Partial load also makes it possible to correct any data
inconsistencies that can occur if at least one Collection Report run has been
performed using wrong selection criteria in the past.
Single processes may still be shown as in process by the Central Reporting tools
but they have already been completed in the meantime. The reason for this could be
that the regular Collection Report delta load (usually scheduled as background job)
only considers work items that have been finished since the last collection run, and
the cut-off date has been set in a too restrictive way; see Example 30-1, “Collection
Report inconsistencies” on page 817.
The partial load feature allows to correct such inconsistencies at any time by
updating all corresponding work items of a certain period of time again.
To run the Collection Report in partial load mode, you use a new selection field
“Work Item Creation Date To” (to) in combination with Creation Date From. If you
provide a value in the to field, the Collection Report runs a “partial load” for the
specified creation date range.
Figure 30-1 on page 816 shows a partial load example for exactly one day.
Note: OpenText recommends that you only run the partial load manually if
really required. Do not schedule the partial load job regularly as a background
job.
Example work item: creation date 3rd of July, completed by posting on 4th of
July
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 817
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
Trying to download the missed work item at a later time will not help
anymore since the date of the last Collection Report run will be enhanced
every time during the regular scheduled job run.
In this example, the Creation Date From is set too restrictive because the
following parameters were ignored:
Assume that the longest work item processing time is 2 weeks and (to make
it simple for this example) a download is triggered only once a day (note that
the recommendation is twice a day or even more often). This means that all
work items that were created 15 days or less ago would have to be
downloaded again to ensure that the correct work item status is uploaded.
Creation Date From of the Collection Report: Current system date minus 2
weeks minus gap between the data loads. In our case this is: 4th of July
(current system date) - 14 days - 1 day (gap between the data loads) = 19th of
June
Collection Report run scheduled on 4th of July , with Creation Date From
set to 19th of June
The work item is finished in the meantime and is updated because the
creation date is 3rd July.
You can use the to date (partial load) to correct data inconsistencies that
happened in the past.
Assume that the current system date is 14th of October. Since 4th of October,
the upload is correctly done with a Creation Date From as the current
system date minus 15 days; for details, see Example 30-1, “Collection Report
inconsistencies” on page 817. Before 4th of October, the upload was done
with the current date as Creation Date From.
The work item created on 3rd of July still shows the wrong status.
818 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.7. Scheduling the User Master Report
Collection Report run on 14th of October , with Creation Date From set to
3rd of July , and to date set to 19th of September
All work items created in the given time frame are updated correctly
now.
Partial load may also be an option if the assumed longest work item
processing time was exceeded for a limited period of time in the past (more
than 15 days ago).
Table /OPT/ The last run time of the Collection Report is stored in table /OPT/VT_JOB. At the first
VT_JOB time the Collection Report runs, table /OPT/VT_JOB is empty. Thereafter, the last run
time always gets updated in this table.
Note: If you select Test Mode, the data is not saved to source tables or any
table. Even /OPT/VT_JOB will remain unchanged.
Schedule the User Master Report to run only after a previous run of the Collection
Report because the User Master Report uses the information from the tables filled in
by the Collection Report. So, if the Collection Report has never run, running the User
Master Report will not produce the desired results.
The User Master Report collects additional user information like first name, last
name, and OpenText user ID when new users appear in the system or any changes
happen to users. This information is used, for example, in the Central Audit Report:
You can click a link in the Current Role column to display details of the agents
associated with the role.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 819
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
820 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.9. Scheduling the Aggregation Report
The Aggregation Report depends on the results of the Collection Report. Therefore,
schedule the Collection Report, the User Master Report, and the Text Master Report
before the Aggregation Report.
Example: The User Master Report runs every Sunday at 20:00. The Aggregation Report with
group USER should be scheduled afterwards, for example every Sunday at 20:10. If the
Aggregation Report would be scheduled before the User Master Report, for example at 19:00,
it would result in user data that is almost one week old.
Single system In a single system scenario, the Central System is the same as the current system.
Schedule the Aggregation Report with all Group IDs, except the Group IDs that start
with OTH_*.
Multiple In a multiple backend system, schedule the Aggregation Report with all Group IDs,
backend including the Group IDs that start with OTH_*.
You might need to clean up the Central Reporting tables, for example to reload data
after fixing some issues. Whereas VIM Analytics bases on real time VIM tables,
Central Reports base on tables that are not real time. Collection Report, User Master
Report, and Text Master Report pull information from real time VIM tables and
provide data to Source Data Tables. The Aggregation Report selects data from the
Source Data Tables and provides data to the Reporting Data Tables. As Source Data
Tables and Reporting Data Tables are not real time, these tables can be reloaded.
• If you know that there is a special time frame with inconsistencies, you can use
the partial load mode of the report /OPT/VR_COLLECTION_REPORT to correct it.
See “Partial load” on page 816.
• If you cannot identify which inconsistencies occurred, you can use the cleanup
report /OPT/VR_CLEAN_TABLES (see “Cleanup report” on page 822) and reload
all reporting data afterwards again; see “To reload reporting data:“
on page 822.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 821
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
Cleanup report To run the cleanup report, run the SA38 transaction with program /OPT/
VR_CLEAN_TABLES.
Report Tables
Select this check box to delete Reporting Data Tables.
Important
This will clean up all data in the end user Central Reports.
Source Tables
Select this check box to delete Source Data Tables.
This will not impact the end user Central Reports, except the Central Audit
Report.
Note: If you reload the whole data, consider the corresponding data volume
that needs to be reloaded.
2. If the data volume is extremely high, use the partial load mode of the Collection
Report to reload the data in buckets. For example, always gather three months
of data, starting from the go-live-date until today.
If the data volume is small, run the Collection Report in the regular mode (with
go-live-date as start date). This results in a “full load” for the very first time. All
later runs are considered as “delta loads”.
3. After data is completely reloaded (either by some “partial loads” or just one
“full load”), schedule the Central Reporting reports as described in “Scheduling
the Collection Report” on page 815 and the subsequent sections.
822 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.11. Maintaining thresholds for the Key Process Analytics Report
You can define threshold values for an attention status and a critical status. If the
attention value is exceeded in a cell (or falls below it for the First Pass panel), the cell
is highlighted in orange. If the critical value is exceeded in a cell (or falls below it for
the First Pass panel), the cell is highlighted in red.
1. To enter the WebFlow Constant Table where you maintain the constants, run
the /n/OPT/VIM_KPA_CFG transaction.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 823
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>
where you must replace all <value> fields with a number, as follows:
• Value 1 and 2 define the lower and upper threshold for the total number of First
Pass PO Invoices.
• Value 3 and 4 define the lower and upper threshold for the total number of First
Pass NPO Invoices.
• Value 5 and 6 define the lower and upper threshold for the total number of all
First Pass Invoices.
If the total number of First Pass invoices is lower than value 1/3/5, the respective cell
is marked red.
If the total number of First Pass invoices is greater or equal than value 1/3/5 but
lower than value 2/4/6, the respective cell is marked orange.
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
824 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.11. Maintaining thresholds for the Key Process Analytics Report
If the total number of First Pass PO Invoices is lower than 10,000, the
respective cell will be marked red.
If the total number of First Pass PO Invoices is greater or equal than 10,000
but lower than 30,000, the respective cell will be marked orange.
If the total number of First Pass NPO Invoices is lower than 10,000, the
respective cell will be marked red.
If the total number of First Pass NPO Invoices is greater or equal than 10,000
but lower than 30,000, the respective cell will be marked orange.
If the total number of all First Pass Invoices is lower than 20,000, the
respective cell will be marked red.
If the total number of all First Pass Invoices is greater or equal than 20,000
but lower than 60,000, the respective cell will be marked orange.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 825
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
The total number of first pass invoices is checked against the thresholds for
the All Invoices line, only.
If the total number of all First Pass Invoices goes below 20,000, the respective
cell will be marked red.
If the total number of all First Pass Invoices is greater or equal than 20,000
but lower than 60,000, the respective cell will be marked orange.
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>
where you must replace all <value> fields with a percentage quotation, as follows:
• Value 1 and 2 define the lower and upper threshold for the percentage of First
Pass PO Invoices.
• Value 3 and 4 define the lower and upper threshold for the percentage of First
Pass NPO Invoices.
• Value 5 and 6 define the lower and upper threshold for the percentage of all First
Pass Invoices.
If the percentage of First Pass invoices is lower than value 1/3/5, the respective cell is
marked red.
If the percentage of First Pass invoices is greater or equal than value 1/3/5 but lower
than value 2/4/6, the respective cell is marked orange.
826 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.11. Maintaining thresholds for the Key Process Analytics Report
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
<Value1>;<Value2>;<Value3>
where you must replace all <value> fields with data, as follows:
If the amount of Blocked Documents is greater than the lower threshold but smaller
or equal than the upper threshold, the respective cell is marked orange.
If the amount of Blocked Documents exceeds the upper threshold, the respective cell
is marked red.
The currency value must be maintained if you want to use the threshold
functionality. If any of the other values is not maintained, the respective check is not
done and the cell will not be colored.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 827
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
If the amount of Blocked Documents is greater than 20,000 USD, the respective cell is marked
red. The cell will never be marked orange because the respective value is not maintained.
If the amount of Blocked Documents is greater than 10,000 USD but smaller
or equal than 20,000 USD, the respective cell is marked orange.
<Value1>;<Value2>;<Value3>
where you must replace all <value> fields with data, as follows:
If the amount of Parked Documents is greater than the lower threshold but smaller
or equal than the upper threshold, the respective cell is marked orange.
If the amount of Parked Documents exceeds the upper threshold, the respective cell
is marked red.
The currency value must be maintained if you want to use the threshold
functionality. If any of the other values is not maintained, the respective check is not
done and the cell will not be colored.
828 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.11. Maintaining thresholds for the Key Process Analytics Report
If the amount of Parked Documents is greater than 20,000 USD, the respective cell is marked
red. The cell will never be marked orange because the respective value is not maintained.
If the amount of Parked Documents is greater than 5,000 USD but smaller or
equal than 15,000 USD, the respective cell is marked orange.
If the amount of Parked Documents exceeds 15,000 USD, the respective cell
is marked red.
<Value1>;<Value2>;<Value3>
where you must replace all <value> fields with data, as follows:
If the amount of Pre-Process Documents is greater than the lower threshold but
smaller or equal than the upper threshold, the respective cell is marked orange.
If the amount of Pre-Process Documents exceeds the upper threshold, the respective
cell is marked red.
The currency value must be maintained if you want to use the threshold
functionality. If any of the other values is not maintained, the respective check is not
done and the cell will not be colored.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 829
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
If the amount of Pre-Process Documents is greater than 20,000 USD, the respective cell is
marked red. The cell will never be marked orange because the respective value is not
maintained.
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>;<Value7>;<Value
8>
where you must replace all <value> fields with a number, as follows:
• Value 1 and 2 define the lower and upper threshold for the total number of
processed PO Invoices.
• Value 3 and 4 define the lower and upper threshold for the total number of PO
Invoices in process.
• Value 5 and 6 define the lower and upper threshold for the total number of
processed NPO Invoices.
• Value 7 and 8 define the lower and upper threshold for the total number of NPO
Invoices in process.
If the number of invoices is greater than the lower threshold but smaller or equal
than the upper threshold, the respective cell is marked orange.
If the number of invoices is greater than the upper threshold, the respective cell is
marked red.
830 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.11. Maintaining thresholds for the Key Process Analytics Report
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
If the total number of NPO Invoices in Process is greater than 150,000 but
smaller or equal than 250,000, the respective cell is marked orange.
<Value1>;<Value2>;<Value3>;<Value4>;<Value5>;<Value6>;<Value7>;<Value
8>
where you must replace all <value> fields with a percentage quotation, as follows:
• Value 1 and 2 define the lower and upper threshold for the percentage of
Processed PO Invoices.
• Value 3 and 4 define the lower and upper threshold for the percentage of PO
Invoices in Process.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 831
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
• Value 5 and 6 define the lower and upper threshold for the percentage of
Processed NPO Invoices.
• Value 7 and 8 define the lower and upper threshold for the percentage of NPO
Invoices in Process.
If the percentage of invoices is greater than the lower threshold but smaller or equal
than the upper threshold, the respective cell is marked orange.
If the percentage of invoices is greater than the upper threshold, the respective cell is
marked red.
If any of the values is not maintained, the respective check is not done and the cell
will not be colored.
If the percentage of NPO Invoices in Process is greater than 50% but smaller
or equal than 80%, the respective cell is marked orange.
If the percentage of NPO Invoices in Process exceeds 80%, the respective cell
is marked red.
832 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.12. Configuring the Summary Report
Note: The Summary Report evaluates data from the offline reporting table /
opt/vt_doc_h.
You can configure the report to assign individual document statuses to different
categories and groups.
At the highest level, the summary report distinguishes between invoices and credit
memos. All group IDs created during configuration are applicable to both invoices
and credit memos.
Groups are the highest level unit in the Summary Report. They have one or
more Category IDs assigned to them. In the Report output, groups appear as
headings. Baseline configuration provides the following group IDs:
In process
Invoices that are in VIM processes
Pre Processed
Invoices that are in OCR processing
Processed
Invoices that are posted
Others
Invoices that have statuses, for example Obsolete, or Rescan completed
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 833
VIM070500-08-CGD-EN-01
Chapter 30 Central Reporting infrastructure
2. To configure the mapping of Category IDs and text, double-click Category id/
text Configuration in the Dialog Structure panel. Each category is assigned to a
group ID. Baseline configuration provides the following category IDs:
StatusCode
Enter the Status Code for the Category ID. You can assign multiple Status
Codes for each Category ID.
When the Summary Report is run, the program distinguishes the invoice
documents depending on the Status Code. Then, the program categorizes
and displays the Category (text) in the report, as a subsection of the Group.
If the Status Code of a Category is not found in the Summary Report, the
corresponding Category Text is not displayed in the report.
834 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
30.12. Configuring the Summary Report
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 835
VIM070500-08-CGD-EN-01
Chapter 31
SAP Shared Service Framework integration
As part of Business Suite 2010 (ERP 6.0 EhP5 and SAP CRM 7.0 EhP1), SAP delivers
SAP Shared Service Framework. SAP Shared Service Framework contains a rich set
of tools to improve and automate Shared Service Center operations.
SAP Shared Service Framework integrates the leading CRM system with the
backend ERP systems, for example VIM. Shared Service Center agents work entirely
in their AIC, with access to the backend ERP systems that they are responsible for.
The AIC provides the means to support communication with employees, suppliers
and customers.
VIM can be integrated with SAP Shared Service Framework. The VIM integration
provides the feature to display VIM Analytics (VAN) inside the CRM interaction:
In both cases, still the old VAN is displayed instead of the new VAN.
VIM leverages SAP Shared Service Framework and provides integration scenarios
with the AIC. See the following examples:
Example:
• The integration allows searching and finding invoices in VIM from AIC.
• VIM users in the ERP backend system can open service requests from VIM work items and
exceptions.
• Specific exceptions can be configured to automatically create a service request in CRM/
AIC.
Among others, the benefits of SAP Shared Service Framework integration are the
following:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 837
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
Note: You must perform the tasks either in the SAP ERP (VIM) system or in
the CRM system. The system is indicated in square brackets, for example
[ERP], in the title of each section.
• “Maintaining a logical system for the CRM system in VIM [ERP]” on page 838
• “Creating an ITS service in the backend ERP system [ERP]” on page 839
• “Defining transaction launcher logical systems and URL [CRM]” on page 847
• “Creating a transaction launcher for VIM work centers to call VIM Analytics
(Service Request) [CRM]” on page 850
• “Creating a transaction launcher for VIM work centers to call VIM Analytics
(account ID confirmation) [CRM]” on page 857
• “Configuring work centers for VIM Analytics [CRM]” on page 858
• “Configuring Business Context links for OpenText linked objects in Service
Request [CRM]” on page 863
• “Configuring the OpenText Vendor Factsheet BSP component [CRM]”
on page 869
• “Maintaining the logical system in OpenText configuration tables [CRM]”
on page 881
• “Defining prefill business role settings for RFC (Service Request display) [CRM]”
on page 882
838 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
The transaction launcher is a tool that you can use to allow agent access to business
transactions directly from the IC WebClient screen (in case of VIM, this is the AIC).
Essentially, the transaction launcher is a collection of shortcuts to available functions
or transactions within SAP CRM and ERP systems.
You can create own service names in the nodes in the SICF transaction. The Service
Name creation in this section is an example to create own services under the ITS
node.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 839
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
3. Expand default_host > sap > bc > gui > sap > its and right-click the ITS Service
name.
840 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
Note: If you get a popup with information about the SAP namespace,
confirm it by clicking .
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 841
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
842 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 843
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
Note: You can create own service names in the nodes in the SICF
transaction. However, for GUI Configuration in the Service Data tab, you
must set the following Parameter Name and Value. The ERP transaction
that OpenText SSF Transaction Launcher ITS Services depend on is /OPT/
VIM_SSF_LAUNCH. This transaction is called when the dependent
transaction launcher is called.
844 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
~WEBGUI_SIMPLE_TOOL 114
BAR
Click to continue.
8. In the Handler List tab, set the Handler class name CL_HTTP_EXT_ITS.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 845
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
12. To activate the parent node where you have created the new service name,
select the node default_host > sap and right-click.
846 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
Click .
1. In the CRM system, navigate to SAP menu > Interaction Center > Interaction
Center WebClient > Administration > System Parameters > Define
Transaction Launcher Logical Systems and URLs.
Alternatively, run the CRMS_IC_CROSS_SYS transaction.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 847
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
2. Maintain the Mapping name and the corresponding backend ERP Logical
System name with the ITS Client and the URL of ERP ITS, specifically for
OpenText components.
Determine the URL of ITS, for example: <http>://<Host Name>:<Port>/
<sap><created service name path>?sap-client=<CLIENT>.
If SAP Shared Service Framework for Financials is enabled in your SAP ERP
backend system, use the WEBGUI ITS service instead of your newly created
service:
• if you are using SAP ERP 6.0 enhancement package 5 (or higher), or
• if you have implemented all the SAP notes regarding the enablement of
the Financials Shares Service Center (see SAP note 1454759).
Notes
• Mapping logical systems and setting the URLs for standard SAP objects
like Vendor Links in business context must follow SAP conventions to
determine the URLs.
• You must maintain 2 URLs for each backend ERP system, one URL for
standard SAP objects and another URL for OpenText objects.
• Mapping names for OpenText objects follow a convention: The first 5
characters in the mapping name are ZZZZZ, followed by free text that
identifies the backend ERP system, for example ZZZZZD94.
848 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
3. If your CRM system is connected to more than one SAP ERP backend system,
mark the MultiSys check box for your OpenText object URL links.
URL for OpenText objects (--> see “Maintaining the logical system in
OpenText configuration tables [CRM]” on page 881)
Mapping: ZZZZZD94
Logical system: D94CLNT800
Local ITS:
ITS Client: 800
URL of ITS: http://op60vimd94.optura.local:8000/sap/bc/
gui/sap/its/opt_ltx?sap-client=800
Mapped Logical System Description: D94CLNT800
URL for standard SAP objects
Mapping: ZZZZZD95
Logical system: D95CLNT800
Local ITS:
ITS Client: 800
URL of ITS: http://op60vimd95.optura.local:8000/sap/bc/
gui/sap/its/webgui/!?~transa
ction=IC_LTXE&~okcode=ICEXECUTE
Mapped Logical System Description: D95CLNT800
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 849
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
To create a transaction launcher for VIM work centers to call VIM Analytics
(Service Request):
2. Click Continue.
850 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
3. Enter the Launch Transaction ID, for example ZVIM_TL_CONFIG_SRQ, and the
Component Set ALL.
Click Continue.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 851
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
852 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
5. In the Transaction Type list, select A BOR Transaction and fill in the following
details:
Logical System
Example: D94CLNT800 (belonging to mapping ZZZZZD94)
See “Defining transaction launcher logical systems and URL [CRM]”
on page 847.
BOR Object Type
/OPT/V1001
Method Name
DISPLAY
6. Click Continue.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 853
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
854 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 855
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
9. Click Complete.
10. Change the Handler Class of the newly created Transaction Launcher ID.
Perform the following steps:
c. Change the Handler Class entry for the selected Launch Transaction ID
to /OPT/CL_VIM_TL_CONFIG_SRQ.
856 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
• if you are using SAP ERP 6.0 enhancement package 5 (or higher), or
If the Definition fields are not populated correctly, delete the newly created
Launch Transaction and repeat the above steps beginning from Step 1. Check
the fields in Step 5 carefully.
To create a transaction launcher for VIM work centers to call VIM Analytics
(account ID confirmation):
Note: When entering the same handler class in Step 4, the fields in the
Details section are prefilled automatically in Step 5.
2. Change the Handler Class of the newly created Transaction Launcher ID.
Perform the following steps:
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 857
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
c. Change the Handler Class entry for the selected Launch Transaction ID
to /OPT/CL_VIM_TL_CONFIG.
In the CRM Interaction Center, the work centers are displayed as buttons in the
navigation bar.
858 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 859
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
2. In the Define Logical Links screen, click New Entries and create a new Logical
Link ID using the following parameters:
Logical Link ID
<Name of the Logical Link ID>, for example ZAIC_LINK1
Type
Launch Transaction
Target ID
EXECLTX
Parameter
<Your Launch Transaction ID>, for example ZVIM_TL_CONFIG_SRQ; see
“Creating a transaction launcher for VIM work centers to call VIM Analytics
(Service Request) [CRM]” on page 850
Parameter Class
CL_CRM_UI_LTX_NAVBAR_PARAM
Title
VIM Analytics SRQ
Description
VIM Analytics SRQ
3. Click New Entries again and create another new Logical Link ID using the
following parameters:
860 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
Logical Link ID
<Name of the Logical Link ID>, for example ZAIC_LINK2
Type
Launch Transaction
Target ID
EXECLTX
Parameter
<Your Launch Transaction ID>, for example ZVIM_TL_CONFIG; see “Creating a
transaction launcher for VIM work centers to call VIM Analytics (account
ID confirmation) [CRM]” on page 857
Parameter Class
CL_CRM_UI_LTX_NAVBAR_PARAM
Title
VIM Analytics Account ID
Description
VIM Analytics Account ID
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 861
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
5. Create one work center for VIM Analytics with regards to Account ID and
another work center for VIM Analytics with regards to Service Request. Enter
the Logical Link ID, created in Step 2 and Step 3.
Note: SAP's default navigation bar profile for the Accounting Interaction
Center Agent is AIC_AGENT. SAP strongly recommends that you never
alter the SAP Standard Navigation Bar Profiles. Always create a new one
or use an existing copy of the Navigation Bar Profiles. See the SAP
documentation for more information about copying the Navigation Bar
Profiles, assigning them to business roles, and so on.
862 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
8. Assign the 2 work centers you have created and enter the position at which the
work centers should be located within the navigation bar.
Save your changes.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 863
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
3. Define a Link Type with the same name as business object name: /OPT/V1001
with Description of Object Link Type: OpenText DP document and save the
Link Type.
Note: Ignore a warning to choose the key from the allowed namespace.
4. Select the Link Type /OPT/V1001 and double-click Define Object Link Type
Details in Dialog Structure.
5. In the Define Object Link Type Details screen, click New Entries.
Note: Ignore a warning to choose the key from the allowed namespace.
7. Double-click Define Object Link Profile in Dialog Structure and select the
Link Prof. SSF_AIC.
.
864 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
9. Click New Entries and assign the new entry /OPT/V1001 to the Link Types of
Object Link Profile SSF_AIC and save the configuration.
Note: Ignore a warning to choose the key from the allowed namespace.
10. In Dialog Structure, double-click Define Business Context Profile and select
the SSF_AIC Business Context Profile.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 865
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
Note: Ignore a warning to choose the key from the allowed namespace.
13. In Dialog Structure, double-click Define Business Context Profile and select
the Business Context Profile SSF_ALL.
Note: Ignore a warning to choose the key from the allowed namespace.
866 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
17. In the Define Logical Links screen, click New Entries and create a new Logical
Link ID for Service Request Business Context DP links, using the following
parameters:
Type
Enter Link.
Parameter
Enter the already created Launch Transaction ID (see “Creating a
transaction launcher for VIM work centers to call VIM Analytics (Service
Request) [CRM]” on page 850) with regards to the Service Request work
center.
18. In Dialog Structure, double-click Define Navigation Bar Profiles and select the
custom Navigation Bar Profile.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 867
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
20. In the Define Generic Outbound Plug Mappings screen, click New Entries,
create a new entry with name WRAPPED_/OPT/V1001, and assign the Logical
Link ID created for Business context links, for example ZOPTBC.
21. Repeat Step 18 to Step 20 for all custom Navigation Bar Profiles that are
affected; that means, also for the navigation bar profile belonging to the SAP
Shared Service Framework Occasional User (for example, navigation bar profile
ZVIM_SSF_OCC_USER).
Note: SAP's default navigation bar profile for the SAP Shared Service
Framework Occasional User is SSF_OCC_USER. SAP strongly recommends
that you never alter the SAP Standard Navigation Bar Profiles. Always
create a new one or use an existing copy of the Navigation Bar Profiles.
Please see the SAP documentation for more information about copying the
Navigation Bar Profiles, assigning them to business roles, and so on.
868 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
Object Type
WRAPPED_/OPT/V1001
Description
OpenText Document
The Factsheet uses the Business Server Page (BSP) component to display the loading
data in a web browser.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 869
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
Note: All OpenText CRM BC SETs must be activated before the following
step.
Implementation Class
/OPT/CL_FACTSHEET
Object Table
/OPT/FS_OBJECT
Model Table
/OPT/FS_MODEL
870 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
In the Component Assignment screen, click New Entries, assign the newly
created Component Name to the newly created Component Set, and save the
configuration.
6. Click Runtime Repository Editor, expand the Models node and click to
switch to edit mode.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 871
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
9. Open the Models node. Right-click Models and click Add Model.
872 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
10. Enter the Component Set name created in Step 3 on page 870, for example
ZOPTCOMPSET.
Save and exit from the transaction.
11. To configure the view in the BSP component, run the BSP_WD_CMPWB transaction
(UI Component Workbench), enter the Component /OPT/VENDOR_FS, and click
Display.
Click Component Structure Browser.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 873
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
Click .
Press the ENTER key and assign to a Transport Request.
874 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
14. Select the fields in Available Fields and move them to Displayed Fields.
15. When you have moved all fields to Displayed Fields, save and exit from the
transaction.
17. Choose the Fact Sheet ID to plug the OpenText Vendor Factsheet. You can add
the BSP Component /OPT/VENDOR_FS to any of the Fact Sheet IDs. In the
example, the BSP Component /OPT/VENDOR_FS is added to Fact Sheet ID
FSSC_VEND_FS.
Select the Fact Sheet ID FSSC_VEND_FS and double-click View Assignments in
Dialog Structure.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 875
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
Component Name
/OPT/VENDOR_FS
Interface View
Select /OPT/VENDOR_FS/MainWindow from the drop-down list (F4 help).
Inbound Plug
DEFAULT
Title
OpenText Vendor Factsheet ID
Note: Ignore a warning to choose the key from the allowed namespace.
19. To link the configured Factsheet ID to the BSP Vendor Factsheet ID, run the
BSP_WD_CMPWB transaction (UI Component Workbench), enter the Component
BSP_DLC_FS, and click Display.
876 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
21. From the drop-down list, select the Factsheet where you added the OpenText
business component. In the example, the BSP Component /OPT/VENDOR_FS was
added to Factsheet ID FSSC_CUST_FS
Select the Factsheet FSSC_CUST_FS and click New.
22. From the drop-down lists, select the Fact Sheet ID FSSC_CUST_FS and the Role
Key Accounting IC Default Key and click Next.
Note: If you use a customer specific role configuration key, select your
role configuration key for the field Role Key instead of selecting the
default role configuration key Accounting IC Default Key.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 877
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
23. From the drop-down lists, select the Page Type, for example Tiles, and the
Tile Layout, for example 2_X_3 (2 columns and 3 rows), then click Next.
Each cell (tile) in Tiles represents a View. Tiles are grouped under a Tiles group
which is displayed in the CRM UI page.
24. To move the OpenText Vendor Factsheet to any of the tiles, select a tile, then
select the OpenText Vendor Factsheet ID, and click the down arrow which will
place the OpenText Vendor Factsheet into the selected tile.
Use the Up and Down arrows to move the OpenText Vendor Factsheet to the
target position within the tile.
878 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
Click the Configuration link to the right of the assigned OpenText Vendor
Factsheet.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 879
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
27. Select the Available Fields and move them to the Displayed Fields. To do so,
select each field and click the arrow button.
880 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
29. Click Save and then click Finish. The new configuration is saved.
Exit from the transaction.
Every backend ERP system is mapped with a unique mapping name as a logical
system. Maintain the mapping names for each logical system in tables/views /OPT/
LOGSYS_MAP.
Note: Mapping names for OpenText objects follow a convention: The first 5
characters in the mapping name are ZZZZZ, followed by free text that identifies
the backend ERP system, for example ZZZZZD94.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 881
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
3. In the Mapping column, enter an appropriate mapping name for the Logical
system of the VIM system. See also “Defining transaction launcher logical
systems and URL [CRM]” on page 847.
This setting restricts the user not to display all other work centers when opening a
Service Request from VIM Analytics.
2. In the Define Prefill Business Role Settings for RFC screen, add a new entry
with the following values:
RFC Name
CRM_PREFILL_SRVQ_RFC_DISPLAY
882 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.1. SAP Shared Service Framework integration activities
Business Role
<Name of your business role for the SSF Occasional User>, for example
ZVIM_SSF_OCC
Object Type
CRM_SRQM_INCIDENT
Object Action
Display
4. Repeat Step 2 and Step 3 to create a second entry with the following values:
RFC Name
CRM_PREFILL_SRVQ_RFC_CREATION
Business Role
<Name of your business role for the SSF Occasional User>, for example
ZVIM_SSF_OCC
Object Type
CRM_SRQM_INCIDENT
Object Action
Create
5. Repeat Step 2 and Step 3 to create a third entry with the following values:
RFC Name
CRM_PREFILL_SRVQ_RFC_SEARCH
Business Role
<Name of your business role for the SSF Occasional User>, for example
ZVIM_SSF_OCC
Object Type
CRM_SRQM_INCIDENT
Object Action
Search
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 883
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
When creating a CRM service request, some fields can be set initially. The
initialization procedure defines the initial values (the default values) for some fields
in a CRM service request. Moreover, the initialization procedure provides the
configuration options to set initial values to these fields.
1. Run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Invoice Management > Cross Component Configuration > CRM Integration >
Maintain Initialization procedure for service requests.
Field Type
Select Table or Field from the drop-down list.
Value Determination Type
Select one of the following types from the drop-down list:
Field value
Enter the field value, depending on the setting in Value Determination
Type.
884 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.3. Mapping the initialization procedure to the Service Request creation points [ERP]
Function Module
Provide the name of the function module that will provide the value of
the field. The interface of this function module must be exactly the same
as /OPT/SR_DETERMINE_FIELD_VALUE.
Application Variable
Provide any field from the table /OPT/VIM_1HEAD.
1. Run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Invoice Management > Cross Component Configuration > CRM Integration >
Mapping of Initialization procedures to SR creation points.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 885
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
1. Run the SPRO transaction and navigate to the menu path Cross-Application
Components > Processes and Tools for Enterprise Applications > Shared
Service Framework > Integration with SAP CRM > Integration with Service
Request > Define Customer Application > Define Application Areas.
Application
FINANCIALS
3. Run the SPRO transaction and navigate to the menu path Cross-Application
Components > Processes and Tools for Enterprise Applications > Shared
Service Framework > Integration with SAP CRM > Integration with Service
Request > Define Customer Application > Define Activities.
886 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
31.4. Defining Application Areas for Service Request [CRM]
Application
FINANCIALS
5. Run the SPRO transaction and navigate to the menu path Cross-Application
Components > Processes and Tools for Enterprise Applications > Shared
Service Framework > Integration with SAP CRM > Integration with Service
Request > Processing > Activate Manual Service Request Creation for
Activities.
Application
FINANCIALS
Activity
SAIC
Application Area
VIM
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 887
VIM070500-08-CGD-EN-01
Chapter 31 SAP Shared Service Framework integration
Man. Creat
Select the check box.
7. Run the SPRO transaction and navigate to the menu path Cross-Application
Components > Processes and Tools for Enterprise Applications > Shared
Service Framework > Integration with SAP CRM > Integration with Service
Request > Processing > Determine Service Request Attributes from
Application Context.
Application
FINANCIALS
Application Area
VIM
Trans. Type
SAIC
9. Based on the application area, you can perform some further settings, for
example determine service request attributes from the application context. For
example, you may want to populate the subject category fields. For more
information, see the SAP documentation of the IMG activities mentioned in this
section.
888 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 32
SRM integration
VIM supports the following scenarios for SRM related purchase order invoices:
• Missing goods receipt (GR) for SRM related purchase orders (SRM scenario
“Classic” and “Extended Classic”)
• Quantity discrepancy in invoice for SRM related purchase orders which requires
confirmation in the SRM system (SRM scenario “Classic”)
• Price discrepancy in invoice for SRM related purchase orders which requires
changes in the purchase order located in the SRM system (SRM scenario
“Extended Classic”)
Note: For details about the scenarios, see “Configuring SRM purchase orders”
on page 893.
This chapter describes the activities necessary for configuring the SRM integration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 889
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
890 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
32.1. Use cases
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 891
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
1. Run the /N/OPT/SPRO transaction and navigate to the menu path Vendor
Invoice Management > PO Based Invoice Configuration > SRM Integration >
SRM PO Statuses.
892 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
32.3. Configuring SRM purchase orders
2. Check the values in table EKKO, field STATU, for SRM related purchase orders
and maintain the appropriate statuses in the Constant Value field, separated by
semicolons.
Z constant The Z constant SRM_PO_CHECK for the product code LIX enables you to write custom
SRM_PO_CHE logic to determine if a particular PO is an SRM PO. You must write the custom logic
CK
in a custom function module. This function module is called from the standard
function /OPT/S_DETERMINE_SRM_PO_TYPE. Your custom function module must
have the same interface as the standard function module /OPT/
S_DETERMINE_SRM_PO_TYPE.
To access the respective menu items for this section, run the /N/OPT/SPRO
transaction and navigate to the menu path Vendor Invoice Management > PO
Based Invoice Configuration > SRM Integration.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 893
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
Process type VIM Baseline contains process type 162 for SRM. See “Configuring the process type”
maintenance on page 230 for details on maintaining the process type.
Verify that the following fields are maintained for the SRM process type:
Option to send VIM Baseline contains the option ID 2740 which will enable the AP Processor to
email send an email to the SRM user. You can configure the email text based on the mail
configuration ID maintained in the process option. See “Configuring the SRM mail
infrastructure” on page 900 for details on how to maintain the email text.
Note: The baseline configuration for process option 2740 always uses the send
function /OPT/S_DP_EMAIL_NOTIFICATION. The possibility to set a custom
send function in the configuration for process type 162 (see “Process type
maintenance” on page 894) has no effect on process option 2740.
894 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
32.3. Configuring SRM purchase orders
In the quantity discrepancy scenario, you need to maintain the DP process type for
the Missing goods receipt scenario; see “Missing goods receipt scenario”
on page 894. The SRM process type will be used to determine attributes like the
delay time and get the receiver email ID.
1. Run the SM30 transaction to maintain table /PTGWFI/Z_CONST, and locate the
record with Product Code LIX and Constant SRM_QTY_BLK_PROCTYPE.
2. Enter the SRM Quantity Block process type in the Constant Value field. The
OpenText Baseline value is 162.
The maximum number of days (delay time) will be based on the process type.
The delay time will be calculated as the Maximum Number of retry time
multiplied by the Maximum Retry time limit.
The Email Receiver function module to get the receivers is also derived from the
process type.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 895
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
2. Enter the mail configuration ID in the Constant Value field and save your
settings. For details on the mail configuration ID, see “Configuring the SRM
mail infrastructure” on page 900.
You must determine the initial actor who will receive the work item after the wait
period completes.
2. Enter the initial actor's role in the Constant Value field and save your settings.
896 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
32.3. Configuring SRM purchase orders
If these conditions apply, an email will be sent to the SRM requester to change the
purchase order. The workflow will be in wait status for the specified time, based on
the configuration. After the time has lapsed or the block has been removed, the work
item will be completed.
The mail configuration ID is used for sending emails out. You can modify the actual
email content, see “Configuring the SRM mail infrastructure” on page 900.
2. Enter the mail configuration ID in the Constant Value field and save your
settings. For details on the mail configuration ID, see “Configuring the SRM
mail infrastructure” on page 900.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 897
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
You must determine the initial actor who will receive the work item after the wait
period completes.
2. Enter the initial actor's role in the Constant Value field and save your settings.
After the workflow has sent an email to the SRM user, the workflow is in wait
status. You can configure the amount of time for the wait period.
898 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
32.3. Configuring SRM purchase orders
2. Enter the amount of time for the wait period (in minutes) in the Constant Value
field and save your settings.
Note: For the price discrepancy scenario, only the “Extended Classic” SRM
scenario is relevant.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 899
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
2. Enter EXTENDED_CLASSIC or CLASSIC in the Constant Value field and save your
settings.
Email body and email subject base on the business object type and object key.
Email format The SRM email notification can be sent in different formats. The format is configured
in Z Constant (product code 005) REM_MAIL_DOCTYPE . Default value is RAW. This
email format is used globally for all kind of email notification : Reminder
notification, Approval notification, and SRM notification.
The notification emails can be sent in HTML format with readable formatting and
invoice data presented in the form of HTML tables. To enable this functionality, you
must set the constant 005 / REM_MAIL_DOCTYPE to HTM. In the /OPT/VIM_8CX50
transaction, you must configure the Email Type to be Internet Email.
900 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
32.4. Configuring the SRM mail infrastructure
2. To add a new entry in the Mail config definition overview screen, click New
Entries in the application tool bar.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 901
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
Object type
Enter the VIM object type. The following values are possible:
/OPT/V1001
Object type for DP
/OPT/LIV
Object type for blocking
Text Block 1
Enter a text object for the email context header, like addressing and
description of the issue. For example, /OPT/VIM_DP_SRM_QTY_HEADER is a
text for the DP email header.
Note: You can maintain text objects using the SO10 transaction.
Text Block 2
Enter a text object for the URL Header; for example, /OPT/
VIM_DP_SRM_QTY_URL_HEAD.
Text Block 3
Enter a text object for the conclusion and/or the address of the email
generating location. For example, /OPT/VIM_DP_SRM_QTY_FOOTER is a text
for the email footer.
902 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
32.4. Configuring the SRM mail infrastructure
I_MAIL_CFG_ID
Mail configuration ID
I_OBJTYPE
Object type
I_OBJKEY
Object key
Exporting parameters
T_URL
Table of URLs
URL
Enter a URL that is used in the mail body, in case the URL generating
function module is not maintained.
Line Item Function Module
Enter the function module that will populate the line item information and
construct the table. For example, the function module /OPT/
CNOTIF_GET_LINE_ITEM_DATA will populate the line item information with
the following parameters:
Importing parameters
I_MAIL_CFG_ID
Mail configuration ID
I_OBJTYPE
Object type
I_OBJKEY
Object key
I_GROUP_BY
Group by (used as SRM PO Requester in baseline)
Exporting parameters
T_LINE
Table parameter, with PO line item information
4. To configure the mail fields which need to be populated in the email content,
double-click Mail field list and description in the Dialog Structure panel.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 903
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
The list shows all object key fields that can be shown in the email. These fields
derive from the object type defined in Step 3 on page 902.
6. To configure the mail subject line, double-click Mail subject/Title in the Dialog
Structure panel.
904 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
32.4. Configuring the SRM mail infrastructure
Maintain the (language dependent) mail subject. The mail sending function
module will populate the appropriate subject if it is not set while invoking the
mail.
You must enable the email sending program to send invoice images as attachments
with the correct file extension. Therefore, you maintain the attachment extensions
for each archive object type.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 905
VIM070500-08-CGD-EN-01
Chapter 32 SRM integration
In the example, the Image File extension TIF is maintained for the archive
object type /OPT/ICC. For /OPT/ICC, invoice images will be archived and
attached to emails as *.TIF.
906 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 33
PDF log
At various locations throughout VIM, a PDF log can be created. At the beginning of
the VIM process, it is possible to create PDFs of incoming IDocs. At the end of the
VIM process, it is possible to automatically create a PDF history log.
Note: If any issues occur during the creation of the PDF log, a log message is
written to the application log for the /OPT/VIM object with subobject DP. For
more information about the application log and how to display log messages,
see section 27 “Working with the application log” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM070500-08-AGD).
2. In the Define Profiles screen, define the profile, using the following parameters:
PDF Profile
Enter the unique ID of the profile.
Profile Description
Enter the description of the profile.
PDF Log Class
Enter the name of the class containing the logic for creation of the PDF log.
As an example, see the /OPT/CL_C_PDF_LOG class for the PDF history log,
which is delivered with the baseline.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 907
VIM070500-08-CGD-EN-01
Chapter 33 PDF log
You can enhance the baseline classes for the specific PDF log by redefining
components of the class within a custom class, which you can maintain
instead of the baseline class.
PDF Form Type
Enter the type of the PDF form.
There are different ways to create a PDF file in a SAP ERP system, for
example by creating a local spool request, by using SAP Script, SAP Smart
Forms, or SAP Interactive Forms by Adobe. SAP Smart Forms are included
in the baseline delivery. Currently, Smart Forms is the only available entry
for this field. However, it is also possible to redefine the logic of the PDF log
classes within custom classes to support other techniques, for example SAP
Interactive Forms.
Form Name
Enter the name of the SAP Smart Forms form.
As an example, see the /OPT/C_WORKFLOW_HISTORY01 SAP Smart Form for
the PDF history log, which is delivered with the baseline.
You can copy the SAP Smart Forms of the baseline using the smartforms
transaction and adjust them to your needs. You can maintain the adjusted
Smart Form in the Form Name box instead of the baseline Smart Form.
PDF Language
Select the language to be used for the PDF log. The following values are
available:
Fixed Language
A fixed language key is used for the PDF log. If you enter Fixed
Language, it is necessary to enter a value in the Language box.
Language
If you have selected Fixed Language in the PDF Language field, enter the
language, for example EN, in this box.
PDF Timezone
Select the time zone to be used for time values in the PDF log. The following
values are available:
Fixed Time Zone
A fixed time zone is used for the PDF log. If you enter Fixed Time
Zone, it is necessary to enter a value for the Time Zone box.
908 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
33.1. Customizing profiles for the PDF log
Time Zone
If you have selected Fixed Time Zone in the PDF Timezone field, enter the
time zone in this box.
Document type
Enter the archive document type to be used for archiving the PDF log.
Important
The document type must be different from the one used for the
invoice image.
Overwrite
Select this check box to overwrite PDF logs that have already been linked to
the DP document and its SAP invoice with the same archive document type.
Selecting the Overwrite check box deletes the physical PDF log and its links
to the DP document and the SAP invoice.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 909
VIM070500-08-CGD-EN-01
Chapter 33 PDF log
The PDF history log file is archived and linked to the DP document and its SAP
invoice.
910 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
33.3. PDF history log
You must specify that the PDF history log will be created at the end of the VIM
process. To enable the creation of the PDF history log, you must assign the profile
for the PDF history log (default profile: HISTORY) to the VIM process “VIM process
is finished”. Without this, the PDF history log will not be created at the end of the
VIM process.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 911
VIM070500-08-CGD-EN-01
Chapter 33 PDF log
2. In the Define Profiles screen, define the profile. The following parameters are
specific for the PDF history log.
Note: For a description of the profile definition for PDF logs in general,
see “Defining profiles for the PDF log” on page 907.
912 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
33.3. PDF history log
Form Name
Enter the name of the SAP Smart Forms form.
Baseline delivery includes a Smart Form /OPT/C_WORKFLOW_HISTORY01.
You can copy the Smart Form using the smartforms transaction and adjust
it to your needs. You can maintain this adjusted Smart Form in the Form
Name box instead of the baseline Smart Form.
The baseline Smart Form uses the SAP Smart Style /OPT/C_SF_STYLE01 for
the format options of the Smart Form, for example the font and the font size
of headers or default paragraphs. You can copy the Smart Style using the
smartstyles transaction and adjust it to your needs. Additionally, copy the
Smart Form and maintain your new Smart Style in the Output Options tab
of the Form Attributes screen of the Smart Form.
Default value: /OPT/C_WORKFLOW_HISTORY01
Document type
Enter the archive document type to be used for archiving the PDF history
log.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 913
VIM070500-08-CGD-EN-01
Chapter 33 PDF log
With baseline delivery, a profile (HISTORY) is delivered, which creates a PDF file
with history information of the VIM process.
To create this PDF history log at the end of the VIM process, you must assign the
profile to the VIM process is finished process step for your company codes. If you
leave Company Code empty, the setting is used for all company codes.
Note: The VIM process is finished process step is triggered only if there is a
DP document workflow running. This is not the case for the old direct posting
and direct parking scenario. If you want to create a PDF history log
nevertheless, use the /OPT/CR_PDF_LOG report. For more information about the
report, see section 26 “Creating a PDF history log file” in OpenText Vendor
Invoice Management for SAP Solutions - Administration Guide (VIM070500-08-
AGD).
914 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Part 5
Special topics
Part 5 Special topics
This part describes the configuration of VIM special topics, like VIM Notifications.
916 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 34
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 917
VIM070500-08-CGD-EN-01
Chapter 34 Posting Non PO (FI) invoices
information, see the SAP BAPI documentation. This posting function creates an
LIV document in addition to the FI document. That LIV document is not shown
in VIM reporting whereas the FI document is shown everywhere.
Table 34-1: “Scenarios of posting BDCs” on page 918 lists some known scenarios
where the logic differs between the posting BDCs listed in this section. Use this table
as a guide when deciding which BDC ID is suitable for your process.
Additional You might want to use the extended VAT date support for PO invoices and Non PO
transport invoices posted with BDC 42. In this case, you need to import an additional
transport, which contains a BAdI implementation used in the posting. For more
information, see section 3.2.12 “Installing transport for extended VAT date support”
in OpenText Vendor Invoice Management for SAP Solutions - Installation Guide
(VIM070500-08-IGD).
918 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
34.2. Dialog posting of Non PO (FI) invoices
The SAP BAdI definition used by this functionality allows only one implementation
to be active. Importing the transport replaces the active standard implementation,
which is linked to the SAP class CL_BADI_EXM_VATDATE_VALUES_SAP. The OpenText
implementation, which becomes active, calls the standard class if a document is not
posted from VIM. If you are using a custom implementation, OpenText recommends
that you activate it again and merge the logic of the OpenText implementation into
it.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 919
VIM070500-08-CGD-EN-01
Chapter 35
Down payments process for PO and NPO invoices
In the baseline, the classifier field has already been added to the standard field
mapping for the ICC channel and the technical ICC – VIM interface in general.
Restriction
At the moment, ICC does not recognize down payments out of the box. It
requires additional project specific configurations because there are many
different requirements, which usually vary from automatic classification based
on keywords to manual document separation and scanning.
ICC Invoice Category is mapped to the field INV_CAT. There is a new function
module for field mapping: /OPT/VIM_CONVERT_INV_CAT.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 921
VIM070500-08-CGD-EN-01
Chapter 35 Down payments process for PO and NPO invoices
922 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
35.1. General information and DP process
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 923
VIM070500-08-CGD-EN-01
Chapter 35 Down payments process for PO and NPO invoices
• AP_PROCESSOR
• BUYER
• DUP_CHECK
• INDEXER
• RESCAN
BDC-ID 50
Dialog posting of down payment requests using the F-47 transaction.
BDC-ID 51
Background posting of down payment requests using the F-47 transaction.
Input data is transferred from the DP document into the batch input calls of F-47.
As an exception, fields like posting date and currency translation date are set
according to VIM customizing. The special G/L indicator is set according to the
characteristic specific settings relevant for the document. In VIM baseline, the special
G/L indicator is country specific, that means, a fixed value for special G/L indicator
per country. For more information, see “Characteristic specific settings for document
types” on page 558.
924 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
35.2. Down payment approval
To support the line item tax for down payments, a new line item field
ITEM_TAX_AMOUNT has been created with VIM 7.0 SP1 in the accounting structure /
ORS/INVOICE_ACCT_DATA. The new field is set up in the table /OPT/FIELDS for the
device names WEB and MOB.
Z constant To enable document type specific tax logic, maintain the Z constant IAP -
CALC_TAX_O CALC_TAX_ON_NET in the global constant table /PTGWFI/Z_CONST. For the Constant
N_NET
Value, enter D. For more information, see “Configuring tax calculation on net
amount” on page 380.
Document type In the document type configuration, clear the Calculate Tax on Net check box.
configuration
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 925
VIM070500-08-CGD-EN-01
Chapter 35 Down payments process for PO and NPO invoices
926 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 36
Tools
VIM provides some tools that help to use the application. The following tools are
available:
2. Enter the relevant information for the role you want to test. For example:
Company Code, Document Number, and Responsible Party.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 927
VIM070500-08-CGD-EN-01
Chapter 36 Tools
The result for that role shows the default user maintained for this role:
REQUESTER1.
928 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
36.3. Changing the work item text
TS00275253
Approve Invoice
TS00275260
Non-PO Invoice Dashboard
TS00275262
PO Parked Invoice Dashboard
TS00275265
PO Invoice Dashboard (Line Level)
TS00275267
PO Invoice Dashboard (Header WF)
TS00275278
DP Document Dashboard
TS00275283
Reference requested
2. In the Multi Language Workitem Text Maintenance Utility screen, enter the
task ID (TS00275257 in the example) and press the ENTER key.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 929
VIM070500-08-CGD-EN-01
Chapter 36 Tools
4. Change the text in the Task Text field and click the Update button.
Important
Actually, these tools are internal tools. Although you can use them, OpenText
does not provide customer support for these test tools.
Transaction /OPT/VIM_7AX1
Non-OCR Scenario
Transaction /OPT/VIM_7AX2
OCR Scenario
Transaction /OPT/VIM_7AX7
OCR Test Utility
930 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 37
Using VIM Notifications
The VIM Notifications program (called VIM Reminder in earlier versions) provides a
way to remind users about the invoices waiting in their inbox to be processed. The
program sends email notifications for all overdue invoices and for invoices that have
spent a particular number of days in the user inbox. You can customize the number
of days.
To start the VIM Notifications program, run the /OPT/REMINDER transaction. The
program is typically scheduled as a batch job so that the agents get notifications of
their reminders regularly.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 931
VIM070500-08-CGD-EN-01
Chapter 37 Using VIM Notifications
The selection screen allows you to enter search criteria and process options. The
selection screen is divided into the following panels:
• Invoice Information
• Document Process
• Workitem Date Range
• Process Options
• Recipient of Reminder
Tip: Where applicable, use for multiple selection and for search
help.
932 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
37.1. Working with the selection screen
• Company Code
• Document Number
• Fiscal Year
• Line Item
• Document ID: the number that was generated for the document during
the DP process
• SAP User ID
• OpenText User Id
Note: When adding user IDs as search criteria, the system does not
consider the substitutes for the user, if there are any.
• Document Processing
• PO Block Invoices - Header
• PO Block Invoices – Line
• PO Parked Invoices
• NPO Parked Invoices
• PO Approval Inv. (Parked/DP)
• NPO Approval Inv. (Parked/DP)
• PO Referred Invoices
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 933
VIM070500-08-CGD-EN-01
Chapter 37 Using VIM Notifications
Mode
Select one of the process modes:
Test
The program generates a list of eligible work items for notification.
The program does not send the notifications. Users can select the
work items to send the notification.
Background
The program sends the notification to users and displays the work
items.
4. Once you finished entering the search criteria and selecting the process options,
click in the application tool bar to display the VIM Notifications List with
the search results.
934 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
37.2. Working with the VIM Notifications List
Send Notification
To send an email or an SAP note to an agent, select the agent in the list and click
the Send Notification button.
SAPconnect
To run the SCOT transaction, click the SAPconnect button.
The SAPconnect Administration (system status) screen is displayed.
SAPconnect allows the connection of external communication components to the
SAP ERP system.
Details: Select a line in the list and click this button to display details for the
selected line.
, Sort: Select a report column in the list and click one of these buttons to sort it in
either ascending or descending order.
Find: Click this button to open the Find dialog that allows you to search the list
for any keyword.
Filter: Select a report column in the list and click this button. The Filter criteria
dialog is displayed, allowing you to restrict the criteria in the selected column
without having to rerun the report with new search criteria.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 935
VIM070500-08-CGD-EN-01
Chapter 37 Using VIM Notifications
Layout: Click this button to select a saved layout. To change, save or manage
layouts of the list, click the icon next to the Layout button.
Notes
• The following list only covers columns whose meaning is not obvious.
• Some of the column headers might be abbreviated. Expand the column to see
the full text.
• The columns might not be displayed or might not be in the following
sequence. You can add or remove columns, or change the sequence by using
the Layout function, see “ALV grid control” on page 935.
Column Description
Current Agent Current agent who owns items
Process Type Type of the document (DP, PO document, Non PO document…); see the
list in Scenario on page 933.
936 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
37.3. Configuring VIM Notifications
Sub Process Sub Process Type for each process type, for example Approval
Type Required for Non PO Invoice Approval process type
Document SAP document number
Number
Document ID DP document ID
Vendor Vendor number
Name 1 Vendor name
Inbox Days Number of days the work item lies in the inbox
Before Due Days before the due date of the work item
Due Date Due date of the work item
First name First name of the current agent
Last name Last name of the current agent
Responsible Role that is responsible for the work item
Party
Receiver ID Email address of the current agent
ID Work item ID
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 937
VIM070500-08-CGD-EN-01
Chapter 37 Using VIM Notifications
Note: You cannot change the Notification Type and the Notification Sub
Type for an existing notification.
3. To add a notification, click the New entries button in the application tool bar.
Notification Type
Select the notification scenario. Possible values:
• Document Processing
• PO Parked Invoices
• PO Blocked Invoices - Line Level
• PO Blocked Invoices - Header Level
• NPO Parked Invoices
• NPO Approval Invoices (Parked/DP)
• PO Approval Invoices (Parked/DP)
• NPO Referred Invoices
• PO Referred Invoices
Example: Notification sub scenarios for the NPO Parked Invoices notification
scenario:
• Approval Required
938 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
37.3. Configuring VIM Notifications
• Vendor Maintenance
• Vendor Audit Required
• Tax Audit Required
• All Scenarios
Responsible Party
Select the role for the notification. All users assigned to this role will receive
the notification.
Notify Substitutes
Select this check box to have all notifications also sent to substitutes of users
that receive the notification.
Notify Manager, Notification Counter
The notification program enables you to also inform the manager about
approval work items that are too long in the inbox of an approver. This
configuration is available for the Approval and Referred notification types.
Select the Notify Manager check box, to send the notification email in CC to
the related manager, too.
In the Notification Counter field, enter the number of notification mails
that have been sent to a user, before a notification mail is sent to the
manager, too. Therefore only one invoice needs to be over the limit in the
list of invoices which the notification program collects.
For the level based approval, it is also possible to configure the manager
within COA. The manager will only be used for the notification escalation
processing but not for any approval processing logic.
Inbox Days, Days Before Payment Due
Use these two fields to decide if the reminder will be sent. The system
calculates the work item creating date plus the inbox days or the days
before payment is due. If the result is less or equal today's date, then a
reminder will be sent.
Email Type
Select the notification type. At the moment, only Internet Email is
available.
Notification Text
Select the SAP text name to be used for the notification email body.
Notification Receiver Function
Select the function module that determines the email address for the
notification. The interface for this function module is same as for the /OPT/
VIM_NOTIF_EMAIL_ADDRESS function module.
If you select a different function model in this field, VIM Notifications will
run this function module first. If the function module cannot find a valid
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 939
VIM070500-08-CGD-EN-01
Chapter 37 Using VIM Notifications
email address, VIM Notifications will run the default function module /
OPT/VIM_NOTIF_EMAIL_ADDRESS.
Field name
You find the field names in structure /OPT/VIM_S1_REMINDER_MAILBODY.
Each field name represents a column in the generated VIM Notifications
email.
Note: You cannot change this parameter in the Mail Configuration
screen.
Language
VIM supports the following languages:
• Czech (CZ)
940 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
37.3. Configuring VIM Notifications
• German (DE)
• English (EN)
• Spanish (ES)
• French (FR)
• Hungarian (HU)
• Italian (IT)
• Japanese (JA)
• Dutch (NL)
• Polish (PL)
• Portuguese (PT)
• Romanian (RO)
• Russian (RU)
• Slowakian (SK)
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 941
VIM070500-08-CGD-EN-01
Chapter 37 Using VIM Notifications
Language
For a list of languages that are supported by VIM, see Language
on page 940.
Notes
942 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
37.3. Configuring VIM Notifications
2. To exclude another user, click the New entries button in the application tool bar
of the Excluded Receivers for Notifications Overview screen.
User Type
Select SAP User Id or OpenText User ID from the list.
User Id
Enter the user ID to be excluded, corresponding to the selected user type.
Disable Notification
Mark this field with X to disable VIM Notifications emails.
Single Notification
Mark this field with X to have VIM Notifications emails sent only once per
work item instead of multiple times during the notification period.
Language Pref
For a list of languages that are supported by VIM, see Language
on page 940.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 943
VIM070500-08-CGD-EN-01
Chapter 37 Using VIM Notifications
Note: The preferences are set for the currently logged-in user.
Disable Notification
Select this check box if you want to receive no VIM Notifications emails
regarding the SAP inbox or Web Approval.
Clear the check box to receive VIM Notifications emails.
Single Notification (One Time Reminder)
Select this check box if you want to receive only one VIM Notifications
email for a SAP inbox or Web Approval work item.
Clear the check box to receive VIM Notifications emails more than once,
regarding the same work item.
User Language
For a list of languages that are supported by VIM, see Language
on page 940.
944 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
37.4. Maintaining a notification email formatting function module
The notification emails can be sent in HTML format with readable formatting and
invoice data presented in the form of HTML tables. To enable this functionality, you
must set the constant 005 / REM_MAIL_DOCTYPE to HTM. In the /OPT/VIM_8CX50
transaction, you must configure the Email Type to be Internet Email.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 945
VIM070500-08-CGD-EN-01
Chapter 38
In the context of VIM, archiving only considers the VIM data tables of:
• DP invoices
• Reporting data from Central Reporting
• License report data
For a list of tables you can archive data from and a short description of the archiving
process itself, see section 18 “Archiving VIM information” in OpenText Vendor Invoice
Management for SAP Solutions - Administration Guide (VIM070500-08-AGD).
• The data size of the VIM tables has increased to an extent that reduces the
performance of the database.
• The old transaction data is not relevant anymore and not accessed regularly.
Important
OpenText recommends archiving data of the VIM tables only, when the data is
not required in everyday tasks and it is not relevant from auditing perspective.
Make absolutely sure that you run license reporting before you archive data.
Otherwise, you might lose data that is needed for license reporting. For more
information, see section 19.2 “Using the ICC and VIM License Report” in
OpenText Vendor Invoice Management for SAP Solutions - Administration Guide
(VIM070500-08-AGD).
Notes
• Once the data is archived, all reports and transactions will not be able to
show the data anymore. However, VIM Baseline provides a program to
reload the data into the database: Run the SARA transaction, and enter
archiving object /OPT/DOC. On the Goto menu, click Reload.
• There are no known dependencies on data archiving of standard SAP objects
like invoice documents, workflow logs, archive link entries, and so on.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 947
VIM070500-08-CGD-EN-01
Chapter 38 Data archiving configuration
Note: Starting with VIM 7.5 SP4, the archiving object /OPT/DOC is enhanced to
delete VIM change documents (/OPT/VIM_IDXDAT).
1. Use the standard SAP transaction FILE to create the logical file name. The
logical file name is needed in Step 5.
2. To invoke the View Cluster Maintenance screen, run the AOBJ transaction.
Important
Do not change the Structure Definition of the archiving object; see the
following screenshot. This would cause inconsistency between the
programs and the structure.
948 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
38.1. Configuring archiving of DP documents
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 949
VIM070500-08-CGD-EN-01
Chapter 38 Data archiving configuration
5. Assign the logical file name created in Step 1 to the archiving object in the
Logical File Name field.
6. Enter the customizing settings for the archiving object for Archive File Size and
Settings for Delete Program according to your requirements.
Note: You must first archive the DP documents and then archive the reporting
information of the DP documents. If you do not archive the DP documents
first, the data is populated back to the reporting tables again, when the
background jobs scheduled to collect data for the reporting tables are executed.
1. Use the standard SAP transaction FILE to create the logical file name, see Step 5.
950 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
38.2. Configuring archiving of Central Reporting information
2. To invoke the View Cluster Maintenance screen, run the AOBJ transaction.
3. Select Archiving Object /OPT/REP and click .
Important
Do not change the Structure Definition of the archiving object, see the
following screenshot. This would cause inconsistency between the
programs and the structure.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 951
VIM070500-08-CGD-EN-01
Chapter 38 Data archiving configuration
952 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
38.3. Configuring archiving of license report data
5. Assign the logical file name created in Step 1 to the archiving object in the
Logical File Name field.
6. Enter the customizing settings for the archiving object for Archive File Size and
Settings for Delete Program according to your requirements.
1. Use the standard SAP transaction FILE to create the logical file name. The
logical file name is needed in Step 5.
2. To invoke the View Cluster Maintenance screen, run the AOBJ transaction.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 953
VIM070500-08-CGD-EN-01
Chapter 38 Data archiving configuration
Important
Do not change the Structure Definition of the archiving object; see the
following screenshot. This would cause inconsistency between the
programs and the structure.
954 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
38.3. Configuring archiving of license report data
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 955
VIM070500-08-CGD-EN-01
Chapter 38 Data archiving configuration
5. Assign the logical file name created in Step 1 to the archiving object in the
Logical File Name field.
6. Enter the customizing settings for the archiving object for Archive File Size and
Settings for Delete Program according to your requirements.
Notes
• You can archive license report data only if the timestamp of the data is
older than 5 years.
• The Baseline settings provided are for guidance only.
956 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Chapter 39
Rerunning waiting process types
The process types within a wait step can be monitored. You can execute the
corresponding process types again, or you can finish the wait step manually.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 957
VIM070500-08-CGD-EN-01
Chapter 39 Rerunning waiting process types
958 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
39.2. Working with the Monitor list
If you use the Rerun non waiting in background option, the following
search fields are not processed for the execution of the program:
3. When you have finished entering the search criteria and selecting the process
options, click in the application tool bar to display either the dialog result list
or to execute the report in background.
The Monitor list shows all entries for the waiting rules according to your selection.
The Monitor list highlights (in green) all process types where the waiting step has
already been finished.
The Monitor list provides access to the business data and the monitoring processing
of the rerun execution like the following:
1
Wait step created
2
An error occurred during rerun execution, for example the terminating event of
the task could not be processed.
6
Process was skipped / reassigned manually.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 959
VIM070500-08-CGD-EN-01
Chapter 39 Rerunning waiting process types
7
Exception occurred again during rerun processing.
8
Period exceeded and process type was skipped / reassigned.
9
Process type was executed successfully.
Within the list, you can mark one or many entries. For the marked entries, you can
perform the following actions, using the buttons:
960 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-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.
AP processor
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 ERP
system
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 961
VIM070500-08-CGD-EN-01
Glossary
Authorization profiles
The SAP administrator assigns authorizations to the users that determine which
actions a user can perform in the SAP ERP system. These authorizations are
stored in Authorization profiles.
Automation Report
Tool that provides data about automated and manual processing steps of VIM
documents
BAdI
See Business Add-Ins (BAdI).
BAPI®
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).
962 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Glossary
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.
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
Buyer
Person who is in charge of the PO. This role should have authorization to create
and change the purchase order. This role is also responsible for negotiating and
communicating with vendors.
Central 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
Contract agent
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 963
VIM070500-08-CGD-EN-01
Glossary
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.
DocuLink
OpenText™ DocuLink for SAP Solutions enables the archiving, management and
retrieval of SAP CRM or SAP ERP 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).
Duplicate analyzer
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
964 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Glossary
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).
IAP
See Invoice Approval (IAP).
ICC
See Invoice Capture Center (ICC).
IDoc
See Intermediate Document (IDoc).
IE
See Invoice Exception (IE).
Indexer
Indexing
InfoArea
InfoCube
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 965
VIM070500-08-CGD-EN-01
Glossary
enhanced star schema: A large fact table in the middle surrounded by several
dimension tables
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
Information provider
VIM component that enables users to perform coding, approving and rejecting
invoices
Invoice approver
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
966 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Glossary
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).
MM
See Materials Management (MM).
MultiProvider
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 967
VIM070500-08-CGD-EN-01
Glossary
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 ERP 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.
PIR
See Non purchase order (Non PO) invoice (PIR).
PO
See Purchase order (PO).
Invoice that has already been posted in SAP ERP. Only free-form text fields can
be changed. Related documents such as POs or good receipts may be created or
changed to effect the invoice. If the document is not needed, it must be cancelled
( PO invoice) or reversed ( non-PO invoice).
968 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Glossary
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).
SAP module. PO indicates a document sent from a buyer to a seller. The purpose
of the document is to order the delivery of goods or services.
Quantity variance
Situation where the quantity on the invoice is different from the quantity in the
purchase order
Receiver
Person who can create and reverse the goods receipt in SAP ERP
Requisitioner
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 969
VIM070500-08-CGD-EN-01
Glossary
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)
Service approver
Service requisitioner
Summary Report
Swimlane
970 OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide
VIM070500-08-CGD-EN-01
Glossary
Tax expert
Person who advises on invoices that need tax audit. Normally tax department
personnel.
Transformation (TRF)
TRF
See Transformation (TRF).
VAN
See VIM Analytics (VAN).
Vendor maintenance
Person who is responsible for creating and maintaining the vendor master
records
VIM component that gives users a clear data report on their invoices in progress.
VIM Analytics allows to track the documents routed through SAP workflows via
VIM.
VIM Workplace
Tool for VIM super users, which allows users to display lists of their work items
that meet a selection they have entered before. Users also can display work items
of other users and of their team as a whole.
Workflow
SAP Business Workflows can be used to define business processes that are not yet
mapped in the SAP ERP system.
OpenText Vendor Invoice Management for SAP Solutions – Configuration Guide 971
VIM070500-08-CGD-EN-01