Entering content frame

Background documentation Function Modules Locate the document in its SAP Library structure

The procedure for maintenance using function modules corresponds in most ways to the procedure for direct input. In the BDT, events run in exactly the same order as in direct input. Only the collection of data in a format that is both neutral and comprehensible to the BDT as well as the transfer of this data to the BDT had to be realized separately.

  1. Create function module per table/table group

A function module is created for each table or group of related tables. The interface generally corresponds to the DI structure (structure or table in multiple entry). The function module converts the existing, structured data into an unstructured form comprehensible to the BDT.

Examples:

  1. Function module per application object/object part

If an application object uses divisibility, one function module per object part is usually available. For all other application objects, one function module is generally sufficient to maintain all the data for an application object. This module calls the function modules of all relevant tables/table groups (see 1) and collects the data in unstructured form in a table. The BDT function module BUS_CONTROL_MAIN_DI is then called and the content of this table is transferred.

Examples:

  1. Extensibility

If a downstream application adds other fields to a table, it also needs to add these fields to the DI structure for this table with the APPEND function. These fields can then be transferred to the function modules created in step 2, as the structure and/or table in the interface references the complete DI structure.
On the other hand, adding another table requires you to create a separate function module for it (see step 1). In order to provide a function module for each application object/object part (see 2), this application creates an additional layer in the form of its own function module.

 

 

Leaving content frame