Sage 100

 View Only
  • 1.  Sage Intelligence report conversion from FRx. I ha

    Posted 11-17-2015 10:44
    Sage Intelligence report conversion from FRx. I have converted the reports from FRx using the defined row and column formats. The client has several GL's listed in groupings in the Row Format, and uses wildcard function very heavily. Not only that but they use the same report layout for several different company codes in which a specific GL may or may not exist. I need to format a detail report that will take a reference from the conversion like ????-620-??? and display all the GLs that fit this criteria dynamically for any given company code. Has anyone had any experience with something like this? I have the reports as laid out in FRx Row and Column formatting done. But does anyone know how to get the detail GL listing from FRx in row format for Sage Intelligence?


  • 2.  RE: Sage Intelligence report conversion from FRx. I ha

    Posted 11-17-2015 10:55
    I think it's going to be a manual process to match against the coa or run the detail reports from FRx and if you can copy/export to excel and then copy to your SI report. SI just doesn't support that detail level very well.


  • 3.  RE: Sage Intelligence report conversion from FRx. I ha

    Posted 11-17-2015 11:13
    @KimberlyDavis You can add a column to the column format to print the GLACCT, make the length 60+ to make sure you get everything,


  • 4.  RE: Sage Intelligence report conversion from FRx. I ha

    Posted 11-17-2015 11:15
    @KimberlyDavis i forgot to mention to generate the report to Excel, right?


  • 5.  RE: Sage Intelligence report conversion from FRx. I ha

    Posted 11-17-2015 11:22
    This is what I thought...so sad. Do you know if there is a way to run an Frx report to excel and have it not hide the rows that are reporting zero? Doug I am not sure what you mean to add a column to the column format. I have all the GL's in the Row already, but they look like this...(3???-010-??? TO 4999-050-???) -(3760-030-000 TO 3810-040-000) -(3530-010-000 TO 3532-010-000) -(4530-050-000) -(4920-050-000 TO 4926-050-000) -(4300-050-???) -(4685-050-000) -(4640-050-000 TO 4649-050-000) -(4950-050-000) -(4650-050-000) -(3550-010-000) -(4550-050-000) -(4927-050-000) +(4646-050-000) -(4301-050-000) -(3755-030-000).... this is just one row. I need to make another report that lists each of these accounts individually on a row and will incorporate several different company codes gl chart even though it may not be used. What do you think just an extremely manual process?


  • 6.  RE: Sage Intelligence report conversion from FRx. I ha

    Posted 11-17-2015 11:28
    There is an option in the Column Definition to print account numbers on the report. you can insert a column heading and print the GL account numbers listed in the Row setting. Your situation is not typical and the width of the column is limited. Given the example you are showing, i don't think you can get what you want.


  • 7.  RE: Sage Intelligence report conversion from FRx. I ha

    Posted 11-17-2015 11:30
    Thanks so much for trying to help me out!


  • 8.  RE: Sage Intelligence report conversion from FRx. I ha

    Posted 11-17-2015 14:33
    Can set the GL Accts column width (in Column Layout) to a max of 255 in FRx to minimize truncation. Also, there is a report option in FRx to show zero rows. I had one client that still had more than 255 characters for their GL Link - they ended in "" ..."" as you noted - for over a dozen rows and it was common in over a dozen reports. I copied both the row description (ex. Payroll Expenses) and the associated truncated GL Link into a blank spreadsheet. I then went into FRx Row Format and copy/pasted the full GL Link to replace the truncated one in my spreadsheet list. Now I had an easier copy/paste to fix the truncated GL Links from my spreadsheet list into the exported reports. Yes, still manual, but using Excel's search for the truncated row and the easier copy/paste from the other spreadsheet, it saved me hours and gave me some control and consistency when working with many complex reports. I hope this lessens the pain.