Hi Pushpalatha
Generally, it is possible to have more than 1 ICO for the same sender system and sender interface, if you specify a virtual receiver.
In your particular case, when working with outbound IDocs, you can specify virtual receiver if your IDoc partner type is Customer (KU) or Vendor (LI).
This is a common approach for IDoc interfaces in a B2B scenario, and it is the correct design to prevent the issue you are facing - transport dependency issues on common objects.
If indeed your IDoc type is KU or LI, then you can create a party representing the receiver partner. In the party object, you can specify additional identifiers by adding the IDoc partner number - refer below.
Then use the party as a virtual receiver for the ICO.
Rgds
Eng Swee