on 11-23-2009 7:20 AM
I have a webservice to RFC scenario Where I have published a webservice from PI and given it to EP to consume it.
till friday the senario was working fine.But from Today morning I can see the XML structure is changed in Inbound Payload becuse of which mapping failed.
I have not made any change in the system.
Please let me know if anybody has any idea.
<Z_QMNC_SAVE_CORRECTIONS xmlns="urn:sap-com:document:sap:rfc:functions" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><QMNUM xmlns="">001100313880_</QMNUM><ACT_TEXT xmlns="">_<item><TDFORMAT>*</TDFORMAT><TDLINE>sixcth</TDLINE></item></ACT_TEXT></Z_QMNC_SAVE_CORRECTIONS>
Incorrect Payload
<Z_QMNC_SAVE_CORRECTIONS xmlns="urn:sap-com:document:sap:rfc:functions" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><QMNUM>001100313880</QMNUM><ACT_TEXT><item><TDFORMAT>*</TDFORMAT><TDLINE>sdfsdfsdf</TDLINE></item></ACT_TEXT></Z_QMNC_SAVE_CORRECTIONS>
Hi Nidhi,
The absense of xmlns="" in QMNUM and ACT_TEXT might be causing the error...
check this:
1. Check the source structure in Message Mapping->test. IF it is having xmlns fopr the above field then EP should send a payload with this details.
2. Try re-generating the wsdl and make necessary changes in wsdl...
Also see whether the RFC was re-imported withn these few days
Regards
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nidhi,
Regenerate the WSDL file and using any soap utility look how the sender request message should be.. (you can even see the test tab of message mapping and see how the payload should look like. Here only SOAP Headers are not available, but that should not be a problem)
>>how can I check that the EP is sending correct payload
The message in MONI is the one sent by EP.. Also you can try print the request message in EP side
Regards
Suraj
Nidhi,
>>My Question is How can I make sure that EP sends correct payload or why there is a change in Payload structure.
did you tried what I suggested in first reply???
check this:
1. Check the source structure in Message Mapping->test. IF it is having xmlns fopr the above field then EP should send a payload with this details.
2. Try re-generating the wsdl and make necessary changes in wsdl...
May be if you try correcting this you may come to know why this error happend??
Regards
Suraj
Check the source structure in Message Mapping->test. IF it is having xmlns fopr the above field then EP should send a payload with this details.
I did this and xmlns is required but its nort coming in INBOUND payload SO how can I check that why its not coming in Inbound Payload now as earlier it was coming.
My Question is How can I make sure that EP sends correct payload or why there is a change in Payload structure.
Check the payload received by the Sender SOAP adapter:
RWB --> Component Monitoring --> Adapter Engine --> CC Monitoring --> Your Sender Channel --> Click on MEssage ID --> message Content
verify the payload with the expected one...if it differs then the EP team needs to work on it....confirm that no change was done from the EP end....better if you get a view of the payload sent by them.....if needed re-create the wsdl and provide it to them.
Regards,
Abhishek.
Hi Nidhi,
1. Take the payload on Friday and compare with current payload which you got in PI/XI.. Did Friday's payload from EP had the xmlns attribute? IF yes then there is some change done in EP side during weekend..
2. As i mentioned earlier before sending the request message to PI , print it in EP side.. This is a pure java coding which you need.. In case of any problem try pasting the portion of code which calls PI web service here and let us see....
You have two problem.. first how it got changed and second how to correct it.. I will say concentrate on correcting this error and you may come to know how it got changed...
So the (1) question is very important for any further analysis or correction measure.. Also try to do (2) from your end and in case of any help paste the code here
Regards
Suraj
Hi Nidhi,
Strange Error...
Can you brief what is your sender message type and interface ? In any way can you try to remove the empty xmlns from the input payload of PI? I guess the message type need to be modified or if you have imported RFC then the XSD need to be checked.. but a couple of R&D is required...
Try removing xmlns from source side in Message Mapping
Regards
Suraj
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
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.