Territory Assignment known issue in Release 11 (Doc ID 2153423.1)

Last updated on JULY 04, 2016

Applies to:

Oracle Fusion Sales Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Symptoms

 Issue: Territory Assignment Does not match any Territories when the Geo Dimension is used and the top level territory zone/geography is used to assign Accounts, Opportunities, Leads, Partners or Deals.

 

1. The assignment processing fails to find any matching territories
2. Example Error from the Request Account Assignments diagnostic log


The final matching candidates for mapping set Account Territory Assignment were identified. (MOW-225207)
class java.lang.NullPointerException
oracle.apps.crmCommon.salesParties.salesPartiesService.applicationModule.DynamicTerritoryAssigner.createSalesAcctTeams(DynamicTerritoryAssigner.java:824)
oracle.apps.crmCommon.salesParties.salesPartiesService.applicationModule.SalesPartyAMImpl.assignmentDispositionCallback(SalesPartyAMImpl.java:3926)


3. When assignment is run in diagnostic mode the following information appears in the mappings section of the diagnostic log:
Assignment mapping values were translated to sequence values. (MOW-225212)
Function Code=Geo,Translated values=(ANY)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms