General Process Parameters in IFB

These are the parameters which are common to all the EIM process (Import,Export,Delete,Merge) and are written with in the Process section in an IFB file. They are :-

BATCH

• Required field that specifies the batch number, which is used to identify the set of records that should be considered for this EIM process.
• This batch number corresponds to the number specified in the IF_ROW_BATCH_NUM column of the EIM table.
• Valid values are 0 to 2147483647 (2³¹ – 1).
• Batch numbers can be specified in ranges or as a comma delimited format.
• Example: BATCH = 100 – 110, BATCH = 100, 103, 120.
• If batch number is specified wrongly in IFB file, the EIM throws an error stating, no records found for the stated batch number.

COMMIT EACH PASS

• Optional parameter that specifies whether the process needs to do a commit after every EIM passes.
• Pass is defined as one SQL DML statement that got executed.
• Valid values are TRUE or FALSE.
• Default value of this parameter is TRUE.
• This parameter should be set to FALSE while using in delete or merge process. Since it commits after each pass, and in case of any failures, the database is left corrupted with dangling foreign key references, etc…
• Example: COMMIT EACH PASS = FALSE

COMMIT EACH TABLE

• Optional parameter that specifies whether the process needs to do a commit after processing each base table.
• Valid values are TRUE or FALSE.
• Default value of this parameter is TRUE.
• This parameter should be set to FALSE while using in delete or merge process.
• The reason behind this is, since it commits after each pass, and in case of any failures, the database will be left corrupted with dangling foreign key references, etc…
• Example: COMMIT EACH TABLE = FALSE

IGNORE BASE TABLES

• Optional parameter that specifies which base tables has to be ignored for the process for the particular EIM table.
• This parameter improves the EIM performance.
• Example: IGNORE BASE TABLES = S_PARTY_PER, S_ORG_BU

INCLUDE

• Optional parameter that specifies which other sub-process needs to be included in the process in question.
• Example: INCLUDE = Import Contacts

LOG TRANSACTIONS

• Optional parameter that tells whether to log transactions or not.
• Valid values are TRUE or FALSE.
• Default value depends on the DOCKING: TRANSACTION LOGGING parameter defined in the System Preferences.
• Example: LOG TRANSACTIONS = FALSE

ONLY BASE TABLES

• Optional parameter that specifies which base tables has to be considered for the process for the particular EIM table.
• This parameter improves the EIM performance.
• Example: ONLY BASE TABLES = S_PARTY, S_ORG_EXT, S_ADDR_ORG, S_ORG_BU, S_ACCNT_POSTN

ROLLBACK ON ERROR

• Optional parameter that specifies whether a rollback has to be made if any failure occurs during the EIM process.
• Valid values are TRUE or FALSE.
• Default value is FALSE.
• This parameter should be set to TRUE while using in delete or merge process. In case of any failure, the database will be roll backed to the last commit point and thus avoiding the database corruption.
• Example: ROLLBACK ON ERROR = TRUE

SESSION SQL

• Optional parameter that specifies a user defined SQL statement to be sent to database for execution before any other SQL statements.
• This parameter can be used to set tracing for performance analysis.
• Only one SESSION SQL parameter is allowed per process section.
• This parameter cannot be used to insert or update any data in Siebel tables.
• Example: SESSION SQL = "UPDATE EIM_CONTACT SET PP_START_DT = SYSDATE WHERE IF_ROW_BATCH_NUM = 200”

SKIP BU_ID DEFAULT

• Optional parameter that specifies whether to use the default BU_ID defined in the repository.
• Valid values are TRUE or FALSE.
• Default value is FALSE.
• If set to FALSE, the BU_ID defined in the repository is used for BU_ID columns in the base tables.
• If set to TRUE, the values set in the interface table is used.
• This parameter is only limited to insert, delete and merge process, because the foreign key must be resolved for these processes.
• Example: SKIP BU_ID DEFAULT = TRUE

TABLE

• Required parameter that specifies the EIM table to be used for the process.
• Example: TABLE = EIM_ACCOUNT
• For performance reasons, the number of tables should be limited to fewer than five for a merge or export process.

TRANSACTION SQL

• Optional parameter that specifies a user defined SQL statement to be sent to database before other SQL statements are processed and immediately after every commit or rollback operation.
• If both SESSION SQL and TRANSACTION SQL parameters are specified, the latter gets executed immediately after the former.
• Only one TRANSACTION SQL parameter can be defined per process section.

TYPE

• Required parameter that specifies the type of EIM process.
• Typical process types are IMPORT, EXPORT, MERGE, DELETE and SHELL.
• SHELL process defines that this process has other sub-processes that needs to be executed.

USE ESSENTIAL INDEX HINTS

• Optional parameter specified for MS SQL Server and Oracle databases.
• Valid values are TRUE or FALSE.
• When set to TRUE, it enables a subset of index hints for MS SQL server.
• Default value is TRUE.

USE INDEX HINTS

• Optional parameter specified for Oracle databases only.
• Valid values are TRUE or FALSE.
• When set to TRUE, EIM issues optimizer hints to the database in order to improve the performance.
• Default value is FALSE.
• Example: USE INDEX HINTS = TRUE

USING SYNONYMS

• Optional parameter that specifies whether to use the account synonyms during the import process.
• Valid values are TRUE or FALE.
• Default value is TRUE.
• In order to improve the performance, set this parameter value to FALSE, but care must be taken while specifying this parameter.