EIM Interview Questions

Q 1 : When I tried to set the primary employee for the position through EIM, it is not getting updated. Why?

Ans :
While updating the primary employee for position, apart from setting the POSTN_PR_EMP column in the EIM table, you should also define the MISC SQL parameter in your IFB file.

Q 2 : Although setting the trace flags, I’m not able to see log information in the log file. Why?
Ans :
You should configure your component event levels as described below :-

                               Event Type                                                  Log Level
                            ----------------------                                              ---------------
                            SQL Tracing                                                          4
                            SQL Summary                                                      4
                            Task Configuration                                                 4
                            Component Tracing                                                3

Q 3 : What does IFB stands for?
Ans :
IFB stands for InterFace Builder.

Q 4 : Can I use more than one IFB file for an EIM process?
Ans :
No, it’s not possible. You can use shell process in case if you want to do more than one operation in a single EIM task.

EIM Merge Process Overview

• This process merges multiple records into one surviving record.
• During Merge Process we identify the Parent record and Child records to be merged into that.
• Records loaded in the identified interface table are matched against the corresponding base tables based on the user primary keys.
• All the references (ROW_ID) of Child records will be replaced by parent record and Child records will be deleted.
• While Populating the EIM ,IF_ROW_MERGE_ID is used to distinguish between  parent and child records by EIM process.

EIM Delete Process Overview

• This process deletes the records from the Siebel base tables.
• Deletes records from the base table by identifying the records in the base on the basis of the user keys specified in the corresponding interface table.
• Deletes all records from the Siebel base table if the parameter DELETE ALL ROWS is specified as true. For this process the records are not populated in the interface table. Even if the records are populated on using this parameter EIM component skips these records and proceed by deleting all the rows in the given base table
• If  the DELETE MATCHES parameter is specified then only those records are deleted that matches the condition in the WHERE clause.  
• On successful deletion the IF_ROW_STAT column of the interface table will have the status as DELETED.

EIM Export Process Overview

• This process allows to pull the existing records from the Siebel base tables.
• The interface table need to be correctly identified.
• Create the configuration file with suitable parameters as in EXPORT ALL or EXPORT MATCHES according to the requirement
• Start the EIM job manually by logging into the application and navigating to Administration – Server or via the command line.

EIM Import Process Overview

• The process drives the new record inserts and updates on existing records in the Siebel base table.
• The interface table need to be correctly identified.
• Load the business data into the identified interface tables. 
• Create the configuration file.
• Set the value of IF_ROW_STAT to FOR_IMPORT before load.
• Make sure all the user key columns and the required columns for the targeted base tables are populated in the corresponding columns mapped in the interface tables.
• Start the EIM job manually by logging into the application and navigating to Administration – Server or via the command line.

An Overview to EIM Process

There are four types of process in EIM. They are :-

• Import Process.
• Export Process.
• Delete Process.
• Merge Process.

Import Process

• Import Process is basically used to Insert or Update the data from external system into the Siebel base tables.
• Identify and validate the data to be imported.
• Identify the column mappings and user key columns of the data to be imported.
• Import the data in the order of the business model.
• Set the value of IF_ROW_STAT to FOR_IMPORT before load which will get changed to IMPORTED after process successfully commits.

To know more on import process, click here . . .