Thanks Hareesh,
I added the Swap as you suggest into the SOAP Receiver adapter at first PI (the regional SAP PI)
See that the MTB and the SWAP was performed sucessfuly
Do you think &nosoap=tru& may affect in something as you can see below, the SOAP receiver adapter is the start to our B2B (second) PI so I give him the name of the Channel which will trigger the interface at the second PI. Do you see anything strange?
In the first PI, see in the mapping pipeline, the result of the mapping, very simple mapping
Until here is fina, after this picture above, it reaches the Adapter level as I showed some Log of it above, where the MTB and the swap module process sucessfully, but in the end, I can't the see this flat file in the payload in the second PI.
See below the second PI, see that the message has NO Payload.
Do you have any other suggestion?
Regards,
Diego