Oracle Fusion HRMS (Australia)—Release 8 (11.1.

8)

Geography Import and Validation—Detailed Steps for the Australia

Localisation
Contents
Introduction ..................................................................................................................................................... 4
Importing the Geography Structure ................................................................................................................ 4
Importing Geography Hierarchy Data ............................................................................................................. 6
Validating Geography Data Load ..................................................................................................................... 9
Deleting Geography Hierarchy Data ................................................................................................................ 9
Deleting the Geography Structure ................................................................................................................ 11
Managing Geography Validation ................................................................................................................... 12
Appendix ........................................................................................................................................................ 16
Geography Loading Trouble Shooting ....................................................................................................... 16
Example 1 .............................................................................................................................................. 17
Example 2 .............................................................................................................................................. 18
Geography Hierarchy Data File Structure Explanation.............................................................................. 19
Sample Geography Hierarchy Data File ................................................................................................. 19
Geography Hierarchy Data File Columns ............................................................................................... 20
Structure Transformation .......................................................................................................................... 21
SQL Query .................................................................................................................................................. 22

Page 2 of 22
Disclaimer

The information contained in this document is for informational sharing purposes only, and should be considered in
your capacity as a customer advisory board member or pursuant to your beta trial agreement only. 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 in this document remains at
the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of
Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle
software license and service agreement, which has been executed and with which you agree to comply.

This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone
outside Oracle without prior written consent of Oracle.

This document is not part of your license agreement nor can it be incorporated into any contractual agreement with
Oracle or its subsidiaries or affiliates.

Page 3 of 22
Introduction
This document details how to load, validate and delete Australian geography data and how to enable
geography validation. Sample geography data for Australia can be downloaded from My Oracle Support.
See the Sample Geography Data document (Doc ID 1341174.1) for more details.

Importing the Geography Structure

Importing geography data is a two-step process—you first import the geography structure and then the
geography data. The geography structure defines which attributes (country, state, suburb, postal code)
make up an address. The geography data contains the actual values for the states, suburbs and postal
codes.

1. Search for and go to the task “Manage File Import Activities”.

2. Create a new import activity.

3. Enter import options:

 Select “Country structure” as Object type.

 The geography data source file can be uploaded from a local drive and the file extension must
be .csv if it is a text file.
 The data type can be:
1. Comma separated

Page 4 of 22
 2. Fixed width
3. Other delimited
4. Tab delimited
 In order to make it easier to configure the mapping, it is recommended you include a header row
in your source file and tick the "Header row included" check box.
 The Date Format will be used to validate and parse date values, so make sure it is consistent with
the date format used in the CSV file when date columns are included.

4. Map the CSV file columns to the attributes in the geography structure table.

Page 5 of 22
5. Review and activate the activity.

6. After the import activity is activated and run to completion, if there are any errors in the result details,
refer to the Geography Loading Trouble Shooting section in the Appendix. If you want to verify whether
the geography data has been loaded successfully, refer to the Validating Geography Data Load section.

Importing Geography Hierarchy Data

1. Search for and go to the task “Manage File Import Activities”.

2. Create a new import activity.

Page 6 of 22
3. Enter import options:

 Select “Geography” as Object type.

 The geography data source file can be uploaded from a local drive and the file extension must
be .csv if it is a text file.
 The data type can be:
1. Comma separated
2. Fixed width
3. Other delimited
4. Tab delimited
 In order to make it easier to configure the mapping, it is recommended you include a header row
in your source file and tick the "Header row included" check box.
 The Date Format will be used to validate and parse date values, so make sure it is consistent with
the date format used in the CSV file when date columns are included.

4. Map the CSV file columns to the attributes in the geography table.

Page 7 of 22
5. Review and activate the import activity.

6. After the import activity is activated and run to completion, if there are any errors in the result details,
refer to the Geography Loading Trouble Shooting section in the Appendix. If you want to verify
whether the geography data has been loaded successfully, refer to the Validating Geography Data
Load section.

Page 8 of 22
Validating Geography Data Load
1. You can verify whether geography data has been uploaded successfully from the Manage Geography
Hierarchy screen.

Deleting Geography Hierarchy Data

1. Search for and go to the task “Manage Geographies”.

Page 9 of 22
2. Search for the geography code starting with “AU” (Australia).

3. Click on the check mark below “Hierarchy Defined” and select the root node in the Geography
Hierarchy table, which is Australia in this case.

Page 10 of 22
4. Click the delete button to delete all hierarchy data belonging to the selected geography. A warning
message will be shown, click OK if you are sure you want to remove all geography data belonging to
Australia (the country itself cannot be deleted). After removing existing geography data you can upload
new geography data.

5. After deletion, only the country (Australia) is left in the geography data table.

Deleting the Geography Structure

Geography hierarchy data must be deleted before the geography structure can be deleted.

1. Search for and go to the task “Manage Geographies”.

2. Search for the geography code starting with “AU” (Australia).

Page 11 of 22
3. Click on the check mark below “Structure Defined”. You can only delete the geography structure when
there is no hierarchy data. Press the button to delete the geography structure.

Managing Geography Validation

1. Search and go to task “Manage Geographies”.

Page 12 of 22
2. Search for the geography code starting with “AU” (Australia).

3. Click on the icon in the “Validation Defined” column. You can enable validation for the selected
geography. When done, click “Save and Close” to save your changes.

Page 13 of 22
Note: Validation is only available on fields which have lists of values enabled.

You can check how the geography validation works in the hiring process.

If you select a value from the list for a lower level attribute, all the higher level attributes will be
automatically populated with the related values. For example, if you enter the postal code (“4001”) first,
the State and City will be automatically populated with the associated values (“QLD” and “BRISBANE”
respectively).

Page 14 of 22
Note: Validation will be triggered after you have entered a value and move focus to a different control on
the page.

Page 15 of 22
Appendix
Geography Loading Trouble Shooting

After an import activity is activated, it will be scheduled to run and end in the status “Completed” or
“Completed with Errors”. You can find the import result details by clicking on the link in the Status column.

If the Status is “Completed” and Load Errors is 0, the CSV file has been uploaded successfully and all data
has been loaded into the geography tables.

If the Status is “Completed”, but Load Errors is greater than 0, some data has failed to load into the
geography tables, although the CSV file has been uploaded successfully.

Page 16 of 22
If the Status is “Completed with Errors” the following error details are provided for further trouble
shooting.

Example 1
Problem: Geography data CSV file throws an exception of “Java.lang.ArrayIndexOutOfBoundsException
error: please note the column and line are indexed from 0.”

Solution: Check your source file and make sure that all rows have the appropriate number of columns
defined. See the following source file example:

RECORD_TYPE_CODE,COUNTRY_CODE,GEOGRAPHY_TYPE,PRIMARY_GEOGRAPHY_NAME,SOURCE_ID,PAR
ENT_SOURCE_ID,LANGUAGE_CODE,START_DATE,END_DATE
0,AU,COUNTRY,Australia,1,,,,
1,AU,STATE,ACT,1000,1,US,2011/11/28,4712/12/31
1,AU,STATE,NSW,2000,1,US,2011/11/28,4712/12/31
1,AU,STATE,NT,3000,1,US,2011/11/28,4712/12/31
1,AU,STATE,QLD,4000,1,US,2011/11/28,4712/12/31
1,AU,STATE,SA,5000,1,US,2011/11/28,4712/12/31
1,AU,STATE,TAS,6000,1,US,2011/11/28,4712/12/31
1,AU,STATE,VIC,7000,1,US,2011/11/28,4712/12/31
1,AU,STATE,WA,8000,1,US,2011/11/28,4712/12/31
1,AU,CITY,DARWIN,10001,1000,US,2011/11/28,4712/12/31
1,AU,POSTAL_CODE,100001,10001,US,2011/11/28,4712/12/31 --- The fourth column
(PRIMARY_GEOGRAPHY_NAME) is missing in this line, thus causing the error.
1,AU,POSTAL_CODE,801,100001,10001,US,2011/11/28,4712/12/31 --- This is the correct line.

Page 17 of 22
Example 2
Problem: Some geography data is not loaded successfully.

Solution: Check your source file and make sure the correct ReportTypeCodes are used (see the Geography
Hierarchy File Data Columns section for an overview of the ReportTypeCodes).

Source file with invalid ReportTypeCodes:

RecordTypeCode,PrimaryGeographyName,CountryCode,LevelNumber,SourceId,ParentSourceId,Language
Code,StartDate,EndDate
0,Australia,AX,1,10001,,US,0001-01-01,4712-12-31
1,NSW,AX,2,20002,10001,US,0001-01-01,4712-12-31
2,BEACON HILL,AX,3,30382,20002,US,0001-01-01,4712-12-31 --- Wrong use of ReportTypeCode “2” will
lead to a fail in loading geography data. ReportTypeCode “2” is used for creating translated values only.
3,2100,AX,4,40374,30382,US,0001-01-01,4712-12-31 --- Wrong use of ReportTypeCode “3” will
lead to a fail in loading geography data. ReportTypeCode “3” is not supported by the geography loader.

Source file with corrected ReportTypeCodes:

1,BEACON HILL,AX,3,30382,20002,US,0001-01-01,4712-12-31 --- Use ReportTypeCode “1” to create

geography data.
1,2100,AX,4,40374,30382,US,0001-01-01,4712-12-31 --- Use ReportTypeCode “1” to create
geography data.

Page 18 of 22
After changing the RecordTypeCode to “1”, all data can be loaded successfully.

Geography Hierarchy Data File Structure Explanation

This section provides an explanation of the geography hierarchy data file structure.

Sample Geography Hierarchy Data File

RecordTypeCode,PrimaryGeographyName,CountryCode,LevelNumber,SourceId,ParentSourceId,Language
Code,StartDate,EndDate
0,Australia,AU,1,1,,US,0001-01-01,4712-12-31

Page 19 of 22
1,ACT,AU,2,1000,1,US,0001-01-01,4712-12-31
1,NSW,AU,2,2000,1,US,0001-01-01,4712-12-31
1,NT,AU,2,3000,1,US,0001-01-01,4712-12-31
1,QLD,AU,2,4000,1,US,0001-01-01,4712-12-31
1,SA,AU,2,5000,1,US,0001-01-01,4712-12-31
1,TAS,AU,2,6000,1,US,0001-01-01,4712-12-31
1,VIC,AU,2,7000,1,US,0001-01-01,4712-12-31
1,WA,AU,2,8000,1,US,0001-01-01,4712-12-31
1,NORTH RYDE,AU,3,20001,2000,US,0001-01-01,4712-12-31
1,NORTH RYDE BC,AU,3,20002,2000,US,0001-01-01,4712-12-31
1,DARWIN,AU,3,30001,3000,US,0001-01-01,4712-12-31
1,BRISBANE ADELAIDE STREET,AU,3,40001,4000,US,0001-01-01,4712-12-31
1,BRISBANE CITY,AU,3,40002,4000,US,0001-01-01,4712-12-31
1,BRISBANE,AU,3,40003,4000,US,0001-01-01,4712-12-31
1,1670,AU,4,200001,20001,US,0001-01-01,4712-12-31
1,1670,AU,4,200002,20002,US,0001-01-01,4712-12-31
1,2113,AU,4,200003,20001,US,0001-01-01,4712-12-31
1,800,AU,4,300001,30001,US,0001-01-01,4712-12-31
1,801,AU,4,300002,30001,US,0001-01-01,4712-12-31
1,4000,AU,4,400001,40001,US,0001-01-01,4712-12-31
1,4000,AU,4,400002,40002,US,0001-01-01,4712-12-31
1,4001,AU,4,400003,40003,US,0001-01-01,4712-12-31
1,9000,AU,4,400004,40003,US,0001-01-01,4712-12-31
1,9001,AU,4,400005,40003,US,0001-01-01,4712-12-31

Geography Hierarchy Data File Columns

The following table explains which columns are used in the geography hierarchy data file.

Column Comments
RecordTypeCode 0 – Identifier for the country in the geography data (Australia in the sample
file)
1 – Creates a row with the corresponding values under the identified country
2 – Creates a translated name for an existing geography data element (not
used to load English geography data for Australia)
PrimaryGeographyName The value of the country, state, suburb or postal code (depending on the
structure of the geography).
CountryCode AU – Australia
LevelNumber Use the same LevelNumber defined in the geography structure file according
to the geography type of the geography data record. For example, in the
sample file:
1 – Country
2 – State
3 – Suburb
4 – Postal code
SourceId The SourceId and ParentSourceId are used to establish the hierarchical
relationship between the items in the geography data file. The SourceId is the
unique identifier of the data row itself. The ParentSourceId refers to the
[SourceId of the] row of data that “owns” the row of data. For example, take
the following data row for the suburb of North Ryde:

Page 20 of 22
 1,NORTH RYDE,AU,3,20001,2000,US,0001-01-01,4712-12-31

The SourceId = 20001

The ParentSourceId = 2000

If we lookup the row of data where the SourceId = 2000, we find the owner
of North Ryde:

1,NSW,AU,2,2000,1,US,0001-01-01,4712-12-31

This is the row of data that defines the state of NSW. That is correct because
North Ryde is a suburb in the state of NSW.
ParentSourceId See SourceId.
LanguageCode US – This code is used for (American) English.
StartDate This is the date when this data row becomes active. If this date is omitted
from the source file, the system will use the current date as the start date.
EndDate This is the date when this data row stops being active. If this date is omitted
from the source file, the system will take 31-Dec-4712 as the default end
date.

Structure Transformation
In order to upload your geography data to Fusion, your geography data file must comply with the
structure outlined in the previous section. If the structure is different, you will have to transform it so it
complies with the required structure.

Sample Data in Wrong Format:

Pcode,Locality,State --- Header

1670,NORTH RYDE,NSW --- Data
1670,NORTH RYDE BC,NSW
1671,NORTH RYDE,NSW
2113,NORTH RYDE,NSW
4000,BRISBANE ADELAIDE STREET,QLD
4000,BRISBANE CITY,QLD
4001,BRISBANE,QLD
9000,BRISBANE,QLD
9001,BRISBANE,QLD

This data needs to be transformed to following structure required by geography data loader:

RecordTypeCode,PrimaryGeographyName,CountryCode,LevelNumber,SourceId,ParentSourceId,Language
Code,StartDate,EndDate --- Header
0,Australia,AU,1,1,,US,0001-01-01,4712-12-31 --- Country (level 1)
1,ACT,AU,2,1000,1,US,0001-01-01,4712-12-31 --- State (level 2)
1,NSW,AU,2,2000,1,US,0001-01-01,4712-12-31
1,NT,AU,2,3000,1,US,0001-01-01,4712-12-31
1,QLD,AU,2,4000,1,US,0001-01-01,4712-12-31
1,SA,AU,2,5000,1,US,0001-01-01,4712-12-31
1,TAS,AU,2,6000,1,US,0001-01-01,4712-12-31
1,VIC,AU,2,7000,1,US,0001-01-01,4712-12-31
1,WA,AU,2,8000,1,US,0001-01-01,4712-12-31

Page 21 of 22
1,NORTH RYDE,AU,3,20001,2000,US,0001-01-01,4712-12-31 --- Suburb (level 3)
1,NORTH RYDE BC,AU,3,20002,2000,US,0001-01-01,4712-12-31
1,DARWIN,AU,3,30001,3000,US,0001-01-01,4712-12-31
1,BRISBANE ADELAIDE STREET,AU,3,40001,4000,US,0001-01-01,4712-12-31
1,BRISBANE CITY,AU,3,40002,4000,US,0001-01-01,4712-12-31
1,BRISBANE,AU,3,40003,4000,US,0001-01-01,4712-12-31
1,1670,AU,4,200001,20001,US,0001-01-01,4712-12-31 --- Postal code (level 4)
1,1670,AU,4,200002,20002,US,0001-01-01,4712-12-31
1,2113,AU,4,200003,20001,US,0001-01-01,4712-12-31
1,800,AU,4,300001,30001,US,0001-01-01,4712-12-31
1,801,AU,4,300002,30001,US,0001-01-01,4712-12-31
1,4000,AU,4,400001,40001,US,0001-01-01,4712-12-31
1,4000,AU,4,400002,40002,US,0001-01-01,4712-12-31
1,4001,AU,4,400003,40003,US,0001-01-01,4712-12-31
1,9000,AU,4,400004,40003,US,0001-01-01,4712-12-31
1,9001,AU,4,400005,40003,US,0001-01-01,4712-12-31

SQL Query
On-premise customers can run the following query to validate if their geography data was uploaded
successfully.

SELECT * FROM hz_geo_structure_levels WHERE geography_id IN (SELECT geography_id FROM

hz_geographies WHERE country_code='AU');
SELECT * FROM hz_geography_identifiers_vl WHERE geography_id IN (SELECT geography_id FROM
hz_geographies WHERE country_code='AU');
SELECT * FROM hz_geographies WHERE country_code='AU';
SELECT g.geography_id, g.geography_type, g.geography_name, g.geography_code, g.start_date,
g.end_date, gi.identifier_value, gi.identifier_type
FROM hz_geographies g, hz_geography_identifiers_vl gi
WHERE g.geography_id=gi.geography_id
AND g.country_code='AU';

Page 22 of 22