Request Opportunity Resource Assignment

Use the Request Opportunity Resource Assignment scheduled process to run rule-based assignment on opportunities. During this process, assignment processing executes a set of rules, as defined in the profile option, Sales Team Member Assignment Rule Set Group, to find matching candidates for opportunities.

If matching candidates are found, they're added to the opportunity team. Note that team members for whom lock assignment is disabled will be replaced if they no longer match the assignment rules.

When to Use

This scheduled process:

• Assigns sales resources to an opportunity based on a set of rules such as assigning sales team members, including the opportunity owner.

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.	We recommend that you use the default value.	None	Not applicable
Maximum Sub Processes per Process	Optional	Specify the maximum number of sub processes per process.	We recommend that you use the default value.	None	Not applicable
Metrics Logging Interval	Optional	Specify the metrics for logging interval.	We recommend that you use the default value.	None	Not applicable
Refresh Forecast Automatically	Optional	Specify if the forecast must be refreshed automatically.	We recommend that you use the default value.	None	Not applicable
Diagnostic Mode	Optional	Used for troubleshooting purposes.	Not applicable	Not applicable	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
OpenOpportunitiesUpdated InLastNDays	All open opportunities which were updated in the last 30 days. Optionally, the user can enter a different number of days.	BindOptyUpdatedSince=[30] For example, opportunities updated in last 15 days: BindOptyUpdatedSince=15	Daily
OpenOpportunitiesUpdatedInLastNHours	All open opportunities which were updated in the last number of hours. Optionally, the user can enter a different number of days.	BindOptyUpdatedWithinHours=[4] For example, opportunities updated within the last 6 hours: BindOptyUpdatedWithin=6	Multiple times per day
OpportunityForImport BatchVO	All opportunities imported through the given bulk import batch ID. Value for BatchId is mandatory.	BindBatchId For example: BindBatchId=5618782	Run on need basis as per business requirements
OpenOpportunities ByCreationDate	Open Opportunities created in the last 90 days. Optionally, the user can pass a different date range.	BindOptyCreationDateTo =[date], BindOptyCreation DateFrom =[date] For example: BindOptyCreation DateTo=2015-02-29, BindOptyCreation DateFrom=2015-01-01 or BindOptyCreation DateFrom=2015-01-01. This second example processes all open Opportunities created between January 1, 2015 and the current date.	Daily
OpenOpportunities ByEffectiveDate	Open opportunities that have an expected close date in the last 90 days. Optionally, the user can pass a different date range.	BindEffective DateFrom [sysdate], BindEffective DateTo[sysdate [90] For example: BindEffective DateFrom=2015-01-01, BindEffective DateTo=2015-02-29	Daily
SalesAccountUpdated InLastNDays	All open opportunities whose sales account got updated in the last 30 days. Optionally, the user can pass a different number of days.	BindSalesAccountUpdated Since [30] For example, opportunities whose sales account was updated in last 15 days: BindSalesAccount UpdatedSince=15	Daily
ClosedOpportunities ByCreationDate	Closed opportunities created in the last 90 days. Optionally, the user can pass a different date range.	BindOptyCreation DateTo [date], BindOptyCreation DateFrom [date-90] For example: BindEffective DateFrom=2015-01-01, BindEffective DateTo=2015-02-29	Daily
ClosedOpportunitiesBy EffectiveDate	Revenue lines of opportunities closed in the last 90 days. Optionally, the user can enter a different date range.	BindEffectiveDateFrom =[date], BindEffectiveDateTo =[date] For example: BindEffectiveDateFrom =2015-01-01, BindEffectiveDateT o=2015-02-29	Daily
OpportunitySearchbyOptyNumber	The opportunity with a specific number.	BindOpportunityNumber=<number> For example, BindOpportunityNumber=17001	Run on need basis as per business requirements

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 the reports, see the Related Topics section.