Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Life Sciences Guide > Importing Data into Life Sciences > Extracting Data for Mobile UsersThis task is a step in Process of Importing Data. Once the data is in the database, it needs to be made visible to the users. The data is visible by position and can be viewed on many chart and analysis views in Siebel Life Sciences. This is fine for connected users, but the typical user of such data will be the sales rep or sales manager of a particular territory, who are likely to be remote users, synchronizing with the database using Siebel Remote. Therefore, the data needs to be extracted from the database. The application administrator extracts syndicated data according to data-routing (visibility) rules that the administrator defines. When you do this, a full export-process audit trail is generated through log files. NOTE: Insurance plan data (S_INS_PLAN table) might not be extracted for a specific mobile if syndicated data (S_SYND_DATA table) is loaded to the server at the same time a database extract component is running for the mobile client. In addition, if there is no account associated to the insurance plan data, then insurance data for a specific mobile can not be extracted. The data extraction rule, (dock object MedicalInsPlan, rule # 3) controls how insurance plan data is routed. If an account is associated to an insurance plan record and mobile has visibility over that account, the insurance plan data is successfully extracted. You can run multiple instances of the extraction process on each Siebel Server to maximize hardware capacity. The resulting output files are written in a compressed form and then zipped again to minimize file transfer time. The general steps for data extraction are:
These general steps are detailed in the following procedures. |
![]() ![]() |
Siebel Life Sciences Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |