How to add a column to price sheets?

SOLVED

Hi All,

First post, a little bit about myself: I'm an IT intern for a small manufacturing company in Northern Colorado, I've been given some projects that involve MAS 500, mainly report customization. There currently is no on-site IT staff, so I've come here for a bit of insight.

So, I'm looking to add a column to a grid; specifically our price sheets. (Inventory Management > maintenance > Maintain Prices > Price Sheets)

As they are, we have an item # and associated pricing attributes, but many users of the system are requesting we add an 'Item Description' to the gird. After some research I've found that reports and lookups are generated through SQL views, and that MAS is meta-data driven; so there should a record in a table that contains the columns to be returned for the price sheets. 

I've searched in the 'tsmLookupView' tables, and haven't found anything matching our price sheet; and haven't found a view that returns our pricing information. I have run a SQL trace, and found the SQL query that is being executed when calling the price sheets, but haven't found where to edit that statement and to add any meta-data for the price sheet.

Any assistance or insight would be appreciated!

  • 0
    verified answer

    Unfortunately the task Maintain Price Sheets is not built using Meta-Data.  It is a standard VB 6 program.  In order to add an additional column to the grid, you will need have a modification done to the source code.  This will require the Sage 500 SDK as well as the source code for the IM Module.  Customizer is not a viable solution for this as it is "quirky" when working with grids in Sage 500 depending on the task being customized.

    From your post it appears you may not havethe SDK or source code, so if you need this customization done I would suggest contacting your reseller to see if they could do it or sub-contract the work to a reseller such as E2B Teknologies to do the work.

    In regards to underlying views being used for lookups you are correct.  Views are also used to populate the various Business Insights Explorers in Sage 500 with data.  However, for report tasks that generate a Crystal Report file, these are created using work tables and stored procedures to populate those.  The task that creates the Crystal Report is responsible for this.

    I hope this helps.

  • 0 in reply to LouDavis

    Thanks for the input Lou! We do have a re seller that actively supports our system, I'll get in contact with them. If I manage to get access to an SDK and source code, would you consider this to be a very complicated task?

    I'm trying to gain as much experience as possible, rather than contract the work out. Though I realize some tasks are better left for the professionals.

  • 0 in reply to elliottN

    The modification you describe wouldn't be that complicated. However, it may take you a bit a bit longer than someone who is familiar with the SDK Framework.   This forum as well as forums on LinkedIn are good places to go if you have any questions if you undertake this.