Kofax MarkView 10.0.0 Fix Pack 9

Build Date: January 10, 2023

© 2023 Kofax. All rights reserved.
Use is subject to license terms.

Introduction

You can install Kofax MarkView 10.0.0.9 to resolve the issues listed below.
Note: To install Kofax MarkView 10.0.0.9 successfully, a full installation of Kofax MarkView 10.0.0 is required.
If you need to perform a full product installation, see the Kofax MarkView Installation Guide for instructions.

List of Issues Resolved in This Fix Pack

1882184: Parameter checking added to improve security

1848394: Web application security improved

1848393: SQL security improved

1562684: Encountered an issue when coding an invoice with NON billable project coding

List of Issues Resolved in Previous Fix Packs

Issues Resolved in Fix Pack 8

1734082: After applying the Oracle patch for the Log4j vulnerability, MarkView negatively impacted core Oracle functionality

1697167: Viewer did not display all layers of some PDF files imported through the Import Server

1587075: Viewer tools icons did not appear in the Viewer

1212776: Using Invoice Audit to print Expense based invoices caused both Expense Report and Invoice Document to be printed, which resulted in duplicates

Issues Resolved in Fix Pack 7

1584268: Import Server failed to import PDFs with embedded images or signed with Docusign

1580963: Auto escalations did not work due to error ORA-01722: invalid number

1572013: Request was denied due to unacceptable characters in the input - error trying to reach MarkView Home using Google Chrome browser

1555426: MarkView 10.x Fix Pack Installer included an option to select "Install Wildfly"

Issues Resolved in Fix Pack 6

1559630: C&O: Support for RDBMS 19c (19.3) and Windows 2019 was added

1559294: The dependency on Oracle Java Advanced Imaging (JAI) was eliminated

1538780: KTM Validation screen 'Match Receipt Lines' was showing the Fully Invoiced Releases

1538776: KTM Validation screen 'Match Receipt Lines' was showing 'CLOSED' releases

1538754: Deliver To Person ID and Agent ID longer than 30 characters resulted in error when processing a PO invoice

1538744: R12 Tax Field - MarkView Tax Regime LOV values were not similar to Oracle LOV values

1538733: Invoices with "Misc Costs" in their amount after the queue "Waiting for Interface Processing" got stuck in "Interface Processing Error"

1538720: Account Coding - the ACD list of values did not show certain Legal Entities

1538711: MarkView showed end-dated Legal Entities in the ACD list of values

1524473: Changes to the default displaying of invoices were not saved

1518264: MarkView Documents did not open from an iExpense notification email when Java Web Start was enabled

1516044: Support for SAML using SHA256 was added

1500095: When attempting to apply the 10.0.0.5 hotfix, an error occurred during publishing the batch class, if the Kofax Analytics for MarkView workflow agent did not exist

1497101: Users with the LOCALE_de group assigned could not assign an alternate user

1491230: When entering an OU into the invoice workbench in R12, after clicking Get Next an error was thrown: 'FRM-402020: Field must be entered'

1472893: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXRTINV form in Oracle Apps as that user

1472892: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXPNDQS form in Oracle Apps as that user

1470296: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the Workflow Role Select form in Oracle Apps as that user

1469054: Oracle user names (USER_ID) longer than 30 characters resulted in error when trying to launch the Working Folder as that user

1467544: MarkView Viewer did not load when opening an invoice

1451693: Account Coding - Business Entity Segment LOV values did not match Oracle segment values; MarkView showed only the segments attached to a legal entity

1413512: Generating properties for silent installation was incorrect

Issues Resolved in Fix Pack 5

1412182: Kofax Analytics for MarkView displayed two invoices processed via Kofax Capture instead of one

1407752: Java Web Start (JWS): request to open MarkView documents in a single instance of the Viewer

1406029: Enhancement Request to support Oracle Database 19c (19.3)

1395912: Coding DFF - error encountered with apostrophe in DFF segment values

1110352: PO Line Numbers greater than 5 characters lead to error: PL/SQL: numeric or value error: character string buffer too small

Issues Resolved in Fix Pack 4

1374043: MarkView Viewer: vertical scroll bars were missing

Issues Resolved in Fix Pack 3

1344237: There were no titles of controls in the AUSS "Select Source System Groups" window in Google Chrome browser

1343791: There were no "Add" and "Remove" buttons on the AUSS Source System groups page in Google Chrome browser

1337672: Change to MV_IMP_GENERIC to support Kofax Analytics for MarkView overwrote workitem properties in customer's MVT_DOCUMENT_CAPTURE_CUSTOM.PostCreateDocument procedure

1327542: Verify Upload functionality did not work in MarkView Import API Configuration

1303543: XSS filter failed when there were double quotes in the header from Single Sign On

1290734: Line amount defaulted was not the same as the undistributed amount when mverp_dfm_custom.GetAmountUndistributed was customized

Issues Resolved in Fix Pack 2

1282898: Enter button did not work correctly in the Accounting section in edit mode

1281228: Apostrophe in MarkView user's last name or email address caused viewer to lock

1279493: Edit mode was not cancelled when you collapsed a line or distribution

1279490: Column functions did not work properly while edit mode was enabled

1270468: Hidden column headers were visible after refresh in Viewer Accounting section

Issues Resolved in Fix Pack 1

1253986: Could not print the document if the range starts from the second page or later

1253266: The "Page of Total" button was displayed incorrectly

1247741: SSI - Opening SSI Supplier LOV did not return value list and eventually caused failure

1243664: Viewer loaded definitions of all action tools regardless of their availability for a particular document

1243663: Viewer loaded definitions of all annotation tools regardless of their availability for the particular document

1243424: Strings bundle for Viewer located in resources

1243422: On Viewer loading, initial requests were not optimized (Auth, whoami, strings bundle)

1242976: Sorting in AP Inbox changed by user was not applied after Return to Inbox from Viewer

1242967: Sorting in AP Inbox was incorrect

1240691: Not possible to create Tax Line manually

1240663: Wrong font sizes in Migration Utility UI

1232814: Incorrect width and position of text about Approve/Reject from email in the Quick Info section

1231826: Viewer redrew the layout during loading

1231725: Viewer loaded more annotation templates than necessary

1230188: Excessive number of table definition requests between application server and database

1229711: Unable to call the custom package MVOA_SSI_DFF_CUSTOM from the package MVOA_SSI_UI_DFF if the validation type was F

1228717: Viewer loaded thumbnail #1 twice

1228695: Viewer redundantly loaded formats amount formats, which could adversely affect performance

1225277: About dialog listed Flex as dependency./p>

1221912: In-Place editor lost the decimal symbol <,> when a line or distribution were added

1221096: Confusing dates in message "The page needs to be refreshed because user JSMITH updated the page ..."

1220311: User was able to approve invoice edited in MarkView by another user

1175804: 'MVT Global Maintain Alt Usr' rule must Unassign first and then Assign new alternate user assignments

1117295: It was possible to create Org in MarkView without functions, filter parameters and block function mappings being set up

1110055: Different scripts sharing the name — accounts-payable-1217-mvappolimlocmv-alter-tab.sql

1108095: Button and info message contained inconsistent Action names

1104704: Incorrect queue name in the Viewer info message

1057444: URL Preferences with no value could adversely affect the Migration Utility

978014: Incorrect variable type declaration in MV_IMP_GENERIC

963348: Mail properties did not carry to redirected work items

919916: Incorrect user name in Alternate User Assignment notification when more than one user was unassigned

883411: MarkView ACD Tool - Requested ability to modify an unmodifiable field

863060: Authentication was successful when Oracle password was expired

760554: Mismatch in spelling of “User Name” and “Username” on login page

608198: L10N: An invoice could not be escalated or reassigned to a user whose name included Chinese/Japanese characters

Applies To

This fix pack is based on Kofax MarkView for Accounts Payable 10.0.0.
Only apply this fix pack to the MarkView 10.0.0 application server; do not run the fix pack installer on a MarkView Oracle Objects installation or on a Kofax Capture Output installation
Verify that the version of all installed MarkView components (such as Self-Service Invoices, Document Library, Expenses) is 10.0.0.
For information about system requirements, see the Kofax MarkView 10.0.0 Planning Guide and the Technical Specifications document on the Kofax MarkView Product Documentation website.
Applying this fix pack multiple times on the same system causes no harm. Also, fix packs are cumulative for a release, so Kofax expects you to apply the latest fix pack on top of any previously installed 10.0.0 fix packs.
This fix pack includes files that are staged on the application server and that require manual steps, which are included in the sections that follow.

Files Included

This fix pack includes the following files:

File name	Version
KofaxMarkView-10.0.0.9.zip	10.0.0.9

Install This Fix Pack

Use the following procedures to install the fix pack.

MarkView Application Server Installation (includes Database Components)

Only apply this fix pack to the MarkView 10.0.0 application server.
Before starting the following procedure, read this entire ReadMe file.

Silent Installation Preparation

If you used the silent installation method to install MarkView 10.0.0 and you plan to use the same method to install the fix pack, do the following:

1. Go to the distribution > conf folder.

2. Open the preliminary_interview.properties file.

3. Enter the required information according to the Kofax MarkView 10.0.0 Upgrade Guide (see Chapter 2), but leave the SelectedProducts.selected_products parameter blank.

4. Run the generateInterviewTemplate script to create or update the installer_interview.properties file.

5. Open the installer_interview.properties file.

6. Enter the required information according to the Kofax MarkView 10.0.0 Upgrade Guide.

Apply the Fix

1. Log in to the application server as the user who installed MarkView 10.0.0.
   Ensure that the environment variables required for installing MarkView 10.0.0 are defined.
   See the Kofax MarkView 10.0.0 Upgrade Guide for information about setting environment variables and the settings required to run the installer.

2. Locate the base MarkView directory where MarkView is installed. Use this pathname when prompted for the "Install Directory" during installation.
   The base MarkView install directory includes the following files:

   • target_registry.properties
   • thirdparty.txt

3. Extract the KofaxMarkView-10.0.0.9.zip file into a new directory on the application server where MarkView 10.0.0 is installed.

4. Verify that the system is quiet to ensure that the data remains synchronized.

5. Log in to an SQL*Plus command window as the SYSDBA user.

6. Assign all needed grants and privileges to the MarkView schema user by executing the markview_grant_privileges.sql script, which is included in the following fix pack distribution directory:
   <MARKVIEW-FIX-PACK-INSTALLER>/modules/installer-dist-10.0.0/scripts
   where <MARKVIEW-FIX-PACK-INSTALLER> is the directory where KofaxMarkView-10.0.0.9.zip was extracted.

7. Log in to an SQL*Plus command window as the MarkView schema user.

8. Stop the currently running database user jobs by executing the breakDBJobs.sql script, which is included in the following fix pack distribution directory:
   <MARKVIEW-FIX-PACK-INSTALLER>/modules/installer-dist-10.0.0/installer-db

9. To run the installer, invoke the installation script in the bin directory of the fix pack distribution (install.bat|sh or install_silent.bat|sh).
   See the Kofax MarkView 10.0.0 Upgrade Guide for information about running the installer.
   The installer shows the list of all 10.0.0 fixes in the fix pack.

10. Provide answers to any unspecified values in the installer windows.
    Use values that match those provided during version 10.0.0 installation.
    (If available, use the installation worksheet that was completed for MarkView 10.0.0.)
    Note: Install the fix pack in the same target directory specified for the MarkView 10.0.0 installation.
    If you run the installer and see pre-populated information for the wrong environment, such as production URLs when running against a non-production environment, update the fields manually in the installation window.
    If you install this fix pack on WildFly, do one of the following:

    • For standalone mode:
      In the Enter App Server information for MarkView applications, leave the Domain field blank.

    • For domain mode:
      In the Enter App Server information for MarkView applications, enter your domain name in the Domain field.

11. When the installation is completed, follow the on-screen instructions that appear in the installation summary window.

12. Restart the application server.

13. Skip this step if you have MarkView 10.0.0 Fix Pack 3 installed.
    As a result of the implemented changes, the following procedure is modified in the MVERP_DFM_Custom package.
    GetAmountUndistributed: Sets the undistributed amount for invoice lines or invoice header.
    Follow these steps to update the customization:

    1. In <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX10312, find the mverp_dfm_custom_pb.sql package,
       where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

    2. If you have not customized your MVERP_DFM_Custom package, compile this package to upgrade it to the current version.

    3. If you have customized your MVERP_DFM_Custom package, modify it manually and compile the package to correspond to the current specification.

    4. Note that procedures and functions from the MVERP_DFM_Custom package are called only if the ENABLE_MVERP_DFM_CUSTOM preference is set to TRUE.

14. To ensure that all database objects are compiled successfully, follow the instructions in the "Check for Invalid Packages" section of Chapter 5 of the Kofax MarkView 10.0.0 Upgrade Guide.

15. Skip this step if you have MarkView 10.0.0 Fix Pack 5 installed.
    As a result of changes implemented, a database job for Connector Workflow Manager should be recreated.
    To create new database job for Connector Workflow Manager, follow the instructions in "Create a database job for Connector Workflow Manager" in the Kofax MarkView 10.0.0 Upgrade Guide.

16. Log in to an SQL*Plus command window as the MarkView schema user.

17. Start database user jobs by executing the startDBJobs.sql script located in the following fix pack distribution directory:
    <MARKVIEW-FIX-PACK-INSTALLER>/modules/installer-dist-10.0.0/installer-db
    where <MARKVIEW-FIX-PACK-INSTALLER> is the directory where KofaxMarkView-10.0.0.9.zip was extracted.
    In a clustered environment, point to one server, then propagate to other nodes in the cluster using the appropriate process for your application server.

18. If you plan to install Import Server or you have Import Server 10.0, verify that you clear the Verify Upload option on the Import tab of the MarkView Import Server Preferences window.

Kofax MarkView Export Connector 10.0.0

Skip this section if you have MarkView 10.0.0 Fix Pack 3 or later installed.

Install Kofax MarkView Export Connector version 10.0.0.3.

Note: If you have any customizations of the MarkView KTM Project, back up your customized version. If you have any customizations of the XSLT files used by MVImportAPIConfig, back up the XSLT files before running the installer.
If you do not plan to use Kofax Analytics for MarkView, you can restore the XSLT backup files after the installation of Kofax MarkView Export Connector.

To install Kofax MarkView Export Connector:

1. Run the kcec-markview.msi file from:
   <MARKVIEW-INSTALL-DIR>/misc/10.0.0/KCEC-MarkView
   where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

2. Clear the KTM Project Feature checkbox in the installer window.

3. To perform a silent installation or removal, run one of the following commands from the directory where kcec-markview.msi is located:

   • To install Kofax MarkView Export Connector silently and overwrite your existing KTM project:
     

     msiexec.exe /i kcec-markview.msi /qn

   • To install Kofax MarkView Export Connector silently without the new KTM project:
     

     msiexec.exe /i kcec-markview.msi ADDLOCAL=ProductFeature /qn

   • To remove Kofax MarkView Export Connector:
     

     msiexec.exe /uninstall kcec-markview.msi /qn

   The msiexec.exe file is located in the following directory:
   C:\Windows\system32\

Kofax Capture batch class templates

Kofax Capture batch class templates for MarkView were updated as part of 10.0.0 Fix Pack 6.

To apply the changes, follow the steps:

1. Copy the MarkView.cab file
   From:
   <MARKVIEW-INSTALL-DIR>/misc/10.0.0/KTMProject
   To:
   C:\KTM\MarkView

2. In Kofax Capture Administration, import the MarkView.cab file.

3. Resynchronize your project and republish the corresponding batch classes.

Capture and Output components for MarkView 10.0.0

1. Skip this section if you have MarkView 10.0.0 Fix Pack 7 installed.

   MarkView Import Server was updated as part of the MarkView 10.0.0 Fix Pack 7.
   

   1. To install or upgrade MarkView Import Server, run the MVImport.Installer.msi file from:
      <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX14823
      where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

   2. Configure MarkView Import Server on a machine with KTM installed.

2. Skip this section if you have MarkView 10.0.0 Fix Pack 6 installed.
   To support RDBMS 19c and Windows 2019, do the following steps:

   1. Install ODAC1931_x64;

   2. Install Oracle Database 19c Client (19.3) for Microsoft Windows (32-bit):

      1. Run the installer.

      2. Select the Custom installation type.

      3. On the Available Product Components page, select the following components:
         Oracle ODBC Driver
         Oracle Provider for OLE DB
         Oracle Data Provider for .NET

      4. Install the product.

   3. Register the Oracle.DataAccess.dll in the GAC by running the following commands in the CMD (use 32-bit CMD):

      cd <Oracle Database 19c Client for Microsoft Windows (32-bit) installation directory>\odp.net\bin\4
      OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\ODP.NET\bin\4\Oracle.DataAccess.dll
      OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\4\Policy.4.112.Oracle.DataAccess.dll
      OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\4\Policy.4.121.Oracle.DataAccess.dll
      
      cd <Oracle Database 19c Client (32-bit) installation directory>\odp.net\bin\4
      OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\ODP.NET\bin\4\Oracle.DataAccess.dll
      OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\4\Policy.4.112.Oracle.DataAccess.dll
      OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\4\Policy.4.121.Oracle.DataAccess.dll
      
      cd <Oracle Database 19c Client (32-bit) installation directory>\odp.net\bin\2.x
      OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\ODP.NET\bin\2.x\Oracle.DataAccess.dll
      OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.102.Oracle.DataAccess.dll
      OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.111.Oracle.DataAccess.dll
      OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.112.Oracle.DataAccess.dll
      OraProvCfg.exe /action:ungac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.121.Oracle.DataAccess.dll
      
      cd <Oracle Database 19c Client (32-bit) installation directory>\odp.net\bin\2.x
      OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\ODP.NET\bin\2.x\Oracle.DataAccess.dll
      OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.102.Oracle.DataAccess.dll
      OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.111.Oracle.DataAccess.dll
      OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.112.Oracle.DataAccess.dll
      OraProvCfg.exe /action:gac /providerpath:<Oracle Database 19c Client (32-bit) installation directory>\odp.net\PublisherPolicy\2.x\Policy.2.121.Oracle.DataAccess.dll
      

3. MarkView Mail Gateway and Barcode Server were updated as part of MarkView 10.0.0 Fix Pack 6.

   1. To install or upgrade MarkView Mail Gateway, run the sfMailService.Installer.msi file from:
      <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX14539

   2. To install or upgrade MarkView Bar Code Server, run the MVBarcodeServer.Installer.msi file from:
      <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX14539

   3. Configure MarkView Barcode Server and Mail Gateway on a machine with KTM installed.

MarkView Post-Installation Steps (WildFly and FileNet only)

Skip these steps if you have MarkView 10.0.0 Fix Pack 3 installed.

If you are installing this fix pack on WebLogic Application Server, or if you do not use the FileNet server, skip this section.

If you are installing this fix pack on WildFly Application Server and you use the FileNet server, perform the following post-installation steps:

1. Back up $JBOSS_HOME/standalone/configuration/standalone.xml.

2. Open $JBOSS_HOME/standalone/configuration/standalone.xml and locate the following tag:
   <subsystem xmlns="urn:jboss:domain:security:1.2">

3. Within <subsystem xmlns="urn:jboss:domain:security:1.2">, locate the <security-domains> tag and add the following strings:

   <security-domain name="FileNetP8WSI" cache-type="default">
    <authentication>
     <login-module code="com.filenet.api.util.WSILoginModule" flag="required"/>
    </authentication>
   </security-domain>

4. Save the file and restart the WildFly Application Server.

MarkView Post-Installation Steps (Oracle E-Business Suite using Java Web Start only)

MarkView 10.0.0 Fix Pack 5 includes an interim solution to Oracle E-Business Suite issue (Doc ID 2386335.1) WEB.SHOW_DOCUMENT Target WindowName Does Not Work with Java WebStart (JWS) that affects the MarkView Get Next functionality by opening a new browser tab for every invoice.
If you are integrating with Oracle E-Business Suite using the Java Plug-In technology to run Oracle Forms, skip this section.
If you are integrating with Oracle E-Business Suite using the Java Web Start technology to run Oracle Forms, perform the following steps for the appropriate client browsers.

To apply the MarkView patch in the Internet Explorer and Edge browsers:

1. Log in to MarkView as the Admin user.

2. Open Administration > MarkView Admin menu and set the MVOAIN_FORM_JWS preference value to TRUE.

3. Allow pop-up windows in the Internet Explorer and Edge client browsers.

MarkView 10.0.0 Fix Pack 5 also includes plugins for the Google Chrome and Firefox browsers that can be applied in the debug mode or published in Web Store.

To apply the fix in the Google Chrome browser in the debug mode:

1. Extract the Chrome.zip file to any location on your local PC.
   The file is located at the following path: <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX12311
   where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

2. Open a new tab in your Chrome browser, type "chrome://extensions" and click the Enter button.

3. Turn the Developer Mode on by sliding the Developer Mode slider to the right.
   As a result, the Load Unpacked button appears on the screen.

4. Click the Load Unpacked button, navigate to the directory where the Chrome.zip archive was extracted to, then click Select Folder.
   As a result, the "Kofax MarkView Tab Control for JWS" extension appears on the list of extensions.
   Note: To publish the fix in Chrome Web Store, follow the Chrome extension developer guide.

To apply the fix in the Firefox browser in the debug mode:

1. Extract <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX12311/Firefox.zip
   where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

2. Open the browser and enter "about:debugging#addons" in the address bar.

3. Click Load Temporary Add-on and select manifest.json file from the extension directory.
   Note: To publish the fix in Firefox Web Store, follow the Firefox extension developer guide.

Oracle Forms Integration

Apply FIX8627

Starting from version 10.0.0.6, the fix pack contains FIX8627 for the following bug:
Bug 1491230: When entering an OU into the invoice workbench in R12, after clicking Get Next an error was thrown: 'FRM-402020: Field must be entered'
If you do not experience the same issue or if you have already applied this fix, skip these steps.

To apply FIX8627:

1. Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.

2. Copy the MVOAUTIL.pll file from:
   <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX8627
   To:
   $c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries
   where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

3. Back up the previous version of $c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries/MVOAUTIL.plx.

4. Compile MVOAUTIL.pll into MVOAUTIL.plx using your valid connection string value:
   

   frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/libraries/MVOAUTIL.pll module_type=LIBRARY compile_all=YES

   Note: If you copy and paste from this file, remove any line breaks.

5. Back up the previous version of $AU_TOP/resource/MVOAUTIL.plx.

6. Copy the MVOAUTIL.plx file from:
   $c_MARKVIEW_TOP/MVOA/6.1.0.0
   To:
   $AU_TOP/resource

Apply FIX12715

Starting from version 10.0.0.6, the fix pack contains FIX12715 for the following bugs:
Bug 1472893: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXRTINV form in Oracle Apps as that user
Bug 1472892: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the SFXPNDQS form in Oracle Apps as that user
Bug 1470296: Oracle user names (USER_ID) longer than 30 characters resulted in error when opening the Workflow Role Select form in Oracle Apps as that user
Bug 1469054: Oracle user names (USER_ID) longer than 30 characters resulted in error when trying to launch the Working Folder as that user
If you do not experience any of the listed issues or if you have already applied this fix, skip these steps. You may skip the steps for any form which you do not use.

To apply FIX12715:

1. Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.

2. Copy SFXWKFDR.fmb, SFXURSEL.fmb, SFXPNDQS.fmb, SFXRTINV.fmb files from:
   <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX12715
   To:
   $c_MARKVIEW_TOP/MVOA/6.1.0.0/forms
   where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

3. Back up the previous versions of $c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/*.fmx files.

4. Important: Add the AU_TOP/forms/US path to the FORMS_PATH variable:
   

   FORMS_PATH=$FORMS_PATH:$AU_TOP/forms/US

   Note:If you skip this step, the forms may be still successfully compiled but they may not work correctly.

5. Compile SFXWKFDR.fmb into SFXWKFDR.fmx using your valid connection string value:
   

   frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/SFXWKFDR.fmb module_type=FORM compile_all=YES

   Note: If you copy and paste from this file, remove any line breaks.

6. Compile SFXURSEL.fmb into SFXURSEL.fmx using your valid connection string value:
   

   frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/SFXURSEL.fmb module_type=FORM compile_all=YES

   Note: If you copy and paste from this file, remove any line breaks.

7. Compile SFXPNDQS.fmb into SFXPNDQS.fmx using your valid connection string value:
   

   frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/SFXPNDQS.fmb module_type=FORM compile_all=YES

   Note: If you copy and paste from this file, remove any line breaks.

8. Compile SFXRTINV.fmb into SFXRTINV.fmx using your valid connection string value:
   

   frmcmp userid=apps/apps-pw@connectstring module=$c_MARKVIEW_TOP/MVOA/6.1.0.0/forms/SFXRTINV.fmb module_type=FORM compile_all=YES

   Note: If you copy and paste from this file, remove any line breaks.

9. Back up the previous versions of $c_MARKVIEW_TOP/forms/US/*.fmx files.

10. Copy the compiled SFXWKFDR.fmx, SFXURSEL.fmx, SFXPNDQS.fmx, SFXRTINV.fmx forms from:
    $c_MARKVIEW_TOP/MVOA/6.1.0.0/forms
    To:
    $c_MARKVIEW_TOP/forms/US

Apply FIX16695

Starting from version 10.0.0.8, the fix pack contains FIX16695 for the following bug:
Bug 1734082: After applying the Oracle patch for the Log4j vulnerability, MarkView negatively impacted core Oracle functionality.
If you do not experience the same issue or if you already applied this fix, skip these steps.

To apply FIX16695:

1. Log in to the operating system where the Oracle ERP server is installed as the owner of the Oracle ERP system.

2. Change the directory to <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX16695:
   

   cd <MARKVIEW-INSTALL-DIR>/misc/10.0.0/FIX16695

   where <MARKVIEW-INSTALL-DIR> is the base directory where MarkView is installed.

3. Extract the files from mvoa_patch.zip archive into $JAVA_TOP directory:
   

   unzip -o -d $JAVA_TOP mvoa_patch.zip

4. Change the directory to $JAVA_TOP:
   

   cd $JAVA_TOP

5. Optionally remove log4j classes from $JAVA_TOP if they exist:
   

   rm -f log4j.jar log4j.properties
   rm -rf org/apache/log4j
   rmdir --ignore-fail-on-non-empty org/apache org

6. For Oracle EBS 12.2.x only:

   1. Back up the previous version of $JAVA_TOP/customall.jar file.

   2. Run adcgnjar utility to recreate and sign $JAVA_TOP/customall.jar file:
      

      adcgnjar

      (Enter APPS schema name and password when prompted.)

7. Restart the Oracle ERP system.

Issues Resolved in This Fix Pack

Issues Resolved in Previous Fix Packs

Issues Resolved in Fix Pack 8 (10.0.0.8)

Issues Resolved in Fix Pack 7 (10.0.0.7)

Issues Resolved in Fix Pack 6 (10.0.0.6)

Issues Resolved in Fix Pack 5 (10.0.0.5)

Issues Resolved in Fix Pack 4 (10.0.0.4)

Issues Resolved in Fix Pack 3 (10.0.0.3)

Issues Resolved in Fix Pack 2 (10.0.0.2)

Issues Resolved in Fix Pack 1 (10.0.0.1)