Siebel EIM – Custom table mapping
This article is similar to my previous article (Siebel EIM – Custom column mapping). As a feedback to it, associates asked as to how we can actually map an entire custom table itself, rather than only custom columns. Here are the simple steps:
1. In object explorer select “Table” and query for base as well as for corresponding EIM table. For example here I am taking example of CX_ACCOUNT and corresponding EIM table EIM_ACCOUNT. Lock both of them.
Siebel EIM – Custom column mapping
It’s a very basic concept explaining how we can generate EIM mapping for custom columns. You need to follow some steps as mention in the post below.
This topic was a Tutorial Request from one of the associates on GeeksBlogging@dotCOM. The associate had asked as to how do we map the custom columns created in the BC to the EIM tables.
1. In object explorer select “Table” and query for base as well as for corresponding EIM table. For example here I am taking example of S_ORG_EXT and corresponding EIM table EIM_ACCOUNT. Lock both these tables.
Siebel 7.x – Party Model Changes
After 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).