Overview : This document gives overview on Siebel 6.x , 7.

x Architecture and Data Model of Siebel with respect to Siebel Interview. Sample Interview Questions on this Topic:
1. What does an opportunity, account contact do in Siebel? Answer: In Siebel, Opportunity, Account and Contact are the business entities and these entities have relationships. For example opportunity to account M:1 and account to opportunity 1:M . 2. How is the opportunity related to an account? Ans: opportunity to account M:1 and account to opportunity 1:M. 3. How is tools architecture constructed in Siebel? . 4. What is the new layer in Siebel 7.x version? Answer: Physical User Interface Layer 5. Why is it not recommended to modify existing base tables? Answer: During upgradation it will cause problem if we extend base tables. More over if it is necessary u can go for extension tables. Modifying base tables would affect the performance of the siebel application. 6. How do you create extension table to an interface table in Siebel? Ans: Extension tables are created only for base tables can not extend Interface tables.

7. What is an extension table and how is it related to base table? Answer: Extension tables provide additional columns that you can use to store custom attributes. Extension tables have either an implicit 1:1 or a 1:M relationship with a given base table. Siebel Systems provides a set of preconfigured extension tables that are set aside for customer use. These tables are known as static extension tables. Static extension tables include generic columns (ATTRIB_) that you can use to store custom attributes. Static extension tables are already part of the data model, so using them does not require updating the physical database. 8. Can you create an extension table with an intersection table? Answer: We cannot create Extension table for Intersection Table only we can use extension column for Base table .

10.How is Siebel 7.x data model is different from Siebel 6.0 data model? Answer: The main difference is the S_PARTY Table is introduced in Siebel 7.x data model. S_PARTY is the base tables and S_CONTACT,S_ORG_EXT,S_POSTN, S_USER are now extension tables. Siebel 6.x was dedicated application while from Siebel 7.x onwards we can access Siebel application via web. 9. What is seed data in Siebel? Ans: The data that siebel supplies, as a part of siebel vanilla application is seed data. 10.What is S_PARTY table? Ans S_PARTY Table is the Base Table for all the Party related tables. S_ORG_EXT S_CONTACT S_USER S_BU And etc. The party tables can have the implied joins. the party related BC's have the S_PARTY as the base table. So, any of these tables are extension tables. 11.How is Siebel 7.x architecture different from Siebel 6.x? Answer : 12.What is Siebel file system? Answer: 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.

13. How can we say the Performance increases if we make use of

S_PARTY , can you elaborate with real time ? Ans: There are two kinds of Joins in Siebel. 1. Implicit Join 2. Explicit Join Implicit Joins are from base table to extension table. And the Foreign Key in this case will be there in Extension Table. So, these Joins is faster than Explicit Join. To utilize this feature siebel has introduced concept of Party Tables. S_PARTY will be the base table for all the party tables and they are extended tables to S_PARTY. All the Business Component's will use S_PARTY as the base table. and make joins to get the columns from different tables.

If you have S_CONTACT as base table and you have to get a column from S_ORG_EXT then you have to create a Explicit Join. Where as if you have S_PARTY as the base table then all the party tables like S_CONTACT, S_ORG_EXT, S_USER are the extension tables we can create Impilicit Joins. So, in this way the performance will be increased using the Implicit Joins 14.What is the difference between S_OPTY , S_OPTY_X and S_OPTY_XM? Ans: s_opty is a base table for which s_opty_x is an extension table with 1:1 relationship s_opty_xm is an extension table with 1:M relationship

15. What is the purpose of 1:M extended table? Answer:

We can use it in parent child relationship where the child entity is lonely related to the parent table. (or) we can make it as a intersection table by adding the foriegn key of another table's primary key in the 1:M extended table.

16. What is an extension table and how is it related to base table? Ans : Extension tables are 1:1 or 1:M extensions of Base tables, like
S_PARTY (base) has S_CONTACT etc. For a 1:1 extension there is implict join but for a 1:M extension. You can only extend a base table. For 1:1 there is a PAR_ROW_ID to ROW_ID join and for a 1:M there is 3 different columns that represents a unique record.

17. How do you recognize that a particular table(Base table) can be extended?
Ans : If the table property is Private, then we can not extend the table. If it is Pubilc, we can

18.

What are different types of tables?

Ans : There are 3 types of tables. Data Tables Repository tables( eg : S_APPLET, S_BUSCOMP , S_BUSOBJ , S_VIEW) Interface tables(used for EIM) Again Data Tables are categorized into Base tables (eg : S_CONTACT , S_ORG_EXT ..etc) Extension tables (eg:: S_CONTACT_X , S_ORG_EXT_X..etc) EIM tables (eg: EIM_ACCOUNT, EIM_ASSET..etc) Intersection tables (eg: S_ORG_BU. , S_CON_ADDR..ect)

19.

What are the different types of columns?

Ans:

1.Data (Public), 2.Data (Private), 3.Denormalized, 4.Extension, 5.System

20.

Detailed Theory : Architectural Layers of Object Definitions

Client Server Architecture for Siebel Web Engine

Overview of the Major Object Types and Their Relationships

S_PARTY: Serves as the base table for all party business components o Stores the party name and party type Has multiple extension tables that store the business data for the party business components. Party refers to all types of Siebel person and business entities. This includes: Person-related entities ( for example Contact , Employee, User , Partner Employee) Organization-related entities( for example Account , Position , Division ,Organization Household) Grouping for access control ( for example , Access Group , User List) Important points for S_PARTY Configuring business components o All person-related business component use S_CONTACT o All organization related business component use S_ORG_EXT o Over 100 party related business component reference S_PARTY but store their data in one of the many S_PARTY extension tables. Importing data for party-related business components o You must populate columns in S_PARTY table in addition to tables that store the data of interest to users. Importing data for organization-related business components: o For single organization data , you must populate BU_ID

o For multi organization data , you must populate the corresponding intersection table. S_PARTY table columns are 1.ROW_ID 2.NAME 3.PARTY_TYPE_CD 4.PARTY_UID

S_PARTY_PER In the implied join between S_PARTY_PER and S_PARTY S_PARTY_PER.PARTY_ID maps to the groups row ID (S_ORG_EXT.ROW_ID) S_PARTY_PER.PERSON_ID maps to the members row ID(S_CONTACT.ROW_ID) Primary Key / ROW_ID Primary key is a column that uniquely identifies each row in a table. ROW_ID Serves as the primary key for Siebel database tables. ROW_ID is a column in every table , contains a Siebel application-generated identifier that is unique across all tables and mobile users. ROW_ID is the means by which Siebel applications maintain referential Integrity ROW_ID is managed by Siebel applications and must not be modified by users. User Key Index Specifies columns that must contain a unique set of values. Prevents users from entering duplicate records User Key is used to determine the uniqueness of records during data import operations. Cannot be edited.

Index is a separate data structure that stores a data value for a column and a pointer to the corresponding row.Index are used to retrieve and sort data rapidly. Index should be inspected to assess performance issues for query and sort operations. Index can be created by configurators

Prominent Data Tables : S_PROD_INT S_SRV_REQ S_CONTACT

: Internal Product : Service Request : Contact

S_OPTY : Opportunity S_ORG_EXT : Account S_ASSET : Asset

Account: Is a business external to your company or represents a current potential client, a business partner, or a competitor Opportunity: Is a potential revenue-generating event Contact: Is a person with whom you do business Service Request: Is a request from a customer for information or assistance with a problem related to products or services purchased from your company Activity Is a specific task or event to be completed. Has the characteristic like Start data and due data, Priority and assigned to specific employees for completion. Asset: Is an Instance of a purchased product.