|Bookshelf Home | Contents | Index | PDF|
You can enter and maintain some values through LOVs, but you must create other values through tables. The advantage of using tables to enter values is that each company can establish a unique hierarchy and define appropriate values for its business processes.
Populating tables in your Siebel application is a consistent process when setting up Regions, Product Lines, and Session templates, which are described in this section. You can update event-related tables from the Administration - Application screen.
Because Siebel Events Management is only one of many parts of your Siebel application that uses the concept of region, you will want to define a regional hierarchy appropriate for your overall business.
Other parts of the Siebel application use region to indicate the investment focus of your salesmen and their coverage regarding your client companies. Therefore, it is important that you select a region hierarchy that is generic enough to describe event regions, coverage regions, and investment product regions in a single table.
For global or multinational companies, you will want to define regional hierarchies that relate to the geographical areas your business serves and in which you conduct events. Application Administrators can manage region hierarchies by navigating to Administration - Locations> Regions. In the Parent Region list, you can define the region, for instance, North America, Asia, and so on. In the Child Region list, you can then define subsets of the Parent Regions. For example, your Child Regions could be the individual countries that are associated with the highlighted record in the Parent Region list.
Alternatively, you many choose to use individual cities that are associated with the highlighted Parent Region. If two levels of region hierarchies are not sufficient for your company's business requirements, the Siebel data model allows a database administrator to create additional levels. You will however, have to configure the user interface to allow users to define this hierarchy.
The following list illustrates how multiple regions and areas within regions can be set up in the Region table. For instance, your financial institution may define geographies in the following major regions and then areas within a region:
If you are a financial services customer, Siebel Events Management uses the Product Line table to store Asset Classes. You will want to add a row to the table for each relevant asset class associated with a product line from the Product Line Fee view of the Administration - Application screen.
Siebel Events Management uses Session Templates to store templates for groups of sessions that are similar. For example, all events that take place in London may follow the same sequence of sessions, including the same start times and end times. In this case, you may want to save a London template that contains the same sequence of sessions, which you can reuse each time you host a London event.
Session templates may be used in more than one region, area, or location. You can manage session templates by navigating to the Administration- Application screen and choosing Session Template Administration. For more information, see Event Management Process Phases.
Table 5 displays sample line items in a session template. For example, your company may define the following one-day event in London as part of a session template.
After you have created an outline for a London session template, you can add typical sessions that occur during your London-based events. Table 6 displays sample sessions within the London session template.
|Siebel Events Management Guide|