How do I run the Request Revenue Territory Assignment scheduled process?
Use the Request Revenue Territory Assignment scheduled process for territory-based opportunity assignment. This scheduled process evaluates opportunity revenue lines and matches eligible territories and their salespeople to the revenue lines.
When to Use
This scheduled process:
-
Runs territory-based assignment on opportunity product lines. During this process, the application evaluates every product line in the opportunity batch. Territories whose dimensions match the dimensional attributes of a given product line are then assigned to that line.
Privileges Required
Verify that you have the following roles or privileges:
-
Roles:
-
Sales Administrator
-
Setup User
-
Before You Start
Review the following before scheduling this scheduled process:
-
Recommended Frequency
-
See the table containing the view criteria information in the Parameters section.
-
-
Compatibility:
-
This scheduled process is incompatible with itself. These scheduled processes should not be requested to run in parallel against the same opportunity batch, to avoid potential locking issues.
-
High volume opportunities and revenue lines impact the performance.
-
We recommend that you don't run multiple instances of this scheduled process in parallel.
-
Parameters
Parameter |
Optional or Mandatory |
Description |
Parameter Values |
Special Combinations Required |
Notes |
---|---|---|---|---|---|
View Criteria Name |
Mandatory |
Specify a view criteria name from the View Criteria table. |
See the View Criteria table. |
None |
Not applicable |
View Criteria Bind Values |
Optional |
Specify the view criteria bind values of the associated view criteria name from the View Criteria table. |
See the View Criteria table. |
None |
Not applicable |
Number of Work Objects per Sub Process |
Optional |
Specify the number of work objects per sub process. |
Recommend that you use the default values. |
None |
Not applicable |
Maximum Sub Processes per Process |
Optional |
Specify the maximum number of sub processes per process. |
Recommend that you use the default values. |
None |
Not applicable |
Metrics Logging Interval |
Optional |
Specify the metrics for logging interval. |
Recommend that you use the default values. |
None |
Not applicable |
Refresh Forecast Automatically |
Optional |
Specify of the forecast must be refreshed automatically. |
Recommend that you use the default values. |
None |
Not applicable |
Diagnostic Mode |
Optional |
Used only for troubleshooting purposes. |
Not applicable |
None |
Not applicable |
If the view criteria is relevant for your business, use the information in the Recommended Run Frequency column. Typically, most implementations don't use all of the view criteria.
View Criteria Name |
View Criteria Description |
View Criteria Bind Values |
Recommended Run Frequency |
---|---|---|---|
|
Revenue lines of open opportunities created in the last 90 days. Note that the view criteria bind values aren't required for the default date range, 90 days. You can pass a different date range by entering View Criteria Bind Values. |
|
Daily |
|
Revenue lines of open opportunities that have an expected close date in the last 90 days. Optionally, you can enter a different date range. |
|
Daily |
SalesAccountUpdated InLastNDays |
Revenue lines of all open opportunities whose sales account was updated in the last 30 days. Optionally, you can enter a different number of days. |
|
Daily |
SalesAccountUpdatedInLastNHours |
Revenue lines of all open opportunities whose sales account was updated in the last number of hours. Optionally, you can enter a different number of hours. |
|
Multiple times per day |
OpenOpportunitiesUpdatedInLastNHours |
Revenue lines of all open opportunities updated within the last four hours. Optionally, you can enter a different number of hours. |
|
Multiple times per day |
|
Revenue lines of all open opportunities updated in the last 30 days. Optionally, you can enter a different number of days. |
|
Daily |
|
Revenue lines of all open opportunities that contain a specific value in the Batch Tag field. |
|
Run on need basis as per business requirements |
|
Revenue lines of all opportunities imported through the given bulk import batch ID. The view criteria bind value, BatchId, is mandatory. |
|
Run on need basis as per business requirements |
|
Revenue lines of closed opportunities created in the last 90 days. Optionally, you can enter a different date range. |
|
Daily |
ClosedOpportunitiesBy EffectiveDate |
Revenue lines of opportunities closed in the last 90 days. Optionally, you can enter a different date range. |
|
Daily |
|
Revenue lines of an opportunity with a specific number. |
|
Run on need basis as per business requirements. Usually run while troubleshooting in diagnostic mode. |
Troubleshooting Information
Use this information to troubleshoot the scheduled process:
-
Warning or errors are displayed and details are captured in the scheduled process.
-
Use the Diagnostic mode for detailed analysis.
-
Use the Batch Assignment Progress Report or the Batch Assignment Error Report to view the details. For more information about these reports, see the Related Topics section.