Running EIM is an iterative process, with each step accomplishing specific tasks and moving toward successful completion of the entire process. To process on a row-by-row basis, EIM uses several columns common to every EIM table. These columns are described in this section.
Several columns are mandatory. Others are conditionally mandatory, depending on the conditions of your import. To determine mandatory columns, use Siebel Tools to view each column in an EIM table and the EIM table.s target base table columns.
By following the recommended import sequence, you make sure that the appropriate data
dependencies are established.

NOTE: For import and merge processes, you must populate the ROW_ID, IF_ROW_STAT, and IF_ROW_BATCH_NUM columns in the EIM tables. This also must be done for delete processes when you run DELETE EXACT. For merge processes, you also need to populate the IF_ROW_MERGE_ID column. Do not populate these required columns with spaces because a space does not equal a NULL value.

EIM tables in the Siebel database use a three-part naming convention; the syntax is:
PREFIX_NAME_SUFFIX. These three parts are described as follows:

■PREFIX. All interface tables used by EIM have the prefix EIM_ (such as EIM_ACCOUNT). These EIM tables support Organizations, so they can be used for all EIM processes.
NOTE: Previous versions of EIM used a different set of EIM (interface) tables, identified by the
prefix S_ and the suffix _IF. These tables still appear in the Siebel database, but are inactive.
These tables will not be included in the Siebel database in future versions. If you need these
tables activated temporarily, contact Siebel Expert Services.

■ NAME. A unique table name that is generally composed of an abbreviation of an entity type
name. If more than one EIM table is required to fully support an entity, a sequential number may be added to the name of each table after the first one.

■ SUFFIX. A supertype name may be followed by a suffix that indicates the types of data
supported by the EIM table or to distinguish it as an EIM table.

Siebel EIM tables are intermediate database tables that act as a staging area between the base
tables in the Siebel database and other databases. EIM tables are designed to be simple and
straightforward so they can be loaded or read by way of external programs.This section provides an overview of how EIM works with these EIM tables and how table names are derived.

1 Import Data into Siebel Base Tables:
The EIM import function can be used in several different ways:

• When initially implementing a Siebel application, load the Siebel database tables with data and file attachments created by external applications. For example, you can import information about product lines and products from an inventory control database into the Products entity in the Siebel database.
• As part of maintaining the Siebel database, you can use EIM for data archival. This not only provides customers with a Siebel database that is optimally using the resources available to it, but also streamlines the implementation of a corporate data archival strategy.
• As part of maintaining a non-Siebel database, you can update it with information from the Siebel database. For example, you might add new customers to an accounting database from the Siebel database.

2 Export Data from Siebel Base Tables:
The data contained within a Siebel application is available for transfer to non-Siebel applications by using EIM. When implementing a non-Siebel application, you can export data from the Siebel
database tables for use by that application. For example, you can export employee information to a corporate sales commission application.

3 Delete Data from Siebel Base Tables:
As part of maintaining the Siebel database, you can identify rows to be deleted from a table and its associated child and intersection tables. For example, you might delete an obsolete product line and its associated products.

4 Merge Data in Siebel Base Tables:

In response to such external events as corporate mergers, you can merge two or more database rows into a single row. For example, you might merge the Frame, Inc. account information into the Adobe Corp. account.