EIM Configuration File

This chapter covers the generic use of EIM configuration files (referred to as .IFB files) and is organized into the following sections:

For specific parameter-level information that affects importing, deleting, merging, and exporting, see the chapters for those functions.

Using the EIM Configuration File to Define a Process

EIM reads a configuration file that specifies the EIM process to perform (import, update, merge, delete, or export) using the appropriate parameters. The EIM configuration file (the default file is default.ifb) is an ASCII text file of extension type .IFB that resides in the Siebel Server/admin directory. Before you can run an EIM process, you must edit the contents of the EIM configuration file to define the processes for EIM to perform.

Note: If you are planning to use Unicode in your implementation, then the EIM configuration file must be saved as a Unicode text file.

EIM then sets the process locale as specified during start up in the command line, the Server Manager graphical user interface (GUI), or the configuration file. You must specify the correct character set, such as Western European or UTF-8, for the target database in one of these locales. For information on locales and character sets, see Siebel Global Deployment Guide.

EIM accepts parameter values from three sources:

The command line entered by the user who invokes the EIM process
The Siebel Server Manager GUI
The configuration file specified, or default.ifb if none is specified

Parameter value searches are performed according to a specific hierarchy: command line, component parameter, and configuration file. Command-line parameters thus override component parameters, and component parameters override configuration file parameters.

Note: If the batch number component parameter is set to 0, the batch number in the EIM configuration file (if any) is used. This is the only exception to the parameter hierarchy.

You can define multiple processes in the EIM configuration file and then invoke a specific process using the process parameters discussed later in this chapter. Alternatively, you can create multiple configuration files and specify which one EIM should use.

Defining EIM Configuration File Parameters

The EIM configuration file begins with a header section used to specify global parameters that apply to all process sections defined later in the file. Following the header section, there must be at least one process section with its associated parameters. Some process section parameters are generic for all EIM processes. Other process section parameters are specific to a particular EIM process, such as import.

This chapter describes only the header section and process section parameters that are generic to all EIM processes. For information on process-specific section parameters, see the relevant chapter for each process:

For an import process, see Editing the Configuration File for Import Processing.
For an export process, see Editing the Configuration File for Export Processing.
For a delete process, see Editing the Configuration File for Delete Processing.
For a merge process, see Editing the Configuration File for Merge Processing.

EIM Configuration File Parameters

You can find descriptions of all EIM configuration file parameters in this chapter and the chapters that follow. For information on inheritance rules, see Inheritance Rules for Configuration Parameters.

Each parameter is categorized by the specific type of EIM process in which it is used:

General Header Parameters. Header parameters may be used in all EIM processes. See Header Section Parameters Generic to All EIM Processes for a list of general header parameters.
General Process Parameters. General process parameters may be used in all EIM processes. See Process Section Parameters Generic to All EIM Processes for this list.
Import Process Parameters. Import process parameters apply specifically to an import process. See the tables in Process Section Parameters Used for Imports and Parameters Used for Imports in Both the Header and Process Sections.
Export Process Parameters. Export process parameters apply specifically to an export process. See Parameters Used for Exports in Both the Header and Process Sections.
Delete Process Parameters. Delete process parameters apply specifically to a delete process. See Parameters Used for Deletes in Both the Header and Process Sections.
Merge Process Parameters. Merge process parameters apply specifically to a merge process. See Parameters Used for Merges in Both the Header and Process Sections.

You may want to refer to the default.ifb configuration file as you read the description of each parameter.

Header Section Parameters Generic to All EIM Processes

Header parameters are necessary at the beginning of the .IFB file. At a minimum, [Siebel Interface Manager] and PROCESS must be specified. The following information provides descriptions of header parameters.

Parameter	Description
CONNECT	The ODBC source name for connecting to the database server.
LOG TRANSACTIONS TO FILE	This parameter must be in the header section and the default value is TRUE. Transactions can be logged in a file or a table. By default, EIM logs transactions into files. Log files are saved in the file system’s EIM directory. If you do not want transactions to be logged in files, then setting this parameter to FALSE logs transactions to a table. Note: If this parameter is set to TRUE, you must make sure that the Siebel Server can write to the file system’s EIM directory. During installation, the file system directory must be specified using the Uniform Naming Convention (UNC). For more information, see the Siebel Installation Guide for the operating system you are using.
PASSWORD	The database password for the process to be run. This parameter is inherited for the EIM component from the Siebel Gateway, so it should already be set. However, you can specify this in the .IFB file if you are running EIM from the Siebel application (not the command line) and if you have not already set this value in the EIM Server Component parameters. Note: If you start EIM from the command line, it uses the user name and password you used to log into the srvrmgr. If you start EIM from the Siebel application, EIM looks for the user name and password in the EIM Server Component parameters first, and if they are not specified, EIM then looks in the .IFB file. If EIM cannot find the user name and password in those places, EIM cannot log into the database and it fails. If you do not want your user name and password visible in the .IFB file, then specify them in the EIM Server Component parameters.
PROCESS	Identifies the specific process to run during this invocation of EIM. The named process must be defined in the process section of the .IFB file.
[Siebel Interface Manager]	Header section must use this reserved name.
TABLEOWNER	The database logon name that owns the tables to be operated on; used as the prefix for table names; defined during installation.
USERNAME	The database/employee logon name for the process to be run. This parameter is inherited for the EIM component from the Siebel Gateway, so it should already be set. However, you can specify this in the .IFB file if you are running EIM from the Siebel application (not the command line), and if you have not already set this value in the EIM Server Component parameters. Note: If you start EIM from the command line, it uses the user name and password you used to log into the srvrmgr. If you start EIM from the Siebel application, EIM looks for the user name and password in the EIM Server Component parameters first, and if they are not specified, EIM then looks in the .IFB file. If EIM cannot find the user name and password in those places, EIM cannot log into the database and it fails. If you do not want your user name and password visible in the .IFB file, then specify them in the EIM Server Component parameters.

Process Section Parameters Generic to All EIM Processes

This section contains general process parameters generic to all EIM processes that appear in the process section of the EIM configuration file. The following information provides descriptions of these parameters.

Note: If your configuration file has more than one process section and you want a certain parameter to act on more than one process, you must include the parameter setting within each of the process sections that correspond to the processes on which you intend for the parameter to act.

Parameter	Description
BATCH	Required. Specifies a required batch number for the process to be run. Use this batch number to identify the set of rows to load from the EIM tables for this specific process. This batch number corresponds to the value in the interface column IF_ROW_BATCH_NUM and must be a positive integer between 0 and 2147483647 (no commas). To specify multiple batches, use a range or list of batch numbers. To specify a range of batches, use the first_batch-last_batch format as shown in this example: `BATCH=100-120`. To list batches, use the comma-delimited format as shown in this example: `BATCH=100,103,104`.
COMMIT EACH PASS	Optional. Commit after each EIM pass; default is TRUE. Note: It is best not to use this parameter in delete processes. This is because if a commit occurs after each table or each pass in a delete process, then in case of errors causing exit from the process, orphan records and dangling references can remain. If the commit occurs for the whole batch, then in case of errors, you can roll back other table deletes.
COMMIT EACH TABLE	Optional. Commit after each base table; default is TRUE. Note: It is best not to use this parameter in delete processes. This is because if a commit occurs after each table or each pass in a delete process, then in case of errors causing exit from the process, orphan records and dangling references can remain. If the commit occurs for the whole batch, then in case of errors, you can roll back other table deletes.
IGNORE BASE TABLES	Optional. Do not process these tables.
INCLUDE	Optional. Subprocess to execute. Note: This parameter can be used only in shell processes. A shell process uses the INCLUDE statement to invoke a sequence of processes in a single run. INCLUDE names a process to be included as part of this process. More than one process may be included in another process. All included processes execute before the process itself.
LOG TRANSACTIONS	Optional. Default value depends on system preference. Use this parameter to control the logging mode. If this parameter is set to TRUE, EIM logs changes when mobile clients synchronize. If this parameter is set to FALSE, changes are not logged. In general, when you load data into the HQ database for the first time, this parameter should be set to FALSE. `LOG TRANSACTIONS = TRUE` operates in row-by-row mode. `LOG TRANSACTIONS = FALSE` operates in set-based mode.
ONLY BASE TABLES	Optional. Process only base tables.
ROLLBACK ON ERROR	Optional. Error rollback behavior; default is FALSE.
SESSION SQL	Optional. Specifies a user-defined SQL statement to be sent to the database server before other SQL statements for this process. This string is sent directly to the database and must be a single SQL statement suitable for immediate processing. You can use the SESSION SQL parameter to set tracing for performance analysis. Only one SESSION SQL parameter can be used in each process section. Note: This parameter cannot be used to insert or update data in Siebel base tables. EIM sends the SQL statement directly to the database and may cause data loss for Siebel Remote and Siebel Replication Manager.
SKIP BU_ID DEFAULT	Optional. Specifies whether the virtual null key is to be skipped for the BU_ID column. The default value is FALSE. Virtual null key sets the BU_ID column value to the default value defined in the repository. To use the default value defined in the repository for the BU_ID column, set this parameter to FALSE (the default). To skip the virtual null key and not use the default value defined in the repository for the BU_ID column, set this parameter to TRUE. This parameter applies to import, delete, and merge processes because the foreign key must be resolved before these processes can run.
TABLE	Required. Specifies the name of an EIM table used in this process. Multiple TABLE parameters may be used to define a process using more than one table. Example: `TYPE = EXPORT` `BATCH = 101` `TABLE = EIM_ACCOUNT` `EXPORT MATCHES = S_ORG_EXT, (NAME > ‘A’)` Note: For performance reasons, you should limit the number of tables to export or merge in a single process section to five tables or fewer.
TRANSACTION SQL	Optional. Post-commit SQL statement. Specifies a user-defined SQL statement to be sent to the database before other SQL statements, and immediately after each commit or rollback operation during the process (including subprocesses). For more information about this parameter, see TRANSACTION SQL Parameter.
TYPE	Required. This parameter specifies the type of process being defined (possible values are IMPORT, EXPORT, DELETE, MERGE, SHELL). A shell process uses the INCLUDE statement to invoke a sequence of processes in a single run.
UPDATE STATISTICS	Optional. For DB2 databases only. Controls whether EIM dynamically updates the statistics of EIM tables. The default value is TRUE. For example, if you are running EIM on a DB2 database, the account under which EIM runs must have the DB2 CONTROL table privilege on the EIM tables. The database installer automatically grants this privilege when creating the tables. However, it may be necessary to regrant this privilege if the EIM tables have been modified or recreated. To regrant the CONTROL privilege, use the script named grantstat.sql in the database installer directory. Note: If you plan to run EIM processes in parallel on a DB2 database, this may cause a deadlock when multiple EIM processes access the same EIM table simultaneously. To avoid this potential problem, set the UPDATE STATISTICS parameter to FALSE.
USE ESSENTIAL INDEX HINTS	Optional. For MS SQL Server and Oracle databases only. The default value is TRUE. This parameter enables a subset of index hints for MS SQL Server.
USE INDEX HINTS	Optional. For Oracle databases only. Controls whether EIM issues optimizer hints to the underlying database to improve performance and throughput. The default value is FALSE.
USING SYNONYMS	Optional. Controls the queries of account synonyms during import processing. When set to FALSE, this parameter saves processing time because queries that look up synonyms are not used. The default value is TRUE.

Inheritance Rules for Configuration Parameters

Some configuration parameters can only be used in a process section of a configuration file, not in the header section. The parameters TYPE and ONLY BASE TABLES are two examples of parameters in this category. Parameters that can be used only in a process section only affect that section, and only the process for which they appear.

Most configuration parameters are used in both the header section and the process section of the configuration file—the parameters USE INDEX HINTS and COMMIT EACH PASS are two examples. These parameters follow the inheritance rules that are listed here, using USE INDEX HINTS as an example:

If you specify USE INDEX HINTS in a configuration file’s header section (that is, in the section [Siebel Interface Manager]), then it will be used for all processes in that configuration file.
If you specify USE INDEX HINTS in a shell process, then USE INDEX HINTS affects all of the shell’s subprocesses when running that shell process.
If you specify USE INDEX HINTS in a shell process and in its subprocess, then the value from the subprocess will override the value from the shell process.
If you specify USE INDEX HINTS in any other type of EIM process (import, export, delete, or merge), then USE INDEX HINTS will be used only for that process and not for any other processes that might be listed in the configuration file.
If you specify USE INDEX HINTS in a configuration file’s header section (in [Siebel Interface Manager]) and in the process section, the value from the process section will override the value from [Siebel Interface Manager].

Setting EIM Configuration Parameters

The table in the topic Header Section Parameters Generic to All EIM Processes lists the general configuration parameters that can be set when using EIM.

Keep in mind the following points when working with the EIM configuration file:

Lines in the default.ifb file that begin with a semicolon (;) are comment lines and are ignored.
If you are continuing a parameter definition to multiple lines in the .IFB file, make certain that the backslash character (\) is the last character on the line. The backslash character denotes continuation. Do not combine comments (;) with new lines (/) because this format creates difficulties finding a comment in the middle of a line.

Caution: When the backslash is followed by a space, EIM interprets the space character as “escaped,” and the new line character then terminates the parameter definition. This can generate an error message indicating the parameter definition is incomplete.
If multiple lines have the backslash (continuation) character (\) at the end, this means they are a single parameter line. So, if a semi-colon (comment character) is placed among these lines, EIM ignores the column with the semi-colon and all columns linked through the continuation character.
For example:
```
ONLY BASE COLUMNS = S_PARTY.PARTY_TYPE_CD,\
S_PARTY.PARTY_UID,\
; S_PARTY.ROOT_PARTY_FLG,\
S_CONTACT_FNX.PAR_ROW_ID,\
S_CONTACT_FNX.X_BATCH_ID
```
These statements will cause EIM to comment off S_PARTY.ROOT_PARTY_FLG, S_CONTACT_FNX.PAR_ROW_ID, and S_CONTACT_FNX.X_BATCH_ID.
PASSWORD and USERNAME values are generally not used for access authentication or as a security measure. EIM acquires access authentication from the component parameters. PASSWORD and USERNAME values in the .IFB file are only used if the parameters are not set at the enterprise or component level.

Setting EIM Configuration File Header Parameters

The first nonblank, noncomment line of the configuration file’s header section must contain the exact information shown:

[Siebel Interface Manager]

The table in the topic Header Section Parameters Generic to All EIM Processes lists the other general header parameters to set when using EIM.

Setting EIM Configuration File Process Parameters

This topic describes only the general process parameters, that is, the process parameters that are generic to all EIM processes and that appear in the process section of the EIM configuration file. The process-specific section parameters are described in the chapters that cover each specific EIM process.

The table in Process Section Parameters Generic to All EIM Processes lists the general process parameters to set when using EIM.

The first nonblank, noncomment line of each process section is a bracketed string that specifies the name of the process. This is the name used in the process argument, or in the run process parameter in the header section. The value between [ ] (the brackets) can contain alphanumeric characters, spaces, and the following punctuation marks:

# _ : - $ % / +

There are two types of keywords for process section parameters: required keywords and optional keywords.

Required Keywords for Process Parameters

Of the general configuration parameters listed in Process Section Parameters Generic to All EIM Processes, note that the following ones are required when using EIM:

TYPE
BATCH
TABLE

Optional Keywords for Process Parameters

Of the general configuration parameters listed in Process Section Parameters Generic to All EIM Processes, note that the following ones are optional when using EIM:

COMMIT EACH PASS
COMMIT EACH TABLE
IGNORE BASE TABLES
INCLUDE
LOG TRANSACTIONS
ONLY BASE TABLES
ROLLBACK ON ERROR
SKIP BU_ID DEFAULT
SESSION SQL
TRANSACTION SQL
UPDATE STATISTICS
USE ESSENTIAL INDEX HINTS
USE INDEX HINTS
USING SYNONYMS

TRANSACTION SQL Parameter

This parameter specifies a user-defined SQL statement to be sent to the database before other SQL statements and immediately after each commit or rollback operation during the process (including subprocesses). Although a commit operation is processed first, this statement is emitted (for the first time) immediately after the SESSION SQL parameter. Only one TRANSACTION SQL parameter can be used in each process section.

You must define the rollback of the EIM process by doing either of the following:

Add the TRANSACTION SQL parameter in the configuration file
Use the Server Manager to set the Database Rollback Segment Name parameter of the Enterprise Integration Mgr component at the component level

To avoid errors, do not specify the rollback segment:

When using the siebenv.bat file
At the task level
When using both the configuration file and the Server Manager

Note: Do not use the TRANSACTION SQL parameter to insert or update data in Siebel base tables.

To define the rollback segment in the configuration file

Add a line (as shown in the following example for an Oracle database) to the EIM configuration file.
```
TRANSACTION SQL = "set transaction use rollback segment rb_big"
```

To define the rollback segment using the Server Manager

Navigate to Administration - Server Configuration screen, Servers, Components, and then the Parameters view.
In the Components list, select Enterprise Integration Mgr.
Click the Component Parameters view tab.
In the Component Parameters list, select Database Rollback Segment Name.
In the Current Value field, type the name of the rollback segment to be used and click Save.
For more information on using the Server Manager, see Siebel System Administration Guide.

Setting Extended EIM Configuration Parameters

You can dynamically name and define extended parameters. This section explains how to use extended parameters in the EIM configuration file.

User-Defined Extended Parameters

Use extended parameters to create new parameter names and define values. You can define extended parameters using either the GUI or the command-line interface. User-defined extended parameters use the $name=value format inside the EIM configuration file, and the name=value format in the GUI or the command-line interface. The parameter can be a character string consisting of any alphanumeric characters; the underscore symbol (_) can also be used.

To define extended parameters using the GUI

Navigate to the Administration - Server Management screen.
From the link bar, click Jobs.
In the Jobs list, click New.
The component job status field changes to Creating.
In the Component/Job field, click the select button.
In the Component/Jobs window, select the Enterprise Integration Mgr component, and then click OK.
If you want to use a component job template based on EIM for your component job, you must first define the component job template. For information on defining component jobs, see Siebel System Administration Guide.
Complete the rest of the fields and click Save.
In the Job Parameters list, click the menu button and then New Record.
In the Name field, click the Select button.
In the Job Parameters window, select Extended Parameters, and then click OK.
In the Value field, type in extended parameters using the comma-delimited format name=value,name=value as shown in the following example:
```
ACCT_NAME=COMPAQ,ACCT_NUM=01101,ACCT_CONTACT=John Dove, CONTACT_PHONE=(987)123-
4567
```
If you are defining multiple values for an extended parameter, you need to enclose the values in double quotes preceded by a backslash as shown in the following example:
```
\”BatchNum1=20001”
```
Click Save.
In the Component Job form, click the Submit Job button.

To define extended parameters using the command-line interface

Use the reserved keyword ExtendedParams to define the name=value format as shown in the following example:
```
ExtendedParams=”ACCT_NAME=COMPAQ,ACCT_NUM=01101, ACCT_CONTACT=John 
Dove,CONTACT_PHONE=(987)123-4567”
```
Note: You must enter extended parameters in double quotes when using the Server Manager command-line interface.
Run EIM to test the extended parameters.

Predefined Extended Parameters

Some extended parameters are predefined in Siebel applications. These parameters also use the name=value format. The following information lists these predefined extended parameters.

Parameter	Description	Example
CURRENT_USER	Logon name of current user	`CURRENT_USER =Customer1`
PASSWORD	Password of current user	`PASSWORD=ABC`
CURRENT_DATETIME	Current date and time information	`CURRENT_DATETIME= 11/3/98_22:45`
ROOT_DIR	Home directory of Siebel Server	`ROOT_DIR=Siebel`
SIEBEL_FILE_DIR	Siebel file system	`SIEBEL_FILE_DIR=Files`
LANGUAGE	Language of Siebel Server installation	`LANGUAGE=English`
TABLE_OWNER	Name of tableowner	`TABLE_OWNER=ora22`
ODBC_DATA_SOURCE	Connect string for ODBC data source	`ODBC_DATA_SOURCE=sun1`
MAX_NEST_SUBST	Maximum level of nesting in parameter substitutions. The default value is 10.	`MAX_NEST_SUBST=10`
NUM_IFTABLE_LOAD_CUTOFF	When this parameter is enabled, EIM loads all schema mappings if the value is less than the number of EIM tables used in the run process. To enable, set the value to a positive number that is less than the number of EIM tables used in the run process. For example, if the EIM process is using one EIM table, then the setting should be `NUM_IFTABLE_LOAD_CUTOFF = 0`. When disabled, EIM loads only mappings for EIM tables used in the run process. This speeds up the dictionary loading process in EIM. To disable, set the value to -1. This feature is disabled by default. For more information, see Example of Using the NUM_IFTABLE_LOAD_CUTOFF Parameter.	`NUM_IFTABLE_LOAD_CUTOFF=-1`
IfbFileName	Name of the .IFB file where resolved parameters are stored.	`IfbFileName=TEST`
TraceFlags	Contains logs of various EIM operations. Available TraceFlags include 1, 2, 4, 8, and 32. For descriptions of available TraceFlags, see Trace Flags.	`TraceFlags=2`

Sample SQL Scripts

Use the following sample SQL scripts as a starting point for your own scripts. These scripts each provide an example of the data that is necessary when loading account and contact records. Sample scripts are provided for the following RDBMSs:

DB2 Sample SQL Script

insert into Siebel.EIM_ACCOUNT

(ROW_ID, IF_ROW_BATCH_NUM,IF_ROW_STAT, PARTY_UID, PARTY_TYPE_CD, 
ROOT_PARTY_FLG,PARTY_NAME, NAME, MAIN_PH_NUM, LOC, ACCNT_BU, ACTIVE_FLG, 
DISA_CLEANSE_FLG, EVT_LOC_FLG, FCST_ORG_FLG, INT_ORG_FLG, PROSPECT_FLG, PRTNR_FLG, 
PRTNR_PUBLISH_FLG, RPLCD_WTH_CMPT_FLG, SKIP_PO_CRDCHK_FLG)

values

('100', '100','FOR_IMPORT', 'AUID1', 'ACD1', 'Y', 'Party1', 'Account1', 
'6505511784','HQ', 'Default Organization', 'Y', 'Y','Y','Y','Y','Y', 
'Y','Y','Y','Y');

insert into Siebel.EIM_CONTACT

(ROW_ID, IF_ROW_BATCH_NUM, IF_ROW_STAT, PARTY_UID, PARTY_TYPE_CD, ROOT_PARTY_FLG, 
ADDR_NAME, DEPT_ACCNT_BU, DEPT_ACCNT_LOC, DEPT_ACCNT_NAME,  CON_PERSON_UID, CON_BU, 
CON_ACTIVE_FLG, CON_DISACLEANSEFLG, CON_DISPIMGAUTHFLG, CON_EMAILSRUPD_FLG, 
CON_EMP_FLG, CON_FST_NAME, CON_LAST_NAME, CON_PO_PAY_FLG, CON_PRIV_FLG, 
CON_PROSPECT_FLG, CON_PTSHPCONTACTFL, CON_PTSHPKEYCONFLG, CON_SUPPRESSEMAILF, 
CON_SUPPRESSFAXFLG, CLINT_ACCNT_BU, CLINT_ACCNT_LOC, CLINT_ACCNT_NAME, 
PP_PARTY_TYPE_CD, PP_PARTY_UID, PP_REF_FLG, PP_START_DT)

values

('200', '200', 'FOR_IMPORT', 'CUID1', 'CCD1', 'Y', 'Address1', 'Default 
Organization', 'HQ', 'Account1', 'CONUID1', 'Default Organization', 
'Y','Y','Y','Y','Y','Tom','Hanks', 'Y','Y','Y','Y','Y','Y','Y','Default 
Organization', 'CrossRoads', 'Account2', 'ACD1', 'AUID1', 'Y', ‘2000-05-17-
15.40.55.000000');

MS SQL Sample SQL Script

insert into dbo.EIM_ACCOUNT

(ROW_ID, IF_ROW_BATCH_NUM,IF_ROW_STAT, PARTY_UID, PARTY_TYPE_CD, 
ROOT_PARTY_FLG,PARTY_NAME, NAME, MAIN_PH_NUM, LOC, ACCNT_BU, ACTIVE_FLG, 
DISA_CLEANSE_FLG, EVT_LOC_FLG, FCST_ORG_FLG, INT_ORG_FLG, PROSPECT_FLG, PRTNR_FLG, 
PRTNR_PUBLISH_FLG, RPLCD_WTH_CMPT_FLG, SKIP_PO_CRDCHK_FLG)

values

('100', '100','FOR_IMPORT', 'AUID1', 'ACD1', 'Y', 'Party1', 'Account1', 
'6505511784','HQ', 'Default Organization', 'Y', 'Y','Y','Y','Y','Y', 
'Y','Y','Y','Y')

insert into dbo.EIM_CONTACT

(ROW_ID, IF_ROW_BATCH_NUM, IF_ROW_STAT, PARTY_UID, PARTY_TYPE_CD, ROOT_PARTY_FLG, 
ADDR_NAME, DEPT_ACCNT_BU, DEPT_ACCNT_LOC, DEPT_ACCNT_NAME,  CON_PERSON_UID, CON_BU, 
CON_ACTIVE_FLG, CON_DISACLEANSEFLG, CON_DISPIMGAUTHFLG, CON_EMAILSRUPD_FLG, 
CON_EMP_FLG, CON_FST_NAME, CON_LAST_NAME, CON_PO_PAY_FLG, CON_PRIV_FLG, 
CON_PROSPECT_FLG, CON_PTSHPCONTACTFL, CON_PTSHPKEYCONFLG, CON_SUPPRESSEMAILF, 
CON_SUPPRESSFAXFLG, CLINT_ACCNT_BU, CLINT_ACCNT_LOC, CLINT_ACCNT_NAME, 
PP_PARTY_TYPE_CD, PP_PARTY_UID, PP_REF_FLG, PP_START_DT)

values

('200', '200', 'FOR_IMPORT', 'CUID1', 'CCD1', 'Y', 'Address1', 'Default 
Organization', 'HQ', 'Account1', 'CONUID1', 'Default Organization', 
'Y','Y','Y','Y','Y','Tom','Hanks', 'Y','Y','Y','Y','Y','Y','Y','Default 
Organization', 'CrossRoads', 'Account2', 'ACD1', 'AUID1', 'Y', '02-FEB-2002')

insert into EIM_ACCOUNT

(ROW_ID, IF_ROW_BATCH_NUM,IF_ROW_STAT, PARTY_UID, PARTY_TYPE_CD, 
ROOT_PARTY_FLG,PARTY_NAME, NAME, MAIN_PH_NUM, LOC, ACCNT_BU, ACTIVE_FLG, 
DISA_CLEANSE_FLG, EVT_LOC_FLG, FCST_ORG_FLG, INT_ORG_FLG, PROSPECT_FLG, PRTNR_FLG, 
PRTNR_PUBLISH_FLG, RPLCD_WTH_CMPT_FLG, SKIP_PO_CRDCHK_FLG)

values

('100', '100','FOR_IMPORT', 'AUID1', 'ACD1', 'Y', 'Party1', 'Account1', 
'6505511784','HQ', 'Default Organization', 'Y', 'Y','Y','Y','Y','Y', 
'Y','Y','Y','Y');

insert into EIM_CONTACT

(ROW_ID, IF_ROW_BATCH_NUM, IF_ROW_STAT, PARTY_UID, PARTY_TYPE_CD, ROOT_PARTY_FLG, 
ADDR_NAME, DEPT_ACCNT_BU, DEPT_ACCNT_LOC, DEPT_ACCNT_NAME,  CON_PERSON_UID, CON_BU, 
CON_ACTIVE_FLG, CON_DISACLEANSEFLG, CON_DISPIMGAUTHFLG, CON_EMAILSRUPD_FLG, 
CON_EMP_FLG, CON_FST_NAME, CON_LAST_NAME, CON_PO_PAY_FLG, CON_PRIV_FLG, 
CON_PROSPECT_FLG, CON_PTSHPCONTACTFL, CON_PTSHPKEYCONFLG, CON_SUPPRESSEMAILF, 
CON_SUPPRESSFAXFLG, CLINT_ACCNT_BU, CLINT_ACCNT_LOC, CLINT_ACCNT_NAME, 
PP_PARTY_TYPE_CD, PP_PARTY_UID, PP_REF_FLG, PP_START_DT)

values

('200', '200', 'FOR_IMPORT', 'CUID1', 'CCD1', 'Y', 'Address1', 'Default 
Organization', 'HQ', 'Account1', 'CONUID1', 'Default Organization', 
'Y','Y','Y','Y','Y','Tom','Hanks', 'Y','Y','Y','Y','Y','Y','Y','Default 
Organization', 'CrossRoads', 'Account2', 'ACD1', 'AUID1', 'Y', '02-FEB-2002');