• Replies 5 replies
  • Subscribers 414 subscribers
  • Views 39 views
  • Users 0 members are here
Related

Report Displaying Wrong FY

Amy Aldrich
$organization

Can anyone please tell me where in ticketing set up does the data feed into the "Transactions by Posting"  report in the column labeled  "Fund/Pmap/Fee/Payment" ?

We have revenue showing up there, but its labeled incorrectly. Its showing that is from the 09 season but its really the 10 season. The money is tied to the correct GL #. I have searched high and low and everything seems to be correct in terms of setup, so I am not sure where to fix this data that is appearing in the  "Fund/Pmap/Fee/Payment" column on this report.

Thanks!

Amy Aldrich

Ticket Operations Manager

Boston Symphony Orchestra

www.bso.org

aaldrich@bso.org

Parents
  • $organization

    That column just lists the description of the fund, price map, fee, or payment method that caused the transaction.  If the season is wrong either the description for your price map or fee is wrong or the price map or fee has the wrong GL assigned.  For example if GL 1234 has a transaction for a price map of 09 Single Tickets, that means a price map with a description of 09 Single Tickets has GL 1234 assigned.  Take a look at price map 10 Single Tickets and see if it was given the wrong description (like someone put 09 on it instead of 10) or selected the wrong GL.

     

    This report doesn’t actually do anything with fiscal year or seasons.  They will only be reflected if you include them in the descriptions of your funds, price maps, fees, and payment methods.

Reply
  • $organization

    That column just lists the description of the fund, price map, fee, or payment method that caused the transaction.  If the season is wrong either the description for your price map or fee is wrong or the price map or fee has the wrong GL assigned.  For example if GL 1234 has a transaction for a price map of 09 Single Tickets, that means a price map with a description of 09 Single Tickets has GL 1234 assigned.  Take a look at price map 10 Single Tickets and see if it was given the wrong description (like someone put 09 on it instead of 10) or selected the wrong GL.

     

    This report doesn’t actually do anything with fiscal year or seasons.  They will only be reflected if you include them in the descriptions of your funds, price maps, fees, and payment methods.

Children
  • $organization in reply to Kevin Sheehan

    Amy, quick clarification of our points here.  Kevin is referring to a situation where you have GL Accounts created separately for each fiscal year.  I was referring to the fiscal year associated at the time of posting based on the campaign of the transaction.  You probably have an incorrectly mapped GL Account in either the Fee or Price Map.  Check the price maps in Facility Manager, or you can click the Details button in the Pricing tab of the Performance Details screen, which will show you information about the price map that is highlighted.

     

    Another key point about the Transactions by Posting report is that it does use the GL Account that was associated to the price map (or fee, fund, etc) at the time the transaction occurred.  So if the price map was associated to GL 1234 on January 1, and was changed to GL 5678 on May 1, transactions occurring before May 1 will be associated to GL 1234.  Changes in mapped GL Accounts are maintained in the system table T_GL_ACCOUNT_HIST.

     

    ______________________________________

    Ryan Creps

    Network Developer |Tessitura Network, Inc

     

    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Kevin Sheehan
    Sent: Monday, June 01, 2009 8:50 AM
    To: Ryan Creps
    Subject: RE: [Tessitura Ticketing Forum] Report Displaying Wrong FY

     

    That column just lists the description of the fund, price map, fee, or payment method that caused the transaction.  If the season is wrong either the description for your price map or fee is wrong or the price map or fee has the wrong GL assigned.  For example if GL 1234 has a transaction for a price map of 09 Single Tickets, that means a price map with a description of 09 Single Tickets has GL 1234 assigned.  Take a look at price map 10 Single Tickets and see if it was given the wrong description (like someone put 09 on it instead of 10) or selected the wrong GL.

     

    This report doesn’t actually do anything with fiscal year or seasons.  They will only be reflected if you include them in the descriptions of your funds, price maps, fees, and payment methods.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

    No virus found in this incoming message.
    Checked by AVG - www.avg.com
    Version: 8.5.339 / Virus Database: 270.12.45/2141 - Release Date: 06/01/09 06:09:00

  • $organization in reply to Ryan Creps (Past Staff Member)
    Thanks Everyone for your help! I figured it out. I had copied a price
    map and didn't change the name to "10", I just left it as "09." Our
    posting reports showed that the income was being posted to the right GL,
    but it was freaking out the business office that the wrong FY was
    showing on this report.

    Thanks again, I couldn't have done it without your helpful advice!
    Amy

    >>> "Ryan Creps" 6/1/2009
    12:15 PM >>>

    Amy, quick clarification of our points here. Kevin is referring to a
    situation where you have GL Accounts created separately for each fiscal
    year. I was referring to the fiscal year associated at the time of
    posting based on the campaign of the transaction. You probably have an
    incorrectly mapped GL Account in either the Fee or Price Map. Check the
    price maps in Facility Manager, or you can click the Details button in
    the Pricing tab of the Performance Details screen, which will show you
    information about the price map that is highlighted.

    Another key point about the Transactions by Posting report is that it
    does use the GL Account that was associated to the price map (or fee,
    fund, etc) at the time the transaction occurred. So if the price map
    was associated to GL 1234 on January 1, and was changed to GL 5678 on
    May 1, transactions occurring before May 1 will be associated to GL
    1234. Changes in mapped GL Accounts are maintained in the system table
    T_GL_ACCOUNT_HIST.


    ______________________________________
    Ryan Creps
    Network Developer |Tessitura Network, Inc



    From:Tessitura Ticketing Forum
    [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Kevin
    Sheehan
    Sent: Monday, June 01, 2009 8:50 AM
    To: Ryan Creps
    Subject: RE: [Tessitura Ticketing Forum] Report Displaying Wrong FY


    That column just lists the description of the fund, price map, fee, or
    payment method that caused the transaction. If the season is wrong
    either the description for your price map or fee is wrong or the price
    map or fee has the wrong GL assigned. For example if GL 1234 has a
    transaction for a price map of 09 Single Tickets, that means a price map
    with a description of 09 Single Tickets has GL 1234 assigned. Take a
    look at price map 10 Single Tickets and see if it was given the wrong
    description (like someone put 09 on it instead of 10) or selected the
    wrong GL.

    This report doesn’t actually do anything with fiscal year or seasons.
    They will only be reflected if you include them in the descriptions of
    your funds, price maps, fees, and payment methods.



    This message was sent automatically to you by www.tessituranetwork.com
    because you subscribed to the Tessitura Ticketing Forum. You may reply
    to this message to post to the Ticketing forum or visit the site to
    search, read and post to the forums. In the interest of keeping the
    forum posts from becoming cluttered, we encourage you to delete previous
    message text from your reply before sending. Thank you!
    No virus found in this incoming message.
    Checked by AVG - www.avg.com
    Version: 8.5.339 / Virus Database: 270.12.45/2141 - Release Date:
    06/01/09 06:09:00



    This message was sent automatically to you by www.tessituranetwork.com
    because you subscribed to the Tessitura Ticketing Forum. You may reply
    to this message to post to the Ticketing forum or visit the site to
    search, read and post to the forums. In the interest of keeping the
    forum posts from becoming cluttered, we encourage you to delete previous
    message text from your reply before sending. Thank you!