Explore topic-wise InterviewSolutions in .

It is a shared directory that stores compressed files USED by Siebel applications. Examples: Product literature, sales TOOLS, presentations Read/write access is controlled by the FILE System Manager component on Siebel Server.

It is a shared directory that stores compressed files used by Siebel applications. Examples: Product literature, sales tools, presentations Read/write access is controlled by the File System Manager component on Siebel Server.

Virtual BUSINESS Component is USED to display the DATA from ANOTHER LEGACY database table, in the Siebel screen.

Virtual Business Component is used to display the data from another Legacy database table, in the Siebel screen.

The basic factors for performance DECREASE in views will be. more number of applets. which led to MANY links. and more JOINED fields in a SINGLE applet. MVG's which do not have the PRIMARIES set.

The basic factors for performance decrease in views will be. more number of applets. which led to many links. and more joined fields in a single applet. MVG's which do not have the primaries set.

USING PICKLISTS and MVGs. MVGs REQUIRE join field and LINK as PREREQUISITES unlike picklists where just a join is enough.

Using picklists and MVGs. MVGs require join field and link as prerequisites unlike picklists where just a join is enough.

Constrainted PICKLIST displayed value based on CONSTRAINT used. Add field to constraint in pickmap of a field where picklist has configured in BC and SET constraint OPTION of added field to TRUE.

Constrainted picklist displayed value based on constraint used. Add field to constraint in pickmap of a field where picklist has configured in BC and set constraint option of added field to true.

Detailed Category and Aggregate Category are the TWO different sets. You can ADD a view to a screen under Detailed Category or an Aggregate Category. For Example: If I am creating two Views as detailes views. First I NEED to CREATE a Detailed Category. Then I have to create two Detailed Views, for which the "Category" property must be specified with the CREATED Detailed Category name. This is same for Aggregate Views also.

Detailed Category and Aggregate Category are the two different sets. You can add a view to a screen under Detailed Category or an Aggregate Category. For Example: If I am creating two Views as detailes views. First I need to create a Detailed Category. Then I have to create two Detailed Views, for which the "Category" property must be specified with the created Detailed Category name. This is same for Aggregate Views also.

Usually Drilldowns will be in List Applets only. But, in Siebel 6 there are Drilldowns on Form applets ALSO. But, these are not SIMILAR to those in List Applets. in order to go to the target view we need to right click on the applet, on the menu SHOWN we can find the AVAILABLE Drilldowns with Title as "Go To XYZ View".

Usually Drilldowns will be in List Applets only. But, in Siebel 6 there are Drilldowns on Form applets also. But, these are not similar to those in List Applets. in order to go to the target view we need to right click on the applet, on the menu shown we can find the available Drilldowns with Title as "Go To XYZ View".

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.

Optimization techniques in EIM
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.

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.

Optimization techniques in EIM
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.

Actually 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.

Actually 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.

We can enter free TEXT INCASE of Unbounded PICKLIST. But, incase of Bounded Picklist, we can not enter FREETEXT.

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

MODIFY the OBJECT DEFINITIONS in the LOCAL REPOSITORY.

Modify the object definitions in the local repository.

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.

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.

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.

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.

Multi Value field has the CHILD values from a child 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.

Multi Value field has the child values from a child 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.

SIEBEL is the LEADING PROVIDER of Customer RELATIONSHIP MANAGEMENT (CRM) SOFTWARE.

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