Several different systems might be involved in a business process that you want to test. Consider a simple scenario:

1. A purchase order is entered on the first system.
2. The order is passed to a second system where production is scheduled.
3. The second system passes information to a third system where a table is updated.

You want to test the transactions and check the table update.

eCATT enables you to create and manage the tests in a single system, and execute the appropriate tests against the various target systems.

The central test system must be based on Release 6.20 of the Web Application Server or later.

The target systems must be based on SAP Basis Release 4.6 or later. A patch containing essential eCATT functions must have been applied to each of the target systems.

The central test system contains:

• eCATT
• Repository of eCATT objects (test script, test data containers, system data containers, and test configurations)
• Logs
• RFC destinations for the target systems

The applications under test reside on the target systems. The central test system can also be a target system.

In a test script, the RFC destinations are not specified directly. You specify the RFC destinations in a system data container, where you assign them to target systems. You create the names of the target systems yourself, and it is these name that you use in the test script.

In a system data container, you could have:

In a test script, you could have:

The advantage of this separation of test script and RFC destinations is that you can change the target systems without having to change the test script. You can simply assign a different system data container, containing a different set of RFC destinations, to the test script. You can do this in a test configuration.

Continuing the example, a second system data container could have: