Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager
    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. When using extended fund allocation with percentages, amounts don't match in all tables

    When using extended fund allocation with percentages, amounts don't match in all tables

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Symptoms
    2. Defect Status
    3. Replication Steps
    4. Workaround
    • Product: Voyager
    • Product Version: 9.2.0, 9.2.1
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Symptoms

    • Using extended fund allocation, amounts stored in PO_FUNDS / LINE_ITEM FUNDS and INVOICE_FUNDS / INVOICE_LINE_ITEM_FUNDS don't match.
    • Amount in LINE_ITEM_FUNDS and INVOICE_LINE_ITEM_FUNDS off by $0.01

    Defect Status

    Issue VYG-6851 is resolved in Voyager 9.2.1 and higher.

    Replication Steps

    1. Create purchase order (PO)
    2. Add line item with price $208.09
    3. Click Detailed Line Item > Copies/Funds
    4. Edit funds > Extended Fund Allocation
    5. Using Percentage, allocate this total across four different funds
      1. 33% (68.6697)
      2. 37% (76.9933)
      3. 16% (33.2944)
      4. 14% (29.1326)
    6. Save
    7. Totals in client show additional penny added to first fund:
      1. 68.68 (66.6697)
      2. 76.99 (76.9933)
      3. 33.29 (33.2944)
      4. 29.13 (29.1326)
    8. Total for first fund (33% allocation) is 68.67 in PO_FUNDS and INVOICE_FUNDS, and 68.68 in LINE_ITEM_FUNDS and INVOICE_LINE_ITEM_FUNDS

    Workaround

    Use amounts instead of percentages for extended fund allocation.


    • Article last edited: 21-Mar-2017
    View article in the Exlibris Knowledge Center
    1. Back to top
      • When trying to run a query in Voyager Prepackaged Access Reports get error "The Microsoft Access database engine cannot find the input table or query..."
      • When using Microsoft Access get errors like "Microsoft Office Access database engine cannot open or write to the file"
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      1. Acquisitions
      2. voy-resolved-9
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved