Procedure:Update a specific geography, for example the city San Francisco or the country United States, and specify details such as the geography's date range, primary and alternate names and codes, and parent geographies.
The geography you want to update must be already defined. See: Defining Geographies. If you want to update a specific country, it must be in the FND_TERRITORIES table.
Procedure:This table describes some terms in the pages used for this procedure.
Selected Terminology
| Term | Description |
|---|---|
| Data Provider | The source of the geography name or code. The data provider is User Entered if the name or code was manually added to the list of geographies. See: Defining Geographies. |
| Time Zone | The time zone that the geography is in. |
Update general information for the geography.
Update primary and alternate names and codes. Names must be unique, and codes unique within a code type.
An example of primary and alternate name usage is in real-time address validation. For example, the primary name is CA and alternate names are Cal and Calif. If the user enters Cal or Calif, then the application considers that valid and saves the value to the HZ_LOCATIONS table as CA.
You cannot delete a primary name or code until another name or code is selected as primary.
If you select a different name or code as primary, that change is reflected when you revisit the View Details page.
Add geographies, from one level above in the country structure, that are parents of the geography you are updating. When this geography was first defined, a parent-child relationship was already established.
For example, when defining Humboldt county, you added Gilmore City as a city, so Humboldt is the parent of Gilmore City. Gilmore City, however, is also in Pocahontas county, so when you update Gilmore City, you add Pocahontas as a parent. When you define or view details for Pocahontas county, Gilmore City would already be displayed as a city within that county. See: Defining Geographies.
