DirecTutor.com

Choosing the correct interface table for Siebel EIM process

When migrating data to or from Siebel Base tables, one of the main tasks is to identify the Interface table that would be used in the EIM process. There are cases in which a base table can be loaded from more than one EIM Interface tables. In such cases, the choice of interface table could optimize the EIM performance significantly. ROW_ID and IF_ROW_BATCH_NUM are mandatory columns for EIM processing. 

Siebel EIM

Siebel EIM Import Order of Entities

The order in which legacy data is imported is critical to make sure that relationships between dependent data elements are established correctly. Siebel interface tables do not map one-to-one with Siebel target database tables. To make sure that the necessary data is present to establish relationships between data entities, import data in the following recommended order:

Siebel EIM

Component request parameters for running an EIM process

The component request parameters for running an EIM process are

1. Batch Number:  This parameter is used for identifying the rows to be processed by the EIM process. Value 0 specifies the EIM process to use the batch number as specified in the EIM configuration file.


2. Configuration file: This parameter names the configuration file to be used by the EIM process. This file should be placed in the ADMIN subdirectory of the Siebel server.

Siebel EIM

Running the Siebel EIM Process

The EIM Process consists of executing the following sequence of steps:

1.Populate the columns in the Interface/ EIM table that are required to load the Siebel base
2.Write/Edit the EIM Configuration (IFB) File to define the EIM Process to perform
3.Submit the EIM as a Siebel Server Batch component task

Siebel EIM

Mystery of Siebel EIM Merge Process Explained

A merge process deletes one or more existing rows from the base table and ensures that intersecting table rows are adjusted to refer to the remaining rows. Some process parameters like TYPE, BATCH and TABLE are similar to that in case of the above mentioned processes. Upon completion of the merge process, the some row survives and the remaining rows are deleted.

Siebel EIM

Siebel EIM Delete Process Parameter Reference

Some process parameters like TYPE, BATCH, and TABLE are similar to an Import process.

DELETE ROWS: For Delete process the TYPE parameter should be defined as TYPE = DELETE. As a result the DELETE ROWS parameter will be automatically set to TRUE. This parameter can prevent deletions from one table while allowing them in others. For example, the following parameter prevents deletion of rows from the S_ADDR_PER table:

DELETE ROWS = S_ADDR_PER, FALSE

Siebel EIM

Siebel EIM Export Parameter Process Reference

Some process parameters like TYPE, BATCH, and TABLE are similar to an Import process.

EXPORT ALL ROWS: It implies that all rows in the target base table and data from the related child tables in a specific batch section are to be exported. Valid values are TRUE and FALSE (the default). When it is set to TRUE, the EXPORT MATCHES parameter is ignored, as it is selective export process.

Siebel EIM

How is IFB File Structured

An IFB file consists of two main sections namely:

Header Section: The .ifb file begins with a header section to specify global parameters that apply to all process sections.

Process Section: 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 ‘Type’, ‘Process Name’, ‘Batch Number’, ‘EIM Table Selection’ etc.

Siebel EIM

What is IFB file?

An IFB file is nothing but a EIM configuration file which is an ASCII or Unicode (Binary) text file of extension type .ifb. IFB stands for Interface Batch. It resides in the Admin directory of Siebel Server and allows the database administrator to define the type of EIM process like Import, Export, Merge and Delete to be performed.

Why IFB is needed?

Siebel EIM
Recent content