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

Unexpected display of view after using Columns Displayed with list applet [ID 1203723.1]

Symptoms
When using the standard Columns Displayed menu item to add a new column to a list applet, on saving the view was redisplayed incorrectly with just a grey page and to redisplay the view correctly the user has to navigate away to a different screen and then return to the view.
Changes
This was a custom view.
Cause
It has been found that the unexpected behavior was related to the name of the view that the list applet is displayed. The name of the view contained a long hyphen character. When the long hyphen character was removed from the view name the unexpected behavior was resolved.
Solution
It is recommended that you should not use a long hyphen character (or any other "special" ascii characters) in the name of any of your custom views.Please see the following bookshelf reference:Configuring Siebel Business Applications > Overview of Configuring Siebel Applications > About Configuring Siebel Applications > Guidelines for Naming ObjectsIn general when naming the views it is advised to use similar naming convention to the standard objects including alpha-numeric characters and a limited number of other characters such as space, open and close brackets, underscore and the regular hyphen character.Using other characters such as accented characters and other symbol characters could cause unexpected behavior.

Day of Week in SQL

select datepart (dw, '5/11/7') as dayOfTheWeek, datename (dw, '5/11/7') as NameOfDay

/*dayOfTheWeek NameOfDay ------------ ------------------------------
6 Friday*/