Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Geography validation level for country setting for US Only implementation

edited Jun 27, 2023 5:08PM in Payroll and Global Payroll Interface (GPI) 1 comment

Summary:

We have defined Geography validation at State, City, County, Zip code for a US and single state implementation and have selected no validation for 'Geography validation level for country'. Do we need Country validation set to error also? What is the difference between behavior for the settings for Country? Screen shot attached.

The client is a payroll customer.

Content (required):

We have defined Geography validation at State, City, County, Zip code for a US Only implementation and have selected no validation for 'Geography validation level for country'. Do we need Country validation set to error also? What is the difference between behavior for the settings for Country? Screen shot attached.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!