on 04-18-2016 1:38 PM
Hi Experts,
Still we are not resolved this issue .
Please help me on this.
Thanks,
Raju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please check if your service interface definition matches that of your receiver proxy. This is necessary if you have made any changes in service interface after generating your proxy. In this case, regenerate the receiver proxy again.
Also, check the inbound structure in sproxy for any mandatory/data type mismatch
You may also take the data after mapping and do a sanity check by testing the proxy in sproxy tcode itself to check if there's any data related issue
Hi Ravi,
1) Please check if your service interface definition matches that of your receiver proxy. This is necessary if you have made any changes in service interface after generating your proxy. In this case, regenerate the receiver proxy again.
Yes my service definition matches with our receiver proxy and we regenerate proxy also
2) Also, check the inbound structure in sproxy for any mandatory/data type mismatch
check the inbound stretcher in sproxy it's godd
3) You may also take the data after mapping and do a sanity check by testing the proxy in sproxy tcode itself to check if there's any data related issue
And check with AM data in sproxy level it didn't show any data related issues
Still we are facing same error
Please help me on this
Thanks,
Raju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
70 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
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.