S_Party Model

Person based BC

S_CONTACT

Organization based BC

Position based BC

S_USER

S_ORG_EXT

S_EMP_PER

S_BU

S_POSTN

The party model organizes entities such as Person, Organization, Position, and
Household. A party always represents a single person or a group that can be translated
into a set of people such as a company or a household. Siebel data access technology
makes use of the Party model. Certain parts of the data model use the Party model to
abstract the difference between people, companies, households and other legal entities.
This covers relationships between your company and people (contacts, employees,
partner employees, users) and other businesses (accounts, divisions, organizations,
partners). The base table for all such access is S_PARTY. Related tables are implicitly
joined as extension tables. The below Table lists the extension tables and their
corresponding EIM interface tables.
S_PARTY Extension Tables and Corresponding EIM Interface Tables
Data Type
Accounts

Extension Table to S_PARTY

EIM Interface Table

S_ORG_EXT

EIM_ACCOUNT

Business Units S_BU

EIM_BU

Contacts

S_CONTACT

EIM_CONTACT

Employees

S_CONTACT

EIM_EMPLOYEE

Households

S_ORG_GROUP

EIM_GROUP

Parties

N/A

EIM_PARTY

Positions

S_POSTN

EIM_POSITION

Users

S_USER

EIM_USER

Because these extension tables are implicitly joined to S_PARTY, they are available
through S_PARTY. Two pre-configured intersection tables (S_PARTY_PER and
S_PARTY_REL) implement M:M relationships between party business components,
such as Account and Contact. Which one you use depends on whether or not you need to
enforce access control.
Use S_PARTY_PER when implementing M:M relationships between two party business
components where you need to define access control. Records in S_PARTY_PER
propagate data access rights from the parent to the child parties. However, it is important
to minimize the number of rows in S_PARTY_PER to maintain good response times in
visibility-constrained queries. Therefore, when implementing M:M relationships where
you do not need to enforce access control, such as when implementing a recursive M:M
relationship between a party business component and itself, use S_PARTY_REL.
For example, use S_PARTY_PER to implement relationships between members:

Access groups and members

Accounts and contacts
Employees and positions
User lists and users

If you need to extend tables in the party model, you need to create an extension table
from S_PARTY. For example, S_CONTACT is an extension table of S_PARTY. Because
S_CONTACT is of type Extension (Siebel), you cannot use it as a base table for an
extension table. You must create an extension table and use S_PARTY as the base table.
To display data from the new extension table, create a Join object (explicit join) to bring
in data from the new extension table to the business component you are using.
On Field Update Set n User Property
This user property allows you to set the value of a field in the business component when
another field is updated.
Parent Object Type: Business Component
Description Instructs the Siebel eAI connector that it should not perform updates on the
field that the integration component field represents.
Syntax The value for On Field Update Invoke consists of three quoted parameters
separated by a comma and a space, as follows:

[FieldToCheck], [FieldToSet], Value

[FieldToSet] is set to [Value] when [FieldToCheck] is updated. If the Value
Parameter is not defined, [FieldToSet] is set to the value of [FieldToCheck].
An expression can optionally be used for the Value parameter. In the following
example, the Done field is set using the expression when the Done Flag field is
updated. Eg:

"Done Flag", "Done", "IIF ([Done Flag] = ""Y"", Today (), """")"