Contexts are obsolete and should not be used. Contexts were introduced for Release 4.0 for high performance access to frequently required data. Since the introduction of ABAP Objects for Release 4.5, contexts have not been developed further. Since Release 6.40, contexts can be replaced by shared objects.
This section describes how to test a context. It uses the context DOCU_TEST2 from the previous example Using Function Modules as Modules.
To test a context, call the Context Builder (Transaction SE33) and enter the name of the context you wish to test in the Context field. Choose Test. If texts appear in a language other than the logon language when you test the context, you must generate it. This need only be done once. Afterwards, the translated texts will appear.
The following illustration shows the Context Builder: Testing environment. To display the meanings of the various icons, choose Legend.
To test the context, enter values in the key fields of the context. Choose Enter to accept the input values.
If you want to use a blank character (space) as an input value for a field, click on the traffic light symbol on the left hand side of the field to change the status of the input field.
If you enter values in all of the input fields, the system will be able to calculate all of the output fields. To activate the context, select the output fields required and choose Calculate values.
By choosing individual fields, you can use the Context Builder: Testing screen to display the relationships between fields and modules. For example, if you choose the Test Function Module for Context module, the following is displayed: