How to resolve conflict in ID Communication channel

Question

Hi  Experts ,
I am getting conflict while importing a communication channel in QA . Basically we have done a change in Interface determiantion in dev system to get this change refelcted iin QA instead of transporting only interface determination whole config scenario has been transported . Transport got imported succesfully but while activating the change list it failed and shown conflict in Communication channel . Now If in Object tab I select SELECTDSPLAYED VERSION  then geeting error merge relation is null if selecting the displayed version then changelist get rejected .in that case it works now but in future also I will not able to make any change in the communication channel and whenever I make change and try to activate it it shows the same version conflict issue .
KIndly help me with your inputs in this regard as sooner or later these transport will be moved to production and I want to keep myself prepared before it goes to production.
Regards,
Saurabh

Answer 1

Hi Saurabh Sharma,
Sorry for missing out that, this issue is with ID (Integration Directory)
I think this has gone wrong in your case. Only interface determination has been changed, but, you have imported whole configuration scenario (along with communication channels).
SAP help [Link|http://help.sap.com/saphelp_nwpi711/helpdata/en/39/f3103e02db137de10000000a114084/frameset.htm ] . Note the following for communication channels: To avoid messages being sent from a productive system to systems in the test landscape, the Integration Builder only exports a selection of attributes. Therefore, address data (host, port) and access data (user, password) are not contained in the export. In the adapter metadata in the ES Repository, such attributes are flagged as not transportable (they depend on the adapter type and are fixed). Once new objects have been imported, you must add the non-transportable attributes in the target system. These additions are retained in any further import of the object.
FYI. Unlike when importing in the ES Repository, when importing objects to a directory, version management always creates a new version for the objects.
Solution, as you are not able to activate objects in ID (Integration Directory) due to error message, reject them. Export only Interface determination and import it in QA system.
Regards,
Raghu_Vamsee