Siebel CRM Interview Preparation Guide

Download PDF

SIEBEL is the leading provider of Customer Relationship Management (CRM) software.

multivalue field has the child values from a chind BC for the parent record configured through MVL. single value field will be either from the base table or joined table.
the Difference between Single Value Field (SVF) and Multi Value Field(MVF)
SVF- a field in BC which references a column in a table
MVF- a field in parent BC which references a field in child BC
Field-Identifies and defines a field in a business component. All fields making up a business component record contain entries from both Single Value Field and Multi Value Field object types.

1:1 extension table is like an extension to the base table. if we do not have the required table space in the base table for craeting new extension columns, we will use the 1:1 extension table's columns using an implicit join.
in contrast, 1:M extension tables are used for parent child relationship with the base table. where the 1:M extension has only related to the base table. for example, for a contact (S_CONTACT) there will be a number of specialities in the extension table(S_CONTACT_XM) with the parent child relationship.

Complex joins are joins which have following diffrences from a PK-FK joins
# Complex joins can have conditional mappings like >,<,>=,NOT,AND,etc apart from '=' whereas the PK-FK joins are always '='.
# PK-FK joins are always (1-N), whereas complex joins can have (1 - 0,1) and (0,1 - N) kind of relationships

Modify the object definitions in the local repository.

We can enter free text incase of Unbounded Picklist. But, incase of Bounded Picklist, we can not enter freetext.

Actuavally we cannot modify the join fields we cannot do any modifications and updations on that fields to do these things we create the dynamic picklist or pickapplet.dynamic picklist to modify (to enter new records )in the join fields

are having lot of differences between siebel 7.7 and 7.5.2. the primary difference among them is " Symbolic strings are available in Siebel 7.7 and not available in 7.5.2". hence the future scope for upgradation like things are high in siebel 7.7.

1) Limit base tables and columns to be processed by using : only base Tables,ignore base Tables,only base Columns,ignore base Columns.
2) Always delete batches from EIM tables upon completion. Leaving old batches in the EIM table wastes space and can adversely affect performance. For other suggestions on working with batches.
3) Run independent EIM jobs in parallel. Two or more EIM processes can be started simultaneously by using the Siebel Server Manager.
4) Trace Flag Settings, using Synonyms, primary key only Parameters
Limiting the Number of Records and Rows for Merge Processes.
like this many techniques are there which will optimize the EIM process

The new views which are to be restricted from the other 3 users can be grouped up in a seperate responsibility and then the 1st user can be assigned that the newly created responsibility. This will save time and will ensure smooth operations as well.