shivshankar

• Apr 8th, 2005

 

Release 7.x introduces the concept of a party table (S_PARTY), in which all persons and organizational units are held. With the new model, Accounts, Organizations, Internal Divisions, Contacts, Employees, Positions, and Households are all considered parties and can be referenced from the same table, S_PARTY.

Soori

• May 4th, 2005

 

It is a base table for all party entities, now the s-org_ext,s_contact becomes the xtension tables for s_party

raja

• Oct 13th, 2005

 

s_party table is base table for all person and organization related base table. for example s_org_ext is the extension table of s_party. s_contact is the extension table of s_party.

chary

 Profile Answers by chary Questions by chary

• Oct 28th, 2005

 

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.

PraveenBallani

 Profile Answers by PraveenBallani Questions by PraveenBallani

• Jun 12th, 2008

 

S_PARTY concept introduced in the versions after Siebel 6. The main use of S_PARTY is to increase the performance and reduce the redundancy of the data. S_PARTY started with the concept of normalisation which is a RDBMS concept.

S_PARTY will be serving as the master table for all the person related, organization related, Contact related information. So S_ORG_EXT, S_CONTACT, S_USER etc tables will be the logical extension tables for S_PARTY.

With out the Party concept when we are doing the Visibility setting, we need to perform for all the above mentioned entities. With Party if we build Visibility rules on the party table that will apply to all, so performance will be more.