Professional Documents
Culture Documents
OpenText Vendor Invoice Management 75 SP3 Release Notes PDF
OpenText Vendor Invoice Management 75 SP3 Release Notes PDF
SAP Solutions
Release Notes
Version 7.5 SP3
Product Released: October 12, 2015
Contents
OpenText Vendor Invoice Management for SAP Solutions .............................................................. 2
Release Notes ....................................................................................................................................... 2
1
Introduction .................................................................................................................................... 6
1.1 Release Notes Revision History ................................................................................................ 6
Installation ...................................................................................................................................... 9
3.1 SAP Prerequisites...................................................................................................................... 9
3.2 Prerequisites on Archive Server (VIMI-4180) ............................................................................ 9
4.11
4.12
Extended Selection Screen for VIM Automation Report and ICC Admin Tool
(VIMI-15264) ............................................................................................................................ 12
4.13
Manual and Automated Processing of Reject from Validation in DP Workflow
(VIMI-4060) .............................................................................................................................. 12
4.14
4.15
Support option Distribution by Amount for multiple account assignment
(VIMI-8082) .............................................................................................................................. 13
4.16
Direct link to VIM document available in exception analysis report (VIMI12684) 13
4.17
Enhancement spot for Process option Change Document Types (VIMI12596) 13
4.18
4.19
VIM-Workplace: Support of Select All function with activated filters for Bulk
Processing (VIMI-15357) ......................................................................................................... 14
4.20
Optional check for update task issues before posting in dialog (VIMI-15480) ........... 14
4.21
Calculation of due date and baseline date according to SAP logic (VIMI14768) 14
4.22
4.23
4.24
4.25
4.26
4.27
4.28
New BDC ID and posting function for Non-PO invoices (VIMI-14371) ...................... 16
4.29
4.30
4.31
4.32
Data Archiving Objects /OPT/REP and /OPT/DOC enhanced (VIMI-12501 +
VIMI-15595) ............................................................................................................................. 18
4.33
Improve Debugging Possibilities in ICC Dispatcher Focus on Extraction
Queue (VIMI-15618) ................................................................................................................ 18
4.34
4.35
4.36
Posting of NPO invoices with different tax codes in the line items (VIMI15786) 20
4.37
4.38
Customization possibility for the WEB Viewer for the Image in the Detail pane
(VIMI-13416) ............................................................................................................................ 21
4.39
4.40
4.41
4.42
5.1.2
Language Package..................................................................................................... 23
5.1.3
5.1.4
5.1.5
7.10
7.11
Customizing ................................................................................................................ 53
7.12
7.13
9.1.2
9.1.3
9.1.4
10.2
10.3
10.4
10.5
10.6
Reversal of NPO invoices posted with new posting function, BDC 42 ...................... 67
11.1.1 Change section 3.2 Accessing Workflows Using VIM Workplace .............................. 68
11.1.2 Change section 7.9 Entering Accounting Information (Approval Portal new
UI) ............................................................................................................................... 69
11.2
1 Introduction
These Release Notes provide an overview of OpenText Vendor Invoice Management 7.5 SP3,
including new features, delivery information, and supported platforms. OpenText recommends that
you read these Release Notes in conjunction with the documentation included with the software
package. If any conflicts exist, the Release Notes supersede the other documentation.
We also recommend that you check the OpenText Knowledge Center
(https://knowledge.opentext.com/) for any patches or documentation updates that may have been
posted after the initial release of OpenText Vendor Invoice Management 7.5 SP3.
Sections Revised
Description of Revisions
12.10.2015
All
Initial Version
19.10.2015
VIMI-14675 added
11 Documentation
Extensions added
30.Nov.2015
07.Jan.2016
11.2
Guide
Installation
15.Jan.2016
11.2.1
Guide
Installation
Revision Date
Sections Revised
Description of Revisions
18.Jan.2016
5.1.5
Business
Center for SAP
Solutions
Caution
Read these Release Notes completely BEFORE applying VIM 7.5 SP3 and follow the
instructions given.
3 Installation
This chapter gives some hints for the installation of Support Package 3 for Vendor Invoice
Management (VIM) 7.5. For the detailed installation description read the VIM 7.5 Installation Guide.
Caution
Any repairs made to the VIM objects will be overwritten by SP3.
4 New Features
OpenText Vendor Invoice Management 7.5 SP3 includes the following new features.
4.2 New VAN (VIMI-14314) Data selection with ABAP CDS views
The new VAN was enabled for data selection with ABAP CDS views. ABAP CDS views can
be used on a SAP system with SAP NetWeaver AS ABAP 7.40 SP05 or higher, independent
of the database system.
Data selection based on SAP HANA views is no longer supported but is replaced by data
selection based on ABAP CDS views.
characteristic only but for combinations of characteristics as well. Finally, it is possible to expand one
or all nodes to display the associated invoice documents.
For details, see the Reference Guide for VIM 7.5 SP3.
/OPT/VIM_VA21 (AP Basic) launches VIM Analytics with a sub-set of selection fields tailored
to an accounting expert. This variant allows searches for specific invoices using invoice data
as invoice numbers, document date, total amount, reference number, etc.
/OPT/VIM_VA22 (AP Advanced) launches VIM Analytics with a sub-set of selection fields
tailored to a higher level accounting expert or special roles as duplicate checker, financial
administrator or tax expert. This variant allows searches for specific invoices using invoice
data as invoice numbers, document date, total amount, reference number, but also process
data, accounting data and due dates.
/OPT/VIM_VA23 (Procurement) launches VIM Analytics with a sub-set of selection fields
tailored to a purchase agent in the procurement department. This variants allows searches for
specific invoices using invoice data as invoice numbers, document date, total amount,
reference number and requisitioner, but also purchasing data.
/OPT/VIM_VA24 (Monitor) launches VIM Analytics with a sub-set of selection fields tailored to
a person who needs to monitor invoices and their processes. This variant allows searches for
invoice data as document date, total amount and reference number, but also accounting data,
due dates, document dates and VIM exceptions.
4.9 Exits for mapping of custom fields for external tax systems
(VIMI-15177)
To map custom invoice fields or change line item data before passing it to the tax calculation
functions, a user exit is now provided by VIM that can be enabled with a new Z-constant:
Product Code 005
Constant name - EXT_MAP_LINE_ITEM External Line item Mapping
If used, the constant value must contain a function module name. The function module interface must
be the same as that of /OPT/VIM_EXT_LINE_MAPPING.
Manual processing: Manual processing means that the documents have to be processed in
the new exception 243 Check Data After Reject From Validation. To enable manual
processing, the forwarding option must be set for entry RJ Reject from validation in table
/OPT/VIM_RETRY.
Automated processing: Automated processing is possible for documents that have been
rejected with Mark for deletion or Mark for rescan.
Forwarding option must be set for entry RJ Reject from validation in table /OPT/VIM_RETRY.
Background option must be activated for entry 007 (Obsolete) or, respectively, 008 (Rescan)
in table /OPT/VIM_REJECTV.
4.20 Optional check for update task issues before posting in dialog
(VIMI-15480)
In system environments where the SAP update task processing is not stable, inconsistency between
VIM and SAP data (that means, invoices are posted, but not registered in VIM) could occur
sporadically, if the user is cancelling the update processing by force.
To prevent such inconsistencies, a new check can be activated if required. It will check the status of
the update tasks before executing a process option calling a dialog posting transaction. If it is enabled
and running updates are detected, a message will be displayed to the user: Update processing is
delayed. Additionally, the inconsistent data situations are avoided in these cases by rolling back the
transaction before the actual SAP posting transactions are started. The check can be activated by
setting Z-Constant 005 / CHK_UPD_TSK_IS_ALIVE to X. Please see VIM Reference Guide for
additional information.
The selection in VIM Workplace was extended by new select option Document ID and Range
selection for date fields and invoice amount:
4.28 New BDC ID and posting function for Non-PO invoices (VIMI14371)
To support several specific posting scenarios and to follow recommendations of SAP, a new posting
function for Non-PO invoices is provided, along with corresponding BDC ID. The new function is using
the MM-LIV BAPI functions to post the invoices. It is using the BAPI
BAPI_INCOMINGINVOICE_CREATE1 if it exists, and using BAPI_INCOMINGINVOICE_CREATE
(the older BAPI version) otherwise.
The new BDC ID delivered with baseline configuration is 42. We recommend to review the new
supported features and limitations of the new posting function before using it. Depending on your
business processes, you may decide to keep the older logic for some scenarios or DP document
types and use the new one for other cases.
While most commonly used account assignment fields are supported by the new function, there may
be discrepancies in the sets of supported fields, compared the new function and the existing BDC 34
and 41. For the complete list of supported account assignment fields please see the documentation of
SAP BAPI BAPI_INCOMINGINVOICE_CREATE.
New scenarios supported by the new posting function:
Posting of net vendor invoices (typically SAP document type KN). Discounts are calculated
automatically and posted to separate line items according to the configuration. Note: the
company code setting Tax base net of discount (which may be used for US company codes)
is still not supported in general.
Posting to tax GL accounts (see separate entry for feature request VIMI-7071).
introduced. Using this parameter, comments can be transferred into the DP workflow and can be seen
in the VIM dashboards.
The comments can be associated to log data entries. When the comments are viewed in the VIM
workflow, the original data (user, date, time) are visible.
Comments with logdata reference will be associated to the related entry. If user, date, time are not
filled in the logdata entry, the current time and user will be used.
Comments without logdata reference will be associated to the Workflow Start entry.
Comments with invalid logdata reference will be ignored.
Each document runs through defined process steps indicated by the inbound handler process.
Process steps consist of a number of service modules. These service modules are integrated
components of the framework that offers the functionality.
Inbound Configuration will replace Incoming Document Handling (IDH) framework and the ICC
Dispatcher framework with the next full version of VIM. Customers doing new VIM implementations
with VIM 7.5 SP3 must use BC Inbound configuration. Customers upgrading to VIM 7.5 SP3 can use
BC Inbound configuration or ICC Dispatcher and IDH. But customers should keep in mind that ICC
Dispatcher and IDH will be discarded in future.
If you plan to use the BC Inbound Configuration, you must activate it as described in the section
Activating BC Inbound Configuration in the Optional Post Installation chapter later in this
document.
Caution
Due to those changes, if you have installed the packages for BC, please note that you
might have to adjust the authorizations for ICC users (see ICC/BCC Administrators
Guide, chapter 5.1.2).
Rejected documents in ICC validation are not processed within DP process (BOB-624)
Bulk processing in Business Center Workplace for Inbound Administration Workcenter (BOB532 / BOB-623)
4.36 Posting of NPO invoices with different tax codes in the line
items (VIMI-15786)
It is now possible to post NPO invoices with different tax codes in the line items like in FB60, which
means, leaving the tax code in the invoice header empty. This requires changes in the customizing.
The new customizing will be delivered in a BC set for the baseline document types NPO_GLOBAL /
NPO_75.
4.38 Customization possibility for the WEB Viewer for the Image in
the Detail pane (VIMI-13416)
In detail pane (plugin), the image was shown in the WEB viewer if the FM
'/IXOS/OA_X_OA_OBJECTDISPLAY_01' was available in the system. If not, the normal viewer was
shown and also the standard ArchiveLink customization of the viewer was not fully supported.
Now, VIM offers flexibility to choose the viewer to be launched from detail pane, including the support
for standard ArchiveLink customization of the viewer.
New Z-Constant 005 / PLUG_IN_OBJECTDISP is introduced, with the following 3 possibilities:
SPACE (default) or ON
Read TOAEX with EXIT_ID = OA_OBJECTDISPLAY_01 AND ACTIVE = X and use the
function module found there (default: /IXOS/OA_X_OA_OBJECTDISPLAY_01).
(Note: Web Viewer integration is delivered in the standard configuration as defined in
TOAEX).
OFF
Native viewer is launched.
(Note: dont use any Web Viewer function in this case).
D240020305028_0000020.PAT
Packages
Please use the files located in
IM_APPROVAL_PORTAL7_5SP3.zip:
IM_APPROVAL_PORTAL7_5SP3.sca,
IM_APPROVAL_PORTAL7_5SP3.sda - either .SCA or
.SDA file should be deployed.
IM_APPROVAL_PORTAL7_5SP3.sca,
IM_APPROVAL_PORTAL7_5SP3.sda - either .SCA or
.SDA file should be deployed.
vimsupplierselfservice.war
Vendor Invoice Management -> Vendor Invoice Management 7.5 -> Support Package 3
-> Business Center for SAP Solutions 10.0
-> Solution Accelerator for Business Center
-> Solution Integration Invoices
-> Solution Integration Invoices - SP2
-> otbcsl03_sp02_0700_001.sar
5.2 Documentation
For OpenText Vendor Invoice Management 7.5 SP3, the following guides are available.
Document title
(Code number)
Available languages
English
OpenText Vendor Invoice Management for SAP Solutions 7.5 SP3 Installation
Guide (VIM-IGD)
OpenText Vendor Invoice Management for SAP Solutions 7.5 SP3 Reference
Guide (VIM-RGD)
Others*
OpenText Vendor Invoice Management for SAP Solutions 7.5 SP1 User Guide
(VIM-UGD)
Note: The User Guide is not updated for VIM 7.5 SP3. User Guide 7.5 SP1 is
still valid. For the latest updates of the User Guide, refer to the section
Documentation Extensions later in this document.
OpenText Vendor Invoice Management for SAP Solutions 7.5 SP3 Scenario
Guide (VIM-CCS)
OpenText Vendor Invoice Management for SAP Solutions 7.5 SP1 User Guide is available in
German, French, Spanish, Japanese, Portuguese, Italian, Dutch, Russian and Chinese with VIM 7.5,
Support Package 2.
Translation Guide VIM 7.0 which provides general information around translation of VIM product:
https://knowledge.opentext.com/knowledge/cs.dll/properties/46423475
Component
Languages
EN
DE
JA
FR
IT
ZH
ES
RU
NL
PT
HU
OpenText Vendor
Invoice Management
UI
Component
Languages
OpenText Vendor
Invoice Management
RO
TR
PL
CZ
SK
UI
UI
UI
UI
UI*
Note
VIM 7.5 SP3 provides translations in other languages than English only for end
user screens (transactions and reports using in a production system by nontechnical users). Translation is not provided for configuration screens.
Language packages for the supported languages are available in the OpenText
Knowledge Center in the corresponding patch area.
The installation package for VIM 7.5 SP3 does not contain full language support
except for English and German.
Compatibility
Matrix VIM 7.5
The following table lists the supported combinations of the Web Approval Portal (OAP) and the VIM
backend versions.
VIM 7.5
VIM 7.5 SP1
VIM 7.5 SP2
VIM 7.5 SP3
Note
VIM 7.5 OAP is not supported in combination with VIM 6.0. The new User Interface
(new UI) is available since OAP 7.0 SP2 and the same Interface is used in OAP 7.5. It
is using a new web application framework to support HTML5 and the latest web
technologies.
It is possible, in certain situations, to use OAP 7.5 with VIM 7.0 (ABAP) backend. In
case you need such mixed system landscape for your project, please contact
OpenText to verify whether your specific versions combination is technically possible.
Some of the features are partially supported, recommended to have completely
supported stack.
IE9
IE10
IE8
IE11
MS
Edge
FF
Chrome
Safari
OAP 7.5
Note
To support HTML5 and the latest web technologies we are using a new web application
framework in VIM 7.5 which doesn't support old browser versions like Internet Explorer 8
and below.
Firefox is supported for version 17 and higher.
Google Chrome is supported for version 22 and higher.
Safari is supported for version 5.0 and higher.
Microsoft Edge:
Microsoft Edge has been tested on SAP standalone WAS 7.4, but not completely tested
on SAP Netweaver Portal 7.4. Please note the general recommendation from Microsoft:
We also recommend that you upgrade to IE11 if you're running any earlier versions of
Internet Explorer. Microsoft Edge lets you continue to use IE11 for sites that are on your
corporate intranet or that are included on your Enterprise Mode Site List. You must use
IE11 to run older, less secure technology, such as ActiveX controls".
OAP 7.5
The following table lists the supported combinations of the Operation Systems for Mobile Services
and the Web Approval Portal Versions.
Note
In general, you can view the Mobile Approval Portal inside the browsers on all kind of
Android devices. Due to the diversity of physical Android devices, OpenText cannot
guarantee 100% compatibility on all functionality that the Mobile Approval Portal offers.
Please consider the list of all supported browsers also.
7 Fixed Issues
The following issues were fixed.
VIMI-14741
The exchange rate value is not taken from the goods receipt when creating a PO parked document.
VIMI-14771
PO invoice autoposting fails with error message "You cannot process conditions for delivery costs
(Message M8 524).
VIMI-14852
Company code data is not populated on new indexing screen after pressing ENTER.
VIMI-14860
Tax lines in SAP document look different when posting with VIM compared with SAP FB60.
VIMI-14871
Subsequent debit & credit not working for parked PO with BDC 11 and 28.
VIMI-14876
If mandatory fields are not populated in the indexing screen, some functions like Obsolete cannot be
executed. Now the following functions can be used in such cases: View Image, Obsolete,
Rescan, Display rescan reason, Help. In comparison with the old pre-7.0 indexing screen, due to
screen design constraints, using any process options (for example Change document type) requires
all mandatory fields to be populated.
VIMI-14912
When using the Service Entry Sheet button in the dashboard, the PO number from the indexing
screen is not pre-populated in the called transaction ML81N.
VIMI-14925
Individual payment terms are ignored when ZTERM is empty.
VIMI-14940
If payment terms are entered manually in the indexing screen (not using a search help), it is possible
to enter values that are not relevant for vendor invoices. No proper validation is made in this case.
VIMI-14968
In the function module /OPT/VIM_DETERMINE_PROC_406, while doing the tolerance check, it is
adding the tax amount to the gross amount instead of checking against the gross amount only.
VIMI-14978
Empty withholding tax amounts are posted incorrectly if you post a Non-PO invoice online or in
background (using batch input BDC ID 41). The amount is posted as zero, while it has to be posted
according to customizing.
VIMI-15016
Enhanced warnings in indexing screen when processing posted invoices. New check function
/OPT/VIM_BL_OPTION_CHCK_POSTED to hide select options in indexing screen for posted
documents.
VIMI-15046
Auto calculate flag is not set, as per Doc Type configuration, when DP is created.
VIMI-15100
Business rule Validate bank details was not correct for countries where bank key and bank number
are not equal.
VIMI-15103
Negative value for net amount field causes short dump when displaying DP document.
VIMI-15119
Balance of DP PO document is recalculated incorrectly on the indexing screen whenever scrollbar (up
or down button) is used, after Match All is done.
VIMI-15121
No explicit alert to user, when posting fails in background through process option (ex: Post PO
Invoice). Thus, user is confused if posting was successful or failed.
VIMI-15125
Performance issues while reading from table /ORS/APPR_LOG in the indexing screen.
VIMI-15149
Function module /OPT/VIM_DETERMINE_PROC_165 (Business Rule Wait for GR - Enhanced
Check (PO)) is considering the G/L account lines when checking the document data.
VIMI-15151
Document type determination did not work correctly, when check type F (PO related) was used, and
a delivery number was given as input, but not a PO number.
VIMI-15157
Payment terms specified in the input screen of the OCR simulation tool (Tx /OPT/VIM_7AX2) get
overwritten.
VIMI-15169
Posting of service POs is not possible, because there is a mismatch between LFPOS and
SHEET_ITEM fields. This may happen in scenarios without service based IV depending on line item
input.
VIMI-15200
Default posting date is overwritten when document status changed from Extraction completed (i.e.
73) to Ready for validation (i.e. 74).
VIMI-15220
When obsoleting a DP document that was used to post a valuated GR resulting into GRs FI
document number to be recorded in the DP document (bug VIMI-13559, fixed in VIM 7.0 SP5, 7.5
SP1), the DP document status is not set to Obsolete but to Posted.
VIMI-15221
The Edit OTV button is active in the indexing screen even if the vendor field is set to display in the
index screen fields configuration.
VIMI-15234
The obsolete reason text "Vendor sent in replacement vendor" should apparently read as "Vendor
sent in replacement invoice" in English.
VIMI-15239
The Submit button should not be available for invoices opened in display only mode.
VIMI-15241
Performance optimization for PO BAPI. Additionally, a new Z-Constant 005/
NR_ALLOWED_LINEITEMS is introduced to restrict the number of line items for background posting.
This can avoid workflows stopping in status Create Document due to background posting time outs.
If the number of line items exceeds the customized value, the workflow is sent to the processor and
can be posted manually.
VIMI-15244
Old indexing screen line items are getting duplicated after changing them while pressing the Enter
button.
VIMI-15246
Baseline date is not updated in /opt/vim_1head table for old indexing screen.
VIMI-15257
It was not possible to set the VAT_AMOUNT field to Display Only using the index header screen
configuration.
VIMI-15259
IBAN number passing from ICC is overwritten.
VIMI-15271
Posting a document in background for a CPD vendor via BDC infrastructure (for example BDC 41)
fails with error message 00 347 'Field INVFO-ZFBDT is not an input field'.
VIMI-15275
In some scenarios of PO processing with multiple accounting, the line items in /OPT/VIM_1ITEM were
overwritten after posting with wrong amounts and quantities.
VIMI-15307
Workflow runs into error state when one removes company code and applies business rules.
VIMI-15311
Logic module for payment terms determination did not consider credit memos.
VIMI-15313
Changed By / Changed On" history is missing in comments log.
VIMI-15317
Parking an NPO invoice with BDC 14 (Batch input) failed with error message 00 349 Field INVFOLZBKZ does not exist in the screen SAPMF05A 1100.
VIMI-15321
SES partial invoice is not posting in background by using BAPI (BDC ID 6).
VIMI-15337
When a CPD vendor is used in an NPO invoice and vendor language key is entered in CPD data,
background posting fails with the error ISO code XX has not been assigned a language key.
VIMI-15338
When trying to capture an indexing line item field using Single Click Entry, the captured value is not
transferred to the corresponding screen field.
VIMI-15353
Country specific fields (NFe data) are not displayed on the Basic Data indexing screen.
VIMI-15360
The button Display vendor uses transaction FK03 to display the vendor, so the purchasing
organization data are not available. This was changed now and XK03 is used when appropriate.
VIMI-15365
Table /opt/dt_br_wait is not getting updated properly when new wait process option has triggered.
VIMI-15367
Enabled data dictionary Log Data changes flag for table /OPT/VIM_2HEAD causes performance
overhead.
VIMI-15390
Negative withholding tax amounts are showing for credit memos and SAP documents are posted with
wrong posting key.
VIMI-15400
System shows the error message like Error: Characteristic value XXXXX does not exist for
characteristic Profit Center even when the correct profit center is entered in the profitability segment
pop up in approval portal.
VIMI-15402
If an invalid WBS element is entered in the indexing screen, an error message is displayed and it is
possible only to exit the dashboard correcting the value is not possible.
VIMI-15408
Down payment net amounts are posted incorrectly.
VIMI-15436
When a DP document is referred to some role other than the initial actor of the current exception, and
the rerun rules job ends the work item, the document is sent to the initial actor role and not to the role
to which it was referred to.
VIMI-15455
If the currency conversion from some currency to the local currency is not maintained in SAP and that
currency is entered during ICC process, system is not allowing to open the indexing screen.
VIMI-15458
When posting an invoice online in VIM via MIRO, the proposal line is not highlighted for items where
no quantity is needed (limit POs, service POs without S-based invoice verification).
VIMI-15475
Comments entered when bypassing business rules are displaying without the date, time and user
name entered by the comments.
VIMI-15463
Display scheduling agreement with ME33L does not work properly when the order number is less
than 10 digits.
VIMI-15494
If company code is set up to use net amount as discount base amount and NPO invoices are posted
in background through BDC ID 34, the discount base amount has an incorrect value. This patch
disables the setting of calculate tax (BKPF-XMWST) in the posted document by the posting function
used by BDC 34 in a standard configuration. The flag should not be used when posting through BAPI,
but in case your process requires that flag at all times, please set the Z-constant 005 /
SET_TAX_CALC_FLAG to X (Note that it results in incorrect value of the discount base amount if its
set to net).
VIMI-15503
Short dump BDC_ZERODIVIDE happens in FM /OPT/VIM_BDC_NPO_FILL_WT_DATA when there
are more than one line items in the document and you try to change the vendor number in the
indexing screen.
VIMI-15522
You have set up some processes to wait/rerun mode. When you execute the rerun rules report
/OPT/DR_BR_WAIT, the waiting work item ends and shortly after the workflow runs into an infinite
loop creating many process control steps and finally stops with an error.
VIMI-15524
When the DP document type is changed, withholding tax is not re-calculated.
VIMI-15527
The new extended recipient selection screen used in DP "refer" type option does not work correctly
when the "Override Resolved Actor" option is selected in the process option configuration.
VIMI-15531
Wrong ISR reference number can be posted in background.
VIMI-15552
Missing timestamp / user for the comments entered before upgrade.
VIMI-15555
A document could be imported for training at the ICC only if it had been validated at an ICC validation
client.
VIMI-15584
Some of the SEPA-related check in business rule Validate bank details were not appropriate and had
to be modified or removed.
VIMI-15587
Posting of an invoice in background fails in the following case.
Posting date setting should be current date. Invoice process stopped with an exception in the
past.
The exception is cleared without touching the invoice so that the posting date will be in the
past date itself.
VIMI-15590
Old customer sort interface for validation queue delivers documents, if it is called for a validator who
has no documents assigned.
VIMI-15617
Missing authorization checks allow displaying vendor data or changing a vendor in DP dashboard
when it should not be allowed (with authorization object F_LFA1_BEK).
VIMI-15644
Auto Calculate tax flag is not set by default while it is maintained in document type settings in case
of Non-OCR scenario.
VIMI-15646
Updating the /OPT/VIM_2HEAD table is spending much time on a select in EKKO.
VIMI-15651
The new DP document ID is not created when process option delete and re-enter is used for a
parked NPO invoice and the document is posted immediately (while re-entering).
VIMI-15670
The invoice image is not copied to the newly created DP document when process option of deleting
and re-entering a parked NPO as PO is executed.
VIMI-15673
The image and the Expense type is not copied to the newly created DP Doc ID when the process
option Delete and Re-enter as Non-PO invoice is used and a credit memo is posted instead of an
invoice.
VIMI-15690
The Requisitioner ID is not updated according to the email ID when the email ID is changed on
validation stage.
VIMI-15700
The posting date is not assigned as per the characteristic specific attributes, when processing an
invoice through ICC channel.
VIMI-15701
You are processing an invoice created with a service PO, which has the flag SR-IV set but does not
have GR-IV flag set and does not have SES entered. When VIM attempts to post the invoice in
background with standard VIM BDC ID 6, it fails with the error message Service number entered
(0000000000) does not exist.
VIMI-15713
When you park a document (through MIRO, MIR7) and the Z-constant for default DP document
type (005 / DOCTYPE_PO) is not maintained, a short dump is generated by the system.
VIMI-15740
Valid extended withholding tax lines are prefilled with withholding tax type. If you entered a
withholding tax amount in empty lines (with no withholding tax type filled), a dump could occur.
VIMI-15755
ISR number in wrong format is ignored.
VIMI-15778
Invoice referring to a service PO with multiple account assignment cannot be posted in background,
when SR-IV check box is not enabled in the PO.
VIMI-16019
Tax amounts are not correctly posted in NPO invoices if currency with no decimals is used and
automatic tax calculation is enabled.
VIMI-15251
Tax amount is not displayed in the format according to user preferences.
VIMI-15254
A short dump with exception CX_SY_CONVERSION_NO_NUMBER could occur, when coding was
done with amounts using more than one formatting characters (decimals or thousands separators).
VIMI-15308
Incorrect comment icon in approval history log.
VIMI-15312
When user enters * in the last line to automatically generate the remaining amount for that line, the
balance amount is entered instead.
VIMI-15325
Short dump CONVT_OVERFLOW occurs when performing a custom action during invoice approval, if
the invoice amount is very high.
VIMI-15354
When doing approvals with a parked NPO invoice that has multiple line items, balance and batch
input related errors are being displayed when attempting to approve.
VIMI-15360
In the PO Approval dashboard balance amount is not displaying in proper currency format for
currencies like TWD, JPY.
VIMI-15441
In approval notification mail, the standard text is not aligning in HTML format.
VIMI-15537
When the user is added in COA from /OPT/AR_COA and this user already has SAP substitutes, the
SAP substitution entries for that user are getting deleted.
VIMI-15557
Extended withholding tax is wrongly calculated if vendor has several withholding tax types assigned
and at least one withholding tax type is tax based and document contains no tax.
VIMI-15571
When a requester (as a coder) enters line items for a DP document that had no lines originally and
tries to approve, next approver is not determined correctly due to incorrect entries in
/OPT/AT_APPR_HIS table.
VIMI-15654
COA change history is not showing all the changes, when selecting a line in COA tab and clicking on
the button Display Changes".
VIMI-15696
Buffer option of level based approvals is not working with combination of Skip COA and Substitutes
inherit COA.
VIMI-15707
Item amount for PO invoice doesnt show up on approval screen.
VIMI-15736
Chinese translation in indexing screen for Refer Back is missing, translation for Add Comments is
wrong (cut off). Note: please see also the section Known Issues regarding translation problems.
Approval Portal). If this check box is cleared, the first invoice details are not loaded automatically on
the launch of the application.
VIMI-15228
Web Approval Portal screen does not use full available screen space.
VIMI-15306
History, Search-Pop-Up too big for lower resolution.
VIMI-15327
Next Approver displayed in all lower case characters.
VIMI-15363
Email ID is truncated in search help.
VIMI-15378
Using lower case company code in OAP leads to the error Entry XXXX XXXX does not exist in
SKB1 or Entry XXXX does not exist in T001 (check entry).
VIMI-15382
Referral Pop-Up hangs.
VIMI-15391
Tax jurisdiction code is not being determined from work order.
VIMI-15411
The functionality of maintaining the account assignment for parked PO invoices is missing in the
Approval Portal (7.0 and 7.5 versions), compared to the older VIM versions.
To use the new function, the following fields must be maintained in the item fields configuration with
proper COBL sequence and length settings in VIM approvals customizing:
QUANTITY, PO_CODING_SEQ, INVOICE_DOC_ITEM, PO_ITEM and PO_NUMBER.
NOTE: also, see the list of known problems in the Known Issues section.
VIMI-15449
Approval Portal - Disable or allow different servers for cross-site scripting (CSS)
Introduced a new option in Admin Configuration tab to enable/disable the security features
implemented to prevent security vulnerabilities like CSRF (Cross Site Request Forgery) and Click
Jacking. Note: By default this option is disabled.
VIMI-15497
Forward Invoice - First / Last-Name not separated by space after selection
VIMI-15553
Approval Portal new UI, value of business area of invoice header cannot be displayed.
Approval Portal now supports the field GSBER (Business Area) in Invoice Header section.
VIMI-15571
After upgrade to VIM 7.5 SP2 (both ABAP and portal) approval not working correctly. Invoices are
routed to wrong approvers (coders/requesters).
VIMI-15576
Invoice posting to a VAT GL account - enhance portal screen
Approval portal now supports the field TAX_BASE_AMT in Cost assignment section.
VIMI-15633
When a cost center is entered in lower case, it is not converted to upper case after saving or
performing balance check.
VIMI-15687
Tax Code - Technical name is not displayed for RMRP and DP PO invoices.
VIMI-15688
PO Approval in Web Approval Portal - not possible to show fields & values only in detail view
VIMI-15855
When forwarding an invoice in Approval Portal, list of "recent users" in dropdown box is always empty.
VIMI-15302
User exit to provide data for ICC metadata does not work for documents coming in through IDH
standard processing module 'OCR'.
VIMI-15303
Email channel with OCR does not work. DP Documents are created but have the wrong status 56
Sending data to ICC dispatcher instead of 01 Scanned.
VIMI-15316
Archive document type is not getting passed on from PDF rendering into the index data.
VIMI-15477
Field ACTION_TIME within the table /opt/vim_1head shows wrong value if XML timestamp stored in
Brazilian NFe documents that have an additional time zone.
VIMI-15508
ICMS, IPI and additional taxes not getting extracted in the XML channel for Brazilian NFe documents
and therefore cant be mapped to the VIM item table.
VIMI-15675
IDH document in status Mapping Error could not be processed in the IDH admin tool. Now the
options Discard Image and Change Status are possible.
VIMI-15406
Process option Pay-As-Invoiced is not displayed for some blocked invoices.
VIMI-15484
Problems with confirmation popup after executing the process option Submit for Approval in
NPO/PO parked dashboard:
Clicking the CANCEL button still keeps the work item with the AP_PROCESSOR inbox.
Now the confirmation popup does not appear when approvals are started.
Due to uncleared memory variables work items are not getting completed randomly.
VIMI-15615
If a user with the assigned role Info Provider enters the parked dashboard and executes any
process options other than Refer, then exits the dashboard and enters it again, all Refer process
options are missing.
7.8 VIM Analytics (new VAN) Report and VAN Liability Report
VIMI-14314
Up to VIM 7.5 SP2, SAP HANA (graphical) views have been the means of choice for the new VAN
report running on a SAP HANA database. In case of mass data, this proved not to be an appropriate
approach. This is why the new VAN was now enabled for ABAP CDS views. Data selection based on
ABAP CDS views support all types of databases, not only SAP HANA databases, and is supported for
SAP systems with SAP NetWeaver AS ABAP 7.40 SP05 or higher.
Note: Data selection based on SAP HANA views is no longer supported but is replaced by data
selection based on ABAP CDS views.
VIMI-15351
Performance improvement of VAN Initialization report
VIMI-15368
Field Invoice Type Text in the result list was empty if field Invoice Type was not displayed.
VIMI-15396
Wrong status in new VAN report for cancelled invoices (NPO scenario)
VIMI-15404
VAN Initialization report runs into endless loop if test mode and extended display options are checked
when running in background.
VIMI-15495
Run time was lost on selection from EKKO table if a purchase order related field was displayed in the
result list (purchase order number, purchasing document type, purchasing document category,
description of purchasing document type, purchasing group, description of purchasing group).
VIMI-15496
Field block_pa is not updated if block is changed outside of VIM Workflow (Ex: FB02) even after
running SYNC_JOB.
VIMI-15517
Selection field Transaction/event was moved down to avoid issues with mouse wheel scrolling after
opening VIM Analytics.
VIMI-15586
Depending on the SAP basis version, CDS view /OPT/VVA2_USFB_V could not be activated
because of error message Select lists with unions must have the same name; insert aliases.
VIMI-15635
In new VAN report Paid on field is not displayed for PO invoices.
VIMI-15636
New VAN report is triggering a short dump when choosing layout from the selection screen when
layout contains sort and filter options also.
VIMI-15836
When selecting by accounting data, as for example the G/L account, together with the Document
Processing Number, deleted PO based invoices were not found.
VIMI-15863
The result list of the new VAN report provides two output fields Transaction/Event and
Transaction/Event Text. Both fields were empty in case of down payments.
VIMI-16012
Fixed error Object Name is too long when trying to implement enhancement spot
/OPT/ES_VIM_VA2_DATA_PROV_BE_S in class /OPT/CL_V_VA2_DATA_PROV_BE_STD, method
PREPARE_OUTPUT_DOC_HDR for VIM Analytics (7.5).
VIMI-15369
/OPT/VR_A_AGGREGATION lacks proper commit handling for large data volumes.
7.11 Customizing
VIMI-15381
Exception Validate Bank Details was placed at the end of the sequence of processing types, which is
not appropriate. Baseline setting has been changed for NPO_GLOBAL/NPO_75 from 445 to 125, and
for PO_GLOBAL/PO_75 from 565 to 165.
In VIM customizing, DP Process configuration BDC Procedures, create a new BDC ID 42 that is
using the function /OPT/VIM_NPO_POST_VIA_LIV with options as shown below.
Mark the standard document type for NPO invoices (NPO_GLOBAL for VIM 7.0 and NPO_75 for VIM
7.5, and possibly other document types that you use) and add a new field record in the index item
configuration as shown below:
Mark the standard AFS ID 10, and click Maintain Invoice Detail Fields:
Add a new entry for tax base amount field as shown below:
Add two more entries with the same content for devices SAPGUI and WEB, but with field status
Input. Save your changes.
Note: Translated texts for those fields labels are provided in the translations transport delivered with
this SP. If you are using your own AFS IDs, you need to create similar mapping entries and create
your own translations for languages other than English.
Double click Maintain Coding Fields Mapping at the left. Add two new entries for field
TAX_BASE_AMT and TAX_BASE_AMT_D as shown below:
Mark all three existing entries for field TAX_BASE_AMOUNT_B (with AFS ID 10) and create their
copies for AFS ID 0. Example:
Mark two entries with field names TAX_BASE_AMT and TAX_BASE_AMT_B (with AFS ID 10), and
create their copies with AFS ID 0. Example:
8.6 Posting of NPO invoices with different tax codes in the line
items (VIMI-15786)
To support this, two customizing changes are necessary.
Check the document type configuration for your NPO document types.
In the index header configuration, set the field status for the field TaxCode to Input.
Check the transaction data for your BDC procedures for NPO posting.
8.7
To solve the problem of incorrect tax and balance calculation in specific situations for Brazil and
Indian invoices, VIM now provides a user exit that can be used depending on project needs. A
standard implementation is provided as the function module /OPT/VIM_GET_TAX_AMOUNT.
Maintain the function module in the table /PTGWFI/Z_CONST as shown in the following screen
shot.
In case you would like to implement your own logic, please use the following function module
interface:
Change the status of the documents to Discarded using the Discard Image option in the
IDH admin tool (Transaction /OPT/VIM_7AX8).
Use the new Z-constant ICC_VA_RJ_FWD to set a start date for the move. Documents older
than this start date will not be moved. You can edit the constant value in the Advanced
Configuration node or using the transaction /OPT/VIM_ICC_ADV_CFG.
The program creates a transport, and you can use the transport to distribute the changes to the other
systems.
You can use the program to distribute the new process type from template
-
9.3
If you want to use BC Inbound Configuration, please make sure that you have installed the necessary
components (see 5.1.5)
To activate the BC_INBOUND configuration, add the Z-constant 005 / BC_INBOUND as follows:
10 Known Issues
The following known issues exist in this release.
VIMI-15971
Auto Forward functionality is not working.
If it does not solve the problem, the following trick can help: Open the affected screen in Transaction
code se51, menu Goto -> Translation. Check if correct translations are available for the affected
strings. For each affected string do the following:
-
Go to the string, capture the translation into the clipboard. Be sure to capture only the
characters, no additional spaces.
Make the line empty, save with translation fields empty.
Insert the text again. Save.
Do this for all strings that are not correctly presented. After that, return from the translation sub screen
and activate the screen.
If it does not help, please refer to SAP Notes 1307719 and 1508122 or create an OSS to SAP
(component BC-CTS-LAN).
11 Documentation Extensions
11.1 User Guide
The User Guide will not be updated for VIM 7.5 SP3. The User Guide VIM 7.5 SP1 is still in use.
However, there are some changes necessary. Please see them in this section.
Execute
Resubmit
End Resubmission
Reserve
Unreserve
This feature is only available for simple approvals (header based). For the level based
approval workflow, the feature is not available.
You can upload a maximum of 50 line items. More than 50 line items are not supported.
User notes
For an invoice, a user should only upload the coding template that was downloaded from that
invoice.
The 1st row of the downloaded coding template is hidden. It contains the column metadata.
The 2nd row displays the column titles. To properly upload the coding template, users should
not edit or delete these two rows. Users should only do the coding from the 3rd row on.
The coding templates feature is applicable only for coders.
12 Contact Information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1
Support: https://support.opentext.com
Knowledge Center: https://knowledge.opentext.com
For more information, visit www.opentext.com
Copyright 2015 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not
exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names mentioned
herein are property of Open Text SA and/or Open Text ULC or other respective owners.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.