 |
 |
> While I can certainly understand your predicament with SAP access on > Macs and other OS, enabling SAP GUI for Java client is not a feasible > business approach, for several reasons: > 1. Portal would need to be reconfigured to accept SAP GUI for Java > 2. New Access/Security roles would need to be created and issued > to those using SAP GUI for Java (or we would need to redeploy the GUI to > all users [switch them from current SAP GUI for Windows]) > 3. EBS infrastructure would need to be verified/changed to use the > SAP GUI for Java (changes to development, applications, etc.) > 4. Changes would be required to online and hard copy user > documentation of the system (screens look and sometimes behave > differently between the SAP GUI clients) > With these changes there would need to be full regression tests of the > SAP links and workflow processes to make sure all functionality works > under the new configuration. This change would likely require a new > project be invoked (with the major cost and time implications that come > with it). Ok, whoever wrote the above: 1. There should be no regression tests needed. It should have been built that way from day one. 2. Get over your head in the sand problem with Macs. There are lots of them on campus, many used by the staff who deal with the U business systems and procedures most heavily. The world is not entirely made of Windows. You had a cross-platform alternative. Why in the world did you not choose it in the first place?! And I don't want to hear a support cost argument. All you've done is push the support cost out to units that already don't have the budget to spare. De