Hi Nadeem,
I believe you are using global dev system because you have consistent security architecture across all child systems (APAC, Americas, EMEA etc). So I don't see a reason why if an auth object is accepted in one region, it wouldn't be accepted in another region.
Also I would assume that this new auth object is added to the role because you added a new tcode to the role. So would suggest below2 options:
1. If the new tcode is needed for all regions, bring the new auth object into all child systems. Then you would be able to import role without any error.
2. If the new tcode is specific to only EMEA, then don't add it to existing role. Instead create a new role for tcode, or add it to another role which is suitable for this tcode and is used for only EMEA. Then import this role to only EMEA systems.
Thanks