Tables

Menu path: Start of the navigation path Control Next navigation step <Object Next navigation step > Next navigation step Tables End of the navigation path

Description: Each application table you want to maintain must be entered here. The application responsible for the table (determined by the table’s development class) must write two function modules for communicating with other applications. These modules allow applications that participate in tables as well as the BDT to exchange table contents with the responsible application during dialog.

  • Read data

This function module is used by other applications as well as the BDT to determine the current content of the table at any time during data maintenance. Refer to the description for event ISDST for more details on how to use it (see Program Logic ).

Naming convention: <application>_<application>_<table name>_GET

(Customer: Function module name also has the prefix Y_ or Z_)

Example:

  • BUP_BUPA_BUT000_GET

  • BUP_BUPA_BUT0BK_GET

  • Collect data

This function module allows an application that participates in tables to transfer the values of fields it attached to the application that owns the table. Refer to the description for event DSAVB for more details on how to use it (see Program Logic ). The function module has to be developed in such a way that only the fields of the application participating in tables in the current memory of the application that owns the table are overwritten. The name of the INCLUDE/APPEND structure in the interface is also transferred.

Naming convention: <application>_<application object>_<table name>_COLLECT

(Customer: Function module name also has the prefix Y_ or Z_)

Example: BUP_BUPA_BUT000_COLLECT