Skip to main content

MarkView Invoice Audit - What diagnostic steps should I follow and what information should I gather when there is an issue with the MarkView Invoice Audit functionality?

Article # 304270 - Page views: 146



Applies To

  • ERP System: Oracle, SAP
  • MarkView Version: 7.0.2

Note: for 7.1 customers this functionality will be included in the first Service Pack 7.1.1


  • When running Invoice Audit to batch print a group of MarkView documents there are a few errors which may occur. The following is a list of those error messages as well as the common scenarios which may cause them.
    • Invalid invoice or no MarkView Documents
      • The requested Invoice does not exist.
        • Check the CSV file and your ERP system to ensure that the Invoice is valid and that the data was entered into the CSV file correctly.
        • Check the CSV file to ensure that the data entered matches the header. (That is that the OrganizationID/Company Code wasn't entered under the InvoiceID header for example.)
      • SAP Customers - the Fiscal Year of the invoice has been rolled over in SAP but not MarkView.
        • For performance reasons the Invoice Audit functionality does not check to see if the Fiscal Year of the invoice was rolled over in SAP. If you receive a message indicating that the Invoice is invalid and it was recently rolled over in SAP you can take one of the following options.
          • Open the document in the MarkView Viewer which will automatically update the Fiscal Year. You can then print directly from the Viewer, or resubmit the Invoice Audit request which should successfully print the document.
          • Run the Explicit Rollover process against the MarkView schema to update all of the active invoices in MarkView to ensure they are associated with the correct SAP Document. Resubmit the Invoice Audit request which should successfully print the document(s).
  • No print privileges
    • This issue will occur if the user performing the Invoice Audit printing is not part of a MarkView group that has privileges to actually print the Document Type. To resolve the issue ensure that the user has the correct privileges to print the Document Type.


  • If additional details are needed debug logging for the Invoice Audit functionality can be enabled by following the steps below.

Enable Debug Logging

  • Set the MVERP_SERVICE_LOGGING_LEVEL preference to DEBUG.
  • Restart the MarkView Middle Tier.

Disable Debug Logging

  • Set the MVERP_SERVICE_LOGGING_LEVEL preference to WARN.
  • Restart the MarkView Middle Tier.

Log File Location

Impact of Debug Logging

  • The erp-services log file will grow to 5000KB and will keep 3 backup copies of the log file before automatically overwriting them. In this case the maximum hard drive space taken up by the erp-services log file is 15000KB. If the log file exceeds the maximum size it will automatically overwrite the oldest information.

Keywords: diag, info