This topic describes how to get you started with importing country structures. It includes the following information:
• The minimum data required and the prerequisite tasks
• How to use Oracle Enterprise Repository Assets to evaluate optional attributes • Additional tips
With the country structure of a country you can define which geography types are part of the country, and how the
geography types are hierarchically related within the country. For example, you can create geography types called State, City, and Postal Code. Then you can rank the State geography type as the highest level within the country, the City as the second level, and the Postal Code as the lowest level within the country structure.
The following table lists the file-based import objects and target objects that you can use to import country structures.
Import Object Target Object
Country Structure
ImpGeoStructureLevel
Identifying and Associating Records with Each Other
To add country structures to a country, or to update existing country structure values using file-based import, your source file must contain information about the country to which the country structure is being assigned. Also, you need to specify the level number at which the geography types you are importing need to be placed. All countries are, by default, placed at Level 1. Create the country structure by increasing the level number as you go down the country structure. Thus, geography types such as states, provinces, and so on, can be placed at Level 2; districts or counties at Level 3, and so on.
To add an additional identifier to an existing party or to update an existing additional identifier record, your source file must include values that enable the import process to identify the existing records. These values will be either source system and source system reference value combination, Oracle Sales Cloud internal ID, or PUIDs, such as business keys or external IDs. If the source of your data is an external system, and if you intend to import updates to previously imported records from the external system, then you can provide the source system code and the unique reference value for the source system's record in your source file. The file-based data import process stores a cross-reference between the source system information and Oracle Sales Cloud internal ID. The import process uses the combination of source system and source system reference value to identify the existing record.
Minimum Data Required and the Prerequisite Setup Tasks
The following table lists the attributes (minimum data) that are required or conditionally required in your import file to create or update a country structure record. You can optionally include attributes that are available for import in your import file but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed.
Attribute Description Prerequisite Setup
Task Creating CountryStructure Record for an Existing Country
CountryCode
The code representingthe country to which the country structure belongs.
Oracle Sales Cloud uses two-letter ISO country codes to refer to countries.
Identify country codes using the Setup and Maintenance, Manage Geographies task.
Required
Attribute Description Prerequisite Setup
Task Creating CountryStructure Record for an Existing Country
GeographyType
A code used for internalreference by Oracle Sales Cloud at an administrative level. For example, this administrative code may be COUNTRY, STATE, COUNTY, CITY, etc. You must include either the LevelNumber or GeographyType field to define the hierarchical structure of your data.
No prerequisite tasks
Required
LevelNumber
The level number for thegeography type in the hierarchy. For example, a country has the level of 1 in the hierarchy because it is the top level.
No prerequisite tasks
Required
The following image depicts a sample attribute mapping to import a country structure.
Using Oracle Enterprise Repository Assets to Evaluate Optional Attributes
Information about all available attributes is included in a reference file located in Oracle Enterprise Repository. Review the reference file to explore other country structure attributes that are available to import and the possible prerequisite tasks for those attributes.
This reference file includes the following information:
• All country structure attributes available for importing.
• The attribute descriptions. If the attribute is exposed in the UI, then the corresponding UI display name is included
• The data type, length, and validation logic. The validation information includes the task or work area where you can
view or define valid values before importing data.
• Default values, if these values aren't provided in your source file.
To access the reference file for country structures:
1. Using your browser, enter http://fusionappsoer.oracle.com. Sign in as a user or a guest to Oracle Enterprise
Repository.
2. Enter any of the following search criteria, then click Search. Note: You can further refine any of the following criteria
by choosing File Based Data Import from the Type list or a release number from the Version list.
◦
If you know the name of the specific spreadsheet reference file, then enter a piece of the beginning of its file name, such as HZ_IMP_GEO_STRUCTURE_LEVELS to find the HZ_IMP_GEO_STRUCTURE_LEVELS_T_Reference.xls reference file.◦
If you know an object to which the spreadsheet applies, then enter the name of the object, such as Contact.3. The results include a set of assets. The assets that apply to file-based import are typically titled <<Object Name>>
Import, such as Contact Import. Within the asset, click the link to the reference file in the Details tab. The file opens in Excel or in another application of your choice.
Note: The results of a search on the beginning of the reference file name might also include the interface table, such as the HZ_IMP_GEO_STRUCTURE_LEVELS_T. This asset isn't a reference file. It's a description of each row in the interface table, and doesn't provide the same guidance for importing data as does a reference file.
Additional Tips
Tip: You can explore related topics by entering the following keywords in Oracle Sales Cloud Help Application search.
• Importing country structures
Tip: For sample country structures and detailed steps for importing country structures, see article 1341174.1 on My Oracle Support.
Related Topics
• Geography Structures (cloned): ExplainedGeography Structures: Explained • Geography Structure, Hierarchy, and Validation: How They Fit Together