Share

Account Data Load

Let us discuss the account load in the Siebel through eim in this article. For loading account data into the Siebel application the perquisite is to load the LOV data for the state should also be loaded before the account entity. So just check for the lov data for state. • Identify which are new records to be loaded and load them. • Identify which records are already there in the database but are inactive thus update them to active records, so that it can be used.Now we start loading the account entity. Note

This is a high level process as we are not going deep into technical aspects of what sql query to write to fetch the data and sql queries for data messaging the data.

 

First of all we will load the account data using the EIM_ACCOUNT table and the base table will be S_PARTY, S_ORG_EXT.

There will be few columns with coulumn name as “%DUNS_NUM%” make sure that you check the size for the duns number and update themcorrect value for all those whose length is less.

E.g In the application the duns_num should be of 9 digits , so I will append zero where ever the duns_num length is less then 9 , thus making the duns number as of 9 digits. I will make sure that there is no record were the duns_num length is less than 9 digits.

Check it for all the columns that you are uploading for the duns_number.

Like the fews columns for your reference are below, but they may vary from the application to application i.e sales, telecommunication, marketing, hospitality etc as there utility varies.

DUN_NUM

X_PREVIOUS_DUNS_NUM

X_DISP_HQ_DUN_NUM

PAR_DUNS_NUM

DOM_ULT_DUNS_NUM

GLBLULT_DUNS_NUM

ETC

 

S_PARTY.PARTY_UID — Data message the column with pulling the correct value from the base table , sample query that most of us can use/using :

update siebel.eim_account c

set party_uid = (select a.party_uid from tbsie.s_party a , tbsie.s_org_ext b

where a.row_id = b.par_row_id

and b.loc = c.loc and b.name = c.name)

where if_row_batch_num = '1001' ;

Now check the eim table for the data completeness and validate the data correctness for the records as it is very crucial task because we should not miss loading even any small data aswells we should load only the correct data. Now load the data to base table running the EIM task. The account is associated to some other child entities aswell so we need to associate account to those entities aswell.We will discuss those entities in next article. Note Next Article on How to load child entities of Account

3 comments on “Account Data Load”

  1. payday loans Reply

    siebeloracle.com is very informative. The article is very professionally written. I enjoy reading this every day.

  2. Akash Reply

    We have uploaded accounts through EIM and later did a DeV to Q migration. After migration the accounts are visible in accounts administration screen but not in accounts functionality used in processes defined. To check we reassigned the account to the position through ‘account team’ in account administration screen and then it was visible. What is wrong and how to rectify it . Please help urgently

  3. Mandeep Grewal Reply

    Hello Akash,

    Please check search specifications for the BC and applet.
    Check if the respective columns are populated with the correct data on the account functionality screen.

    Thanks
    Mandeep Grewal

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!