Sage 100

 View Only
  • 1.  Can someone test this? In v4.4 PU6, a patch was r

    Posted 11-15-2011 19:45
      |   view attached
    Can someone test this? In v4.4 PU6, a patch was released to correct a GL posting issue when creating a JE in bank reconciliation. It didn't seem to work after installing the PU and it still doesn't after install PU7. The JE is created but doesn't post to the GL. A source journal register transaction is advanced in journal maintenance and the transaction is posted to paperless. If memory serves me, they had this problem PR transactions two years ago.


  • 2.  RE: Can someone test this? In v4.4 PU6, a patch was r

    Posted 11-16-2011 12:49
    With v4.4 PU7 I entered a check in BR, printed the BR Transaction Register, updated, then printed the Daily transaction Register and updated. The entry wass posted to GL.


  • 3.  RE: Can someone test this? In v4.4 PU6, a patch was r

    Posted 11-16-2011 13:45
    What version was the client set up in? In reading the resolution ID post, it seems that it only affects those companies created after the 4.4.3 release. The resolution does give a solution (flip the flag on field 9 to Y (it will be blank if it isn't working) in the BR_options table.


  • 4.  RE: Can someone test this? In v4.4 PU6, a patch was r

    Posted 11-16-2011 13:49
    It was v4.4 PU4 which i upgraded to PU7


  • 5.  RE: Can someone test this? In v4.4 PU6, a patch was r

    Posted 11-16-2011 14:02
    Thanks for the feedback!! The company was created in v4.4.4? Here is an exerpt from the resolution. Bank Reconciliation does not post to General Ledger in version 4.40 in Sage MAS 90 and 200. Entry Type: Program Issue Product: Sage MAS 90 ERP Sage MAS 200 ERP Application: Bank Reconciliation Version Reported: 4.40.0.3 (still occurs in pu 4) Status: Resolved in product update 6 for version 4.40. Subject: Bank Reconciliation does not post to General Ledger in version 4.40 in Sage MAS 90 and 200. Steps to Duplicate: Issue seems to only occur with new company codes created in 4.40.0.3 or higher. In my case, this was a new install at v4.4.5 back in May. FWIW, the issue is resolved in v4.5.


  • 6.  RE: Can someone test this? In v4.4 PU6, a patch was r

    Posted 11-16-2011 14:52
    The company i tested this in was created before v4.4.