on 07-30-2008 12:04 AM
BAPI_TRIP_CREATE_FROM_DATA works in SE37, but gives error when calling from external program.
The error is "Deserialisation failed". I have the WSDL generated by a Web Service wizard in SE 37,
so there should not be any problem like element name or case(upper/lower) mismatch etc. I populate all mandatory fields.
I am using the web service created by wizard in a InfoPath form.
This is the exact error:
The SOAP response indicates that an error occurred:
Deserialisation failed
Hi MB,
take a look to the code of the OBA Sample Application for SAP v1.0 on http://msdn.microsoft.com/en-us/cc442491.aspx, here you will find the complete code of the sample application and in htis code we used the Trip Create via Web Services, hope that helps. You can download the complete sample and run it on your machine, just change the parameters for the Web Service proxy to your environment.
- Juergen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for this pointer. I downloaded the code and looked at the same. It very useful as conceptual and coding guidance. However, there are many BAPis working in our product already, only a few return the same error "Deserialisation failed" The sample you pointed out uses BAPI_FLTRIP_CREATE but we have problem with the following BAPIs:
BAPI_TRIP_CREATE_FROM_DATA
BAPI_ADDRESSEMP_CREATE
BAPI_FAMILY_CREATE
All of them give error similar to following:
Deserialisation failed
<detail>
<n0:SimpleTransformationFault xmlns:n0="http://www.sap.com/transformation-templates">
<MainName>/1BCDWB/WSS0071212021944898000</MainName>
<ProgName>/1BCDWB/WSS0071212021944898000</ProgName>
<Line>170 </Line>
<Valid>X</Valid>
<ReferenceFault>
<DescriptionText>Error accessing the ref. node 'EMPLOYEENUMBER'</DescriptionText>
<RefName>EMPLOYEENUMBER</RefName>
</ReferenceFault>
<Caller>
<Class>CL_SRG_RFC_PROXY_CONTEXT</Class>
<Method>IF_SXML_PART~DECODE</Method><Positions>1 </Positions>
</Caller>
</n0:SimpleTransformationFault>
</detail>
Any more suggestions are most welcome and highly appreciated.
Have you checked that the field employeenumber is in the response and that it is at the level the WSDL told you? I had the experience in 1 or 2 cases that the response was not in the format the WSDL had. I would recommend checking the response in the ICM monitor and compare it with the WSDL, maybe that helps. Set the log level to the highest level (transaction SMICM).
Looks like the SOAP response is having error
This is part of the trace (I don't know how to analyse the trace correctly)
Logon Error Message< META http-equiv= Content-Type c ontent="text/htm l;charset=UTF-8" >
Anmeldung fe hlgeschlagen
Was ist passiert ?
Der Aufruf de r URL http://sap ecc6:8000/sap/bc /srt/rfc/sap/Z_T OPAZ_ESS_PERSONA LDATA_BDC wurde aufgrund fehlerh after Anmeldedat en abgebrochen.< /p>
< strong>Hinweis
Die A nmeldung wurde i m System EC6 aus gef..hrt. Hierbe i wurden keine A nmeldedaten bere itgestellt.
&nb sp;
< /p>
Was k..nn en Sie tun ?
Falls Sie noch ..ber k eine Benutzerken nung verf..gen, so wenden Sie si ch an Ihren Syst emadministrator.
Fehlercode: ICF- LE-http-c:800-l: -T:-C:3-U:-P:-L: 6
HT TP 401 - Unautho rized
Ih r SAP Internet C ommunication Fra mework Team
< /td>
As described in the SAP Online Help a user needs the roles
SAP_BC_EMPLOYEE and SAP_ESSUSER in the backend.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/38/1a245ac90211d3b587006094b9c9b4/content.htm
Best regards,
Andre
Deserialisation failed
detail
Simple Transformation Fault
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
detail
SimpleTransformationFault
MainName 1BCDWB/WSS0071212021944898000
ProgName 1BCDWB/WSS0071212021944898000
Line 170
Valid X
ReferenceFault
DescriptionText Error accessing the ref. node 'EMPLOYEENUMBER'
RefName EMPLOYEENUMBER
Caller
Class CL SRG RFC PROXY CONTEXT
Method IF SXML PART-DECODE
Positions 1
User | Count |
---|---|
93 | |
10 | |
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.