Transition to Simplified Geographies

Oracle CX Sales Territory Management

Update 21A
IMPLEMENTATION NOTE | MARCH 2021

Disclaimer

The following is intended to outline our general product direction. It is intended for information purposes only, and
may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing decisions. The development, release, and timing of any
features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
About This Document

This document supplements standard product documentation, which you are encouraged to review. To find
documentation, such as guides, click Help and search for topics.

AUDIENCE

This document is for Oracle Sales customers involved in implementation, and the information applies to
both Oracle Public Cloud and on-premise deployments.
Transition to Simplified Geographies

Table of Contents
What's New – Update 19A: ..................................................................................................................................................... 4
Simplified Geographies ....................................................................................................................................................... 4
New Feature Summary – Update 19A: ................................................................................................................................... 4
Simplified Geographies ....................................................................................................................................................... 4
Steps to Enable................................................................................................................................................................ 4
Transition to Simplified Geographies...................................................................................................................................... 4
Assumptions ........................................................................................................................................................................ 4
Tips and Considerations ...................................................................................................................................................... 5
Geography – Address Coverage, and Address Matching Examples.................................................................................... 5
Transition Guidelines .......................................................................................................................................................... 6
Release Training Information: ................................................................................................................................................. 7
Geo to Address Examples ....................................................................................................................................................... 8
Geo to Address Coverage Mapping Examples .................................................................................................................... 8
Geo to Address Postal Code Matching Examples & Recommendations .......................................................................... 10
Postal Code Recommendations .................................................................................................................................... 10
Geo to Address State and City Matching Examples and Recommendations.................................................................... 14
State & City Recommendations .................................................................................................................................... 14
What's New – Update 19A:
Simplified Geographies
The Simplified Geographies feature dramatically reduces on-boarding time and territory re-alignment overhead for
certain Engagement Cloud territory implementations. This feature allows the implementation to de-couple territory
geography coverage and address assignment from the TCA geographies master data, allowing territory setup to proceed
with fewer prerequisites and dependencies.

New Feature Summary – Update 19A:

Simplified Geographies
Territory management setup can take substantial effort when an Engagement Cloud territory implementation covers
multiple countries and/or the coverage is highly granular, involving postal codes. This feature simplifies the territory
setup effort by introducing a new dimension called Address. The Address dimension simplifies Territory setup by:
1. Removing the dependency on Master Geography data - there is no longer a need to setup TCA geographies as a
pre-requisite. An additional benefit is that it now becomes straight-forward to handle duplicate postal code data
- for example, when a postal code straddles city, county or state boundaries
2. Allowing partial address data to be assigned to territories successfully, and
3. Providing convenient short-cuts to define coverage using postal code patterns or range

Steps to Enable
No steps are required to enable this feature, but a transition is required if currently using the geography dimension.

Transition to Simplified Geographies

The following is a guideline of the steps an implementation should follow to transition Territory Management from the
Geography dimension to the Address dimension.

Assumptions
• Product Development does not have a Geography to Address migration feature
• The customer is currently using the geography dimension
• There are no changes in the territory assignments as a result of the move to simplified geographies
• Territory export and import may be the simplest approach to mass update all territories
• Using Export and Import Management will be a good way to add the Address dimension territory coverage
records to each territory, and once the transition is successful, subsequently remove the Geography
dimension coverage records.
• Import Management may be a useful approach to use, as the customer will be able to add Address territory
coverage records without having to pass the complete territory definition.
• These changes may be done directly on the active territories without using a proposal. Here’s the link to the
Update Territories using Export and Import Management (Doc ID 2612317.1) white paper which has
examples for exporting active territories and importing territory coverage records either using or not using a
proposal.
• If a customer has different operations team members responsible for transitioning territory geography to
address definitions for each country, it may be useful to extend the territory object and introduce a country
field for territories. Once this information is populated on each territory, country can be used within the
Export Management filter criteria to group the export of territories and territory coverage records.
Tips and Considerations
The documentation states “You can't enable both the Address and the Geography dimension.” because customers
should not attempt to use both Geo and Address LONG TERM. Also, customers should not use BOTH Address and Geo in
territory assignment as the performance is significantly impacted.

While a customer is TRANSITIONING from Geo to Address, BOTH dimensions can be enabled by setting the Allow both
Address and Geography Dimensions (MOT_ALLOW_ADDR_AND_GEO) = Y. It is okay to have both enabled for a few
weeks.

BUT there is a caveat: ONLY the Geo OR Address assignment mappings should be enabled for territory assignment
processing for Accounts, Opportunities, Leads, Partners and Deal Registrations (for which ever objects territory
assignment is used). By default, the Address and Geo assignment mappings are ACTIVE, so the administrator will need to
go into the appropriate Manage Assignment Objects setup task e.g. Manage Customer Center Assignment Objects, to
inactive one of the two of mappings.

NOTE:
1. Setting any single Address mapping to Active or Inactive will automatically update all the other Address
mappings in that mapping set to the same. Please see the following screenshot showing the Address mappings
as Inactive and the Geo mapping as Active for the Account Territory mapping set in Manage Customer Center
Assignment Objects.
2. For some objects, e.g. Leads there are a number of mapping sets, so this may need to be repeated for each of
those mapping sets used.

Screenshot: Manage Customer Center Assignment Objects

Geography – Address Matching Examples and Recommendations

See the Geo to Address Examples section for the examples that are useful when transitioning to the Address dimension:
 o Geo to Address Coverage Mappings
o Geo to Address Postal Code Matching and Recommendations
o Geo to Address State and City Matching Examples and Recommendations

Transition Guidelines

PROD ENVIRONMENT:
• Configuration Updates:
o Set the profile option: Allow both Address and Geography Dimensions (MOT_ALLOW_ADDR_AND_GEO) = Y
o Enable Address dimension via Enable Dimensions and Metrics Setup Task
o Set the Assignment address dimension mappings to INACTIVE
▪ For Accounts, Opportunities, Leads, and Partners (and if applicable Deal Registrations)
▪ This means assignment will continue using Geography dimension in addition to any other
dimensions (but not the Address dimension)
o Add appropriate address definitions to all territories
o See the Appendices for examples o……..mappings of the Geography dimension territory coverage examples
to the Address dimension territory coverage examples.
o Validate territory assignments are unaffected by this, due the continued use of the Geography dimension in
assignment
▪ As the assignment mappings are configured to use the Geography dimension in addition to any
other dimensions, but not the Address dimension, the assignment will not be impacted.
o Copy PRODUCTION environment to a TEST environment
o Contact Oracle Support to request

TEST ENVIRONMENT:
• Confirm Configuration:
o Allow both Address and Geography Dimensions
▪ Address dimension is enabled via Enable Dimensions and Metrics Setup Task
o Ensure the Assignment address dimension mappings are INACTIVE
▪ For Accounts, Opportunities, Leads, and Partners (and if applicable Deal Registrations)
▪ This means assignment will continue using Geography dimension in addition to any other
dimensions (but not the Address dimension)
o Run account assignment using Geo dimension
▪ Validate territory assignments are consistent with production
o Enable the Address assignment mappings & disable Geo assignment mapping
▪ For Accounts, Opportunities, Leads, and Partners (and if applicable Deal Registrations)
▪ This means assignment will now use the Address dimension in addition to any other dimensions (but
not the Geography dimension)
o Run account assignment and verify no changes in territory assignments
o Define a BI Publisher report on account territory assignments to validate this (confirming that there are no
accounts with updates to any of the account territory assignments)
▪ This checks the last update date in Sales Account Territory intersection table, however it will not
indicate if any territories have been deleted from the account.
▪ An alternative is to enable audit for the Sales Account Territory object and define a BIP report based
on the audit table, which would indicate any additions, updates or deletes to the sales account
territory.
PROD ENVIRONMENT:
We recommend customers test the territory assignment thoroughly before turning on the Address mappings and
inactivating the Geo mapping for territory assignment in a Production instance. This the key aspect of the Transition
to Simplified Geographies so as not to impact the sales rep access to records.
• When confident that territory definition and the territory assignment results in the Test environment are as
expected:
• Enable the Assignment Address mappings & disable Geo mapping for Accounts, Opportunities,
Leads, and Partners (and if applicable Deal Registrations)
• Run account assignment and verify no changes in territory assignments
• Use a BI report on account territory assignments to validate this
• Disable the Geography dimension via Enable Dimensions and Metrics Setup Task

Release Training Information:

• The Simplified Geographies feature description and overview are available on Customer Connect in the Sales Update
19A New Feature Summary and What’s New sections: https://cloud.oracle.com/en_US/saas/readiness?offering=sales
• For a brief overview and demo, please see the following YouTube video: https://youtu.be/6izZTLjjQVQ
• For the more comprehensive details including setup ad implementation considerations, please see the Release
Training presentation & demo:
• Simplified Geographies
Video: http://download.oracle.com/ocomdocs/global/apps_19A/sales/Simplified_Geographies/index.html
• Simplified Geographies
Handout: http://download.oracle.com/ocomdocs/global/apps_19A/sales/Simplified_Geographies/Simplified
_Geographies.doc
Geo to Address Examples
Geo to Address Coverage Mapping Examples
Mappings of Geography dimension territory coverage examples to Address dimension territory coverage.

Territory Coverage
Geography Definitions Address Definitions
Territory Geo Geo High Country State County City Postal Code Comments
Global ~Global
EMEA ~Global~Europe Middle GB
East and Africa FR
GY
BE
SP
IT
GR
PO
etc….
NAM-US >United States US
NAM-MidWest ~Global~North US OH
America~United US MI
States~Mid West US WI
US IL
US IN
etc….
NAM-Ohio ~Global~North America US OH
~United States~Mid
West~OH
NAM - WA >United States>WA US WA
NAM-CA ~Global~North US CA
America~United
States~West~CA
NAM-San ~Global~North US San
Mateo America~United Mateo
 States~West~CA~San
Mateo
NAM-San ~Global~North US CA San If the county exists in more than
Mateo America~United Mateo one state then the Address State
States~West~CA~San value should be provided
Mateo
NAM-San >United States>CA>San US San
Mateo Mateo Mateo
NAM-Redwood >United States>CA>San US Redwood
City Mateo Mateo> Redwood City City
NAM-Redwood >United States>CA>San US CA Redwood If the city of exists in more than
City Mateo Mateo> Redwood City City one state then the Address State
value should be provided
NAM-Redwood >United States>CA>San US CA San Redwood If the above is true AND the city
City Mateo Mateo> Redwood City Mateo City exists in more than one county
in a state then the Address State
and County values should be
provided
NAM- >United States>94080 US 94080
SoSanFran
NAM-SanFran >United States>94102 >United US 94102-94188 if all account postal code values
States>94188 are 5 digits
NAM-SanFran >United States>94102 >United US "94102-0000"- alternative if account postal
States>94188 "94188-9999" code values are sometimes 5
digits, sometimes 9 digits
NAM-SanFran >United States>94102 >United US 941% alternative if it is easier to use a
States>94188 'Starts With' matching criteria
and account postal code values
may be 5 or 9 digits
Geo to Address Postal Code Matching Examples & Recommendations

Postal Code Recommendations

- Variable length alphanumeric postal codes recommend using starts with (%) and if need to use a between/range define separate rules for matching postal code
number of characters (see Rows 12 & 13)
- Between/Range is recommended for numeric postal codes
- Territory address postal code rules do not allow % plus a range (-) (see Row 9)
- Territory address postal code rules allow - in rules but must use double quotes (see Row 8)

TM Address Rules AM Matching Behavior

Country Postal Code Comments Account Postal Code Value Territory Matched? Alternatives as will not support ~
(tilda)
US 94065 Allowed in UI & 94065 Territory matches
Import 94065-2808 No territory match
94065- No territory match
94066 No territory match
US "94065-2811" Allowed in UI & 94065-2811 Territory matches
Import 94065 No territory match
94065-2813 No territory match
US 94065-94070 Allowed in UI & 94065 Territory matches Add a 2nd rule: 94070% OR write rule
Import 94065-2808 Territory matches as: 94065-"94070-9999"
94065- Territory matches
94066 Territory matches
94071 No territory match
US "94065-0000"-"94070- Allowed in UI & 94065-0000 Territory matches
9999" Import 94065-2808 Territory matches
94065- No territory match
94066 Territory matches
94071 No territory match
94065-4318221 (corner case example) Territory matches
US "94065-0000"-94070 Allowed in UI & 94065-0000 Territory matches If needed can add a 2nd rule: 94070%
Import 94069-2808 Territory matches OR write rule as:
94065- (corner case example) No Territory match "94065-000"-"94070-9999"
94066- Territory matches
94070 Territory matches
94070-4122 No Territory match
94071 No Territory match

GB G1 Allowed in UI & G1 Territory matches

Import G1 7AY No territory match
G9 No territory match
G99 No territory match
GB G1 - G99 Allowed in UI & G1 Territory matches
Import. Need to G1 7AY Territory matches
confirm matching G9 Territory matches
behavior when 2 G99 Territory matches
numbers used in G80 Territory matches
the front section G99 8AW No territory match
of the postal code
GB G1 - G9 G1 Territory matches
G1 7AY Territory matches
G9 Territory matches
G10 8AW Territory matches
G90 No territory match
G99 8AW No territory match
GB G1 0AA - G99 9ZZ Allowed in UI & G1 No territory match
Import, but not a G1 7AY Territory matches
valid rule G9 8DD Territory matches
definition to get G99 7HD Territory matches
the correct G99 8AW Territory matches
territory matches G100 (corner case as max 2 digits in Territory matches
postal codes) Territory matches
G99 Territory matches
G90 Territory matches
G10 8AW
GB G1 0AA - G9 9ZZ Allowed in UI & G1 No territory match
Import - correct G1 7AY Territory matches
way to define G9 8DD Territory matches
address rule when G10 Territory matches
there are only 5 G99 No territory match
characters in the G99 8DD No territory match
postal code
GB G10 0AA - G99 9ZZ Allowed in UI & G10 No territory match
Import - correct G10 7AY Territory matches
way to define G90 8DD Territory matches
address rule when G99 8DD Territory matches
there are 6
characters in the
postal code
GB G1% - G99% Not allowed in UI N/A
or Import
GB G1% Allowed in UI & G1 Territory matches
Import G1 7AY Territory matches
G11 8RW Territory matches
G9 No territory match
G99 No territory match
GB SW1A% Allowed in UI & SW1A Territory matches
Import SW1A 6AN Territory matches
SW1 No territory match
SW1W 8BC No territory match
SW2W 6DF No territory match
GB SW1% Allowed in UI & SW1 Territory matches
Import. SW1 6AN Territory matches
Recommendation: SW1W Territory matches
define a separate SW1W 8BC Territory matches
rule for each
number in first
part of postal
code, as long as
postal code such
as SW1A and
SW1W are also
 included in the
boundary

CA V0A% Allowed in UI & V0A Territory matches

Import V0A 0G9 Territory matches
V1A 7B9 No territory match
CA T7% Allowed in UI & T7 Territory matches
Import T7A 0G9 Territory matches
T9A 7B9 No territory match
CA T4A% Allowed in UI & T4A Territory matches
Import T4A 0G9 Territory matches
T9A 7B9 No territory match
CA V0A-V9Z Allowed in UI & V0A Territory matches
Import V0A 0G9 Territory matches
V1A 7B9 Territory matches
V9Z Territory matches
V9Z 9D8 No territory match
CA V0A 0A0 -V9Z 9Z9 Allowed in UI & V0A No territory match
Import V0A 0G9 Territory matches
V1A 7B9 Territory matches
V9Z Territory matches
V9Z 9D8 Territory matches
Geo to Address State and City Matching Examples and Recommendations
State & City Recommendations
- Partial matches and ranges are not support for fields other than postal code
- Where there may be multiple spellings, and the address data is inconsistent, recommend including rules for all possible
combinations

TM Address Rules AM Matching Behavior

Country State City State Territory Matched?

US MO MO Territory matches
No territory match
US Missouri Missouri No territory match
Territory matches
US Saint Louis Territory matches
No territory match
No territory match
US St Louis No territory match
Territory matches
No territory match
US St. Louis No territory match
No territory match
Territory matches