Siebel Life Sciences Guide > Importing Data into Life Sciences > Importing, Extracting, and Routing Syndicated Data >

Loading Data into the Siebel Life Sciences Database

This task is a step in Process of Analysis.

Before you can view syndicated data in Siebel Business Applications, you must first populate the foreign keys fields in the S_SYND_DATA table. These keys are populated from the sales representative (POSITION_ID), territory (TERR_ID), product group (MARKET_ID), product (PROD_ID), contact (CON_ID), area (AREA_ID), and period (PERIOD_ID) fields. Each of these is a key to a record in another Siebel Business Application table. Therefore, these fields need to be populated with valid row IDs for the corresponding position, territory, product group, product, and period business components.

To load syndicated data, the application must have the row IDs for the foreign key data that is stored in the S_SYND_DATA table. The data files used to load syndicated data are supplied in a format in which any key information is supplied as a textual description. This means that unless EIM is used to load the data, the textual descriptions need to be converted into their Siebel Business Application table row ID equivalents.

Different data types need to be supplied to make a record visible in S_SYND_DATA. The only compulsory foreign key field is the PERIOD_ID. However, there is a unique index on the table that comprises all of the foreign key fields: S_SYND_DATA_U1. Table 23 lists all of the foreign key fields, their foreign key table, and a description of what the field contains for Siebel Life Sciences.

Use a native data loader (recommended method) such as SQL*Loader in Oracle or BCP in SQL Server. For the purposes of example, Oracle is used as the target database, although the technique applies equally to SQL Server. Alternatively, you can use Visual Basic and Com.