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.

What populates the geography hierarchy and location/address REST LOVs?

edited Sep 21, 2023 5:45PM in Payroll and Global Payroll Interface (GPI) 1 comment

Summary:

hi,

We are noticing the option to select invalid city, state, and county combinations in our UI (see example below& by "invalid" I mean the combination does not exist within our manage geographies hierarchy, I realize it may be valid per google).

When we referenced our geography hierarchy we are unable to find an instance where the combination pictured below exists - does anyone know how these REST LOVs are populated? I would have assumed manage geographies would govern what is populated here...but that does not appear to be the case.

Content (required):

Note the below image includes the cities within Kent County MI per the geography hierarchy - notice Walker is not included

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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