Sending Customer City and Zip/Postal Code to eQuest
Organizations can send the customer city and its zip/postal code to eQuest.
The setting City Location Level for eQuest Posting allows system administrators to specify the location level that will be considered when posting a requisition to eQuest. Once set, the location sent to eQuest to represent the requisition city will no longer be the reference locations level 3 and its postal code, but the location level specified in this setting. This will allow recruiters to post a requisition to the most precise city location, usually located at level 3 or level 4.
| Setting | Description | Possible Value | Location |
|---|---|---|---|
| City Location Level for eQuest Posting | When posting requisitions to eQuest, the level specified here will be considered as the location level for cities. | A number from 1 to 5 based on locations configuration | Configuration > [Recruiting] Settings |
In SmartOrg (under Locations Element Management), the Zip/Postal Code field is available for each level of location.
In Recruiting, when associating a Location structure to a requisition, the zip/postal code set for the location in SmartOrg is used by eQuest to post a requisition on a job board at the appropriate location (instead of using the reference locations set by the system), provided the City Location Level for eQuest Posting setting has been configured in the administration module.
Requisitions can be associated to any level of company defined locations. When Oracle sends the requisition to eQuest, we always try to send three location values:
Country: this is derived from the mapping between location and the reference location level 1 done in SmartOrg by the administrator.
State/Province: this is also derived from the mapping done in SmartOrg between the location and location level 2. This exists only if the requisition has an associated location at least at the state/province level.
City: by default, this is also derived from the mapping between location and location at level 3, if the requisition is associated to a location with a level 3 mapping. If not, such information is not sent to eQuest, although it is usually required, depending on the country and job board. With the City Location Level for eQuest Posting setting, customers can send a more precise location, as defined in SmartOrg, instead of sending the broader location level 3, which represents a region rather than a city. For a large city such as San Francisco, this does not change the situation that much, although you can define a more precise zip/postal code if required. But for a city like Dublin, CA, which does not exist in our list of reference regions, you can now use your own location instead of using the closest region, which would be Hayward on this example, which is about 10 miles away.
Zip/postal codes will be considered by eQuest when posting a requisition only if the zip/postal code is for the US and few other countries, but not all.