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.
To find an existing context and to familiarize yourself with it, use the initial screen of the Context Builder (Transaction SE33).
· Use the possible entries help for the Context field to display a list of existing contexts.
· Use Test to display the names of the key fields and dependent fields, and the function of the context (see Testing a Context).
· Use Network graphic to display the derivation schema for the context.
Enter the name DEMO_TRAVEL in the Context field on the initial screen of transaction SE33 and choose Test.
You will see that the context has two key fields, from which the other fields are derived, and that a total of five modules are used to define the relationships between the fields. Four of these modules are database tables, and one is another context. If you choose Network graphic, you will see the names of the key fields (CARRID and CONNID) and their relationships to the modules.
To see the names of all context fields, display the Fields table in the Context Builder.
You now have the most important information which you need to work with the context. Further information such as message texts and the buffering types for the modules are contained in the Modules table.