Hi,
Is it possible to add new party type into the paty model (PARTY_TYPE_CD)

Hi Manideep,
Nicely articulated . One of the best article which i had come across so far ..
Thanks,
Ram..

hI MANDEEP.
you are doing a great job man,
 
thanks&regards
gopikrishna

Can you elaborate with an example the pre/post cases data redundancy and how it was avoided with the new data model?

Would you consider providing a similar explanation for the ASSETS area?

Hello,

I am new to Siebel and need the complete data model for Siebel UCM. Can someone please direct me to any resources?

Thanks,
John

Sir, i have doubt in S_ORG_EXT and S_BU..If we r storing a Division then the flag in the S_ORG_EXT will be “Y”,if it “N” it may be a organisation or an Account,how we will distingush wether it is an Organisation or Account.I know there is S_BU flag but for account and org its showing “Y”.So pls help me to clear it

Thanks a lot Mandeep…This article clears out a lot of doubts….

Cheers!!!

Suansh

HI Mandeep,

thsi is a good post, PARTY_TYPE_CD column denotes the party type, can you please eloborate this?

Thx
Kishore

Hi Mandeep,
This is very informative and understandable. Keep sharing more topics..

Regards,
Mani

Mandeep Dear,
I was strugling like any thing to understand Party concept by the help of Book shelf and all but some how I was not understanding. After going through your update, Now its clear to me. You are just great. Please keep posting this kind of thing.

Regards,
Anuj Mishra

You are simply GREAT!!! God bless the people like you… My sincere thanks to you for sharing your knowledge… May I would get a chance or not but my blessings would definately with you for your success… Thanks again…

Hi Santosh,
Please ask questions in ask question page so that only comments related to the post can be answered in this page.

Hi Mandeep,

U are doing a very good job by sharing your knowledge and educating people like me.

I am a beginner in SIEBEL and I’m finding difficulty in identifying the Parent key and foreign key when I’m configuring any join or any link.Can u please explain my doubt.

Thank you and Regards,
Santosh

Hello Ashay,

1) S_EMPLOYEE_ATT : This table was used to stored additional detail information regarding employee
.

2) I am not sure about this, but will update you soon on this.

3) In siebel 7 their was not much major in business layer but the data layer was changed to a major extent. In siebel 7.x they introduced administrative consoles were you can easily provide access to the various views and responsibilities etc. But in siebel 6.x there was not any such concept. The other major change was in siebel 6.x these S_view , s_resp etc these tables exists but they were having the explicit joins and in siebel 7.x they have implicit joins.
The data redundancy was removed with these implicit joins having 1:M relationship among the parent and child entities.

Thanks
Mandeep Singh Grewal