on 02-17-2015 10:01 AM
Hi All,
I'm currently working in PI 7.3 dual stack. There is an issue with the CREMAS and MATMAS idocs that are sent from ECC systems. They are being sent through XML HTTP port to PI.
When reaching PI, failing in moni with error "No receiver could be determined". I have checked the message header and the receiver determination, no issues with that.
But when I post the same messages from PI integration engine in RWB, they are getting processed successfully and sent to the corresponding receiver system. So what is the actual problem here? I'm not able to locate the issue. Please help.
Thanks,
Jegatha
Hello All,
Thanks for all your inputs!!
Finally, the issue is solved. The mistake was in the HTTP path used, where there was a unwanted space between '=' and the BS name. We removed it and it started working.
Thanks,
Jegatha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Try clearing sxi_cache.
Regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shaikh,
Thanks for the document. I have configured all the steps as mentioned. The issue has ben resolved as there was some mistake in the HTTP path used in ECC!!
And in the document, it was said like to use HTTP plain adapter in the sender side, which we are not using, but the interface works.
Thanks,
Jegatha
HI Jegatha,
Thanks for the screen shots. It looks fine. Can u try dummy activating the receiver determination and receiver agreement and try restarting the msg
Regards,
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jegatha,
Please provide a screen shot of the RD(complete) for both CREMAS and MATMAS and also the the configuration test in ID successsful one
Regards,
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check sender service and sender interface as displayed in SXI_MONITOR and compare names to those, which receiver determination is configured for. Are they for sure the same?Also message & its namespace, does it fullfil the interface description?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sriram,
Yes. the message header and the Rx. determination matches exactly. When I post it from RWB, I'm using the same sender service and the sender interface (have taken from the message header in sxi_monitor ). There is no message specific namespace since this is idoc.
I have give the screenshot of the message below.
Thanks,
Jegatha
Hi Sriram,
We have tow interfaces for CREMAS and MATMAS. CREMAS is sent to one receiver and MATMAS is sent to two receivers where we have used Rx condition to determine the receiver. But the problem is in both the interfaces.
I checked by testing the configuration with the same payload in ID. It works fine.
Thanks,
Jegatha.
Seems like a configuration issue. Was this working before or is a new interface?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This interface is not working since it has been created. I have re-configured all the objects and checked. But still no luck.
Below are the configurations in place. Tell me if anything else I should check.
HTTP connection (RFC destination type H)from ECC pointing to PI. (necessary partner profile and XML HTTP port)
RFC destination type 3 pointing to ECC system in PI.
Thanks,
Jegatha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please give a screen shot of the failed and successful message in Moni along with your Interface determination and Receiver detrmn
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.