http://it.toolbox.com/blogs/siebel-answers/siebel-eim-mapping-step-by-step-guide -part-1-26075 Siebel EIM Mapping Step By Step Guide 1. Determine the base tables that the data will be mapped to and you must unders tand the data models that the data will be converted into. I am assuming that yo u have already worked out the mapping and data conversion rules so you know what fields from excel file will be mapped to what base tables etc. 2. For each of the Siebel base tables to be populated, make a note of all the co lumns in the base tables that you will be mapping to with your source data. Also make a note of the columns that make up the user key for the table. If you are using Siebel EIM to update existing data in base tables then all that is require d for EIM mapping is the mapping to user key and the columns being updated from source data. However if you are using Siebel EIM to insert new records you also need to also map to the non-system columns on the base tables that have the "Req uired" checkbox flagged and make a note of these. So you have 3 separate notes: a. The required columns of the table (required for EIM inserts) b. The columns mapping data to c. The user key columns of the base table 3. In you need to determine a Siebel EIM table that is appropriate to load the d ata into the base tables, the appropriate Siebel EIM table would be that which h as all the column mappings you need to populate the data. To do this, in the Sie bel Tools Object Explorer go to "Flat Mode" and select "EIM Table Mapping". In t he list of table mappings, query in the "Destination Table" column for the base table you wish to populate make a note of some of the "Parent EIM Interface Tabl e" tables. It is usually obvious which table(s) to use (i.e. EIM_ACTIVITY would map to S_EVT_ACT, but you would use EIM_ACTIVITY1/EIM_ACTIVITY2 etc for mapping to activity related tables etc.). When you have found the Parent EIM Interface T able, go to the "Types" view in the object explorer and select "EIM Interface Ta ble" query for the table, drill into the table to the "EIM Table Mapping" and se lect the base table being mapped to then drill in to "Attribute Mapping" to veri fy that all the base columns you want to populate are there. 4. Lookup through Attribute Mapping in the "Base Table Attribute Column" field e ach of the columns being mapped to and make a note of what the corresponding int erface table column is to populate with that field value. Do this for all the co lumns you wish to map to. It is good practice to maintain a mapping spreadsheet document to map fields from source data to interface table columns and Siebel ba se table columns. 5. In the same way as above lookup the required base table columns that you made a note of as these will need to be populated for the Siebel EIM insert/update o peration to be successful. As part of this you need to determine what the value of the base table column that is required should be. Most of the time these are flag fields as part of the vanilla Siebel table in which you just need to ensure that you populate which that default value. 6. In the same way as the above step lookup the user key columns that you made a note of. You need to ensure that these columns are correctly populated with the unique identifier for each record that you wish to insert. Most of the time the user key will consist of the Name/LOC/BU, for example if for populating S_ORG_E XT, the user key is NAME/LOC/BU (not sure exactly what the BU column is called) where the NAME represents the unique name column of the Org, LOC is usually NULL and BU is based on the Organization the record belongs to "Default Organization " would be the value for a single org application. 7. In the Siebel Tools Object Explorer, go to EIM Interface Table > EIM Interfac e Table Column and filter for all records where "Required" = Y. Check if there a re any columns here that have not been included to be mapped in the above mappin gs. If there are you need to ensure that these columns are also populated. Again it is a matter of determining what the column will map to and what the appropri ate value for that column should be. Usually if the column does not mean anythin g to your application functionality specifically you would just map it to the de fault value that all other records in the base table are populated with.
