Siebel 7.x – Party Model Changes
by brijeshAfter introduction of party model, the table structure (as far as EIM is concerned) have changed tremendously. The largest data model change involves the Party model, which I think is basis of post siebel 7 releases. Accounts, Organizations, Internal Divisions, Contacts, Employees, Positions, and Households are all party entities and are the logical extension table of S_PARTY and they all have the corresponding entry in S_PARTY base table and the data is brought into the business components through an implicit join (PLEASE NOTE THEY ARE NOT EXPLICIT JOINS).
Some of the major data model changes are also related to this new model. Employees and Contacts have been combined into the same table (S_CONTACT) and similarly, internal and external Organizations have been combined into one table (S_ORG_EXT), in pre 7 releases of siebel employees and internal organizations are stored in S_EMPLOYEE and S_ORG_INT respectively means there tables have gotten obsolete.
The S_PARTY table is the primary table and is the single entity to store all party types – organization units (both external and internal), positions, access groups, user lists, households, contacts, and employees.
So in nutshell following are the new tables or we can say modified functionality tables in siebel:
• S_USER (For siebel Users)
• S_CONTACT (contacts, employees)
• S_ORG_EXT organizations (internal, external)
• S_POSTN (positions)
• S_ORG_GROUP (Households)
• S_PARTY_GROUP (Access Groups: To implement data security one of the major changes)
• S_USERLIST (user lists)
• S_BU (Internal Organizations)
Non-person party entities will have directly or indirectly ralation with employees and contacts.
Data Migration Changes:
All relation based tables have changed in post 7 releases the following tables have gotten obsolete:
| Old Table (pre 7 release) | New Table (post 7 release) |
|---|---|
| S_ORG_REL | S_PARTY_REL (hold relationships between account and party entities) |
| S_CONTACT_REL | S_PARTY_REL (hold relationships between contact and party entities) |
| S_PER_ORG_UNIT | S_PARTY_PER (hold relationships between account and party contact etc. or more generic it stores the ralationship between party and person) |
| S_ORG_INT | S_ORG_EXT (For both internal and external organization.) |
| S_EMP_POSTN | S_PARTY_PER |
| S_EMPLOYEE | S_CONTACT |
| S_POSTN_RPT_REL | S_PARTY_PER |
Related posts:
- Siebel EIM – Custom column mapping It’s a very basic concept explaining how we can generate...
- Siebel EIM Career – A day in Life Consider this article as a simple overview of Siebel EIM....
- Siebel EIM – USING SYNONYMS Performance is always a major issue in most of the...
- Siebel EIM – Custom table mapping This article is similar to my previous article (Siebel EIM...
- Siebel – EAI Queue Okay, what are you thinking about? Is it Middlewares in...
- Siebel – EAI JMS Transport Hi All, After being a mere spectator and a regular...
- Siebel Server Architecture – an Introduction You may call this an introductory tutorial. Siebel as we...