Day 8-Siebel 7.7 EIM Lab - Draft B

TCS Siebel EIM Lab Exercises
Internal Document
EIM Lab Exercises Draft B
June 2005
Tata Consultancy Services
In Confidence
Page 1 of 6
Table of Contents
IMPORT DATA PROCESS FLOW..................................................................................3 INSTRUCTIONS FOR THE EIM LAB..............................................................................5 ADDITIONAL POINTS:....................................................................................................6
In Confidence
Page 2 of 6
Import Data Process Flow

This section describes the general process flow that you must follow to import data into the Siebel database using EIM. Identify and validate the data to be imported: Determine the data to load and whether it already exists in another database. You should review existing data for completeness. For example, the Siebel database may require both an area code and a telephone number, while your existing database may not. Determine the number of opportunities, contacts, and accounts you plan to import. This information assists you in estimating the time and resources required to import, process, and store your data. NOTE: If the data exists in a database that uses a different character set, the import process does not work properly until you recreate the database. Identify the column mappings and user key columns of the data to be imported: Identify the mapping between the data and Siebel base columns. For information on Siebel base table columns Identify the EIM table columns that map to these base table columns. To view mappings between EIM table columns and base table columns Identify the user key columns and make sure they are populated uniquely. For information on user key columns Make sure that your hardware and software environments are ready. Before you use Siebel EIM tables to import data, the Siebel application must be properly installed. Work with your Siebel representative and MIS personnel to verify that the required hardware and software resources are available. Back up your existing database. Before undertaking any significant change. Such as installing a new application, importing data, or upgrading an installed application. You should first perform a comprehensive backup of your database. This facilitates an easy recovery if problems occur. Copy file attachments to the Siebel server subdirectory named .input. If you want to import file attachments, you can: Copy the files to the input subdirectory under the Siebel server root directory. Stores file attachments in the location specified in the ATTACHMENT DIRECTORY .IFB file header parameter. Siebel EIM tables support all file attachment formats, including common file types such as Word documents (.doc), Excel spreadsheets (.xls), and text files (.txt). For information on file attachment columns. Load and verify the EIM tables. Your database administrator can use a database tool provided with your RDBMS (such as SQL*Loader, Bulk Copy Utility, or dbload) to copy data from your existing database to the Siebel EIM tables. NOTE: Siebel EIM tables contain several special columns that must be populated before rows can be imported.
In Confidence
Page 3 of 6
After the EIM tables are loaded, check the number of loaded rows against your existing database to make sure that the appropriate rows were loaded. Check the contents of several rows to make sure that the tables are ready for the import process. Edit the EIM configuration file (default.ifb). This file customizes the behavior of EIM by defining the data you will import and identifying the batch number to use. For information on editing the EIM configuration file for data import. Test your import process. Run a small test batch (perhaps 100 records) to verify that the EIM tables load correctly, and that the correct parameters are set in the configuration file and on the srvrmgr command line. Run the import process. Although your batch sizes depend on the volume of data you must import, consider using multiple smaller batches (1,000 to 5,000 rows) rather than one large batch. Smaller batches place fewer demands on resources. Also, when using smaller batches, the fixing of problems is simpler. If a batch is not imported correctly, it is easier to isolate the condition, correct it, and rerun the batch. Verify results. EIM provides several diagnostic tools that let you verify the success of import processing
In Confidence
Page 4 of 6
Instructions for the EIM LAB

Study the data mappings provided in the document 'account_data_mapping.xls'. Note that in order to populate a single column (PAR_ROW_ID in the table S_ORG_EXT), we are required to specify two columns in the Interface Table. This is true for all foreign key columns. We provide values that form part of the unique index for the table containing the primary key. EIM then resolves the key and returns an ID field, which gets stored in the target column. The Instructor will be assigning a Batch Number to each of the groups. Open the .SQL file representing your batch number and copy the text. Execute the insert statements that you have just copied. Use the following query to verify if the data has been successfully loaded into the Interface Table (EIM_ACCOUNT in this case): SELECT COUNT (*) FROM SIEBEL.EIM_ACCOUNT WHERE IF_ROW_BATCH_NUM = XXX ; XXX here represents the corresponding batch number. This query should return 4 records.
Navigate to Server Administration -- Enterprise Operations -- Component Requests. Add a new record in the Component Requests List Applet with the following value: Component/Job -- Enterprise Integration Manager Click 'New' in the Component Requests parameters List Applet and set the following parameter: Name -- Configuration file, Value -- batchX.ifb where X is the batch number. Click the menu button in the Component Request form applet and select 'Submit Request' After the run, the status of the task should show 'Completed'. Go to the SQL window and run the following query to check if all the records have been successfully inserted into the target base tables: SELECT COUNT (*) FROM SIEBEL.S_ORG_EXT WHERE NAME like '%Batch-XXX'; XXX being the batch number. This query should return 4 rows if the server task finished successfully. Note that the IF_ROW_STAT column in the Interface Table automatically changes to 'Imported' after the process. The value of this field after the EIM run is most often used for determining the error encountered, if any. Note that the same EIM process has inserted similar number of rows in the table S_PARTY as well. Examine data in the two tables to find out the relationship between them.
In Confidence
Page 5 of 6
Additional Points:
Any combination of ROW_ID and IF_ROW_BATCH_NUM for an Interface Table is unique. The EIM Server Task processes only the Batches specified in the .IFB file. In this Lab, different groups will be using different Batches of data. Each group will be loading the same Target Tables but will work independent of each other due to different batch numbers. Please perform all update/delete in the Interface Table without affecting other batches. Please take care to use 'where IF_ROW_BATCH_NUM = your_batch_num' while doing any such operations.
In Confidence
Page 6 of 6

Day 8-Siebel 7.7 EIM Lab - Draft B

Uploaded by

Copyright:

Available Formats

Day 8-Siebel 7.7 EIM Lab - Draft B

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Day 8-Siebel 7.7 EIM Lab - Draft B

Uploaded by

Copyright:

Available Formats

TCS Siebel EIM Lab Exercises

EIM Lab Exercises Draft B

Tata Consultancy Services

TCS Siebel EIM Lab Exercises

Tata Consultancy Services

TCS Siebel EIM Lab Exercises

Import Data Process Flow

Tata Consultancy Services

TCS Siebel EIM Lab Exercises

Tata Consultancy Services

TCS Siebel EIM Lab Exercises

Instructions for the EIM LAB

Tata Consultancy Services

TCS Siebel EIM Lab Exercises

Tata Consultancy Services

You might also like