Structure of the Logical Databases

The selection of master data is separate from the selection of transaction data. The assignment of transaction data to the relevant master data is not statistical, as a consequence, performance is improved. The assignment is first made during the execution of a report that uses LDB FMB.

By setting indicators Master data is selective or Transaction data is selective , the user can decide whether the master data should be selected first and then the corresponding transaction data or whether the transaction data should be selected first, followed by the characteristics of the relevant master data.

Transaction SE36 contains the structure and description of the databases.

Selection Options

To add several selection fields for the FM area, funds centers, and commitment items, choose the function Dynamic selection .

If you integrate the Hie_id field (position of a commitment item or funds center in a hierarchy) into your report, you can also evaluate the data using the hierarchy .

Notes on System Performance

The important aspect when using FMB is performance. Therefore you should restrict the selection criteria for FM area and single Funds Management account assignments (FMAA) as much as possible. For this reason, the FMAA selection fields always appear on the selection screens of all programs that use FMB.

You can also prescribe FMAA selection criteria using the classification or predefined master data groups or extend the selections using the further fields of nodes (not complete set of all fields available) using the dynamic selection feature.

If the LDB reports use more than one type of FMAA_* master data nodes, then the resulting huge control-budget-posting object/address hierarchies might have a serious impact on performance. Therefore, the maximum data volume of selected master data records is restricted by the following constants:

The data volume of transactional data can be optionally resctricted/optimized using the selection screen parameter P_MAXSEL. You can improve the performance of the report by entering a maximum number of hits. Then the number of records specified is read from the transaction data tables during DB access.

If you want to execute a report with transaction data, select Only master data with postings . For master data, which was not posted up to now, no ' GET event' is triggered.

When creating your own ABAP programs, which access the LDB FMB, performance can be considerably influenced by using the FIELD extra of the GET statement. The fewer fields made available, the more quickly the LDB works. This applies particularly for fields that are physically deposited in their own tables (for example, master data texts). Read accesses are not needed here.

If possible, parameter Master data is selective or Transaction data is selective should be preselected in the report so that the user cannot make any settings that have a negative effect on performance.

Business Transaction Events

To fill user-defined fields in the logical database or to modify the selection screen, you can use the following sample function modules as templates for your own function modules:

SAMPLE_PROCESS_00106111 Logical Database FMB - Nodes FMAA

SAMPLE_PROCESS_00106121 Logical Database FMB - Nodes FMTOX

SAMPLE_PROCESS_00106122 Logical Database FMB - Nodes FMOIX

SAMPLE_PROCESS_00106123 Logical Database FMB - Nodes FMBIX

SAMPLE_PROCESS_00106124 Logical Database FMB - Nodes FMCOX

SAMPLE_PROCESS_00106131 Logical Database FMB – Selection Screen

For more information on Business Transaction Event techniques, see theIMGunder  Financial Accounting Financial Accounting Global Settings Business Transaction Events .