| | Create Table from Sequential Dump (ttaad4227m000) Use this session to import data from
sequential files, created by the Create Sequential Dump of Table (ttaad4226m000) session, into LN database
tables. The session can append data to existing database tables, or
create new database tables based on the information in the sequential
files. The session offers many features, for example: - it creates the database tables if they do not exist.
- it compares the current data dictionary information
with the information in the dump. If the information does not match, an error
message is shown. If the current data dictionary is not present the session
creates one based on the dump, for example dtccom/dtccom001.
Session usage To import data: - Select the company into which the content of the sequential
files must be imported.
- Use the remaining fields and check boxes to specify the
settings for the import process. Refer to the online field help for
details.
- Click Create.
Note - Use this session
only if the sequential files are created through the Create Sequential Dump of Table (ttaad4226m000) session. This session cannot import
manually converted data.
- If you import data with the Ignore Referential Integrity Constraints check box selected, you must run the Reorganize Tables (ttaad4225m000) session afterwards, with the Repair Reference Counter check box selected.
Sequential file types You can import data from: - sequential files with a field separator. To use this option,
select the Specify Field Separators of Seq File check box and specify the separator in
the Specify Field Separators of Seq File field.
- sequential files with a fixed record length. To use this
option, select the Sequential File has Fixed Record Length check
box.
- a sequential dump file containing the records and data
dictionary information of multiple tables. To use this option, enter the name
of the dump file in the Name of the Dump File field.
All these files are created through the Create Sequential Dump of Table (ttaad4226m000) session. Load data from another company If you want to import data that was exported from another
company, you must first correct the company numbers in the sequential files:
the extracted data in the sequential files contains references to the source
company number. Before loading the data into the target company, you must run
the Copy Company Data (tccom0214m000) session to correct these references, so that they
refer to the target company. This session can only handle files with a field
separator. Therefore, to extract the data from the source company, you
must run the Create Sequential Dump of Table (ttaad4226m000) session with the Specify Field Separators check box selected. Refer to To copy a multicompany structure - Procedure details for more
information. Technical information Internally the session uses the bdbpost6.2 executable. For
more information on this executable, refer to the Infor10 ERP Enterprise Server (LN) Technical Manual (U8172 US). Create Tables for Different Company If this check box is selected, the content of the
file(s) can be imported into a different company than the one from which they
were exported. You must specify the target company in the Company field. Before you import data into a different company, you must
correct the company numbers in the sequential files. This is only possible if
the files contain a field separator. Refer to Load data from another company for details. If this check box is cleared, the content of the files
is imported into the company they were exported from. Package Combination The package combination that
belongs to the company into which you want to import the contents of the
sequential files. Company The company number into which the content of the file(s) will
be imported. Note You can only specify a company number if the Create Tables for Different Company check box is selected. Options Append if Table Exists If this check box is selected, the data from the
sequential (dump) file is appended to existing tables in the selected company.
If a particular table does not exist, it will be created automatically before
the corresponding data is imported. If this check box is cleared, no data is imported into
already existing tables. The import process only creates new tables and
subsequently loads the corresponding data from the files. Overwrite Duplicate Records from Dump If this check box is selected, duplicate records are
overwritten: if the file and the table contain records with identical key
values, the records from the file will overwrite the corresponding duplicate
records in the table. Example The Item Groups (tcmc023) table and the corresponding
sequential file both contain an Item Group record with Item Group Code "ABC". If this check box is selected, the record from the file will overwrite the record in the table. Delete Existing Tables If this check box is selected, the tables already
present are deleted before the new ones are created. You cannot use this option if the Append if Table Exists check box is selected. If this check box is cleared, the existing tables are
not deleted. Only new tables are created. Create Rows before Index If this check box is selected, the tables are created
by first inserting all rows and then creating the indexes. By using this option the tables are created faster but
a few things should be noted: - Interrupting the
process results in table inconsistency
- An index cannot be
created in case of a duplicate conflict
- For large tables,
adding of indices can take a long time (> 15 min)
Disable Domain Constraints If this check box is selected, the domain constraints
are disabled. There is no check to make sure that the data of a table field
meets the requirements of the domain in the table definition. Example It is possible that a string of 30 characters is placed
in a field with a string domain of only 15 characters. In that case you loose
information. So take care when you select this check box. Normally the domains of the data in the sequential files
must be identical to the domains in the environment into which the files are
imported. In that case you must clear this check box. If the domains differ,
you must select this check box. Ignore Referential Integrity Constraints If this check box is selected, the referential
integrity constraints are ignored. It is possible that the tables created from the
sequential files / dump have a reference to tables that will be created later
from the same set of files or from the same dump. Because the latter tables do
not exist yet, this can create a problem. Example: The tccom001 (Employees - General) table contains a
reference to the tcmcs046 (Languages) table. The import process creates the
tables in alphabetical order. Therefore tccom001 is created before tcmcs046.
The import of records in tccom001 fails because for each employee record, the
corresponding Language record in tcmcs046 does not exist yet. You can ignore this type of referential integrity
constraints by selecting this check box. In this way tables will be created and
the import of data will succeed, despite the corresponding reference tables do
not exist yet. Once all tables have been created from the sequential files /
dump, you must run the Reorganize Tables (ttaad4225m000) session, with the Repair Reference Counter check box selected. Note You can also overwrite data of existing tables, or create
tables from the sequential files / dump which have a reference to existing
tables in the environment where the tables are created. In that case, this
check box must be cleared, because the reference tables are already present. Exclude Logical Tables From Dump If this check box is selected, LN does not import
data into tables that are defined as "logical tables". For each logical table
that is skipped, LN writes a message to the "dump.err" output file. If this check box is cleared, LN does not skip the
import for logical tables. If a table is defined as a "logical table", LN imports the data
into the corresponding physical table, which is stored in a different
company. For example: The Employees (tccom001) table in company 100
is a logical table. The corresponding physical table is stored in company 200.
When you import employee data into company 100, the data is imported in the
physical Employees (tccom001) table in company 200. Note - To import data into a logical table, the corresponding
physical table must exist. If the physical table does not exist, LN cannot import the
data, and therefore logs an error message.
- When you import data into logical tables through the
bdbpost6.2 executable, errors are logged if bdbpost6.2 tries to delete the
‘old’ table, which is not physically available in the logical company. For more
information on bdbpost6.2, refer to the Infor10 ERP Enterprise Server (LN) Technical Manual (U8172 US).
- You can only clear this check box if the Append if Table Exists check box is selected.
Set Timestamp to Import Date If this check box is selected, LN updates all
timestamp values of the rcd_utc column, if present, to the time the import is
done. If this check box is cleared, LN preserves the
timestamp values of the rcd_utc column. This way a straightforward
export/import is neutral with respect to the data stored in the
table. Workflow options Also checked out data If this check box is cleared, only the checked-in data
is imported. If this check box is selected, also the checked-out
data is imported. By default, this check box must be selected. Note This check box is only displayed if bdbost6.2 supports
workflow. Allow incomplete object types (not recommended) If this check box is selected, you can import a subset
of the tables of an object type. If the sequential file contains only a subset of the tables of an
object type, these tables are imported. This may result in an incomplete object
type. If this check box is cleared, you can only import the
object type as a whole. Tables that belong to an object type are only imported
if all tables of that object type are present in the file. Note We recommend that you clear this check box. Only select
this check box if you are completely aware of all the consequences! This check box is only displayed if bdbost6.2 supports
workflow. Allow incomplete table sharing sets (not recommended) If this check box is selected, you can import a subset
of the tables of a table sharing set. If the sequential file contains only a
subset of the tables of a table sharing set, these tables are imported. This
may result in an incomplete table sharing set. If this check box is cleared, you can only import the
table sharing set as a whole. Tables that belong to a table sharing set are
only imported if all tables of that table sharing set are present in the file. Note We recommend that you clear this check box. Only select
this check box if you are completely aware of all the consequences! This check box is only displayed if bdbost6.2 supports
workflow. Format Specify Field Separators of Seq File Select this check box if the sequential files contain a field
separator. You must specify the separator in the next field. You must specify the directory where the sequential files
are stored in the Directory for Searching Table Files field. Note Files with a field separator are created through the Create Sequential Dump of Table (ttaad4226m000) session. A file with a .S extension is
created for each of the selected tables. For example: the sequential file
ttccom001550.S contains the data that is extracted from the tccom001 (Employees
- General) table in company 550. Specify Field Separators of Seq File The field separator that is used in the sequential files:
this is the same separator as the one that was specified during the export in
the Create Sequential Dump of Table (ttaad4226m000) session. Sequential File has Fixed Record Length Select this check box if you want to import data from
sequential files with a fixed record length and without any
separators. Note Files with a fixed record length are created through the Create Sequential Dump of Table (ttaad4226m000) session. A file with a .F extension is
created for each of the selected tables. For example: the sequential file
ttccom001550.F contains the data that is extracted from the tccom001 (Employees
- General) table in company 550. You must specify the directory where the sequential files
are stored in the Directory for Searching Table Files field. Important: Do not load files with a fixed record length into a
different company than the one from which they were exported. Refer to Load data from another company for details. Directory for Searching Table Files The directory where the files with a fixed record length, or
the files with a field separator, are stored. Pattern to Match Table Names A sequential dump can contain the contents of many tables.
Use this field to specify the name of the tables for which data will be loaded
from the dump. You can use the following wildcards: - * : matches any string of characters
- ?: matches any single character
Examples: - Enter * to load data for all tables in the
dump.
- Enter *tccom* to load data for tables of package tc,
module com, only.
Files File to Store Table Names not Created If this check box is selected, the names of tables that
cannot be created are stored in a file. You must enter the file name in the
next field. File to Store Table Names not Created The file in which the names of tables that cannot be created
are stored. Name of the Dump File The name, including the path, of the file in which the
sequential dump of the tables is stored. For example: /tmp/dump.400. Name of the Error File Specifies the name, including the path, of the file to which
all error messages and statistics information is written. | |