|
Siebel Territory Management Guide > Setting Up and Running Territory Alignments > Process of Setting Up and Running Territory Alignments >
Running Territory Alignments
When you run an alignment, a job is submitted to the Workflow Process Manager. The workflow creates assignment rules and submits a batch job to Assignment Manager. When the Assignment Manager job has finished, the results are presented in the Results view of the Siebel Territory Management screen. No changes are made to the current assignments of accounts, contacts, or assets in the database—these changes do not occur until the alignment becomes active. NOTE: While an alignment is being run, no other alignment in the same hierarchy can be run at the same time.
About the Status Field
The status field is an important indicator about the state of the alignment, from creation of the alignment record through to the rollout of the new assignments in the database. Table 8 lists the possible values for the Status field.
Table 8. Possible Values for the Status Field in the Alignment Record
|
|
|
In Progress |
The alignment record has been created but the alignment has not yet been run. Additional information, such as activation date, rules, and conditions, might have been entered for the alignment record. The alignment remains In Progress until you click the Run Alignment button. |
Creation |
Creating Assignment Rules |
Siebel Territory Management is creating an Assignment Manager rule group and Assignment Manager rules based on the alignment's rules and conditions. |
Running |
Splitting Assignment Tasks |
Load Splitter is splitting the assignment tasks based on the load splitting configuration. For information about configuring the Load Splitter for alignment runs, see Siebel Assignment Manager Administration Guide. |
Running Activation |
Identifying Affected Objects |
The TOS service is searching the database to identify which objects (contacts, accounts, assets, opportunities, or a combination thereof) are affected by the alignment. The purpose is to select only those objects affected and not all object in the database. |
Running Activation |
Request Submitted |
The request for alignment has been successfully submitted to Assignment Manager. |
Running |
Run Completed |
The Assignment Manger run has been successfully completed. When an alignment is run, this value is the final status. (You need to monitor the Server Management Administration screen, Tasks view to see when the Assignment Manager job is complete.) |
|
Moving Territory Rules |
The rules defined by the alignment are being copied to each of the territories covered by the alignment. During this process, territory rules are compared against the alignment rules and updated accordingly. |
Activation |
Scheduling Assignment Run |
An Assignment Manager job is being scheduled to run on the activation date. |
Activation |
Scheduled |
The scheduling of the Assignment Manager job has completed, and the alignment is scheduled to run. |
Activation |
Update Rules for Production |
The assignment rules are being converted to reflect the production environment. |
Activation |
Active |
The request for alignment activation has been successfully submitted to Assignment Manager. When an alignment is activated, this value is the final status. (You need to monitor the Server Management Administration screen, Tasks view to see when the Assignment Manager job is complete.) |
Activation |
Alignment Run Failed |
The alignment run did not complete successfully. This status can indicate some user-related issue such as:
- No position rules
- Conflicting conditions
- An alignment activation date before territory nodes effective start dates
- No add rules (Every alignment must contain at least one add rule.)
It can also indicate some system-related issues, such as the server component Workflow Process Manager is not enabled. |
Running |
Alignment Activation Failed |
The alignment activation did not complete successfully. This status can indicate some user-related issue such as:
- No position rules
- An alignment activation date before territory nodes effective start dates
It can also indicate some system-related issues, such as the server component group Siebel Territory Management is not enabled. If the status is Alignment Activation Failed, the alignment cannot be rerun or reactivated. You need to copy the alignment, fix the problem, and then run and activate the copied alignment. |
Activation |
Running a Territory Alignment
This task is a step in the Process of Setting Up and Running Territory Alignments. To run a territory alignment
- Review the dates on the territory nodes to make sure that all the territories that you want to assign have active nodes:
- Navigate to the Territory Management screen, then the Hierarchies List view.
- Drill down on the hierarchy record.
- In the Territory Nodes list, review the Effective Start Date and Effective End Date for each territory.
- Navigate to the Siebel Territory Management screen, then the Alignments Administration view.
- Drill down on the desired alignment record.
- Click Run Alignment.
- Refresh the screen to monitor the status as the alignment runs.
For information about status values, see Table 8.
- When the status shown is Request Submitted, from the applet menu, select Go to Server Tasks to view the status of the job submitted to the Assignment Manager.
When the alignment has finished running, you can see the results by navigating to the Siebel Territory Management screen, then the Alignments List, and then Results view.
|
