Load Data Form (Binary Loader)

The Binary Loader is used to export and import any table data. In contrast to the ASCII Loader the Binary Loader transfers also tables with BLOB fields. Complete data stock or selected table data can be exported into a loader file (binary file). For data selection you can specify tables and several selection criteria. Additionally table fields can be pre-assigned during export and import. In the loader form the logical and the direct import can be performed, logical import in several import modes. You can summarize export- and import-activities in loader objects and store and manage them in the database.

Attention! The Binary Loader does not import loader files, which were produced with the ASCII Loader.

To export individual records you can open alternatively to the load data form a record export form via [Ctrl+B] at every DataView system mask (NoSelect function). It is particularly suitable for export of individual meta data records (e.g. an individual menu with all contained selections).

More information: -> Export and import of data (Binary Loader)


Fields and Functions

Loader object name of the loader object
Loader file name of the loader file
Log file name of the log file
Comment comment on the loader object
Table name list of the tables to be exported
Field name table fields to limit the data export/import
Query expression search terms to limit the data export/import
Field name table fields for automatic pre-assignment
Text entry values for automatic pre-assignment of table fields

Transaction clause on/off combines single statements to one database transaction
Export tables exports table data in a loader file
Import tables imports all table data of the loader file into the target system
Import/replace logical import of table data in replace mode
Import/insert logical import of table data in insert mode
Import/update logical import of table data in update mode
Import/overload logical import of table data in overload mode
DataView update updates the DataView system data

Loader Object

Name of the loader object.

attribute master attribute for loader object (T_LOAD)
type, entry string, uppercase, entry required
max. no. of characters 20
selection tool no
multilingual field no

The loader object uniquely identifies a loader process and stores all export and import settings entered in the form. Thus you can combine repeatedly used export and import activities in loader objects and manage them in the database.

Loader File

Name of the loader file.

attribute master attribute for loader object (T_LOAD)
type, entry string, entry required
max. no. of characters 255
selection tool file browser
multilingual field no

The file created by the new loader is a binary file and, thus, not editable. In addition to the records to be exported, the loader file stores all information defining the export process in detail (exported tables, selection criteria, field pre-assignments).

For exporting you enter any loader file name *.bld including (server!)-path (selection via file browser only possible if DataView server and client run on the same host computer). Default path and file name are ... application_dir\dmp\export.bld.

For importing you enter the name of an existing loader file (same way like export). DataView will then automatically read all information stored in the loader file (exported tables, selection criteria, field pre-assignments) and displays them in the corresponding form fields.

Log File

Name of the log file.

attribute master attribute for loader object (T_LOAD)
type, entry string, entry optional
max. no. of characters 255
selection tool file browser
multilingual field no

All activities executed by DataView in an import or export procedure can be additionally recorded in a log file. The log file is in readable ASCII format and can be opened with any editor. It lists the C_IDs of all exported/imported records as well as the corresponding table names.

For exporting and importing you enter any log file name *.log including (server!)-path (selection via file browser only possible if DataView server and client run on the same host computer). Default path and file name are ... application_dir\tmp\export.log.

Comment

Comment on the loader object.

attribute master attribute for loader object (T_LOAD)
type, entry string, entry optional
max. no. of characters 255
selection tool no
multilingual field no

Table Name

List of the tables to be exported.

attribute relation attribute for loader object-table (T_LOA_TAB)
type, entry string, uppercase, no special characters, entry required
max. no. of characters 13
selection tool menu with all DataView system tables and all existing application tables (separated by master, relation or type table)
multilingual field no

For exporting you enter all the tables into this list whose data you want to export. Selection is done using a choice box. It offers all DataView system tables for exporting meta-data of an application as well as all database tables created for the application for exporting user data stock.

Note! Always export all tables that are related in the data model. Thus you make sure that all internal references in the data model are also contained in the loader file.

During import immediately after selecting the loader file the list displays all tables whose names were exported in the loader file.

Example: You have added or customized a number of fields in a development environment and want to port these changes to a test system or a productive system. To do so, you have to select all DataView system tables relevant for the definition of the field objects. These are T_FIELD, T_MASK, T_MAS_FLD, T_TABLE, T_TAB_FLD. As selection criteria you must enter the following terms. We assume that the field name MED_% identifies the changed fields.

Field Name

Table fields to limit the export/import of records.

type, entry string, uppercase, specification optional
max. no. of characters 50
selection tool menu with all fields in the selected tables (separated by internal system fields or application-specific fields)
multilingual field no

Depending on the tables to be exported, the choice box at the field offers all fields available for defining selection criteria. This results in different opportunities to limit export or import to certain data:

DataView system fields global
(C_VERSION ... C_ACC_OGW)
Globally (in all tables) limits export/import of records to entries in the DataView system fields. For instance you can only export records with a certain version identifier (C_VERSION).

DataView system fields for each individual table
(TABLE NAME.C_VERSION ... TABLE NAME.C_ACC_OGW)
Limits the export/import of records for certain individual tables to entries in DataView system fields. For instance, within one data stock you can export records from one table only after a certain date of creation (C_CRE_DAT), while all data from other tables are not affected by these limitations.

Application-specific attribute fields
(TABLE NAME.COLUMN NAME)
Limits export/import of records by entries in certain application-specific attribute fields. For instance you can export only field objects with a certain name from the DataView system table T_FIELD.

Joins for each individual table
(TABLE NAME-<JOIN)
Limits export/import of records by entries in other tables. It is a precondition, however, that the other table is related to the offered one and is contained in the list of tables to be exported. You must enter the name of the related table as a search term. For instance, when exporting field objects from T_FIELD you could make sure that only the table- and mask objects related to the fields are exported by using a join from T_MASK to T_MAS_FLD and from T_TABLE to T_TAB_FLD.

Attention! Tables containing a BLOB field can not be exported as dependent tables with the binary loader (link via "parenttable-<JOIN" or "parenttable-<CONST"). Currently this behavior cannot be changed.

The desired search terms and join tables for each field you must define in the -> query expression field. Search terms and join conditions for several fields are AND-combined.

During import immediately after selecting the loader file, the list displays all tables whose names were defined during export. In case of logical import via import/replace the selection criteria displayed are responsible for deleting records in the target system. Immediately before starting the import process you can change or extend the criteria for this load mode. For all other logical load modes and for direct import changes to the displayed selection criteria are without any effect.

Example: You have added or customized a number of fields in a development environment and want to port these changes to a test system or a productive system. To do so, you have to select in -> table name all DataView system tables relevant for the definition of the field objects. These are T_FIELD, T_MASK, T_MAS_FLD, T_TABLE, T_TAB_FLD. As selection criteria you must enter the following terms. We assume that the field name MED_% identifies the changed fields.

Query Expression

Search terms to limit the export/import of records.

type, entry string, entry optional
max. no. of characters 255
selection tool no
multilingual field no

You enter search terms and join tables for the table fields, are selected in the field -> field name:

For DataView system fields and application-specific attribute fields
Search term, conventions for search terms correspond to those of the -> standard function Query.

For individual table joins
Name of the related table

Search terms and join conditions for several fields are AND-combined.

During import immediately after selecting the loader file, the list displays all tables whose names were defined during export. In case of logical import via import/replace the selection criteria displayed are responsible for deleting records in the target system. Immediately before starting the import process you can change or extend the criteria for this load mode. For all other logical load modes and for direct import changes to the displayed selection criteria are without any effect.

Example: You have added or customized a number of fields in a development environment and want to port these changes to a test system or a productive system. To do so, you have to select in -> table name all DataView system tables relevant for the definition of the field objects. These are T_FIELD, T_MASK, T_MAS_FLD, T_TABLE, T_TAB_FLD. As selection criteria you must enter the following terms. We assume that the field name MED_% identifies the changed fields.

Field Name

Table fields for automatic pre-assignment.

type, entry string, uppercase, specification optional
max. no. of characters 50
selection tool

Menu with fields of all selected database tables for the loader process, sorted by internal system fields and object specific attribute fields.

multilingual field no

Depending on the tables to be exported, the choice box at the field offers all fields available for automatic pre-assignment. This results in different opportunities to pre-assign fields:

DataView system fields global
(C_VERSION ... C_ACC_OGW)
Global automatic pre-assignment of DataView system fields, i.e. for all tables.

DataView system fields for each individual table
(TABLE NAME.C_VERSION ... TABLE NAME.C_ACC_OGW)
Automatic pre-assignment of DataView system fields for certain individual tables.

Application-specific attribute fields
(TABLE NAME.COLUMN NAME)
Automatic pre-assignment for individual application-specific attribute fields.

The desired values for automatic pre-assignmentand you must enter in the -> text entry field. The values must be type compatible.

You can define an automatic pre-assignment of fields for export or import (direct import and all modes of the logical import), depending on whether the loader files already contain the pre-assignment.

Text Entry

Values for automatic pre-assignment of table fields.

type, entry string, entry optional
max. no. of characters 255
selection tool no
multilingual field no

You enter values for the table fields, are selected in the field -> field name. The values must be type compatible.

Note! The pre-assignment of date fields must be done using the database date format YYYY-MM-DD HH:MM:SS.

You can define an automatic pre-assignment of fields for export or import (direct import and all modes of the logical import), depending on whether the loader files already contain the pre-assignment.

Transaction Clause On/Off

Combines single statements to one database transaction.

In order to allow the complete rollback of actions already performed while importing, you can switch on the transaction clause. It combines single statements to one transaction. Please note that a complete rollback of an import of a large loader file with several thousand records is only possible if the rollback segment of the database is sufficiently large.

Export Tables

Exports the records of the selected tables of the source system into the loader file.

The specified selection criteria and field pre-assignments are considered. In addition to the exported records, DataView stores all export information (tables, selection criteria, field pre-assignments) in the loader file.

Import Tables

Imports all records of the loader file into the tables of the target system.

The import is done directly, i.e. the ident numbers are taken from the loader file and not re-assigned in the target system. They come from the source system.

For direct import definitions to the selection criteria are without any effect. The automatic pre-assignment of table fields is possible.

If you start the function, a survey window will be opened. During import you can monitor for each target table how many records are deleted, updated or newly inserted. If necessary, you can interrupt the running import procedures using a cancel button. In order to allow the complete rollback of actions already performed while importing, you can switch on the transaction clause.

Import/Replace

First deletes all records in the tables of the target system identified by the selection criteria. Then DataView loads all records of the loader file adding them to the records still existing in the target tables. If unique field entries in loader file and target system are identical, these records and their related records are not imported.

The import is done in logical mode, i.e. DataView re-assigns the ident numbers of the imported records in the target system.

The selection criteria responsible for deleting the records in the target system are read from the loader file and displayed in the corresponding fields. Immediately before starting the import process you can change or extend the criteria for import/replace. The automatic pre-assignment of table fields is possible too.

If you start the function, a survey window will be opened. During import you can monitor for each target table how many records are deleted, updated or newly inserted. If necessary, you can interrupt the running import procedures using a cancel button. In order to allow the complete rollback of actions already performed while importing, you can switch on the transaction clause.

Import/Insert

Loads all records of the loader file in addition to existing records in the target tables. If unique field entries in loader file and target system are identical, these records and their related records are not imported.

The import is done in logical mode, i.e. DataView re-assigns the ident numbers of the imported records in the target system.

For import/insert definitions to the selection criteria are without any effect. The automatic pre-assignment of table fields is possible.

If you start the function, a survey window will be opened. During import you can monitor for each target table how many records are deleted, updated or newly inserted. If necessary, you can interrupt the running import procedures using a cancel button. In order to allow the complete rollback of actions already performed while importing, you can switch on the transaction clause.

Import/Update

Replaces all records in master tables whose unique field entries correspond. Records in master tables and type tables are only replaced by DataView if the corresponding parent and child elements exist in the master tables.

The import is done in logical mode, i.e. DataView re-assigns the ident numbers of the imported records in the target system.

For import/update definitions to the selection criteria are without any effect. The automatic pre-assignment of table fields is possible.

If you start the function, a survey window will be opened. During import you can monitor for each target table how many records are deleted, updated or newly inserted. If necessary, you can interrupt the running import procedures using a cancel button. In order to allow the complete rollback of actions already performed while importing, you can switch on the transaction clause.

Import/Overload

Loads all records of the loader file and adds them to the existing records in the target tables. Replaces all records in master tables whose unique fields entries correspond (combination of Insert and Update).

The import is done in logical mode, i.e. DataView re-assigns the ident numbers of the imported records in the target system.

For import/overload definitions to the selection criteria are without any effect. The automatic pre-assignment of table fields is possible.

If you start the function, a survey window will be opened. During import you can monitor for each target table how many records are deleted, updated or newly inserted. If necessary, you can interrupt the running import procedures using a cancel button. In order to allow the complete rollback of actions already performed while importing, you can switch on the transaction clause.

DataView Update

Updates the DataView system data.

During update first all DataView system data are automatically deleted after a security confirmation. Then they are updated by importing the loader file dtv_root/dtv0/dmp/dtv.dat.