why is location information stored in 2 tables HZ_LOCATIONS AND HR_LOCATIONS
Hi,
Is there a reason to store location information in 2 tables hr_locations and hz_locations, instead of one.
We are in the process of deactivating couple of addresses.
what will be its impact on different modules viz iprocurement, Purchasing, HR, Tax ...etc.
Is there a note or whitepaper which describes the dependencies of locations in different modules.
Regards,
Megan