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.

Refreshing Loqate Geography Data

edited Dec 1, 2023 4:41PM in Payroll and Global Payroll Interface (GPI) 1 comment
  • Summary:We are planning to refresh Spain Loqate Geography data. We have several environments Test, Dev, Prod etc. What is the recommended & most efficient method to update Spain Loqate data in ALL of our environments? For example...Copy Prod Spain Geography structure and hierarchy to our lowest Dev environment, Delete the Geography data (after downstream dependencies have been documented) and import refreshed Loqate data OR is it necessary to Delete Loqate data an import refreshed Loqate data in each environment individually? Geography IDs that existed PRIOR to the Loqate refresh will need to be corrected so that they are

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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