Re: CAS - Printer Override Maintenance

Hi Kevin,

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:[email protected]] 
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
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.