on 12-02-2005 5:11 PM
Hi,
I am using SOAP-XI-RFC scenario.
I can successfully get data into my application for some XXX entity.
But, for YYY entity I am not getting data using XI.
I receive a blank XML Response from XI,
When I see the data using the same BAPI_XX I used in XI, it returns me some data in CRM 4.0 !!
What can be the possible causes for it!
Thanks,
Narendra.
HI,
can you in both the cases see data sent by the SOAP Client in XI (sxmb_moni)???
Naveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Narendra,
It may sound crazy, but can you make some changes to the RFC reciever communication channel, activate the channel and test the two cases...
also you are poplulating the same entity in the request message ???
check if there were any authorizations problem on ur back end r3 using su53 for the id u r using.
naveen
ur interface is all synch correct?? soap client initials the call, to xi , xi gets data from crm using the rfc and returns the respose to the soap client.
now what do you see in xi for the response from rfc adapter ???
again, did u get authorizations in CRM using Tcode=su53 for the user id you are using to connect to CRM
naveen
Narendra,
log into CRM, goto se37 execute ur function module, fill in the parameters that the soap client passes and see if the RFC returns any results.
Naveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That was the first thing i did. Thats how I know that data is there in CRM but in XI i m not getting the same.
I have checked with the documentation in BAPI explorer and I am using BAPI_BUPA_CENTRAL_GETDETAIL and BAPI_BUPA_ADDRESS_GETDETAIL. No need to commit explicitly to READ data from that.
any more inputs!!
Thanks,
Narendra.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.