EIM Load order for any new Siebel Application

Siebel Support Web For Complete Siebel Reference

EIM Load order for any new Siebel Application

22 July 2009 491 views 6 Comments

Many get confused with data loading for the new siebel application starting from scratch. Below is the order in which we need to load data for new Siebel application. we should start loading data in follwing sequence to avoid problems

1) Administrative data – LOV’s

2) Responsibilities

3) Views

4) Organization

5) Position

6) Employee

7) Address

8) Account

9) Contacts

10) And now other related entities depending on the dependency of the entity but here also we load all the parent entities or reference entities for any child or referring entity.

6 Comments »

Mayank said:

dear mandeep

This is really a very valuable and a rare information you have given to all of us but I have some queries. First how come Address we migrate before Accounts and Contacts? Second what about Access Group and User entities? Third can’t we migrate Contacts before Accounts for e.g. in Siebel Financial application?

reply is highly appreciated.

# 5 October 2009 at 9:43 am

Javed said:

I think Addresses can be loaded before or after Accounts & Contacts.

As there is intersection table between Accounts – addresses / Contact – addresses. SO , if addresses are loaded before accounts / contacts than this association can be done during the accounts / contacts loads.

I’m not sure if contacts can be loaded before Accounts.

# 8 October 2009 at 10:05 am

Raj said:

I am guessing he meant by core address. In one of our implementation we loaded country and state lov’s as part of intial data load before loading accounts and contacts.

# 3 November 2009 at 11:42 pm

Gaurav Tiwari said:

The Address data gets loaded into S_ADDR_PER table and its association is maintained by S_CON_ADDR.
So when we load address we are loading data in table.After loading accounts/contacts we create relation using S_CON_ADDR.

# 26 November 2009 at 10:21 pm