1. Administering Oracle Fusion Field Service
  2. Geocoding in Oracle Fusion Field Service

Geocoding in Oracle Fusion Field Service

Oracle Fusion Field Service tries to geocode a location using the address data provided when the activity is created.

When address information is available for both the activity and the related Work Order, the application uses the address details from the activity first when determining location for mapping and routing. If any part of the address (such as Postal Code or City) is missing in the activity, that missing detail will automatically be filled in using the corresponding value from the Work Order. For example, if Address Line 1 is provided at the activity level but the Postal Code is missing, the system will use the Postal Code from the Work Order. If no address information is entered for the activity, then the full address from the Work Order will be used.

The application uses these fields when attempting to geocode the location:

  • Address (caddress)

  • City (ccity)

  • State (cstate)

  • Zip/Postal Code (czip)

  • Country (country_code)

Work Order related:

  • Address Line 1
  • Address Line 2
  • Address Line 3
  • Address Line 4
  • City,
  • Postal Code
  • State
  • Country

Data provided in these fields are submitted to the geocoding service without any modification or manipulation. When the geocoding service resolves a location, it returns a response with an accuracy level. The better the data quality, the more likely the location is resolved. For example - if you submit “10 Henr St Chartley, MA 02712”, the accuracy level will most likely result in something less then an accuracy level of Address, because Henry is misspelled. Other items to watch out for are extra characters or spaces in the fields, missing or wrong address prefix or suffix, abbreviations that don't match postal guidelines, a new address that is not in any geocoding service, wrong data (wrong zip/post code or street name), and partial data. Any of these items can cause challenges with resolving an address.

Best practices

  • We strongly recommend that you send us the geo-coordinates when you create activities. This ensures that the coordinates are available for use in the application. Send the values using Coordinate X (acoord_x) and Coordinate Y (acoord_y).

  • For the activities associated with the Activity Types that have the Calculate travel option selected, we encourage you add and populate address fields. This helps the application use the information to make the best possible decision.

  • don't include additional address elements in the Address (caddress) field. The element includes but is not limited a business name, unit, flat, suite, floor number, and so on.

  • Avoid uncommon abbreviations, or abbreviations that are part of a defined standard used by the postal authority. It is possible that “Ave”, “Ave.” and “Avenue” can lead to different accuracy resolutions.

  • You may have to experiment to find the best way to send address data to Oracle Fusion Field Service.