Advance Solution Blogs

A while back, I responded to a post on an ASUG forum. The question was 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 my reply to the poster. The original question was precipitated by a statement that the client’s consultant made: that it is a best practice (the misuse of this term really bothers me) to refresh their development client from production regularly. My response to this issue was, 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, anyway? 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.

It's been a while since we published our white paper on the state of SAP landscapes, but our NetWeaver support team regularly discusses landscapes and possible strategies for setting up clients. While we move forward on this research, I will share with you my thoughts on the reference landscape, which still hold true today. In future articles, I'll expand on this with other new dimension productions.

 

 

 

Occasionally, the client's environment has restrictions on user access to a browser, or runs restricted desktops that cannot access the BarTender Web Print server to generate on-demand Barcode labels. If this is the case in your environment, you still have the option of printing using a utility included with Enterprise label. Here are the steps.

During my normal day job, I meet with customers regularly and present proposals that revolve around SAP WM. More often than not, we find ourselves suggesting solutions that utilize SAP EWM, which is delivered as a component of SAP SCM. Lately, I have received many questions regarding the differences and why I recommend one solution over another. I figured that I would write a series of posts around the offerings to better explain them.

It used to be that the big question was simple: IM or WM? But now with the introduction of new versions of warehouse management, the choice is not as clear. Over the next couple of posts, I will introduce to you the different versions of SAP WM, and then provide you with a simple grid to help you make your choice. I say "assist you," because only a thorough evaluation of your environment and requirements will decide the best choice for your situation. At the very least, I’ll try and provide you some guidance. If you need an evaluation, call me – shameless plug :-)

Subcategories

     
Go To Top