Votes

3

All fields from an Entry screen need to available in ONE Explorer inquiry, not segregated into "Header" and Lines Explorers

by: DAVID G. | over a year ago | 4 - Reports / BI
Cast your vote or comment ...
return to idea list

We are using "Sage ERP MAS 500 June 2012 Update (Version 7.40.4.0)". It is not possible to see all fields related to several of the data entry forms (Enter Sales Order, Enter RMA, View/Edit Invoice, etc.) on ONE Explorer lookup. It appears to me that the tables in the data base for these forms are divided into "header" and "lines" tables, and Explorer lookups/inquiries are similarly divided, such as Explore RMAs and Explore RMA Line, Explore Sales Orders and Explore Sales Order Lines, etc. Yet as a user, I don't make such distinctions. If I want to know, for a give Item, which Salesperson has sold the most, I have to export to Excel the results of Explore Sales Order Lines, and Explore Sales Orders, then use Excel Functions INDEX and MATCH functions to pull data from one export into the other export. To me, the user, I should have 1 Explorer give me access to EVERY field I see on the Enter Sales Order screen. I don't care if behind the scenes, those fields are divided into 99 tables, to me it is ONE "set" of data and I should be able to export all the fields into one spreadsheet and manipulate it however needed. Perhaps later versions have this capability. If so, yahoo, can't wait to upgrade! If not, please talk to programmers and implement this idea. It will save untold hours for your users!

by: DAVID G. | over a year ago | 4 - Reports / BI

Comments

  • There is an enhancement request at this site titled "Add fields to out-of-the-box BI reports" that also addresses the fact that many of the BI reports are missing fields. This has been a problem with the native Sage 500 BI reports for as long as they have existed.

    by: Ralph A. | over a year ago

  • It's actually more of a parent-child relationship where there exists a one to many paradigm. An example would be where a sales order has a single identifying transaction number and customer but may contain many lines with different items, quantities, shipping information and dates. Adding all that data into a single explorer view wouldn't work for many businesses. There are a large number of columns through those tables and I have seen hundreds of lines items for a document so it would be a repeat of the header (parent) hundreds of times with only information changing on the lines.

    You can pretty easily add your own Explorer views, so that is an option, but you may want to review the table schema and diagrams available in System Manager / Schema Browser.

    by: Steve C. | over a year ago