Oracle Synchronize Territory Assignment Rules In The Nineties

Mapping Set Components: How They Work Together

Assignment mapping sets and their underlying mappings drive territory-based assignment. This topic explains how these components work together in assignment processing.

The mapping sets determine which mappings are used and their sequence of use in territory-based assignment. Mapping sets allow different groups of attributes or dimensions to be used when matching territories.


Mappings

The mappings identify the dimensions, attributes, and territory filtering used in the assignment processing. Default mapping sets and their related mappings are predefined for account, leads, partner accounts, and opportunity revenue assignment. This predefined mapping assumes that opportunities, leads, sales, and partner accounts use the same territory hierarchy.

Each predefined mapping set has between 9 and 16 mappings that determine the information on the object, such as the account industry or the sales lead product, and how each is mapped to a dimension or attribute on the territory.

You can create additional mappings using the work objects, candidate objects, and attributes that you already established.

Mapping Sets

Mapping sets enable the grouping of mappings so that you can create more than one mapping for each combination of work object and candidate object. The mapping set concept is used only with territory-based assignment and territory-based assignment with rule filtering. Mappings sets are predefined for accounts, leads, opportunities, and partner accounts. When managing assignment objects, the user can define additional mapping sets, each of which is comprised of multiple mappings, for each combination or work object and candidate object.

Mapping Types

There are three types of assignment mapping:

Dimension Mapping: Dimension mappings should be used when the work object and candidate object attributes in the comparison are dimension attributes, such as Geography, Product, or Account. When creating the mapping, use the Function Code field to specify a unique identifier for the dimension. This identifier is passed to the translation function, in case the same function is used for multiple dimensions.

When creating the mapping, the Function Service and Function Code are only needed if a translations function is used. The function code field is used to specify a unique identifier for the attribute, and this identifier is passed to the translation function.

An example is assigning territories to opportunity revenue lines based on the product associated with the revenue line. In this case, dimension is selected as the mapping type. The candidate object low attribute and high attribute correspond to the names of the low sequence and high sequence attributes for product on the territory. The work object low attribute and high attribute correspond to the names of the low sequence and high sequence attributes for product on the revenue line.

Attribute Mapping: This mapping enables you to compare and match attribute values between a work object attribute and a candidate object attribute. When the value of the candidate object attribute matches the work object attribute, the candidate is selected. Attribute mappings should be used when the work object and candidate object attributes in the comparison are non-dimensional attributes.

For example, consider a lead work object with a Partner Identifier attribute and the territory object with Partner ID attribute. The selection criterion is: . The assignment engine will use this mapping data to construct a query on the candidate object that is equivalent to the selection criteria.

Literal Mapping: Literal Mapping is used almost exclusively to filter the candidate objects. This form of mapping enables the comparison of candidate attributes against a specific value chosen by the user. The assignment engine will compare the mapped candidate object attribute against the specified literal value. For example, select the Territory Candidate object that has the attribute Coverage Model that equals the value PARTNER_CENTRIC.

Note

For Literal Mappings, ensure that the value entered corresponds to the Lookup Type Value code, not the meaning.

Assignment Processing Using Mapping Sets and Mappings

When designing your mappings, carefully consider the dimensions and attributes you use in your territory structure and how you want to match these territory candidates to work objects. Also consider the shape of the information used in the territory structure; this may affect the sequence of each mapping. A sequence can be entered for each mapping set which is used to determine the order in which these mapping sets will be used in the territory-based assignment processing. The sequence of the dimension mappings used in territory matching can affect performance. The most selective dimension mapping should be given lowest sequence number. By default, this dimension is the Geography Dimension. By using the lowest sequence number, it is performed earliest in the matching process, which results in the smallest number of territory matches. Mappings that do not have a sequence are used together at the end of the matching process.

Sometimes the mapping set sequence does not matter, for example, there are two predefined opportunity revenue assignment mapping sets. When the first mapping set is used, it finds matching territories based on the information on the opportunity/opportunity account, and the territory information. Then the second mapping set is used which matches territories based on the opportunity/opportunity partner information and the territory information. The order of the mapping sets are interchangeable; regardless of which mapping set is used first, the resulting territories that match will be the same.

In the case of leads, the mapping set sequence is important as the territories matched using the first mapping set may result in a primary partner being added to the lead. This information is significant to the territory matching performed using the second mapping set.

Mapping sets can be made conditional to control whether the mapping set is used or not used during assignment processing. For example, the partner channel manager territory assignment mapping set conditional attribute is set to the value RevenuePartnerId. During the assignment processing of a revenue line, if the Revenue PartnerId attribute for that revenue line contains a value, then this mapping set will be used in territory matching processing.

An indicator in the related Candidates region controls whether to merge the matching assignment candidates identified from processing each set of mappings. This indicator is used to drive the merging of matching candidates when multiple mapping sets are used in assignment processing. If the box is checked, then the candidates are merged. The default is unchecked.

In most implementations, the predefined mapping sets will be sufficient, but mapping sets can offer some flexibility if custom assignment processing is needed.

Creating Assignment Mappings: Examples

For territory-based assignment, you must create work object to candidate object mappings while creating the assignment object. These mappings are used to make candidate assignments. The scenarios in this topic illustrate creating the different mapping types:

  • Attribute mapping

  • Dimension mapping

  • Literal mapping

Creating an Attribute Mapping

You want to assign territories to a sales lead when the territory partner ID is the same as the sales lead partner ID. To create an attribute mapping:

  1. Create the following mapping:

    • Work object - sales lead

    • Candidate object - sales lead territory

  2. Select the territory when the attribute territory partner ID is equal to the sales lead attribute partner ID.

  3. Enter a value for the sequence which determines the order in which the mapping is used when matching territories.

    Note

    Assign the lowest sequence number to the most selective mapping, and the next sequence number to the next most selective mapping.

Creating a Dimension Mapping

You want to assign territories to opportunity revenue lines based on the product associated with the revenue line. To create a dimension mapping:

  1. Select the mapping type Dimension and enter a sequence value, which determines the order in which the mapping is used when matching territories. The most selective dimension mapping should be given the lowest sequence number.

  2. Enter the function and the Service .

  3. Enter the value for the function code.

  4. Select the candidate object Territory, the work object Revenue, and the alternate work object Revenue.

  5. Select the candidate object low and high attributes.

    The candidate object low and high attributes correspond to the names of the low sequence and high sequence attributes for product on the territory. For example, Dimension Sequence Low and Dimension Sequence High respectively.

  6. Select the work object low and high attributes.

    The work object low and high attributes correspond to the names of the attributes for product on the revenue line. For example, Inventory Item ID and Inventory Organization ID respectively.

    When assigning territories to opportunity revenue lines based on the product, a revenue line may be for a product group instead of a product. In this case, the work object alternate low and high attributes can be used. For example, alternate work object low attribute would be set to Product Group.

    If the revenue line does not contain either a product or product group, the low and high default values for the product dimension mapping can be used to match against the product dimension with the value Any. In this example, the default value low would be set to 1 and default value high to 999999999999999.

Creating a Literal Mapping

Literal mappings are a way of filtering the matched territories based on specific values of a territory attribute. You want to find only territories that have an account-centric coverage model assigned to each revenue line. For example, territory coverage model equals SALES_ACCOUNT_CENTRIC. To create this literal mapping:

  1. Select the mapping type Literal and optionally enter a sequence value, which determines the order in which the mapping is used when matching territories.

  2. Select the candidate object Territory.

  3. Select the candidate object attribute that will be used for filtering. For example, Coverage Model.

  4. Select the operator value Equals.

  5. Select the literal value. In our example, only sales account centric territories should be assigned to revenue lines, so the Literal Value entered corresponds to the code value for the coverage model. For example, SALES_ACCOUNT_CENTRIC.

About Setting Up Sales Territories and Assignment

In Oracle Sales Cloud, you assign salespeople to both accounts and individual opportunities. Being assigned to the sales team of an account or opportunity affects you access to information.

While all salespeople in your organization can view basic account information, including customer names, contacts, and addresses, assignment provides additional access:

  • Accounts

    Assignees can share all the details they need to collaborate, including customer interactions, to-do lists, and appointments. Assignees participate in social discussions, share collateral, and collaborate on presentations.

  • Opportunities

    You must be assigned to an opportunity (or be in the management chain for someone who is), to view and update opportunities and their revenue lines, and to submit forecasts.

Salespeople can always assign others manually while editing an account or opportunity. In Oracle Sales Cloud, there are two methods of automatically assigning salespeople:

  • By setting up sales territories

    The primary method for assigning salespeople to both accounts and opportunities is using sales territories. You can set up the sales territory boundaries based on a wide variety of factors, called dimensions. The most common dimensions include geography, products, customer size, customer type, and industry.

    Sales territories take care of assigning both accounts and opportunities. Sales territories also form the basis for forecasting setup described in a later chapter.

    When you assign salespeople using territories, the territories themselves become associated with the account and opportunity. If you later realign your sales territories or there's turnover in your sales organization, then the assignments reflect those changes automatically after you run the assignment process.

    If you implement Outlook or Mobile, then only the accounts that are part of a salesperson's territory are downloaded when synchronizing.

  • By creating assignment rules

    For opportunities, you can assign additional salespeople based on factors that are not covered by territories, such as deal size or product knowledge. This is accomplished by creating rules to supplement territory assignment. For more information about assignment rules, see the Oracle Sales Cloud Implementing Sales guide.

Managers in a salesperson's management hierarchy have automatic visibility to their team's set of accounts and contacts. They don't have to be explicitly assigned to each territory or sales team.

Vision Corp. Use Case

Vision Corp. sells only to one country, the United States, and divides the country into three geographic regions: west, central, and east. Each territory is owned by one salesperson (although you can assign multiple salespeople, if required).

Recently, Vision Corp. introduced a new line of servers, called Green Servers. The company is assigning an additional salesperson in each region to help sell the new servers.

The following figure shows the organization chart:

Whenever a new account or opportunity is created or updated, Vision Corp. has the application automatically check the territories to see who must be assigned. Here's how the assignment works:

  • Based on the state the account is located in, the application assigns the territory of the prime salesperson.

  • When an opportunity includes a line item for any of the company's products, including a green server, the application assigns the prime salesperson's territory to the opportunity.

  • When an opportunity line item includes Green servers, the application assigns the additional salesperson's overlay territory to the opportunity.

The following diagram shows the sales territory setup with the territory owners. Because Vision Corp. is using territories for forecasting as well, it makes sure that the territory hierarchy mirrors the management hierarchy.

Vision Corp. sets up the sales territories from the top down as described in this chapter. The following table lists the key values for the Vision Corp. US territories and the product groups in the sales catalog.

Note the following:

  • The default value Any means that any value matches the territory.

  • Vision Corp. is organizing the 50 states in the US into three geographical regions.

  • The entries in the Product dimension are the product groups in the sales catalog. Selecting a product group includes all the product groups nested within the product group.

  • All territories participate in revenue forecasting except the overlay territories, which aren't prime territories for sales and are designated nonrevenue. The owner of an overlay territory can forecast the same revenue as the owner of a prime territory, but the amount for the nonrevenue territory isn't added to the overall forecast.

Product Sales

Martin Conway

Prime

Any

Any

Revenue and nonrevenue

East

Michael Rhodes

Prime

Arkansas and all the other states in the eastern US

Any

Revenue and nonrevenue

East All Products

Kristen Garrity

Prime

Arkansas and all the other states in the eastern US

Any

Revenue

East Green Server Overlay

Sean Goodkin

Overlay

Arkansas and all the other states in the eastern US

Green Servers

Nonrevenue

Central

Alex Smith

Prime

Illinois and all the other states in the central US

Any

Revenue and nonrevenue

Central All Products

Peter Branch

Prime

Illinois and all the other states in the central US

Any

Revenue

Central Green Server Overlay

Marilyn Richie

Overlay

Illinois and all the other states in the central US

Green Servers

Nonrevenue

West

Mateo Lopez

Prime

Alaska and all the other states in the western US

Any

Revenue and nonrevenue

West All Products

Lisa Jones

Prime

Alaska and all the other states in the western US

Any

Revenue

West Green Server Overlay

Julian Henderson

Overlay

Alaska and all the other states in the western US

Green Servers

Nonrevenue

The application matches territories to accounts and opportunities from the bottom of the hierarchy up. For example:

  • An account in Illinois is assigned the Central territory.

  • An opportunity for the Illinois account with a Green server line item is assigned the Central territory as well as the Central Green Server Overlay territory.

Setup Overview

  1. You configure the application for the types of sales territories you plan to create:

    1. If you are setting up territories based on geography, like Vision Corporation, you must enable the geographical elements you plan to use during territory setup for the countries for which you imported geography reference information. Optionally, you can organize the geography elements into zones.

      See Specifying Geography Elements for Territory Setup in this chapter for details.

    2. You must enable the territory dimensions you plan to use in your territories.

      See Enabling Territory Dimensions for details.

  2. You set up the sales territories themselves. This step involves:

    1. Creating a territory proposal.

      A proposal is a sandbox that permits you to update territories without affecting any existing territory setup, so it becomes useful when you want to readjust your territories in the future.

      If you use the simplified UI to change territories, your changes become active immediately.

      See Creating a Territory Proposal for details.

    2. Create the hierarchy of sales territories in the proposal starting with the top territory and working your way down.

      See Creating the Sales Territory Hierarchy

    3. Activate the proposal.

      See Activating the Territory Proposal.

  3. You set assignment options.

    Assignment behavior is controlled by a set of system profile options. By default, the application does the following:

    • Automatically assigns sales territories to accounts whenever an account is created or updated.

    • Assignment of opportunities is manual: salespeople can either trigger the assignment process while editing an individual opportunity or the opportunities are assigned by the Sales Account Assignment Process which you set up to run periodically.

    Oracle sets manual assignment for opportunities as the default behavior to prevent performance issues for companies with large number of opportunities (100,000 and up).

    If your organization, like Vision Corporation, does not have such a large volume, you can have the application assign the opportunity automatically by setting the profile Assignment Submission at Save Enabled to Yes. A setting of Yes is also recommended for forecasting.

    See Making Opportunity Assignment Automatic for details.

  4. Run the following assignment processes to assign account and opportunities respectively:

    • Request Account Assignments

    • Revenue Territory Territory Based Assignment

    You must run these processes immediately after you activate your territories and then set them to run on a regular basis, perhaps once a day in off-peak periods, to handle ongoing assignments. Just how frequently you must run these processes depends on your business needs.

    See Running the Account Assignment Process and Running the Opportunity Assignment Process topics for details.

Preparing to Create Territories

Specifying Geography Elements for Territory Setup

This task is required only if you are creating territories with geography as one of the dimensions. For example, if you are creating territories based on states, you must enable the states for selection during territory creation.

In an earlier step, you imported the reference geography for the countries where you do business. Now you must specify which of those geography elements you want to use in your sales territories. Vision Corp. is creating territories by states, so it enables states.

Optionally, you can organize the geographies into zones to simplify territory creation. Vision Corp., in this use case, imported just one country, the US, and plans just three geographical territories: West, Central, and East.

Vision has two options:

  • To enable states only

    Each territory requires the entry of the states it covers. For example, you must enter all the western states in the West territory, the central states in the Central territory, and so on.

  • To enable the states and create zones to organize them

    If you organize the states in zones, you can then select the zone in each territory rather than entering the individual states. For example, if you create a West zone and add all the western states, then you can select the West zone for the West territory instead of the individual states.

Vision Corp. foregoes zones and enables states only. When building the territory hierarchy, you copy the existing territories and modify them. The individual states you entered are copied as well.

To specify which geography elements you want to use for sales territories:

  1. While signed in as a setup user, open the Manage Territory Geographies task from the implementation project. Alternatively, sales administrators and setup users can search for the task by name in the Setup and Maintenance work area.

    The Manage Territory Geographies page appears.

  2. In the Zones Hierarchies region, select Add Geography from the Actions menu.

    The Add Geography page appears.

  3. From the Country list, select Search.

  4. In the Search and Select Country window, search for the country, select it, and click OK.

  5. Click Search. The geographies belonging to the country appear in the Add Geography page.

  6. Select the country and click Submit.

  7. In the confirmation box, select Add geography and include selected children.

  8. Select the geography elements you want to use in territories. For Vision Corp., this is State.

  9. Click OK.

  10. Click OK again in the batch process confirmation box.

  11. Click OK.

Enabling Sales Territory Dimensions

You must enable the territory dimensions that you will use to create your sales territories.

Make sure you have all the source data available before you start. Vision Corporation plans to enable the Product and Geography dimensions, so it has completed the sales catalog and territory geography setup.

To enable the territory dimensions:

  1. While signed in as a setup user, open the task Enable Dimensions and Metrics from the implementation project.

    Alternatively, you can use the following steps to open the same task:

    1. Click the Territories link under the Sales heading in the Navigator.

      The Territories page appears.

    2. Click More Details. This is the button with two arrows at the top right-hand corner of the page.

    3. Click the Enable Dimensions and Metrics task link on the left side of the page.

    The Enable Dimensions and Metrics page appears.

  2. Click Edit.

    The Edit: Enable Dimensions and Metrics page appears.

  3. In the Dimensions table, click Select and Add.

    The Select and Add: Dimensions window appears.

  4. Select the dimensions that you want to use and click OK. Vision Corporation adds Geography and Product.

  5. From the Actions menu, select Load and Activate.

When the process completes successfully, you can start defining territories in the application.

For more information about enabling dimensions, see the Define Territory Management Configuration chapter in the Oracle Sales Cloud Implementing Sales guide.

Creating the Sales Territory Hierarchy

Creating a Territory Proposal

Use this procedure to create a territory proposal. A territory proposal is the sandbox where you create the sales territory hierarchy.

  1. While signed in as a setup user, open the task Manage Territory Proposals from the implementation project.

    Alternatively, click the Territories link under the Sales heading in the Navigator:

    The Territories page appears.

  2. Click the Manage Territory Proposals task link on the left side of the page.

    The Manage Territory Proposals page appears.

  3. In the Current Territory Proposals region, click Create (the plus sign icon).

    The Create Territory Proposal window appears.

  4. Enter a name for the proposal.

  5. Leave the Activation Date field blank. This will cause the proposal to be activated immediately after you build your territories.

    Note: Entering a future activation date requires you to run the Run Territory Proposal Activation process. See the Implementing Sales guide for more details.

  6. Click Save and View.

Your territory proposal opens and you can start building your territory hierarchy.

Creating the Sales Territory Hierarchy

With your territory proposal open, create the sales territory hierarchy starting with the top territory in the hierarchy. For each territory you create, you enter the name of the salesperson or manager who owns the territory and the values for the dimensions that form the territory boundaries. When you create the territories, the application automatically copies all the dimension values from the parent territories to the child territories to speed up entry.

Creating the Top of the Hierarchy

  1. In the Territories region of your territory proposal, click Create.

    The Create Territory page appears.

  2. Enter the territory name, for example, .

  3. Select an owner for the top territory, most likely the VP of Sales:

    1. From the Owner list, select Search

    2. Search for the resource name using any of the criteria.

    3. Select the name and click OK.

    The owner appears on the Territory Team tab. You can add additional members to the team, and the owner himself can add members later.

  4. From the territory Type list, select Prime.

  5. From the Forecast Participation list, select Revenue and nonrevenue. This setting enables the territory to be used for forecasting.

  6. Click Save and Close.

    Your new territory appears in the Territories table of your proposal.

  7. Click the Coverages tab in the Details region at the bottom of the page.

    Note: If the Coverages tab is blank, then your territory configuration is incomplete. Navigate to Scheduled Processes and check to see whether the Synchronize Stage Environment process completed successfully. See Enabling Territory Dimensions topic for more information.

  8. In the Dimensional Coverage table, click Add.

    The enabled dimensions appear. Every enabled dimension is represented by a column, and each column shows . For the Vision Corp. example, this entry means that sales accounts in any location and for any product are assigned to this territory. This is the setting you want for your top territory.

  9. Click Done.

Adding the Rest of the Hierarchy

  1. In Manage Territory Proposals page, select the name of your proposal.

    The territory proposal opens for editing.

  2. If you are creating a subordinate territory, then:

    1. Select the parent territory.

    2. From the Actions menu, select Create and Update and Create Child.

  3. If you are creating a territory at the same level as an existing territory, then:

    1. Select the territory you want to duplicate.

    2. From the Actions menu, select Duplicate.

    The application creates a new territory and copies all of the existing coverage values.

  4. Enter the territory name.

  5. Select the owner for the territory.

  6. Select the territory type.

  7. Click Save and Close.

  8. Click Edit Coverage.

  9. Select the members for each dimension that you want to change.

    For details, see Defining the Territory Coverage in this chapter.

  10. If you must make changes to an existing territory that was not added to the proposal, then select it and click Add to Proposal and make your changes.

  11. Click Save and Close.

Defining the Territory Coverage

Perform the following steps to change the territory coverage of a territory. Any new territory defaults to the coverage of the parent territory.

  1. In Manage Territory Proposals page, select the name of your proposal.

    The proposal opens for viewing.

  2. In the Territories table, select the territory you want to change.

  3. Click Edit Coverage.

    The Edit Coverage window appears.

  4. For every dimension you want to change:

    1. Select the dimension from the Dimensions list.

    2. Add or remove dimension members from the Selected Dimension Members box.

      For example, to specify the states in Vision Corp.'s West territory, you would move the following states to the Selected Dimension Members box:

      • Alaska

      • Arizona

      • California

      • Colorado

      • Idaho

      • Montana

      • Nevada

      • New Mexico

      • Oregon

      • Utah

      • Washington

      • Wyoming

      Tip: If the Product dimension does not show the correct list of products from the sales catalog, then navigate to the Scheduled Processes work area and run the Refresh Denormalized Product Catalog Table for BI process. The wrong products can show up in rare cases where you have changed the root of your sales catalog.

    3. Click Save and Close.

Activating the Territory Proposal

When you have completed building your territory hierarchy, use this procedure to activate the territory proposal and start using the new territories for assignment.

Activating the Territory Proposal

  1. Sign in as a setup user or sales administrator.

  2. Navigate to the Territories work area.

  3. In the Tasks region, click Manage Territory Proposals.

    The Manage Territory Proposals page appears.

  4. If the proposal you want to activate doesn't appear in the Current Territory Proposals table, select All Proposals from the Proposals list.

  5. Select the proposal and click Activate.

    The application displays the new territories in the View Active Territories page.

Running Assignment Processes

Running the Account Assignments Process

You must run the Request Account Assignments process to assign territories to accounts after you activate a territory proposal. You must also schedule this process to run regularly to ensure that all territories are assigned properly.

Running the Request Account Assignments Process

  1. While signed in as a setup user, click Go to Task for the Request Account Assignments Process task in the implementation project.

  2. If you are not using the implementation project, then do the following:

    1. Navigate to the Scheduled Processes work area.

    2. On the Overview page, click Schedule New Process.

      The Schedule New Process window appears.

    3. Click the down arrow to the right of the Name field and select the Search... link.

      The Search and Select: Name window appears.

    4. Enter in the Name field and click Search.

    5. Select the name below and click OK.

      You are returned to the Schedule New Process window.

    6. Click OK.

    The Process Details page appears.

  3. Make the entries described in the following table to assign all account records.

    Work Object Code

    Candidate Object Code

    Assignment Mode

    Territory

    View Criteria Name

    Note: You can run the assignment process on a subset of records rather than on all records by entering different process parameters. For example, you can run the process only on records that have been updated. See the Scheduling Account Assignment: Explained topic in the Implementing Sales guide on docs.oracle.com for more details.

  4. Set up the process to run on a regular basis, perhaps once a day:

    1. Click Advanced.

    2. Click the Schedule tab.

    3. Select the Using a schedule option.

    4. Select the frequency and start date.

    5. Enter an end date far in the future.

  5. Click Submit.

  6. Unless you specified a schedule, your process runs immediately. You can monitor its progress by searching for the process by name on the Overview page.

Related Topics

Running the Assignment Process for Opportunities

You must run the Revenue Territory Territory Based Assignment process to assign territories to opportunities after you activate a territory proposal. You must also set this process to run regularly to ensure that all territories are assigned properly.

Just how frequently and when to run this process depends on such factors as your opportunity volume and the sales cycle.

Running the Assignment Process

  1. While signed in as a setup user, open the Revenue Territory Territory Based Assignment task from the implementation project.

  2. If you are not using the project, you can do the following

    1. While signed in as a setup user or sales administrator, select Scheduled Processes in the Tools group in the Navigator.

    2. In the Scheduled Processes page, click Schedule New Process.

    3. In the Schedule New Process dialog, select the Name list and then select the Search link.

    4. In the Search and Select dialog, enter the process name , and click Search. You can search by a partial name, but note that the search is case-sensitive.

    5. Select the process name in the results and click OK.

    6. Click OK again if needed to dismiss the dialog.

    The Process Details window appears.

  3. Enter the process parameters listed in the following table:

    View Criteria Name

    Enter .

    View Criteria Bind Values

    You can have the option of assigning territories to those open opportunities created since a certain date or those created for a range of dates:

    • For a specific date, enter where YYYY-MM-DD is the date you started implementing the application. For example, assigns all open opportunities created since January 1, 2014.

    • To use a date range, enter . Note that the From and To values are separated by a comma.

    Note: You can find more information about the process parameters in application help, by searching for the Revenue Territory Territory Based Assignment Process. Or, you can view article Opportunity Assignment Process Parameters (1507365.1) available on support.oracle.com.

  4. To run this process periodically:

    1. Click Advanced.

    2. Select the Schedule tab.

    3. Select the Using a schedule option.

0 thoughts on “Oracle Synchronize Territory Assignment Rules In The Nineties

Leave a Reply

Your email address will not be published. Required fields are marked *