EIM : Shell execution order

When running an EIM process with a shell type process section, it will be executed from top to bottom. In this example, first process to run will be Assess followed by Contact.

[Siebel Interface Manager]
PROCESS = P1
USER NAME = "XXXX"
PASSWORD = "XXXX"

[Lancar]
TYPE=SHELL
INCLUDE = "ASSESS"
INCLUDE = "CONTACT"

[CONTACT]
TYPE = DELETEBATCH = 3999
TABLE = EIM_CONTACT
ONLY BASE TABLES = S_PARTY,S_CONTACT
DELETE MATCHES = S_CONTACT, (COLUMN= 'DELETED')

[ASSESS]
TYPE = DELETE
BATCH = 3998
TABLE = EIM_ASSESS
ONLY BASE TABLES = S_ASSESS,S_ASSESS_VAL
DELETE MATCHES = S_ASSESS, (COLUMN = 'DELETED')

EIM : DUP_RECORD_EXISTS after Update

This status happens after running an EIM update process with lines that match exactly the lines being updated in base table.

Error 452: Match column X not found in Y

Today I had to create a new column in EIM_CONTACT table, to build a new attribute mapping for deletion purposes. All went fine until I test my EIM task.

Error 452: Match column X_COLUMN not found in S_CONTACT.

I run trough all my steps to find what's wrong in it. All seems to be in perfect shape. My next step was to loose some time reading bookshelf and Siebel support SR's. Nothing came across that helped me to solve my problem.

Last step in problem resolution algorithm, ask for help. Allways work!!

My colleague João had the solution, Siebel caches EIM mappings in \siebsrvr\BIN\diccache.dat, all we have to do is delete this file and Siebel will build a new one for you (with your new mappings).

Finally, I successfully ran my EIM process.