This is for those who are new to Web Dynpro programming. Here is an explanation of how to set up a Web Dynpro application using the context and binding the context to User Interface (UI) elements of the application. This is only a basic explanation to help set a foundation for understanding Web Dynpro programming. The 3 basic elements of a Web Dynpro application are windows, views and the context. The window is simply a container for a view. To assign a view to a window expand the views and windows under the section labeled ‘Object Name.’ Double click on a window and then drag and drop the view into the window. [Read more...]
SAP TechEd 09 Demo Jam Liveblog Recap
October 14, 2009 By Leave a Comment
This blog is a recap of the liveblog of the SAP TechEd 09 conference Demo Jam. To read in chronological order, start from the bottom and work your way up.
SAP ABAP Performance Tuning – High CPU Utilization, Low DB Activity
July 21, 2009 By 4 Comments
So I have been working on a list of blog topics. I actually have an outline that is 3 pages long, but I am not going to blog on any of the topics on the outline because my experience this week at the client site I think was useful and relevant. We are at crunch time. A lot of things have stacked up and as usual we are working to a very aggressive deadline. In recent years I have typically held many leadership roles on SAP projects. Usually heading up the technical team, working as the project architect or serving as the overall project manager for the SAP project. In my current roll I heading up the Basis Team in a very hands on role. I have been doing my best not to interfere with the development team. The development team is headed up by a good friend of mine and a very talented senior SAP consultant. This week we have had a number of SAP performance defects logged. Upon a quick initial analysis it was clear that the SAP performance issues were not Basis related. The development team is currently buried in the perfect storm of conversions finally coming together and the test team finally kicking the tires on the rest of the delivered development interface objects. This gave me the opportunity to pitch in get my hands dirty and look at some code and performance issues. We knocked off a significant SAP ABAP performance issue with a 100 fold improvement when all was said and done. Looking back on the problem it was obvious to me, but I missed a couple of clues that should have pointed me to the problem even sooner. This is what this blog post is about.
