Importing, Extracting, and Routing Syndicated Data

This task is a step in Process of Importing Data.

The process described here for importing syndicated data takes advantage of the fact that syndicated data is read-only. Because the row ID on the S_SYND_DATA table is never referred to anywhere else in the Siebel data model, it can be populated with dummy values that differ from usual row IDs. The application administrator uses SQL*Loader to populate the ID field with a unique sequential value, a process that allows either full or partial table-level extraction. Using views in the Administration - Syndicated Data screen, you can define complex routing rules for syndicated data.

Note: Routing rules are used by Siebel Remote and Replication Manager to determine what data and transactions are routed to mobile client databases and regional databases. For more information on routing rules, see Siebel Remote and Replication Manager Administration Guide.

The views that require syndicated data import are shown in the table in the topic Views Requiring Syndicated Data Import.

The general steps for loading syndicated data and distributing it to mobile users are:

1. Load the data into the base tables of the Siebel Life Sciencesdatabase.

   If you choose to use EIM to load the data, turn off transaction logging.

2. Extract the data required by mobile users.

3. Transfer the extracted data files to mobile users.