This chapter covers the following topics:
Verify your implementation by performing one or more of the following tasks:
Create a territory for your usage and run the concurrent program.
Create a transaction for your usage.
Verify that the transaction is assigned to the correct resources.
The following profile options are in the profile category Territory Administration. These system profile options are discussed in the preceding chapter.
Territory Alignment Metric Calculation From Date (mm/dd/yyyy)
Territory Alignment Metric Calculation To Date (mm/dd/yyyy)
The From and To dates specify the time period for information to be calculated by concurrent programs for metric calculation used by territory alignment.
Self Service Named Account Proxy User Role
When the role specified in this profile option is assigned to a user, that user becomes a proxy user and is able to view and manage self-service geographic and named account territories controlled by the manager of the sales group for whom the user is a proxy user.
The following are the prerequisites for Web ADI:
Client PC with Windows ME, Windows NT 4.0 (with Service Pack 3 or later), Windows 2000, Windows XP, or Windows 98 installed on it
Internet Explorer 5.0 or greater installed on the client PC
Microsoft Excel 97, 2000, 2003, or XP installed on the client PC. For Web ADI to work with Microsoft Excel XP/2003, you must change the macro settings for Excel XP/2003. To do so:
In Excel, go to Tools > Macro > Security > Trusted Sources.
Select the "Trust access to Visual Basic Project" option.
To allow spreadsheets to be created on your desktop, change your intranet browser security settings as follows:
Navigate to Tools > Internet Options > Security > Custom Level.
Set the "Initialize and script ActiveX controls not marked as safe" option to "Prompt".
Note: Web ADI is not certified on Mac operating system with Safari browser.
Refer to the Web ADI documentation for more information.
To export using Web ADI
Navigate to Tools > Internet Options > Security > Trusted Sites > Sites
Click the Add button to add the server name to the list of trusted sites
Deselect the Require Server verification (https) for all the sites in this zone check box.
Please refer to the Oracle Web Applications Desktop Integrator User Guide for more information when you troubleshoot your export to Excel. For the very latest updates to troubleshooting information for Web ADI, refer to related links in the release notes for Oracle Territory Manager. Following are some troubleshooting notes:
If images are not displaying properly in the Web ADI page flow, then check the following profile options :
BNE UIX Base Path: Default value is "/OA_HTML/cabo"
BNE UIX Physical Directory: This should be set to the physical directory that is mapped to the value being used for BNE UIX Base Path. The default is derived by looking up the Java system variable OA_HTML in jserv.properties. If OA_HTML cannot be found, then a search is done for MEDIA_DIRECTORY. Once the path of either of these is found, it is appended with "/cabo/".
If you are getting an "Unexpected error" during download, then make sure that the log file has the write permission. The log file name and directory are specified by the following profile options:
BNE Server Log Filename: default value bne.log
BNE ServerLog Path: default is $FND_TOP/log
Oracle Web ADI provides a diagnostic tool named BNETEST to confirm the configuration of Web ADI. To run this tool, download the patch for the diagnostic tool that matches the version of Web ADI you have installed and enter the following URL:
When you merge parties in Oracle Trading Community Architecture, it affects territories in the following ways:
Named party merged into named party
The merge-from named account and the associated sales team are deleted if they belong to the same territory. If the merge-from named account belongs to a separate territory, then the merge-from named account is deleted but the associated sales team becomes part of the merge-to named account, and the merge-to named account now belongs to all of the separate territories.
Non-named party merged into named party
The merge-from party is deleted with no impact on territories.
Named party merged into non-named party
The non-named party replaces the merge-from named party in the existing territory, and the territory and the sales team of the merge-from named party is retained.
If the party or party site records are identified as duplicates, then the territory definition values that are based on parties are transferred.
If both the merge-from party site and the merge-to party site are named accounts in Oracle Territory Manager, then:
If both the named accounts belong to the same parent territory, then the merge-from named account and the associated sales team are deleted.
If the named accounts belong to different parent territories, then the merge-to named account is added to the parent territory of the merge-from named account with the sales team of the merge-from named account. The merge-from named account is then deleted.
If the merge-from party site was set up as a named account in Oracle Territory Manager and the merge-to party site was not a named account in Oracle Territory Manager, then:
If the merge-from named account belongs to a territory whose matching rule is either DUNS or REGISTRY ID, then:
If the party of the merge-to party site already exists as a named account in the territory, then the merge-from named account and the associated sales team are deleted.
If the party of the merge-to party site does not exist as a named account in the territory, then the merge-to party site will replace the merge-from party site as a named account.
If the merge-from named account belongs to a territory whose matching rule is neither DUNS nor REGISTRY ID, then the merge-to party site replaces the merge-from party site as a named account.
Avoid using "<>" operator.
The following tips can be useful.
Set up territories in hierarchical fashion for easy maintenance.
Make the territories as generic as possible.
If you create a territory and do not assign resources to it, then the Territory Manager does not return this territory as a winning territory.
You can create your own module specific "Catch All."
If you run the Synchronize Territory Assignment Rules concurrent program and it errors out, run it again with the Debug and Trace flags set to Yes. Then review the log file that results. The log file gives clear information on exactly what step the error occurred at in the program and what the error is.
The following are frequently asked questions about transaction matching attributes. Answers to these questions may help you in troubleshooting problems with Territory Manager.
Answer: In the Define Matching Attributes step, you must enter at least three letters in order to bring up the LOV in the Value From and Value To fields. For example, enter "Bus" to launch the LOV starting with "Bus". If wildcard "%" is used, then use it with letters, such as "B%%", or "%%%" to query the list of values.
Answer: Customer Name Range is used to group similar customer names. It allows you to define access based on pre-defined customer names.
Service Request: This transaction type allows you to define access for account and service request related transaction qualifiers. It limits the transaction access to a service request only.
For example, a territory is defined with appropriate rank information and has Service Request transaction type identified. That territory can be a winning territory among other competitive territories only if it is for a service request transaction, but not a task or a task associated with a service request transaction.
Task: This type allows you to define access for account and task related transaction qualifiers. It limits the transaction access to a task only, not a task created within a service request.
Service Request and Task: This type allows you to define access for account, task and service request related transaction qualifiers. However, it limits the transaction access to a task associated with a service request only, not a task or a service request.
For example, a territory is created with "Service Request" and "Task" transaction types. When a transaction is lunched through a task within a service request, that territory will not be selected as a winning territory even the qualifier and its value is matched to the transaction (a task associated with a service request).