As consultants, we regularly work on many different SAP systems, since we may work on the same functionality from client to client we use an easy trick supported by SAPgui to get ourselves setup on a new system as quickly as possible. Of course, if you like drilling through the standard Easy Access menu, you can stop reading. I am providing an example role below that you can use. Follow along so you can leverage this trick in your work as well.

Read more: Your SAPgui Favorites Can Follow You

A while back I responded to a post on an ASUG forum. The question was regarding how others handle the refresh of their development client and data for development and testing.  I couldn’t find the original post but a recent CIO Insight article made me think about what I had told the poster. The original question was precipitated by the statement the client’s consultant had made that it is a best practice (I hate the misuse of this term) to refresh their development client from production regularly. My response to this issue was that it is NOT a best practice to refresh the development client. In actuality, it is harmful because of the loss of change transport links, modification data (there are ways to restore the modification data but not the version history) and version history. My other comment was: "Why would you even want to do this anyways?" Normally a production environment for a large company can be upwards of 900 GB. I couldn’t imagine copying this amount of data yet some sites do this on a regular basis. Does it make sense? You weigh in.

Read more: Should You Copy Production Data to DEV and TEST Environments?

You are probably aware we are not fans of Java on the client, quite frankly considering the constant updates needed and the inability to shut off Java checks for updates its time for something new. I have been happily using SAPgui 7.2 without a problem for over a year now, our developers recently encountered a problem with the older SAPgui that was fixed in 7.3 so it was time to update.

Read more: SAPgui 7.3 and Java

It's been a while since we last published our White Paper on the state of SAP landscapes, but out NetWeaver support team regularly discusses landscapes and  possible strategies for setting up clients that might be needed. While we move forward on this research I will share with you thoughts on the reference landscape, which still holds true today, and in future articles, I'll expand on this with other new dimension productions.




Read more: SAP Reference Client Landscape

Go To Top