Import Contact:
For importing contact in siebel you need to import below siebel tables:
S_CONTACT
S_CONTACT_BU
S_POSTN_CON
S_PARTY
Brief description of above tables:
For importing contact in siebel you need to import below siebel tables:
S_CONTACT
S_CONTACT_BU
S_POSTN_CON
S_PARTY
Brief description of above tables:
- S_CONTACT: This base table stores all the general details related to a contact like Name, Telephone No. etc.
- S_CONTACT_BU: This is an intersection table between S_CONTACT and S_BU which stores the organization of the contact.
- S_POSTN_CON: This is an intersection table between S_CONTACT and S_POSTN. The POSTN_ID of this table specifies which employee can see this contact in his My Contact List. Associating a position to a contact is mandatory, if you do not associate, the contact will not be visible on UI.
- S_PARTY: This is the parent table for S_CONTACT, S_CONTACT being the siebel extension table for S_PARTY. Whenever a new contact is loaded in siebel S_PARTY must have an entry of the contact. You cannot import a contact in siebel without populating this table.
The EIM table that we can use is EIM_CONTACT since this table populates all the above mentioned tables.
Loading Contact:
Step 1: Run the below query, this query will insert the contact details in the eim table.
INSERT INTO EIM_CONTACT
(
ROW_ID,
IF_ROW_STAT,
IF_ROW_BATCH_NUM,
CON_PERSON_UID,
CON_PRIV_FLG,
CON_BU,
CON_ACTIVE_FLG,
CON_COURT_PAY_FLG,
CON_DISACLEANSEFLG,
CON_DISPIMGAUTHFLG,
CON_EMAILSRUPD_FLG,
CON_EMP_FLG,
CON_FST_NAME,
CON_INVSTGTR_FLG,
CON_LAST_NAME,
CON_ONDMNDSYNCFLG,
CON_PO_PAY_FLG,
CON_PROSPECT_FLG,
CON_PTSHPCONTACTFL,
CON_PTSHPKEYCONFLG,
CON_SENDSURVEY_FLG,
CON_SPEAKER_FLG,
CON_SUPPRESSEMAILF,
CON_SUPPRESSFAXFLG,
CON_SUSPECT_FLG,
CON_SUSP_WTCH_FLG,
CON_VETERAN_FLG,
PARTY_UID,
PARTY_TYPE_CD,
ROOT_PARTY_FLG,
ADMIN_ADJ_FLG,
PC_POSTN_BU,
PC_POSTN_DIVN,
PC_POSTN_NAME,
PC_ROW_STATUS,
CB_BU
)
VALUES
(
1,
'FOR_IMPORT',
1,
'EIM_TEST_1',
'N',
'Default Organization',
'Y',
'N',
'N',
'N',
'N',
'N',
'Mohammed',
'N',
'Arif',
'N',
'N',
'N',
'N',
'N',
'N',
'N',
'N',
'N',
'N',
'N',
'N',
'EIM_TEST_1',
'Person',
'N',
'N',
'Default Organization',
'INDIA',
'ACCOUNT_MANAGER-123',
'N',
'Default Organization'
);
COMMIT;
Remember that while importing new contacts, you need to populate all the required columns along with the user key columns of all the 4 base tables mentioned above.
Step 2: Check the inserted records:
select count(1), if_row_stat, if_row_batch_num
from eim_contact where if_row_batch_num = 1
group by if_row_stat, if_row_batch_num;
Step 3: Run EIM job with below IFB configuration parameters:
[Siebel Interface Manager]
PROCESS = Import_Contact
[Import_Contact]
TYPE = IMPORT
BATCH = 1
TABLE = EIM_CONTACT
ONLY BASE TABLES = S_PARTY, S_CONTACT, S_POSTN_CON, S_CONTACT_BU
Provide other necessary parameters like username, password etc. if required.
Step 4: Once the job is successfully completed, Check the IF_ROW_STAT column of the EIM table by running the below query.
select count(1), if_row_stat, if_row_batch_num
from eim_contact where if_row_batch_num = 1
group by if_row_stat, if_row_batch_num;
Step 5: Check imported records from UI.
NOTE: For any kind of errors in running EIM job, check the log file placed at /siebsrv/log/ location on the server. To get appropriate messages in the log file you need to specify below parameters while running the EIM job from UI.
Trace Flags = 3
SQL Trace Flags = 8
Error Flags = 1
No comments:
Post a Comment