Issue after Migration: ID and Content-ID are different in SOAP Payload

Question

Hi Experts,
I am facing a strange issue in the PI landscape after the migration from XI 3.0 to PI 7.1.
The scenario is from R/3 system to TIBCO System (Proxy-to-SOAP). The TIBCO system receives the file in SOAP Format. The message is sent from PI via SOAP adapter to TIBCO System.
There is a attachment coming from the R/3 System along with the main message and the main payload/message has a "attachment-ID" as a field. Earlier what used to happen in XI 3.0 that the "Attachment-ID" used to equal to the "Content-ID" when the SOAP payload was generated at the TIBCO end. Now after migration, in PI 7.1 the "Attachment-ID" and "Content-ID" are different. We have control over the "Attachment-ID" as it is coming from the source payload but we do not have any control over the "Content-ID" as we are not creating it.
Can anyone of you please let me know how the SOAP Payload is created and how the content-ID gets populated in the Header of the SOAP Envelope? Also, can anyone help me to fix this issue? Is it something which needs to be handled by us or the BASIS Team?
Thanks,
Arkesh
Edited by: Arkesh Sharma on Dec 16, 2011 12:53 PM

Answer 1

Hi Ramesh,
Thank You for the very Helpful Answer. Before I proceed and close this thread, I have one more question which comes to my mind:
I create my own SOAP Header if I apply the solution provided by you then will the rest of the details in the SOAP Header payload will change or do I need to customize it for myself? For e.g., there is a field named MessageId in the SOAP Header. If I write a Java Mapping, do I need to manually populate the MessageId field in the SOAP Header of my java code or will it be automatically populated?
My requirement is to change only the content ID of the SOAP Header Payload and the rest of the fields should remain the same as it is. Is it possible with the approach that you mentioned above?
Thanks,
Arkesh