Troubleshooting EIM

Well there are few ways to import data into Siebel but my favorite is EIM since its much faster than the others.Also it's much interesting when it involves loading data in millions and billions.But probably not an interesting area for most of the Siebel developers out there because it does not involve lot of design and customization but leveraging OOB functionalities to import data. I had been working more actively in EIM these days and identified the following steps to run and troubleshoot EIM jobs.


> To create the import script use the EIM reports in tools (Client from 8.1) and identify the required columns and foreign keys to be imported.
>Look at the foreign key column mapping to populate all the UK columns required to resolve the FK during EIM. Also, this will help us identify the various base tables required to populate UK columns in EIM tables.
>Better keep number of rows less than 5000 rows in a batch .Siebel recommends < 20k
> Run the EIM job for few records at first ,in numbers less than 100 with sql flags,error flags and task flags set to 8
>Check the IF_ROW_STAT for all the records imported in the EIM table
>Check the if_row_stat_num for all the records imported .If the row status number is not zero look for the status number in log file to get more info on the error against all the base tables.
> Check the temporary columns row_id for the base tables and check if the foreign key columns are correctly populated.

If I find more in addition to this will post it later..