Submit Your Suggestions for Vista

Last updated field would be super-useful in PR Deductions / Liabilities, especially for those that are not updated annually.

We  also need this, Our auditors are constantly asking for this information.  We use a user-defined field to currently tract this in payroll. We need a way for invoices, and we use the processing group field to assign our billing clerks to a job. It would be great to have this added as a selling feature of the software. Andrew Karr has the correct idea in his post!  This is a similar idea to the one about who is posting notes in the system, although this idea is a much more complete solution.

Agreed to the need for this.  With the size of our database, having these fields would allow for incremental refreshes into an offline reporting system (ODS or DW) with minimal impact to transactional processing.  Some tables have other date fields that can be used (AP, AR, & Payroll tranaction dates) but others do not (e.g. Job Cost Detail).  In our case, some of these tables the warrnat these fields are getting to the 20 million row level.

This is necessary for internal audit, external audit, security, other controls, and reporting!!  Having to use the HQ Audit table as the 'master'  table and then go search for additional data to see the whole picture is very time consuming.  Additionally, finding out when a record was "inserted" is also hindered by the table's key field only appearing in a string of information in the audit table.  In the mean time it would be helpful to add a column to the HQAuditDetail table with the key field only, so it is quicker and easier to find adds/changes to a particular vendor number, employee number, SL record, etc.  If we are trying to find who created/updated a record and we have to already know the table name, the key field should also be known.

This would be huge for reporting also, would make it so much easier.

Thank you for the details - they are appreciated.  Based on this detail, I've moved this to the "nice" list and we'll see when we can fit it in.

I agree that Master tables will be good place to start especially Company Parameters (PR, HQ, AP,AR, JC, JB, HR , CM, EM, GL, PO, SM, PM) . Also PR/HR Employees, AP Transactions, AR Customers, AR Invoices, Job Master, AP Vendors, CM Accounts, PR Group Master, PM Projects, SM Work Orders and SM Invoices would be great to have first.

Hi Eric,

I guess the first ones will be PR/HR Employees, AP Vendor Master, AR Customers, PM Projects, PM Contracts, JC Jobs Master, JC Contracts, AP Invoices, PO Purchase Orders, JB Billing, PR Timecards. This will be a good starting point but ideally all tables as soon as possible.

R,

[cid:image001.gif@01D24ED4.CD945790]

Jas Coetsee
Project Manager | Kawana
T 07 5413 5400 | F 07 5438 8972 | M 0427 109 351
E Jas.Coetsee@goodline.com.au | W goodline.com.au
PO Box 1541, Buddina QLD 4575 | ABN 40 085 847 892

This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments. This notice must not be removed.
Please consider the environment before printing this email.

This would be in the area of the Master Audit tables.  I would recommend pinging the voters to get their ideas.  Putting myself in a customers shoes, I would say PR Employees, PR Timecards, AP Vendors, AP Transactions, JC Job, JC Contract, MS Tickets, JB Progress Entry, GL Journal Entries, HQ Materials, etc...

Great idea, but a significant amount of work.  It may be implemented in specific areas before others, rather than all at once.  Is there a specific set of record types that are most desired for this capability?