When performing code reviews, one of our checklist items is, "What package did you put your development in?" When asking external developers, we always get a puzzled look, so I'll try and explain why it can be useful. I recently responded to a stack overflow post asking whether ABAP had a similar functionality to libraries in other languages.

On occasion, I am asked how to decide the best type of modification to make into an SAP system. Any modification made to the standard SAP system incurs cost. The largest part of this cost is rarely the cost of the initial coding, testing, etc. - rather, it's the long-term cost of maintaining the modification. I took a stab at trying to map out how I would compare the various techniques for modification based on long-term costs and ease of use.

This will be the first of a series of blogs that will hopefully introduce you to eCATTs, explain the various important eCATT objects and show you how to use them. In this first blog, I will cover:

  1. What is an eCATT?
  2. Pre-requisites and settings required before using eCATTs
  3. Introducing the four important eCATT objects – Test Configuration, Test Data Container, System Data Container and Test Script

In part one of my eCATTs blog series, I covered the introduction to eCATTs, prerequisites, basic features and the four main eCATTs objects.

In this post, I will explain in greater detail the test script editor and 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:

One customer recently asked us to look into a problem they were having generating an accurate data report related to materials. This was a standard report and the functionality had been pretty solid for some time. What we found was that, at some point, fields in the material master were hijacked for use in classifying materials. When it came time to use the fields for their intended purpose, they were already being used. So, a work-around was developed. I won’t go into too much detail as it’ll distract from my point, but the end result was that standard reports were not working as SAP intended. The customer was forced to redevelop the standard reports (they did not move the data because a custom application had been developed on top of the various hijacked fields so redeveloping the report seemed easier) to be able to report properly. I certainly do not have a feel for the costs involved, but I imagine that maintenance, and of course the workarounds, are going to have a long-term cost.

     
Go To Top