Runtime Data Dictionary

The tools environment consists of two major components, namely the application data dictionary and the runtime data dictionary. A data dictionary is, basically, a collection of software components and data definitions. Together, these software components and data definitions form the BAAN IV application.

In the application data dictionary, only the definitions and the descriptions of how the entire BAAN IV application is built are stored. To be able to work with this software, there must first be a conversion to the runtime data dictionary. The conversion to runtime procedure is used to create operational pieces of software based on the definitions stored in the application data dictionary.

Any customization or development with BAAN IV tools means changing the application data dictionary. Therefore, it is necessary to convert the changes in the application data dictionary to the runtime data dictionary in order to activate the changes.

Structure of Application Data Dictionary and Runtime Data Dictionary

Contents of the application data dictionary

The application data dictionary contains all data definitions and software components. Together, these data definitions and software components form the BAAN IV application.

The data definition part of the application data dictionary is a database-independent description of the physical data model of BAAN IV, namely:

the table definitions including their relationship with other tables
the domain definitions including the enum descriptions of enumerated domains

The software component part of the application data dictionary contains the definitions of all other software components, namely:

sessions
forms
menus
reports
labels
messages
questions
program scripts
functions

Contents of the runtime data dictionary

The conversion of parts of the application data dictionary to the runtime data dictionary basically means that definitions are linked to software components and that runtime components are created. Physically, these runtime components are per package combination and package VRC.

Two different types of runtime components can be distinguished, namely the application runtime components for the different BAAN IV applications (for example, BAAN IV Manufacturing and BAAN IV Distribution) and the runtime components for BAAN IV Tools. Since the runtime components are stored on the basis of this distinction, an overview is given of where the application runtime components and the tools runtime components are stored physically.

The ${BSE}/application directory is used to store such runtime components as forms, menus, and reports. For each package VRC, there is a separate subdirectory. These package VRC directories in the ${BSE}/application directory themselves also consist of a number of subdirectories for each type of software component.

The ${BSE}/dict directory contains subdirectories for the table and domain definitions of each package combination. A package combination is a collection of a number of package VRCs and can contain software in different versions.

The ${BSE}/tools directory is used to the software components, and table and domain definitions of BAAN IV Tools. The ${BSE}/tools directory consists of two subdirectories, namely the dd directory for the table and domain definitions of BAAN IV Tools and the ttB40_a directory for the runtime software components of BAAN IV Tools. The software components themselves are stored in several subdirectories for the different modules, language codes, and types of software components.

Other components of the runtime data dictionary

In addition to data definitions and software components, some other components that are not directly related to the application dictionary must also be converted to runtime, namely: