Printing is somewhat more complex for SAPGui for Java when compared with it's Windows cousin. Like always you should define a printer with access method 'G' (see SAP note 821519 (http://service.sap.com/sap/support/notes/821519) - Front-end printing with control technology) and have the host printer named "__DEFAULT". It is important you should have a SAP printer definition for the printer itself. Formatting is done at the SAP application server and not, as is the case with SAPWIN, on the client. If the default printer on the Mac is not the preferred printer for SAP, the preferences panel offers the option to assign specific SAP queues to OS X printer queues. Unfortunately not all transactions can be used with SAP GUI for Java. Refer to the transaction classification (transaction SE93) to see if SAPGui for Java is supported. The transaction clearly indicates which SAPGui variants are supported.
An example of unsupported transactions are those which directly interact with MS Word. The transaction 'solution_manager' is able to generate an EWA report with the help of MS Word and Visual Basic for Applications on a Windows computer. When started on a Mac the ABAP transaction aborts with the message "Exception condition "JAVABEANNOTSUPPORTED" raised. Due to the way a Mac handles it's function keys, quick navigating can be rather complex. For example if one uses the ‘spaces' function on a MacBook Pro the default hotkey will be F8. One needs the fn + key to actually use the fn keys. The usage of shift+fn to generate for example F24 for page down does not work on a laptop keyboard. With the preference pane "Keyboard" the function key assignment can be adjusted. h3. SAPGui Scripting According to the document SAP GUI Scripting Scripting User Guide (http://www.synactive.com/download/sap%20gui%20scripting/sap%20gui%20scripting%20userguide.pdf) it should be possible to use AppleScript in combination with the SAPGui. Unfortunately the AppleScript editor returns an error message. It seems that the scripting functionality is no longer functioning anymore, at least with the current 7.20 revision 2 release of the Java Gui. 
According to SAP officials, AppleScript used to be part of the SAPGui for Java offering. The current status is that it is propriety software of Apple Inc. I'm trying to convince SAP and Apple to re-release the scripting functionality. It seems that I'm the first one since 2007 digging into this subject. h3. Office Integration Office integration is limited. Although Microsoft maintains binary compatibility between the Windows and Macintosh versions for quite some time, integration with the SAPGui does brings its difficulties. First of all Microsoft has removed the Visual Basic scripting facilities in Office 2008. As a consequence SAP programs who rely on VB scripting will fail. An example of this is the functionality to download Early Watch Alert reports from the SAP solution Manager. But also a simple download of data from an ABAP ALV grid can bring confusion to Excel. Although the file extension is "xls", Excel tries to read it as a text file. Sometimes all data is loaded in a single column.
But remember you must save the file first to the client. After this first step you need to manually open the file. h4. NetWeaver Business Client for Desktop Unfortunately the NetWeaver Business Client for Desktop is still a Windows only program. h4. Web Browsers Currently (PAM April 2010) SAP officially supports the following browsers: Firefox 3.5 and Safari 4 on Mac OS 10.5 and 10.6. More precise the Web Application Server (ABAP or JAVA) should be at EHP4 / SPS4. From that level on, most SAP web based technologies are supported within Safari 4 (on OS X). The officially not supported elements are the Portal Administrator, Interactive Forms, NetWeaver Business Client Desktop and Visual Composer (Design and Runtime). In reality the scope of choice is broader: first of all you can choose a Firefox variant like Camino. Safari 4 works reasonably well, but you should carefully check its transactions or applications in use. There will still be a list of not supported or even not working functionalities. For an example see SAP note SAP note 1248182 for the list of missing functionalities in the CRM Interaction Center. Playing with Safari 5 and CE 7.2 brings this disappointing result:
An example of unsupported transactions are those which directly interact with MS Word. The transaction 'solution_manager' is able to generate an EWA report with the help of MS Word and Visual Basic for Applications on a Windows computer. When started on a Mac the ABAP transaction aborts with the message "Exception condition "JAVABEANNOTSUPPORTED" raised. Due to the way a Mac handles it's function keys, quick navigating can be rather complex. For example if one uses the ‘spaces' function on a MacBook Pro the default hotkey will be F8. One needs the fn + key to actually use the fn keys. The usage of shift+fn to generate for example F24 for page down does not work on a laptop keyboard. With the preference pane "Keyboard" the function key assignment can be adjusted. h3. SAPGui Scripting According to the document SAP GUI Scripting Scripting User Guide (http://www.synactive.com/download/sap%20gui%20scripting/sap%20gui%20scripting%20userguide.pdf) it should be possible to use AppleScript in combination with the SAPGui. Unfortunately the AppleScript editor returns an error message. It seems that the scripting functionality is no longer functioning anymore, at least with the current 7.20 revision 2 release of the Java Gui. According to SAP officials, AppleScript used to be part of the SAPGui for Java offering. The current status is that it is propriety software of Apple Inc. I'm trying to convince SAP and Apple to re-release the scripting functionality. It seems that I'm the first one since 2007 digging into this subject. h3. Office Integration Office integration is limited. Although Microsoft maintains binary compatibility between the Windows and Macintosh versions for quite some time, integration with the SAPGui does brings its difficulties. First of all Microsoft has removed the Visual Basic scripting facilities in Office 2008. As a consequence SAP programs who rely on VB scripting will fail. An example of this is the functionality to download Early Watch Alert reports from the SAP solution Manager. But also a simple download of data from an ABAP ALV grid can bring confusion to Excel. Although the file extension is "xls", Excel tries to read it as a text file. Sometimes all data is loaded in a single column.But remember you must save the file first to the client. After this first step you need to manually open the file. h4. NetWeaver Business Client for Desktop Unfortunately the NetWeaver Business Client for Desktop is still a Windows only program. h4. Web Browsers Currently (PAM April 2010) SAP officially supports the following browsers: Firefox 3.5 and Safari 4 on Mac OS 10.5 and 10.6. More precise the Web Application Server (ABAP or JAVA) should be at EHP4 / SPS4. From that level on, most SAP web based technologies are supported within Safari 4 (on OS X). The officially not supported elements are the Portal Administrator, Interactive Forms, NetWeaver Business Client Desktop and Visual Composer (Design and Runtime). In reality the scope of choice is broader: first of all you can choose a Firefox variant like Camino. Safari 4 works reasonably well, but you should carefully check its transactions or applications in use. There will still be a list of not supported or even not working functionalities. For an example see SAP note SAP note 1248182 for the list of missing functionalities in the CRM Interaction Center. Playing with Safari 5 and CE 7.2 brings this disappointing result:
9 Comments
