Do you identify errors when designing your application? When developing a technical specification every analyst should know and account for the possible errors that can occur in an application. I think it’s pretty commonly known that no application should cause an ABAP dump, unfortunately I still see these happen but I believe also that every analysts and developer should be able to tell you what happened within their application when an error occurs. When performing a detailed technical design, the possible error should be trapped and I would argue that …

I spent a afternoon with a good friend of mine who was having a hard time turning application requirements to a detailed design (I’m sure he is not the only one with this issue). We reviewed an example Software Requirements Specification that we use and once we were on the same page as to what the application was intended to do I started up Visio to start working through the design elements. What I found amusing was that he was shocked that I was going to do this in Visio. …

Over the years I have managed and/or been involved in every level of testing of applications known to man J , for most of our SAP projects we normally adopt the internal testing strategy dictated by our customer so it’s simple to say that every project is different. In many cases we provide input to our clients, peers on how to make testing more effective for the project, development team, company. I am in the process of writing a paper on testing and considered some of the thoughts I had on this subject and what others can benefit from.

A while back I responded to a post on an ASUG forum with the question about how others handle the refresh of their development client and data for development and testing. It’s been a while and I couldn’t find the post but a recent CIO Insight article made me think about what I had told the poster. The original question was precipitated because the client’s consultant had told them that it is a best practice (I hate the mis-use of this term) to refresh their development client from production regularly.

The benefit of a ERP system is the tight integration that it provides, in the past the practice of hijacking fields was common but had little impact. Systems were generally islands so modifying the data in the WM system would not affect finance system etc. but with ERP everything is integrated, this means that a small decision in one area can affect other areas and/ or functionality.

Normally when we do classroom or onsite training for customers, we want to ensure that all users have a basic understanding of how to access SAP. This is really not hard but we realized a while ago not to assume that people who attend classes have the same basic understanding. We have a SAP Navigation course which we direct all our trainees to take before attending our classes.

We are now making it available for free for anyone to take, it is about 15 minutes long so it’s quick, and if your new to SAP a great way to learn about navigation.

Of course we also always love feedback.

In Part I of my eCATT blog series, I introduced eCATT’s their main features and objects. In Part 2 of my eCATT blog series I covered recording a script and the main aspects of the Test Script Editor. In this blog post I will explain how to parameterize the script we previously recorded in Part 2 of this series. We will paramaterize both the material number and gross weight fields from this script. This will enable the script to be executed for any range of materials and adjust their weights accordingly.
Parameters:
Parameters are a test script’s import and export interface, and …

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 you can use for this below so follow along so you can leverage this trick in your work as well.

Good CIO Insight bullet points on project management 10 truths about project planning which targets specifically the impact of a poor requriments process. What surprises me about this study is that’s it’s been years since the start of the publication of the CHAOS report and it appears that project success rates have not changed much in IT project management since then.

In part I of my eCATT series of blogs, I covered the introduction to eCATTs, prerequisites, basic features, and the four main eCATT’s objects.
In this post I will explain in greater detail the test script editor and I will provide detail on how to record a test script using the SAP GUI mode.
Test Script Editor
The test script editor is used to create and maintain test scripts. You can use the recording functions, or directly input eCATT commands into the command editor to create test scripts.  The test script editor contains the following areas:

Application Toolbar
Information …