Share:
Territory and Quota for Administrators » Territory Admin » Territory Programs » Workflow Tab

PREVIOUS  |  NEXT

Workflow Tab


Workflow enables sales operators to efficiently control how quotas are distributed. With SAP Business Workflow, you can configure custom workflows to gain additional flexibility and control over the quota distribution methods and tasks.


Note: Using SAP Business Workflow with Territory and Quota requires valid Workflow licenses. These licenses can be obtained as Stand-Alone, or via the Commissions Intelligent Add-On bundle. 


Notification Toggle

You can temporarily disable all workflow communications from bulk distribution actions from the territory program so that one can update quota values in new programs before initiating communication with the field or develop programs without impacting end users.

Commit List  

Administrators and Managers can specify which workflows will be included in the Commit List tab so that one can quickly view and manage cases related to changes to territories and quotas.

Default Workflows

You can also pick from a set of default workflows for all of the available actions so that one can quickly start using the application without creating custom workflows. All default (non-distribution) workflows expected to have one step which auto-approves the action and performs it.

Custom Email Templates

You can also define custom email templates for notifications of various actions which leverage T&Q data to provide context to users who must perform a task. For example, a notification for an account transfer provides information about which accounts are being added, removed, and so on. A quota distribution email provides information about the new quota value and more.

Ad-Hoc Notification Workflows

Administrators, managers, and sales representative can initiate a basic notification workflow from any action list to notify a specific user or set of users about the proposal. Users can also add comments and or request approvals, and specify a priority. The notification includes links to relevant objects from which the request was generated. Notification Status is available to all users. They can also view the status of ad-hoc workflows.

You must have a general understanding of the requirement to define a Custom Notification Workflow. You can define a custom notification workflow to add custom business logic to the interactions.


Multi-select accounts and launch workflow (account screen)

The Administrator/ Manager can select multiple Accounts and launch the workflow for all. The workflow case must be created for individual actions and acted upon by the respective roles. Also, multiple cases created for each account selection.

Task View and Assignment

You must have a general understanding of the requirement to define a Custom Task Custom Form. Custom forms govern the format and display of task-related properties, actions, and so on and allow users to specify custom visualization by case/activity.

Tasks display details of a case or activity:
  • Status Subway Map: Displays a visual overview of completed and upcoming status based on the workflow definition in context to the business process.
  • Update T&Q Properties: Allows users to update task fields which are tied to T&Q properties and have those changes reflected in the T&Q application. For example, a manager should be able to change an alignment change task that includes effective start and end dates. When the task is completed, those property changes reflect in the scenario in T&Q.
  • Scenario Comparison: Users can determine the impact of a proposed change by visualizing, in line with the task, the appropriate scenario comparison screen for the proposed action. For example, a set of alignment changes might include the territory alignment scenario comparison screen.
  • Appeals: Provides an option to include an action to invoke another workflow at certain workflow stages so that users can invoke an "appeals" workflow that is related to a completed workflow.
  • Reason Codes: Lists Reason codes for the task so users can specify why they are approving/rejecting the task, or making the request in the first place.

Task Assignments

  • Task Team Scope: You must define placeholders for workflow case status so that the same process can apply to any level in a workflow. For example, a quota change request first needs to go to the requestor's immediate manager, then it must be approved by the regional VP, and if the quota change is > 10% it must be approved by finance, and so on. 
  • Task Escalation: You must define workflow status in such a way that the task can be routed to a manager for a variety of reasons: the position is not filled, the participant assigned to the position is on vacation, or if the primary approver has not responded within a certain period of time.

Workflow Audit History

Administrators, Managers, and Sales Representatives can view workflow status changes in the History tab for the related object. This tab provides information about the workflow action, including details about who performed the action, what elements were impacted, and so on.



Related Articles