You are correct if at every level the Allow OUTQ override and Allow
attribute overrides is marked "Y".
Otherwise it goes from bottom up until it meets a "N" in those entries.
So my #9 Report definition has precedence over 4 User/Report because it
is marked Allow overrides "N".
So is all of this definitely hard coded? It would have nice if there
was a list that could be adjusted to change the hierachy.
Greg
-----Original Message-----
From: Kevin Fox [mailto:kdfox@xxxxxxxxxxxxx]
Sent: Wednesday, October 28, 2009 12:45 PM
To: 'MAPICS ERP System Discussion'
Subject: Re: [MAPICS-L] CAS - Printer Override Maintenance
Greg
It is defined in CAS and is "hard wired" as follows:
1. Session
2. Workstation
3. User
4. User/Report
5. Company
6. Company/Report
7. Warehouse
8. Warehouse/Report
9. Report
10. Group
For example, session overrides workstation, workstation overrides user,
user overrides user/report.....
As you can see, user/report(4) takes precedence over report (9).
Kevin
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
