Other ERPsFree worksheetPDF, Excel, Word exportQAD

QAD Menu Program Reference Template

Every QAD site ends up with a few people who know the program names by heart and a lot of people who do not. This worksheet turns that knowledge into a table you can export to Excel for training, access reviews and migration planning.

Download:
ProgramDescriptionModuleMenu path or numberUsageChanges data?Role that needs itUsers
Total user assignments
86
Programs listed
6

The example programs are common QAD names, but program names, menu numbers and labels vary by site, version and customization. Verify every row against your own menu before relying on it. Add custom programs and mark them in the notes column of your own copy.

Generate this from your QAD usage data

We can show a read-only way to build the program inventory with last-used dates from your own logs.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

Start with the programs your team uses weekly. Add a row for each, copy the menu path from your own system, and note whether it changes data. Then add the role that needs it and an approximate user count. The totals show how many assignments you have. Export to Excel and share with auditors and trainers.

  • Start with daily programs, then add weekly ones
  • Copy menu paths from your own system
  • Mark programs that change data
  • Record the role, not individual names

Why a program reference matters

QAD menus are organised by function, but people search by program name, because the program name is what appears in the title bar, in tickets and in security setup. A current reference shortens onboarding, makes tickets precise, and gives auditors an artifact for who can change what. It also becomes the starting inventory when you plan an upgrade or a move to a newer architecture.

Using it for access reviews and migration

Sort by the writes column and role. Any data-changing program with a large user count is worth a second look. During migration planning, the same table helps you decide which programs are standard, which are customized and which can be retired because nobody has used them in a year. Add a column in Excel for last-used date if you can pull it from your logs.

Common mistakes

The most common error is copying program names from a training document that predates your version. Another is mixing standard and customized programs in one list without marking which is which. A third is listing individual users instead of roles, which makes the sheet outdated after every personnel change. Keep it role based and review it each quarter.

Frequently Asked Questions

Are the program names in the examples exact?

They are common QAD program names for core functions, but you should confirm them against your own system. Names, menu numbers and labels differ by version, language and customization, so treat the examples as a starting format.

Can I use this for a QAD security audit?

Yes as a supporting artifact. Combine it with your actual security configuration export. The worksheet shows intent and ownership, but the system configuration is the evidence of who actually has access.

How do I find the program name behind a screen?

In most QAD interfaces the program name appears in the title bar or can be shown from the menu or help. Check your version documentation or ask your administrator for the exact method on your site.

Does this export to Excel?

Yes. Use the export controls to download the table as Excel, CSV or PDF. You can then add columns such as last used date or control owner.

If you want this reference generated from your actual QAD menu and usage logs, Netray can build a read-only extract and keep it current.