Bookshelf v7.5: Assigning Target Lists to a Route

Siebel Consumer Sector Guide > Routes > End-User Procedures >

Assigning Target Lists to a Route

NOTE: The Account Targeting module is designed for end users, such as retail sales representatives, who have local data access and are not continuously connected to a network. For more information, see Account Targeting.

On your local database, you can use account lists created with the Account Targeting feature. After creating and saving a target list, you can optimize the target list by merging (intersecting or combining) it with other target lists. When you have finished merging target lists, you can assign the results to a route in the view that you use to plan your routes. You can also add or delete accounts after assigning the list of accounts to a route.

NOTE: You must create and save a target list using the Account Targeting module before you can merge it with other target lists and assign the results to a route. For information on these procedures, see Creating a Target List and Saving a Target List.

To merge a target list

Navigate to the Routes screen.

In the Routes list, select a route.

Click the Target Accounts view tab.

Click the Target Accounts list to activate it.

A blue line appears around the Target Accounts list.

In the toolbar, click the apply target list button, located in the row of buttons next to the History button.

The Targeting dialog box appears and displays the targeted routes.

Click to select one or more target lists (query name) you want to assign to the route; to deselect a target list, click it again.

If you selected more than one target list, use one of the following methods to merge the lists:

Click the Intersection button to retrieve only those accounts common to all the selected target lists. For example, if List 1 contains A, B, and C, and List 2 contains B, C, and D, the resulting list will contain only B and C, which are common to both target lists.

Click the Union button to retrieve all accounts from all the selected lists. For example, if List 1 contains A and B, and List 2 contains C and D, the resulting list will contain A, B, C, and D, the combination of both target lists.

NOTE: If only one target list is selected, the buttons are ignored.

Click OK.

In the toolbar, click the save target list button, located in the row of buttons next to the history button.

The Targeting dialog box appears with a blank Target Name field.

In the Target Name field, enter a unique name for the target list. Click Save.

The target list is saved. You can merge this list with other target lists to optimize your list of accounts.

Repeat Step 5 through Step 10 until you have optimized your target list. You are now ready to assign the target list to a route.

Caution: If you enter a name already in use, the previously saved target list will be overwritten without warning.

To assign a target list to a route

Navigate to the Routes screen.

In the Routes list, select a route.

Click the Target Accounts view tab.

In the Target Accounts list, merge target lists until you have an optimized list of accounts.

NOTE: For information on merging target lists, see To merge a target list.

In the Target Accounts list, select the accounts that you want to add to a route.

Click the Commit button.

The selected accounts are added to a route and appear in the Accounts list. When you are adding target accounts to an existing route, the target accounts will be added without duplicating accounts. If necessary, you can add or delete accounts from the Accounts list.

Fill in the fields for each account you added.

Some fields in the Target Accounts list are described in Table 42.

Table 42. Fields in the Target Accounts List
Field	Comments
Call Duration	The scheduled duration of the account visit. LOV Type: APPOINTMENT_DURATION
Call Time	The current time is automatically entered in this field. You should edit this field to reflect the time when the account is to be visited.
Offset Day	Allows you to create routes that span more than one day. It indicates the number of days after the beginning of the route that an account should be visited. For instance, if an account is to be visited on the first day of a route, this field should be set to 0. If the account is to be visited on the second day of a route, this field should be set to 1.