Bookshelf v8.1/8.2: About Storing Persistent User Profile Attributes

All persistent user profile attributes are stored in the Personalization Profile business component, which has two sets of fields, as shown in Table 6.

Table 6. Persistent User Profile Attributes
Field	Description
Person-related	All person-related fields are based on the S_PARTY table or its extension tables and joins that point to a person's attributes. Examples of such extension tables are S_CONTACT, S_CONTACT_X, and S_USER. The best way to define a new field is to find a similar one in the person-based business components, such as User and Employee, and use it as a prototype.
Organization-related	All organization-related fields start with `Org.` and are based on the S_PARTY table or its extension tables and joins that point to an organization's attributes. Examples of such extension tables are S_ADDR_ORG, S_ORG_EXT, and S_POSTN. The best way to define a new field is to find a similar one in the organization-based business components, such as Account and Internal Division, and use it as an example.

Attribute Components Obsolete in Version 7

Personalization Profile Business Component Used in Version 7

In version 6, these business components are used to store persistent user profile attributes, but in version 7, the Personalization Profile business component is used instead. Any reference to the user profiles in those business components have to be modified.

Basic information such as name and email address should be stored as persistent attributes. Your business needs will determine what other attributes are important to store from one session to another. In general, the most frequently used attributes are made part of the persistent profile.

Siebel Personalization Administration Guide		Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.