Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Life Sciences Guide > Importing Data into Life Sciences > Importing, Extracting, and Routing Syndicated Data > About Summary RecordsSales forces are frequently hierarchically organized, with a sales representative being the lowest level of the hierarchy, rising through various managerial levels. It is possible that someone at the start of the hierarchy needs to see all of the syndicated data in the system. This might be practical if the particular user is connected to the database. However, if the managerial levels are remote users, they will have visibility on a very large number of records; their synchronization times will be extremely long. A solution to this problem is to store summary records in the S_SYND_DATA table. Summary records are totals of the sales data for territory, region, division, and other groupings, stored with a type flag in an extension column that indicates the level of summarization is being stored. The summary records can be created by SQL scripts or with a database package such as Microsoft Access. They can be loaded using the two methods described in the previous topics. In addition to loading summary records, you also must configure the table in the Siebel runtime repository, to make sure that a manager-level user sees only summary records, rather than detail records, on the sales data views. Using this technique, you can also implement drill-down functionality for connected managers so that they can start at high level data and work down. |
![]() ![]() |
Siebel Life Sciences Guide | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |