Siebel Community

Welcome to Siebel Community. In this place you can find all the topics related to Siebel. This place is dedicated to provide information about how to implement Siebel CRM application. Siebel Technical/Functional consultants can get information from basics of Siebel CRM to advanced topics like EAI, EIM, eScripting, Workflows, Assignment Manager, Actuate Reports, Territory Management. This place also included Forums and Blogs to help you further.

Tuesday, January 31, 2012

Guidelines for Using the S_PARTY_PER and S_PARTY_REL Tables

The predefined S_PARTY_PER and S_PARTY_REL intersection tables create a many-to-many relationship between party business components, such as Account and Contact. Which table you use depends on if you must or must not enforce access control.
Use the S_PARTY_PER table to create a many-to-many relationship between two party business components where you must create access control. Records in the S_PARTY_PER table provide data access rights from the parent to the child parties. However, to maintain a good response time with a query that is constrained by visibility, you must minimize the number of rows in the S_PARTY_PER table. Therefore, if you create a many-to-many relationship where you do not require access control, such as if you create a recursive many-to-many relationship between a party business component and itself, then use the S_PARTY_REL table.
For example, use the S_PARTY_PER table to create a relationship between the following members:
Access groups and members
Accounts and contacts
Employees and positions
User lists and users

No comments:

Post a Comment