ADRC number for a plant is same in both the clients

[snadupalli1705]

We have situation where a plant is created in 100 client and which generated a ADRC number 4000 for in the client, and when moved TR is moved to 200 and if the same 4000 is already assinged to an existing plant in 200 client for same Dev , system is picking the 200 client address for 100 client plant since the ADRC 4000 is assigned the same, 

example- 

Plant ABCD with ADRC number 4000 country code as HU( Hungary ) , when this TR is moved to 200 and ADRC table if ADRNR = 4000 with Country code CA (Canada) then HU plant now have CA as it country code, this doesn't happen for all but only with same ADRNR number 

[raymond_giuseppi]

There is a KBA on this topic, read 3393039 - Company code or plant address is incorrect after transport (with some procedure to prevent, transport and repair inconsistencies in Customizing addresses)

[HakanHaslaman]

The ADRC number (ADRNR) is being reused across clients, causing address mismatches after transport. This happens because ADRNR is client-independent in some cases.
To fix it, may you can try to use a Client-Specific ADRC Approach, so ensure addresses are stored with client dependency to avoid conflicts. If ADRNR is externally assigned, consider using a different range per client. After transport, verify and update the address in the target client if needed. Implement logic to ensure unique ADRNR assignment per client.

This should prevents plants from inheriting incorrect addresses after transport.