About a year and a half ago we started using LDAP to provision and update all of our users from Active Directory.  We have the Locations table (cmn_locations) where all of our Datacenters and field offices are store.  What we recently discovered was that when LDAP provisioned a new user, their location was added to the cmn_locations table.  So, if someone fat-fingered the city, a new record would be inserted with that invalid city name.  We don't really want the location information from the sys_user table to update the cmn_locations table, but we do want the location information for that user.  Anyone know where or how that could be getting updated from?  I have looked at all the LDAP Import scripts, Scheduled Jobs, Business Rules, etc and don't see anything that is doing that, yet the invalid record that is inserted into cmn_locations was created by the account used to run the LDAP Imports.