Thursday, August 16, 2012

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.

Q 5 : What is the effect of setting Docking Transaction Logging parameter to TRUE in case of EIM export?
Ans :
Any transaction logging won’t take place, since export process doesn’t change any data values. Also any parameter setting for transaction logging is ignored.

Q 6 : What is the use of DELETE SKIP PRIMARY parameter in EIM DELETE operation?
Ans :
The default value of this parameter is TRUE which doesn’t update the primary child column in the parent record when the primary child record is deleted. If set to FALSE, the primary child column is set to “No Match Row Id”.

Q 7 : How will I get the position details when I need to populate these values in the EIM table?
Ans :
The query listed below will fetch all the positions and their details in the underlying Siebel database.

Q 8 : Is it valid to set the configuration file in such a way to restrict inserts or updates in the target base table?
Ans :
Yes. You can disable the inserts or updates done to the target base table and still it won’t throw any error, provided the user keys and required column’s values are available.

Q 9 : Why am I getting “NOT_ALLOWED” in the IF_ROW_STAT column after EIM import?
Ans :
Possible reason could be the misuse of the INSERT ROWS or UPDATE ROWS parameter. When you set the INSERT ROWS parameter to false and you try to import new record, you will get this error. When you set the UPDATE ROWS parameter to false and you try to make changes to this particular record, you get this error.

Q 10: My EIM Delete fails by setting the IF_ROW_STAT column to AMBIGUOUS. Why?
Ans :
Whenever EIM encounters more than one record with same user key values but different CONFLICT_ID values, EIM cannot proceed with the delete operation and hence it sets the value “AMBIGUOUS” in the IF_ROW_STAT column.

Q 11: What is an Account Synonym? How it affects my EIM?
Ans :
A synonym is nothing but an alias name given for any account. These synonyms can be entered by the Siebel Administrator through Synonym Views. Whenever you do an EIM Import on accounts, EIM not only checks the user key in the base table but also checks the associated Synonyms for that account to find a match. This makes EIM time consuming. To suppress this behavior, you must set the USING SYNONYMS parameter to FALSE.

1 comment: