| # Log Table (Batch Line Level) (daxch0509m000) Use this session to view the log table that contains the results of the exchange process on table relation level. Related topics Introduction to the miscellaneous business object Relation between logical ASCII files and physical ASCII files To store exchange programs and files in BAAN Type of Exchange The type of exchange scheme. Allowed values See Exchange type Exchange Scheme The code of the exchange scheme. Run Number A consecutive number linked to an export or import run. The run number is unique for each combination of an exchange batch and an exchange type. Each exchange run is written to the log table by using the run number. The log table is then used to determine the run number of the next export or import run. In regular export or import, the run number is used to avoid importing the same ASCII file twice or overwriting existing ASCII files. In multisite control, the run number is also used to ensure that data is replicated in the correct sequence. Try Number A consecutive number that is unique within an exchange run. Each run starts with try number 1. When the same run is continued, reprocessed or restarted, the run number remains the same and the try number is incremented by 1. Batch The code of the batch. Batch Start Date The date the batch of an exchange process is started. Table Rel. A sequential number that identifies the table relation and its processing order. It makes the table relation unique in the batch. Seq. No. The sequence number of the table relation in the batch during an import process. The sequence number of the table relation does not have to be unique. If two relations have the same sequence number, the relation with the lowest sequence number is processed first. Table The code of the LN table from which data was exported, or in which the data is imported. The LN table is defined by the package code, a module code and a table number. For example, tiitm001. ASCII File The code of the logical ASCII file from which data was read during an import, or to which data was written during an export. Related topics Relation between logical ASCII files and physical ASCII files Records Read The number of records read from the ASCII file during an import procedure or from the LN table during an export procedure. Note The number of records read is the same as the number of processed records, plus the number of error rejected messages, plus the number of condition rejected records, plus the number of skipped records. Records Proc. The number of records processed successfully to the LN table during an import procedure or to the ASCII file during an export procedure. Error Rej. The number of rejected records due to errors. These records are written to the log file. Cond. Rej. The number of records rejected due to an add, update, overwrite, or delete condition with the return value, false. These records are written to the log file. Records Skipped The number of skipped records. A record can be skipped during an import for the following reasons: The table relation is not active. The record was already imported during a previous try. The options add, overwrite, update, or delete were not selected in the Table Relations (Import) (daxch0121s000) session. A record can be skipped during an export if the function "do.not.export.record()" is used in a condition. Related topics To use conditions in the exchange module Batch Line End Date and Time The date and time, according to Coordinated Universal Time, that the table relation in a batch of an exchange process was ended. Use DAL This check box indicates whether the Data Access Layer (DAL) was used for the current batch line. By using the DAL, an import carries out all the constraint checks, integrity checks and side effects, such as updates on other tables, that are programmed into the DAL. This guarantees database integrity, saves programming time, and avoids the errors that can occur in condition scripts. Refer to Import using the Data Access Layer (DAL) for details. DAL Checks This check box indicates whether the Data Access Layer (DAL) property checks were used for the current batch line. Using property checks is safer, but you can turn them off to boost performance. Refer to Import using the Data Access Layer (DAL) for details. |