Modules 

 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.

 

The following illustration shows the Modules table for the sample context DEMO_TRAVEL:

Modules have input and output parameters. Together, they form the Interfaces of the module. Modules describe the relationship between key fields and their dependent fields. Between them, all of the modules in a context derive all of the dependent fields from the key fields. Each individual module carries out its own part of that task. For example, one module uses some of the key fields as its input parameters to derive some of the dependent fields.

These, in turn, can become input parameters for further modules. You can enter new modules in the table directly, or fill it automatically by creating fields in the Fields table. To edit the table, use the selection column and the pushbuttons on the left hand side of the table.

The table columns have the following meanings:

·        Name

The names of all modules.

·        Type

The module type. A module can be

¡          a table:

The primary key fields of the table are input parameters. All other table fields are output parameters.

¡         a function module:

The import parameters of the function module are input parameters. The export parameters of the function module are output parameters.

¡          another context:

The key fields of contexts are input parameters. The dependent fields of contexts are output fields.

Different modules can have the same type. This allows you to establish the same relationships between different groups of fields.

·        Table/Module

The name of the table, function module or context establishing the link between the context fields.

·        Text

A short text describing each module.

·        Message ID, Number, Variable 1, ... , Variable 4, Type

This column contains the specification of a message by class (Message ID), number, and type (Type). In the columns Variable 1, ... , Variable 4, you can specify context fields whose contents will replace the placeholders ‘&’ in the message. If the module is unable to supply all of the values requested in a DEMANDstatement – for example, because there is no dependent data in the database tables – the system sends this message. You can use message handling in your application program for this message (see Message Handling in Contexts).

·        Buffer type

The buffering type of each context. For more information about buffering, see Buffering Contexts