Organization Columns  

Posted by Rajesh

The EIM_ type interface tables use the xxx_BU/xxx_BI column pairs to map organizations. For
example, the CON_BU/CON_BI column in the EIM_CONTACT interface table is mapped to the BU_ID column in the S_CONTACT base table.

In order for organizations to be resolved properly, you need to populate the xxx_BU column with the organization name and leave the xxx_BI column empty. Do not populate the xxx_BU column with the organization ROW_ID. EIM looks up the ROW_ID for the organization in xxx_BU and puts it in the corresponding xxx_BI column.

File Attachment Columns  

Posted by Rajesh

Three EIM table columns must be populated in order to import file attachments. Table describes these columns and uses the attachment file budget99.doc as an example.

Table . File Attachment Columns
FILE_NAME:
This column requires the root filename of the file
attachment. (ex FILE_NAME=.budget99.)
FILE_EXT: This column requires the extension type of the file attachment (DOC, XLS, or TXT). (ex FILE_EXT="doc")
FILE_SRC_TYPE: This column requires the value "FILE" or the rows
cannot be imported. (ex FILE_SRC_TYPE="FILE")

You can also use these columns to define hyperlinks,.
Defining Hyperlinks With File Attachment Columns
Column Setting
FILE_NAME Set to actual URL
FILE_EXT NULL
FILE_SRC_TYPE . URL.

Temporary columns.  

Posted by Rajesh

EIM uses temporary columns to manipulate data during processing. For example, EIM might store the ROW_ID value for a Siebel base table in a temporary column. These column names begin with T_ and indicate the table or column for which they are used. Because EIM uses these columns internally during processing, do not manipulate these columns in the EIM tables.

Mandatory Columns for EIM Processing  

Posted by Rajesh

ROW_ID. For an EIM table row to be eligible for processing, you must initialize its ROW_ID. The ROW_ID, in combination with the value of IF_ROW_BATCH_NUM, must yield a unique value. The ROW_ID values in the EIM tables are not the ROW_ID values that are assigned to the row when it is loaded into the base table. An EIM-generated ROW_ID has a ##-###-### format. A regular row ID that is assigned to the row has a #-## format.

IF_ROW_BATCH_NUM. You must set the values in this column to the same integer, greater than or equal to 0, as an identifying number for all rows to be processed as a batch. The maximum value is 2147483647. Use this column as the first key of any new indexes created on an EIM table.

IF_ROW_MERGE_ID. You can set this column to one of two values:
■ NULL: This value identifies the surviving or merged-into-row.
■ROW_ID:This value identifies the ROW_ID number in the EIM table where the row will be
merged.

IF_ROW_STAT. EIM updates this column after processing the row to indicate the status of the record. The IF_ROW_STAT column is not used by EIM when determining which rows to process. When populating the EIM tables, you can set this column to any value except NULL. You can initially set this value to FOR_IMPORT to indicate that the row has not been imported. After processing, if certain rows were not imported due to a data error, you should change:
■ IF_ROW_BATCH_NUM value for the rows that require reimporting
■ BATCH line in the configuration file
If EIM updates this column to NOT_ALLOWED after processing a row, EIM has attempted to insert a new row but the action is not allowed. In such cases, the INSERT ROWS parameter may have been set to FALSE.

IF_ROW_STAT_NUM. After processing, this column contains a zero (0) if a row was successfully processed to completion. If processing failed, this column contains the pass number where the pass failed.