Data Model / Programming Model

Use

Appearance of the Data Model

The runtime data model for the BRF maintenance environment comprises the following data:

  • OLD data:

    All configuration data that is read from the database is placed in structures or internal tables with the suffix '_OLD' (such as ms_brf150_old or mt_brf144_old).

    These structures or tables are referred to as 'OLD' data".

  • CUR data:

    The so-called OLD data is copied to structures or internal tables that have the suffix "_CUR" (such as ms_brf150_cur or mt_brf144_cur).

    These structures or tables are referred to as "CUR" data".

  • SCR data:

    Data that is displayed in the subscreens is located in tables and structures that have the suffix _SCR (such as ms_brf150_scr or mt_brf144_scr).

    These structures or tables are referred to as "SCR data".

Note the following:

  • The OLD data always matches the status in the database

  • The CUR data always matches the current status in processing

  • On occasions, there are some examples in the development systems in which one of the following prefixes is used instead of the suffix '_SCR':

    • 'DS_' (stands for 'screen structure')

    • 'DT_' (stands for 'screen table')

    Do not use this convention any more.

  • Regarding PBO the following applies:

    1. The CUR data is copied to structures or internal tables with the suffix '_SCR' and enhanced to include further data (usually texts).

    2. The screen data is transferred to the corresponding subscreens and displayed there.

  • Regarding PAI the following applies:

    1. The SCR data is transferred to the corresponding maintenance class

    2. The SCR data is checked for errors

  • When the data is saved, the system compares the data from CUR and OLD.

    In doing so, the system creates the following tables:

    • Table with the table lines that have been added (INS)

    • Table with the table lines that have been changed (UPD)

    • Table with the table lines that have been deleted (DEL)

Methods of the Maintenance Classes

The maintenance classes contain more than 50 methods. These methods correspond to clearly defined, small steps in the flow of maintenance of a BRF object.

This large number of methods offers the following advantages:

  • The source text of the individual methods is short

  • You can recognize relatively quickly which source text has to be implemented and where

  • The error search is simplified, as the symptom often lets you deduce the method affected

The description of the methods is split as follows: