VIM_23.4_Release_Notes_for_Invoice_Solution (2)
VIM_23.4_Release_Notes_for_Invoice_Solution (2)
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 OpenText My Support for any patches or documentation updates
that may have been posted after the initial release of this product.
For additional details on release names, please refer to SAP Note 2339256.
The technical release number for Vendor Invoice Management 23.4, designed for SAP S/4HANA 2023
and set to launch in the fourth quarter of 2023, remains "23.4." The release name for this package is
"23.4 for SAP S/4HANA".
This section provides an overview of Vendor Invoice Management for SAP Solutions 23.4.
Note
OpenText Vendor Invoice Management by SAP Solutions 23.4 supports
SAP S/4HANA 2023.
Future SAP S/4HANA versions will typically be supported by the VIM Update
(Support Package) directly after release of the new SAP S/4HANA release.
SAP S/4HANA Cloud, essentials editions (ES) are not supported by any
version of OpenText Vendor Invoice Management by SAP Solutions.
Software solutions like VIM cannot be or not be GDPR compliant. Every customer using SAP S/4HANA
and VIM is responsible to provide GDPR compliance in their organization.
Several VIM features and additional details listed in product documentation can help clients to achieve
GDPR compliance.
These improvements were achieved through the implementation of a new algorithm that takes into
consideration the newly introduced field weights and confidences. This release offers the ability to
customize confidence for improved matching results, based on the following criteria:
• Confidence-based field matching calculation, which includes full and partial field matches.
• Confidence-based item matching calculation, taking into account the weight of fields to match,
the number of fields to match, and the number of fields requested to match.
• A confidence threshold for item matching.
Customers have the flexibility to fine-tune the matching process by configuring higher weights for
specific fields like material text, adjusting matching confidence levels for partial matches, and setting
threshold values to ignore matching pairs with low confidence.
• Invoices with Purchase Order numbers that have already been used in other invoices not yet
posted, offering options for both background and screen matching with warning popups.
• Large invoice documents, providing choices for background and screen matching with warning
popups.
Furthermore, the matching process can be logged and analyzed, and customers have the ability to
adjust configurations based on the matching result report.
• Multiple Service Entry Sheets (SES) per PO item and multiple Goods
Receipts (GR) per PO item may yield fewer matching results compared to
older versions (up to VIM 20.4 SPS5).
• Large document handling might not fully populate logging tables or
analytics reports.
The IES Extraction Dashboard provides the key figures (KPIs) of the extraction process in the Inbound
phase based on the feedback results. Instead of providing the key figures for each inbound process,
the dashboard provides the key figures aggregated per capture profile ID or other inbound parameters.
For customers who are currently utilizing the central electronic mapping utility in the invoice solution
and are planning to upgrade to the latest release, a data migration utility has been provided to
facilitate this process. By executing the migration program, you can significantly reduce the manual
effort associated with copying existing data from /OPT* (Invoice solution) tables to /OTX* (foundation
solution) tables within the e-invoicing solution. This approach not only minimizes the potential for data
entry errors in /OTX tables but also allows for options to modify or overwrite the existing entries in
/OTX tables.
To initiate the migration tool, utilize program /OTX/PF14_P_MIGRATE_DATA through the T-code:
/OTX/PF14_MIGRATE.
For a comprehensive understanding of this tool, please consult the "One-time administration tasks"
chapter in the Administration Guide for Invoice Solution.
Note
It is crucial to note that any future enhancements or new developments pertaining
to the e-invoicing solution will exclusively be carried out within the /OTX* objects.
We highly recommend transitioning to this approach, as the older /OPT XML data
model is slated for obsolescence in future iterations.
The resulting PDF output simplifies the reading for the end-user compared to more technical file like
XML, enhancing the usability of your electronic documents.
Note
For a deeper understanding of PDF Visualization, please consult the "Configuring
PDF Visualization" chapter within the Configuration Guide for Foundation, as well
as the "Visualization of XML Invoices" section in the Scenario Guide for the
Invoice Solution. These resources provide comprehensive insights and
instructions on the topic.
VIM provides support to send these rejection codes back to invoice issuer, along with optional
comments for customers of VIM integrated with SAP Document and Reporting Compliance.
For more details, refer to Chapter “Extension of eDocument feedback functionality to support rejection
codes” of Scenario guide for Invoice solution.
This functionality is validated with 2 new business rules relevant for this solution.
• When the tax rate is zero and ARN is not entered on item.
• When the tax rate is non-zero and ARN is entered on the item.
Note: The value passed/entered in the ARN field will not be validated in VIM.
For more details, refer to Section “Italy” under Chapter “Scenarios for special countries” of Scenario
guide for Invoice solution.
With a new user experience, we deliver six predefined analytical cards with different views such as
Donut chart, Column chart, List card, Table card and Link List card.
The user can use the cockpit to make a system-guided and intelligent decision which invoice workflows
to focus on, i.e.: urgent invoices by due date”, “top exceptions”, etc…
Note
• Fiori Cockpit for Accounts Payable is delivered as a preconfigured Fiori tile
with six predefined cards.
• It´s only available from S4HANA 2023.
Note
To ensure the inclusion of leasing invoices in the aforementioned Fiori apps, it is
essential to configure and enable approvals for the leasing document types,
REC_S4 and/or REC_75.
• Indexing Invoices
• Process Blocked Invoices
• My Touched Invoices
• Completed Invoices
Note
• The General Team View definition is configured using the T-code:
/OPT/VIM_WP_TMG
• The Personal Team members are configured using the Invoice Workplace
in the SAP GUI, T-code /OPT/VIM_WP
Note
• All the features on the desktop version are now made available on the
mobile app except for upload coding.
For more details refer to Chapter “Redo Role Resolution utility” of VIM
Administration guide.
With the new enhancement, sender email id (shared or individual) can be configured based on
company code.
Note
For more details refer to Chapter “Maintain the Sender Email Address” of
Configuration guide for Invoice solution and Chapter “Returning invoices to the
vendor” of User guide for Invoice solution.
Limitations:
• SCE activation will not be controlled, if DP items are being added/deleted in the indexing screen
while SCE plugin is already active. The evaluation is done if a different plugin is chosen and
then SCE button is clicked again.
• The last plugin chosen/clicked will be set as default and saved to database. Next DP will show
this plugin as default (existing logic). If any plugin other than SCE was last executed, SCE will
not be evaluated when indexing screen loads (in PBO).
For more details, refer to Chapter “Z constants for product code 005” of Reference
guide and Chapter “Using the Single Click Entry feature” of User guide for Invoice
solution.
Note
• N/A
The following features have been deprecated in this release:
• Supplier Self Service Lean Variant app is deprecated and replaced with Full Variant app.
• Support of the e-invoice processing with a transformation is deprecated and customers can
use new parsing class.
• Supplier Invoices node in VIM Central (BC) workplace for invoice processing tasks. VIM Invoice
Workplace (/OPT/VIM_WP) provides more features for invoice processing. Note that IES
Extraction Analytics is fully supported and must be used from the Supplier Invoices node in VIM
Central (BC) workplace.
• Enter Cost Assignment Simple Fiori app is not supported and has been replaced with Enter
Cost Assignment Advanced Coding Fiori app.
• Ariba Integration with Ariba Business Network Integration adapter (BSAO). SAP Integration
Suite, managed gateway SAP Business Network (formerly known as Cloud Integration
Gateway, CIG) is the supported option to integrate with Ariba Network. Note that SAP ends the
support of BSAO on 31st of December 2023.
• VIM KPI Dashboard. Equivalent features can be found in Central Reporting and can be
augmented by using the data provided through delivered BW data sources to build custom
reports.
• Approve Invoices Full Screen List Fiori tile is deprecated, and customers can now use full
screen list view in Approve Invoices App from Invoice Approval Workplace.
• Older XML visualization (simple and complex) is deprecated for e-documents and replaced
with new PDF visualization.
As a best practice it is recommended to use FIORI Capture Validation Workplace app for SCE instead
of Windows Validation client.
3 Downloads
Downloads for Vendor Invoice Management for SAP Solutions are available on My Support.
Mandatory packages
For implementing the support package VIM classic mode 23.4 including Fiori apps, the following
packages are mandatory:
Component Description Package file name
otbcsl30 _006.SAR _81610_
OTVIMINV OpenText VIM S/4 Invoice OTVIMINV_02023_001.SAR
106.sar
Packages and Transports for Additional Scenarios
Several additional packages are delivered along with the product. This section lists those that are
updated and provided with VIM 23.4. A complete list of all additional packages can be found in VIM
23.4 Installation Guide.
The following packages are required to implement the VIM Approval Portal for invoice coding and
approval based on SAP NetWeaver Java and SAP NetWeaver Portal:
Component Packages
Approval Portal based on JCo3.1 im_approval_portal23_4_sp0.zip
Java1.8
NOTE: SAP offers mainstream maintenance for SAP NetWeaver Java until the end of 2027.
OpenText supports VIM Approval Portal only within the timeframe of mainstream maintenance for
SAP NetWeaver Java, that is, until the end of 2027 as well. For reference, please see SAP note
2912858. OpenText recommends customers to replace VIM Approval Portal by VIM Fiori Apps: Enter
Cost Assignment Advanced and Approve Invoices apps.
The table below lists other delivered files, specifying the related deployment scenario.
Fiori Launchpad
content transports
for on-premise
invoice solutions-launchpad content.zip D46K900901 Front end All scenarios
Fiori perspectives
layouts
invoice solutions_fiori_perspectives_layouts.zip D66K923469 [a] Back end All scenarios
Used for: Fiori
invoice apps on-
premise scenario
Fiori perspectives
customization
invoice solutions_fiori_perspectives_customizing.zip T8FK900083 [a] Used for: Fiori Back end All scenarios
invoice apps on-
premise scenario
Send Back Action
Dialog
Invoice solutions_fiori_approvals_sendback.zip D46K900897 Backend All scenarios
Implementation
Approval Apps
Confirm Quantity
Invoice solutions_fiori_app_qty_customizing.zip D66K923452 [a] Price App Submit Backend All scenarios
button customizing
Confirm Quantity
Invoice solutions_fiori_app_qty_launchpad_content.zip Q45K900217 [a] Price App Front end All scenarios
Launchpad content
Send Back
Invoice
D66K923450 [a] Perspective for Backend All scenarios
solutions_fiori_sendback_perspective_approvals.zip
Approval Apps
Site transport for Cloud
sitetransport_cf_23.4_invoice solution.zip Cloud Foundry
Cloud Foundry Foundry
Annotation Custom
template files for development
Fiori Analytics with SAP
Fiori_Analytics_ALP_Templates.zip
Reports (Invoice Life Business
Cycle and IES Application
Extraction Analytics) Studio
Notes:
4 Documentation
Documentation for Vendor Invoice Management for SAP Solutions is available on My Support.
For additional information about OpenText™ Vendor Invoice Management for SAP® Invoice Solutions
and for supplemental information about related products, refer to the following documents, which are
available on OpenText My Support.
Available
Document title (Code number)
languages
OpenText Vendor Invoice Management for SAP Invoice Solutions 23.4 Reference
Guide (VIM-RGD) See SAP Note 3405218 - SAP Invoice Management by Open Text English
23.4: Release Restriction Note
OpenText Vendor Invoice Management for SAP Invoice Solutions 23.4 Scenario
Guide (VIM-CCS) See SAP Note 3405218 - SAP Invoice Management by Open Text
English
23.4: Release Restriction Note
OpenText Vendor Invoice Management for SAP 23.4 Security Guide (VIM-GSM) * English
OpenText Vendor Invoice Management for SAP Invoice Solutions 23.4 User Guide
(VIM-UGD) See SAP Note 3405218 - SAP Invoice Management by Open Text 23.4:
English **
Release Restriction Note
* Those documents include the information on VIM Framework components, formerly known as Business Center
SAP S/4HANA Cloud, Extended editions (EX) are supported by VIM 23.4 on the releases that
correspond to the supported on-premise releases listed above (also see SAP Note 2962569).
VIM does not support SAP S/4HANA Cloud, essentials editions (ES).
For details, Support Package levels of SAP platforms, and for dependencies on VIM Foundation add-
ons, see the following tables and the release notes for VIM Foundation.
1. Check the support package compatibility matrix in chapter 7 about allowed support
package combinations.
The SAP BTP Document Management Service is not supported by the VIM Fiori app.
Some specific functions (for example the input channel batch pipeline) are only supported for
OpenText Archiving and Document Access for SAP Solutions.
• Note: For the latest compatibility information for OpenText products, refer to the Compatibility
Matrix (https://knowledge.opentext.com/go/matrix) on OpenText My Support.
7.5
Compatibility VIM23.4
Matrix VIM 23.4 SPS0
OAP 23.4
OAP 23.4
Note
The following table lists the supported combinations of the operating systems for mobile devices and
the OpenText Approval Portal versions:
OAP 23.4
Mobile Devices Matrix
Web
Viewer
support
matrix 22.4
Web Mobile
OAP 23.4
Web Mobile
OAP 23.4
Note
Supported document types are JPG, TIF and PDF. For the rest of document
types, it is recommended to test this combination in a test environment before
moving on to production.
Approve Invoice
Bulk Approve
OTVIMFUI_02023_001
OTVIMFUI_BTP_02023_001
1.1"
Yes
Italy FatturaPA 1.2.1"
FPA12"
Yes
Xrechnung 1.0"
Germany
ZUGFeRD 1.0"
ZUGFeRD 2.0" No
ZUGFeRD ZUGFeRD 2.1"
ZUGFeRD 2.1.1"
Netherlands
Generic UBL format and delivery Yes
Check documentation
Belgium networks
Singapore
Japan
*
Version 1"
No
Mexico Factura Version 3”
Version 4”
No
China OFD OFD-Format
Yes
Poland Faktura
Yes
Switzerland Envelope Version 2.0
HDon
Vietnam 2.0.0 No
TDiep
See VIM Invoice Solution Scenario Guide for more information on electronic invoices.
Note: SAP provides Document Reporting and Compliance module (SAP DRC) to enable connectivity
with electronic document delivery networks like Peppol. VIM can integrate with SAP DRC when the
XML format of the documents is supported by VIM, automating the inbound processing (for example,
with invoices in UBL format). SAP and OpenText verify the country specific integration scenarios when
support of new countries is delivered by SAP DRC. The table above shows which country/format
scenarios have been verified with SAP DRC integration.
Component Languages
EN DE JA FR IT ZH ES RU * NL PT
OpenText Vendor B, F B, F B, F B, F B, F B, F B, F B, F B, F B, F
Invoice Management
Component Languages
HU RO TR PL CS SK KO SV FI
OpenText Vendor UI UI UI UI UI UI UI UI UI
Invoice Management
* = Supported with limitations (not all texts may have translations).
UI = user interface only
B = both user interface and User Guide
F = Fiori UI
Please note that the installation sequence of VIM invoice solution and VIM Foundation add-ons is
important unless you install everything in one step. Always install the latest Support Package for VIM
during the installation. More information about that is provided in the Installation Guide.
• 2339460 - Exception "Invalid or no mapping to system data types found" occurs when calling
a service with multi origin (mo) query option.
Consider specific requirements and instructions associated to the VIM gateway component for the
Supplier Self Service (lean). For details, see OpenText Vendor Invoice Management 23.4 Installation
Guide.
• /OTX/PS35_DROP_ALL_DRAFTS
• /OTX/PS37_DROP_ALL_DRAFTS
Backend Packages
The following table lists the supported release and support package level of each mandatory backend
component that is required for a specific VIM version and support package level.
Frontend Packages
It is possible to install a higher SP level of the front-end packages (OTVIMFUI) and connect to
backends with lower SP levels. The following combinations are supported:
OpenText recommends that you check OpenText My Support (https://support.opentext.com) for new
product updates or documentation updates that may have been posted after this release.
The default values for these constants are provided primarily for backward compatibility. If you are
processing large invoices, review the settings for each. Factors that need to be considered are number
of fields visible in line items, number of line items in extreme cases that still need to be processed with
SCE, performance of your application servers and end user workstations (as the data will be loaded
into SCE control running in SAPGUI). Note that large invoices with their corresponding data sets will
cause long run time and potentially short dumps due to timeouts.
A new constant 'MAX_ALLOWED_DPS' has been added to table /PTGWFI/Z_CONST for the product
code 005.
In VIM Invoice workplace whenever switch work view to "All users view" there is run time error whenever
the number of invoices to be processed exceeds certain limit in All Users view.
With the above constant, customers can restrict the number of invoices to be processed by changing
the value of above-mentioned constant value. The default value is 3000.
8 Fixed issues
This section provides information about past issues that have been fixed in this release.
VIMI-32924
Custom function configured in DP document type for Application sync function is not being
determined correctly when “Change document type” process option is used.
VIMI-34433
While posting a service PO with multiple account assignment using BDC 2200 amount distribution
is done incorrectly.
VIMI-34757
While posting a service PO with multiple account assignment having multiple G/L lines, posting to
few G/L line items are missing.
VIMI-35238
When process type changes but role remains the same when resolving exceptions, the DP workflow
data shows the first exception and not the latest one.
VIMI-35655
In DP indexing screen line item tab, the company code in the cost center search help is incorrectly
set at times.
VIMI-36064
There is balance issue due to incorrect line item amount calculation for a PO invoice with multi
account assignment category split based on amount for multiple PO lines.
VIMI-36179
Posting of PO invoice or credit memo using BDC 2200 fails when the PO has return item.
VIMI-36211
For Non-PO invoice posted using BDC 34 the vendor VAT registration number is missing.
VIMI-36250
For Mexico Non-PO invoice posted using BDC 34 the UUID number is missing.
VIMI-36278
In the DP indexing screen line item PO Reference tab, the label for field "Balance" is missing.
VIMI-36281
When opening a PO invoice with non-decimal currency runtime error
'CX_SY_CONVERSION_OVERFLOW' occurs if the line item amount holds value greater than 12
digits.
VIMI-36287
Performance improvements for Single Click Entry for SAPGUI in case of large documents.
VIMI-36325
When invoice currency is different from the company code currency the gross amount calculation is
incorrect and holds an incorrect value.
VIMI-36326
When posting TM invoices with profitability segment in line items, BDC error “There is different
account assignment information in item" occurs.
VIMI-36428
When configuration for coding field mapping is incorrect, certain fields are assigned incorrect values.
VIMI-36456
Deleted WHT data is sporadically added again on executing “Apply Rules” process option.
VIMI-36459
The exception “PO Not Released or Incomplete” (process type 106) is raised incorrectly for PO
invoices without release strategy.
VIMI-36611
Background posting of a PO invoice using BDC 2200 fails for a PO with single account assignment
and all the invoice receipt flags disabled.
VIMI-36645
During background posting of PO invoice using BDC 6 there is balance error when the invoice has
few line items that are already invoiced.
VIMI-36668
Incorrect error message is displayed in tax tab of the indexing screen when the reporting country is
changed which does not match with that of vendor.
VIMI-36675
The exception "Validate Bank Details" (process type 270) is raised incorrectly in case of permitted
alternative payee.
VIMI-36751
When using custom function to determine the baseline date, payment terms days are incorrectly
calculated in the indexing screen.
VIMI-36781
Incorrect translation text appears in German language for "Select All" button in the indexing screen.
VIMI-36796
The exception "Invalid Vendor VAT Number" (process type 220) is getting incorrectly triggered even
after having the correct vendor VAT Number in the indexing screen.
VIMI-36874
The net price in the line items tab of the indexing screen gets cleared if manually updated or after
pressing enter when amount is less than net price in the PO.
VIMI-36952
Withholding tax amount for Non-PO Invoice in the indexing screen is not getting calculated for
vendor currency when company code has multiple local currencies.
VIMI-36957
For a PO invoice the place of supply is derived from plant instead of business place in the basic data
tab of the indexing screen.
VIMI-36967
Amount values are uploaded incorrectly when using “Upload coding” function for 3rd decimal
notation setting where the decimal value contains comma and no thousands separator.
VIMI-36974
Work item is assigned incorrectly to referrer instead of referee when posting fails in background.
VIMI-37057
When using feedback on process end, data entered using SCE (Single Click Entry) for SAPGUI is
not sent into feedback completely. Geometry data is missing for those fields.
VIMI-37060
Custom function for Canadian PO invoice is not considered even though Z-constant
'005/DEFAULT_TAXCODE_PO' is maintained when doing tax calculations.
VIMI-37443
When vendor is changed and 'NO' is chosen in the IBAN update confirmation popup, QR-IBAN is
getting updated.
VIMI-37449
Background posting of service PO invoice with multi account assignment for non-decimal currency
fails as balance is not zero.
VIMI-37580
In indexing screen basic data tab, the ‘Ship-To Region’ value in company address is replaced with
master data even though the value is manually entered.
VIMI-37676
For PO invoice with limit item category and service IV indicator checked the exception
“Manual check needed” (process type 113) is triggered incorrectly when quantity is zero.
VIMI-37687
Performance issues while posting invoices with multiple lines having tax jurisdiction.
VIMI-37746
Repetitive warning messages appear in the indexing and approval screens if tax code is not
maintained at header/line item level and when “Plants Abroad Active” is activated.
VIMI-37797
During background posting of PO invoice using BDC 6, posting fails when same delivery note is
used for multiple POs across different company codes but with same vendor.
VIMI-37906
Withholding tax is calculated incorrectly for Non-PO Indian invoice when threshold limit is crossed.
VIMI-37916
During background posting of PO invoice using BDC 6 with only G/L lines and no line item data, tax
amount is posted against wrong G/L account.
VIMI-37929
The search help in the DP document type field level configuration does not show all fields of VIM
header data table.
VIMI-37945
Withholding Tax is calculated based on gross amount instead of net amount when PO line
items are proposed & matched.
VIMI-37948
A run time error occurs when proposing line items in the indexing screen using bill of landing option
where the freight lines have foreign vendor.
VIMI-37999
VIMI-38064
During background posting of Non-PO invoice using external tax system having debit and credit line
items BDC error 'Tax entered incorrect' occurs.
VIMI-38068
DP workflow runs into error while posting a service PO in background when each service line is
mapped to multiple WBS elements.
VIMI-38187
Run time error occurs during DP creation or using “Apply Rules” process option for a PO DP with
item category ‘A’.
VIMI-38217
Changing the reporting country in the DP document does not pull the correct vendor VAT number.
VIMI-38239
In the indexing screen run time error occurs when negative value is entered in the quantity field.
VIMI-38445
Withholding tax amount is not rounded correctly for invoice with non-decimal currency when the
base amount is manually entered in the indexing screen.
VIMI-38447
Incorrect translation for fields ‘Plant’ and ‘Order Unit’ for Swedish language in the proposal tab of the
indexing screen.
VIMI-38492
For Non-PO invoice reporting country value from VIM is not passed while doing online posting
using BDC 40.
VIMI-38539
When entering bank details without IBAN for the first time in OTV screen, bank data is not transferred
to indexing screen.
VIMI-38624; VIMI-39083
Withholding tax amount values not calculated correctly on manual change of withholding tax
codes for India PO invoice in the indexing screen.
VIMI-38768
Incorrect gross amount is updated to the DP after posting the intercompany credit memo document.
VIMI-38791
During background posting of Non-PO invoice using BDC ID 34, BDC error "Tax statement item
missing for tax code Z0" occurs.
VIMI-38779
During background posting of PO invoice using BDC 2200 BDC error “Enter fulfillment date' occurs
even when VAT date is available in the posting data.
VIMI-38798
VIMI-38845
WBS element value in smart coding proposal screen is shown in internal format.
VIMI-38850
During online posting of Non-PO invoice gross amount is set back to VIM as zero when amount is
split in FB60.
VIMI-38987
The exception "Tolerance Exceeded (PO)" (process type 406) is raised incorrectly for PO DPs
having G/L line items for Indian PO invoice.
VIMI-39121
For a PO invoice of Indian Company code WHT base amount is reappearing when the WHT base
amount is cleared manually and pressing enter on the screen.
VIMI-39125
After using the process option "Post Goods Receipt" (2007), control does not navigate back to
indexing screen.
VIMI-39619
Posting of PO invoices in background is not possible as asset data gets locked by background user.
VIMI-39699
During DP workflow creation the WHT data though determined in the logic module does not get
saved to the DP in the subsequent processing.
VIMI-39846
When executing F110 transaction error ‘Vendor is blocked, editing not possible’ occurs as locks on
vendor are not getting released during Non-PO invoice postings.
VIMI-39753
Payment terms are getting deleted during background posting (BDC 2200) when configured as fixed
day.
Invoice Approvals
VIMI-36074
For a DP that is approved and posted few days after receiving in inbox, the baseline date is not
getting reflected correctly when the configuration is set to posting date (current system date).
VIMI-34689
In COA maintenance transaction (/OPT/AR_COA), data is not saved properly when user has
different edit and display authorizations at company code level.
VIMI-36498; VIMI-37447
Attachments are not visible in the approval screen when CMIS Repository is used.
VIMI-36783
DP is routed to last referred role incorrectly when invoice is approved by user logged into language
other than English and when posting fails.
VIMI-36797
For multi-approver scenario (AFS ID 25), approving invoice goes into endless loop when "Skip COA
levels" is checked in the configuration.
VIMI-37009
The pack amount for approval limit is calculated wrong when approval amount base is set to gross
and auto-calculate tax option is checked.
VIMI-37167
For Non-PO Invoice with non-decimal currency approver is not determined correctly when auto
calculate tax is set off and there is VAT amount in the invoice.
VIMI-37799
When approval action is cancelled and started again in approval screen in the same session, next
approver is determined incorrectly for Non-PO invoice with VAT balance and auto calculate tax check
option set to off.
VIMI-38184
When manager ID is changed for a user in COA the new manager ID is not saved.
VIMI-38209
Invoice approval workflow gets stuck if the next approver is not available in SAP user master table.
VIMI-38569
For a PO invoice having both material line items and G/L line items, after approval the line item
information is swapped or duplicated.
VIMI-38584
When using custom exit function for "DETERMINE_VALID_USR" there is no access to global
variable "gv_current_approver".
VIMI-38781
Not possible to add new substitutes in transaction (/ORS/MAIN_SUBS) under "Substitutes for" tab
when the user has substitutes who are not active in the validity period.
VIMI-39049
There is error 'Account XXXXXXX requires an assignment to a CO object' during coding validation
due to which invoice is not approved.
Invoice Exceptions
VIMI-37634
When using “Short Pay” process option in PO invoice dashboard, PO number is not getting
populated in MIRO screen when TM module is activated.
VIMI-38558
Blocked workflow is triggered for a TM invoice when status is set to blocked due to price or quantity
discrepancy.
VIMI-39086
Performance issues while removing payment blocks of FI or MM documents.
VIM Notifications
VIMI-36792
The reminder report does not send overdue notification to substitute whose OPT user id and SAP
user id are different.
VIMI-36940
The reminder report does not send notification to substitute when approval work item was viewed
by substitute.
VIMI-37669
SRM notification mails are sent in incorrect format when configured format type is ‘HTM’.
VIMI-36298
The clearing document number and paid date are not seen for a PO invoice whose clearing
document is posted and then block removed outside of VIM.
VIMI-36641
When processing PO invoice with large number of line items (800+) though entire transaction is
rolled back, MM document number which does not exist is shown in VIM Analytics.
VIMI-36656
Option Text is missing in the process tab of the detail pane.
VIMI-36685
Overall Process Status selection criteria does not work correctly for Selected Status - 33 (Approved,
payment block exists)
VIMI-36790
Special characters are not displayed correctly when viewing the archived mail originated from RTV
process option in HTML view.
VIMI-36947
VIMI-36951;VIMI-38752
When clearing document is reversed or when MM invoice is cancelled and cleared using
F-44/FB1K then clearing document and Paid On/At details are updated in the DP.
VIMI-37090
Performance issues when searching for documents with selection criteria as Overall Process Status
(Open Invoices) and Channel ID (MAIL_IES).
VIMI-37299
VIM Analytics does not display accounting documents when invoice posted through standard SAP
IDOC function module.
VIMI-37728
For invoices posted against multiple service POs, there is incorrect service entry reference in the
line item tab.
VIMI-38181
Error message "Error archiving E-Mail" is displayed when using Process Option 'Return to Vendor'.
VIMI-38204
There is status discrepancy when a DP is first canceled and then blocked outside VIM.
VIMI-38300
Even after confirming the DP as Duplicate, exception reason shows as ‘Suspected Duplicate’.
VIMI-38490
Status discrepancy between document status & process status when block is removed from a
cancelled document.
VIMI-38621
DP documents are not displayed when current role is removed from layout.
VIMI-38848
While opening a PO subsequent debit invoice having unplanned delivery costs there is a runtime
error.
VIMI-39321
When a DP is rejected in validation client the rejected reason comments are not showing in the DP
document after upgrading to VIM 20.4.
VIMI-39388
When layout of VIM Analytics is changed for large number of invoices, system throws run time error.
VIMI-39672
PDF workflow history document is not attached in the accounting document for posted Non-PO
invoice using BDC 34.
VIMI-39702
VIMI-34730
For invoices that are getting posted while yearend program is running, posted data is replaced with
previous data for the DP document.
VIMI-37187
Performance improvements in the collection report program (/OPT/VR_COLLECTION_REPORT).
VIMI-37767
DP documents stuck in default exception are not processed by DR BR Wait (/OPT/DR_BR_WAIT)
program when there is no BDC log.
VIMI-37828
During background jobs execution for rerun rules or DR BR wait, in certain scenarios the DP data is
not updated with posted data and retains the old values.
VIMI-38017
The program to mass update posting date (/OPT/DP_POST_DT_UPD) is including the documents
with confirmed duplicates.
VIMI-38063
When reassigning the invoice from user map maintenance utility (/ORS/UMREASSIGNED) wrong
DP header data is fetched for a scenario where DP DOCID value occupies all 12 characters.
VIMI-38553
Incomplete Spanish translation in screen of user map maintenance utility (/ORS/UMREASSIGNED).
VIMI-39053
The KPA report /OPT/VIM_KPA1 shows incorrect values for ‘First Pass’ entries.
VIMI-39590
The DP Cancel and Recreate (/OPT/INV_CANCL_RECRT) report does not work for a DP processed
via IDOC channel and has custom fields configured in mapping.
VIMI-39654
The DP document is not assigned to correct agent when DR BR report (/OPT/DR_BR_WAIT) is
executed for an invoice in GR Wait step and wait time is over.
VIM Workplace
VIMI-35608
In VIM Workplace for Other User work view in the pending tab the current agent is incorrectly shown.
VIMI-38502
VIMI-36245
There is no data validation for new members added to a team in General Team Definition for VIM
Workplace.
VIMI-36454
In the selection pane search field for vendor name does not fetch proper results when using '*' in the
wild character.
VIMI-36494
When working with multiple DP documents in the same session, data is wrongly overwritten from
previously cancelled DP to subsequent DPs.
VIMI-36683 I
When using “Return to Vendor” option, the field "CC_Requester" cannot hold more than 80
characters.
VIMI-36744
Polish translations texts are not seen for work items in VIM workplace.
VIMI-38628
Missing French language translation in VIM workplace and line item fields in the indexing screen.
VIMI-37924
Performance issues in “Team View” when more than 100+ users are configured in the team.
VIMI-36495
Security issues as XSS-Payload can be executed by manipulating the attachment file name.
VIMI-37769
It is not possible to upload a .CSV file as an attachment in Web Approval Portal.
VIMI-39011
For PO invoices with multiple G/L line items, few cost elements data is duplicated in some line items.
VIMI-39283
All values of Delivery and Price fields are available for selection even when not made active.
VIMI-39859
Search by vendor number is not working.
VIMI-37971
Incorrect list of approvers is displayed when using search option to select approvers.
VIMI-39284
When both header and line item tax amount are changed at the same time the header tax amount
still reflects the old value.
VIMI-39330
The XML visualization of invoice image is not shown in default in FIORI Exception app.
VIMI-38536
Performance issues when forwarding invoices from Invoice Approval Workplace app.
VIMI-38823
Input Channels
VIMI-35656
When an XML with blank name spaces is processed using transformations no data is extracted.
VIMI-36139
The enhancement mapping function derives incorrect company code when recipient VAT number is
empty in the FATTURA XML invoice for Italy.
VIMI-36398
During IDOC inbound processing archive date and time are not captured for the invoice image
created from IDOC data.
VIMI-36436
During inbound processing baseline date determination is incorrect when custom function is used.
VIMI-36446
Header labels are not translated in respective language when complex visualization is applied for
XML invoice.
VIMI-36697
For XML document with multiple POs, only header PO is considered, and the line item POs are
ignored for line item determination.
VIMI-36749
When the XML invoice has a negative amount, the document is treated as invoice and not credit
memo.
VIMI-36977
There is a run time error while creating a DP document without company code at line item level
when smart coding logic module is activated.
VIMI-36979
The bank name and bank account no. are not transferred to DP document though validated from
validation client.
VIMI-37011
Approval comments are not visible in Supplier Invoices node of VIM Central Workplace.
VIMI-37060
During inbound processing tax determination for Canadian PO invoice is incorrect when custom
function is configured in the Z-constant '005/DEFAULT_TAXCODE_PO'.
VIMI-37199; VIMI-38361
During inbound processing for single line item PO, unplanned / planned costs during PO line item
matching are calculated incorrectly.
VIMI-37500
Line items from OCR are not ignored when "Ignore items from Ext System" activated at document
type configuration.
VIMI-37668
When zero tax rate tax code is unique, and no value for tax rate is provided, tax determination will
set that tax code which is not correct.
VIMI-37974
Exceptions/Errors raised during tax calculation are not handled when DP is created from inbound.
VIMI-38591
When line item amounts are positive in a credit memo created through IDoc, the lines are considered
as debit.
VIMI-38739
Extracted data from Core Capture not transferred to VIM.
VIMI-39648
During inbound process run time error occurs when TM invoice has combination of Freight Order,
Freight Settlement Document, Bill of Lading, and Air Waybill.
VIMI-39674
For custom document type in configuration if the ‘Invoice Type’ is not set there is run time error
during DP workflow creation.
9 Known issues
The following known issues exist in this release.
VIMI-39135 In the line items tab the amount fields for non-decimal currency invoice display
wrong notation.
VIMI-39703 In Fiori ECA App line item split is not working correctly when split lines count is
greater than 2.
VIM Analytics does not show current agent when DP is at GR Wait business
VIMI-39944;
rules (163,164,165) with and without CDS views options.
VIMI-38738
Runtime error reported when 'Attachment List' button is clicked in VAN report
VIMI-40462