Combined Hot Fix for Four Accounts Payable Report Issues

  • Created:
  • / Author: tombucci
Issue

 

This Hot Fix addresses the following issues. These fixes have been incorporated into Sage Pro ERP 7.4 Build 3400.

  • PTR 81146 (original Hot Fix) – Some Vendors May Not Appear in As of Aging Report if Using Microsoft SQL Version and Multicurrency
  • PTR 65119 (Added to Hot Fix 6/27/2006) – Aged Payables Report Using Report Type Set to Transaction Posting Date May Not Report Currency Balances
  • PTR 80329 (Added to Hot Fix 6/27/2006) – Invoice Register Report May Be Incorrect When Voiding And Reusing An Invoice Number For A Vendor and using Microsoft SQL Version of Sage ProImportant
    It is not recommended to reuse invoice numbers for a vendor. Audit trails are difficult to follow and this may create performance issues with the As of Aging Report. Add an “A” or “1” at the end of a reused invoice number to avoid these issues.
  • PTR 83747 (Added to Hot Fix 8/4/2006) – AP-PO Audit Trail Report May Experience Performance Issues If Large Data and Using Microsoft SQL Version of Sage Pro

 

 

Special Considerations or Warnings

None.

Solution or Workaround

This Hot Fix addresses PTRs 81146, 65119, 80329, and 83747.

Hot Fix files included (in the AP program folder):

  • APREPT.FXP
  • APREPT.PRG

Important Notes:

  1. PTRs 81146, 65119, 80329, and 83747 have been fixed as of Sage Pro ERP 7.4 Build 3400.
  2. PTRs 81146, 83747 and 80329 only occurs with the Microsoft SQL Server (SQL) version of Sage Pro, not with the Microsoft Visual FoxPro version.
  3. PTRs 81146 and 65119 only occur when using Multicurrency (MC). They do not occur if MC is not used, even when using SQL.
  4. Back up affected program files and data before applying Hot Fix.
  5. Apply Hot Fix in a test environment to ensure proper results before implementing in a live installation.
  6. Verify that Hot Fix files will not overwrite any modifications. If there are modified files, a qualified Sage Certified Consultant familiar with the modifications should be used to integrate the changes.

 

This Hot Fix addresses the above behaviour. Please follow the instructions included in the attached readme to implement this Hot Fix.

HF21995_4APReportIssues_Pro73B_B3301 (2)

© Copyright Sage Software

 

Leave A Comment?